It turns out SystemClock.elapsedRealtime() is horribly wrong on a real device (or at least mine). After turning my phone off then running an app that just prints out the value for this, it came out to 8704953600000. On the emulator it's a much nicer number. Having said that, it still works fine if the Alarm is registered on BOOT_RECEIVED.
On Mar 29, 9:22 am, AuxOne <[email protected]> wrote: > I've done extensive tests and realized that the Alarm works perfectly > when I install it to my device via Eclipse (then unplug the cable), > but when I upload it to Android market the Alarm won't even start. > > Investigating further... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
