I dont know what kind of alarm manager or partial wakelock system have you set up but I would surely advise you to refer to Mark's wakefulintentservice. If you can get hold of it correctly, you should not face any problem with the notification. You may require broadcast receiver only to start the alarm if the phone restarts.
I would also advise you to test your app on different devices if you have any and test the results. I dont know why you have multiple notifications when you can have all in one.. I was able to implement similar structure without any issues on nexus and g1. But for droid it didn't work that well.. Also, test all the possibilities the speakers, headphones etc. I would also test the sound files if you are using a custom sound notification. On Apr 27, 11:43 am, code_android_festival_way <festival.s...@googlemail.com> wrote: > Hmm does really no one got an idea what could be wrong here? > > Regards > > On 25 Apr., 19:44, code_android_festival_way > > > > > > <festival.s...@googlemail.com> wrote: > > Well you are right that this will drain the battery pretty heavily. At > > the moment I am using the broadcast which gets fired every n seconds > > and gets caught by the receiver which handles the notifications in its > > onReceive method. But well the problem remains. I haven't found a > > possibility to get the sound noitification working during the wake > > lock. > > > If someone has got a solution for that problem I would love hearing > > about it. :) > > > On 25 Apr., 17:17, Mark Murphy <mmur...@commonsware.com> wrote: > > > > code_android_festival_way wrote: > > > > What do you mean exactly by that? Well I know that 30 seconds or even > > > > lower is very frequent but I would let the user decide how often he > > > > would like to be notified. > > > > I mean you may chew up a fair bit of battery life constantly cycling > > > through processes, starting and stopping receiver and/or service > > > components every 30 seconds. I'd use the battery blame screen in > > > Settings to test and see how bad this is in reality. > > > > -- > > > Mark Murphy (a Commons > > > Guy)http://commonsware.com|http://twitter.com/commonsguy > > > > _Beginning Android 2_ from Apress Now Available! > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to android-developers@googlegroups.com > > > To unsubscribe from this group, send email to > > > android-developers+unsubscr...@googlegroups.com > > > For more options, visit this group > > > athttp://groups.google.com/group/android-developers?hl=en > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to android-developers@googlegroups.com > > To unsubscribe from this group, send email to > > android-developers+unsubscr...@googlegroups.com > > For more options, visit this group > > athttp://groups.google.com/group/android-developers?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group > athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
