Roon 1.8 Android hangs and have to force close app [Fixed in Build 795]

When recalling roon today (after a maintenance shutdown of the server) app freezes. Nothing worked, so removed, reinstalled and rebooted S10 Note 5G.

Terse message says try and shift Focus… the Focus button wasn’t on, tapped it, and roon unfroze. It’s been working, but trying to find a track in search… was easier to find it in Explorer and tap through the search that way once I knew what the album was.

So called master at metadata, yeah well. Sadly stuck with roon with no other alternative. I want a divorce! And I don’t like the editor for posting right at the bluddy bottom of the page.

The same here on a S9+, tried everything from another thread. Helps only short time then back to the old behavior

Any response on this? It will be good to see a response or at least an acknowledgment from Roon

1 Like

+1

Huawei Mediapad as a remote for my Nucleus used to work flawlessly 99% of the time, now it’s just a hot mess. The app freezes constantly and usually requires several reboots to work.

Core Machine (Operating system/System info/Roon build number)

NUC 8i5 running ROCK

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Cable modem > Synology RT2600AC > Core (ethernet)
1x Synology mesh RT2200AC mesh router elsewhere in house.
All devices running on same network - only have 1 network in the house.
Own music stored on Synology DS413j via ethernet to router.
Streaming music via Tidal account.

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Ifi zen DAC : USB (to iMac on ethernet to router)
Matrix Element M (ethernet)
Lyngdorf 1120 (ethernet)
Matrix mini-i Pro 3 (wifi)
Sonos Play 5 (wifi)
Sonos Play 1 (wifi)

Control via Roon apps on:
Imac
2 x Huawei mate 10 pro (Android 10)
1 x Huawei mediapad m5 (Android 9)

Core and all controllers are running latest available versions of Roon.

Description Of Issue

Since 1.8 rollout all 3 android devices experience constant crashing / freezing. This being:

  1. Handing on Roon splash screen at startup. This requires force close of apps and multiple attempts to get app to open.
  2. If app is open and you go to control Roon, app is frozen and requires force close and reopen (loop 1 above can then occur).
  3. When force close is required you have to kill all open apps on the android units. Force close of only Roon does not do anything.

Have tried to run the apps / setup in various config:

  • clear apps cache
  • reinstall apps multiple times
  • battery optimisation on / off on Android units
  • 255.255… Subnet for core
  • static / DHCP setup
  • mesh router turned on / off
  • recycle of entire network
  • reinstall core OS
  • changing wifi channels.

Non of the above allow the app to open smoothly.
App has circa 20% success rate on start up and 80% hang rate.

This freezing / crashing was never an issue with 1.7 and related Android apps but is constant since 1.8 and related Android apps.

Hope you can advise here as this issue really is killing the user experience on Roon unless I tie myself to the iMac. That’s really not an option.

Cheers. :+1:

Same problem here (since 1.8) with samsung s8.
Reinstall, clearing cache etc. doesn’t solve the problem.
It needs some tries (1-10; killing the app and start it again) to get connection to roon.
Other android devices (for example Samsung Tab S2) doesn’t show this behaviour.

Just thought I’d bump this (again)
Starting Roon app on the android tablet required 7 “force kill all” routines this morning. Yes that’s right : 7.

Can Roon give some indication as to what the root cause is here and what / when it will be addressed?

It should be very obvious from reading the boards that this is not an isolated issue yet the silence from Roon @support on this is frankly turning into a joke.

This ongoing android issue and the recent Tidal skipping issues are really making me start to think twice about Roon. It just doesn’t work properly recently. I couldn’t care less about purple, font size and wasted real estate. I just want something that works and right now Roon is not a joy to use by any stretch.

Is there anybody out there?

1 Like

I face the same issue - resort kill and try again 2-3 times.
Connecting the phone with USB debugging enabled shows this:

2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Local Time: 03/25/2021 21:48:40 +00:00
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Device Serial Number: 9E3969FB-4681-464B-B5FF-BC0DB01126C6
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Roon Version: 1.8 (build 778) stable
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 OS Version: Android 10
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Mono Version: 6.4.0 ((no/fe64a476)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Application Domain: RoonMobile.exe
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Assembly Codebase: file:///RoonMobile.exe
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Assembly Full Name: RoonMobile, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Exception Source: BrooEngine
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Exception Type: System.NullReferenceException
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Exception Target Site: LoadContext.GetIcon
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Exception Message: Object reference not set to an instance of an object
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Exception Data: none
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 --[ Stack Trace ]------------
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.LoadContext.GetIcon(String name)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 58, N 156
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.BaseImageDrawable.LoadImage()
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 119, N 419
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.BaseImageDrawable.CreateNode(Widget w)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 0, N 27
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.AnimatedDrawable/Node…ctor(AnimatedDrawable spec, Widget w)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 86, N 523
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.AnimatedDrawable.CreateNode(Widget w)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 0, N 51
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.DrawNode.CreateHelper(Widget w, Drawable spec, WidgetState state, DrawNode old, RenNode parent)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 15, N 91
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.ImageWidget._Update()
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 47, N 195
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.Widget.Update()
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 227, N 712
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.Engine.Update()
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 157, N 383
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.DeviceTarget.GuiMainLoop()
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 341, N 919
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Broo.Engine.Engine.GuiMainLoop()
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 BrooEngine, IL 0, N 31
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Sooloos.Application.RoonMain(String[] args)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 RoonMobile.exe, IL 673, N 2403
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 Sooloos.Application.Main(String[] args)
2021-03-25 22:48:40.685 16550-16631/? E/Roon: 03/25 21:48:40 RoonMobile.exe, IL 0, N 19
2021-03-25 22:49:09.882 16550-16550/? D/Roon: Pausing

I am happy to share details on setup, the TL;DR is

Rock on NUC
Roon Bridge on PI 4b
Client on Huawei Mate 20 - Android 10
Rock and Bridge connected via Ethernet - client via WI-FI all on same TP Link Router

The problem arose after 1.8 upgrade

I appreciate that not all problems are easily fixed ASAP, but there seems to be a lack of feedback from @support on this issue

3 Likes

I just installed Roon Server on my Linux machine which was a breeze. I installed the Android app and I find this happening to me. I can’t even log in though. I know Android users are 2nd class citizens but you can try a little harder to not be so obvious about it? I am sure if the iPhone app was doing this it would be fixed already. Last time I looked Android users money was the same as Apple users’.

@noris @dylan @support

Chaps,

This thread is now 22 days open and still no solid reply from @support

It is blatantly obvious, by just skimming this forum, that the 1.8 android app is not working as intended (on Huawei and Samsung devices in particular).

What is being done here? Anything? Nothing?
Is there any debugging going on to try and understand the root cause of this so that corrective action can be rolled out?

To be blunt, but not rude, the complete silence (lack of any update) toward your paying customers on this significant usability issue is nothing short of shocking.

Cheers
And Happy Easter.

1 Like

Hi @ogdens_sliced

Apologies for the delay! Our team’s queue is longer than typical at the moment, but we’re working to get back to everyone as quickly as we can.

I’ve enabled diagnostics on your account so our team can take a closer look at what’s occurring. Can you try connecting your android devices to Roon a couple of times each, closing the app completely between each attempt? This should upload some diagnostics information so our team can take a look.

Thanks!

1 Like

Thanks for the reply.

After reading I just used 2 of my devices. 1 x mediaped m5 and 1 x mate 10 pro.
Mediapad: Attempt 1 crash. Attempt 2 OK.
Mate 10 Pro: Attempt 1 and 2 crash. Attempt 3 OK.

Keep diagnostics open as long as you see fit.

Cheers.

Edit to add:
Right after the post above I opened the media pad again.
Attempt 1 and 2 crash. Attempt 3 OK.

This is the standard cycle these days.

Hi,

on my side the same behavior occurs since the update to 1.8. I have a Mate 20 pro still running on Android 9 and a Motorola device running Android 10.

I often have to kill the app.After a second or third try the App is usable. I reinstalled the App and checked the battery settings as well.

Best
Benedikt

1 Like

I found out I can sign in through desktop app which I guess is signing into the server. After that the Android app was signed in.

After yesterday’s update there was a sporadic moment of no crash and hang.
Today the android apps are pretty useless again with multiple kill all routines required to interface with Roon.
This really is starting to wear thin now.

1 Like

I find it quite interesting that there is no interest from @support when I submit a stack trace from a reproducible bug. The feedback frequency makes me wonder - are you trying to fix this, or is it time to look for other solutions?

2 Likes

Yes, happening on my Samsung S8 too. Often have to close then start the app 3 or 4 times before it opens. Never happened at all before 1.8.

Oddly does not happen on Samsung tablet which is much older than the phone.

1 Like

Hello All,

Thank you for the reports and for bringing this to our attention.

There were a few related threads to this issue, so we have merged them to have all the relevent information in one place.

For those impacted by this issue, can you please let us know the following information?

  1. Model and Manufacturer of Android Device
  2. Android Operating System Version
  3. Roon Core Operating System
  4. A brief overview of your network setup (router model/manufacturer + any access point details)
  5. The exact local time + date of when a hang next occurs on your Android device (only one timestamp is needed for now, please do not provide us a timestamp of every hang)

Thank you!

3 Likes

QNAP NAS HS 251+, 8GB Ram, 2 .1 TB local storage, 200MBS fiber line, TP link SG 1008p network switch, dedicated to Roon, Router is Asus 8c87u, ethernet line to Devialet Expert Pro. Phone, Samsung Galaxy 9+.The hang occurred 7.33 Am SAST, GMT+2 on 8 April. I have stopped using my phone for now, that is how bad it is, using my laptop, which is seriously annoying.

1 Like
  1. Huawei Mate 20
  2. Android 10
  3. Rock running on a [NUC Kit i7-10710U ] - USB attached storage
  4. TP-Link AC-2300
  5. Thu Apr 8 10:23:52 CEST 2021

Can reproduce on request - happens 30% -50% of attempts

1 Like