23
graphene os advice (lemmy.world)

so I've got a pixel 6A and I really like the device itself, but the last several months of updates have just screwed it up over and over again.

first I lost my fingerprint sensor and it still hasn't been fixed with any of the updates. now with one of the more recent beta updates I have seen intermittent cell service issues in areas where I never used to have service issues.

I've been considering switching over to graphene for a while now but wanted some feedback on how that works when I'm not really trying to disconnect from the rest of Google services.

I use family link for my kids tablets, I use Google pay I use Gmail etc.

Will I have any issues if I switch using the same Google services?

also I use Nova launcher, and it would be convenient if I could save that profile and import it, assuming Nova works just fine on graphene as well?

top 12 comments
sorted by: hot top controversial new old
[-] Mahonia@lemmy.world 8 points 8 months ago

I've been using GrapheneOS for about 5 years.

Google pay won't work, but everything else should. I've never experienced any of the issues the other commenter had, and I've installed Graphene on 4 devices (not dismissing you BTW, just saying I think your experience is quite uncommon).

I don't think third-party launchers are a good idea (you're giving full device permission to an unneeded app) but it should work.

Almost every app I wanted to use worked with Graphene before they introduced their sandboxed google services, and now everything I've tested works with Google push notifications. The only exception is Google pay, and there are upstream reasons for that. Keep in mind, on a very rare occasion the hardened memory allocator breaks compatibility (again this is very rare), but there is an app-specific setting toggle to turn this off so it's kind of a non-issue.

[-] pinpin@sh.itjust.works 7 points 8 months ago

Google Pay and RCS don't work. Third party launchers shouldn't be an issue if you don't give them network access. That's how I use Nova.

[-] OmnislashIsACloudApp@lemmy.world 2 points 8 months ago

ah dang I do use rcs, that would be annoying

[-] seang96@spgrn.com 2 points 8 months ago

RCS not working is new, people are saying a magical module fixes it and pay though.

[-] lemmyfanadmin@daring.lemmy.fan 5 points 8 months ago

I used GrapheneOS as a daily driver for about two months on my Pixel 7. I ended up having to switch back:

  1. RCS messaging just doesn't work. No matter what I tried, RCS would never connect so all texts were being sent OTA in the clear - not great when using a security-focused OS.

  2. Notifications just stopped working despite permissions being in place. Apps with all permissions just did not send notifications.

  3. Apps that rely on background updates do not update unless manually opened.

  4. Calls went straight to voicemail after my first web-based USB install - I reflashed GrapheneOS and the issue went away for a little while, then returned.

  5. Less control over my phone's settings than I have in stock Android.

It's a good idea and I wanted it to work, but it's still just not stable nor ready for daily use.

[-] dataprolet@lemmy.dbzer0.com 4 points 8 months ago
  1. This could be due to missing Google services?

I wouldn't say that GrapheneOS isn't ready for daily use just because you have some issues. It's a mature project with decent support for only a couple of devices and a lot of people use it on a daily basis without issues.

[-] LibreFish@lemmy.world 2 points 8 months ago* (last edited 8 months ago)

On notifications if Google play services is not installed unless the app let's you configure another server to use in place notifications won't work that use Google Play services installed on the back end.

If sandboxed Google play services is installed, assure it has the neccisiary permission to run in the background (unrestricted battery and network) access. Not just the individual apps, but the google apps specifically as Graphene installs thegoogle stuff with standard permissions.

Same goes for apps that run in the background. If you expect them to be running in the background to auto update or perform another function then it needs to be permitted in the battery settings. Background updates may also rely on Google Play services.

Edit: to clarify I haven't experienced any issues myself that weren't directly related to my decision to not use sandboxes google play services (no push notifications) despite daily driving for years. It's a particularly old and reliable project in the privacy space, and while I'm sorry you experienced issues that doesn't make it an unstable project not ready as a daily driver (any more that somebody having issues with Windows/Linux makes those unstable and not ready to be daily driven).

[-] Atemu@lemmy.ml 3 points 8 months ago

If your issue with fingerprint stopping to work is anything like the issue I experienced in home-brewed LineageOS on my Fairphone 4, the only solution is to wipe userdata.

[-] OmnislashIsACloudApp@lemmy.world 1 points 8 months ago

yeah I suppose it's time to try a reset

[-] dataprolet@lemmy.dbzer0.com 2 points 8 months ago

Don't use the Beta channel and expect everything to work.

I don't use Google at all but theoretically everything should work with the sandboxed Google services.

And I did use Nova Launcher and it's working without an issue. Importing a profile should also work.

[-] OmnislashIsACloudApp@lemmy.world 2 points 8 months ago* (last edited 8 months ago)

I actually switched to beta hoping it would fix the broken biometrics update, was using standard release before that.

[-] Pantherina@feddit.de -2 points 8 months ago* (last edited 8 months ago)

First, discuss.grapheneos.org

If you have bugs, github.com/grapheneos/os-issue-tracker/issues

first I lost my fingerprint sensor

Same device, no problems, likely hardware problem

now with one of the more recent beta updates

have just screwed it up over and over again.

You may want to use the stable channel.

intermittent cell service issues in areas where I never used to have service issues.

Likely LTE-only mode, network settings. Keep it on if you care about using something without known security flaws.

I've been considering switching over to graphene for a while now

How can you consider it and at the same time use it?

Please just use their website, it should cover what is working and what is not using their sandboxed play compatibility layer.

Gmail works, avoid using their app, and just switch to a better provider. Privacyguides.org

That family link stuff idk, if it is invasive like parental controls it will not work.

but wanted some feedback on how that works when I'm not really trying to disconnect from the rest of Google services.

The OS makes no connections to google. Sandboxed play uses the same google code but as a sandboxed app. This will not give google any sensitive data or control over the device. Read and understand this thread

Will I have any issues if I switch using the same Google services?

Check gmscompat compatibility. Search for every thing you use in their forum or matrix (server: grapheneos.org), if you dont find it ask in the forum.

assuming Nova works just fine on graphene as well?

Yes it does. For paid apps you need sandboxed google play, have not tested that. Aurorastore (use session installer, dont grant file storage permission) doesnt require google login and services but may break in the future and is less secure.

this post was submitted on 28 Feb 2024
23 points (92.6% liked)

Android

27933 readers
91 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

!android@lemmy.ml


founded 1 year ago
MODERATORS