Conversation

Replying to @DanielMicay and @iNPUTmice

My Auditor app ends up in the Rare bucket since it's not meant to be regularly interacted with at all. I can't see any way to do what is required to keep reliably sending remote attestations on a schedule without resorting to an awful mess of alarms with a battery opt exception.

It currently ends up not sending the attestations on the expected schedule and then the alerts will probably be triggered. For now, I should probably just set the minimum alert delay to a value like 48 hours so people stop getting unnecessarily spammed with the alert emails.

It's really hard to understand why it's no longer possible to upload 300 bytes every 4-6 hours with JobScheduler. I can definitely work around it by hacking together something uglier, but it's going to waste more power / resources than the desired JobScheduler implementation...

It's backwards that power optimizations force doing things much less efficiently. When the Auditor app is used for scheduled remote attestation, users have no reason to interact with it, so it ends up in the Rare bucket developer.android.com/about/versions resulting in 24h+ delays right now.