Search the Community

I note that my Emby server will not go to sleep if my mobile has used Emby, BUT then the Emby app has been closed and cleared from android recent apps. The server dashboard still show the device in Active Devices: "Emby for Android Mobile 3.0.45" But I have a clue and a way to get the device removed. Apparently, Android 6.0+ will keep apps Active, even though they are not "open" and even if removed from the list of recent apps. The feature is "App Standby": https://developer.android.com/training/monitoring-device-state/doze-standby The Emby app shows as "Active" (not in standby) even when closed. You can enable Developer mode, and see which apps are in Standby, and which are Active: https://www.howtogeek.com/242834/how-androids-app-standby-works-and-how-to-permanently-stop-apps/ (Scroll to "How to See Which Apps Are Currently in Standby") Follow instructions above, scroll to Emby, tap it to toggle from Active to Inactive. Then after a while, the server dashboard drops the device from Active Devices, and will go to sleep. Is there some way to force the Emby app to Inactive/Standby when it is closed?

So here's my scenario: Kodi on HTPC, Emby on Server I always let the HTPC with running Kodi go to sleep while the Server is still active. The Server itself goes to sleep some minutes after this. The next time i wake up the HTPC while the Server is still sleeping, i get the known "Library Sync Thread has Exited" error. Shortly after this i get the notification from the Kodi Emby addon "Server unreachable". Imho this is a simple error in the logic how things are executed. The addon should first check for successful connection before starting the sync thread. If the connection is refused, then don't start the sync thread at all. I can attach the logs in the evening if you want some, but maybe my description is enough to find the culprit?!