search

novendraap / kraigsandroid

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

Alarm not ringing because of "notification timeout" #43

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Set an alarm for a time in the future
2. Wait until the time the alarm is about to go off and snooze it.
2. Receive an notification from gmail and an sms with ChompSMS as sms 
application during the snooze timeout.
3. Wait until the time the alarm is about to go off again.

What is the expected output? What do you see instead?
The expected output is for the alarm to function as normally and go off.
What happen is that I woke up an hour late thanks to an phonecall, when I 
opened the phone and alarm klock I received a warning saying something like 
alarm timeout because of notification or something like that (I were in a hurry 
so I didn't have time to write it down).

What version of the product are you using? On what operating system?
Android 2.2.1 with HTC Sense on a HTC Desire HD with version 1.72 of the HTC 
Desire HD Rom and version 1.6 of Alarm Klock.

Please provide any additional information below.
I really love this application and it's features but the most crucial part of 
an alarm is that is reliable and if it's not going to work if a receive an sms 
or email (don't know which caused the bug) I can't rely on it.

Original issue reported on code.google.com by ahult...@gmail.com on 11 Jan 2011 at 10:13

GoogleCodeExporter commented 8 years ago 
Sorry meant to be 
1. Set an alarm for a time in the future
2. Wait until the time the alarm is about to go off and snooze it.
3. Receive an notification from gmail and an sms with ChompSMS as sms 
application during the snooze timeout.
4. Wait until the time the alarm is about to go off again.

Not 1 2 2 3

Original comment by ahult...@gmail.com on 11 Jan 2011 at 10:16

GoogleCodeExporter commented 8 years ago 
This shouldn't happen with gmail, but I'm not familiar with ChompSMS.  Can you 
reproduce the issue when that application is not installed?  I'd be willing to 
bet that it takes exclusive access to the notification audio channel.  If 
that's the case, it's probably a bug with that application.

Original comment by kraigs.a...@gmail.com on 12 Jan 2011 at 3:54

GoogleCodeExporter commented 8 years ago 
I tried to reproduce the problem without success. Both by sending sms and email 
to the phone several times. I don't know what went wrong yesterday. Is there 
any error/warning log somewhere which maybe can tell me more about what went 
wrong and maybe help you as an developer. I haven't developed anything for the 
Android platform yet as I just recently got an android phone so I don't know 
where those sort of logs would be located if there's an central place.

Original comment by ahult...@gmail.com on 12 Jan 2011 at 8:04

GoogleCodeExporter commented 8 years ago 
You can use logcat in adb (the android debugger) to get a tail of the system 
log, but it doesn't give you a lot of history.  Any crash stack trace should 
show up in there.
http://developer.android.com/guide/developing/tools/adb.html

Alternatively, there's a debug version of this application in the download 
section of the project website that will dump a stack trace into a file on the 
SD card if it crashes.
http://kraigsandroid.googlecode.com/files/Alarm%20Klock-dbg_1.6.apk
Again, not much help in hindsight, but if you figure out how to consistently 
reproduce it, this information would definitely be helpful to fix it.

Original comment by cgal...@google.com on 12 Jan 2011 at 3:43