zlacker

But you don't have any ability to run AOSP on any devices? Free as in literally unrunnable?

AOSP feels incomplete without there being some flagship way to use it.

>>jaunty+(OP)
It is the literal source code. You can read it, study it, distribute it, modify it. And I'm pretty sure the license allows you to sell it.

That's really really permissive.

>>bitpus+8j
They are talking about the device tree which has not been released with Android 16. So no way to run a custom kernel on actual hardware, unless that hardware is open. AOSP is a car without an engine now.

>>bitpus+8j
I guess I can also paper my walls with it...

>>jaunty+(OP)
Having stewed on this for a week, I'm even more morose over this.

I'm getting particularly salty that this is happening exactly as Android hurdles two huge integration challenges, as it goes from a standalone not-Linux-desktop single-screen computing device to something vastly more: a multi-screen capable, virtualized Linux desktop running device. Two huge leaps of integration.

This is just a maddening maddeningly crucial leap forward that Android is making right now, and it's woeful beyond words to see it making such a bold leap but leaving open-source totally behind at this exact junction, where the OS actually integrates with the hardware reasonably well/with more than the most trivial complexity for the first time ever.

This is just such a shitty shitty shitty turn of events.