As the title says, I want to finally degoogle (completely) my life. I've found a Pixel 7 8/128 for ~270€ (or pixel 8? ~470€ but no white :c) it's refurbished so google doesn't get a shit from me.
I'm curious to know if:
- You can change the default icons color (black and gray-ish in the image) or is based on the wallpaper
- The camera app is good. Not going to make professional pics or videos but I still want to use it to take pics and a good quality is important. Tried their camera on a phone and the bottom menu to switch mode (picture/video/night mode/etc) was buggy
- Battery life is better/worse than stock Android (if anyone tried that)
- How the sandboxed play services work
- Anything else that I should know about. Some people say it's good, some it's bad so I'm curious to know.
I'm still looking for a good maps replacement, Organic Map is not the best because it's missing a lot of places where I live. I wish there was a google wallet Foss alternative... I needed it to use my card with the phone (rare but still possible!)
Help a new user to fully leave shitty phone companies
~~Edit: Does it have some kind of cross profile notifications? Can I see notifications of another profile on the main?~~
GrapheneOS supports forwarding notifications from users running in the background to the currently active user. Forwarding notifications to other users is disabled by default and can be enabled within each user profile where forwarding to the active profile is wanted. Notifications forwarded from other profiles are displayed by default in a standard local notification channel.
It does
I have tried on several occasions to like GrapheneOS. But every time I install it on my Pixel 7, basic functionality breaks. Things like receiving regular phone calls, as in people calling my number using a normal phone. GrapheneOS will sometimes not even ring and immediately display a notification saying "Missed call". If my phone cannot be used as a .. phone, what good is is?
Hell my android does that
Ditto. Deeply frustrating.
I never had that problem when i had my Pixel 7 before the fucking screen died and google didn't honor the warranty.
Is it a problem with you only or is it a problem others have too?
I've had 2 phones with GrapheneOS and never heard of those issues before.
So it's not a known problem (?). Good to know
Generally with android custom ROMs including GrapheneOS, you will need to make sure your cell service and data is working properly on stock android first. Things like VoLTE provisioning need to be done on stock OS for some reason.
Basically if everything with cellular talk / text / data works on stock, it's probably good to go for upgrading to custom ROMs. VoLTE provisioning can be checked with a secret dialpad code I don't remember at the moment.
So I have to use my Sim to see if everything works? 🤔 we'll see about it, nees to pick a phone first
It does make sense to setup the carrier first on stock Android to prevent GrapheneOS security from causing headaches.
But I have setup my phone service after installing GrapheneOS.
I just had to be aware of all the necessary permissions my phone carrier's app needed, and grant them all.
Basically, I granted it all the available permissions, to get through my phone carrier setup. Then I let GrapheneOS' automatic removal of unused permissions take all the permissions back. (And it removed basically all the permissions. It seems like my carrier's app does extremely little or nothing, after initial setup, unless I open it to check my billing information.)
Edit: I also have not see the rejected call situation, except maybe once on a weird public wifi network. I think I recall I forced my wifi list to forget and never reuse that wifi, to correct/prevent the issue.
I've been using GrapheneOS on my phones since the Pixel 3 and I have not had this issue when using Verizon. For the other person maybe it was a different carrier? Or some issue a while ago with that carrier and GrapheneOS.
I don't know. I'm trying to see all possible problems with GOS before buying. Doesn't mean I'll get any of these problems but better know than don't know
That's just "regular" Android behaviour