I thought that the intention for the RTC_WAKEUP alarm was to wake up a sleeping or powered off device. I was a bit surprised to find out that it was not only the Alarm Clock application that registered RTC_WAKEUP alarms, but also the Calendar does this to drive its synchronization. I assume the GMail application uses the same technique.
This means that I cannot use RTC_WAKEUP alarms on my hardware to program an RTC to power on a device on an alarm. Because if I did it would also power up the device when a synchronization activity is scheduled, the device would stay powered up, the battery power would eventually be exhausted, possibly long before the alarm set in the Alarm Clock app is reached. Is this the intended behaviour, or am I assuming to much that the intention for Android was to support alarms to power up a device and sound an alarm as many classic feature phones have supported almost since time immemorial? If this wasn't intended then there needs to be a new RTC category of alarms that does power up the device, and only alarms set in the Alarm Clock or a Calendar event with a reminder can trigger it. TIA --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
