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

RE: It's really quite simple
By FITCamaro on 9/27/2010 8:39:58 AM , Rating: 2
PS - "Because it looks cool" or "It has a fast processor" is not a valid excuse for bitching about a phone you chose to buy having a UI you deem to be crappy.

You have the ability to try the phone out in a store before you buy it. And you also have the ability to return said phone within 30 days and get a new one if you don't like it.


RE: It's really quite simple
By Redwin on 9/27/2010 9:24:32 AM , Rating: 2
Not sure why you get rated down for this Fit. Its true, nobody is forcing you to buy a skinned phone. I bought an Evo, but I happen to like SenseUI. If you don't, then don't buy one, or do, but realize you may have to root it to reskin it totally. Which, honestly, is not very hard on an Android phone, and many would argue that google doesn't mind it being that way for just this reason.

Open source cuts both ways... they can easily put what they want on the phone they sell you, but you can also pretty easily take it back off. If you really don't want it there, and really don't want to root your phone, then you probably just should get a different phone. Voting with your dollars is the proper response if you disagree with a company that stringently.


"Young lady, in this house we obey the laws of thermodynamics!" -- Homer Simpson














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