B
balance3767

  • Joined Mar 10, 2024
  • In Results of a 2-month-long SOT tracking comparison between stock vs. Graphene

    GrapheneOS Google Play services uses a significant amount of resources and running 2 instances of it will reduce battery life significantly compared to running 1 instance. GrapheneOS out-of-the-box will have much better battery life and it should still be better if you're comparing a single instance of sandboxed Google Play to the stock OS. This fully explains why you have lower battery life.

    This does not explain the lower battery life if he also used the work profile on stock OS, because he would also have 2 running instances of Google Play Services.

      • In Request for testing and feedback with Bluetooth on Android 14 QPR2 GrapheneOS

        Build: 2024031400
        Pixel 6
        Galaxy Watch5

        Hardened memory allocator for Bluetooth disabled with phone rebooted afterwards and the watch factory reset.
        The issue persists without any noticeable difference. After disconnecting the watch it jumps between 'saved devices' and 'connected devices' exactly like before installing this build.

      • In Request for testing and feedback with Bluetooth on Android 14 QPR2 GrapheneOS

        other8026 , it appears the issue might be affecting people with the Stock OS too if they've updated to a post QPR2 release.

        This is not true. I have confirmed that the issue with Samsung watches does not occur on the QPR2 stock OS. While you are correct that the Samsung Wearable app is really buggy, it does work on stock OS.

        On GrapheneOS, the watch can only be connected to the phone during pairing (either directly in system settings or with the Samsung app). After disconnecting the watch, it cannot be connected again without removing it from saved Bluetooth devices first. The phone constantly tries to connect to the watch, as can be seen by the Galaxy Watch constantly jumping between the 'connected devices' and 'saved devices' sections in Bluetooth settings.
        This strange behavior is exclusive to GrapheneOS and has been reported by a few other people here.

        • In Request for testing and feedback with Bluetooth on Android 14 QPR2 GrapheneOS

          topro It happens that I was able to do a test with another Pixel8Pro which is on latest stock rom (2024-03-05) and on this one connect works flawlessly, so I assume it is a grapheneos specific issue.

          Well, so now we have at least one evidence of something working with QPR2 stock OS and not working with QPR2 GrapheneOS.
          Can anyone confirm this phenomenon with any other device?

            • In Request for testing and feedback with Bluetooth on Android 14 QPR2 GrapheneOS

              p0well34
              I can confirm that the exact same thing is happening with Galaxy Watch 5 and Pixel 6 after QPR2 update.
              2024030900 release has not fixed the issue.