Snooze fails with ICS

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Galaxy Nexus with ICS 4.0.2
2. Alarm goes off, press Snooze
3. Alarm never goes off again

What is the expected output? What do you see instead?
I verify that after pressing snooze the next alarm time is 10 minutes away.  
But the 10 minutes comes and goes and Alarm Klock never sounds the alarm again. 
 After 10 minutes the alarm goes back to 23 hours, 50 minutes.  No indication 
of force close is present.

What version of the product are you using? On what operating system?
1.7 on stock unrooted 4.0.2 ICS. (Galaxy Nexus LTE on Verizon).

I've been using Alarm Klock for years.  I know it doesn't get updated often but 
I'd love to see this fixed for ICS.  Thanks.

Please provide any additional information below.

Original issue reported on code.google.com by afrat...@gmail.com on 27 Mar 2012 at 2:22

[GoogleCodeExporter]

I am using the HTC one s that runs ICS and am experiencing the exact same 
issue. I've also used AlarmKlock forever and would hate to have to switch, but 
a girl's gotta snooze.  Please fix!

Thanks!

Original comment by colleen...@gmail.com on 8 May 2012 at 10:38

[GoogleCodeExporter]

Same here, using this app for the last 2 years now, worked without fail. When 
updated my Arc to ICS, snooze has stopped working.

A fix would be highly appreciated.

Thanks.

Original comment by pkolas@gmail.com on 14 Jun 2012 at 12:40

[GoogleCodeExporter]

Similar problem on the HTC One XL, but for me only randomly occurs. 

Previously had ASOP ICS on a HTC Desire & didn't have the issue - not that I 
noticed anyway.

Original comment by bgclar...@gmail.com on 16 Aug 2012 at 1:32

[GoogleCodeExporter]

Same issue!  ICS on HTC 4G LTE

Original comment by m...@d3solutions.com on 29 Aug 2012 at 6:59

[GoogleCodeExporter]

Same issue here on att skyrocket ICS 4.0.3 ... worked for 4 months without any 
problems, and just couple days ago snooze didn't work.

Original comment by dado.klj...@gmail.com on 30 Aug 2012 at 12:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Same issue on HTC Dream with Android 2.2.1. For a couple of weeks worked with 
no problems, then snooze stopped working (no indication of Force Close). When I 
changed snooze duration, it started working again, but now I don't know when it 
will or won't work, and if you can't trust your alarm clock, you might as well 
not use it. I'm afraid I'll have to change to the stock app until this issue is 
solved. It's disconcerting, though, to see that it's been posted since March 
with a "New" status and only a Medium priority. I can't think of anything that 
is higher priority for an alarm clock app than its reliability. This is really 
too bad, as otherwise I really liked this app.

Original comment by oleggorf...@gmail.com on 27 Sep 2012 at 6:40

[GoogleCodeExporter]

Hi,
I also have this issue, Nexus S with Android 4.1.2. I use AlarmKlock for almost 
2 Years now, and love it. The problems started only recently.

I enabled the debug-settings and found following:
If the alarm is supposed to ring again after the snooze time, it either works, 
OR prints a toast message "RENABLE x" with x being the alarm number.

I also found out, that killing all Tasks/Services with a task manager causes 
exactly the same behaviour. If I kill the services a few minutes before the 
alarm, no problem. AlarmKlock starts again, printing "RENABLE x" for all active 
alarms.

If I kill all tasks 30-40 seconds before the alarm is supposed to happen, it 
fails.

I hope this helps fixing this issue, because it's really annoing to have an 
alarm clock which isn't reliable.

Original comment by ttei...@gmail.com on 7 Nov 2012 at 12:32

[GoogleCodeExporter]

OK, I think I found the problem. I build a version which reliably produces the 
snooze-alarm. This however causes the notification icon to be unreliable. 

I have a plan how to correctly fix this, it'll take a few days to find the 
time, though.
I'll upload a patch once it's working

Original comment by ttei...@gmail.com on 12 Nov 2012 at 10:37

[GoogleCodeExporter]

That's great! I hope you can fix this unrealiability, so I can go back to using 
this otherwise great program. It is my favorite alarm clock app of them all. 
I'll look forward to news about your patch. Thanks!

Original comment by oleggorf...@gmail.com on 12 Nov 2012 at 7:15

[GoogleCodeExporter]

My modification seems to be working correctly. I'm testing it for about two 
weeks now. As soon as I find the time, I'll clean up the code, create a 
possibility for database-upgrade from the previous version and upload a patch. 

Original comment by ttei...@gmail.com on 10 Dec 2012 at 7:31

[GoogleCodeExporter]

That's great to hear! I can't wait for your patch to be available, so I can fix 
this apps and be able to use it again. Thanks for your efforts, and I look 
forward to news of the patch.

Original comment by oleggorf...@gmail.com on 21 Dec 2012 at 10:23

[GoogleCodeExporter]

It took a little longer than expected, but I tested my fix for a few weeks now.
For my use scenario, it works perfectly. I hope thats true for all others, too.

I'm not sure if the upgrade-path works, if the new version crashes, please 
remove the stored data of the app. (Android settings -> Apps -> Alarm Klock, 
there's a "clear data" button (or similar. mine is german, don't know how it's 
labelled in english)).

Please let me know if this patch works. I'm not sure I created the diff file 
correctly.

Original comment by ttei...@gmail.com on 23 Jan 2013 at 8:23

Attachments:

• patch_alarmklock_1.7_snooze_fails.diff

[GoogleCodeExporter]

I just saw your message from many months ago... Thanks for the patch, but could 
you please tell me how to apply it?

Original comment by oleggorf...@gmail.com on 22 Oct 2013 at 4:44