> That's already happening today.

That's not a hard fork. They always rebase on top of AOSP when there's a new AOSP source release

There is no reason to hard fork, as long as Google contributes to AOSP without breaking it.

Regulators in the US decided that Android did not have to be split from Google, but they could theoretically decide that Google is not allowed to break AOSP to gain a competitive advantage. Not that it would matter: TooBigTech is too powerful to care about regulations anyway.

▲

charcircuit 3 hours ago | parent | prev | next [-]

It doesn't have to be. Most of Android is fine.

▲

realusername 3 hours ago | parent | prev [-]

Nobody really want a hard fork, if you can't run Android apps, you might as well use a Linux distribution.

▲

palata 3 hours ago | parent [-]

Well the idea would be to run Android apps on the hard fork :-).

	▲	realusername 3 hours ago \| parent [-]
		If you can run Android apps then you need the same behavior as AOSP or I'm missing something? If you don't rebase from AOSP, the apps won't run pretty quickly.