this post was submitted on 27 Nov 2024
286 points (98.3% liked)
DeGoogle Yourself
8984 readers
2 users here now
A community for those that would like to get away from Google.
Here you may post anything related to DeGoogling, why we should do it or good software alternatives!
Rules
-
Be respectful even in disagreement
-
No advertising unless it is very relevent and justified. Do not do this excessively.
-
No low value posts / memes. We or you need to learn, or discuss something.
Related communities
!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.