Open GoogleCodeExporter opened 9 years ago
Ok,
I will investigate this bug
Original comment by michaelt...@gmail.com
on 1 Dec 2009 at 7:48
Can you verify again this issue?
Original comment by michaelt...@gmail.com
on 24 Dec 2009 at 1:39
Hello
I have the same issue with the 0.20 rc1, but not only with incoming calls. The
phone
suspends itself and I must press the power button to recover it. It's not very
useful
with voice mail when you must use the keyboard.
Thanks for the great job on this distrib !
Original comment by pgu...@free.fr
on 7 Feb 2010 at 5:56
exactly the same as skliarie, but using cupcake 0.2.0 RC1
Original comment by dopp...@gmail.com
on 2 Mar 2010 at 11:38
Confirmed for android-on-freerunner-master-daily-20100404.tar.bz2
Original comment by skliarie@gmail.com
on 6 Apr 2010 at 3:58
I'm having the same issue (cupcake 0.2.0 RC1). When I try to send the phone to
sleep after a call by pressing Aux+Power (=End, which I have set to "Home, then
sleep"), the screen briefly goes dark and immediately comes up again.
I have noticed the same behavior after unplugging the phone from a wall charger
(different third-party ones; haven't tried the one supplied). In those
instances I always had the screen lock on while charging. I would then unplug
the phone and press AUX+POWER; same behavior - screen briefly goes dark phoe
wakes up again immediately. When I then press Power, the screen unlocks itself
(but no menu, which would require a second press to Power). Now I can send the
phone to sleep pressing Aux+Power.
So I conclude:
- Something gets stuck, preventing the phone from sleeping or waking it up
immediately if it does.
- Apparently different events can trigger this, some of them being accepting a
call or plugging into/unplugging from a wall charger.
- Whatever is stuck resets itself when Power is pressed. It is really the press
of the button (alone, not in conjunction with Aux), regardless of the UI
behavior it triggers in the current context (can be either Unlock or Menu).
Original comment by mich...@vonglasow.com
on 23 Nov 2010 at 6:35
Original issue reported on code.google.com by
skliarie@gmail.com
on 16 Nov 2009 at 4:24