Google demands veto on OEM Android changes, stretches definition of 'open source'
Google, according to reports from "a dozen executives working at key companies in the Android ecosystem" is finally locking down the open source and easily-fragmented Android operating system.
As it currently stands, Google hands over the 'final' code for each version of Android, and OEMs and developers then spend some time customizing the OS to fit their hardware, and to create a unique and marketable flavor. That's all set to change, however.
Over the last few months, according to several people familiar with the matter, Android licensees such as HTC, Motorola and Facebook, have been asked to sign 'non-fragmentation clauses.' This new contract caveat will give Google the right to review and pass judgment on all changes to the Android OS. Two executives at Facebook say that they're unhappy that Google gets to review its changes to Android -- which is understandable, given Facebook and Google are direct competitors -- and there have also been allegations that Google is preventing some Verizon devices from shipping because they include Microsoft's Bing instead of Google search.
The thing is, licensees could refuse to accept Google's new vice-like grip on its OS, but then they would have to wait for the source code to be released to the Android Open Source Project. At the moment, OEMs get access to the code some weeks or months before its public release, but -- theoretically -- if Motorola signs the new contract, and Samsung refuses, then Samsung could be months behind Motorola in releasing the latest and greatest version of Android on its devices.
At this stage we're not sure whether Google's non-fragmentation clause will affect 'skins' like HTC Sense and Motorola Blur, or if this change is merely targeted at preventing bastardized versions of Android appearing on tablets. In the long run, though, we're probably looking at Google becoming the sole arbiter of Android's look and feel.
There will still be replacement home screen apps and launchers, and custom ROMs, but their release will be dictated by Google's currently-unknown source code release schedule. Don't forget, the latest version of Android, Honeycomb, again because of fragmentation risks, won't have its source released for the foreseeable future. In other words, if you want to compete in the Android ecosystem, you have to grant Google's demand for veto power, or wait for a source code release that may never happen.
Reel them in with the lure of open source and free licensing, reach an astounding and industry-leading 31% market share, and then tighten the screws. Genius, Google; despicably genius.













Comments
10
Subscribe to commentsSamuel GibbsMar 31st 2011 8:55AM
Don't be evil eh? Smart move for the platform IMHO, but a bit ruthless.
JamesMar 31st 2011 9:23AM
Brilliant. All the "Faindroids" out there won't be able to litter comment sections with as much "Open" B.S.!
k7of9Apr 3rd 2011 8:40AM
@James seems to me comments sections are mostly littered by non-fandroids eager to tell the world how not open android is according to them.
I'm an Android user and if you ask me it's better for the platform to impose some restrictions. However I wish they would have done so from the start.
thatguyzxMar 31st 2011 12:55PM
I love my Nexus One, but I am sick of the fragmentation making it so that I suffer crappy looking apps due to low res android cheapy phones. Some manufacturer mods (sense and blur ) make the phone lag or at least the animation speeds are so slow my friends are forced to use custom launchers to speed it up.
As long as the "open" aspect stays enough for devs to keep making awesome custom roms, I support this ban hammer on fragging. lol But who knows where slopes like this will end up..
AdamMar 31st 2011 4:16PM
@thatguyzx Kinda need manufactures to not lock everything inside the phone aswell for that to work, as we are seeing more and more ppl like HTC etc rly locking their phones up.
thatguyzxMar 31st 2011 6:59PM
@Adam This is true. Before we only had Motorola to fear for locking their devices, but it seems it's starting to spread...
Speaking of fragmentation, Amazon Appstore?... wth is up with that?!
Mike ComierMar 31st 2011 10:10PM
It's not a matter of "if" the source code will be released but when. And it's perfectly reasonable that if developers want early access to the code from everyone else that they have to abide by certain conditions. Otherwise they'll just have to hold up for the open source release like any other developer that would take advantage of its open source nature. I personally don't think it's fair that OEMs get to play with the code as much as they want and turn Android into a mess before anyone else gets a chance to do their own open source magic. This puts things on even ground and help prevent Android from getting too messy. I will grant though that Google should have done it from the start. But I suppose they just didn't see fragmentation becoming as much of a problem which is a shame.
HarshApr 1st 2011 11:04AM
The Android OS is open source. Period. They have a closed branch called Honeycomb that they refuse to open until they have a version that works well on phones. Reasonable but that branch is not open source. Again well within in their rights to do though. Not just as the founder of the project but anyone can take a branch, modify it a lot and not release the code. The OS's OSS license is permissive enough.
Now Google licences its Google services with the OS which affords them some leverage. Such as demanding veto rights on OEMs changes. This has nothing to do with the OS's open source status. It just doesn't.
ANGELUSApr 1st 2011 11:49PM
I wouldn't mind Sense and Touchwiz and the like if Google just made it mandatory that they can be easily turned off or removed. Same with OEM software...
AnthonyApr 2nd 2011 7:40AM
Good. If OEM skins died tomorrow on Android the world would be a better place.
Nothing. And I mean nothing is and nice as a "Google Experience" phone.