KitKat now on nearly a quarter of Android devices

KitKat now on nearly a quarter of Android devices
According to the latest Android distribution figures computed by Google, 24.5% of Android devices are using Android 4.4.x, also known as KitKat. This is up from the 20.9% of Android models sporting KitKat last month. The version of Android most in use is Android 4.1.x, with 25.1% of Android devices powered by the build. Over all, 53.9% are using Jelly Bean, which covers Android 4.1.x to Android 4.3.x. That is off from the 54.2% that Jelly Bean powered last month.

After Jelly Bean and KitKat, Gingerbread (Android 2.3.3 to Android 2.3.7) is next covering 11.4% of Android devices (down from last month's 13.6%). To show you how old that build of Android is, consider that the final update to 2011's Motorola ATRIX 4G was Android 2.3.6. And yet, you can find this build on better than one out of every ten Android powered devices. Ice Cream Sandwich, accounting for Android 4.0.3 and 4.0.4, is on 9.6% of Android phones and tablets. That is off a full percentage point from the reading of 10.6% that this build garnered last month.

Google put together these readings from Android devices that visited the Google Play Store, for the week that ended September 9th.

source: AndroidDevelopers via AndroidandMe



1. chistoefur

Posts: 103; Member since: Nov 05, 2012

Very nice. With the new iPone's and iOS 8 coming shortly, I need Android L now more than ever :x

2. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Still way too low for devs setting it as the minimum requirement. What's the point? They mostly don't even target JB.

3. nathan.carter

Posts: 416; Member since: Aug 11, 2014

wrong. almost everuthing in 4.4 is supported in android 4.1. get it right.

6. JakeLee

Posts: 1021; Member since: Nov 02, 2013

You most probably won't be able to make your apps 64-bit ready unless you target Kitkat or higher. It's just a guess since Google never talked about this. It may be wrong on this, on the other hand however, chances are there that it bluntly requires L. That's the Google I know.

13. sgodsell

Posts: 7431; Member since: Mar 16, 2013

Google actually did talk about 64 bit and Android L. They even said you won't have to change a thing. Why because Android is using a VM (Virtual Machine). So things are compiled at runtime. With ART its at install time when things get compiled. So when Google decides to update Android to 64 bit, then if the virtual machine is updated then things are recompiled to either take advantage of 64 bits, like longs and double calculations will automatically take advantage of 64 bits. Not to mention the internals of Android will be 64 bit and the Linux Kernel will be 64bit as well. Naturally not everything will be 64bits like Native code won't take advantage of 64 bits. But native code is usually tied to a specific architecture.

18. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Another typical, clueless Androtaku copy paste mastery. What you are saying REQUIRES the apps to be written COMPLETELY in Java. And 90% of top apps AREN'T. What do the devs have to do then to make their apps become 64-bit ones? They HAVE TO build their apps again TARGETING an Android version as the minimum REQUIREMENT, and Google has been silent about this, just mentioning what you said : Java apps don't need to be rebuilt. Great. What can a person with average intelligence deduct from this? It will be HIGH, either Kikat or straight L. And neither is acceptable for the devs taking the fragmentation into account. It's only the Androtakus who doesn't want to believe this, blindly repeating BS passed by Google. Andro-sheeps.

20. sgodsell

Posts: 7431; Member since: Mar 16, 2013

Don't be an idiot. First and foremost apps whether 32 bit or 64 bit will work on the same 64 bit processors (Cortex-A57/A53). The same holds true for 64 bit intel processors as well. So no worries for Native code. But naturally if you did use Native code then its up to developers to ultimately make sure things will continue to still work and function properly on the new 64bit hardware. I like the lie you continue to post about the 90% of the top apps are not written in COMPLETE Java. But lets go there with your lie of 90% okay. Now do you honestly think those top apps on the play store are not going to be updated to take advantage or for that matter even checked to make sure that they will still run on the new Android - L? Please tell me that you are not that dumb, especially since Android - L has been out for some time. There is no reason to be able to not check things out with your apps especially if its an app being using by millions or even hundreds of millions of people.

22. Finalflash

Posts: 4063; Member since: Jul 23, 2013

Dude, don't waste your time on him, he is a hardcore fanboy and won't back down even though he's been proven wrong like 20 times. Literally over 90% of Android apps are programmed in java and the remaining will just update their code (just like they did for iOS). He literally is trying to gain back his glory days when the iCircleJerk used to welcome him because he hadn't been smacked down by an author of this site (some of us called him out on his BS but obviously the iCircleJerk came to his rescue and just jerked his comment higher). PS: I am noting the time this comment gets deleted in since apparently JakeLee has an inside man at PA who is always making sure comments calling him out are deleted.

24. JakeLee

Posts: 1021; Member since: Nov 02, 2013

I don't just honestly THINK, but I also KNOW devs will target Kitkat or L in three years, not earlier. And what lie? Unpack the APK, only two apps were pure Java ones while the other 23 were running native codes. Millions of users? Alas, that's the whole point. Vast majority of consumers who purchased 64-bit Android phones will be stuck with 32-bit apps during the lifespan of the phones. Is that OK for you? I think that's crap.

4. PapaSmurf

Posts: 10457; Member since: May 14, 2012

Why did I know I was going to find you here?

7. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Glad to know that you can learn.

15. sgodsell

Posts: 7431; Member since: Mar 16, 2013

Please keep posting your lies. Please so everyone can see JakeLee as he truly is, a trolling liar.

12. nithyakr

Posts: 161; Member since: Jun 20, 2014

This shows exactly whats wrong with Android. nearly 50% of Users are still stuck in Software which is more than 2 years old. (GB + ICS + 4.1 JB) That's just pathetic when it compares with iOS 7 (the latest iOS since iOS 8 is not yet released) which runs on 99% of iDevices. You can make any number of excuses but truth never lies.

16. sgodsell

Posts: 7431; Member since: Mar 16, 2013

So why do you think Apple is going with their new language Swift. Its actually in a lot of ways similar to how Java's runtime is. Apple is even scrapping pointers for the new Apple Swift language.

19. JakeLee

Posts: 1021; Member since: Nov 02, 2013

You don't have to struggle to prove your ignorance. That VM part of LLVM is for virtual machine, but the LLVM compiler has nothing to do with the VM known to you. Noone even wants to mimic Java. Java sucks, especially on mobile where resources are so scarce. Only Google was stupid enough to revive this dying language.

21. sgodsell

Posts: 7431; Member since: Mar 16, 2013

Its has nothing to do with it does it? So why is Swift removing the use of pointers from the language. Also with Apple talking about iOS apps going to run on Macs and vise verse Mac apps on iOS devices. So how is that suppose to run then JakeLee? I will love to here you explain that one to me. Especially since I am ignorant in your words. Please I am waiting for your reply. I am sure everyone else here is waiting for you to go into your details to explain how its going to work.

23. Finalflash

Posts: 4063; Member since: Jul 23, 2013

Dude stop egging him on, watch him just throw a tantrum like he did to all your other comments and then have his buddy on the inside delete all our comments (they already deleted one of mine in this thread). He will defend Apple's moves at all cost and just call you names. Then darkjedii will show up with a comment like "YEA you go bro, and good job tim cook, I love you, can't wait for your new phone, call me.....please...." or something.

32. Arte-8800

Posts: 4562; Member since: Mar 13, 2014

Darkkjedii Lmfao. Another cheerleader for Apple.

25. JakeLee

Posts: 1021; Member since: Nov 02, 2013

"Swift does not create pointers and other unsafe accessors by default" See? BY DEFAULT, to protect incompetent, clueless ex-Java programmers like FF from getting harmed by dozens of crashes. They can be (and should be) enabled by competent devs for maximum efficiency which is absolutely impossible in Java. And again, you don't have to struggle to prove......... That two platforms share the same/similar *framework* doesn't mean the default programming language is a VM based one. It's called *portability*.

31. Finalflash

Posts: 4063; Member since: Jul 23, 2013

Ex-java? No I still program in java which is working perfectly well for me. I'd program in swift too but I make customization apps which really aren't useful in iOS since the jailbreak community is so limited. But you should keep commenting the mindless drivel you come up with because it is very entertaining. Lord only knows when you'll stop shooting yourself in the foot...maybe when they write another article to smack you down again with actual expert sources.

37. JakeLee

Posts: 1021; Member since: Nov 02, 2013

I knew that. Only Java devs can talk so much BS.

33. sgodsell

Posts: 7431; Member since: Mar 16, 2013

To protect incompetent clueless ex-Java programmers. Well Considering there is no pointers in Java in the first place. I guess those clueless Java programmers are safe to begin with. Also I see you are going to avoid and dance around, and not going to explain how the new Swift apps are going to work. I will tell you how it will work then. If you do not use pointers then you can make an app that will be portable as you say. With Apples new Swift they have also introduced a runtime (kind of like Java). So you will be able to take the same app that is going to run on an iOS device and also be able to run it on OS X (ARM and x86). Two very different architectures. Well with Swift introducing a runtime (like Java), now at run time apps will not be tied to any specific hardware architecture. Why do you think Apple is doing this in the first place? So iOS developers will be easily able to make OS X apps as well. Also with Swift under Apples belt, then it can move forward with OS X as well. Just think Apple could make OS X tablets and laptops that could run on Apples AX Arm based chips in the future. Or for that matter any other ARM based CPU or CPU in general. So to sum it up. Swift is emulating what Android is already doing with Java.

35. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Ever heard of fat binary deployment? Just like Java, what I hate the most about Android isn't Android itself, but the Androtakus, half baked techie wannabes who think they know a lot but knows sh*t actually. That sucks.

38. sgodsell

Posts: 7431; Member since: Mar 16, 2013

So in your words then. Explain to me how its going to work then. Please you make a million posts anyway. So no more dancing around or calling names. Please explain in terms that we can all understand how apps are going to work on different architectures using Apples new Swift. If you can't do that. Then no worries. People will see how much your word is really worth. As they say, put your money where your mouth is.

39. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Just like the ARMv7 and ARMv8 binaries are distributed on AppStore currently, thanks to the fat binary deployment. Do you need a tutor? Make an offer. I'm a professional, and there is no free lunch, especially for Androtakus.

40. sgodsell

Posts: 7431; Member since: Mar 16, 2013

Thanks JakeLee, no everyone can truly see how clueless you truly are. That or you can't read properly. But that's okay. Everyone can look at all these posts and still see how you will dance around and avoid questions that are put to you. You pretend you are smart with by using miss directions. That's okay you are a professional and I can see that clearly, but not the type of expert I would be proud of. What you truly are is a professional troll and a liar.

41. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Clueless? Just look at who's the #1 at StackOverflow.

26. Arte-8800

Posts: 4562; Member since: Mar 13, 2014

What's your problem? Are you lazy? Yes Java and Android is resource hungry, but specs are available to be justified. Yes that's why iOS is still halfbaked that it only needs dual core cpu running at 1.5Ghz. Just imagine Apple had used Flash on ios8, it would even lag like anything. iBoy, go play with your fake bogus pusedo Darwin bogus fake platform, that the new ios8 still only needs 1Gb Ram to function the mumbo jumbo 64bit Cpu with pathetic useless 1Gb Ram. iBoy go play with your iToys, ios8 still way behind Android mini PC. Your jealousy is killing you, that you wish ios was full baked and fledged like Android.

27. JakeLee

Posts: 1021; Member since: Nov 02, 2013

The worst thing about Java isn't that it sucks. It generated TONS of clueless, half baked programmers who can only do copy and paste, just like you Androtakus.

29. Arte-8800

Posts: 4562; Member since: Mar 13, 2014

iBoy is that why Siri is Java based.

* Some comments have been hidden, because they don't meet the discussions rules.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.