Re: AlarmManager wake locks only fire when the WiFi radio is enabled and connected
Then those are internal to Android code.
Re: A single AlarmManager wake lock is generated at an interval roughly corresponding to the timer setting in "best network switcher
And those are too.
Re:
http://developer.android.com/reference/android/app/AlarmManager.htmlIf you look at "constants" there you'll see "RTC":
"This alarm does not wake the device up; if it goes off while the device is asleep, it will not be delivered until the next time the device wakes up."
And my code in "best network switcher" is like this:
mAlarmManager.setRepeating(AlarmManager.RTC, now + interval, interval, operation);
So I suppose what may be happening -- since it's a "no wake up" alarm type, the system will not wake up the device just for that.
OK, but if the device already is awake (for other reasons) the Android "alarm handling" code might acquire a wake lock, *while it's delivering this alarm to the app* to avoid possible "race conditions" -- i.e. the device being awake, the system code deciding to deliver the alarm, then the device falling asleep in the middle of that.
---
Getting back to AquaMail -- I suppose there could be wake locks internal to Android implementation of some things.
One thing comes to mind is -- even though the app does not use "system settings -> accounts -> various "sync" things" to actually check mail, it does trigger a "sync" there (just so the "last sync time" there updates, for the user to see).
The sync operation (as far as "system settings -> accounts" goes) is "dummy", a "no-op", takes a few milliseconds, but I suppose Android could acquire a wake lock while processing it.