My display does not timeout and it might be related to something to do with the asus cover detection. Kills my battery because if some notification or alert happens to turn on the screen after I maually turned it off, it will not timeout again.
Howerver, I don't have a cover or anything but having this bizarre issue when the asus cover option is turned on my display constantly but sporadically flashes off and on. If the asus cover option is unchecked/disabled then the phone SEEMS to work normally until I get a call. The proximity kicks in but then the display turns itself back on. I installed sensor box and the proximity seems to work just fine -- nothing errant. Same applies for all the other sensors including the magnometer which does 35uT which seems right for my part of the world.
Did factory resets, cleared cache partitions, reinstalled stock roms etc... toggled the display timeout settings etc..nothing there.
Finally installed bettery battery stats and checked adb so it seems like some process is going crazy but I'm not sure if this is normal behaviour for the device or not.
But if its a rogue process anyone know how to kill it or whatever?
Attached is screenshot from battery stats and logcat
Howerver, I don't have a cover or anything but having this bizarre issue when the asus cover option is turned on my display constantly but sporadically flashes off and on. If the asus cover option is unchecked/disabled then the phone SEEMS to work normally until I get a call. The proximity kicks in but then the display turns itself back on. I installed sensor box and the proximity seems to work just fine -- nothing errant. Same applies for all the other sensors including the magnometer which does 35uT which seems right for my part of the world.
Did factory resets, cleared cache partitions, reinstalled stock roms etc... toggled the display timeout settings etc..nothing there.
Finally installed bettery battery stats and checked adb so it seems like some process is going crazy but I'm not sure if this is normal behaviour for the device or not.
But if its a rogue process anyone know how to kill it or whatever?
Attached is screenshot from battery stats and logcat
Aucun commentaire:
Enregistrer un commentaire