Google: Android KitKat now runs on 21% of all Android devices

Google: Android KitKat now runs on 21  of all Android devices

Released by Google in October 2013, Android KitKat is slowly but surely embracing more and more devices, as manufacturers are striving to provide updates to keep users happy. According to Google data gathered between August 5 and August 12, KitKat now runs on 20.9% of all Android devices. KitKat was at 17.9% in July, and 13.6% in June, so its steady growth is obvious.

While we now have fewer devices running Jelly Bean when compared to last month, this version of Android (including 4.1, 4.2 and 4.3) is still the most widely used, being found on 54.2% of devices. Android 4.0 Ice Cream Sandwich currently powers 10.6% of Android devices, while 13.6% are stuck running 2.3 Gingerbread. Last on the list, still giving life to 0.7% of devices, is the very old Android 2.2 Froyo. Other Android versions, like Honeycomb or Éclair, are not listed because they account for less than 0.1%.

It will be interesting to see how things stand after Google launches the brand new Android L (currently available as a Developer preview for select Nexus devices). Let's hope the upgrade process won't be a painfully long one - though we're afraid that this is exactly what will happen in the case of some manufacturers.

FEATURED VIDEO

47 Comments

1. sgodsell

Posts: 6739; Member since: Mar 16, 2013

So what this means is 29% of all the Android devices can use Android wear watches.

5. verbalize

Posts: 150; Member since: May 03, 2013

That's pathetic.

7. 0xFFFF

Posts: 3806; Member since: Apr 16, 2014

Considering that projected sales of Android are over 1.1 billion devices just this year alone, and that Android is well on the way to 2 billion total devices in use, 29% of this massive number is just fine.

15. AfterShock

Posts: 4146; Member since: Nov 02, 2012

That's more users then the no2 leading OS Eco system holds still isn't it?

19. 0xFFFF

Posts: 3806; Member since: Apr 16, 2014

Good question. As a matter of fact, I believe it is.

35. carlos5593

Posts: 28; Member since: Jun 23, 2012

No, that means 75% of all Android devices can use android wear. It goes from from Android 4.1 to present.

38. sgodsell

Posts: 6739; Member since: Mar 16, 2013

No Android wear needs Bluetooth 4.0 LE. Which only arrived in 4.3 and above. Its still not bad. Considering that's almost a 1/3 of the users now. By next month it should be a 1/3 for sure.

40. skyline88

Posts: 697; Member since: Jul 15, 2013

and the percentage within the 29 % who actually owns a smartwatch? 0.0002916738 % perhaps?

2. Dastrix unregistered

Android L will surely be well received by consumers and manufacturers alike. Refreshed UI, Material Design, and the functionality overhaul all look very promising.

3. Arte-8800

Posts: 4562; Member since: Mar 13, 2014

Android KitKat sounds and looks familiar better than Android L> LimePie. JakeLee might be here soon..to bash Android.?

6. 0xFFFF

Posts: 3806; Member since: Apr 16, 2014

"KitKat now runs on 20.9% of all Android devices. KitKat was at 17.9% in July, and 13.6% in June, so its steady growth is obvious." Obvious, except to FakeLee. Though it was at times entertaining, FakeLee's incessant shill nonsense is just a form of pollution. Hopefully PA let him know he needed to cease and desist.

17. StraightEdgeNexus

Posts: 3689; Member since: Feb 14, 2014

Hehe my naming scheme is getting popular. lol@fakelee.

21. 0xFFFF

Posts: 3806; Member since: Apr 16, 2014

It's a good naming scheme. Makes it easier to keep track of the shills.

25. Arte-8800

Posts: 4562; Member since: Mar 13, 2014

Lmao FakeLee.

9. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Fantastic! The devs will surely RUSH porting their apps to 64-bit ditching 70+% of user base and make TONS of money thereby. And those 70+% will be extremely happy with that.

12. AfterShock

Posts: 4146; Member since: Nov 02, 2012

Yeah cause they can only choose one system to Dev for.

26. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Do you have that "varies with device" clause in mind? Sorry disappointing you. It just tells you that the devs used higher SDK version than the minSDKversion they targeted. The devs almost always use the latest SDK version, thus pretty much every app comes with that meaningless clause.

39. sgodsell

Posts: 6739; Member since: Mar 16, 2013

Clearly you don't work with Android. When 64 bit Android-L arrives, the existing apps will still work for 32bit or 64bit.

43. JakeLee

Posts: 1021; Member since: Nov 02, 2013

You Androtakus have one thing in common : cluelessness Google might be telling the truth with 85% of *all* apps being written in Java, but the truth is : 90% of apps 99% of users are using 99% of the time *aren't* written in Java. - for some reasons. In order to make their NDK apps run in 64-bit, the devs *HAVE TO* rebuild them, (most probably) TARGETING KITKAT or later, thus ditching 70+% of the user base (as for now). "varies with device"? The practice supporting multiple levels of APIs only works with SDK, and NOT with NDK. In a nutshell, there won't be any meaningful number of 64-bit NDK apps available until targeting KitKat makes sense : 3~4 years from now. Now, who is lying or talking BS?

44. RebelwithoutaClue unregistered

So a dev will build them in 32 bit and then rebuild them in 64 bit and publish two seperate apps to make sure everybody gets a piece of his action thus maximizing sales. Hardly an effort a dev wouldn't make.

45. RebelwithoutaClue unregistered

And it doesnt even have to be two apps even, he can have multiple apk's under 1 app in the Playstore,even with NDK.

46. nasznjoka

Posts: 418; Member since: Oct 05, 2012

what's wrong with you and java? Do you even know how it looks or you just go to your MSblog to get *clue* and come here vomitting. Java aside, Android leads because of varieties of options available thus developers need not use java to develope they can use unity, html5, cordova etc but users (most of us) don't care what language is used, be it java or whatever language you think should be used

18. sprockkets

Posts: 1612; Member since: Jan 16, 2012

They don't have to fcktard. Most apps use the adk, not the ndk, requiring no porting whatsoever. Oh wait you are trolling, so you can gfy while you are at it.

22. JakeLee

Posts: 1021; Member since: Nov 02, 2013

From the top 25 apps, only three are sdk based while 22 are ndk ones. You call 12% most? Well, I'd call 88% most. You Androtakus have quite different definitions by default.

23. sprockkets

Posts: 1612; Member since: Jan 16, 2012

Oh, were you quoting from that BS article here on PA, you know, the one that got deleted cause it was BS? Nice one there. Oh and I forgot, people can't reprogram apps because, you know, something BS BS something.

27. JakeLee

Posts: 1021; Member since: Nov 02, 2013

I didn't only read that article, but checked 25 free apps for myself. The numbers are dead accurate. Stop talking BS.

33. sprockkets

Posts: 1612; Member since: Jan 16, 2012

You don't even know how to fcking check whether or not they are native apps! Dude, really, STFU.

34. JakeLee

Posts: 1021; Member since: Nov 02, 2013

Oops, I just did some reverse engineering with the static object files (*.so) that came with the apks. Since when do Java apps contain machine code binaries?

47. nasznjoka

Posts: 418; Member since: Oct 05, 2012

sure you did and to answer your question since when bluh bluh... Java uses its own type of binary code (bytecode)

24. StraightEdgeNexus

Posts: 3689; Member since: Feb 14, 2014

What is "androtaku"?

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 https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.