· Good afternoon After today's update 2.70, the application on the PC and Roon ARC on the phone work fine, but the Roon Remote application on the phone opens after the update, the Roon logo appears on a black background and the application collapses (closes?), when opened again the same thing happens. After some time, the application opened, I even managed to listen to a couple of songs, but now the application behaves the same way - it collapses when opened. No pattern was found. Uninstalling and reinstalling doesn't help. The previous version 2.67 (1661) works well.
Smartphone: Nubia Z60 Ultra (NX721J) Operating system Android 15 Snapdragon 8 gen 3 processor. If it's important, screen resolution is 2480x1116
It seems like a pattern has been found:
When the VPN application is running, the Roon application behaves similarly. Once I turn off the VPN, the application opens and works. At the same time, the roon application itself is not tunneled through the VPN (only a few selected applications on the phone are tunneled).
The previous version 2.67 opens and works well in the same situation.
Thanks for writing in! It’s likely the cause of the crashing is related to a known issue, and our development team is already working on a fix. In the meantime there’s a simple workaround that resolves the crashes for most people.
Workaround: enable Notifications for the Roon app on Android
The crashing occurs when the Notifications permission was declined after the 2.70 update. To restore it:
On your Android device, open Settings → Apps.
Select Roon.
Tap Notifications and toggle Allow notifications on.
Fully close and reopen the Roon app.
(Alternatively, long-press the Roon icon →App info → Notifications → Allow.)
After re-enabling notifications and restarting, the app should stop crashing and closing on its own. Let me know if this helps. Thank you!
Yes, I read the related threads about a similar issue. I tried enabling notifications for the installed app as per the instructions above and also enabled notifications on the reinstalled app. But the app still won’t launch, especially with the VPN app running.
Thanks for confirming that, and for testing with notifications enabled both times. Since the notifications workaround didn’t clear it for you, especially with the VPN running, this points to the broader known issue our development team is already tracking here: Android app crashes and stutters after updating to version 2.70.
We’d suggest following that thread for updates on the fix, since your case matches the pattern being investigated there. If the crashing continues once a fix lands, or if anything changes in the meantime, please update us here and we’ll take another look.
I installed the new mobile app build 2.70 (1673) – the app still minimizes when launched with the VPN enabled. If I disable the VPN, the app launches normally.
Thank you for the video! We were able to compare the video with a set of mobile Roon logs, they were exactly what we needed, and they’ve helped a lot.
We’ve been able to confirm the pattern from your logs: every time the app crashed, your VPN’s tunnel network interface (tun0) was active, and the app closed within a second or two of starting up, right as it enumerates the device’s network interfaces.
In every session where the VPN was not active, the app started and ran normally. So this looks like a specific issue with how the 2.70 Remote app handles the VPN network interface at launch, rather than the notifications issue from the other 2.70 thread, which is why enabling notifications didn’t resolve it for you.
The one limitation is that our in-app logs stop at the moment of the crash without recording the underlying error, because the app is being closed at the system level (below what our own logging can capture). To get the missing piece, we’d like to ask for an Android system log (logcat) and a bug report, captured while reproducing the crash. These will show the actual cause and let our development team pinpoint it.
If you’re able to use a computer with ADB (Android Debug Bridge), here’s how:
On the phone: enable Developer options (Settings → About phone → tap Build number 7 times), then turn on USB debugging.
Connect the phone to your computer by USB and confirm the "Allow USB debugging" prompt.
Open a terminal/command prompt and run:
adb logcat -c (clears old logs)
adb logcat > roon_logcat.txt (leave this running)
With the VPN enabled, open Roon Remote and let it crash. Reproduce it a few times just to be safe.
Stop the logcat capture (Ctrl+C), then run:
adb bugreport roon_bugreport.zip
Please upload roon_logcat.txt and roon_bugreport.zip to the same link as before:
Thank you @Atiss! It’s worth noting that we typically don’t fully support the use of VPNs in this case, but we’ll flag for our development team to see what our options are.
Sorry for the delay! I collected the logs, but it seems the smartphone vendor has disabled the ability to output logs to the main at the software level, so the roon_logcat.txt file appears empty. However, the bugreport generated an archive with various files. I’ve downloaded both files (just in case) from the link you provided.
Thank you for your work and effort! I understand that VPN support is not advertised, and for the most part, I don’t need a VPN enabled for home use. However, I’ve already encountered the problem of the Roon Remote not launching due to the VPN being enabled. As a reminder, it worked on the previous version and didn’t cause any issues with the VPN, so disabling the VPN didn’t seem like an obvious solution. Thanks anyway!
