Comment 18 for bug 1429887

I did some more testing, trying to reproduce this. I did my usual "get dbus-daemon to go crazy because I'm running through a bunch of wifi networks" test in my neighborhood.

After getting my phone to be a bit overloaded, I still couldn't trigger this bug even once.

But I did notice one oddity -- sometimes the phone screen wouldn't finish fading in to full brightness. It would then go to full brightness if I touched the screen.

But that made me think that there is some mechanism/bug by which the fade-in early-exits. So what if this bug is an immediate early-exit to the fade? Then second press is actually accurately received as a turn-off-screen-please request (which flashes the screen to full brightness for a moment). And the third is a normal turn-on-request. Pure conjecture without much evidence. Just a thought.