Honestly this is one of the only things holding me back from going to graphene. Once this is available to non alpha users I might make the switch properly.
To me it is super weird that GrapheneOS positions itself as a way to degoogle - but it is only supported on google’s Pixel hardware.
Pixel hardware is some of the easiest to get/best/cost effective with an unlocked bootloader.
Too bad the only affordable ones are those that have little to no support left.
Why would anyone care about official support? That’s not why you buy a pixel
I meant support from Graphene itself.
is it that bad? I though Graphene supports all Pixels well
The following devices are end-of-life, no longer receive firmware or most driver security updates and receive extended support from GrapheneOS as part of the main releases with all GrapheneOS changes including all of the latest Android Open Source Project changes:
Pixel 5 (redfin) Pixel 4a (5G) (bramble)well, I see. thankfully there’s loads and loads and loads of alternatives over on XDA still in development
I’m betting it’s because Pixels have some unique hardware/ software quirks or something.
iirc they are the only phones that allow adding custom avb keys and then relocking the bootloader
I think because on other manufacturer android phones, like Samsung, you’d have to de-Google and also de-Samsung.
I’m still iffy about grapheneos after the rossman issue. Any other good alternatives?
I generally like Louis Rossmann, but his arguments in the GrapheneOS video were beyond stupid. He says that he can’t trust GrapheneOS because it’s developed by Daniel Micay. I guess he doesn’t understand that GrapheneOS is open source and anyone can see the code. Then he switched back to the proprietary Google ROM. So he’s trusting proprietary software that’s filled with spyware over privacy-respecting open source software that can be audited by anyone.
You don’t seem to understand the situation either and you blindly follow some YouTuber. I’d advise you to overthink your opinion on this topic.
iirc that developer doesn’t work on grapheneos anymore
oh wow! i doubt im going to use that feature because android auto is insufferable but that’s still really neat!
I am curious why you think that? My reasons for liking it are the fact that it essentially just works, and gives me a consistent UI across multiple vehicles. What are your issues with it?
I’m just fundamentally against those tablets in cars. I’ve never seen a single good implementation of it. This first question I always have is… what can this do that my phone cant do easier, faster, and better? And 100% of the time I’ve had to ask this it has been nothing. I just use a phone grip on either my dashboard or my windshield and that accomplishes the same thing without having to use the massive, clunky, and usually dysfunctional tablet stuck on my console. Another enormous complaint is that most cars that work like this also remove aux/tape/cd and then BURY the bluetooth audio option underneath a bunch of finnicky android auto shit that has so many different problems all of which wouldn’t exist in the first place if i could just set my phone in a clamp and plugged in the aux cable. The only benefit android consoles have i can tell it has is being big if you have bad eyesight.
Is it easy to install graphenos on iOS? I got an iPhone 14. Does anyone have a good recommendation to help me through the process?
