Google changes how it measures Android version adoption, sees uptick in Jel

By +Frank B.
in Back Page News

 Share

Recommended Posts

Grand Master

+Frank B. Subscriber²

Posted
  • Subscriber²
Posted

Google changes how it measures Android version adoption, sees uptick in Jelly Bean devices

Google routinely gives monthly numbers breaking out the adoption of various versions of Android, but the company has now changed the way it calculates those numbers ? providing a distinctly different portrait of the Android ecosystem in the process. As outlined on the Android Developers site, Google now uses the data collected when users visit the Google Play Store; under the previous system, any check-in to the store by the device would have been incorporated into the results, user-generated or not. The new system went into effect starting with this month's results.

The change essentially skews the results towards those users who are actively visiting the Play Store. Google says as much on the page itself, noting that the new system "more accurately reflects those users who are most engaged in the Android and Google Play ecosystem." To be fair, however, it is those same users that Android developers should arguably be focusing on in the first place, since they're more likely to discover or purchase an app.

Unsurprisingly, the new data collection tactic results in a landscape of Android users that are more current than what was described just one month ago. Jelly Bean accounts for 25 percent of the devices out there ? up from 16.5 percent in March's results. The other numbers saw less dramatic shifts; Ice Cream Sandwich was on 29.3 percent of devices in the new figures (up less than a percentage point from the prior month), while Gingerbread users dropped from 44.2 percent to 39.8 percent.

While adoption of new versions of Android has been on the rise ? last month Android 4 variants overtook Gingerbread for the first time? it's not clear whether the change in the Jelly Bean numbers here is sheer adoption, the change in the way the data is calculated, or a combination of both. Future numbers should provide additional insight, but one thing is certain: the days when the Android ecosystem was reliant on version 2.3 appear to finally be fading away.

post-1302-0-22599300-1364973177.png

Source: The Verge

Rising Star

AlexMagik

Posted
Posted

The sad part is actually the manufacturers that don't send much updates. the whole point of using android, except the sharing of an App store, was to be upgradeable by google as it's standard code. instead end up the same as a closed source OS that got stuck on that device until you trash and get a new one.

We could talk about rooting it, but the majority of the people don't even know what's that, nor they would even bother doing it, so it's not a real option.

  • fusi0n and +Zlip792
  • Like 2
Grand Master

TheLegendOfMart

Posted
Posted

It's great that Android is open source but its only hurting the OS in the long run, there are brand new phones being released today with low resolution, slow cpu and gpu, hardly any memory still running Gingerbread, I don't like closed platforms but there is something to be said about how Microsoft and Apple run things, their phones have a guaranteed level of performance and quality.

Grand Master

+Audioboxer Subscriber²

Posted
  • Subscriber²
Posted

It's great that Android is open source but its only hurting the OS in the long run, there are brand new phones being released today with low resolution, slow cpu and gpu, hardly any memory still running Gingerbread, I don't like closed platforms but there is something to be said about how Microsoft and Apple run things, their phones have a guaranteed level of performance and quality.

And a nice price tag to boot (Apple anyway).

Grand Master

dead.cell

Posted
Posted

The sad part is actually the manufacturers that don't send much updates. the whole point of using android, except the sharing of an App store, was to be upgradeable by google as it's standard code. instead end up the same as a closed source OS that got stuck on that device until you trash and get a new one.

We could talk about rooting it, but the majority of the people don't even know what's that, nor they would even bother doing it, so it's not a real option.

Still stuck with 4.0.4 thanks to Sprint on my GSII. Planning to root my phone but I barely have time for anything as it is. They promised an updated at the end of December, then pushed to February, then March... then LATE March. Now it's April lol...

I love Android and probably wouldn't switch to anything else, but this is friggin stupid.

Grand Master

techbeck

Posted
Posted

Still stuck with 4.0.4 thanks to Sprint on my GSII. Planning to root my phone but I barely have time for anything as it is. They promised an updated at the end of December, then pushed to February, then March... then LATE March. Now it's April lol...

I love Android and probably wouldn't switch to anything else, but this is friggin stupid.

Nexus devices. Always updated first.

Grand Master

Growled Member

Posted
  • Member
Posted

Still stuck with 4.0.4 thanks to Sprint on my GSII. Planning to root my phone but I barely have time for anything as it is. They promised an updated at the end of December, then pushed to February, then March... then LATE March. Now it's April lol...

You get a few more features and such with 4.1 but for me it's wasn't that big of an upgrade. Got a Samsung Galaxy Tab 2 7.0 running 4.1.2

Grand Master

Sandor

Posted
Posted

Still stuck with 4.0.4 thanks to Sprint on my GSII. Planning to root my phone but I barely have time for anything as it is. They promised an updated at the end of December, then pushed to February, then March... then LATE March. Now it's April lol...

I love Android and probably wouldn't switch to anything else, but this is friggin stupid.

HTC/Bell Canada have left my device on 4.0.3

Probably going to cut both the phone (and Bell) in the summer and buy a WP8 device outright.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By Slugsie · Posted

      The machines are starting to fight back any way they can.
    • Linux 7.1 arrives with an NTFS overhaul and major hardware performance boosts

      By Accuphase · Posted

      No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By zikalify · Posted

      Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • Microsoft confirms Recycle Bin bug across all versions of Windows

      By snowy owl · Posted

      I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs

      By hellowalkman · Posted

      Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.

  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post

  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!