Slashdot Mirror


For Android Users, 2012 Is Still the Year of Gingerbread

First time accepted submitter brocket66 writes with this excerpt from BGR: "Three major revisions of Google's Android operating system have launched since the company released Android 2.3 more than 21 months ago in December 2010, but Gingerbread is still the most widely used version of Android by a wide margin. A study conducted early this year by graphic designer Chris Sauve projected that based on Android adoption trends up to that point, Android 2.3 Gingerbread would be the dominant version of Android in 2012 despite the fact that Android 3.0 Honeycomb and Android 4.0 Ice Cream Sandwich had already been released. Now, as the fourth quarter of 2012 approaches, data from Google's Android version distribution tracker confirms once again that those projections were accurate."

52 of 257 comments (clear)

  1. So? by symbolset · · Score: 4, Interesting

    1.3 million Android activations a day. I guess we like it this way.

    --
    Help stamp out iliturcy.
    1. Re:So? by fm6 · · Score: 5, Insightful

      Speak for yourself. I like a having a hackable smartphone or tablet that lives outside the Apple walled garden. I do not like that developers are being forced to code to an API that Google froze as obsolete almost two years ago. Nor do I like the fact that a few braver developers are writing cool apps for the current API, but IU can't run them because phones I can afford are stuck on Gingerbread.

      Android phone sales may be fine now, but technology is a grow-or-die marketplace. No matter how well it's doing now, Android doesn't have a future if it's stuck like this.

    2. Re:So? by hairyfeet · · Score: 3, Insightful

      If these devs are coding for obsolete systems that is their own damned fault, since if you'll look at any eTailer like Amazon or Tigerdirect the ones being sold with 2.x are the CCC (Cheapo Chinese Crap) that frankly won't run anything heavier thanks to low end CPUs and pathetic amounts of RAM!

      If the devs are really giving a shit about 2.x they may as well go write for Symbian feature phones, because THAT is who all these CCC pads and phones are marketed towards. I have no doubt I'll be picking one of those up for my dad, he just wants to try out the pad form factor and see how it fits him before getting a Transformer. Seeing as how the transformer is $500 with keyboard dock it'd be stupid to shell that out if it turns out he can't get used to the touch way of doing things so picking up some $89-$99 CCC makes sense, then if he likes the FF he can get the Transformer and hand the CCC to his GF who does nothing but FB all day anyway.

      So I don't see what the problem is, most devs I'm sure are writing apps that won't run on the low end ARM chips the CCC units running 2.x have anyway, so targeting that version would just be retarded. IIRC the first dual core units all ran 3.2, so I'd target that as a baseline and if they are running something so junky that it can't even run 3.2 then they really should get something that isn't CCC.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    3. Re:So? by AuMatar · · Score: 4, Insightful

      It's a combination of problems.

      1)Too many versions too quickly. 2 major releases (3.0 and 4.0) in too short a timespan

      2)Not enough work on backwards compatibility. If I use the 4.0 features, there's no good fallback. Java doesn't help them here- in C++ I could #define in 2.x and 4.x blocks, Java requires lots of reflection aware code because there is no conditional compilation. Or you need to set up special stuff with antenna and the like, which is hard to get working nicely with all the tools.

      2a)The backwards compatibility they do have is pretty broken. Unless the support library improved, it couldn't do simple stuff like make PreferenceFragments work like PreferenceActivities in 2.x very well. So as a dev I can't code to 4.0 and use libraries to emulate features.

      3)The ratio is still out of whack with more 2.x phones sold than 4.0. This is due to so few phones being upgradeable

      4)For whatever reason, I don't see a lot of open source stepping in to help this. On the PC, there's be open source libraries galore to step into the gap. On mobiles, not so much. I think the idea of easy monetization via ads (regardless of how much you actually make) has helped to kill the open source movement on mobile phones. Plenty of free help out there, but not much in the way of quality libraries. But these are the people who generally would be jumping on new features. Without them, its mostly commercial devs and they just want to target the mass market.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    4. Re:So? by symbolset · · Score: 3, Insightful

      Last Christmas it was only 700,000 units per day - and it was the holidays. June was but 3 months ago, and it was only 900,000 then. Now it's the off season and 1.3 million per day. With a ramp to holiday volumes we could see a 3x year over year increase. I would say that Android is still seeing considerable growth.

      Just Android's increase in sales per day over the last three months is the entire market for the wildly successful iPhone. Nearly 100% increase in just nine months, from an immense base. This sort of growth is supposed to not even be possible. At some point sheer volume dominance kicks in, and the thing becomes hard (but not impossible) to displace.

      I don't know what you think good growth is, but if this ain't it everybody else in the smartphone industry is toast.

      I like ICS just fine on my Transformer I bought on launch day, but Gingerbread works just fine on my 2 year old phone. At renewal time I'll get a phone with JellyBean. In the meantime, all the apps I like work great on both.

      --
      Help stamp out iliturcy.
    5. Re:So? by fm6 · · Score: 3, Interesting

      Oh please. It's the developer's fault that most people don't want to spend $500 for a phone?

    6. Re:So? by Octorian · · Score: 2, Interesting

      1)Too many versions too quickly.

      Thus is life in the mobile world...

      2)Not enough work on backwards compatibility. If I use the 4.0 features, there's no good fallback. Java doesn't help them here- in C++ I could #define in 2.x and 4.x blocks, Java requires lots of reflection aware code because there is no conditional compilation. Or you need to set up special stuff with antenna and the like, which is hard to get working nicely with all the tools.

      This is something I have far too much experience with from the world of BlackBerry. I've done both preprocessor hacks (which is supported by the build tools, but Eclipse hates), and fancy crap with libraries/pseudo-reflection/design-patterns (which lesser developers might cringe at figuring out). Either way, its not fun. It basically means that you have to use any new features "by exception", versus "by design", which makes it very hard to fully leverage them if the intent is to make your life as a developer better.

      3)The ratio is still out of whack with more 2.x phones sold than 4.0. This is due to so few phones being upgradeable

      Or due to carriers not bothering to push updates, when the vendors have. Or due to users not knowing/caring that they should upgrade. Or due to people clinging to their ancient phones and developers having a hard time justifying cutting them off if they want to maximize adoption. Regardless, having so many players between "OS upstream source" and "end user's device", you're pretty much doomed to this problem.

      4)For whatever reason, I don't see a lot of open source stepping in to help this. On the PC, there's be open source libraries galore to step into the gap. On mobiles, not so much. I think the idea of easy monetization via ads (regardless of how much you actually make) has helped to kill the open source movement on mobile phones. Plenty of free help out there, but not much in the way of quality libraries. But these are the people who generally would be jumping on new features. Without them, its mostly commercial devs and they just want to target the mass market.

      On the PC, you also have continual upgrades to common libraries separate from the whole OS, and sometimes even multiple versions of libraries installed. Additionally, the upgrade cycles of the hardware are almost completely separated from the upgrade cycles of these libraries. (at least in relation to the time scales we're talking about)

      I also agree that the mobile business models have greatly discouraged open source. Its quite frustrating, too, since it places far more burden on the shoulders of the platform vendor to provide everything. There's also this idea that you're supposed to try and make money off any and every mobile project. Regardless of how likely you are to actually succeed, you're looked down upon if you don't at least try. And often trying, means your effort isn't going to be open source at all. (Personally, I'd rather make something open-source and gain the community benefits than try to make an insignificant pittance off it as closed-source. If I'm closing something down, its because the monetary benefit is real and not imagined.)

    7. Re:So? by AuMatar · · Score: 5, Interesting

      And sadly, I don't think that the platform vendor is keeping up. I've recently started heavily writing my own reusable components, with the idea of spitting out a lot of small easy apps (to try and force myself to think in those terms, since I usually dream up giant multi-month efforts). Some of the things I had to write myself were ridiculously common, yet every damn dev is writing their own.

      *Splash screen (and side note: the tutorials I found on the web on how to make one were all horrible, involving spawning threads and making sleep calls).
      *Intents to just play full screen video, or audio and matching image.
      *An Image widget that can use a resource or a URL as the source.
      *A wrapper around their gyroscope and accelerometer to form a compass sensor. Something they used to have (ORIENTATION_SENSOR) then deprecated.
      *A single function call method to get a URL as a string (or as an image, etc).
      *A view that displays the output of the camera, and manages requesting access to the camera when the activity is paused/unpaused. Really, how the hell did they miss this?
      *A JSON parsing library that will take JSON and an object definition and use reflection to turn the JSON into a java object.

      Really, most of these are extremely common. Most aren't that hard, only the compass took significant time, and that because I needed to figure out the linear algebra and then clean up the sensor data. But google isn't providing it, and there aren't any good common Android libraries so everyone is rewriting most of these. And sure, some of these have limited use, but there's still ridiculous amounts of time being wasted by rewriting these thousands of times. Give us better tools to get out jobs done quickly, and we might have time to play with more advanced features.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    8. Re:So? by fm6 · · Score: 4, Insightful

      Most developers are using a API that was supposed to be phased out 2 years ago, and most new phones still have that same 2-year-old API? How is that not stuck?

    9. Re:So? by gl4ss · · Score: 2

      no conditional compilation, but you can have conditional execution.
      also some of the ui things have actually backports/compatibility packages to 2.3.

      it really isn't that big of a deal, really. if it were 2.0 or earlier that was dominant, that would be a problem.

      anyhow, in mobiles cheap "1 generation behind" phones are _ALWAYS_ sold twice the amount of the newest thing(even apples previous models have actually made up a significant portion of their sales..). why? because people like cheap.

      --
      world was created 5 seconds before this post as it is.
    10. Re:So? by rasmusbr · · Score: 2

      Speak for yourself. I like a having a hackable smartphone or tablet that lives outside the Apple walled garden. I do not like that developers are being forced to code to an API that Google froze as obsolete almost two years ago. Nor do I like the fact that a few braver developers are writing cool apps for the current API, but IU can't run them because phones I can afford are stuck on Gingerbread.

      Android phone sales may be fine now, but technology is a grow-or-die marketplace. No matter how well it's doing now, Android doesn't have a future if it's stuck like this.

      Okay, but your first and second paragraph seem to be in opposition to one another. The reason why there are two popular API:s, one which you can't afford to buy hardware for, is that technology is a grow-or-die marketplace. Growing pains are growing pains.

      You'll probably find cheap 4.x phones in Q1 2013. If you're more than a hobby developer and you can't get your hands on the latest tech then it's your boss who's to blame, or your own planning if you're freelancing.

    11. Re:So? by Instine · · Score: 2

      but it's not behind. It has grown. Ahead of the market. It's waiting there for the market. The market is what is slow (comparatively) here. I have a Google Nexus One, running Android 2.2. Some years old now. It is still a miraculous little tool. I have no need to upgrade. In fact I have an iPhone4 and never (literally, other than to check what it did) used it. The iPhone is heavier, shorter on battery life, and I can't swap out the battery and so carry multiple with me. I regularly use my 'old' Android for sat nav, playing mp3s when working, buying music, streaming music to my livingroom media player, controlling my TV and media player on my media box, finding places, finding new places, taking pics and video (many hours worth), checking Facbook, looking shit up, playing games, reading books, as a recipe book, as a cooking timer, as a third screen when coding, and as a dog training tool, a torch, texting and phoning. And skyping. And a tape measure. And translation device, spell checker, wireless keyboard and trackpad for my media playing pc, and internet radio player. In car media player and hands free device. And wifi hotspot provider for when I'm out and about with my laptop.

      But I'm not a power user! I don't need the 8 cores on the latest devices, to do all that at once - and screen in screen video playback for multi tasking that await in Jelly Been. I'm not sure I know anyone who does. The only thing I ever wanted that it didn't have was host mode for USB, so I could control robots with it via micro usb. But I never have time for that anyway...

      --
      Because you can - or because you should?
    12. Re:So? by Tapewolf · · Score: 3, Funny

      Oh please. It's the developer's fault that most people don't want to spend $500 for a phone?

      Yes. Doom got people buying £500 PCs, so clearly they aren't trying hard enough ;-)

    13. Re:So? by MagusSlurpy · · Score: 5, Insightful

      There's no real problem, this is just clickbait hype. Phones are lasting longer than 2 years, and normal people don't upgrade their OS. That's being spun as an issue.

      No, the issue is that the manufacturers and carriers aren't upgrading the software. I bought my phone in January, it was released last October, eleven months ago, and the manufacturer (HTC) says it won't push ICS, and my carrier has been mum. I could install the alpha build of CM9 on it, and give up video recording and get "wonky" camera operation (according to the single dev on the project) - but I like having a camera on my person all the time.

      THAT'S the damn problem.

      --
      My sister opened a computer store in Hawaii. She sells C shells by the seashore.
    14. Re:So? by thegarbz · · Score: 2

      Android phone sales ARE the way forward. There's two issues here, a) manufacturers / telecom companies not providing timely updates, and b) end users simply not giving a damn. There are MANY people in these categories. Most Android users don't connect their phones to a computer and are never actually aware that an update is released. More importantly until [killer app] fails to work on their phones due to an obsolete OS issue the phones do everything the end user wants, what's the incentive to upgrade?

      Sure I'm a geek. I need to have the latest and greatest. But the vast majority of these phones are in the hands of 15 year olds, business people, and other luddites. To them they own an appliance, not a computer that fits in their hand and needs software upgrades.

      In any case for most of the world where these handsets are on a contract, in two-three years depending on the duration of said contract the users will often end up with the latest and greatest OS anyway.

      I really don't see the problem.

    15. Re:So? by jeffmeden · · Score: 2

      It's a combination of problems.

      1)Too many versions too quickly. 2 major releases (3.0 and 4.0) in too short a timespan

      3.0 was released as a tablet-specific OS. The next handset OS after 2.3 (gingerbread) as 4.0 (ice cream sandwich). Talking about the "problem" with no real knowledge of it, is um, a PROBLEM.

    16. Re:So? by TheRaven64 · · Score: 2

      Java requires lots of reflection aware code because there is no conditional compilation.

      Well, kind of. There is no preprocessor (although you can, of course, run Java code through the C preprocessor before compiling if you really want to, or through some other text processing system), but you can conditionally compile different versions of the same class, so you can implement shared functionality in a superclass and pre-target functionality in a subclass and then just compile the correct subclass for your target.

      --
      I am TheRaven on Soylent News
    17. Re:So? by AmiMoJo · · Score: 2

      It's a bit more complicated than you seem to think. Most phones consist of parts from many different manufacturers, and they all need to have stable ICS drives for the phone to upgrade. The cheaper the phone the more likely that it has some random and old Broadcom chip or TI radio that has long since been replaced with a new and more expensive model.

      Sure, sometimes Cyanogen proves that it is just the manufacturer being lazy, but once again it comes down to cost. If the manufacturer has to factor in upgrading and re-testing the phone a couple of years after release into the cost of the phone.

      The reality is most buyers and most developers don't care. Buyer gets a cheap smartphone with a large number of apps (including essentials like Angry Birds, a fake cracked screen, whiplash sound effect, Facebook client and so forth). For developers the Gingerbread API was pretty complete and the new stuff is mostly related to features that older phones don't have anyway, so most apps either don't care or are only targeting high end high performance phones anyway. In some ways it actually helps because a developer can release different versions for Gingerbread and ICS, each with features more suited to the types of phone that run them.

      It isn't perfect but it is hardly the terrible problem that some people make it out to be.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    18. Re:So? by JackieBrown · · Score: 2

      Another big problem is closed drivers. That is what is preventing my evo 4g and nook color from upgrading

      I can upgreade to icecream and jellybean for the evo 4g but then I loose 4g and video acceleration (netflix.) Same video problem with the nook. This is not the devolpers fault - in fact it is amazing how well they are doing porting new versions.

    19. Re:So? by DJRumpy · · Score: 4, Insightful

      It's also not the developers fault that they target the dominant version of the OS. Google dropped the ball. They should have made an upgrade path easily available to their users (and by users I mean end users, not handset manufacturers).

      Apple got this one right. It takes no skill to click an 'update' button. Hell it even prompts you that an update is available. Plug it in and your phone is updated in 15 minutes with a single click.

      The current method of relying on handset vendors to provide updates to Android handsets where there is no profit margin for them to do so is broken. Why provide updates when you can get this shiny new phone with a newer (yet obsolete) version of Android? The technical folk can upgrade but the masses are stuck with obsolete and potentially vulnerable versions due to neglect.

    20. Re:So? by sjames · · Score: 2

      I have to take exception to ' people clinging to their ancient phones'. Two years is nothing like ancient. It's not even close. I know a lot of corporations would like to see a hyper consumer culture where people buy buy buy and then throw it away as soon as they get home because it became 'obsolete' within the 10 minute trip, but that's not terribly sustainable.

      You are free to use nothing but the latest, greatest and the bleedingest edge if you like and you are free to code to nothing but the latest APIs if you like, but the fact is that a lot of people are doing just fine with their 2 year old phone and a lot of developers managed just fine writing apps to that API. I'll bet a lot of those 'ancient' phones aren't even out of contract yet (but soon will be).

      As for the carriers, I agree. If the device can support the update, it should be available. If they don't want to bother, they should unlock the devices and make it easy for people to do the upgrades themselves.

      But as a whole, if it ain't broke, don't fix it.

    21. Re:So? by sjames · · Score: 2

      ICS came out less than 1 year ago. Honeycomb was never meant for anything but tablets, so phones COULDN'T update to that. So, the API you're complaining about most certainly was NOT supposed to be phased out 2 years ago. It couldn't even START to phase out until 11 months ago.

      Meanwhile, Gingerbread is NOT 2 years old until December.

      So to recap, we're 'stuck' because a 1.5 year old API hasn't yet been scrubbed from the face of the Earth?

    22. Re:So? by SomePgmr · · Score: 3, Insightful

      Absolutely agree. Developers just go where the people are. People are largely at the mercy of manufacturers and carriers who can take years to release a single update. And even when they do, there's often no notification to the end user that a new version is out.

      And you're absolutely right about Apple having this part nailed. iTunes handles all that quite nicely. Of course Apple only has to deal with 4 or 5 models. I expect Google knew they couldn't manage safe rollouts on an infinite variety of devices, which is a fair assumption.

      End result is Android phones in general just don't get updates. Not in any meaningful way that you can count on. People all have to go buy new phones before you can change your minimum target API.

    23. Re:So? by hairyfeet · · Score: 2

      But as another poster said you're missing the forest for the wood. the question is WHY aren't they updating? The answer is simple, these units are CCC which means the thinnest of razor thin margins, which makes it simply not financially feasible to update most of these things, if there are even drivers for the older/shittier chips these units use.

      Here is a perfect example of what I'm talking about which is VERY popular here BTW. We are talking about a $135 Android smartphone, runs 2.3, and service is $50 a month for unlimited everything. You see these things all over the place here, there is no contract, the web surfing is good, it has a nice selection of built in apps. No do you REALLY think they are making enough profit on a $135 no contract phone to make paying devs to update it worth the expense? Hell I bet the users don't even fricking download or buy apps from the market, instead just using what came with the phone!

      This is the little secret nobody wants to admit here, that the reason Android is stomping iPhone is that for every $500 Android phone you have 30 of the $135 models being sold. Sure that means a lot of Android users, but those users are using it as a cheap feature phone NOT as a true smartphone. they aren't downloading or buying apps, they don't care about updates, as long as the stuff that comes with the phone works they are happy little campers.

      Don't get me wrong, I've tried a friends unit and it does what you'd want a basic phone to do, surf, email, music, its not a bad phone. But one shouldn't be surprised that phones like that simply aren't getting updated, Android has simply taken the feature phone market Symbian used to have with 2.x, that's all.

      --
      ACs don't waste your time replying, your posts are never seen by me.
  2. Sorry guys by OrangeTide · · Score: 4, Insightful

    But I paid hard earned money for my phone. I'm not ready to buy a new one yet. Now maybe if more Android phones were upgradeable to newer operating systems, I might run some newer software on my phone.

    --
    “Common sense is not so common.” — Voltaire
  3. Uhm, CM 7, 9 and 10 by Anonymous Coward · · Score: 3, Informative

    http://www.cyanogenmod.com/devices

    You have to root and upgrade yourself, but the devices can handle it just fine. So back to lazy phone carriers not working with device manufacturers on year old handsets.

    captcha: suspend

    1. Re:Uhm, CM 7, 9 and 10 by txoof · · Score: 4, Informative

      CyanogenMod breathed a whole new life into my 2 year old Nexus one. It was snappier, appeared to get battery life and had a whole host of awesome new features. The only reason I finally upgraded to a newer phone was because the power button broke (again!) and the headphone jack wore out. If you're sitting on an older Android device, consider trying CM. It really turns your phone into a geeksphone.

      --
      This one's tricky. You have to use imaginary numbers, like eleventeen... --Hobbes
    2. Re:Uhm, CM 7, 9 and 10 by the_humeister · · Score: 2

      Agreed. I have an LG Phoenix (aka Optimus One). It is rather underpowered (ARM11 processor is very slow). I found a CM10 rom and put it on. Sure enough it works, and works well - just as snappy as Android 2.1 that it originally shipped with.

  4. Don't fix it if it ain't broke by flyingfsck · · Score: 3, Insightful

    Why mess with a good thing? Most users do not need or want to upgrade. If the phone works, then an upgrade presents real danger of making it worse, not better.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
    1. Re:Don't fix it if it ain't broke by raptor_87 · · Score: 2

      The users generally don't have a choice. Eg: a number of Motorola phones released in 2011 (Droid 3, Droid X2) will never see ICS, and while most released in 2012 will, the upgrades are still being rolled out. https://forums.motorola.com/pages/00add97d6c

    2. Re:Don't fix it if it ain't broke by Bert64 · · Score: 2

      As a developer you should realise that piracy is inevitable, and that the vast majority of attempts to forcibly prevent piracy have only served to irritate or discourage legitimate purchasers.

      So instead of trying to drive more of those who would be willing to buy your apps towards piracy, use the pirate copies as advertising and try to drive the pirates to become paying customer by offering them compelling reasons to do so?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  5. android 3.0 by ganjadude · · Score: 2, Interesting

    honeycomb is only for tablets, not cell phones, so it makes sense. Blame the cell carriers/ 3rd parties for the holdup 4.0 is not even being rolled out to some 90% of phones that are already out there, therefore it only makes sense that 2.3 is the dominant flavor

    --
    have you seen my sig? there are many others like it but none that are the same
  6. What are the min requirements for Jelly Bean? by 93+Escort+Wagon · · Score: 3, Interesting

    I've been assuming the reason there are lots of 1.x and 2.x phones out there just had to do with the fact there are a lot of low-end Android phones for sale. I figured ICS and JB had fairly stiff hardware requirements. Is that not correct?

    --
    #DeleteChrome
    1. Re:What are the min requirements for Jelly Bean? by Zuriel · · Score: 2

      4.0 and 4.1 don't have very harsh CPU/GPU/RAM requirements, the big problem is storage space.

      4.0 uses significantly more space than 2.x so it's complicated to upgrade a lot of phones. Even if the phone has plenty of internal flash you might only have a 512MB system partition, so upgrading means re-partitioning flash to allocate more space to the OS, which is apparently too difficult to do as an OTA update.

      With Cyanogenmod I believe you can use a custom bootloader to wipe and repartition then load the 4.x OS image onto the blank phone over USB.

  7. There's not a lot of incentive to update by Linsaran · · Score: 4, Insightful

    On the consumer side, 90% of smart phone customers don't use even 15% of what their devices are capable of doing. For most consumers, the questions, "Can it go online?", "Can it make phone calls and send texts?", "Does it have some stupid little games I can put on it to pass the time when I'm bored?", and "Does it work reasonably well without being too confusing for me to figure out" are all they care about. That functionality has been available long before android 2.3 even hit the scene, never mind 4.0.

    The average consumer doesn't understand nor care about the differences between OS versions on really anything, computers, smartphones, whatever. As long as it does that one thing(s) that they want, most are satisfied. Now if they're exposed to a new feature from a new version they might grow to like it and use it, but chances are unless they're already a techie and looking into that sort of thing, most users won't care about it until there's some game/app/thing they want to do with their current device/OS and can't. Plus, unless they happen to be fairly tech savvy and aren't afraid of voiding warranties and what not the consumer is at the whim of their device manufacturers and carriers to get them updated software. So it's no surprise most people just stick with what they have if it works 'good enough'

    From a manufacturer point of view they've already sold the product, maintaining updates costs them money, so they're disinclined to spend money on a product that's already sold. There's some work done on flagship products, and maybe a little bit just to earn enough goodwill with their customers that they'll keep coming back, but like all corporations they balance expenses for 'customer service' very carefully. For most corporations, customer service isn't about doing what's right for the customer, it's about doing enough to keep most of the customers happy, but not cost the company a fortune.

    There's a little more incentive on the carrier's end to keep things updated, since their customers are paying for a service, not for hardware, and I'm sure that there's some push from the carriers to get their devices updated. But even then that costs money, so it's really only going to be their most popular devices that get attention, and less popular ones will fall by the wayside.

    Tl;dr most people figure if it ain't broke, don't fix it

    --
    In a bit of shameless internet panhandling, I accept Litecoin Donations at Lbd2oH9QsthD1GfuUXPyka12YxvWJYnBVf
    1. Re:There's not a lot of incentive to update by gutnor · · Score: 2

      That's where Apple got it right with the marketing. They advertise new features that us geek consider not worthy of even talking about. However, as you said Joe User does not care about the OS or what it can do unless it has been demonstrated to him and Apple ads, as silly as they are, just do that.

  8. Limited hardware supported, not by vendor themself by dutchwhizzman · · Score: 4, Insightful

    Cyanogenmod is available for maybe 25% of android devices sold in models, probably less than 10% in number. For my android device, there are severe trouble with the phone/wifi firmware (wifi sometimes doesn't work when you have a SIM inserted) and camera (not supported by native camera app). There is no support for that from the CM team since it's an unofficial port and obviously, the hardware vendor and telco don't support it either.

    Apple supports firmware updates including full hardware support for about 3 years at least. You may not always get all new features, but at least you get the security updates. Google does not mandate any such term from their vendors, they are fine with "fire and forget". In practice, this makes devices with the same quality and features in hardware less worth if they're not running iOS. You may not want to spend iOS money on a device, but if you have to add in the security risk and frustration about the lack of support and McGyvering you will probably be subjected to, the price difference may suddenly not be that big anymore.

    Android vendors get away with putting on their own "improved" UI, which usually isn't that much of an improvement, but makes it harder for people to switch phone because the UI is different. There's no signature "it works this way and looks that way" OS on Android phones, making it harder to market them.

    If Google wants to really get ahead, for Android 5 they should mandate 3 years upgrade support from vendors and telco's (within 1 month after general release) and no customization apart from optional addons that can be switched off by the user. People that spend a lot of money on a device or a "sponsored" telco deal should be able to enjoy their device a whole lot better and marketing the devices would be a lot easier as well, making it more justifiable to pay top dollar for such a device.

    --
    I was promised a flying car. Where is my flying car?
  9. Still 2.3 for sale by dutchwhizzman · · Score: 2

    Probably, in numbers, the amount of devices still sold with Android 2.2 and 2.3 is still higher than the amount of devices sold with 4.X. Even tablets are usually sold with either 2.X or 4.X, not with 3.0. So no, it doesn't make sense, new devices are being sold in the millions with known vulnerable software on them.

    --
    I was promised a flying car. Where is my flying car?
  10. More upgrades available via PCs by whoever57 · · Score: 4, Informative

    My Galaxy S2 got an update to 4.0, but it wasn't available OTA, only by connecting the phone to Samsung's KIES software.

    My wifes's Motorola phone got an update to 2.3 just a couple of month's ago (yes, 2.3, not 4.0), but again, it wasn't available OTA -- only by using Motorola's software on a PC.

    --
    The real "Libtards" are the Libertarians!
  11. Re:Limited hardware supported, not by vendor thems by Hadlock · · Score: 2

    Google sells bare phones direct to consumers. Really good, well supported models with lots of high end features. Consumers have the choice to buy these, or defer the large upfront cost of the phone over a year by paying higher monthly rates. I've had my Nexus S for almost three years and it's paid for itself (actually I'm about $60 ahead at this point) by choosing a plan that reflects my up front purchase cost. Telcos are taking advantage of lazy consumers, but there are also competitors in the market who are serving more informed consumers. There's nothing to worry about here.

    --
    moox. for a new generation.
  12. May I say... by zephvark · · Score: 2, Interesting

    could they stop naming the operating system to appeal to six-year-old girls? That is probably not their best target demographic.

    1. Re:May I say... by MachDelta · · Score: 2

      It's all named after (alphabetical) delicious treats, man. What's not to like? Oh, and just wait until the next major release - Key Lime Pie, mmm mmm!

  13. Re:Poor support from Carriers and Manufacturers by stephanruby · · Score: 4, Insightful

    "Three major revisions of Google's Android operating system have launched..."

    Really? I thought it was just one major revision.

    "Android 3.0" was for tablets only. Perhaps, they should just have called it "Android 2.0 Tablet edition", which was really what it was. Take "Windows XP 32bit" users for example, it's not like they complained when "Windows XP for Netbook" came out, or when "Windows XP 64bit" came out.

    And Jellybeans is just Android 4.1. That's not a major revision, that's a just minor one, hence the ".1" and the minor number of changes compared to Ice Cream Sandwich version - Android 4.0.

  14. Independent Builds for Older Phones by ilikenwf · · Score: 2

    While not officially supported, many phones have working, mostly working, or partially working builds of ICS and JB. I was on a Droid2 before I decided to get a Galaxy Nexus for the fact it has an unlocked bootloader, even over the SIII, but the Droid2 ran ICS like a top, though some hardware acceleration issues existed. The ICS build by some user on RootzWiki was still far better, smoother, faster, and had better battery life than the GB build that came on it by motorola.

    See XDA and RootzWiki with your GB phones, and see about getting a better build on there...of course, I roll my own anymore, and run JB on my Gnex, even though it's not been released yet officially for my phone (vzw).

  15. Have we lost control? by Knutsi · · Score: 2

    Perhaps the fact that we cannot ourselves (easily) update our tablets and phones says something about how much control we've lost on our devices? That scares me. If i buy one of the new style of laptop-tablet hybrid, can I expect the same? Will this not easily cut years of value off these things, and slow down the software ecosystem?

    I had an _expensive_ Window Phone. Then Microsoft told me I could not upgrade my 6 months old phone to WP8. I felt so cheated, and still do. I will never buy another. It is such a disrespect for the customer.

  16. Re:Just Curious by Kergan · · Score: 2

    I'm not aware of any data from Apple, but several devs publish their stats. Bloggers periodically aggregate the whole thing and make pretty graphs. Here's what things looked like last March:

    http://pxldot.com/18754186750

  17. These people are using 21 month old software!? by John+Hasler · · Score: 4, Funny

    Amazing! That's almost two years!! How can they stand to use anything so ancient?

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    1. Re:These people are using 21 month old software!? by PCM2 · · Score: 2

      Amazing! That's almost two years!! How can they stand to use anything so ancient?

      Mobile is a rapidly-developing technology market. Every phone I've owned has been significantly better than the last. What people are starting to understand, though, is that many of the improvements -- some of which are major -- can be delivered via software only. UI glitches in older versions would disappear ... if the carrier or phone maker would just deliver the new software. But they don't. Imagine if you bought a car, and then in the next two years they put out a new model that has the same engine, same transmission, same drive train, but different software in the onboard computer, and it gets 10 mpg better gas mileage. Wouldn't you want to get your hands on that software? Now imagine GM has put a system into your car that makes it impossible to upload the new software. Wouldn't you complain?

      --
      Breakfast served all day!
  18. Re:I would like an Android phone -- without the ph by thopkins · · Score: 3, Informative

    Samsung Galaxy Player.

  19. Re:Limited hardware supported, not by vendor thems by Hadlock · · Score: 3, Insightful

    I would buy an Android powered Blackberry curve in a second. I loved my Blackberry to death, but using it made me feel like I had an Apple II in my pocket, when everyone else had a sparcstation. Dat keyboard.... to this day I'm still slower (even with Swype, Swiftkey, etc... I've tried them all) on a touchscreen than I ever was on my physical keyboard blackberry. Sadly the only android phones that come with a physical keyboard are marketed towards teenagers and thus manufactured as one grade up from trash.

    --
    moox. for a new generation.
  20. Life in the mobile world is not optimal by Envy+Life · · Score: 2

    1)Too many versions too quickly.

    Thus is life in the mobile world...

    That's not how it should be. iPhone releases 1 phone per year, which includes 1 major OS upgrade to all prior phones of the past 2+ years (covering all carrier contract timeframes). All other mnaufacturers release so many phones that they can't keep up on software upgrades, and by the time that 1-2 year timeframe hits, that phone feels ancient. It's not exactly an optimal customer experience.

    As a customer I specifically make phone purchases based on the odds of getting new android updates. At first I thought Samsung would do it, they failed me. Then I thought HTC would, and they failed too. Now I'm back to Samsung, and frankly the situation is even worse... even the Google branded phones have serious upgrade lag. Manufacturers blame it on the carrier, carriers blame it on the manufacturer. In the U.S. anyway, I've resigned to a best case scenario of getting a single upgrade in the first 6 months of the phones existence then spend the next 18 months watching several new Android releases come and do without being able to experience any more upgrades until my contract finally expires. It's just a big stalemate.

  21. I'm running 4.1 on my Galaxy S by charnov · · Score: 2

    My phone came with 2.2 and I have upgraded all the way to the latest Jelly Bean. Here's a hint: only buy Samsung or straight from Google. Maybe Motorola will finally stop being jerks now that Google owns them and have an upgrade path, but my next device will be a Nexus 7 straight from Google.

    --
    [RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.