This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
That is a great point to be made, i haven't thought of that.... But no custom kernal (my bootloader isnt unlocked), it is very possible one of my apps underclocks though. I know i have juicedefender on. That might be the problem. Ill check it out. :biggrin: I remember my D1 had this issue when i had it set low and it wouldnt receive phone calls(Got yelled at by some peeps for that).
That is a great point to be made, i haven't thought of that.... But no custom kernal (my bootloader isnt unlocked), it is very possible one of my apps underclocks though. I know i have juicedefender on. That might be the problem. Ill check it out. :biggrin: I remember my D1 had this issue when i had it set low and it wouldnt receive phone calls(Got yelled at by some peeps for that).
You should use something like BetterBatteryStats (on XDA or play) to check the output wakelock. You should also try a third party app. I use AwakeDroid. Be sure to enable vibrate as a backup. There are bizzare instances in which the alarm can't find the sound file you set or that your phone might be automatically silencing the system alarm volume
I use the stock alarm clock app but I'm not rooted or anything. It works well for me; though I have half woken up to music and fallen back to sleep. The alarm says it was silenced after 10 mins. So it sounds like the phone thinks it went off for 10 mins.