Hi @Harald_Mauthner,
Many thanks for all the details, yes it seems that Roon is having problems running on certain Android devices, whilst others or fine.
I know Roon’s @support team and their dev’s are on the case.
Fingers crossed for a switch resolution.
Same here with a Sony tablet. Any idea when this is being resolved? Is the Roon team still thinking that a roll back to a previous version is not a useful feature? J River looks tempting again.
We’re currently working on this issue, but as per policy, we do not share timelines of when new builds are expected to be released.
All I can say is that we have been able to reproduce in the QA lab, the devs are aware and there are some changes coming in a new Roon release that should help address this behavior.
@noris Thank you for your response. As you can see there are a lot of users depending on older hardware to control Roon, even though Google isn’t supporting these devices anymore. Then it’s nice to here your team is trying to resolve this.
My Sony Experia Z3 compact tablet (SGP612) doesn’t work any more with build 521, but what’s even worse for me is that my Windows 10 (build 1909) doesn’t work either!
So I have no proper remote controls any more, Build 511 on the remotes worked perfectly with the build 521, but the support refuses as a policy to make the build 511 available as a rollback solution.
I’ve learned my lesson and will keep installers for every build so I can rollback myself or I will switch back to my Euphony Stylus 3.0 player instead of Roon. Euphony is really great and sounds better than the Roon, but I use Roon for the multi room feature, but if the issues keeps going on I will scrap Roon. Unfortunately I recently renewed the Roon subscription.
We’ve released a new update, Roon 1.7 Build 528, which contains improvements that we believe will help with the issues you are experiencing here. Please see our release notes below: