23
graphene os advice
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Feb 2024
23 points (92.6% liked)
Android
27939 readers
82 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:
founded 1 year ago
MODERATORS
I used GrapheneOS as a daily driver for about two months on my Pixel 7. I ended up having to switch back:
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.
Notifications just stopped working despite permissions being in place. Apps with all permissions just did not send notifications.
Apps that rely on background updates do not update unless manually opened.
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.
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.
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.
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).