Alarm fails except for tiny vibrate, screen backlight won't turn on, power consumption rockets

[GoogleCodeExporter]

This is a speculative bug report and may well turn out to be nothing to do with 
Alarm Klock.

> What is the expected output?

Alarm sounds, phone vibrates, screen backlight turns on and presents alarm UI 
(bypassing lockscreen).  This has been working just fine for many moons.

> What do you see instead?

First time: I can't remember whether or not I had set an alarm, so it's 
speculation, but the symptoms seem very similar to this morning.  I'd had my 
phone charging overnight.  Around lunchtime I went to turn my phone on but 
found that the screen backlight would not turn on.  The backlight behind 
buttons *would* turn on if buttons that normally wake the phone were pressed.  
Being unable to unlock the screen or navigate the power button menu, I had to 
pull the battery to reboot the phone.  Later that day I noticed high battery 
drain; I don't normally have to charge my phone successive nights, just every 
other night.

This morning: I'm pretty sure I heard the vibrate on time but definitely no 
sound, and I'm pretty sure that again I couldn't get the screen backlight to 
turn on (only the button backlight), but in my semi-awake state I just dumped 
the phone back on my bedside table and went back to sleep (later finding it 
dead, having gone to sleep with 80% battery).

> What steps will reproduce the problem?

I haven't found a reliable way to reproduce this (can't make it happen on 
demand simply by setting alarms), from which I conclude that it's a Heisenbug 
and that relying on the alarm to wake me up is a necessary step :)

> What version of the product are you using? On what operating system?

Alarm Klock 1.7 from APK link in issue 49 on CyanogenMod-7.0.3-Desire (Android 
2.3.3) on an HTC Desire GSM.  No change in this in recent weeks.

> Please provide any additional information below.

As Alarm Klock has been working fine for months, I suspect this is either:
 * nothing to do with AK and I'm just blaming it for some other crash which coincidentally causes AK to fail too
 * some unfortunate interaction somehow related to having recently swapped Setting Profiles for Tasker, or some other app change

I'm going to investigate further by setting a separate alarm on another phone 
for a few minutes earlier for the next few mornings, then see if I can still 
catch the logcat if the phone ends up in this state again.  I'm also going to 
leave Battery Graph running to make sure the battery isn't running down 
excessively before alarm time through some other problem.

Original issue reported on code.google.com by zakwil...@gmail.com on 8 Jun 2011 at 11:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hmm, I haven't heard of anything like this before.  I would be a bit surprised 
if Alarm Klock (or any other user application for that matter) would be capable 
of causing a device to exhibit this behavior even if it wanted to.  It sounds 
more like a lower-level problem, perhaps with the non-stock rom you are using?

Original comment by kraigs.a...@gmail.com on 8 Jun 2011 at 3:25

[GoogleCodeExporter]

My suspicion has shifted away from Alarm Klock; something bad is happening well 
before AK goes off, because in last night's test both the sudden high power 
consumption and the screen backlight problem appeared hours before AK was set 
to go off.

Sorry for the false alarm.  You might think I'd have company in rushing to 
judgement and that the bug tracker would have more "alarm failed to sound 
therefore alarm is at fault", but it doesn't look that way.

Got another bug report up my sleeve though, which I'll get to reproducing in a 
few days ;)

Original comment by zakwil...@gmail.com on 9 Jun 2011 at 2:49

[GoogleCodeExporter]

Original comment by kraigs.a...@gmail.com on 10 Jun 2011 at 2:18

• Changed state: Invalid