Closed GoogleCodeExporter closed 8 years ago
I'll double check this code. I apologize that this happens, as my phone(s)
always pass the test.
It would be helpful to know how long it takes before the screen comes on. The
test should either time out (resulting in failure -- not sure why the message
is lingering), or it will complete successfully.
Original comment by jondwil...@gmail.com
on 12 Jan 2011 at 4:27
Good news, it was my fault. Or, at least, it was some unique circumstances on
my phone. I have a replacement Lock Screen (WidgetLocker) instead of the
default HTC Lock Screen. Since there's no real way (without rooting) to replace
the lock screen, this WidetLocker runs as an app, and I'm assuming that
ElectricSleep was 'listening' for an actual unlock that it never saw, even
though the screen did wake up at exactly the right amount of time (about 10
seconds).
The experience I had was that I'd put the phone to sleep when prompted, it
would wake up 10 second later and automatically display the WidgetLocker, which
I unlocked, then the ElectricSleep spinning circle progress animation would
remain until I tapped the back button to stop it (preventing me from continuing
the setup tutorial).
Anyway, I temporarily turned off my replacement lock screen, and your app
worked perfectly.
By the way, I've used it two nights now, and I'm pretty impressed. I wouldn't
have thought my nightime movements could be mapped so well, and never imagined
that they'd be so regular. I'm certainly donating to this project with a market
purchase.
Original comment by shawn.ke...@gmail.com
on 13 Jan 2011 at 1:07
Thanks!
I will check out WidgetLocker (I see that it is a pay app, I'll ask the dev for
a copy) and see what is going on with it. I doubt it can be messing with what
I'm listening for (Screen On/Off 'broadcasts' which are signaled by android
itself) but perhaps there's some other incompatibility going on.
Original comment by jondwil...@gmail.com
on 13 Jan 2011 at 1:24
I was able to solve the problem specific to WidgetLocker, but I'm looking for a
better and more generic solution.
Original comment by jondwil...@gmail.com
on 13 Jan 2011 at 5:37
Original issue reported on code.google.com by
shawn.ke...@gmail.com
on 9 Jan 2011 at 2:18