SCHEDULE_EXACT_ALARM
Fires scheduled code at precise times, behind a Settings toggle rather than a prompt, which is what makes the polling cadence reliable.
On Android 12 and later this is not a runtime prompt either. SCHEDULE_EXACT_ALARM requires the user to allow exact alarms in a Settings screen, so like REQUEST_IGNORE_BATTERY_OPTIMIZATIONS it is granted through a path that a quick permission review will miss.
What it buys is timing precision. An app holding it can schedule work that fires at an exact moment rather than being batched into a maintenance window, which is what makes a polling cadence reliable. SmsPollingWorker sweeping the inbox, SimInfoRefreshWorker re-checking the SIM, and the call-log worker chain all depend on running when they are supposed to rather than whenever the OS gets around to it.
The system-alarm sibling USE_EXACT_ALARM grants the same power with no Settings toggle at all, but only to apps in the eligible categories, which a sideloaded traffic-challan app is not. Declaring both is therefore partly aspirational: the kit asks for the unconditional version and falls back to the one it could plausibly obtain.
Together with RECEIVE_BOOT_COMPLETED this is the second pillar of persistence. The alarm re-arms the implant on a schedule, the boot receiver re-arms it after a restart, and together they mean the victim never has to open the app for it to run again.
Related: USE_EXACT_ALARM, RECEIVE_BOOT_COMPLETED
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.