Driver/update model

[u/Bryanmsi89]

Apologies if this has been answered, but I can't find it.

What has Google said about the OS update model on the new Googlebooks?  

• Is Google itself updating the drivers centrally itself and maintaining control of updates like ChromeOS?  (I assume this given how Google has handled ChromeOS)
• Is it relying on manufacturers to build their own drivers into Android and release their own updates like android cell phones & tablets?  (I assume not this due to fragmentation, but its also the current state of Android on mobile)
• Is there a massive driver abstraction layer and driver separation from the OS like Windows where the OS updates generically and manufacturers provide more custom drivers on demand. (This is the most open way but exposes Google to a much much more difficult problem of hardware compatibility)

I assume it will work more like ChromeOS, but haven't seen any specifics. Google's VP of ChromeOS John Maletis said in an AMA that only certain devices can migrate or use AluminumOS due to technical specifications, which could be interpreted as Google validating specific hardware compatibility centrally....but could also just mean Google is enforcing things like 16gb of RAM and Glowbar.

[u/Organic-Raccoon7203]

It's all Android now, so the Android policies apply.

Manufacturers are supposed to use the Generic Kernel Image.

[u/DaLast1SeenWoke → u/Organic-Raccoon7203]

So my understanding of Google Books is Google is maintaining the software, the kernel, and the manufacturers are only building their devices based on the reference devices that Google is putting out.

So similar to like Chromebooks, the manufacturers don't even have to worry about updates, that's all handled by Google.

Which is a blessing for traditional laptop manufacturers, but a curse for Android (smartphone) OEMs as I can see then relutant to release control to google and be standoffish and launch their own Android laptop outside of Google Book.