Core Dell 7090, 6 processor/12 extended, 64gb memory, 512 SSD system, 256 SSD Virtual machines, 8TB data/music drive
Network - All Cisco. CS350 switch, RV345 router with 16 ports, wireless are 1832 access points, wireless devices typically use 5ghz connectivity.
Library is 96,000 titles
Following the grade of the Android app to 1.8 952 with the Core at 952, the android app hangs after is not actively used. I use the app on a samsung Note20 Ultra 5G running V12 and a samsung s3 tablet running V9.
Scenario: core is running. using windows 10 access, all systems, a pair on Sonos speakers, and a couple Squeezebox devices all are running just fine. I run Roon on either or both Android devices. The initially connect just fine. I perform whatever management, song queuing I need; all of which works fine as long as I continue to use the android app. Now, I switch to another program. I do not exit the Roon app but leave it in the “running” queue. I come back to the app, say after 1 hour or 96 hours, does not seem to matter. I select the app from the running list, The app “opens”. Here you get different responses, which I don’t believe are necessarily time in the background list, Most of the time, the display shows the last device being managed, the “last” song it started to play. If you try to manage the device: switch to queue or now playing, adjust volume (either with touch or volume key), nothing happens. Some times, when in this state, you can open the menu but not select anything. The only fix is to delete/stop the app from running and restart it. On restart, at least for me, the app comes up, finds the core and runs. The above failure will repeat always when left in the running queue.
This issue did not occur until the recent upgrades. Earlier 1.8 9xx release worked just fine via the android app. As noted, the windows 10 software continues to work even when the android app is hung.
Roaming with the android devices across access points (2), away from home where WiFi fails and reconnects when coming back, etc. does not appear to be cause, or at least the main cause since the failure occurs when staying in one location and trying to manage playback as described above (say reading while music plays in the background). Target device does not matter since I get the same failure scenario using Sonos output, Windows 10 output, or the Squeeze devices.
Please note that I run the core on a Hyper-V machine. I have tested the core on Qnap, Windows 10 dedicated, Windows 10 Hyper-V, and VMware Workstation Pro. I get the same failure scenario regardless of what device runs the core. As a matter of note, running the core under Hyper-V has been the most successful and stable. The main advantage with Hyper-V is that I set the shutdown state to be “Pause” which saves the running state of the virtual machine. Upon reboot of the main hardware, the VM auto-starts and the core resumes running. This improves the core availability by not forcing one to log into the core and run the Roon software since we still can’t get the Roon software to actually work as a service. I know this is a hot debate, but for the Core at least, there must the some way to have it run as a service at boot.