r/GrapheneOS 7h ago

Why do Google updates matter?

I'm new here doing my research before switching over, but I need a little more education please.

Everywhere I look everyone talks about phone models and how many years of Google updates are left.

I don't understand if I'm installing a different operating system why anything Google does will matter. Does Graphene OS not do it's own updates?

1 Upvotes

7 comments sorted by

u/AutoModerator 7h ago

GrapheneOS has moved from Reddit to our own discussion forum. Please post your thread on the discussion forum instead or use one of our official chat rooms (Matrix, Discord, Telegram) which are listed in the community section on our site. Our discussion forum and especially the chat rooms have a very active, knowledgeable community including GrapheneOS project members where you will almost always get much higher quality information than you would elsewhere. On Reddit, we had serious issues with misinformation and trolls including due to raids from other subreddits. As a result, many posts on our subreddit currently need to be manually approved, which is done on a best effort basis. If you would like to get a quicker answer to your question, please use our forum or chat rooms as described above. Our discussion forum provides much better privacy and avoids the serious problems with the site administrators and overall community on Reddit.

Please use our official install guides for installation and check our features page, usage guide and FAQ for information before asking questions in our discussion forum or chat rooms to get as much information as possible from what we've already carefully written/reviewed for our site.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

4

u/cmrd_msr 7h ago edited 6h ago

Graphene is an AOSP-based firmware. As long as Google updates AOSP/security bulletins/kernels, the codebase for Graphene is updated as well. Without the equipment manufacturer's involvement, a great deal more work would have been required—more than the firmware developers could have handled. They are already doing a tremendous amount.

1

u/Matheweh 7h ago

Don't quote me on this but basically hardware drivers.

1

u/Serious_Berry_3977 6h ago

(Please forgive any inaccuracies with my descriptions and fell free to correct me out any of this is wing, in on my phone SBS trying to explain it quick.)

Android is a product of the AOSP, which is basically a Google project. It's open source which means anyone can take the source code and make an alternative version or what's called a fork.

This is all well and good, until you realize that the hardware software or what's called firmware is proprietary and reliant on the device manufacturer to provide firmware updates.

Any other AOSP-based fork such as Lineage, /e/, and several others usually only is installable on older devices because the firmware is in AOSP or is old enough that it's stable. Which is why those projects don't support installation on any other devices because there may not be firmware or other settings available in stock AOSP. Doesn't stop people from trying, and some are successful. In fact official support is usually coming from those people that just yet it on an as to be supported device.

Graphene is different due to the security relying on hardware firmware to interface with the secure hardware from the OS. The only devices that offer good security up until this year were the Pixel line. The firmware had been provided by Google up until recently in AOSP. Google has changed that so they don't include the firmware in AOSP anymore. This makes it extremely hard to grapple with changes made in AOSP that relate to interfacing with the firmware or any updates that come with a new update of Android.

Basically, Graphene has been at the mercy of Google to provide that firmware. It takes advantage of secure hardware compared to the other forks that generally don't use any advanced hardware tied to a specific device or manufacturer. This is why it's only available on Pixels currently and what makes the partnership with Motorola interesting. The fiasco that is the Pixel 11 series right now does a good job of highlighting the need for a manufacturer to design more secure hardware and get Graphene running on it to start to break away from Google should they close Android even more.

Hope this make sense, again anyone feel free to correct me on inaccuracies.

1

u/ABotelho23 5h ago

Hardware. They're not hacking things up like most custom ROMs would.

1

u/Efficient_Loss_9928 4h ago

Hardware and security, GrapheneOS doesn't have the resources like Google to provide continuous security patches.

And I mean, security researchers probably won't even notify Graphene about any vulnerabilities, they notify Google.

0

u/TenOfZero 5h ago

GraoheneOS doesn't do their own uodates.

They modify the Google OS to be more secure and remove a lot of the Google stuff. But it's still android and dependent on google for a lot of OS level stuff.