Snooze hides UI but song keeps playing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set an alarm with 
Repeat:weekdays, 
Tone: a 2:30 min mp3, 
Snooze: 10 min, 
Vibrate: disable, 
Alarm volume fade: 0-100% over 60 sec

What is the expected output? What do you see instead?
In the morning alarm starts as expected
When pressing snooze song goes on and there's no way to stop it. Didn't
wait for 10 min to see if the UI comes up again. 
I'd expect for the song to stop for 10 min before starting again, ideally
going again from 0-100% of volume. 

What version of the product are you using? On what operating system?
Version 1.3 (I see there's a new one out, so maybe this is fixed already,
in which case, thx and sorry for wasting your time) on HTC Desire with
Android 2.1

Please provide any additional information below.
Fix this and the app is PERFECT. Thx. 

Original issue reported on code.google.com by calinco...@gmail.com on 26 Apr 2010 at 10:21

[GoogleCodeExporter]

Hmmm, this is strange.  There's an explicit call to stop the media player in 
the 
onPause handler of the notification activity.  This means that the media player 
should 
be stopped no matter how the window is closed.  I'm not sure what would happen 
if the 
activity crashed while it was playing a sound, though... Is there a 'force 
close' 
dialog that shows up?  Does the same thing happen when you use any of the 
internal 
sounds?  Both mp3s and the internal sounds are played the same way through the 
media 
player, so I'm not sure why this would happen with one but not the other...  
I'll play 
around with it a bit more.  Let me know if you have any more information.

Original comment by kraigs.a...@gmail.com on 27 Apr 2010 at 12:38

[GoogleCodeExporter]

Nice of you to reply as quickly. No "force close" message. I actually tried last
evening to reproduce the issue, but couldn't. I tried to press snooze while the
fading was supposed to be going on, I tried to press it after the fading should 
have
ended, couldn't reproduce the issue. 

However this morning I got it again. Had to reset the phone to make it stop 
ringing
(any other way to do that ?). I noticed that I pressed the snooze button 
something
like 11-12 minutes after the alarm started ringing, so I tried to reproduce the 
same
scenario, again without any luck. 

I'm thinking now that maybe these times when I was testing and trying to 
reproduce it
the phone was not going in sleep mode (or whatever you call it when the screen 
is
turned off) as I was setting the alarm to start during the next 1-2 minutes, so 
I
won't have to wait around for it. I will try to test this scenario again this 
evening
and let you know about the results. 

Regards.

Original comment by calinco...@gmail.com on 27 Apr 2010 at 3:32

[GoogleCodeExporter]

Issue 7 has been merged into this issue.

Original comment by kraigs.a...@gmail.com on 6 Jul 2010 at 9:10

[GoogleCodeExporter]

I believe I may have fixed this issue in the (not yet released) next version of 
the app.  You can try out the beta release by installing the app via this link: 
http://kraigsandroid.googlecode.com/files/Alarm%20Klock_1.5-beta.apk

I'll be releasing this version in about a week or so.  Please let me know if 
you come across any issues.

Original comment by kraigs.a...@gmail.com on 6 Jul 2010 at 9:13

• Changed state: Started

[GoogleCodeExporter]

I ran some more tests recently. I think what happened (at least in my case) was 
that the default Android alarm was set for the exact same time, so actually it 
was the default alarm that kept ringing even after the Alarm Klock got stopped. 

Original comment by calinco...@gmail.com on 6 Jul 2010 at 11:35

[GoogleCodeExporter]

Good deal.  Let me know if you see any more problems.

Original comment by kraigs.a...@gmail.com on 7 Jul 2010 at 2:07

• Changed state: Fixed