Unable to shut off alarm after exiting myLock custom lock screen

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enable myLock custom lockscreen, disable 'secure mode'.
2. Enable alarm.
3. When alarm sounds, exit myLock screen.

What is the expected output? What do you see instead?
The alarm is still sounding and there is no way to stop it short of
powering down the phone.

What version of the product are you using? On what operating system?
myLock widget Lockscreen 1.1 beta r2 on an HTC Desire phone.

Original issue reported on code.google.com by joost.cassee on 19 May 2010 at 7:14

[GoogleCodeExporter]

seems like it might be caused by a flaw in the HTC modified alarm. I've also 
had 
reports of this on eris 2.1 and the incredible 2.1. On non htc with only google 
source, we have a flag in the activity called "no_user_action" which 
essentially 
allows the alarm to work. Without it, the alarm doesn't sound, it is stopped 
immediately because of the existence of the lockscreen.

What I recommend though is not to run the custom lockscreen when the phone is 
idle 
with an alarm set. I am not sure we have a way to fix this since it is only 
impacting 
HTC.

Original comment by myLockan...@gmail.com on 21 May 2010 at 3:33

• Changed state: Accepted
• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

this has been reported even with auto unlock version. don't know how to fix it 
vs HTC 
alarm. they've done something different than the stock 2.0 alarm..

Original comment by myLockan...@gmail.com on 23 May 2010 at 6:37

[GoogleCodeExporter]

This is the same issue reported as no. 35.  Note that it is not custom 
lockscreen
dependent.  I have the basic auto unlock function only.  I'm afraid I am not a
dveeloper and cannot help but notice the follwoing that may be useful for 
someone to
help debug.

When the phone powers on MyLock dismisses the keyguard screen.
When the phone powers on because of a phone call, a "special" keyguard screen 
comes
up (slide to answer) which is not dismissed by MyLock.  This is good behaviour.
When the phone powers on because of an alarm, there is another "special" 
keyguard
screen (slide to dismiss or snooze), but MyLock dismisses this screen.

It would seem (to a non-programmer) a rather trivial matter to add the 
alarm-keyguard
screen to the same exception settings that are used for the incoming 
call-keygaurd
screen.

Original comment by golightlygl on 23 May 2010 at 7:15

[GoogleCodeExporter]

The problem being that there's no system event for this HTC alarm whereas it's 
one 
block of code to be notified that the phone call is there so we abort 
dismissing the 
lockscreen, which has been in myLock since the earliest alphas because it's 
problematic to allow our code to continue processing while calls are going.

HTC has made a poor poor choice to actually tie the alarm dismissal to the 
lockscreen. All they had to do was recycle the lockscreen VISUALS and use an 
independent activity using the show_when_locked option if they wanted to use 
the 
(what they consider to be) user-familiar slider UI. Users have proven they 
dislike 
the slider interface and don't want it whether for calls, waking the phone, 
etc. So 
why HTC would feel the need to reuse their stupid slider and be so lazy as to 
add it 
to their literal system lockscreen is far far beyond me.

Another workaround to this would be to download and use an alternative alarm 
clock 
app such as the excellent Klaxon.

I'd go to the effort of creating my own firmware ROM, but I don't even come 
close to 
having time to even update this simple app very often. I'd do a lockscreen that 
was 
so smart, you'd never get a pocket unlock and you'd have a simple auto unlock 
on any 
key press when the phone is in a usable / recognized-use orientation.

Original comment by myLockan...@gmail.com on 25 May 2010 at 3:02

[GoogleCodeExporter]

Original comment by myLockan...@gmail.com on 25 May 2010 at 3:38

• Changed state: Invalid