Thanks for the update @Victoria_Carlin .
Please, let us know if the system performs as expected moving forward or if you run into any further issues.
Is there an expectation for when the update will be released out of Early Access?
It eventually crashed that day and wouldn’t reopen unfortunately. I set it aside until today, but it’s still not working. I cleared the cache in the Android settings without luck, then cleared the storage, and eventually uninstalled and reinstalled from the Google play store but it still won’t launch past the title screen where it crashes in about 10 seconds. Roon ARC does the same.
just to make a liar out of me, I tried one more time and it opened. lol. Seemed okay as I was doing things in the menus, but once I started a song, it crashed in a few seconds. I started it again, it got as far as my Home Screen and then crashed. One more try, opened, let me start to scroll through one of my mixes, then crashed. Obviously I give up for today. Itncan be replicated, sort of, but it always seems to be at a different point when it crashes, if it opens at all.
Hello @sherifs ,
The Production release typically follows a 2-3 week cadence after Early Access (unless major issues are found), so it shouldn’t be too much longer.
@Victoria_Carlin - Thanks for sharing those details. Would you be willing to gather ADB logs from the device when the issue occurs? To do so:
Connect your PC to Android phone and install ADB (instructions are here (all platforms)). Then:
- Type adb shell in terminal
- Type logcat v (ref: http://developer.android.com/tools/help/logcat.html)
- Reproduce the problem and let terminal print logs for 3-5 more seconds
- Select output from the moment you started the reproduction of the bug till the very end
- Upload the log here and let us know once you have done so:
https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external
Hello @sherifs - The next production release is out, but please note that it may or may not help with this issue, there was a related fix, but it’s possible that it didn’t help with the issues mentioned in this thread.
@Victoria_Carlin - Have you had a chance to look into the logcat output? If you have any questions, please let us know!
Sorry i have not had time to dig into that yet. I’ve kept the email in my in box though so I won’t forget.
@noris - Update - ok I’ve been shamed - I uploaded some crash logs. 
@noris Thanks, still waiting to see it in the Google Play Store on the Walkman. Right now the Last updated is July 6.
Hey @Victoria_Carlin,
Thank you for uploading those logs, they turned out to be exactly what we needed.
Your log captured two launch attempts, and both ended in the same crash roughly 7–10 seconds in. Both crashes are identical down to the finest detail, which tells us this is a specific, reproducible defect in our code rather than anything random or device-specific in nature.
It also explains the behaviour you described. Roon doesn’t load all of its interface graphics at once, it pulls in more as you move around the app. That’s why it sometimes dies on the splash screen, sometimes reaches your Home Screen, and sometimes waits until you start a track. Each of those moments is Roon loading another batch of graphics, and each one is another chance to hit the issue. Your instinct that it “can be replicated, sort of, but always at a different point” was a genuinely accurate read of what’s happening.
I’m escalating this to our development team now with the crash details from your log. Two things would help:
1. A fuller crash report. The logcat gives us most of the picture but cuts off part of the detail our developers need. If you’re willing to run one more command, this captures everything:
adb bugreportRun that right after a crash and upload the resulting zip to the same link as before. It’s a single command, no need to reproduce anything in a particular way, just crash it and then run it.
One thing worth trying in the meantime, offered as an experiment rather than a fix. The crash looks like it depends on how much free memory the DAP has at that moment. If you reboot the Walkman and open Roon first, before anything else (Symfonium especially, it was running in the background during your test), you may find it opens more reliably and stays up longer. If that does make a noticeable difference, please tell us: it would confirm our leading theory and help the developers narrow it down.
Thanks again for your patience on this one, and for going to the trouble of pulling the logs. 
Uploaded more files. And I did a full reboot on the DAP, only opened Roon. Roon loaded (it’s slow though) and I was able to navigate to a few things but then it crashed. So not having Symfonium or anything else opened didn’t seem to make an appreciable difference. It just “feels” like exactly what it’s doing - with each new action introduced, it gets further and further behind in operating until it eventually gives up! Hopefully you like my assignment of human characteristics to Roon - LOL.
Hi everyone,
We’ve reproduced this internally and have a potential fix in the pipeline that will be released in a future update. Please keep an eye on Roon Software Discussion > Software Release Notes, and we’ll share updates here as they become available from the team.