Android 5.0 may be released in late October and be optimized for older phones
The whole idea behind Google slowing down the pace or Android OS releases was ostensibly for manufacturers to get caught up a bit, not that it matters too much because then everything has to go through carrier validation anyway.
With the pending releases of the “Nexus experience” or “Google Edition” devices coming from Samsung and HTC in the near future, there has also been speculation that would also mark the introduction of Android 4.3 to the world. Assuming that happens in late June or early July, that gives the field three months to catch its breath before Android 5.0 might take the stage.
That will be small consolation for those that are getting excited to upgrading their devices just now to Android 4.1 or 4.2. We will dwell on the self-flagellation of the manufacturers another time and note that this tip that the guys at VR-Zone received makes sense in that we know Motorola will be well underway with a total product re-launch between August and October, so we will remain open minded.
As to what Android 5.0 may bring to the table, it is said that the OS has been worked over hard to make Key Lime Pie run okay on devices running as little as 512MB of RAM (that is dating back a bit). This would be a nice gesture seeing as how the manufacturers have been pretty selective as to which of their relatively new hardware will even get a generational update to the operating system to begin with.
Of course it will take a lot of examination by the OEMs to see how feasible it is to bring some of the older gear up to date, but hopefully that issue will have been anticipated and addressed by Google. We know how passionate our readers are about given platforms, but you have to admit, competing platforms have been pretty effective at supporting legacy gear, Apple’s iOS, Windows Phone, even BlackBerry make pretty clear delineations in terms of OS support.
Taken with the appropriate amount of cynicism, this news seems feasible. It also provides enough of a window for the Sony Xperia Z running stock Android to show up and sink in. Meanwhile, the tip hints that the Nexus 5 will enter the spotlight as well. It is shaping up to be an eventful summer.
1. Nathan_ingx (Posts: 3135; Member since: 07 Mar 2012)
This is actually a good thing...
If it can run well on 512mb RAM-ed devices, it'll be better on devices with higher memory.
Of course, the silicon has to be good too.
3. PunyPoop (Posts: 750; Member since: 18 Jan 2013)
Now I think I can update my HTC Wildfire! Maybe..
12. PunyPoop (Posts: 750; Member since: 18 Jan 2013)
Oh yeah! That's what I like in Android! Very Flexible!
16. jatin8189 (Posts: 4; Member since: 16 Jan 2013)
i don't thik key lime pie running on 512 ram :) its crazy.
coz.. my note2 already w8ting for 4.2.2 update. & 5.0 too long time.
HTC Wildfire ?
32. Lauticol (Posts: 248; Member since: 25 Jun 2011)
My dad's Wildfire it's in CM9.1 and it's really snappy!
23. ihatesmartphone (unregistered)
Galaxy S with key lime pie...
2. datsyuk (Posts: 177; Member since: 11 Jan 2012)
With Google continuing to polish and optimize this UI this is going to be extremely exciting when it's released. Can't wait for the next Nexus! The Nexus 4 is running just as smooth as these newer phones with Snapdragon 600s with the old S4.
4. Sniggly (Posts: 7250; Member since: 05 Dec 2009)
I have to wonder what 4.3 and 5.0 are going to bring to the table. I will note that the Android consumer base is the least fragmented it's been in years. The older distributions are all but gone, only a third of Android users are still on 2.3 (and that number will drop like a rock in the coming months; assuming a 5 percent drop each month like it's been going, by next year pre 4.0 will be virtually extinct) and updates are coming faster.
Also of note is that except for a small collection of features, even 4.0 is pretty comparable in performance and ability to the Jelly Bean versions. The next few months should be fun for Android. :)
5. Trex95 (Posts: 660; Member since: 03 Mar 2013)
The good thing Google/Android works hard and this an good news for competition.
well done Google and keep the good job
6. _Bone_ (Posts: 2148; Member since: 29 Oct 2012)
I'm interested in the camera-centric Nexus device.
7. _Bone_ (Posts: 2148; Member since: 29 Oct 2012)
But sure as hell hope that they simplify the kernel code so they get rid of the lag and abuse of power, RAM, battery. It's not just iOS that figured out to run an OS on limited resources but Windows and Blackberry as well, imagine the goods a lightweight Android would do to performance and battery life!
8. Sniggly (Posts: 7250; Member since: 05 Dec 2009)
well, we'll see how the next kernel turns out. I'm actually happy that Android requires significant resources to run, because it's inspired a lot of hardware innovation.
17. joey_sfb (Posts: 4081; Member since: 29 Mar 2012)
do you know what you are talking about? Windows 8 has more feature and therefor require more hardware resources to run, make sense right?
Likewise Android is far more advance than iOS with true multitasking and yet still run well on dual core arms processor like the iPhone 4/5 due to additional optimisation effort such as project butter.
Only Apple fans would overlook this and blindly bash Google.
25. maxican16 (Posts: 364; Member since: 29 Sep 2011)
@joey: I'm a huge fan of Android. And I agree with Bone. I'm not sure if the optimization needs to be done at the kernel level necessarily (just lack of knowledge on the subject), but while Android wipes the floor with iOS in terms of functionality, iOS does pretty much the same to Android in terms of performance. Sometimes the truth hurts, but it sets you free! Haha
And great point Sniggly.
34. joey_sfb (Posts: 4081; Member since: 29 Mar 2012)
I not a fan. I just use it as its the best thing for me right now.
Lack of knowledge in coding that why you don't see the effort require that feature demand hardware resources to go hand in hand. When iOS gain full Android feature sets than we will see who is the better coders Google or Apple.
10. akbar (Posts: 62; Member since: 09 Feb 2012)
I don't see how this is any good news for the old devices. It is clear that Google is not the main reason for the slow upgrade, but the manufacturers and/or the operators. Also the devices with 512 MB RAM are either old and/or from small manufacturers who don't publish updates anyway. Even if Android 5.0 plays well with 512MB RAM this will mean that the manufacturers will have to port their touchWizz/Sens/MotoBlur, etc to old devices which are most likely already out of official support or soon will be.
The announcement is only good news for the future low end devices which will have latest version of the OS on bargain prices.
13. andro. (Posts: 1986; Member since: 16 Sep 2011)
I'll still hold to what reps from OEMS have told me that the next level of android will be offically called kettle corn when actually launches and not kid lime pie,if I'm wrong I'm blame them!
26. maxican16 (Posts: 364; Member since: 29 Sep 2011)
But there have been Google Easter eggs depicting Andy with some key lime pie. Time will tell!
14. .KRATOS. (Posts: 164; Member since: 15 Mar 2013)
It better have some new features also, like what apple did to their os n to be light.
18. HASHTAG (unregistered)
Though Android 5.0 may work on older devices, do you really think manufactures will still give those older devices the upgrade?
27. maxican16 (Posts: 364; Member since: 29 Sep 2011)
Most likely no. But, IF this manages to be true, the developers might take the lead on that and back port 5.0 to older phones. The developer community is pretty flippin' amazing.
19. OpTiMuS_BlAcK (Posts: 413; Member since: 04 May 2012)
Can't to fire up CM11 on my phone then~
20. gehena1315 (Posts: 54; Member since: 12 Jun 2013)
Android 5.0 will suck!! I have 4.1 htc one x. it lags and freeze, nokia is better!
22. jaychildz (Posts: 111; Member since: 31 May 2013)
LIAR that's an AT&T phone you probably have criket or some s**t
24. CanYouSeeTheLight (Posts: 1057; Member since: 05 Jul 2012)
Really doubt you have a One X on 4.1 as my experience is quite the opposite of yours it seems, barely lags (only the occasional stutter) and i never have my phone freezing on me.
28. Daftama (Posts: 590; Member since: 03 Nov 2012)
5.0 yes but 6.0 cheesecake will change the whole game..2014 it a game changer..
35. flynfree (Posts: 374; Member since: 09 Jun 2013)
Were immune of lags and freezes! !!
That's Android world, and love it! !!! ;-)
38. kabhijeet.16 (Posts: 723; Member since: 05 Dec 2012)
LOL.. This guy is Nokia Fanboy. He has never owned an Android device. Any person who owns an Android would love it. Ans HTC One X with android 4.1.. LOL.. Its impossible. Everyone knows that HTC One X is a beast when comes to performance. and its even better with Android 4.1 (than with android 4.0). This guy is juz Trolling..
21. Quezdagreat (Posts: 428; Member since: 05 Apr 2012)
By older phones that mean phones released in 2012
30. VZWuser76 (Posts: 2588; Member since: 04 Mar 2010)
Yes, and Apple products released in 2013.
31. Quezdagreat (Posts: 428; Member since: 05 Apr 2012)
Why would apple products get android 5.0?
37. VZWuser76 (Posts: 2588; Member since: 04 Mar 2010)
That was sarcasm. As in Apple products released this year are considered older models. Mmkay
33. Zero0 (Posts: 592; Member since: 05 Jul 2012)
The next phase.
Android fragmentation will go extinct in 2014.
36. yowanvista (Posts: 338; Member since: 20 Sep 2011)
This is utter nonsense, current Android phones with an advertised RAM amount of 512MB usually have around 350-370MB of usable RAM (the GPU, kernel, surface flinger, ADSP, audio 720p recording, Youtube etc use the rest). Now considering that stock Android itself occupies around 150MB out of that ~350Mb that leaves around 150Mb being free (the services, background processes and Apps will further reduce the available RAM). The problem here is not about Android not being optimized but rather ancient hardware running hardware components not design to run on Jelly Bean.
Most devices from 2012 released 512MB of RAM use the Snapdragon S2 SoCs and were originally packed with Android 2.3/Kernel 2.6. Those devices if flashed with a custom ROM like CM10.1 (JB4.2.2) will definitely exhibit LAGS due to the poor implementation of Adreno libs. Those devices and their components were designed to be used with PMEM allocation along with Kernel 2.6 ONLY but a drastic technical change in memory allocation (from PMEM, NVMAP, CMEM etc to the unified ION) which occurred when ICS was released meant that manufacturers had to rebuild their kernel blobs from scratch if they considered upgrading their older devices but also meant that several devices would never taste ICS let alone JB (The Galaxy S for instance).
Of course one could build a custom kernel with ION but without sources/blobs design for ION the task of making the hardware components like the camera working becomes impossible. Even Qualcomm no longer provides PMEM Adreno libs for Jelly Bean, they basically stopped since ICS. So the "optimized for older phones" fact is moot. Even Google can't help if the manufacturers don't provide ION libs (and they won't waste their time recoding/porting everything from scratch).
And don't forget that Android ICS and above was designed to utilize ION allocation, there's no reason why Google would go back to the fragmented memory allocation architectures used by SoC manufacturers. Those old devices also run kernel 2.6 which is essentially not meant to work with Jelly Bean and above (vsync, project butter and the hwa stuff will be broken with 2.6). And now you expect manufacturers to build new kernels for their older devices?
P.S. I own a 512MB device running CM10.1, kernel 3.4.48 (with PMEM) and anything related to the GPU (gaming, web browsing, 2D-3D performance) is terrible due to the lack of proper libs. Nobody supports such old SoCs, even Qualcomm doesn't care.
39. itsdeepak4u2000 (Posts: 3427; Member since: 03 Nov 2012)
This is great! Now even smaller devices would also enjoy big experience.
40. networkdood (Posts: 6329; Member since: 31 Mar 2010)
My Captivate runs 4.2.2 cm10.1 quite nicely.