zlacker

[parent] [thread] 2 comments
1. hedora+(OP)[view] [source] 2025-04-13 15:01:09
Thanks for doing that. I tried GrapheneOS a few years ago in the states, and the bank thing wasn’t a huge problem (just carry rfid cards because there’s no google pay/apple pay).

The bigger problem came from apps that threw null point exceptions on startup when probing for google play crap.

The following failed for at least one week over a two month period: parkmobile, multiple ev charging networks, uber, lyft, yelp.

Is this still an issue, or are things more reliable these days? (Ignoring the Google integrity stuff.)

I noticed that GrapheneOS got more than 2x Google’s advertised battery life until I installed Google Play Services in a sandbox. Then it dropped to advertised. You might want to add that to your complaint. Halving everyone’s battery life is easily quantified economic damage. (Privacy is more important than bundling $50 of battery, then wasting it, but easier for Google to wave away with big words and doublespeak.)

replies(2): >>hellco+Bf >>strcat+tM1
2. hellco+Bf[view] [source] 2025-04-13 17:12:31
>>hedora+(OP)
The app crashes I found were always due to the additional security hardening features in GrapheneOS. You can toggle these individually for each app.
3. strcat+tM1[view] [source] 2025-04-14 11:28:00
>>hedora+(OP)
> The bigger problem came from apps that threw null point exceptions on startup when probing for google play crap. > > The following failed for at least one week over a two month period: parkmobile, multiple ev charging networks, uber, lyft, yelp. > > Is this still an issue, or are things more reliable these days? (Ignoring the Google integrity stuff.)

These apps have worked reliability since our sandboxed Google Play compatibility layer added support for them in 2021. There wasn't a time period where these apps weren't compatible with GrapheneOS after they initially became supported. That was a problem with your setup, but there's no way to figure out what was wrong at this point. Updating sandboxed Google Play without keeping the OS updated is not supported. If you fell significantly behind on updates but were still getting sandboxed Google Play updates, that would explain why things broke. We sometimes gate those updates. We do keep things working for legacy extended support devices, but whether people are on a fully supported device or a legacy one they're expected to keep the OS updated. We don't keep compatibility with old OS versions indefinitely. Disabling the Network permission for sandboxed Google Play services or sandboxed Google Play Store is another possible cause. Regardless of the cause, that's not at all normal and doesn't reflect a typical experience.

> I noticed that GrapheneOS got more than 2x Google’s advertised battery life until I installed Google Play Services in a sandbox.

GrapheneOS will still tend to get better battery life with the same apps installed by the user unless you install a bunch of other Google apps to match the stock Pixel OS out-of-the-box experience. It's easy to make battery life worse by having multiple push messaging systems running at the same time though. Installing sandboxed Google Play in 2 separate profiles you always keep active could easily have worse battery life than the stock Pixel OS since it's 2 whole separate isolated instances of it vs. the stock Pixel OS having them built into the OS as highly privileged cross-profile system services.

[go to top]