GrapheneOS currently doesn't ship Play Store or Services OOTB. They install as normal apps (albeit with GrapheneOS providing support code to make the fact that these things use/expose custom privileged APIs work correctly). I don't know if the Google TOS would prohibit that, at least I am not aware of any enforcement action against GrapheneOS in this regard. GrapheneOS also doesn't have Google's blessing, meaning some apps like Google Pay won't work on it. To get this, you need to apply to be an OEM.

Really Motorola doesn't need to sell a GOS phone. Motorola just need to sell a phone with the right hardware security features, open source/upstream their Android/Linux patches, and give users the ability to run GOS.

Hopefully they can then give you the option to buy one with GOS preinstalled, but even if they don't. It will be sufficient that it can run GOS.

Unlike Windows, nobody feels they're paying an inherent tax when buying a stock Android phone. I'm sure nobody will mind.

The hard part will be actually supporting the phone for long enough.

GOS is reliant on Google's open sourced Pixel android releases up to and including the 9 series. This is because GOS doesn't have the resources to handle that entire side of things. But I guess part of that is also that GOS doesn't have access to the necessary information to do that stuff properly either.

I 100% agree. It should have just happened 12 or 24 months ago. It's not too late, and there is a chance to capture some market, but it is late. If Motorola did this last year, I think they could have captured 10-20% market share. Their share will be reduced because the people who did care for long term updates have upgraded. Now they get 4+ years of updates because of Android. https://security.samsungmobile.com/workScope.smsb

This is a power move on Motorola's side, and I'm here for it.

There are conditions for OEM's installing any of the Google services. Although, so far it seems that graphene have been able to work around them (although, this is not a world I traverse).

I don't think the standard Android user wants to install ReVanced. They don't care about custom OS's. They want support and updates.

I remember the dark times where you purchased hardware, and you would be lucky to get 4 years of updates.

Motorola/Lenovo are late to this game. Two years ago, people updated to phones with phones that would get monthly security updates for five years. This was new to the Android ecosystem two years ago (with the exception of maybe a few Pixel phones).

I looked into this and it seems like Motorola is coming up with a contrived interpretation of the ecodesign regulation (EU reg. 2023/1670, annex II, "Design for reliability").

Specifically they seem to be interpreting this to mean that they only need to make the update available (i.e. downloadable) for 5 years iff they release an update.

> (a) from the date of end of placement on the market to at least 5 years after that date, manufacturers, importers or authorised representatives shall, if they provide security updates, corrective updates or functionality updates to an operating system, make such updates available at no cost for all units of a product model with the same operating system;

However recital 7 makes the intent crystal clear:

> It is currently not possible, or extremely difficult, for the owners of mobile phones, including smartphones, and tablets to change the operating system of their device, which is chosen and maintained by the manufacturer through regular updates. Such updates generally lead to the establishment of a range of major and minor versions. Updates may be used to ensure the continued security of a device, to correct errors in the operating system or to offer new functionalities to users. They may be offered voluntarily or might be required to be offered by Union law.

> In order to improve the reliability of devices, therefore, it needs to be ensured that users keep receiving such updates for a minimum period of time and at no cost, including for a period after the manufacturer stops selling the relevant product model. Such updates should be offered either as updates to the latest available operating system version that has to be installable on the device, or as updates to the operating system version that was installed on the product model at the moment of the end of placement on the market, or subsequent versions.

They're not getting any points for this, it's anti-consumer and makes a mockery of the law, but I don't think it's an actual loophole and they'll be punished for it if they don't comply.

However all other OEMs are acting equally poorly in other areas so this really shouldn't be the reason for anyone to pass on GOS-powered Motorola devices, especially since this is the one area that's ~guaranteed to be completely different in partnership with GrapheneOS.