14
Apr
image
Last Updated: April 24th, 2012

Update: The takju mystery is solved: it's the U.S. GSM Nexus that Google released this morning. It's pretty clear that this device will be one of the first, if not the very first, to see the Jelly Bean OTA update.

We deal with rumors and potential fakes on a daily basis, and I have to warn you right away - on a scale of unconfirmed to solid, the source of this post is leaning to the left.

Everything you're about to see can be easily spoofed, but the circumstances in which the evidence was allegedly obtained, combined with information I dug up in our web server log and the web make quite a compelling case.

In essence, in this case it's too much fun to speculate and too interesting to keep it away from public analysis and, who knows, maybe even anonymous tips (hint, hint).

The Rumor

This particular rumor was started by Yuku Sugianto, an Android developer whose report I am inclined to trust. Yuku is relatively established in the Play Store (at least 800k installs), an engineer at Found (from what I can tell, he started the project, so he may be the sole founder), and has a history of submitting bugs to the Android team.

While he could be trolling, it's not likely. However, I have to remind you again that everything here may end up being false.

Yuku's report along with the crash log follows:

Android JellyBean (no version number) spotted! I got an automatic crash report from one of my application and surprisingly the device info states JellyBean as the OS version. (Android is known to use no version number for unreleased version, e.g. Honeycomb instead of 11 or 3.0 when it was still developer preview)

From ACRA:
PHONE_MODEL=Galaxy Nexus
ANDROID_VERSION=JellyBean

Device:
BOARD=tuna
BOOTLOADER=PRIMELC03
BRAND=google
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=maguro
DISPLAY=JRN12B
FINGERPRINT=google/takju/maguro:JellyBean/JRN12B/330279:user/dev-keys
HARDWARE=tuna
HOST=vpba3.mtv.corp.google.com
ID=JRN12B
IS_DEBUGGABLE=false
MANUFACTURER=samsung
MODEL=Galaxy Nexus
PRODUCT=takju (what's this takju thing?)
RADIO=unknown
SERIAL=0149xxxxxxxxxxxx (removed by me)
TAGS=dev-keys
TIME=1334275846000 (Fri Apr 13 00:10:46 UTC 2012)
TYPE=user
UNKNOWN=unknown
USER=android-build

Another interesting thing is the location of the external storage, which is in /storage/sdcard0 instead of /mnt/sdcard.
getDataDirectory=/data
getDownloadCacheDirectory=/cache
getExternalStorageAndroidDataDir=/storage/sdcard0/Android/data
getExternalStorageDirectory=/storage/sdcard0
getExternalStorageState=mounted
getRootDirectory=/system
getSecureDataDirectory=/data
getSystemSecureDirectory=/data/system
isEncryptedFilesystemEnabled=false
isExternalStorageEmulated=true
isExternalStorageRemovable=false

The Interesting Bits

Wow, what a treat (if true). Let's enumerate the interesting parts:

  1. JellyBean, which has long been rumored to be the codename for the next version of Android.
  2. takju build of the Galaxy Nexus - we've seen mysid (Verizon CDMA/LTE), countless variants of yakju (GSM), but never a takju. What could it be?
    One of our theories is it's the unreleased 32GB GSM Galaxy Nexus that was canned for unknown reasons after getting announced earlier this year.
    Another, much less plausible, is that it's the Sprint Nexus. I personally doubt it's the latter because Sprint's version is CDMA/LTE, but it sounds way too close to the GSM one. If anything, Sprint's Nexus would be a variant of mysid (mysids, perhaps?).

Rumor Analysis

Now, before we begin, I have to point out that everything in the crash log, which was collected by ACRA from a remote user's phone during a crash in one of Yuku's applications, can be faked.

However, if the data was indeed tempered with, it was done in a very proficient and believable way by someone who really knew what he or she was doing, taking care of every subtlety. The circumstantial nature of the way Yuku acquired the log (a random crash) makes it much less likely that the info was faked and sent over on purpose, leading me to believe that what we're seeing is indeed legitimate.

Let me dive deeper:

  1. While JellyBean is present in the log, the Android version number isn't. This may seem suspicious at first, but it's actually a common practice at Google to assign a codename without a version during development. The same thing happened in our Ice Cream Sandwich leak.
  2. takju.
    1. As I mentioned, the takju variant of the Galaxy Nexus has never been released, yet it appears to exist somewhere out there. For example, this GLBenchmark page, which contains all variants of the Galaxy Nexus it's ever seen, along with version numbers, lists the following:

      google/takju/maguro:4.0.4/IMM30D/262866:user/release-keys
      google/takju/maguro:4.0.4/IMM76B/294908:user/release-keys

      There are also other pages, like this one, but the list is pretty short.

    2. I reached out to an engineer on the Android team (who will remain unnamed), seeking basic info on what takju might be, but got turned away with a "no comment." It could have been a generic statement, but this engineer has been helpful in the past, and if takju never existed, I would have expected the engineer to say that he or she simply didn't know what it was. "No comment" responses are always suspicious.
    3. My bet is on the unreleased 32GB Galaxy Nexus. I can't think of another variant that would be so close, yet not that close, to the current yakju variants.
  3. JRN12B, the build.
    1. This build version looks legitimate for a few reasons. It starts with a J, which JellyBean builds need to start with according to guidelines. The exact build number (or it could be an internal version number or revision control's version - in fact, if I didn't know any better and the Android team didn't use git, I'd say it's an SVN revision number) is 330279, which is sufficiently higher than the builds we saw in IMM76B. Looks like JB is well underway, and if each number increment is an individual commit, it already contains over 35,000 of them. Not bad.
    2. I dug into our web server logs to see if I can spot a pattern and found the following from March:

      Dalvik/1.6.0 (Linux; U; Android JellyBean Build/JRM79)

      JRN12B seems like a future iteration of JRM79, which works nicely with our theory here. Notice the presence of JellyBean in that user-agent as well. Of course, both could be fake.

  4. PRIMELC03, the bootloader. The current 4.0.4 Galaxy Nexus's bootloader is PRIMELA03. Once again, PRIMELC03 checks out and looks like a likely successor.
  5. As Yuku mentions, getExternalStorageDirectory() seems to return /storage/sdcard0 instead of something like /mnt/sdcard or /mnt/sdcard-ext, which could point to new interesting developments in the way JellyBean organizes filesystem mounts. If you're not a developer, you probably won't care, but it's definitely something to look out for in the future.
  6. The only thing that did strike me as weird at first (thanks to jcase for pointing it out) is IS_DEBUGGABLE=false. If the device is signed with dev-keys, why is IS_DEBUGGABLE set to false? I then thought about it some more and realized that the IS_DEBUGGABLE flag refers to the way the app was compiled (<application android:debuggable="false" ... />) and has nothing to do with the OS itself, so it's of no interest to us.

Conclusion

JellyBean, another Galaxy Nexus variant we've never seen before, build numbers - none of it is essential or particularly groundbreaking, but all of it is definitely fun stuff for us to soak in, process, analyze, and dream about at night (you do dream of Android, don't you?).

Did I mention a heavy rumor advisory with a chance of bullshit (I hope you were wearing your skepticism +10 cape)?

All of the above is based on speculations at the moment, which I mentioned numerous times, but after analyzing everything presented, I'm inclined to think that it is indeed legitimate build info from a device that is either in the making or is the Android team's equivalent of one of those 2-headed unicorns pooping rainbows that you can only find in government facilities deep underground. It's a freak, it will not see the light of day, but might as well use it if it's sitting around the office, right?

Thanks, Yuku!

P.S. So, what do you think of the above? Did I miss anything else? Will any anonymous tipsters step up and add their 2 cents into the discussion?

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • http://codytoombs.wordpress.com Cody

    The great thing about this particular leak/rumor/myth/whatever is that it doesn't actually matter. It doesn't change buying decisions, if it's right or wrong it won't change that Jellybean is coming out (arguably under a different name, but I think that ship has pretty much sailed), it won't affect developers in any meaningful way (other than now they know they might get these logs)...in other words, this really is just fun to contemplate and we don't need to worry too much if it's bogus.

    • http://www.AndroidPolice.com Artem Russakovskii

      That's right, it was fun to analyze. Although I am now dying to know what takju really is - it could potentially be another Nexus we might want.

      • fonix232

        That sdcard0 is way too much suspicious - what if, takju is a model with an external SD card slot and support?

        • http://www.AndroidPolice.com Artem Russakovskii

          I doubt it - the Android team seemed pretty adamant about not including SD card support into Nexus devices last time they discussed it. I think it's more of a reorg of the way the OS handles filesystem mounts, but I could end up being wrong. Or it could all be fake.

        • fonix232

          Artem, I know about that, but still it seems to be weird to name the main SD card "sdcard0". It assumes the hardware can handle more, there are interfaces for it. But then, there's the flag isExternalStorageEmulated, what's most probably a reference to the FUSE driver used to cross-mount /data/media to /sdcard in HC and ICS.

          Although I would be the happiest for a real external SD supporting GNexus. 16GB isn't enough, and an SD card can be bought really cheap (I can get class 10 8-16-32GB lifetime warranty Samsung ones for 10-20$ inc. VAT).

          And as we're already talking, I wanted to ask this - any news or updates about the Padfone? EU availability, prices, anything?

      • ZZ

        One possibility is that "takju" is just the software variant codename for that build of Jelly Bean, and they're planning to change the software codename for each release for each variant. The Nexus S 4G having 2.3.7 and 4.0.4 both under sojus contradicts this, but it could be a forward looking thing.

        The more likely possibility opens up when you search for "takju". One of the top links is a Korean tourism site, which says:

        "Korea’s traditional liquors are takju (탁주), cheongju 청주 (or yakju 약주), and soju (소주). The oldest is takju, which is made by fermenting grains like rice or wheat. When takju is strained to a refined clear liquor, it becomes cheongju (yakju), and when cheongju is distilled, it becomes soju. Today, takju is more commonly known as makgeolli, and it is enjoyed by the majority of Koreans as well as many visitors."

        So the pre-release build (takju) gets refined over time into (yakju), which is then "distilled" into a build suitable for the Nexus S (soju) by removing & tweaking elements as necessary (such as Face unlock/the Hardware accel tweaks Dianne Hackborn mentioned in her G+ debunk post).

        Such clever nomenclature would fit Google to a T.

        • fonix232

          Basically you say it's an internal test device? Would make sense!

        • Thomas

          He's trying to say that this may be the way they want to codename releases in the future:

          Takju = Pre-production Software
          Yakju = Launch Software, but only on their flagship device.
          Soju = Post-Launch Software, ported to their older models.

          Presumably when Jelly Bean comes out there would be a new Nexus device, that would ship with Yakju.

          A few weeks/months later the Galaxy Nexus would get the upgrade, and then it would be called the Soju and no longer the Yakju.

          I don't think the "Takju" Galaxy Nexus is different from retail devices other than what debugging/developement stuff it might have.

        • http://www.AndroidPolice.com Artem Russakovskii

          Thomas, sorry, there's not a chance this would happen as it would confuse the crap out of everything and everyone. By that logic, NS would have come out with a yakju and then got downgraded to soju but that wasn't the case. Sorry, I don't see this mass version shifting happening, no way.

  • H4ck3r

    sorry, it was me... :D okay, now seriously... I don't find it "real" too

  • Jordan

    all signs point to the Sprint GNex having the exact same specs as VZW's right?

  • seriosbrad

    That's some pretty convincing detective work Artem, well done gathering all the information.

  • teodhor

    Isn't yakju just a android branch name? Then takju might just be some testbranch for new versions of android for the existing nexus. And 'sdcard0' might just be there to make it easyer for devices with like SGS2 with 'dual sdcards'

    • http://www.AndroidPolice.com Artem Russakovskii

      That's a possibility, sure.

  • Terry

    the leak looks like a prototype.. if it were the tmobile 32gb variant of the nexus, it would be running the current OS 4.0.4, i would assume anyways.
    its a really awesome rumor that begs people to pick their brains.

    i HOPE it is JB 5.0. but it isn't i am sure more rumors will surface soon enough

    • http://www.AndroidPolice.com Artem Russakovskii

      Just because it's a T-Mobile variant doesn't mean it has to run 4.0.4 - the point is, if this log is indeed real, it's obviously a developer device from someone on the Android team running the next major version of Android.

      • Phyxius Debello

        i truly hope you are right that it is a dev device.. i am sporting the Gnex GSM on Telus flashed to yakju, and i am just itching to see the new OS and the phone too. lets hope it comes out before Q4

  • Jake

    I'm willing to bet takju isn't a hardware revision, but instead a software variant

    Think yakju and yakjuux (or any of the carrier variants.

    It's the same hardware just getting updates from a different place.

    • http://www.AndroidPolice.com Artem Russakovskii

      I wouldn't be so sure.

      http://en.wikipedia.org/wiki/Korean_alcoholic_beverages lists soju, yakju, and takju as separate Korean alcoholic beverages. Takju in that sense might just be different enough, more different than variants of yakjuSOMETHING.

      • Scott

        The Galaxy Nexus hardware IDs are maguro and toro. yakju and mysid are the software IDs.

        So if it says it's maguro (which it does), then it's not different hardware.

        • Jake

          Exactly my point, and as was mentioned in a comment earlier, the takju alcohol gets refined into yakju.

          My suspicion is its an in house test branch for Google employees.

          So tempted to change my build.prop to takju and see if anything happens :P

  • Ian Stephenson

    Could be the Sprint Galaxy Nexus (But JellyBean? Naw..). The Sprint Nexus S was way off from the true Nexus S. Maybe it's the same deal here.

    • Jameslepable

      more likely gsm/LTE varient For ATT

  • Roland Stranneborn

    Could it be that Jelly Bean somehow can map cloud storage directly, i.e. treat it like it was an SD card? So /storage could be the most interesting piece here.

    • fonix232

      I don't think so, it would rather be targeting devices with more storage options (tablets, with USB, or any device with USB host function), to have a generic, standard way of accessing the file systems (like, Asus uses the folder /Removable, etcetera).

  • mistawha

    Hmm, with the "no comment" and that suspisious revision number. I think you may be looking at crash log from the prototype of the nexus tablet. BTW, I'm almost 100% sure, don't ask.

    • Roland Stranneborn

      But wasn't Asus supposed to build it? This looks more like a Samsung device, some GN variation.

      • Paul

        JB may debut on the Galaxy Nexus on phones and on the Asus Nexus tablet at the same time, or on the phone a day or few later.

    • http://twitter.com/DasErdbeer DasErdbeer

      But then what about:
      DEVICE=maguro

    • http://www.AndroidPolice.com Artem Russakovskii

      What? It says Galaxy Nexus numerous times, let alone all the codenames. This is most definitely not a Nexus tablet.

  • Zaeem S.

    Well, I'm sure that this news doesn't really make a bit of difference in our lives. Phone companies will be furious, though. Only 2% of the Android community uses ICS and carriers and phone companies are putting all their effort into upgrading phones to ICS. Releasing Jellybean too early would create a lot of hate towards Android. The issue of fragmentation will continue and no one would move forwards.

    Although, as an Android fan, I simply cannot wait to see what Google have up their sleeves for Jellybean. ICS was such a beauty! :D

    • Jordan

      I believe that these quick updates are google's way of telling hardware manufacturers (samsung/moto/htc/etc) to GTFO with their skins.

    • fonix232

      This skinning stupidity really drives many of my friends insane. Their Galaxy S', S Plus', HTCs, etc, won't get updated because they are making the stupid skins (btw, a nonprofit group of developers + Xiaomi successfully outed a fully theme-able and pre-themed ICS ROM after the source code release, so I can't see why other companies can't do the same), what makes the phones laggy and less awesome in most of the cases.

      Plus add please, that the sold Android devices are getting to be more and more of these chinese Shenzhen tablets/phones. Those come with 2.2 or 2.3 best case (except a few new models, with higher price labels), so they add a high percent of non-ICS to the whole.

      Releasing Jelly Bean, if it doesn't bring too much updates and innovations, won't be anything big. It will only do some little changes, but I would love to see something Cornerstone-y implemented (Dianne Hackborn mentioned not liking and implementing CS because of various questionable reasons, and I presume they are making their own version of it in Google-style), or Asus's Padfone's screen-switching capability (so when I connect my phone via HDMI/any other link to my TV, I can get a whole tablet/desktop UI), and this storage method update seems to be a big change. Maybe introducing support with Linux mainstream 3.3 (what already has the Android drivers), GUI and browser enhancements (although I have no idea of how a GUI update would be possible, except maybe bringing back the HC-style click-on-notification-to-show-that-one thing for tablets (I loved that and miss it from ICS)), and some small changes to get out of the legal hassles with Apple (like they did with the slide-to-unlock feature).

    • http://codytoombs.wordpress.com Cody

      Why does everybody bang this drum, as if there shouldn't be improvements in the OS?

      First off, Google announced some time back that they wanted to do significant releases every 6 months (or so). If OEMs have a problem with that, then they are the ones who need to plan/account for it, not Google.

      Second, as we've seen for a while now, it's only the major version upgrades that tend to involve breaking changes. As it's been speculated for a while, Jellybean is likely to be a point upgrade (making it 4.1). Surely there will be new features and improvements, but the average user isn't likely be to able to recognize them like they would the changes from GB to ICS. That means the only people who are going to be disappointed/angered/whatever are the developers and people commenting here who are desperately eager to be running the latest version ;)

      Third, while nobody talks about it this way, the fragmentation issues are actually getting better. Consider how many devices never got updates from 1.x to 2.x, and even among the ones that did, some took more than a year to see that jump and many people didn't even know if their phone would get the upgrade. From 2.x to 4.x the percentage of phones getting the bump is higher (within common sense constraints), the list of devices has been announced (albeit certain carrier variants are still unconfirmed) and everything getting the bump will be within a year of the original ICS source release. Is it perfect...nope, but it's getting better, and will be substantially better now that each company is restraining themselves from putting out 25-30 distinct models each quarter.

      Fourth (just for laughs), how annoyed will people be if they don't see Jellybean for a long time? These micro-improvements to ICS have become pretty dull. Excitement for the platform only persists if something is happening on a regular basis. Like you, I'm definitely looking forward to seeing what they've got to show off next.

      • george

        Google has said that Jellybean will have all the things they took out of ICS. It is not a small upgrade by any stretch.

        • http://codytoombs.wordpress.com Cody

          I think you misunderstood what I wrote or you meant to reply to somebody else. I didn't say that it was a small upgrade, I said that the changes aren't going to be recognizable by the average joe (and that they aren't likely to be breaking changes, that's more of a developer thing). Point updates can be massive like 2.1 -> 2.2 but most regular people only recognized that Google added the wifi-hotspot feature. I have a bunch of friends who still complain they couldn't understand what was so important about the GB update, they still think it's nothing more than security and bug fixes.

          The statement about a lot being held back from ICS was never an official statement (in fact, I can't find who is quoted other than "sources"), and we still don't know that any of those "game-changing" features are actually coming in JB. I believe a lot is coming in the way of new features, and that's likely to be a big deal, but it's almost certainly going to be atomic features. By that I mean they are features that run mostly by themselves and are more on the surface and less integrated at the core (much like wifi-hotspot was). Surely they'll be adding some new API's, but again they are more likely to add entirely new capabilities and perform small fixes than modify existing in any really significant way.

      • Athishay

        I'm guessing you have an Inspire 4G..

        • http://codytoombs.wordpress.com Cody

          That's not the only example of a carrier variant that's unconfirmed...but yeah ;)

          By the time the official update comes out for the Desire HD I'll have already moved onto a new phone.

  • Dami

    Could this be pointing to the next Nexus device? If so, with the "Galaxy" name, Samsung had successfully made a three-peat

  • Adam

    This type of analyzing is why I love AP. Nicely done...good read :)

    • Kenny O

      +1

      My thoughts exactly.

  • Geoff

    Galaxy Nexus Tablet maybe?

  • Geoff

    Oh, Nevermind. I didnt see Artem's comment.

  • Alex Sandy

    This got more interesting...

  • Dami

    Could this be a global LTE 32GB variant?! *Crosses fingers*

  • Noboody

    or it could be an internal version number or revision control's version - in fact, if I didn't know any better and the Android team didn't use git, I'd say it's an SVN revision number

    Definitely wrong. It's well known that they use Git and there's no way in hell you could run a project like Android on a non-D-VCS.

    • http://www.AndroidPolice.com Artem Russakovskii

      Yeah, as I said if I didn't know any better, but thankfully I do.

      I got the answer though: it's a build number (or rather, sequence code), which doesn't have a 1:1 mapping to commits - some commits don't trigger a build, and some commits can trigger multiple builds.

  • Kaik541

    to me, it seems pretty obvious this is a GSM/LTE variant. all GSM variants are "yakju" (whether yakjuxx or yakjuug or whatever) and all CDMA/LTE variants are going to be mysid in similar way. my money's on a GSM/LTE version for carriers like AT&T (what with the also recent rumors of AT&T handing out LTE SIM's for testing with the galaxy nexus).

  • http://beerpla.net Artem Russakovskii

    FYI, I have chosen this quiet Saturday night to finally migrate to DISQUS (over a year in the making), so the comments on a few posts like this one should be missing for a few hours until they sync correctly. It's kind of a pain, but should only be a one-time thing.

    • bl0wf1sh

       Good move to disqus... it's a bit more user-friendly. Sadly, however, it also means I cannot read comments at work (disqus is blocked).

      Cool thing about the JB rumor. I am personally thinking it may be my next phone... the Jelly Bean "Google Phone" (if there still is one). Unless, maybe, it's LG :D

      • John

        disqus is blocked? strange

        i mean...i get why i guess...but weird =/

  • http://twitter.com/MrYuzhai *Certified_geek™

    or takju could just be a typo.. you know with the t & y being next to each other.. o_0

    • http://www.androidpolice.com/ Artem Russakovskii

       It wasn't.

    • Limwooseok92

      It's a korean word.

      Soju, Yakju, Takju is for names of korean alcholic drinks :)

      As i'm a korean i usually drink them so I know it!

  • Simon Belmont

    I love these in depth articles. Very well done, Artem.

    By the way, thanks for switching to Disqus finally. It is a Godsend.

    • http://beerpla.net Artem Russakovskii

      Oh, you don't even know the half of it and what it took to get this move done.

  • fixxmyhead

    Good thing im going to school in the summer for programming so ill finally be able to know what all that code jargon is

    • NotRelevant

      Too bad that won't help you since there was no code there. Nice try though.

      • fixxmyhead

        This was like a month ago Why are u even responding. Sad that I'm responding to u

  • BlackPearl

    new android version, applications still crash .. don't tell me beta please, 
    windows 8 is more stable than 7, and it's beta .. google fix this crap please.

    • warcaster

      Apps crash most of the time because of how they were coded by the developer, not because of the OS. That's why you almost always hear about apps or programs having "bugs". But OS-wide, it was even shown that iOS has 2-3x more crashes than Android. But I guess most people don't realize it because you don't get warned in iOS when there's a crash.

      Also this is an unreleased alpha version of an OS version that's been in the workings for months. Windows 8 has been in development for 3 years, and it's actually very close to release. They're mostly just waiting for manufacturers to put it on their hardware and see what bugs come out of that before they actually ship it.

    • NotRelevant

      Because app crashes are totally the fault of the OS. Come on get real.

  • strra

    i don't know, this just screams fake to me

    • http://www.androidpolice.com/ Artem Russakovskii

      Wasn't fake after all.

  • Christopher Orr

    The AOSP folk posted a guide to the build IDs here: http://source.android.com/source/build-numbers.html

    So, JRN12B identifies the second release build from the Jellybean branch built on April 12th this year.
    The JRM79 ID you saw would be a build from mid-March.