U
upstage4186

  • 8 days ago
  • Joined Mar 16, 2024
  • Everything is working well on my Pixel 8, including WiFi, Bluetooth audio, hotspot, private space, multiple users, etc.

    Thanks for the super quick updates!

  • Hi!

    I was wondering if there's a way to speed up app updates, especially via Google Play (running in a work profile).

    Apps generally take longer to update than other phones/ROMs I've used, but there are certain apps that take a VERY long time, e.g. Revolut (banking app) is currently updating and has so far taken 45 mins and counting.

    It's not the end of the world that updating can take hour(s), but during the installs I obviously can't use the apps, which is a pain with Revolut, as I use it for my daily spending/banking.

    It's at the stage where I purposely delay large batches of updates because I don't want to lose access to those apps, sacrifice the higher battery drain, and keeping the work profile unlocked for so long (I keep crappy apps in there locked away).

    Is there any way to alleviate this maybe?

    Thanks.

    • Working great on my Pixel 8 so far. Amazing work as always!

      Will report back if I experience any hickups.

    • This is amazing from GrapheneOS.

      Is there any way for me to directly support the legal action against Google?

      • GrapheneOS Firefox doesn't have complete site isolation in any form, whether or not Flatpak is involved. It's also a weaker sandbox. Flatpak weakens it further. You're mixing up several different things.

        Would you mind elaborating on this further please?

        I thought that there was indeed site isolation on the desktop version of Firefox (or Mullvad Browser, which is what I use), and that this only applied to the mobile version? I know that there's a fixed number of site processes and that two sites can potentially share the same sandbox, is this what you're referring to with "weaker sandbox"?

        How does Flatpak weaken security further? Do you mean the lack of nested user namespaces in the bubblewrap sandbox? If so, does this have a major impact?

        Thanks!

        • Pixel 8, 2024060500 -> 2024061400

          iFi Audio xDSD headphone DAC, and Sony WH-1000XM4 headphones both connected and playing audio fine. 👍

          The "Done" button on the Bluetooth quick tile pop-up is square, vs other buttons which are rounded though, minor inconsistency.

          • Wow. Thank you so much for all of the amazing work that goes into this project, seriously!

            Not just on the technical side, but the clear and concise communication of best practices, exploit updates, changelogs, community involvement, etc.

            I'm constantly blown away by the holistic approach you take and how well its all communicated. I don't know of many projects that are as consistent, and of high quality as GrapheneOS in this department.

            I need to get around to setting up Monero so I can begin donating.👌

          • I'm also experiencing this since the latest update. I have only one fingerprint registered.

            Swiping down or back (using gesture navigation) removes the PIN unlock and reveals the fingerprint reader.

          • After updating to this build, I'm getting a bug where the PIN number pad shows above the fingerprint unlock when switching user profiles.

            Pressing the back button closes the PIN entry screen and the fingerprint unlock is then shown.

            Doesn't seem to occur when unlocking the phone from screen off.

            Not a major problem but a little annoying.

            • It seems that indeed, the problem was caused by MTE.

              I had MTE crashes with Spotify before they fixed it, and when those occurred, I had a system pop-up notification reporting the error.

              I wasn't getting those notifications with the WhatsApp crashes, so I assumed it wasn't MTE related.

              I'm no longer able to reproduce the crashes with MTE protection disabled, but I'll report back if the problem does occur again.

              I have a Pixel 8 btw.

            • Hi!

              According to a user report here, WhatsApp should work fine with native code debugging disabled, but if I disable it then I get crashes when opening the app after it's been inactive for a minute or two, then clicking on a chat.

              No errors are reported, the app just quits out.

              Enabling native code debugging for just WhatsAapp seems to have fixed this and I'm no longer seeing crashes (...so far).

              Is anyone else getting the same problem, or is something broken with my setup maybe?

              I'm using the APK from www.whatsapp.com/android, installed to the main owner profile, with no Google play installed. The same problem occurs when installing from Aurora.

              Thanks.

              • Seems like it works fine, assuming these apps are indeed using Google's push notifications and not some other method, e.g. polling (I don't know how to confirm this).

              • Hi!

                I've just installed GrapheneOS and am loving it so far. I have a question regarding the sandboxed Google services though...

                I've installed some apps into a work profile that rely on Google push notifications, I've also installed the sandboxed Google Play apps, however, I haven't logged in.

                My question is, do I need an active Google account to register push notifications? Or will apps receive notifications without this?

                I don't really want to create a Google account and give them my phone number just to get notifications.

                Thanks.