On OnePlus you can lock them in memory, it’s made it a great Roon remote experience.
The iPad pro 11" should be my go-to but it’s memory limitations and restarting all the time make it a very disappointing experience.
I think Roon is just a memory hog, and maybe the development platform make it difficult to improve that.
A lot of Chinese Android phones pride themselves on battery life and much of this like Apple is around battery and memory optimisation and just keep shutting down apps that are causing potential issues and I often get informed that Roon is reducing battery life by my phone
Yeah it could be aps and how they deal with fast switching I suppose. Yeah I got those notifications all the time when have battery optimisation off. It’s all got worse with Andorid 12 as it’s even more aggressive with wayward apps, which Roon appears to be.
I’ve had the same issue with my iPhone crashing after installing the last 3 builds. A restart of the phone always sorted it out. Can you try?
As for the error you get from Qobuz, this usually happens when they remove the version you have in your library and replace it with another one. Check versions tab and Qobuz app.
Running Core Server on Mac M1 mini with 16 Gb memory. Core is hard-wired ethernet and network speed is 300 mb/second. Access core using MacBook Pro with 32 Gb memory via Wifi. Yet on 936 still upon search, getting frequent messages that Roon servers not available, and search results only reflect my library.
Discography still loading slowly compared to all other sections, even going back to it with the navigational arrows it has the same delay in loading material.
So after my comments yesterday about almost never seeing the black box, twice this morning I have gone into album view to find a black box with two outlines of albums in and nothing else. Throw Roon away and restart it and all is well.
There is a reason I do not contribute to these thread’s, the smugness God’s always come a looking for revenge
Roon Windows Client is using a lot (25%) of CPU cycles.
Configuration: 1.8.936 server running on Nucleus+; 1.8.936 client running on Windows 7.
I can’t swear that this is only since .936, but it’s only since the .936 update that the performance impact on other applications running on my PC has been severe enough for me to look into who the culprit was & it’s Roon. I don’t recall ever seeing this before. Here’s a picture of the system idling. Most of the ~25% illustrated load is Roon “idling”.
@support: Lots of frozen screens on Android tablet (remote) since Update 935 and 936.
Just to let you know.
Samsung Galaxy S5e, latest Android Version 11, One UI Version 3.1 Roon build 935 for remote and 935 or 936 for core.
Not nice! Thanks
Since the 936 update I’m having trouble with playback through my Chromecast group which I’m using since pretty much the beginning since I’m using Roon. The group is set up via the Google Home app, as you do. Running the core on my DS916+.
During playback of a DJ mix, music suddenly stops after just some minutes of play. It didn’t matter where I was playing throughout the mix. Roon interface says: “Roon lost control of the audio device”. Rebooting client/core didn’t help.
Suddenly Roon can not seem to find the Chromecast group at all now under Settings, Audio. But the individual Chromecast devices are usable there as expected, not just as a group all together. It’s not listed anymore under the name I gave during the group setup. Worked fine before.
Spotify is able to play to my Chromecast group as expected without any problems.
I got no network issues whatsoever, most Chromecast devices in my network are LAN cable connected with fixed IP addresses. All good as far as I can see.
I Hope @support can look into this, if they need more info just let me know. Thanks!
Roon is super slow to load album art when popping up discography. This is pretty consistent since the last batch of Roon updates. Currently running Nucleus+ for core and Pi4 (ropieee) as endpoint.
Ipad mini with current ios - Visit Account Page button doesn’t work
Core is running on NUC. Restart didn’t help.
Not sure of course if it worked before…
Thanks
