In that case, the Fuchsia kernel could just be another "client" to that layer.
(just speculating here, no idea if that is in any way what they're planning)
https://android-developers.googleblog.com/2018/11/an-update-...
OEMs got around Treble certification by releasing mostly devices with Android 7 on them.
And given that OEMs were the ones supposed to push Treble updates not Google, even those that released devices with 8 weren't that active pushing them.
Which has finally made Google include some update requirements on the Play Services access.
Did you mean cannot publish?
What GNU heritage? Android has only ever used the Linux kernel to get a leg up on hardware support in the early days. AFAIK there has never been any GNU userspace of any sort in anything Android related, much to the chagrin of the Linux community.
The NDK is constrained in what it can do, as per security concerns.
There is termux as port of GNU on Android, but only applications that rely on plain ISO C, ISO C++ can be ported.
Syscalls support is hit and miss per devices, as it isn't part of official NDKs APIs.
* A response to Java lawsuits
* Something to work on that is interesting
But you raise a good point — why let go of Linux? Seems like a risky case of rewrite-from-scratch.
What are the odds it works out? It's not a sure thing. And what would the benefits be?
If that is the case I could imagine that Fuchsia might not become a separate "product" for consumers at all - instead, Google could replace Android's implementation "under the hood" with it but still present it as just another Android version brand/UI wise.
If they managed to do the same with Chrome OS, the'd actually have archieved consolidation on a technical level without causing consumer confusion. (Well, more than there already is)