Android app - Roon's Achilles heel?

@Matt actually I’ve had that issue as well! Hadn’t really bothered to troubleshoot it and wasn’t necessarily blaming roon. Like you I’ve been assuming it’s a network thing. Don’t really want to buy an apple device just to use roon as it’s a fairly costly endeavor as it is. Maybe I should forget the lifetime exists and just think of Roon in terms of $10 bucks a month (i.e. $120/year). I guess I can just use my windows
laptop as the remote. Kinda clunky but full functionality & at least it does fold back into a tablet, albeit a large and unwieldy one. Roon is amazing in a lot of ways, but not quite the perfect solution I was hoping for. I’m still on the fence about continuing after the trial.

I’ve put an AIO as the master controller on top of my audio rack and use the Web Controller extension instead of Roon, that doesn’t work on my Lenovo devices, for playback control.

The original post in this thread was only about Roon as a remote on Android. That’s how I use it, and it’s worked very well for me, using Pixel 2, LG V35, and Amazon Fire HD10 tablet (the HD10 has some issues, but not Roon’s fault - see my separate thread on that).

I also have an iPad, so I’ve seen both, and while the iPad is marginally more realiable at connecting and not having to reconnect, it’s not a significant difference for me.

I particularly recommend the HD10 as a remote, since it’s often discounted under $100 and is a solid alternative to iPad. (See HD10 thread on configuration tips.)

1 Like

android app needs a notification play/pause button asap


I reported issues with Android version 2 years ago, but the Roon R&D team don’t respond with any plans for a new version. On my V10, there is a staggering sound whenever I turn to another app, e.g. using the browser. This is because this app uses the Services module of Android. This is disqualifying so I have since long reverted to Tidal for Android.

However, the use of V10 as an endpoint, using the built in ESS 9018 DAC, works fine. This provides a decent audio quality compared to more standard DACs. It means one can use an android phone (V10 in my case) as a “wireless DAC”. Used in this context, only using it for Roon, the app works fine.

I have 3 LG V10 connected here and there in the house, to various hifi gear.

I salute any effort made by the Roon team to get rid of this very old bug. It is a problem on some phones, not a problem on others, but it should be a problem on NO phones. The use of services is in dire need of revision.


I’ve just canceled my Roon trial. I’m just going to use a Plex-based solution. I already purchased the lifetime premium membership for Plex. I converted my Pi B 3+ w/ hifiberry pro + from Volumio to a Rasplex headless player, and control it with the plex app. Was a pain to get set up (as it turns out there’s no official release of Rasplex that’s compatible with the Pi 3 B+) but now works great. Plex provides some metadata. Not like Roon, but with these nagging Android issues, which no Roon dev has so much as commented on, I just can’t justify the considerable expense. The Rasplex is not as good as what Roon could be, but it’s much better than the functional but very bare bones volumio setup I had before, and totally free of charge.

It’s a lot to pay, for what is essentially Volumio with Allmusic baked in (both completely free of charge to access and use, individually), and a problematic Android app. It’s not as if Android is a fringe platform. And people have been complaining for literally years. If the Android app was ever free of the issues plaguing it that have been discussed, along with adding the Focus feature and editing to the Android app, I’d reconsider. But there hasn’t been much indication that this will ever happen.

Good luck everyone. I’m out. Peace.


Strange. I used an Samsung Tab S2 and now an Huawei mediapad 5 10" tablet - non of the above problems noticed, and I am a user since the start of Roon. Same for my telephone, first Samsung S6, now Xiaomi Mi Mix2, none of those problems either. Apart from the wish to rotate screens when turning the device i am fairly happy

1 Like

You are not alone -

Android app having trouble finding Linux Core

Workarounds include 1) turning off IGMP snooping on your router, if it will let you, and 2) going into ROCK settings, if you use ROCK, and hitting “Save”.

One plus 5 and galaxy tab S2 here and I don’t have issues. Yes it has to reconnect when it goes into background but it always reconnects quickly and I don’t have an issue with that. If I turn of the battery management it drains the battery in no time so this to me is preferable. I agree it still needs work but it’s better than some I have used.

Biggest issue with the Android app is that audio stutters when using the phone as playback device and the app is backgrounded. Couldn’t find my iPhone headphone adapter so tried mowing the lawn whilst listening to tunes via my Pixel 2… needless to say it didn’t work very well as I couldn’t minimise the app and it kept on stopping playback as the phone moved in my pocket

1 Like

The MOST annoying aspect is the inability of the Android app to access the internal dac. On my FiiO M11, the Qobuz app has no trouble doing this. The Room app still goes through the crippled core Audio of Android. Grrrrr!
When will Room do what Qobuz seemingly has no problem doing?

1 Like

See this recent post by Brian.

What I would like is an ‘Android light’ app: just a simple remote (search, play, stop, forward, rewind, album cover) for Roon. For the full Roon experience I have my laptop, when I’m cooking or something I just need a light version on my phone.

1 Like

I have said in the past that when it comes to mobile devices that different uses require different interfaces. The interface I want when running on a treadmill is not the full interface I might want at home as a full on controller. Same with being in an Auto, etc etc etc.


I’m using a Galaxy Tab A and a fire hd8. Both work fine. App on the phone doesn’t work as well, but a phone is really too small to get the benefit of Roon.

Ditto to all the above.
I’ve on my third year long subscription to Roon and if I’m being entirely honest I feel like there’s now a stubborn determination on Roon’s part to continue to ignore this issue. It’s beyond a joke now and insulting.
I have a LG V30 and Fiio M11. In both cases Roon is the bottle neck in regard to getting the most out of the device’s internal DAC.
Cheap third party apps are capable of bit perfect playback without the need to constantly dumb down the original files with endless and needless processing due to Android’s limitations.
I’m going to reclaim my music library from the shackles Roon loves to apply by not renewing my subscription. Fed up of requesting this simple fix and certainly won’t beg!


It’s been a while because Paul has been patient!
We have a limit to our patience - it’s silly that I have a good DAP (the M11), but end up using just the Qobuz app and the god awful FiiO music app for locally stored music whilst I’m in the same location as my Roon Rock. Crazey!!!
It’s not as if Android is an obscure operating system.
However, I will continue to twiddle my thumbs and hope for the best.


I can understand the frustration, but just to note, we’ve been working on a complete re-write of Android Audio since May – it’s a big project.

We still have work to do on this project, so it’s not going to ship next week… But it’s not being ignored, and will go live as soon as possible.

We really do appreciate the feedback here, guys. Good things coming, even if the wait has been longer than I’d like!


Thanks Mike.

As someone who has worked on android apps, I can appreciate the challenges Roon might have in getting hi-res audio to work reliably in the background.

Unlike iOS where you are targeting a single unified platform, Android can sometimes be a bit like PC development in that phone manufacturers can provide their own implementation of some services (UI) usually with little or no information or support around the unusual and unexpected issues these can often cause to app behaviour particularly when it transitions to the background.

I have spent way too many hours of my life staring at debug dumps in Android studio trying to diagnose such issues and it can be really frustrating and very time consuming. It can also make predicting ship dates really hard as well. You can get to feature complete, fully tested and think you are almost ready to release to app store then one common phone model that isn’t part of your main test matrix turns the apple cart over and sets you back by a couple of weeks because one day it starts acting weird out of the blue.

Very frustrating.