With how terrible my P7P update experience has been (literally every update has made the phone buggier and more unstable) I’m no longer sure if this is a good thing or not. Maybe if they fix their insane QA issues.
@gvasco @IdleSheep recently it’s even slightly buggy too, but it’s still orders of magnitude lower than stock.
I got my phone through my carrier. Unbeknownst to me at the time, carrier provided phones have locked bootloaders so you can’t install grapheneOS on them, or if you can, I haven’t found a guide to reliably do so. The phone was $800 off through the carrier so I can’t complain too much, but I would have got it straight from Google if I had known prior to buying that you can’t install grapheneOS on it.
All modern phones come with a locked bootloader. This is to protect the OS and the User data, preventing anyone with physical access to the devixe from reseting the device and installing their own software without permissikn. I had to unlock mine on my 1+ 7P before installing /e/OS. It might just be that carrier locked phones might need something extra to unlock them not sure.
I’m switching phones instead, but even if I wasn’t I don’t want to risk bricking my phone or playing the cat and mouse game with banking apps.
Either way I’m never touching a pixel again until they fix their buggy software.
There’s almost no risk, you can install it from the browser, the bootloader gets relocked so no issues with banking apps and rooted device, and you can still have play services on the phone but without it being able to access the whole storage and device info. You seem to literally just be spewing words without knowing anything about the subject.
If you don’t want it I’d be willing to take it and experiment myself with graphene OS.
