Still trying to get my head around this. If I manually create a wakelock:
sudo bash -c "echo mylock > /sys/power/wake_lock"
then I can't reproduce the bug (tried 20 times anyway). If I remove that wakelock:
sudo bash -c "echo mylock > /sys/power/wake_unlock"
then yes, I get the bug again. Sadly there's no /proc/wakelocks to get the wakelock state.
Seeing the Greeter have a black background makes me suspicious too. Is phone going to deep sleep before unity8 is ready - as Greeter should be drawn on screen after display is turned off, not before display is turned on.
I need to learn how powerd is interacting with wakelocks
Still trying to get my head around this. If I manually create a wakelock: wake_lock" wake_unlock"
sudo bash -c "echo mylock > /sys/power/
then I can't reproduce the bug (tried 20 times anyway). If I remove that wakelock:
sudo bash -c "echo mylock > /sys/power/
then yes, I get the bug again. Sadly there's no /proc/wakelocks to get the wakelock state.
Seeing the Greeter have a black background makes me suspicious too. Is phone going to deep sleep before unity8 is ready - as Greeter should be drawn on screen after display is turned off, not before display is turned on.
I need to learn how powerd is interacting with wakelocks