ie8 fix

The Flawed Android Update Process; Too Many Cooks

By | January 19, 2011, 5:43am PST

Summary: The Android update cycle will continue to frustrate users, based on the flawed update process that Google has failed to address.

The Android world is getting used to seeing new accounts every day of users unhappy with the lack of an OS update for a particular handset. Google keeps madly churning out updates with tasty version names, which starts the clock running to see when (or if) a given phone will get the update. That starts the rumor mill cranking with theories why the OEM is refusing to release the update. It’s a cycle that is guaranteed to continue, based on the flawed update process that Google has failed to address.

This process is not new to Android, it’s been around since the birth of the smartphone. The platform creator (Google) releases a new version of the OS (Froyo, Gingerbread, etc.), which starts users clamoring for the tasty treat. The maker of a given handset (Samsung, Motorola, HTC, etc.) then takes the source code in-house and works on getting the new OS version working flawlessly on each phone they produce. If the OEM has made special modifications to the handset for a particular telco, then those have to be updated and tested on top of the basic update. New OS versions often break the OEM apps and widgets, and those must be updated to work properly.

Once the OEM work is done on a given update for a given phone, it is handed off to each carrier handling the phone to test on their network. This testing can be extensive depending on the carrier, and is necessary to make sure that carrier apps/services still work without problems. Once the new software is blessed by the carrier, a ROM image for the phone is prepared for over-the-air (OTA) distribution to the carrier’s customers. This ROM creation is not trivial, as a bad ROM can have drastic consequences, including turning working customer phones into bricks. Those familiar with homebrew ROMs can attest to that, as something as simple as a corrupt download can have dire results.

This entire process can take a fair bit of time, especially if the original OS update was significant. The more things have changed, the more add-on bits get broken and must be fixed. This customization is what has contributed to Android’s astounding adoption rate, but it comes with a significant toll to the update process.

Remember that each company that makes Android phones typically makes multiple models; it is why Android has grown so phenomenally. Unfortunately, multiple models at the OEM level turns each Android update into a major development effort. This effort increases exponentially with the need to specialize those updates for each carrier the OEM must support. Every layer of update development adds costs to the OEM, and more significantly to the customer, more time.

I’m not defending the OEMs nor the carriers, just pointing out the system is complicated and time-consuming. Google doesn’t help matters either, with its insistence on carrying its own phone (Nexus One and now the Nexus S), for the sole purpose of having one handset that gets updates first (and easiest). It is competing with all of its partners, rather than stepping in and doing something to help smooth out the whole process.

It is time for Google to take the Apple approach with the iPhone, and take control of the OS back from the OEMs and carriers. They won’t necessarily like it, but Google will come out on top in the end if Android users get every update in a reasonable amount of time. That may require reducing the level of customization open to handset makers and carriers, but so be it.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

James Kendrick has been using mobile devices since they weighed 30 pounds, and has been sharing his insights on mobile technology for almost that long.

Disclosure

James Kendrick

James Kendrick has no affiliations or relationships that need to be disclosed.

Biography

James Kendrick

James Kendrick has been using mobile devices since they weighed 30 pounds, and has been sharing his insights on mobile technology for almost that long. Prior to joining ZDNet, James was the Founding Editor of jkOnTheRun, a CNET Top 100 Tech Blog that was acquired by GigaOM in 2008 and is now part of that prestigious tech network. James' writing has appeared in many print publications: Smartphone and Pocket PC Magazine, Information Week and Laptop Magazine to name a few. James' coverage of the mobile technology sector has regularly appeared in the New York Times, Salon.com and CNN/ Fortune online. Not just a writer, James has filmed numerous video reviews and how-tos that have garnered well over a million viewers. He has appeared on local news segments and been interviewed by the Associated Press on mobile technology topics. Additionally, James has been podcasting about mobile technology for years.

104
Comments

Join the conversation!

Just In

Microsoft F.U.D. campaigns won't work
2012WillGO2012 29th Mar
Hey Kendrick,
Why not head over to the Tween boards and babble about your nonsense.
Windows Phone is nothing but a BRICK. ZERO Customization. a *NEON BLUE* phone, with a Metro Interface. It's accurately obvious the GOON Ballmer does not "GET" Phones....and simply does not understand it's the 21st century where people want CHOICE---why else is there 15-different flavors of TIDE detergent.

Yeah, that myopic thinking might have worked in the 20th Century---no more
Now that Dell and HP have pretty much said they won't make Home PC's anymore...where is Microsoft gonna sell their CRACK ROCK OS? Much less create a drag effect for their Phones??

OH, wait...I bet all those IPad holders will "update" their Windows Phone via the IPad...YEAH RIGHT.
1 Vote
+ -
Nobody minded when Baskin & Robins came out with 31 flavors
Dietrich T. Schmitz, ~ Your Linux Advocate Updated - 19th Jan 2011
Diversity is a good thing.
Besides OEMs are perfectly happy to take ownership to the degree necessary in the software development process.

It gives them freedom of choice and autonomy to do what when and how.

They didn't have that with previous smartphone O/Ses.

There will be glitches to be worked out regardless--that's life.

But I see nothing but net positives in the Android ecosystem.

The masses won't mind OTA updates once every 3-6 months and even 6 months is reasonable to expect from a release cycle perspective, but not longer.

If you expect more frequent updates, you are a geek and in the minority.

And then if you are a geek, you know what to do flash your own phone anyhow.
@Dietrich T. Schmitz, Your Linux Advocate I think you are missing a very key negative. This is not really about updates, but fragmentation. Fragmentation is becoming a major issue in the andriod ecosystem. I am not only concerned with the frequency of the updates, but also the availability of the updates as my phone ages. Furthermore I am a geek and could flash my phone, but I will not flash my entire fleet of phones. Keep in mind these are tools for me and my staff to use. I like tinkering as much as the next guy, but I don't tinker with my production systems, and I won't tinker with the phones I put into my users hands. They need to work 100% of the time.
So in short fragmentation and the update process is flawed, and represents a big negative in the andriod ecosystem.
@jhuddle: Absolutely. And that's just the tip of the proverbial iceberg. Major version upgrades a problem? Think bug fixes on exponentially growing OS-handset pairs, per carrier. It becomes impossible to trust Android with timely security updates. What do you do the next time there's a zero-day attack on Android? Scrap your entire fleet?
@Dietrich T. Schmitz, Your Linux Advocate
So why in the hell Windows Mobile failed? Except for its user interface and design cues from iPhone, Widgets from Yahoo! and it core os as linux derivative the architecture/design of Android is borrowed from Windows Mobile, so it also borrowed all the issues of Windows Mobile. Fragmentation, Carrier/Maker customizations are hurting the Android, if not they are not doing it today, that will eventually. I have seen Android running on top of resistive touch screens (I have nothing against the resistive touch screen and it gives you more precise and accurate location than capacitive) and the feel of android is not fluid. Google has no control on the end. They missed the main cue from Apple well when they were sitting in its board meetings. Google wanted it has to be on more devices so it could invade more number of emails and search terms of its users so it could pump more ads, there is nothing wrong, but it should have been more strict. It is becoming late for it to go back and fix the issues.
@Dietrich T. Schmitz, Your Linux Advocate
I am not a techie but I still work on IT. Android sucks, I want my iphone back!!
0 Votes
+ -
Now you're getting it, welcome back
MacNewton Updated - 19th Jan 2011
@Hasam1991

Thank you for your honest feedback.

PS
Get well Steve, we are all hoping for the best!
0 Votes
+ -
@Hasam1991 I don't want an iPhone, you do... go get an iPhone, I'll get an android. Isn't it wonderful we have choice!
@Dietrich T. Schmitz, Your Linux Advocate

Sounds like a HUGE plus to the continued profit for the vendors while screwing the end user.

When you have 5 current version of the OS shipping on brand new out of the box hardware, you have serious issues.
Like buy an auto and it ONLY runs on "Shell" gas. Regulation needed if Companies can not behave in a "fair" manner. IF a two year contract is required then ANY and ALL updates need to be OPEN for the customer to decide IF they want it or not. OTA, is not a requirement which is the point that seems to be referred to as the longest delay. Either stop all the "BLOATWARE" and/or release the 'code' so XDA folks can (and will) provide timely updates.
@heredavid - don't put too much faith in XDA guaranteeing to release thoroughly tested updates for all handsets for all carriers:
1) The test matrix itself is a considerable challenge
2) XDA do a pretty good job most of the time, but don't have the resources necessary to perform full network certification testing and/or thorough testing of the rest of the OS and apps.

Most carriers agree to support the OS & software shipped when you buy the phone. They may optionally support future OS releases, but are not AND SHOULD NOT be REQUIRED to do so - the cost of forcing them to do so would make handsets triple in price.

Put it this way, do you expect Ford to have to support installing a brand new engine into a 10 year old vehicle? Of course not. So neither should handset vendors be REQUIRED to do so either.

There are chop shops who can fit a new engine into an old car if you so wish A buddy with a grinder and a welding torch may get it to fit, mechanically, you won't see the same levels of fuel economy and reliability that you'll get from a new vehicle. Some companies (e.g Shelby) will sell you their services along with a warranty on their work ... but only for specific vehicles & engine types that they know and have tested to work well, but they won't sell and support a 1967 Mini Cooper fitted with an F250 engine ... not unless you're willing to pay them A GREAT DEAL OF MONEY!
0 Votes
+ -
@Bruizer
Well put. The title should have read "Too many crooks in the kitchen". What we are seeing happen to android is every entity with their hands in the game (google included) are trying desperately to wring profit from it by taking as much out and putting as little back as they can get away with. See "The tragedy of the commons" (on wikipedia or your reference of choice) for a more eloquent explanation. Bottom line, there is too little incentive for Android to get better, so the corporations will make whatever money they can in the short term and leave it dead on the side of the road when the next big smartphone thing comes along (which is about every two years, the rate we're going.)
@Dietrich T. Schmitz, Your Linux Advocate
Sorry - you're way out in left field on this one.

We've seen this kind of failure once before in another mobile operating system. Windows CE/Mobile. Microsoft would generate a new version, it would go to phone manufacturers who had no incentive to update users. If they updated their phones the carriers balked because no one was renewing a contract with them.

Guess where Windows Mobile ends up? Yeah, rubbish heap.

If Google doesn't start managing updates itself, then I'm afraid the Android juggernaut will grind to a halt and get tossed aside.

Has HP got the plot? Let's hope *someone* does.
0 Votes
+ -
@Dietrich T. Schmitz, Your Linux Advocate

then you missed the main issue...

many of these handsets are still running 1.x versions of Android because the updates are simply not being released. would you really want your Linux servers running on a 2.2.x kernel because the person who sold you the hardware wanted you to buy new hardware to get a 2.4.x or 2.6.x kernel?
@Dietrich T. Schmitz, Your Linux Advocate. Bad analogy as BR never had a Vanilla 2.0 competing with Vanilla. Theoretically, new versions of Android are improvements. Sometimes they contain bug fixes. Take a look at all the unhappy Samsung Captivate users due to GPS problems. How long does THAT take to resolve?

I agree that the masses aren't looking for phone updates, in general, but you better bet that those with bugs, freezes, reboots, or battery issues ARE looking for relief! And to the extent that some company's "overlay" keeps these things from being corrected, these companies deserve to suffer ONGOING BAD PRESS.

I'm now adding "history of upgrades" to my requirements list. Sony Ericsson now loses points in my analysis, while HTC and Motorola gain. Meanwhile, I sit on the sideline.
0 Votes
+ -
GPS
Dietrich T. Schmitz, ~ Your Linux Advocate 19th Jan 2011
@bmgoodman
There was an OTA 2.1 fix that went out in September 2010.
I installed it.
0 Votes
+ -
@Dietrich T. Schmitz, Your Linux Advocate
You will be disappointed to note that, despite more than 6 months having lapsed from the 2.2 "Froyo" version being released, many handsets (released even after that date) are still languishing with no upgrade to 2.2 in sight. Still don't see a problem?
@Dietrich T. Schmitz, Your Linux Advocate

Gee, do we all have to be car mechanics to drive our cars?

We are at the precipice of computers becoming everyday devices that one should not need to be a techie geek to use or maintain. There will always be hot rodders but they become the minority.

Steve Jobs was correct.
@xyzzy_ Gee, do we all have to be car mechanics to drive our cars?

If you want to put that brand new 2011 motor in your 2010 then yes. Most people don't even maintain their cars, but they have no problems using them.
0 Votes
+ -
OEM bottle-neck
Tom6 20th Jan 2011
The bottle-neck is clearly stated as being OEMs using proprietary methods rather than OpenSource. How is that Google's fault?

Google even show by practical example that using an OpenSource route gets the job done faster but still separate companies insist on doing things the slow way. Is the article suggesting that Google should take-over the OEMs? Surely market-forces will push and pull the OEMs to look around to find a better answer than they currently use.
Regards from Tom happy
0 Votes
+ -
Google cannot put the Genie back into the bottle.

The OEM's and carriers are not going to give up their ability to deeply customize Android for their devices and target markets.

One of the costs of Android's explosive diversification is that carriers and OEM's support of legacy handsets will wane more quickly leaving customers stranded on older versions of Android and unable to enjoy the latest and greatest apps that take advantage of newer features of the OS.

The carriers and OEM's have little vested interest in supporting older handsets that they've typically sold at bargain-basement prices - they want users to pay to upgrade their handsets because they cannot afford the ballooning costs of supporting existing customers' devices.

But this sucks for the user who has no guarantee that a handset they buy today will be able to run tomorrow's version of Android.

Such is the cost of the Android model.
0 Votes
+ -
RE: The Flawed Android Update Process; Too Many Cooks
jBundy.com-23888787227187618789222526229331 Updated - 19th Jan 2011
@bitcrazed

The OEM's and carriers won't "give up their ability?" They are free-loading off of Google, albeit an open source platform, and making more than they would with a licensed platform. Google can at any time and must close Android code temporarily to consolidate the many versions in use. It could certainly re-open the code in the future so long as GOOGLE controls the update process where Android is redesigned so future versions are backward compatible with older apps, don't impact existing carrier requirements, and Google MANDATES that OEM "native code" mods be converted into downloadable apps while allowing them to be installed AND uninstallable. To date HTC Sense, Touchwiz, Motoblur, and other OEM mods that impede the update process have done more harm come time for an update than good. The update process shouldn't be as painful as it has been. On another note, the need to configure Android for each individual device is also a problem. Windows Phone 7, while nascent, at least has minimum specs that sort of streamline the R&D of new devices. With Android being open source, GOOGLE NEEDS TO TAKE TEMPORARY CONTROL and launch minimum specs such that the source code could literally be installed and function fully on any device with those minimum specs. Carrier modifications should be pushed OTA and OEM modifications downloadable from the market, not overlaying the system in a way that users can't get an OTA update to the Android stack direct from Google. Open source is good for creativity and technological growth, but does that mean that the delivery process shouldn't be organized to serve the consumer best?
@jBundy.com most OEM/Carrier devices running Android are using the version they've paid to license from Google in order to acquire rights to run Google's apps on those handsets and to get support from Google when customizing their OS build for their devices.

As you point out, Android is now starting to hit the many issues that plagued Windows Mobile and similar :The cost of rolling out an OS build to a wide variety of devices with wildly different hardware, performance and stability characteristics is EXPENSIVE. The costs of supporting that landscape of devices beyond even one update is COLOSSAL.

As I said, Google cannot put the Genie back in the bottle. If they were to try to wrestle control of Android and dictate hardware requirements to the OEM's/carriers, then the OEM's/carriers would just fork Android and create their own OS platform that they layer their own apps and experiences on top of.

One of the reasons the carriers want iOS devices on their shelves is not just that they acquire a ton more customers, but that they don't have to do anything like as much work to support the iOS devices they sell - Apple picks up a HUGE proportion of ongoing iOS device maintenance & support.

Microsoft, while late to reboot their mobile efforts, have also taken a pragmatic approach to this problem: Like Apple, they pick up a lot of the support for the OS and apps, while still supporting a wide range of devices and carriers. What's more, WinPhone's OS cleanly segragates the code that affects the carrier's network allowing them to isolate changes to the OS & user experience from changes that may require re-certification of the comms/network components. This makes rolling out updates to the OS *FAR* simpler and quicker. Of course, over time WinPhone device capabilities will diversify, but perhaps less so than WinMo/Android experienced, allowing Microsoft to deliver a far more consistent and longer-lived device experience.

Only time will tell how this all plays out, but make no mistake, Google have a significant challenge on their hands.
@bitcrazed Just as the Droid Eris was dropped by VZW and OMG! A 2.2.x ROM was released by the dev. community and if I didn't mistake what I read ... there is now a 2.3 stable rom for it. Just because a carrier doesn't want to support it doesn't mean that it can't be upgraded. Now if my Droid X with it's DRM'd eFuse chip is EOL'd .. I'm screwed because the carrier and Motorola decided I wasn't to be trusted to do what I wished with the hardware I purchased .. unlike my Droid 1 which ran vanilla Android and can be upgraded and messed with until it gets too slow for MY tastes.

If Google would put the smackdown on all these UI's and baked in mods ... we wouldn't have this issue. But then the hardware makers start looking like HP, IBM and the rest ...and we get price wars and no margins. The carriers and OEM's won't let that happen ... Google must force the issue.
@ben@...
But why would a non-techie/geek would want to download ROm from a developer and flash their phone. Doesn't WinMo had the same developer community doing and finally it made it failed?
@ben@... Nonsense. Your experience and skills are atypical of most cellphone users.

Imagine the utter cluster$uck that would ensue if Verizon (for example) was to say to customers go install any OS build you like from anybody - we'll be there to support you whatever choice you make.

How long do you think it'd take before some evil sod was to release an OS build (whatever OS - doesn't matter) that either hacked the carrier's network and/or broadcast all your device's stored data and/or usage information, browsing history, calls, etc. to a set of servers that then teased apart your data to empty your bank accounts and obliterated your identity?

A matter of hours numbering less than 20 I would guess.

Carriers have a duty to protect ALL their users from rogue handsets running untested and uncertified code. One rogue phone could cause catastrophic comms meltdown.

When you buy a phone, you buy a phone certified to run a particular software stack. The carrier has the choice as to whether to support future OS releases, but that's their choice based on many factors including the time & cost of porting, testing and re-certifying the OS release on zero or more handsets and supporting that new OS release into the future.
0 Votes
+ -
Yep, the stupid consumer
Economister 19th Jan 2011
@bitcrazed

I have played this tune a few times before, but as the American consumer seems totally enamored with the "great" prices on "subsidized" and contracted phones sold and controlled by the carriers, I guess the consumer gets what he/she deserves. As you say, a big part of what motivates the carriers is to obsolete their phones to make you buy a new one, preferably before your contract expires, so they can charge you a termination fee and then lock you in again.

Buy an unlocked phone that you can control and stop bitching.
0 Votes
+ -
@Economister

What you are talking about? there is no 'termination fee' if you perform an upgrade before the contract is over. There is also no 'termination fee' if you buy a phone from someone else and switch it out before your contract is over. An ETF is charged ONLY if you terminate your contract and switch to another carrier. If you always stay with your current carrier and never switch, or if you switch after the contract is over, you will never have to pay an ETF.
@Economister - on the contrary, carriers don't want you to upgrade your phone unless it moves you up their pricing plans as do the current move from cellphones to smartphones.

Every time you upgrade your device, the carrier has to foot the bill for the $200-$300 discount you get against a new smartphon, carrying that liability for the duration of your contract with them.

The carriers would LOVE YOU if you were to stay with the same handset for more than 2 years - that way, they get to make some decent money off you.

I believe this is something Microsoft is banking on - they've historically offered great support for customers who bought the original Zune devices long after the typical 2 year lifespan that most customers keep their cellphones for. If Microsoft rolls out upgrades and updates for WinPhones many years in to the future, then there'll be less need to buy a new device as your current phone will get many/most of the new features. This will be VERY compelling to most carriers.
@Doctor Demento - while ETF may not have been the correct term, the point was accurate - choose to upgrade your handset before the end of your contract and you're likely to be charged an insubstantial amount for the privelige.
0 Votes
+ -
It is even worse...
Bruizer 19th Jan 2011
@bitcrazed
But this sucks for the user who has no guarantee that a handset they buy today will be able to run tomorrow's version of Android.

Really should be:
But this sucks for the user who has no guarantee that a handset they buy today will be able to run today's version of Android.
@Bruizer
good point.
@Bruizer lol true!
@Bruizer - today's version of Android != the currently shipped version of Android.

Just because Google ships what it thinks is a new OS, it's up to the OEM's to test said release against their hardware and update drivers & code as necessary and the carriers need to do the same, testing the newly updated devices against their network. This may also require updates and changes to drivers and code to ensure the device operates securely and reliably.

This can take considerable time with so many OEM's, devices and carriers with different levels of resources, skills and time available to do the work.

An OS becomes available only when it is installed on a device shipped by the carrier. Until then it's tomorrow's OS release wink
0 Votes
+ -
@ bitcrazed
Bruizer 19th Jan 2011
But you can still get Android 1.5 on brand new devices. This is what people mean when they say Android is fragmented. You have 5 current versions shipping. In 2-3 months, you will have 7.

I am really interested to see how MS rolls out their upgrade to WP 7 in a couple of weeks.

It is a daunting challenge to mass upgrades on a large scale like this and it takes serious planning and logistics. This includes OS, application and infrastructure planning from the requirements to the code.

So far, it looks like Google did not plan this out well at all.
0 Votes
+ -
You've got it exactly right...
rx7racer 21st Jan 2011
@Bruizer Very true. I bought my HTC Legend in late July, about 6 weeks after HTC announced they would release 2.2 for Legend. I was aware the inability of 2.1 to save apps to the card, but wasn't aware, despite a lot of pre-purchase research, of issues with saving photos, failed backups, and the long-running bluetooth issues and voice commands. But my carrier, Bell Canada, shows no sign of pushing 2.2, now more than 2 months after HTC finally released it.

I'm aware I could root the phone and install a ROM such as the Vodafone one that would give me 2.2 and probably only lose me the the Bell billing and usage apps - as long as I didn't brick the phone. I don't have a problem that carriers not OS upgrade old phones ad infinitum, but I do have a problem with my carrier not supporting an OS upgrade announced before they began selling the phone, and certainly before I purchased it. Especially when the update in question promises to fix the significant issues that are detracting from an otherwise very satisfying phone.
0 Votes
+ -
Growing pains.

Well I hope Android makes it through to adulthood.

By then, I hope there will be two new things:

1. Android Internet Cafes
2. "real" CTO or Configure-To-Order

1. An AndroidCafeStation in every town or one in every square city mile! A place where Android user can get help with updates, among a thousand other unique services. I want to relive the good feelings I had at a university computer lab, and the good feelings at I had with users groups at HAL-PC and the good feelings I have and wished I would have at hanging out at Barnes and Noble. There is no place in the world where I can get those combined good feelings.

2. CTO, an enhanced business model, best done by a thrid party, that can solve all the problems you mentioned.

I don't think there is anything wrong with Android's update process nor do I think there are too many cooks. I actually think we should have more cooks, maybe not the kind you referred to. But that's why Android will create new markets and industries. Right?
0 Votes
+ -
"Android Cafe station in every town?"
Tigertank 19th Jan 2011
@JoeyAndroid
Good luck with that.

Honestly, If Android needs a service kiosk in "every square mile" then that is a pretty good indicator that it is doomed to failure.
@Tigertank - precisely. Sometimes, free is too expensive. How much will Android customers pay for access to the services offered in such cafes? Apple can afford to do this because Apple customers pay a heck of a premium on their devices.
@bitcrazed
Apple doesn't have to afford anything, given that their retail stores are already places of commerce that generate some of the highest sales per square foot in the entire retail sector. If anything, Apple has situated their stores to reinforce the brand. It's one thing to offer up a good product, but the brand image and user experience really get burnished if that's followed up with a point-of-sale/service that garners some of the highest customer service ratings in the business. Most CE companies view customer service as an expense that they need to minimize, but the Apple Stores can support the aftersales service function by sharing the overhead with a highly successful sales space.

People like to point out how the iOS ecosystem reinforces the platform. But, the Apple stores are another part of that ecosystem. Doesn't excite tech bloggers (they typically remain convinced that retail stores were killed off by online purchasing years ago, when in fact, ecommerce makes up less than 5% of the overall retail sector), but it serves a critical customer service function and also functions as a community gathering spot (training classes, special events, etc.).

The issue for Android is that there is no one place for a customer to get a definitive answer if they want to know when that 2.2 update is coming for their device, or if they want to try out all the latest Android devices. Google, the manufacturers, and carriers will all point the fingers at each other.
0 Votes
+ -
@SFWooch Apple doesn't have to afford anything, given that their retail stores are already places of commerce that generate some of the highest sales per square foot in the entire retail sector.

Was just thinking yesterday as we walked by an Apple Store that there is no other business that I have ever seen in Malls that consistently has the number of customers that they do. Not that everyone in there is converted into a sale but it is pretty amazing that the stores are consistently packed.
As one of the original supporters of Android when buying an HTC Magic in Norway, I have been frustrated both by the lack of information about possible upgrades to version 1.6 or above, and by over a year without access even to paid Apps.

This resulted in my choosing an iPhone 4 recently, rather than one of the many Android devices on the market.

I will be buying a new Android at some point in the near future, and think tech journalists could do us all a service by demanding clear answers from Manufacturers, Carriers, and Google - hanging them out if you like - so consumers who care can make informed decisions.

Thanks James for taking this matter up in your article happy
0 Votes
+ -
RE: The Flawed Android Update Process
tn77 Updated - 19th Jan 2011
Yes, it's a flawed system. The Nexus phones are the only ones I could ever own (currently have a Nexus One) because the OEM and carrier UI overlays and bloatware are just nonsense. You're right that Google needs to take back some control, but they seem unwilling to do so.

That said... where's my Nexus One update to Gingerbread? No idea why this one is taking so long!
0 Votes
+ -
@tn77

perhaps the Nexus S is the first step in taking back some control?

rather than storm the bastions all at once, a small, more subtle roll out of units that make the option of an unmodified Android OS available (starts with the Nexus S) rather than the only way to get Android at all (Nexus One) will start to build consumer interest without facing the massive roadblocks the carriers here in the states put in the way of the Nexus One.

the only reason i didn't get a Nexus One was that there was not a version that would work on my carrier's network.

perhaps using a blended model will will get the ball rolling here toward the handset being a device separate from the carrier's contract and control?
0 Votes
+ -
The OEMs / Carriers should give us the option of downloading a stock Android version with only the device drivers necessary to support the quirks of the hardware.
@GoldenUnicorn
YUP That's why I'm going back to the iPhone, I am very disappointed with my Android Galaxy S from T-Mobile, seriously, a pink startup screen with that annoying T-mobile jingle??
0 Votes
+ -
How do you think they do the B1G1F?
Bruizer 19th Jan 2011
@GoldenUnicorn

It is because of the carrier add ons. Do you want cheap or do you want quality. Pick one.
UNIX overall has had this problems since System III and BSD versions from way back in the 80's... Solaris, HPUX, AIX, etc. all contributed to some level of fragmentation of the OS. How many dervitive versions of UNIX exist now?

Standards help, and maybe Google can establish that core set - like System V in the day. It still does not get you out of trouble when there are hardware variants throughout the entire universe.

I'm a geek, but I also understand that complex systems that get updated need solid testing, and waiting for a software upgrade to ensure I don't end up with a brick is worth it.

Unfortunately, older hardware will suffer as software always tends to exploit the latest and greatest features. Backward compatibility can be one of the OS standards for basic functionality.

Again, I think we have been here/there.

Tommy.
@TommyDom
This is why I object to people using the term "fragmented" when referring to the situation with Android. These add-on user interfaces and such things from the handset manufacturers do not change what binary executable files run on Android. The same executables run on each of the varying Android phones available. All those versions of Unix that you mention needed entirely different binary files in order to run a program. You couldn't get a program that was released for Solaris and run it on HPUX, etc. Unix was one term that was used to refer to several different operating systems, not just updated versions of the same operating system.

With Android, whichever device you have, you can go to the same App Store and download the same file and have it run (as long as your phone meets the minimum hardware requirements and minimum operating system version requirements). So an Android app with minimum requirements of Android 1.6 will run on just about every phone out there.

Android phones are not in a situation like Unix. The Android situation is more like Windows with one important difference: You are not the administrator of your own system.

Yes, different phones have different add-ons and customizations. You can generally set the Android shell to the generic one if you want to though. The add-ons are like the junkware you get on a new PC. The real problem is that when a new version of Windows comes out, nobody is stopping you from wiping your system and installing it if your system has the power to run it. However, with the way carriers are locking down their phones, you don't have this option with Android unless you "root" the phone.
1 Vote
+ -
An alternative...
printing724 19th Jan 2011
Google doesn't need to directly take back control, but they could provide a strong nudge by providing a basic certification program, let's call it "Android Prime" for conversation's sake.

A phone certified under the Prime program would have to meet the requirement of being able to be reverted to the latest stock Android build and shipped with the necessary tools to do so. Google's certification of it would be that the manufacturer's reversion process actually produces a working phone.

Manufacturers/carriers would be free to load up the retail phones with bloatware and custom UI's. The user would be free to remove them and would be provided the working tools to do so.

A new release of Android would mean that every phone on the market loses its Prime certification (after a grace period) until it is demonstrated that the new version works on the unit.

"Prime" phones would probably be able to command a premium in the market. And no one would be forced to do anything they don't want to...
1 Vote
+ -
Great minds think alike
voyager529 19th Jan 2011
@printing724

I was thinking along a similar line. Google may not be able to put the fragmentation genie back in the bottle (nor would I want them to; I for one like HTC's SenseUI and run SkyRaider for that reason), but they COULD contractually obligate carriers to commit to providing Android updates to any phones advertised as running the OS for the duration of the longest contract issued, starting at the date of the last sale of that handset.

I think this would be a better system (i.e. a commitment to provide updates) than having a device lose its certification. After all, if a handset is owned by a consumer and is no longer certified, what recourse does the consumer have, and what incentive does the telco have to rectify it? IMO, the best 'or else' Google could provide would go something like this: "If there isn't a telco-blessed update of 3.07 Tiramasu released within 60 days of its official rollout on the Nexus line of handsets, we'll make the rooting tools publicly available, and no, you won't be allowed to blacklist the handset from the network". The bleeding obvious issue with this is: the telcos will never agree to it.

Joey
0 Votes
+ -
Microsoft F.U.D. campaigns won't work
2012WillGO2012 29th Mar
Hey Kendrick,
Why not head over to the Tween boards and babble about your nonsense.
Windows Phone is nothing but a BRICK. ZERO Customization. a *NEON BLUE* phone, with a Metro Interface. It's accurately obvious the GOON Ballmer does not "GET" Phones....and simply does not understand it's the 21st century where people want CHOICE---why else is there 15-different flavors of TIDE detergent.

Yeah, that myopic thinking might have worked in the 20th Century---no more
Now that Dell and HP have pretty much said they won't make Home PC's anymore...where is Microsoft gonna sell their CRACK ROCK OS? Much less create a drag effect for their Phones??

OH, wait...I bet all those IPad holders will "update" their Windows Phone via the IPad...YEAH RIGHT.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix