backtop


Print 36 comment(s) - last by bug77.. on Sep 28 at 4:15 AM


Is bloatware protected under the tenants of open source?  (Source: Optaros)

Google CEO Eric Schmidt, during a recent Q&A session  (Source: YouTube)
Google CEO says it would be violating one of Google's guiding principles to allow users to revert to stock configs

From skins like HTC's Sense UI and Motorola's Motoblur, to the deluge of apps installed on Android phones by carriers and hardware manufacturers, Android phones can be a bit cluttered at times -- much like their PC brethren. 

Many customers have wished in vain that there was a single, easy "reset to stock configuration" option, which will revert their phones to a stock build of Android and delete the excess.  Not so fast, says Google CEO Eric Schmidt.

Mr. Schmidt, an opinionated figure in the tech industry and part-time evangelist for Google's philosophy, recently explained in a question and answer session why Google doesn't believe this is a good idea.  He states, "If we were to put those type of restrictions on an open source product, we'd be violating the principle of open source."

Of course "open source" is as wide and diverse an umbrella as possible in the tech industry, and Mr. Schmidt's definition of open source may be quite different from the next man's.

So other than taking the open source "moral higher ground", why might Google not want to give customers a quicker way to remove OEM/carrier junk?  Well one key reason is market share.  Google gives away Android for free, hoping that the mass adoption will more than make up for the development costs via advertising and app sales.  Part of the equation to convince wireless carriers and hardware manufactures to pick Android over a competitor (Symbian, webOS, Windows Phone 7) is allowing them to free modify their custom Android build to their heart's content.

But curiously, despite Mr. Schmidt's statement and the apparent advantages to adoption that not including a "clean build" option brings, Google reportedly will go in quite the opposite direction with Android 3.0 "Gingerbread".  Gingerbread will kill off custom OEM skins, replacing them with a single Google-made skin.  Of course the carrier-specific apps/junkware will likely remain, but Google's actions definitely show it to be quietly moving in the opposite direction, even as it defends customized deployments.


Comments     Threshold


This article is over a month old, voting and posting comments is disabled

I must be reading this wrong.
By UnWeave on 9/27/2010 3:39:21 PM , Rating: 2
"If we were to put those type of restrictions on an open source product, we'd be violating the principle of open source."

What? How is adding an option to revert to stock a restriction? Surely not being able to do so is a restriction.

I'm pretty sure he's just saying that because he has to. If they let you get rid of all the carrier's crap, carriers would get pissy. They put that stuff there because they want it there... or think you want it there. Or something.

I do think the lack of customization for 3.0 might be an issue, though. OEMs no longer have a way of distinguishing themselves (e.g. HTC Sense is great, I prefer it to stock). Also, they better have employed some dedicated UI guys, because vanilla Android is a bit of a mish-mash at present. I'm all for function over form... but come on, it's not even that consistent.




"I'm an Internet expert too. It's all right to wire the industrial zone only, but there are many problems if other regions of the North are wired." -- North Korean Supreme Commander Kim Jong-il














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki