That seems like a terrible solution though. I think we do have a real problem here as this has been confirmed by many users and you can also google the problem and you will see that the stock alarm is not reliable on some devices. As Diane hinted at, this is probably a firmware issue. It would be nice if we can get a developer with one of the affected devices to pull a little weight here by confirming this. For example, a Motorola Droid user. Set the stock alarm to ring in the morning, then turn off wireless over night (flightmode) and turn off the display. Don't use a charger or dock. On some days the alarm will fail, at least this is what my users report.
If we can get someone to submit a log file, we would at least have a confirmed problem. But then what? Do we try to run after the hardware developers? Doesn't seem to be Google's issue. Or do we do workarounds like Pent suggests? I can already see the comments for you app though: "keeps firing up every 10 minutes draining battery, 1 star, learn how to program, uninstalled." And you will get this even if you do explain what and why you are doing it because many users won't pay attention to that. Martin -- 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
