Android 4.3 (Jelly Bean?) spotted running on Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10 in our server logs

April 30, 2013

A series of Google Nexus devices apparently running an unannounced version of Jelly Bean have been spotted in Android Authority’s server logs.

Android 4.3 (and various versions of it including Android 4.3.3 and Android 4.3.1) can be seen in the screenshot above. Naturally, user agent profiles can always be faked, but why would anyone go through all that trouble just to try to fool a few tech websites and their readers.

Similarly, we have spotted Android 4.2.2 and Android 4.2 builds in our server logs ahead of their respective launches, so it would make sense to see traces of Google’s next Android versions appear with just a few weeks to go until Google I/O kicks off.

On that note, we’ll remind you that Android Police also spotted the same Android version a few days ago, but its logs showed build JWR23B running on the Nexus 4 and Nexus 7.

As you can see in the screenshot above, we can easily spot a bunch of Nexus devices including the Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10 running a variety of Android 4.3 versions including JWR25C, JWR24B, and JWR29/JWR29B. We also notice a Nexus 4 running build JDQ39 (Android 4.2.2) which is identified for some reason as Android 4.3.

Of the build versions mentioned above, we spotted JWR25C on the Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10, while JWR24B was seen on the Galaxy Nexus and Nexus 4. Build number JWR29/JWR29B has been seen on the Nexus 4.

After digging through the virtual dirt, we found out that visits from these Nexus devices running these Android 4.3 variants were registered in the last week of April, hitting as early as April 29 and coming from a variety of locations, including Google’s Mountain View home in California, other California-based locations, but also London, UK and India.

The screenshot above also shows two other non-Nexus devices running other Android 4.3 versions. One of them is listed as the Huawei U8819 (a model number awfully similar to the Huawei Ascend G300 U8818/U8815) running Android 4.3.3, while the other one is the ADR8995 4G (known to the public as the Pantech Breakout) running Android 4.3.1 (which is interestingly, and probably mistakenly, dubbed as Key Lime Pie).

Mind you, these non-Nexus devices are not flagship handsets, and they’re not even 2013 gadgets either. The Ascend G300 (assuming that’s what U8819 stands for) has been announced in February 2012, while the Pantech Breakout was unveiled in July 2011. Most likely, these devices aren’t running an Android 4.3 version, although we are mentioning them since you can easily spot them in the image above and question them.

key-lime-pie-1

While not confirmed, Android 4.3 is most likely another Jelly Bean version. Most of these Android 4.3 builds start with the letter J, therefore it makes a lot of sense to think that Android 4.3 would be a new Jelly Bean version rather than Key Lime Pie.

Android 5.0 Key Lime Pie has not been spotted in our logs at this time – or at least we don’t have any relevant Android 5.x sightings to report other than the strange build name for that Pantech handset above and a variety of Android 5.x entries that were seen mostly in relation with non-Android devices.

As for Key Lime Pie (KLP) itself, we have no way of confirming that Android 5.0 will be called KLP or not, even though that’s what the majority of reports seem to indicate.

Considering the timing of this Android 4.3 apparition, it also makes sense to believe that Google may be interested in releasing a Jelly Bean upgrade at this year’s Google I/O instead of moving directly to the next major Android OS release. That way, the company would give OEMss time to update more devices to Jelly Bean (whatever version) before the next Android version launches, be it KLP or anything else.

Google I/O takes place in May (May 15-17) and we’re certainly interested to see what products Google will unveil. There are plenty of sometimes-conflicting rumors detailing products that could be showcased on stage in a few weeks, from new hardware (a new Nexus tablet and smartphone, a Motorola-made X Phone, new Chromebooks ) to software (new Android OS version, Google Babel) although nothing is confirmed right now – and don’t expect Google to announce all these products at the same event either.

Comments

  • NOOOOOOO

    NOOOOOOOO

  • Kacho_ON

    I think you got this wrong, The U8819 might be the successor to (and not the) U8818.
    Huawei Nexus?

    • Anthony Wiseman

      That would be a Nexus I would not buy.

      But I thought the same thing when I saw it.

  • Ivan Myring

    There will not be a new nexus phone

    • MasterMuffin

      And how do you know that…

    • castial

      there is a supernexus project going on

  • Magentic1

    Could be Apple influence with biometric sensor integration slated to come out on new iphone and ipad? You know like finger print recognition sensor.

  • housry23

    I just don’t understand why we think 4.3 is automatically Jellybean and not Key Lime Pie. ICS was 4.0 and JB was 4.1 and 4.2. Maybe, just maybe, 4.3 is KLP. I guess we’ll find out in a couple weeks!

    • Castial

      key lime pie is 5.x

      • FrillArtist

        How do you know that? What OFFICIAL information do you have? Stop making up crap and spreading rumors.

        • Gafanhotz

          Build numbers mate, usually the first letter of the build like JDQ39E match the codename, like Jelly Bean.

          • FrillArtist

            ICS was 4.0. Jelly bean was 4.1. New name doesn’t mean new rounded number.

          • Nicktrance

            he’s talking about build number not version number, although that may easily be changed before release.

          • FrillArtist

            Ah, okay. My bad. Ignore my stupidity.

          • housry23

            But still, there is not Official information that Key Lime Pie will be Android 5.0. In the past, Google has jumped up a whole number when there has been major UI changes like 1.6 to 2.0, then 2.3 to 3.0 and 4.0, but if the changes are more internal workings and features they jump a decimal like 2.1 Eclair to 2.2 Froyo to 2.3 Gingerbread. ICS was 4.0, Jellybean was 4.1 and 4.2 and apparently 4.3. Who’s to say 4.4 or 4.5 won’t be KLP? It could jump to 5.0, but we just have no way of knowing until it starts leaking.

    • http://twitter.com/TheBojanTomic  ~1 Day #CAGI Video

      Because BUILD starts with the name of Android version – Jelly Bean: JWR25C…

  • http://www.facebook.com/profile.php?id=100001088959750 Ryan Lounsbury

    I’ve read/heard from a few spots that supposed 5.0 KLP is behind schedule. Perhaps so much so that a minor update will be released at I/O with a full KLP delayed to Q3 or Q4 ’13?

  • williamworlde

    Thank you gentlemen, I AM SURE you are ALL men, for giving me a good laugh this morning! Maybe alike my Facebook, I need to stop reading AA for really inane conversations. But then again, I just participated didn’t I? Hmmm…..

  • sj

    sean jay reyes
    dont like tablets

    • jodale

      jodale…
      you cool man…

  • Tim Johnson

    I have a Huawei G300 and it’s actually not bad. I ran CM10.1 without many hitches (since went back to CM10 for various reason). But it is, unfortunately, slightly lacking hardware wise (>512MB RAM, single 1GHz processor, 480 x 800 4 inch screen to name a few).

  • rgeiken

    Hooray for Android 4.3 on Nexus 10. I installed it the other day and after removing my External BT Keyboard and then reacquiring it, this device doesn’t disconnect from my tablet ever 20 or 30 seconds as it was doing with BT 3.0. BT 4.0 is the low energy version, and does not use as much energy at BT 3.0. If you are using an external BT keyboard, remove it and then reinstall it and as far as I can see it will no longer drop out after less than 1 minute. It installed a lot easier than it did with BT 3.0. That was the main problem that I had on my Nexus 10, and it looks like it has been put to bed. If you are going to put 10 lines or more of text into your tablet, it will be a lot easier for most of us to use a keyboard and now it looks like the engineers have got this problem solved.