Roon Remote app freezing and closure when accessing album art (ref#6U83PC)

What’s happening?

· I am experiencing freezes or crashes

How can we help?

· I am experiencing freezes or crashes

Other options

· Other

Describe the issue

The Roon remote app for Android recently started freezing when I am streaming a song, on the Now Playing screen, and I click on the Album art in an attempt to go the album tracks and information. The app freezes with the message "Loading album..." Once it freezes I have to close the app and reopen it.
However, I found if I navigate to some other screens such as the Home screen, then return to Now Playing and then click on the Album Art it works.

When using the Roon web app on a PC Windows 10, I am also experiencing an issue for this same scenario however, it does not freeze but instead the web app simply closes. But navigating in this situation prior to clicking on the Album Art on the Now Playing screen doesn't seem to solve the issue as it does on the Android app; the app continues to close.

Neither issue happens all of the time, it is sporadic but seems to happen 75% of the time lately.

Describe your network setup

My router is provided by my Internet provider, Optimum and it is a Gateway 5. I have my Roon server on a MacBook Pro with a Apple M1 Pro chip, 16 GB of memory.
My MacBook Pro uses WiFi, not an ethernet connection. It passes through a BACCH-dSP software and then into my DAC and then to Marantz SR8015 AVR.

I use a Samsung Galaxy S24 for the Android Roon app and a Windows 11 HP laptop for the Roon web app.

I haven't changed anything for some time, and this issue seems to have started after the last Roon update.

2 Likes

4 posts were merged into an existing topic: Roon app crashes when clicking on certain albums [Fix in Early Access testing]

Hello @Douglas_L_Smith

Thank you for the report.

We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.

You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.

2 Likes

Thanks Vadim.
Additional findings: It seems it doesn’t happen with the Android app or the web app IF when I open them, they don’t open on the Now Playing screen. (For example, they open on the Queue screen. Then I go to Now Playing, and then click on the album art it doesn’t freeze or crash.)

But if I do open on the Now Playing screen, and choose “Go to album”, then back to the Now Playing, then they both do not freeze or crash.

UPDATE: The above is not always true, sorry. I thought I was seeing a pattern but it doesn’t always work as describe above.

Hello @Douglas_L_Smith @David_Mas ,

Would you kindly record the ADB logs for us?

Connect your PC to Android phone and install ADB (instructions are here (all platforms)). Then:

  1. Type adb shell in terminal
  2. Type logcat v (ref: Logcat command-line tool  |  Android Studio  |  Android Developers)
  3. Reproduce the problem and let terminal print logs for 3-5 more seconds
  4. Select output from the moment you started the reproduction of the bug till the very end
  5. Upload the log here and let us know once you have done so:

https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

Will do Vadim but allow me a couple of days if you would. I need to find the time and hopefully won’t need help.
Thanks

Hello @Douglas_L_Smith ,

No worries, please just let us know you’ve had a chance to provide the tests from that result and we can pick this back up again!

Okay, will try to complete tommorrow and let you know.

Hello @Douglas_L_Smith

Thank you for the update. Please keep us posted on the progress.

Vadim, I was able to install ADB on my PC, allowed debugging on my Android. I got to the point where I see my Android device number in Terminal.
But when I type “adb shell” in Terminal it does not recognize this command. (name of cmdlet, function, script file, etc.)
So not sure how to proceed.

Hey @Douglas_L_Smith,

Thanks for the update - Let’s go step-by-step to fix it:

  • Open Command Prompt (not PowerShell) — this is important.
    • Press Win + R, type cmd, hit Enter.
  • In that Command Prompt, type:
adb version 
If you get a version output like:
Android Debug Bridge version 1.0.41
Version x.x.x...

You’re good to go- skip to Step 2.

If you get:

'adb' is not recognized as an internal or external command

then ADB isn’t in your PATH.

Step 2 - Run it from the SDK platform-tools folder directly

If it’s not in your PATH, you can still run it manually - Find where ADB is installed-usually:

C:\Users\\AppData\Local\Android\Sdk\platform-tools
  • In File Explorer, Shift + Right-click inside that folder → choose “Open Command window here” (or “Open in Terminal”).
  • Now type:
adb devices
  • You should see your device listed. Then try:
adb shell
That should open an interactive shell (you’ll see something like $ or :/ $)

Once adb shell works, exit the shell with exit, then run:

adb logcat -v time > log.txt

Then reproduce your issue on your phone.
After a few seconds, press Ctrl + C to stop logging.

You’ll now have a file called log.txt in that folder, that’s what you should upload.

Thank you!

Benjamin, it seems my path is D:\Debugging Tools\platform-tools. (My C drive has very little memory left so had to create a folder on my D drive.)
So when I open Terminal in this folder, it opens Windows PowerShell. If I type “./adb devices” it list my Device. Then if I type “adb shell” it says it is not recognized.
But in another suggestion it says to enter “.\adb”
When I do this I get a very long list that I tried to capture but it will take several screenshots so just sending the first before overwhelming you.


Sorry, I am not very computer savvy.

Update: So once I got my Device ID after entering "./adb devices, I then entered “./adb shell” and then got the $ sign. But I don’t see how to exit so I can type “adb logcat -v time > log.txt” OR should I type “./adb logcat…etc.”

Sorry, I just type “exit”. Then I get this and reproduce the issue on my phone which I did:

And then Control + C. See if you got the log? If not, I will try again, I may have let it run too long.

Oh, it would help if I uploaded the log.

File was uploaded…fingers crossed. Let me know if I need to do it again. However, keep in mind I am having a similar issue on my PC using the Roon web app, but it doesn’t freeze, just closes.

Thanks for uploading that @Douglas_L_Smith and thanks for the reminder; it’s happening across all devices.

You have my apologies if I’ve glazed over this - but are you viewing the same artwork across your different remote devices?

Are these all local files/album artwork?

Let’s see if clearing your Roon Server cache folder may help:

  • Exit out of Roon and Roon Server
  • Find and open your Roon Server database
  • Navigate to /Library/RoonServer/Cache
  • Move the contents of the /Cache folder elsewhere, like your desktop
  • Try restarting Roon and verify if the issue still occurs

It may also help to do the same for your Roon folder as well. Let me know if the same issues occur - thank you! :folded_hands:

Benjamin, I am not sure what you mean by local files. I stream from Qobuz mostly, I do have some saved FLAC files on an external drive as well but mostly from Qobuz.
As a reminder, the issue of freezing is on my Android Samsung Galaxy S24. The other issue when attempting the same action is on my Windows laptop. However, my Roon Server is on a MacBook Pro.
To be honest I am not comfortable moving my Roon Server files on my MacBook Pro which connects to my BACCH-DSP, I am really hesitant to move anything. And I see another User is having the exact same issue who also uses a Samsung but different model. Does the file not help determine the issue?
I’ll do it if absolutely necessary but really don’t want to create another issue.