Mid-July: it's between Early July and Late July

I'm a lucky man.

As the technical lead of a major Open Source project, I often get questions about future release dates. Since I can't actually answer those questions, they're a little bit annoying.

I'm lucky to actually get those questions. Those questions mean that I have users who care about my project. They mean that a few days or a few weeks make a difference. They mean that I work on a project that matters.

Really, the worst possible scenario for me would be to find that suddenly nobody cares about Android any more. I'd be very sad if nobody was downloading from our servers any more, if nobody was uploading contributions, if nobody was reporting bugs or submitting feature requests.

So, I appreciate it when people can wait quite patiently, but I also smile when people ask about future releases, even though I can't answer. Keep being patient, and keep being impatient!
Matthew Beckers's profile photoFlorin Chisacov's profile photoUmut Çelik's profile photoJean-Baptiste “JBQ” Quéru's profile photo
Come on, spill the beans: WHERE'S THE SOURCE. :O

Don't make me use my Nokia-made torturephone. You know how tough it is.

I'll always care about android..
Is the rollout global or we Asians have to wait for many more moons anyhow?
So, that means you're releasing it tomorrow, right?
Im not too worried about having to wait for JB for my One X... but I do have to wonder why AOSP Android is so lacking? Simple things like a countdown timer... used to run AOSP ROMs but got sick of trying to find decent market apps to give my phone basic functionality that even every feature phone ships with
+Meng Shen Lim - I'm only responsible for the Open Source distribution, and that's always global. I don't know what the schedule is for the individual rollouts to the various consumer devices, sorry.
+Jean-Baptiste Queru Thanks for the info, would flash the update manually anyway via CWM. I still got my OTA update quite late although there is no carrier restriction rules on phone updates in place where I live. 
Don't know if this applies to you or not +Jean-Baptiste Queru, but  *major* thanks for continuing to support the Xoom. The thing's been a dream since official ICS hit, and I can't wait to get Jelly Bean this month. Super curious how it's going to look/work at 10-inch.
+Jean-Baptiste Queru How do you feel about all this injunction madness going on?  I had one ordered as an anniversary gift for my wife.  She was really looking forward to it too...  Not sure how I'm gonna break the news to her
+Jean-Baptiste Queru will the builds of the nexuses other then the takju and yakju build like the yakjuzs and others get the JB update at the same time since they are also gsm unlocked or will they have to lag behind months like they've had to do with the 4.0.4 update
Agree with +Skye Harris on the timer thing. My one gripe with Google Now is that when you set a timer it just sets an alarm, but doesn't clean up after itself, so it gets cluttered with arbitrary times. WHY NO ONE MAKE TIMER? lol
Carry on with the good work +Jean-Baptiste Queru. Besides the folks who impatiently want the latest release in days and weeks, there are folks who wait months and years - patiently but hopelessly - for their OEMs to do something. Only the folks at AOKP, XDA-Developers, CyanogenMod and their kind finally do come to the rescue - and are so appreciated!
+Skye Harris - Well, in a way, that's the tyranny of having the Google Play Store: Android doesn't fundamentally need that functionality in the OS, since there'll be plenty of 3rd-party apps that'll do that.

At my level, in AOSP, things are surprisingly simple: if there's a decision to ship a certain app on a flagship device, and if there's a decision to make that app Open Source, it ends up in AOSP. Otherwise it doesn't. I have essentially no influence on what makes it and what doesn't.
+1 to the mid-July part. It made me laugh. I figured Jelly Bean would be out in July, I have no further questions. :)

Really looking forward to JB and Google Now on my Nexus S.
+Gerrell Blake - Sorry, those days I pretty much only keep track of the status of the builds for the devices sold on Google Play, so I don't know the exact target date for every single variant (and if I did I couldn't tell anyway).
Te he "spill the beans" I get it.
+Skye Harris if AOSP or the Google Play Store doesn't have what you need, then you should just stick with stock. Nobody is forcing this or anything else on you. Move on and find what you need elsewhere.
+Jean-Baptiste Queru the problem is it is then left up to the user to go through countless apps that don't end up working properly, until they find one that does. I went through about a dozen timer apps before I found one that continues the count-down while the screen was off. I then had the issue that the ones that actually worked were not aesthetically pleasing, and really did not fit in with the holo theme at all.

I have discussed this with many local Android users, most of whom were using either Nexus devices or AOSP ROMs, and they all agreed about the small basics that stock Android lack. App store or no app store, very basic features of pretty much any phone from the last decade are missing from Android.

Another example is a smart dialler.. AOSP (when I last used it at least) did not have a smart dialler built-in. These are however much easier to find working replacements for on the market than a count-down time, but I still had trouble finding one that would fit in well with holo.

Little things like this are what is missing from stock Android IMHO. Yes, you can eventually find apps that will give you this functionality, but how many end users WANT to have to search the market and try a dozen or more apps to find something that provides functionality that has been basic stock functionality on pretty much all their prior phones in the last decade? Just because they can, doesnt mean they should have to, or that they even want to. 

+Kwasi Bunsie so.. If I don't like that stock Android lacks basic features of pretty much any phone from the last decade, I should stick with stock? Stock what? Stock Android? That is exactly the problem, and it is a legitimate concern and one that is not held only by myself. If you instead mean stock ROM on my HTC phone, well yes it does suit my personal needs more in its current state (though my device is not running stock firmware), but that does not in any way make my concerns regarding stock Android functionality any less legitimate
He smiles, but never talks? Folks, we've got the gods-damned Mona Lisa up in this piece.
+Jean-Baptiste Queru how about if I were to flash the google play version build would that therefore put me in line with those same versions
You're work defiantly matters!  I appreciate the effort you put in and also how you directly answer questions when developers who are learning, like myself, ask a question you've probably answered a million times.  Keep up the good work!
+Gerrell Blake - That's definitely not recommended. There's some coupling between the exact hardware and software variants, and doing a mix-and-match is known to cause issues. What's worse, if something goes wrong, you might not be able to go back to a state that works.
Ha! +Meng Shen Lim if your "many moons" is a direct translation.  I like it!  :)  That said.  After a few hardships of getting a good rom of Jelly Bean on my Galaxy Nexus.  I'm definitely happy now that I have a perfectly functional version on my (US Verizon) Galaxy Nexus. (JakeDay's 1.9)
+Jean-Baptiste Queru so my only option is to wait for whoever it is to get around to updating our nexuses??? Can you help explain to me what are the differences to why it takes months for one nexus to get a update while the other receives one immediately being that they both the same gsm unlocked nexus
+Jean-Baptiste Queru despite having big respect to you and your work, I believe that reason why people are asking is because of retarded skins from hw vensors and they inability to push updates in reasonable time :-)
+Gerrell Blake - I don't have a precise answer for you. I know that there are process differences between the variants, which cause the differences in release dates, but that's so far away from my own job that I can't actually get into the details.
+Jean-Baptiste Queru Nice post. In the spirit of caring, may I offer one small bit of feedback? I'm using the developers preview of Jelly Bean and, while it's excellent, it appears the landscape keyboard has been shrunk vertically. This has destroyed my typing accuracy and has made what was once a very nice typing experience into something very tiresome.
+Jamie Spraker I know Swiftkey is very popular but I don't care for it. Actually I've never found a replacemrnt keyboard I did like more tha tbe stock ICS one.
The beauty of Android, SwiftKey or not, switch it out. Your very graphic about the stock keyboard you like?.? Switch it out or flash a rom with a fix
+Jamie Spraker I'm not sure if you intended a hostile tone or if I'm just misreading it. In any case, I was just hoping to offer some feedback since Jelly Bean is currently in a preliminary state; if I'm having trouble with the new layout, others may also.
Very appreciative of all the devs work on Android and the systems that surround it.  Obviously wish we could have the goodies faster of course, but happy to wait for extra perfection to be added on existing perfection! ha!
+Jean-Baptiste Queru , why don't you have a policy of releasing beta/RC versions of AOSP earlier on (like when they are announced)?. I'd think that a bit of free qa from the community would be a good thing :)
+Jean-Baptiste Queru If you had your master development branch public all the time (instead of just merging it from time to time in a public visible repo) you could have both a semi-automatic answer to the release question (people can guess if it is ready) and pull statistics to warm you.
I agree that it's cool to know that people care about your project, but I feel that the Android community has a lot of self-entitled whiners who refuse to acknowledge how product development works. For example, recently there has been a lot of pointless drama over US Galaxy S3 release dates. People are making posts asking things like "why can't Verizon just ship us all our devices," ignoring the fact that there's so much QA and certification work that goes into making sure a device is ready to go out into the hands of consumers. The whining about software updates from manufacturers or from Google is equally pointless and I wish people would stop doing it.

I also wish Android would move to a completely open development model, but I can accept that there are very good reasons that it isn't this way.

I guess in an ideal world you guys would announce new OSes the same day you were ready to release them, but I understand that software development never works out the way you want it to so doing that would be hard.
+Ibrahim Awwal There are definitely whiners in this space, but that is true of any space. I think the key is to engage where the comments/queries/requests/complaints/what-have-you are reasonable and ignore all else as serenely as possible. That's the closest one will get to an ideal world. It's a Zen thing. :)
Whatever happened to the Android platform alliance that supposedly committed to keeping phones current?
Can you tell what commit we need to un commit to get the full features of the new google now? That or a comment in the code saying apple sux un comment this to get the full experience!
+Jean-Baptiste Queru What did you mean by the nexus s is still the preferred aosp development phone? Is it in more hands than the galaxy nexus?
+Viktor Kojouharov - That's really a strategic question, not a technical one, so I can't answer it. Such changes, when they happen, are likely to be made in small steps. As an example, we've distributed devices at Google I/O with a developer preview, and we're keeping an eye on how things evolve from there. That's a baby step, and based on what we hear back we'll have data to help us decide what to do next.
+Alex Riesen - That's quite true indeed. However, there would also be some very significant strategic, business, legal and even technical drawbacks to working entirely in the open. We'll continue making baby steps in that direction, as appropriate, and for Jelly Bean we'll be moving CTS development back in the open.
Thanx I was wondering what mid meant... seariously though people the longer you have to wait the better it will be!
+Skye Harris I personally prefer an AOSP version that's as stripped down as possible. I don't need any frills on my device. I prefer to add functionality missing from AOSP through apps. It's a great way to discover other apps that I wouldn't have previously thought to try, supporting the developer community which ultimately leads to more possibilities and features available to the end user: me.

I won't run a stock build when Cyanogenmod is available for any phone I own. I only purchase CM-supported devices because I feel that the bloat from Sense and Touchwiz and others inhibit the potential of the devices by making them look cool with transition animations and other miscellany that aren't necessary. (I also think the holo look is far classier.)

As far as crappy apps go, a suggestion if you're not a developer is to post requests for apps with the features you're looking for on rootzwiki or xda.
I want it before I leave for another country!
When are we going to get a battery percentages status in our status bar on stock android? Come on. Cyanogenmod has had it for years. Aside from that one gripe you guys are doing GREAT work! Keep it up!
Jean-Baptiste - as long as you guys will keep innovating in the right direction, project will evolve. But our questions usually lead this direction, where you should go next, so they are more or less rhetorical, and answers should be in your code. Thanks for your effort!
Preparing my source tree to merge in the changes, looking forward to the release! :)
+Jean-Baptiste Queru I'm leaving the country by mid July, so I don't if I'll be able to receive the update on my Nexus S before I leave. Will the update still be available when I get back in September, when I sign into my wifi? Or is it game over for me? Thanks
+Jean-Baptiste Queru Are you allowed to disclose whether the Nexus S will have Google Now? I'm curious since it has hardware buttons.
It's alright then. Don't want you to lose your job.

sidenote: It's also nice to see the Nexus 7 doing well in sales. I pre-ordered the day before yesterday and shipping time went from 2-3 weeks to 3-4 weeks.
I don't suppose you know ( and can answer ) this, +Jean-Baptiste Queru but do the "report" buttons for core apps ( camera, clock, etc ) go somewhere other than /dev/null ? I've been getting occasional crashes with the clock alarms, causing me to miss doses of meds. :S
That's OK, thanks for the prompt reply.
Can't wait for mid-July..whenever that is..! Does this mean now you're working on KLP now? ;)
Right now I'm working half-and-half between Ice Cream Sandwich and Jelly Bean, and I don't know the code name for the next release yet, it's too early for that.
I like klmp , what about kiwi? Its a good morning dessert.xD
Apparently The Verge received a tip from their source back in March that Jelly Bean will be followed by Key Lime Pie. They also claim it's from the same source that tipped them about Jelly Bean last year.
I hope I'm alive to see the build after Zabaglione.
+Gerrell Blake Given that Samsung Germany released a tool that flashed phones running yakjuxw to yakju you should be fine if you flash another build, provided you know what you are doing and how to fix it if you mess up (clue: backup stock rom and learn how fastboot/recovery works). The exception seems to be the NTTDocomo phone (which seems unable to run on certain frequencies) but that's not even an i9250.
Can't believe I forgot to +1 this post when I first saw it earlier today.
+Renaud Lepage It used to be available here:


It seems they have removed it now since it was old. It's mirrored below though and still works fine as far as I know. It's using a light-weight version of Odin to flash the stock yakju image without unlocking the bootloader.

+Jean-Baptiste Queru One thing I've been pondering since your eloquent overview of the update process a month or so ago: While ETAs/behind the scenes details are under NDA for obvious reasons, does that apply to the general status of a publically known update within its lifecycle (Development -> Carrier approval -> Rollout)?  

It seems to me like an implementation similar to Nokia's (http://www.nokia.com/global/support/software-update/lumia/europe/availability/) for the various Nexus variants linked from the Nexus home page would drastically cut down the number of "wheres my nexus update???!!" enquiries you get, since a large part of the problem is lack of centralized information. Is this theoretically possible, or do license agreements make this a pipe dream?

Fully understand if I've crossed into stone wall territory, but just wanted to throw it out there anyway. 
+David Lawerteh - That's really a business issue, not a technical one, so my answers aren't going to carry any weight.

Personally, I'd be surprised if anything happened in that domain. I know that some Android OEMs have tried to be transparent in that domain, and got a lot of blowback when they had to change their plans. Based on that, I'd be surprised to see any communication until there's absolute certainty about it, and the only time when there's absolute certainty about a release is when it actually ships.
So, will Google be able to roll it out for Verizon's Galaxy Nexus too? If not, I, as a lawyer, wouldn't have left that 'out' available for Verizon...
+Jean-Baptiste Queru +Alex Riesen That it doesn't work with the Galaxy Nexus... Isn't it an issue that needs fixing? Or will we continue to use an, I hate to use the term, aging device? ;)
+Edward Higgins What he means is that more of the binary blobs (drivers) for the Nexus S can be legally distributed by Google. If you restrict yourself only to using those instead of also pulling in the rest from the device, you'll end up with more working features than the GN. If you pull them from the device or ROM you'll have full AOSP compatability with the GN too though.
+Jean-Baptiste Queru - I guess "Mid July" has arrived!

Thanks for the spilling the (Jelly) Beans. Definitely +1000 for updating AOSP so quickly.
+Jean-Baptiste Queru very disappointed that the sprint gnex will not get support for jelly bean so that means that we will have to run ported jelly bean roms that have major flaws like no MMS.....bought this phone because I thought I was getting the full Google experience but guess not
+Jean-Baptiste Queru - i was wondering will jelly bean be available for my motorola droid bionic on verizon? or is that a matter of ehen they make it available.
oh and i am excited hearing this news.
Weren't you big in the BeOS camp years ago? Loved that damn OS - miss it so much :(
Cool. I remember emailing Gassee offering to fly myself to CA for free in return for a job! Any involvement with Haiku?
I remember installing BeOS on a PPC Mac from a floppy set..and later on watching the mail for cd's..seems like we're always waiting for "newer and better".. I wonder if Haiku would run on my CR48?
+Jean-Baptiste Queru Since it's starting to roll out via OTA now, I am still seeing the usual "did you get the OTA" threads all over XDA and such. Is there an official way for a pure-stock Galaxy Nexus to trigger the OTA? I could very well unlock my bootloader or root, but in the past, I've been caught up flashing ROMs far too much, and I like being completely stock. If there was just a way to "opt-in" and get the OTA, that would be awesome! (maybe future release?)
+Andy Christianson - there's no way to fully trigger the OTA manually. On the OTA servers, devices are randomly separated into the schedule buckets. As long as your device isn't eligible on the server side, you won't be able to trigger an OTA. Once your device is eligible, you'll get the notification the next time it asks the server if an OTA is available (normally every few hours).
+Jean-Baptiste Queru Thanks for the response! Good to know I'm not crazy. Lots of people trying to suggest that clearing data on the Google Services Framework and force stopping it would let you check for an update and it would somehow "work". Seems hokey.

I'll go back to being patient =)
+Jean-Baptiste Queru about those scheduling buckets... approximately how many devices are in one bucket? And what's the time interval between allowing the next batch of devices to download the OTA? thanks :-)
Speaking of OTA's. When do you assume Jelly Bean factory images will arrive?
I hope in the future the more technical users have an easy option to just download the update and push it to the device manually (i.e. w/o unlocking bootloader and such).
Ok, thanks for the answer anyway :-) I'll just be patient :-)
As long as your device isn't eligible on the server side, you won't be able to trigger an OTA. Once your device is eligible, you'll get the notification the next time it asks the server if an OTA is available

+Jean-Baptiste Queru Wait, so why don't all devices get it in the same day? Are there other factors besides make/model/build that determines eligibility? And how does a device suddenly become eligible when it's still the same device?

Maybe it's just semantics tripping me over, or something I'm overlooking
+Jean-Baptiste Queru I see. Now another question, if you don't mind..
Why does android still poll for updates? Is C2DM'ing update notifications in the works?
Any Idea when the Gnex Yakju will get the update? so far only the takju got 4.1.1 and so far I havent seen any gnex yakju with OTA 
Thank you I will XD! but as u can see we all are very impatient to get JB! but I will wait for OTA! hope it doesnt take 4 weeks like 4.0.4 update from 4.0.2 ! XD
Ive been clearing my services framework and checking for updates like 20 times a day since the ota was announced. Does this urban legend even work and Is there anyway I can get it faster I need jelly bean in my life. 
+Nicholas Fanello read JBQ's response a bit further up. There is no way to force trigger the OTA for your device. I doubt the framework trick helps at all. However, there is a theory that when you check for updates your response is "cached" for a period of time, causing further checks to get an automated response of "this is what I told you last time". Clearing the service framework data may prevent the caching but that's all it does. You still won't be able to get the OTA until your device is scheduled server-side.
Can't reallyyy wait for the OTA. Just one question; devices are being scheduled on the servers for OTA according to what? Serial numbers? Someone knows?
ugly way to update , it is posted change anything ...
One last question, randomization made by serial numbers or imei s ? :)