search

ali-akel / kraigsandroid

Automatically exported from code.google.com/p/kraigsandroid
0 stars 0 forks source link

Sometimes snooze does not work #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
If the alarm goes off and you press snooze, 
somestimes the alarm won't go off a second 
time. 

I'm using an up-to-date HTC Desire.

Original issue reported on code.google.com by tobias.kuendig@gmail.com on 30 Apr 2010 at 4:03

GoogleCodeExporter commented 9 years ago 
In the cases where the alarm does not go off again, is the notification icon 
still 
visible at the top of the screen, or does it disappear after you hit snooze?
Are you running any task-killer apps?

Original comment by kraigs.a...@gmail.com on 30 Apr 2010 at 2:37

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Do you get a force-close dialog?  The only way the notification icon should go 
away 
is if all of the alarms are dismissed or if the application crashes.

If it is crashing, a stack trace would be helpful.  You can pull this from the 
phone's log, but you need the developer kit to do this.  Alternatively, you can 
use 
the debug version of the app here
http://kraigsandroid.googlecode.com/files/Alarm%20Klock-dbg_1.4.apk

This version will create a stack trace in a file on your SD card each time the 
application crashes.  The file will look like /sdcard/xxtimexx-alarmclock.txt

Original comment by kraigs.a...@gmail.com on 30 Apr 2010 at 3:45

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I'm having the same problem on my HTC Hero with Android 2.1.  After pressing 
Snooze, the alarm won't go off again.  If I switch to another application and 
then long-press the Home button to switch back to Alarm Klock, it says 
something like "Alarm Klock wasn't closed normally."  (My language setting is 
not in English.  I don't know what the exact error message is in English.)

I can't tell if the notification icon disappeared because I unchecked "Display 
notification icon" in Application Settings.  I didn't get force close dialog.  
I'm running a task-killer ap (Advanced Task Killer) but already put Alarm Klock 
into the ignore list.

I installed Alarm Klock just a few days ago and this problem happened every 
morning -- it's a miracle I didn't oversleep and get late at work. :P  But I 
reboot my phone yesterday for other reasons, and this morning Alarm Klock works 
well!  Hope it will keep working.  (fingers crossed)

Hope these information would help.

Original comment by deborah....@gmail.com on 1 Jul 2010 at 7:29

GoogleCodeExporter commented 9 years ago 
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:12

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Still broken for me.  Snooze creates a temporary alarm for 10 minutes later (it 
shows up on the lock screen) and then it disappears a few minutes later.

Original comment by bengr...@gmail.com on 7 Jul 2010 at 11:00

GoogleCodeExporter commented 9 years ago 
Hmmm, this is strange indeed.  I haven't heard of anyone else experiencing this 
'disappearing' problem.  Does the alarm eventually go off?  If not, there is 
probably some other application killing the alarm process.

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

GoogleCodeExporter commented 9 years ago 
Disappear might be the wrong word -- the "snooze" alarm never goes off, a few 
minutes later the lock text is just replaced by the next scheduled alarm.  

This may be related, try creating an alarm one minute in the future, it will 
first display in the notification as on the lock screen as 1 minute from now.   
If the alarm doesn't go off it will stay enabled and appear to be scheduled 23 
hours 59 minutes later.  Could the temporary snooze alarms be skipping over 
their scheduled time and staying enabled for the following day?

Original comment by bengr...@gmail.com on 7 Jul 2010 at 2:46

GoogleCodeExporter commented 9 years ago 
bengrimm: Just to confirm, you are seeing this in the 1.5-beta version of the 
app?  Also, could you include the settings for this alarm? (repeats, snooze 
time, etc), and your operating system version and hardware type.

Original comment by kraigs.a...@gmail.com on 7 Jul 2010 at 3:25

GoogleCodeExporter commented 9 years ago 
Yes, using the 1.5beta now (which force closes quite often by the way).  

It happens with repeat enabled, and I've tried with 5 and 10 minute snooze 
times.   I'm using a G1 running android 2.1-update1, but the same problems 
occurred while using android 1.5 and 1.6.

Original comment by bengr...@gmail.com on 7 Jul 2010 at 3:48

GoogleCodeExporter commented 9 years ago 
I didn't realize that you could run anything greater than 1.6 on a G1... This 
version of the app should dump stack traces to your SD card when it force 
closes.  Could you please attach the relevant ones?  I can't seem to reproduce 
the issue on G1 with 1.6 nor Nexus with 2.2...

Original comment by kraigs.a...@gmail.com on 7 Jul 2010 at 3:59

GoogleCodeExporter commented 9 years ago 
Ah yeah, it's a recent Cyanogen release, working quite well.   All 38 force 
closes look substantially like this:  

java.lang.IllegalArgumentException: Service not registered: 
com.angrydoughnuts.android.alarmclock.NotificationServiceBinder$1@43c0fb98
    at android.app.ActivityThread$PackageInfo.forgetServiceDispatcher(ActivityThread.java:930)
    at android.app.ApplicationContext.unbindService(ApplicationContext.java:819)
    at android.content.ContextWrapper.unbindService(ContextWrapper.java:342)
    at com.angrydoughnuts.android.alarmclock.NotificationServiceBinder.unbind(NotificationServiceBinder.java:45)
    at com.angrydoughnuts.android.alarmclock.ActivityAlarmClock$6.run(ActivityAlarmClock.java:158)
    at com.angrydoughnuts.android.alarmclock.NotificationServiceBinder$1.onServiceConnected(NotificationServiceBinder.java:59)
    at android.app.ActivityThread$PackageInfo$ServiceDispatcher.doConnected(ActivityThread.java:1103)
    at android.app.ActivityThread$PackageInfo$ServiceDispatcher$RunConnection.run(ActivityThread.java:1120)
    at android.os.Handler.handleCallback(Handler.java:587)
    at android.os.Handler.dispatchMessage(Handler.java:92)
    at android.os.Looper.loop(Looper.java:123)
    at android.app.ActivityThread.main(ActivityThread.java:4363)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:521)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
    at dalvik.system.NativeStart.main(Native Method)

Original comment by bengr...@gmail.com on 7 Jul 2010 at 4:40

GoogleCodeExporter commented 9 years ago 
Interesting, this is a new crash.  I think I see the problem, though.  I'll try 
to patch the beta later tonight...  Thanks for the catch!

Original comment by kraigs.a...@gmail.com on 7 Jul 2010 at 5:18

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
tobias.kuendig: Thanks for trying it out!
bengrimm: Just updated the beta apk to include a fix for the stack trace you 
pasted.  Let me know if it's still happening.

Original comment by kraigs.a...@gmail.com on 8 Jul 2010 at 3:22

GoogleCodeExporter commented 9 years ago 
This has grown into a super bug report.  I'm going to close it.  Please open a 
new one with any specific issues that might still be present in the new release.

Original comment by kraigs.a...@gmail.com on 12 Jul 2010 at 1:56