As far as I understand, most OEMs are not allowed to release QPR1 or QPR3 either (not that OEMs outside maybe Samsung would be able to). So part of it also reeks of giving Pixel benefits over phones of other manufacturers.

▲

dathinab 4 hours ago | parent | next [-]

the more I learn about how Google handles releases the more this looks like there being a need for anti trust actions

▲

izacus 3 hours ago | parent | prev [-]

> As far as I understand, most OEMs are not allowed to release QPR1 or QPR3 either (not that OEMs outside maybe Samsung would be able to).

This is not true at all though. OEMs can release anything whenever they want.

▲

microtonal 2 hours ago | parent | next [-]

I have read in multiple sources that OEMs cannot roll out QPR1/3. E.g. see this thread:

https://grapheneos.social/@GrapheneOS/117282080803799576

Since they are working with two OEMs (one for GrapheneOS support and one for getting embargoed security patches), I think they know what they are taking about.

	▲	izacus 5 minutes ago \| parent [-]
		Nothing of that has to do with OEMs being forbidden from shipping QPRs though. Graphene isn't OEM so they don't get access to Android repository before AOSP drops. OEMs - like Motorola for example - do have access to partner repository and can ship QPRs if they wish to do so. Most often OEMs do not want to push updates (and it took years to make them push regular major Android updates). > I think they know what they are taking about. Err, if you look at that account you'll find that the person running it has a penchant for overexaggeration and selective truth telling when they feel aggrieved.

▲

LoganDark 3 hours ago | parent | prev [-]

Except for phones preinstalled with GrapheneOS (unless you are Samsung)