4 ms·

This is curious. I've recently migrated to Pixel 7 Pro with GrapheneOS and noticed that my battery was lasting for about 6 hours. And there was nothing unusual

This is curious. I've recently migrated to Pixel 7 Pro with GrapheneOS and noticed that my battery was lasting for about 6 hours. And there was nothing unusual in the battery usage report. Initially I thought that something is wrong with new Pixels or GrapheneOS. So, I've started reading ADB logs and assumed that something might be wrong with Meta apps - (which I installed in work profile). The logs were full of various messages and stacktraces from their background services. So, I put them (facebook, messenger, whatsapp) into "restricted battery" mode and disabled background data. That was enough to keep battery for 12 hours. I thought that it might be an issue with Graphene sandbox and bad Meta code, not a deliberately created "feature". In the end I've also restricted Telegram and now my battery lasts for 17 hours. So, I went to the extremes and now I do the same (restricted battery + disabled background data) for all the apps by default.

johnchristopher 4y ago
> In the end I've also restricted Telegram and now my battery lasts for 17 hours. Do notifications for messages still work in restricted mode (sorry if silly question) ?
- pshirshov 4y ago
  Yes. But there may be delays and sometimes when you tap on a notification nothing happens.
  - quyleanh 4y ago
    Yes? I just thought if I restrict it, there will be no notification until I open the app.
    - pshirshov 4y ago
      I did not restrict Play Services, so Firebase notifications definitely do work.
ThePowerOfFuet 4y ago
Facebook app installed on GrapheneOS... talk about an intense yin/yang.
- pshirshov 4y ago
  What's wrong? GrapheneOS is the perfect tool for that. They are installed into a work profile. Created specifically for all the untrusted shit around. Moreover, the networking in that profile is routed through a VPN.
  - politelemon 4y ago
    That makes perfect sense, sandboxing and isolation features were created to be able to run applications you don't want to trust.
izacus 4y ago
Reading ADB logs is useless for any kind of worthwhile analysis. Might as well fortune tell from coffee sediment. If you want to figure out what's going on with your battery, grab a bug report (adb bugreport command is one way). Then upload the resulting ZIP into battery historian - https://github.com/google/battery-historian https://github.com/google/battery-historian (there's a hosted version somehwere on the web is you're willing to trust it with your debug data). That will give you a usable graph of what's been keeping your phone awake, using radio and what the state of your signal quality was.
pokemapper 4y ago
To be fair I wouldn't be surprised if the cause of this is precisely the purity of GrapheneOS: given it lacks Google services and Firebase Cloud Messaging to centralize app notifications through Google, the apps need to do frequent polling or keep an active connection to Facebook's infra to receive notifications. Same with Telegram, each has a slightly different polling mechanism when Google-powered push is not available (a common in phones without Google services), which is most likely way less power efficient.
- pshirshov 4y ago
  It doesn't lack google services nor Firebase. They work as regular apps, sandboxed by selinux (I'm not sure what else is involved, but they are sandboxed and they work flawlessly).

johnchristopher 4y ago

> In the end I've also restricted Telegram and now my battery lasts for 17 hours. Do notifications for messages still work in restricted mode (sorry if silly question) ?

pshirshov 4y ago
Yes. But there may be delays and sometimes when you tap on a notification nothing happens.
- quyleanh 4y ago
  Yes? I just thought if I restrict it, there will be no notification until I open the app.
  - pshirshov 4y ago
    I did not restrict Play Services, so Firebase notifications definitely do work.

ThePowerOfFuet 4y ago

Facebook app installed on GrapheneOS... talk about an intense yin/yang.

pshirshov 4y ago
What's wrong? GrapheneOS is the perfect tool for that. They are installed into a work profile. Created specifically for all the untrusted shit around. Moreover, the networking in that profile is routed through a VPN.
- politelemon 4y ago
  That makes perfect sense, sandboxing and isolation features were created to be able to run applications you don't want to trust.

izacus 4y ago

Reading ADB logs is useless for any kind of worthwhile analysis. Might as well fortune tell from coffee sediment. If you want to figure out what's going on with your battery, grab a bug report (adb bugreport command is one way). Then upload the resulting ZIP into battery historian - https://github.com/google/battery-historian https://github.com/google/battery-historian (there's a hosted version somehwere on the web is you're willing to trust it with your debug data). That will give you a usable graph of what's been keeping your phone awake, using radio and what the state of your signal quality was.

pokemapper 4y ago

To be fair I wouldn't be surprised if the cause of this is precisely the purity of GrapheneOS: given it lacks Google services and Firebase Cloud Messaging to centralize app notifications through Google, the apps need to do frequent polling or keep an active connection to Facebook's infra to receive notifications. Same with Telegram, each has a slightly different polling mechanism when Google-powered push is not available (a common in phones without Google services), which is most likely way less power efficient.

pshirshov 4y ago
It doesn't lack google services nor Firebase. They work as regular apps, sandboxed by selinux (I'm not sure what else is involved, but they are sandboxed and they work flawlessly).