← Back to index
References / filed

USE_EXACT_ALARM

Same precise scheduling power as the alarm permission but reserved for eligible system-adjacent apps, which a sideloaded app cannot be.

222 words2 min read
Filed under
#android#permissions#reference

Granted automatically at install, with no prompt, which sounds like an advantage until you look at who is eligible. USE_EXACT_ALARM is reserved for apps in specific categories, essentially calendar and alarm-clock applications, and Google tightened it on Android 13.

A sideloaded fake traffic-challan app is not in any of those categories, so it cannot actually hold this permission. That is the same pattern as AUTHENTICATE_ACCOUNTS: the manifest asks for a capability the payload has no path to use.

It is also declared immediately next to SCHEDULE_EXACT_ALARM, and the pairing is revealing. One is the unconditional version, gated on app category; the other is the version any app can obtain by asking the user in a Settings screen. A kit that wants exact-timing persistence should take the second. Declaring both suggests a template written to request the strongest form available and let the OS sort it out.

Read that way, this entry is a marker for how the manifest was assembled rather than a capability in use. The scheduling the payload actually depends on is the polling worker cadence, which the Settings-toggle permission can support.

Related: SCHEDULE_EXACT_ALARM

Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.