▲ | abustamam 7 days ago | ||||||||||||||||
It may be a bit pedantic but Pixel is made by Google. I know you de-Googlefied it by using Graphene but it's still running on Google hardware. I wonder if there are any viable alternatives though. | |||||||||||||||||
▲ | sfRattan 7 days ago | parent | next [-] | ||||||||||||||||
I assume GP comment is referring to their software, especially cloud-deployed software, which can change under your feet like quicksand. Hardware, once assembled and in your hands, is yours to a higher degree than that. Eventually each Pixel phone will stop getting firmware updates, but Google has guaranteed 7 years of updates for the newest models. For the future, Graphene OS devs have stated publicly that they're working with an unnamed hardware vendor to develop a phone that will meet their list of hardware requirements. Currently only the Pixel line does. From what I understand, a few Samsung phones come close, but don't support bootloader re-locking... When you unlock Samsung bootloaders it burns out a fuse on the board which in turn completely disables Knox, their architecture for a trusted execution environment. | |||||||||||||||||
| |||||||||||||||||
▲ | drnick1 7 days ago | parent | prev [-] | ||||||||||||||||
You could use a Linux phone, but that would almost certainly mean worse hardware and/or worse compatibility with Android programs (emulator). But for all intents and purposes, when running Graphene Google has no power over you and can't enforce arbitrary bans on sideloading, call recording, etc. |