>Also, the parts of Android that are open aren't really the most interesting ones, but the most mediocre. Much of the guts of Android is merely adequate, technically unimpressive, and deliberately selected over better alternatives because using a truly FOSS base would risk commercial isolation.
Yeah, that's why FireFox OS (HALs, RIL, mediaserver, input system, portions of the graphic system, init, kernel) and Ubuntu Touch (HALs, kernel, RIL, stagefright, input system, etc.) both borrow large pieces from Android. Even Mir uses the Android input system as its base.
You do realize that you're confirming his point. Basically the drivers and low level components are reasonable pieces of open source, and everything else is unusable by people who want to build a complete system.
If a usable open Android existed, those alternatives would be redundant.
No, he said the open source components of Android were mediocre, uninteresting and selected over superior FOSS components. I listed a bunch of the open source components used by two companies who have no problems with using FOSS components, yet still chose to use the Android bits.
Of course they don't use the ActivityManager, the Activity lifecycle is really an Android-ism and doesn't fit Ubuntu Touch or the web. Of course they didn't use WindowManager when they both already have components to do that kind of thing. Of course they didn't use the high level framework APIs, they have their own API surface.
A usable, open Android does exist, but other companies are still going to explore different platform models. I think the fact that they use a number of pieces from Android pretty much wholesale is a huge point in favor of an open, usable Android.
You're still missing the point that I actually rebutted: that Android's open source bits were mediocre and there exist FOSS components which are better.
Regardless, nobody ships AOSP because everyone wants to differentiate their platform by adding their own functionality on top. There are tons of AOSP-based ROMs on XDA, just go look. But with the abundant number of projects to tweak and modify Android, very few people build purely AOSP ROMs. They all add xposed or xprivacy or whatever because that's what they want to use.
Besides, saying nobody ships AOSP only phones doesn't mean they aren't usable, it just means that are better alternatives.
I acknowledge your rebuttal. Those components are fine.
But that doesn't change overall argument that the open parts of Android aren't a complete solution to make a competitive modern phone. What Google calls 'Android' is not just AOSP. So while AOSP provides an open base for a phone platform. Android as Google uses the term, is not an open platform.
Yeah, that's why FireFox OS (HALs, RIL, mediaserver, input system, portions of the graphic system, init, kernel) and Ubuntu Touch (HALs, kernel, RIL, stagefright, input system, etc.) both borrow large pieces from Android. Even Mir uses the Android input system as its base.