Thank you for the report. The team has prepared a relevant fix in Early Access that will be released with the next production build. You’ll likely see a resolution or some improvement in this behavior with the next Roon release, which we’ll announce in Software Release Notes.
Do you have a large number of items Queued when you experienced the crashes described in this thread?
In relation to your question, it’s hard for me to answer since in some way I don’t think that the list has no limit… it operates on a continuos feed, meaning that there’s always one more
Thank you for your patience. The fix is progressing through our pipeline and should be released soon.
Upon re-reading this thread, however, certain details suggest you have Roon Radio enabled, queueing tracks algorithmically via the “next” button at the end of the playlist. Is that the case?
Do you have “Limit Roon Radio to library” toggled in Settings? What about shuffle?
What I think happens is that after the playlist finishes, the “roon radio” kicks in and the list continues from there, since sometimes I see that the list is small, but after it’s fisnishes it goes on without ever stopping. This means that sometimes when I press next, I may be going so on the list, or on the radio…
independent of the two scenarios above, it crashes when I press more times…
I have read your request but I’m a bit confused, since you wrote that you wanted log’s from the tablet, but on the link that you sent me, there’s no instruction for Android.
Before anything else, please make sure your Roon devices have all been updated to the latest release, build 1470. After that, feel free to share a specific date, time, and name of the track playing when the issue occurs.
Here are the directions for obtaining Android logs:
Connect your PC to Android phone and install ADB (instructions are here (all platforms)). Then:
Helllo
I tried to execute your procedure, but this is what I got
platform-tools> adb shell
adb : The term ‘adb’ is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that
the path is correct and try again.
At line:1 char:1
Are you able to share the entire Roon app logset from the affected device, with a specific date, time, and name of track playing when the crash occurs? What you’ve sent is helpful, but our development team will need the full log report for additional review.
With that, and I apologize if this has been glazed over as the length of this thread is now quite long - do you reproduce this issue when using the .APK version of Roon? What about Roon Arc? Downloads below:
Not totally clear what you need me to do. The log that I sent was a good example of the situatiom since the first part all was workin well, and I stopped the log when it crahsed, so if you jump to the end you will see and event.
Please note that this is not associated with a track…, but with “stressing” the system.
Thanks for letting us know the issue is not associated with the track. We’ve been able to review your diagnostics and found an instance of the crash, we are reviewing the exact error with the team and will get back to you once we have discussed. Thank you in advance for your patience.