Have used a U9-H for a few years now. Since a couple of months the device often and by now mostly will not turn off when told to go to sleep. By this I mean that the (far too) bright blue LED remains bright blue; doesn't as it would normally do go to soft green, and the device stays warm to the touch; the screen does turn off. In this state I can also not start it with the power button again; need to yank and replug the power cord to have it functional again.
I.e., seems it's hanging somewhere deep in the shutdown process. I'm using the latest official FW008 Android 6 firmware and have already tried resetting specific apps, resetting the entire device to factory defaults, and reflashing the firmware outright (also briefly tried the CE Android 7 FW and that wouldn't wake up the screen when starting which makes it unusable even for testing). No problems with/during flashing.
The device runs little other than what's supplied OOTB with FW008; it's used mostly for YouTube these days but Kodi 17.6 (later versions have A/V-sync issues but that's always been the case, also when this current problem wasn't) is also used a fair amount.
It's very annoying; will basically need me to throw out the device if I can't fix this in some way. Would anyone know what this would be or would likely be or would perhaps be?
I.e., seems it's hanging somewhere deep in the shutdown process. I'm using the latest official FW008 Android 6 firmware and have already tried resetting specific apps, resetting the entire device to factory defaults, and reflashing the firmware outright (also briefly tried the CE Android 7 FW and that wouldn't wake up the screen when starting which makes it unusable even for testing). No problems with/during flashing.
The device runs little other than what's supplied OOTB with FW008; it's used mostly for YouTube these days but Kodi 17.6 (later versions have A/V-sync issues but that's always been the case, also when this current problem wasn't) is also used a fair amount.
It's very annoying; will basically need me to throw out the device if I can't fix this in some way. Would anyone know what this would be or would likely be or would perhaps be?
