Hello everyone, so I'm quite new to GrapheneOS on my Pixel 8a and my main goal is to set up my phone to last as long as possible. So I've been trying to deactivate the background options for the apps that I don't need to be running in the background (no notification or cloud syncing) whenever I can.

I've noticed that the google camera app (that I use instead of the GOS camera) continue running in the background after I stop using it and that for several minutes. Drowning the battery percentage quite a lot some times.
In the app settings I disable background usage for network and battery but it still running in background sometimes.

So I was wondering if there was a known cause for this comportment and if there was any options to avoid it?
Also if you have any advices on how to properly setup my device to preserve battery life and usage, it would be very appreciated!

Thanks a lot!

22 days later

Just noticed this aswell, may be important to note that I have google cam disconnected from network aswell, but I still find it using a significant amount of battery in the background. It does at least seem like the camera itself isnt being used according to the system battery usage though.

  • de0u replied to this.

    Reproach3656 I wonder if perhaps it is working away trying to download plugins, so banning it from doing that makes it try harder? Since the network permission is a GrapheneOS special, apps aren't coded for permanent network denial, so it would be natural for them to try repeatedly.

        de0u We do mostly pretend that the network is down when Network is disabled for improved compatibility including not running network-dependent JobScheduler jobs, showing it's down for queries via the high-level APIs, etc. Apps could see it's not down via lower-level APIs but don't use them in practice. We're not trying to entirely hide it, just avoiding compatibility issues.

        • de0u replied to this.

            GrapheneOS We do mostly pretend that the network is down when Network is disabled for improved compatibility including not running network-dependent JobScheduler jobs, showing it's down for queries via the high-level APIs, etc.

            That makes sense. Thanks for the clarification!