· My Pixel 9 Pro XL crashes after modifying the volume with slider on the right bottom of the screen. The crash occurs when I use the physical volume buttons on my phone. It is repeatable and is not occurring when I use Roon and do not touch the volume slider.
Tell us about your home network
· Fritzbox modem (WiFi off)--router Asus ZenWifi pro xt12--netgear network adapter--Lyngdorf TDAI-3400 (--=wired). Endpoints MacBook Air 2025, IPhone 15, Google Pixel 9 Pro XL (wireless).
Thanks for the detailed report. We’ve reviewed the symptoms, and since this crash is repeatable on your Pixel 9 Pro XL, we’d like to ask for a little more information to help our development team pinpoint the cause.
Could you please provide us with the following:
A video of the issue: Please record a short video showing the crash reproduction (using the slider and then the physical buttons) and upload it to our Media Uploader
ADB Logs: These logs are crucial for us to see exactly what is failing in the system when the crash occurs. Please follow these steps to capture them:
Connect your PC to your Android phone and install ADB (instructions are here for all platforms). Open your terminal or command prompt. Type adb shell Type logcat -v threadtime (Note: adding -v threadtime usually gives us better timestamps, but standard logcat is also fine). Reproduce the problem on your phone and let the terminal print logs for 3-5 more seconds after the crash. Select the output from the moment you started the reproduction until the end, save it as a text file.
Hi @alex_h, Thanks for your swift reply. If this is the only way to solve this, I think I leave it like it is. First of all, a screen recording will only show my phone turning into a black screen. How is that helpful? And I will not go on the Adb train again. It is meant for rocket scientists: the manual on how to use it is not correct, which means it takes me hours of my valuable time to figure out how to perform all the steps. I’ve done it before for other issues without succes but with heaps of frustration.
Sorry to have bothered you with this bug. You can close the issue. I will have to avoid using the volume control in the meantime.
I completely understand your frustration and hesitation. You are absolutely right that ADB logs involve a technical process that can be time-consuming and tedious, especially if you’ve had negative experiences with it in the past. We definitely don’t want to cause you any extra stress.
I just wanted to clarify why we ask for this: to escalate this issue to our development team and open a formal ticket (Jira) for a fix, we typically need the underlying crash data. The logs allow us to see exactly what fails in the code at the moment of the crash, which is often impossible to spot just by reproducing it on a different device.
That said, I respect your decision. However, if you ever change your mind or decide to give it another shot in the future, please let us know. We’d be more than happy to reopen this and collaborate with you to get it solved.
Hi @alex_h, I understand you need data to solve this and I appreciate your empathy. I will try to retrieve the data with Adb and spend some time to do this.
I’m sorry @alex_h , the link to adb and sdk-manager is even more complicated as the one time I managed to install everything and got it running. I’m afraid it’s impossible for me to get to the point I need to gather data form my phone. The screen recording also does not work because my phone crashes and therefore does not save a recording of the event. Hopefully someone with a computer degree and a Pixel 9 pro XL has the same problem.
If this process is too cumbersome, it’s no problem. We can take the reproduction steps you’ve provided and pass this to the team.
Just to reiterate the sequence and clarify a few details, for due diligence:
Select the Pixel 9 Pro XL’s system output as the active Zone in Roon
Modify the volume using the hardware volume buttons OR the volume slider within the UI.
If you don’t manipulate the volume or use another controller, this crash doesn’t occur.
Does the crash occur if you’re playing to a Zone that is not the phone’s output? We want to isolate this to Roon’s interaction with the Android audio stack.
Hi @connor, thanks for coming back on this. If I set my phone as active zone, I can use my slider and buttons to adjust the volume. If I then set it to my Lyngdorf I can still use my slider and buttons to adjust the volume. When I then go to my homescreen and use the volume buttons my phone crashes to where I have to login again. If I repeat three crashes it crashes to the state of a reboot.
If I am in the Roon app, I can always use my slider and buttons. But if I have done that and go out of the app my buttons always cause the crash. This is very annoying when using apps like YouTube or newsapps with video/sound in it.
When I exit the Roon app and kill it by swiping it away, the volume button can be used again (the music started on Roon, still plays).
Hopefully this description will help you replicate it. If not, maybe my phone is not functioning properly since I seem to be the only one with this issue. Or I am the only one who has a Pixel 9 Pro XL and a Lyngdorf TDAI-3400
Thank you for the detailed description — that’s very helpful, and we appreciate the time you’ve taken to outline the exact behavior.
At this stage, since the application is crashing at the system level, it will unfortunately be very difficult for us to identify and fix the underlying cause without ADB crash logs. Those logs are what allow our development team to see where the failure occurs inside the Android audio stack and Roon’s interaction with it.
That said, we’ve documented your reproduction steps carefully and will share them internally for awareness. If other users with the same device encounter this behavior and are able to provide logs, that may help move this forward.
For now, the best workaround is the one you’ve already identified:
fully closing the Roon app after use before interacting with system volume controls
If you ever decide you’re willing or able to capture ADB logs in the future, please let us know — we’d be glad to revisit this with you.
Hi @Benjamin, Unfortunately I am stuck again (reason I hate this to do). I made usb-debugging active on my phone, installed the sdk tools on my macbook and in terminal I type: adb shell. It says ‘command not found: adb’
I completely understand your frustration. This is the single most annoying hurdle when setting up Android tools; you have the tool, but your computer acts like it doesn’t exist.
The error command not found: adb simply means your Terminal doesn’t know where the adb file is hiding. It doesn’t scan your whole hard drive looking for it; it only looks in specific places.
Since you “installed” the tools, you likely have a folder named platform-tools somewhere (maybe in your Downloads folder or inside your User Library).
Open Finder and locate the platform-tools folder.
Open Terminal.
Type cd followed by a space.
Drag the platform-tools folder from Finder and drop it right into the Terminal window.
It will automatically paste the correct path for you.
Press Enter.
Now, try running the command again, but with a slight change (add ./ to the front):
Success @benjamin ! I managed to create and upload a logfile. I repeated the crashing three times: Every single time I have to login again on my homescreen. The fourth time my phone crashes completely (also where the logfile stops) and is rebooted.
