Last October, ARM founder, Tudor Brown hinted in a Forbes interview that the next version of Android will be called Ice Cream. Today, we have a second confirmation of this name choice courtesy of a rumor fresh from Pocket-Lint. According to the UK-based blog, multiple sources familiar with the matter suggest that Android 2.4 will follow Android 2.3 Gingerbread and Android 3.0 Honeycomb, the tablet version of Android. Keeping with Google's alphabetical naming convention, the next letter is "I" and what better name than ice cream, the sweet treat that everyone loves.
According to this latest rumor, this upcoming version of Android will be unveiled at Google I/O, Google's annual developer conference which is held each spring. Once announced, the mobile operating system will be released in June or July. Details on the changes included in this Ice Cream build were not revealed, but the OS is expected to bring some of the features of Android 3.0 honeycomb to the handset. Though Android 3.0 may arrive on tablets before Android 2.4 is even announced, it is thought that this Honeycomb version is for tablets only and will not make its way to smartphones.
This timing for this launch fits in with Google's current roadmap for future Android updates. After several quick upgrades, Google is expected to slow down the pace of upgrades and will release approximately two major revisions each year. As Google has done in the past, look for search giant to release this 2.4 version first to the Nexus S and then other carrier-branded handsets a few weeks or even a few months later.
Comments (48)
Reply3.0 > is tablets
2.x is mobile
Strange.
To be fair, iOS for iPhone =/= iOS for iPad. But Apple tries to align the features to the version (i.e., multitasking in v4 etc).
If they are going to make it something different than they should call it something different like Android TE (Tablet Edition) or something like that. 3.0 makes it seem like Android for tablets is newer than the version for mobile. What happens when they want to increment the mobile version by a whole number? Doesn't seem to make much sense to go that route. Its all just a bunch of version numbers though...no biggie. Companies tend to do what they want and nevermind the norm.
To be fair, iOS for iPhone =/= iOS for iPad. But Apple tries to align the features to the version (i.e., multitasking in v4 etc).
If they are going to make it something different than they should call it something different like Android TE (Tablet Edition) or something like that. 3.0 makes it seem like Android for tablets is newer than the version for mobile. What happens when they want to increment the mobile version by a whole number? Doesn't seem to make much sense to go that route. Its all just a bunch of version numbers though...no biggie. Companies tend to do what they want and nevermind the norm.
With iOS I'm pretty sure that from 4.2 forward the releases will be simultaneous. The apps running on the OS are different, but I think that the OS itself is the same now.
To be fair, iOS for iPhone =/= iOS for iPad. But Apple tries to align the features to the version (i.e., multitasking in v4 etc).
If they are going to make it something different than they should call it something different like Android TE (Tablet Edition) or something like that. 3.0 makes it seem like Android for tablets is newer than the version for mobile. What happens when they want to increment the mobile version by a whole number? Doesn't seem to make much sense to go that route. Its all just a bunch of version numbers though...no biggie. Companies tend to do what they want and nevermind the norm.
Google never has cared for doing version numbers correctly. Chrome is the perfect example.
Google never has cared for doing version numbers correctly. Chrome is the perfect example.
"Correctly"? Is there even a correct way? Version numbers are used by developers and marketing. Windows 7 is 6.1 although it "should" have been 7.0, but MS cared more for backwards compatibility for apps which only check for the "6" part, so that they won't get confused. And Apple even use letters in their strings, as in 10.6.5 Build 10H531.
If they are going to make it something different than they should call it something different like Android TE (Tablet Edition) or something like that. 3.0 makes it seem like Android for tablets is newer than the version for mobile. What happens when they want to increment the mobile version by a whole number?
I see where this is headed. odd numbers for tablets, even numbers for smartphones
"Correctly"? Is there even a correct way? Version numbers are used by developers and marketing. Windows 7 is 6.1 although it "should" have been 7.0, but MS cared more for backwards compatibility for apps which only check for the "6" part, so that they won't get confused. And Apple even use letters in their strings, as in 10.6.5 Build 10H531.
In both of your examples, higher numbers still meant newer versions. MS didn't go back and release an actual Windows 6.1 as a new product on the shelves after Windows 7 came out. While I realize there is a class of people on Neowin with a sort of spider-sense for whenever someone uses "Chrome" and "version" in the same sentence, and your hands were probably typing before you even realized it when you saw a post pointing out Google's handling of Chrome's version numbers, it's still a valid observation when it comes to Android.
3.0 > is tablets
2.x is mobile
Strange.
Who cares about version numbers??
Even numbers for phones, odds for tablets? I could see that.
In both of your examples, higher numbers still meant newer versions. MS didn't go back and release an actual Windows 6.1 as a new product on the shelves after Windows 7 came out. While I realize there is a class of people on Neowin with a sort of spider-sense for whenever someone uses "Chrome" and "version" in the same sentence, and your hands were probably typing before you even realized it when you saw a post pointing out Google's handling of Chrome's version numbers, it's still a valid observation when it comes to Android.
Perhaps. But the original point about Chrome is void.
yeah cause having support is a bad thing??? not sure why you hate this?
yeah cause having support is a bad thing??? not sure why you hate this?
I think he meant don't
I think he meant don't
Yup thats what i mean, i cant edit my original post.
Android Team at google must smoke a lot of ganj...their OSes are all named after foods.
You are perceptive.
Google are on fire! 2.3 was only released a little while ago and now 2.4 not far away! My trusty HTC Desire is gonna be 2 versions behind soon
oh the rapid pace of the IT industry...
I've had my Android phone for about a month. When I bought it, it was on version 2.1. 2.2 had been out for months and 2.3 had already been announced.
Now 2.4 is being talked about, and where am I? I would still be on 2.1 (2.2 still isn't available to me apparently), but I've moved on to custom ROMs. It's the only downside I can find with Android so far, the lack of consistency when it comes to across-the-board updates.
Thats where we blame the OEMs and carriers. They take ages to update the latest build with their custom software and as a result don't update their phones often (or even at all for some).
This has also put me off Android. Luckily I too use custom roms. There's no chance in hell am I waiting for Google to release the code. Then wait for HTC. Then wait for my phone company to brand and release it OTA.
Personally I won't be using Android again when my contract is up. Steve Jobs is kinda right with the whole fragmentation thing. Over time I can only see the same happening to Windows Mobile 7.
Personally I won't be using Android again when my contract is up. Steve Jobs is kinda right with the whole fragmentation thing. Over time I can only see the same happening to Windows Mobile 7.
One of my favourite things about the iPhone is the software updates and how easy it is to get them when they are released, I use to use windows mobile before moving to an iPhone and you could also go to xda devs and get new roms and flash the phone over and over again. But seems I spent ages trying to locate the fastest/most stable rom. Android seems to be heading down a similar path. Still great phones thou.
Personally I won't be using Android again when my contract is up. Steve Jobs is kinda right with the whole fragmentation thing. Over time I can only see the same happening to Windows Mobile 7.
This is also my main gripe with Android, I know Google is trying to promote "freedom" and "openness" but the carriers/OEMs are holding us hostage and forcing us to "root" our devices just to update them! I too am seriously considering not getting another Android phone because of that.
This is also my main gripe with Android, I know Google is trying to promote "freedom" and "openness" but the carriers/OEMs are holding us hostage and forcing us to "root" our devices just to update them! I too am seriously considering not getting another Android phone because of that.
I feel like it was mentioned that, even though Microsoft would be handling updates, they would be pushed to carriers, not users, who would then decide if/when they would let them through to us.
I was really put off when I read that, because I too felt like MS was going the correct route with centralized updates (I'll take a walled garden over shiny happy open principles if I ultimately win as a consumer, tyvm). We'll see what actually happens when the huge update comes out for WPOS later this year. Hopefully MS will be more Apple than Google with this.
Still would like a hardware accelerated UI, possible battery improvements. But nooooooo.
Hmm, maybe 2.4 and possibly 2.5 will move in the direction of converging the 2.x and 3.x lines. Then like with iOS there will be a 3.x release at some point in the future that is for all devices.
Definitely an interesting version number situation.
Who the hell said that 2.4 is "Ice Cream"? Who the hell are these sources, considering half of what they say is complete BS.
Exactly. This is plain silly.
They are /not/ going to release Honeycomb 3.0 and then Ice Cream 2.4 - it's just retarded and ridiculous.
Exactly. This is plain silly.
They are /not/ going to release Honeycomb 3.0 and then Ice Cream 2.4 - it's just retarded and ridiculous.
Of course I'm referring to the version numbers! lol, I know google names its versions after desserts following the alphabet...so it makes no sense whatsoever to release the /next/ version of Android (Ice Cream) but associate it with a /lower/ version number.
If you watch Engadget's interview with the lead UI designer, Honeycomb is meant to be scalable to phones. All the features in Honeycomb should transfer to phones if a manufacturer wants it like that (e.g. the new multitasking method). I just cannot believe they're going to achieve this by having different versions of Android for phones and tablets.
Exactly. This is plain silly.
They are /not/ going to release Honeycomb 3.0 and then Ice Cream 2.4 - it's just retarded and ridiculous.
A SonyEricsson Arc already leaked running Android 2.4. It was on the front page of multiple tech sites.
Exactly. This is plain silly.
They are /not/ going to release Honeycomb 3.0 and then Ice Cream 2.4 - it's just retarded and ridiculous.
A SonyEricsson Arc already leaked running Android 2.4. It was on the front page of multiple tech sites.
*facepalm* go read engadget. That was a mistake on Sony Ericsson's part. It should have said 2.3.
@hdood: er, no. that's like saying they should release 1.6x updates because 2.1 has higher requirements. yes, 3.0 will have higher requirements...all that will mean is that if manufacturers want to use it, they'll need to provide better hardware. which is going to happen anyway. if they don't, they'll just stick to 2.3.
just my opinion anyway, and i'll eat my hat if i'm wrong.
Excuse me for not noticing every single update all of the time. Some of use have other things to do in life as well.
Sounds like a branch split? Oh noes!
Great, yet another update my HTC Legend won't most likely ever receive. Just lovin' Android...
Then switch or suck it up and root your phone. Its not hard and you can always unroot it and bring it back to stock later on.
I have been running a stable, FAST, solid FROYO ROM for a long time. Works just as good as the offical FROYO does and it is a true FROYO kernal. Plus the file system is now EXT4 and my phone is twice as fast...at least.
First of all, don't tell me what to do okay? Okay. Second, I'm not rooting my HTC Legend for some custom ROM that will always ask me to give up on something. I didn't pay good money for a phone so I can turn it into my own tinkering project, with the potential danger of bricking the thing in the process.
And yeah you're spot on, I'm extremely unlikely to get another Android phone this year. It's either going to be an iPhone or a Windows Phone 7 phone. The latter depending on if 6 month old devices are deemed too old to receive updates as well.
Note that I'm not blaming Google for the above, but purely HTC. If the company is unable to keep up with the 15 billion different phone models they put out, they should either hire more people or keep their line-up in check. However, looking around it doesn't seem like other vendors are doing a much better job.
Bit touchy eh....
Okay. Second, I'm not rooting my HTC Legend for some custom ROM that will always ask me to give up on something. I didn't pay good money for a phone so I can turn it into my own tinkering project, with the potential danger of bricking the thing in the process.
Give up on what? I gain more with rooting and have not given up any features/apps/anything. and rooting is basically fool proof and not a big PITA as it used to be.
I have to give up on Sense and all of the widgets I use frequently. Beyond that: One custom build Android ROM will ask me to drop bluetooth functionality, the other has issues with the camera, another one craps out on automatic brightness etc. etc. Contrary to what you might think I did look into custom ROMS and decided against it for the above reasons.
At this point there's something fundamentally wrong with how third-parties are handling Android updates. In most cases vendors create way too many different phones and create a situation where they are unable to keep up with their own hardware. In other cases companies apparently feel like a 6 month old phone simply isn't worth it anymore. And it's not even about having the latest and greatest features. The HTC Legend's messaging app was unusable for four months because HTC refused to put out a interim bug fix release.
I'm hoping things will go down differently with Windows Phone 7.
I have to give up on Sense and all of the widgets I use frequently. Beyond that: One custom build Android ROM will ask me to drop bluetooth functionality, the other has issues with the camera, another one craps out on automatic brightness etc. etc. Contrary to what you might think I did look into custom ROMS and decided against it for the above reasons.
At this point there's something fundamentally wrong with how third-parties are handling Android updates. In most cases vendors create way too many different phones and create a situation where they are unable to keep up with their own hardware. In other cases companies apparently feel like a 6 month old phone simply isn't worth it anymore. And it's not even about having the latest and greatest features. The HTC Legend's messaging app was unusable for four months because HTC refused to put out a interim bug fix release.
I'm hoping things will go down differently with Windows Phone 7.
Continue hoping and you will be disappointed. HD2 has never received any updates from MS, either to the latest WM 6.5 nor the WP7. I had to root it to get all the updates that were MEANT for the phone...
Then switch or suck it up and root your phone.
This attitude needs to crawl into a hole and die. It's bad for users, it's bad for Google, it's bad for the market, and it's bad for technology. A platform that makes it harder in the name of principles won't win against something that's just plain easier for the consumer. The consumer doesn't care about principles.
Not to mention, not every Android phone has access to the latest versions of the OS, even with rooting. Android handsets are NOT x86 PCs. It is 100% impossible today for, say, an Epic 4G owner to install Gingerbread. Even Cyanogenmod hackers aren't guaranteeing access to 4G with their builds of *Froyo*. These aren't obscure phones that were ditched by OEMs and failed by hackers like the Samsung Moment or anything that isn't HTC (a brand that, even when it's more difficult to hack than others, gets hacked because of some weird love affair XDA has with it).
Motorola phones, Samsung phones--flagship Android phones are simply unable to run Gingerbread. You do not root your phone, download google.com/android/gingerbread.zip and magically have the latest version. Nobody is doing this. Stop pretending it's the reality of Android. It isn't.
This is a major flaw with the platform, and every time someone jumps out and says it doesn't exist if you root your phone, people read it, believe it, and flood XDA forums with idiotic posts asking why they can't install 2.3 yet. It needs to be addressed, and HTC's hardware isn't impressive enough for long enough to tell users to only buy that brand. Sorry.
Sorry, wrong post.
I have to give up on Sense and all of the widgets I use frequently. Beyond that: One custom build Android ROM will ask me to drop bluetooth functionality, the other has issues with the camera, another one craps out on automatic brightness etc. etc.
I do agree that a lot of custom ROMs break a lot of things; many of which you just mentioned. However, you always have the option of running a stock rooted ROM (includes Sense), which is exactly like the stock ROM, except that it is rooted, allowing you to change just about anything.
This is a major flaw with the platform, and every time someone jumps out and says it doesn't exist if you root your phone, people read it, believe it, and flood XDA forums with idiotic posts asking why they can't install 2.3 yet. It needs to be addressed, and HTC's hardware isn't impressive enough for long enough to tell users to only buy that brand. Sorry.
I agree this is a problem, but whose problem exactly? Is it Googles? I doubt it, they just make the software, it's up to other factors whether it gets pushed to other devices.
Also: http://www.xda-developers.com/...ur-frequently-updated-list/ expect some stables
Does Google condone licking Ice Cream?
My Dell Streak came with doughnut, skipped Eclair, put Froyo on it, Gingerbread is next, then Honeycomb, then Ice Cream?
Does google work in a deli??? LOL
i like how the codenames are appropriate for the time of year, at least in the northern countries
like, summer last year you had Frozen Yoghurt, come winter you had Gingerbread, and summer this year you will have Ice Cream ....
They're preparing to announce 2.4 already? I do admire Google's rate of development with Android but there are inherent issues with this breakneck rate; the fragmentation of Androids share of the market becomes more and more significant.
There are still loads of devices on sale in the stores now running 2.1 with one and even two year contracts attached to them with little or no hope of being updated. Even Google themselves haven't bothered to port the updates to the Gmail app enjoyed by Froyo users back to Eclair.
It's not called Ice Cream. It's Ice Cream Sandwich http://techcrunch.com/2011/01/11/android-ice-cream-sandwich/