In the current implementation, the alarm hook is done at triggerAlarmsLocked(), this would stop the app from being notified when the alarm occurs. However, the kernel will be waken from sleep state by the time a blocked alarm got fired by the hardware, as it is already scheduled inside the hardware clock at set()/setRepeating() calls. Correct me if i'm wrong.
If the hook is done at set()/setRepeating() level, the kernel will do nothing about the blocked alarms, it will save more power.
In the current implementation, the alarm hook is done at triggerAlarmsLocked(), this would stop the app from being notified when the alarm occurs. However, the kernel will be waken from sleep state by the time a blocked alarm got fired by the hardware, as it is already scheduled inside the hardware clock at set()/setRepeating() calls. Correct me if i'm wrong.
If the hook is done at set()/setRepeating() level, the kernel will do nothing about the blocked alarms, it will save more power.