I'm pushing the source code for Android 4.0.3 to AOSP. This matches build IML74K. Kernel sources will follow as soon as practical.
Over the years, I've released 50 different versions of Android in AOSP, not counting the SDK and CTS, and I think that this is the best release ever.
Some noteworthy items:
-This version of Android is optimized for a wide range of devices. It works on phones. It works on tablets. It works on devices that don't quite have the horsepower of a Galaxy Nexus.
-From a straight AOSP, it works on Galaxy Nexus (the ones sold with mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus S (all variants). Proprietary binaries will soon be available for those devices at the usual location.
-Out of the box, this is the first time that AOSP works on 3 different device families, the first time that it works on tablets, the first time that it works directly on a device that's neither an ADP nor a Nexus, and the first time that it works on Verizon devices.
> I'm pushing the source code for Android 4.0.3 to AOSP. This matches > build IML74K. Kernel sources will follow as soon as practical.
> Over the years, I've released 50 different versions of Android in > AOSP, not counting the SDK and CTS, and I think that this is the best > release ever.
> Some noteworthy items:
> -This version of Android is optimized for a wide range of devices. It > works on phones. It works on tablets. It works on devices that don't > quite have the horsepower of a Galaxy Nexus.
> -From a straight AOSP, it works on Galaxy Nexus (the ones sold with > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus > S (all variants). Proprietary binaries will soon be available for > those devices at the usual location.
> -Out of the box, this is the first time that AOSP works on 3 different > device families, the first time that it works on tablets, the first > time that it works directly on a device that's neither an ADP nor a > Nexus, and the first time that it works on Verizon devices.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
On Fri, Dec 16, 2011 at 1:53 PM, Jean-Baptiste Queru <j...@android.com> wrote: > I'm pushing the source code for Android 4.0.3 to AOSP. This matches > build IML74K. Kernel sources will follow as soon as practical.
> Over the years, I've released 50 different versions of Android in > AOSP, not counting the SDK and CTS, and I think that this is the best > release ever.
> Some noteworthy items:
> -This version of Android is optimized for a wide range of devices. It > works on phones. It works on tablets. It works on devices that don't > quite have the horsepower of a Galaxy Nexus.
> -From a straight AOSP, it works on Galaxy Nexus (the ones sold with > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus > S (all variants). Proprietary binaries will soon be available for > those devices at the usual location.
> -Out of the box, this is the first time that AOSP works on 3 different > device families, the first time that it works on tablets, the first > time that it works directly on a device that's neither an ADP nor a > Nexus, and the first time that it works on Verizon devices.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
> I'm pushing the source code for Android 4.0.3 to AOSP. This matches > build IML74K. Kernel sources will follow as soon as practical.
> Over the years, I've released 50 different versions of Android in > AOSP, not counting the SDK and CTS, and I think that this is the best > release ever.
> Some noteworthy items:
> -This version of Android is optimized for a wide range of devices. It > works on phones. It works on tablets. It works on devices that don't > quite have the horsepower of a Galaxy Nexus.
> -From a straight AOSP, it works on Galaxy Nexus (the ones sold with > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus > S (all variants). Proprietary binaries will soon be available for > those devices at the usual location.
> -Out of the box, this is the first time that AOSP works on 3 different > device families, the first time that it works on tablets, the first > time that it works directly on a device that's neither an ADP nor a > Nexus, and the first time that it works on Verizon devices.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
I have a Moto Xoom (Stingray) ... isn't a 3.0 kernel required for this to work (? properly), and if so, have the necessary Stingray bits been pushed anywhere?
The branch for IML74K is android-4.0.3_r1. The development branch is ics-mr1, and as usual it's also all merged into master.
If you build for toro (i.e. CDMA/LTE Galaxy Nexus), you'll have partial functionality (graphics, wifi, audio, sensors), but others are missing at this point (CDMA/LTE, camera, GPS). Google is working with the various companies involved to secure distribution contracts for the missing binaries as quickly as possible.
On Fri, Dec 16, 2011 at 1:57 PM, jdkoreclipse <jdkorecli...@gmail.com> wrote: > So, i can build for the LTE Galaxy nexus nd have everything work?
> Also, what branch is it?
> On Dec 16, 4:53 pm, Jean-Baptiste Queru <j...@android.com> wrote: >> I'm pushing the source code for Android 4.0.3 to AOSP. This matches >> build IML74K. Kernel sources will follow as soon as practical.
>> Over the years, I've released 50 different versions of Android in >> AOSP, not counting the SDK and CTS, and I think that this is the best >> release ever.
>> Some noteworthy items:
>> -This version of Android is optimized for a wide range of devices. It >> works on phones. It works on tablets. It works on devices that don't >> quite have the horsepower of a Galaxy Nexus.
>> -From a straight AOSP, it works on Galaxy Nexus (the ones sold with >> mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus >> S (all variants). Proprietary binaries will soon be available for >> those devices at the usual location.
>> -Out of the box, this is the first time that AOSP works on 3 different >> device families, the first time that it works on tablets, the first >> time that it works directly on a device that's neither an ADP nor a >> Nexus, and the first time that it works on Verizon devices.
>> Questions sent directly to me that have no reason for being private >> will likely get ignored or forwarded to a public forum with no further >> warning.
> -- > You received this message because you are subscribed to the "Android Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> I'm pushing the source code for Android 4.0.3 to AOSP. This matches > build IML74K. Kernel sources will follow as soon as practical.
> Over the years, I've released 50 different versions of Android in > AOSP, not counting the SDK and CTS, and I think that this is the best > release ever.
> Some noteworthy items:
> -This version of Android is optimized for a wide range of devices. It > works on phones. It works on tablets. It works on devices that don't > quite have the horsepower of a Galaxy Nexus.
> -From a straight AOSP, it works on Galaxy Nexus (the ones sold with > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus > S (all variants). Proprietary binaries will soon be available for > those devices at the usual location.
> -Out of the box, this is the first time that AOSP works on 3 different > device families, the first time that it works on tablets, the first > time that it works directly on a device that's neither an ADP nor a > Nexus, and the first time that it works on Verizon devices.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
> -- > You received this message because you are subscribed to the "Android Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
That is correct, the timing for yakju and mysid factory images matches that of consumer OTAs. Note however that I've explicitly configured and tested the source tree so that it's possible to flash 4.0.3 on a device that has either the 4.0.1, 4.0.2 or 4.0.3 bootloader and baseband, so there shouldn't be any hurdle in building 4.0.3 from source and running on a support Galaxy Nexus, then restoring the device to the official ICL53F.
For reference, I've also tested the crespo and crespo4g builds on every past bootloader and baseband.
<michal.bans...@gmail.com> wrote: > If I remember correctly, factory images of IML74K for mysid or yakju > will be available once those devices get official OTA, is that > correct?
> 2011/12/16 Jean-Baptiste Queru <j...@android.com>: >> I'm pushing the source code for Android 4.0.3 to AOSP. This matches >> build IML74K. Kernel sources will follow as soon as practical.
>> Over the years, I've released 50 different versions of Android in >> AOSP, not counting the SDK and CTS, and I think that this is the best >> release ever.
>> Some noteworthy items:
>> -This version of Android is optimized for a wide range of devices. It >> works on phones. It works on tablets. It works on devices that don't >> quite have the horsepower of a Galaxy Nexus.
>> -From a straight AOSP, it works on Galaxy Nexus (the ones sold with >> mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus >> S (all variants). Proprietary binaries will soon be available for >> those devices at the usual location.
>> -Out of the box, this is the first time that AOSP works on 3 different >> device families, the first time that it works on tablets, the first >> time that it works directly on a device that's neither an ADP nor a >> Nexus, and the first time that it works on Verizon devices.
>> Questions sent directly to me that have no reason for being private >> will likely get ignored or forwarded to a public forum with no further >> warning.
>> -- >> You received this message because you are subscribed to the "Android Building" mailing list. >> To post to this group, send email to android-building@googlegroups.com >> To unsubscribe from this group, send email to >> android-building+unsubscribe@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en
> -- > You received this message because you are subscribed to the "Android Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
It means that you can use those devices for AOSP development. AOSP is different from consumer builds, so this is only recommended if you have an interest in working on the Android platform at the source level.
JBQ
On Fri, Dec 16, 2011 at 2:22 PM, Diego De Barbieri <diego...@gmail.com> wrote:
> So, that means that I can update my nexus S from AT&T NOW??? > And also my Verizon XOOM???
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
On Fri, Dec 16, 2011 at 20:56, Roman <romanb...@gmail.com> wrote: > Thank you for everything you do!
> On Dec 16, 3:53 pm, Jean-Baptiste Queru <j...@android.com> wrote: > > I'm pushing the source code for Android 4.0.3 to AOSP. This matches > > build IML74K. Kernel sources will follow as soon as practical.
> > Over the years, I've released 50 different versions of Android in > > AOSP, not counting the SDK and CTS, and I think that this is the best > > release ever.
> > Some noteworthy items:
> > -This version of Android is optimized for a wide range of devices. It > > works on phones. It works on tablets. It works on devices that don't > > quite have the horsepower of a Galaxy Nexus.
> > -From a straight AOSP, it works on Galaxy Nexus (the ones sold with > > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus > > S (all variants). Proprietary binaries will soon be available for > > those devices at the usual location.
> > -Out of the box, this is the first time that AOSP works on 3 different > > device families, the first time that it works on tablets, the first > > time that it works directly on a device that's neither an ADP nor a > > Nexus, and the first time that it works on Verizon devices.
> > Questions sent directly to me that have no reason for being private > > will likely get ignored or forwarded to a public forum with no further > > warning.
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
YES!!! Motorola XOOM! Looks like my laptop is gona have some use tonight :)
@JBQ: Will we have a "GO" message like when you did when pushing ICS?
On Fri, Dec 16, 2011 at 2:29 PM, Carlos Silva <r3...@r3pek.org> wrote: > On Fri, Dec 16, 2011 at 20:56, Roman <romanb...@gmail.com> wrote:
>> Thank you for everything you do!
>> On Dec 16, 3:53 pm, Jean-Baptiste Queru <j...@android.com> wrote: >> > I'm pushing the source code for Android 4.0.3 to AOSP. This matches >> > build IML74K. Kernel sources will follow as soon as practical.
>> > Over the years, I've released 50 different versions of Android in >> > AOSP, not counting the SDK and CTS, and I think that this is the best >> > release ever.
>> > Some noteworthy items:
>> > -This version of Android is optimized for a wide range of devices. It >> > works on phones. It works on tablets. It works on devices that don't >> > quite have the horsepower of a Galaxy Nexus.
>> > -From a straight AOSP, it works on Galaxy Nexus (the ones sold with >> > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus >> > S (all variants). Proprietary binaries will soon be available for >> > those devices at the usual location.
>> > -Out of the box, this is the first time that AOSP works on 3 different >> > device families, the first time that it works on tablets, the first >> > time that it works directly on a device that's neither an ADP nor a >> > Nexus, and the first time that it works on Verizon devices.
>> > Questions sent directly to me that have no reason for being private >> > will likely get ignored or forwarded to a public forum with no further >> > warning.
>> -- >> You received this message because you are subscribed to the "Android >> Building" mailing list. >> To post to this group, send email to android-building@googlegroups.com >> To unsubscribe from this group, send email to >> android-building+unsubscribe@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en
> YES!!! Motorola XOOM! Looks like my laptop is gona have some use tonight :)
> @JBQ: Will we have a "GO" message like when you did when pushing ICS?
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> On Fri, Dec 16, 2011 at 1:53 PM, Jean-Baptiste Queru <j...@android.com> wrote: > > I'm pushing the source code for Android 4.0.3 to AOSP. This matches > > build IML74K. Kernel sources will follow as soon as practical.
> > Over the years, I've released 50 different versions of Android in > > AOSP, not counting the SDK and CTS, and I think that this is the best > > release ever.
> > Some noteworthy items:
> > -This version of Android is optimized for a wide range of devices. It > > works on phones. It works on tablets. It works on devices that don't > > quite have the horsepower of a Galaxy Nexus.
> > -From a straight AOSP, it works on Galaxy Nexus (the ones sold with > > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus > > S (all variants). Proprietary binaries will soon be available for > > those devices at the usual location.
> > -Out of the box, this is the first time that AOSP works on 3 different > > device families, the first time that it works on tablets, the first > > time that it works directly on a device that's neither an ADP nor a > > Nexus, and the first time that it works on Verizon devices.
> > Questions sent directly to me that have no reason for being private > > will likely get ignored or forwarded to a public forum with no further > > warning.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
There's a kernel binary in the source tree, which you can use to run the platform. I'll be pushing the matching source tree as soon as I can.
JBQ
On Fri, Dec 16, 2011 at 3:29 PM, Kenneth Crudup <kcru...@gmail.com> wrote: > I have a Moto Xoom (Stingray) ... isn't a 3.0 kernel required for this to > work (? properly), and if so, have the necessary Stingray bits been pushed > anywhere?
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
On Fri, Dec 16, 2011 at 22:31, Jean-Baptiste Queru <j...@android.com> wrote: > The branch for IML74K is android-4.0.3_r1. The development branch is > ics-mr1, and as usual it's also all merged into master.
> If you build for toro (i.e. CDMA/LTE Galaxy Nexus), you'll have > partial functionality (graphics, wifi, audio, sensors), but others are > missing at this point (CDMA/LTE, camera, GPS). Google is working with > the various companies involved to secure distribution contracts for > the missing binaries as quickly as possible.
For Xoom: I know that the camera and HDMI don't work. The rest of the device seems functional (wifi, 3G, sensors, audio, OpenGL). There might be some trickiness with the variety of bootloaders and basebands, I haven't been able to test those broadly as Xoom is a bit ticklish in that domain and you might need to edit your board-info.txt accordingly.
Ubuntu: requirements haven't changed, 10.04 for the tagged version android-4.0.3_r1 and for the development branch ics-mr1, while 11.10 is expected to work for the master branch.
On Fri, Dec 16, 2011 at 3:37 PM, Carlos Silva <r3...@r3pek.org> wrote: > On Fri, Dec 16, 2011 at 22:31, Jean-Baptiste Queru <j...@android.com> wrote:
>> The branch for IML74K is android-4.0.3_r1. The development branch is >> ics-mr1, and as usual it's also all merged into master.
>> If you build for toro (i.e. CDMA/LTE Galaxy Nexus), you'll have >> partial functionality (graphics, wifi, audio, sensors), but others are >> missing at this point (CDMA/LTE, camera, GPS). Google is working with >> the various companies involved to secure distribution contracts for >> the missing binaries as quickly as possible.
> Any limitations on the Xoom?
> Does it build on Ubuntu 11.10 ?
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
Thanks JBQ for your incredible work and all of the android team members, just curious (and anxious, i know) but there is a timeline for the nexus s kernel sources to be uploaded?
Sorry for the question, but this was one of the most awaited releases from google :D
On Friday, December 16, 2011 3:31:10 PM UTC-8, JBQ wrote:
> ... but other [functionalities] are missing at this point .... Google is > working with the various companies involved to secure distribution > contracts for the missing binaries as quickly as possible.
If you've already got a unit and can extract the existing binaries, does that help? Other than video, are there big enough changes in the framework that will prevent drivers that work with your current working kernel to work, albeit perhaps with reduced functionality?
On Fri, Dec 16, 2011 at 3:40 PM, One cosmic <mgleone...@gmail.com> wrote: > Thanks JBQ for your incredible work and all of the android team members, > just curious (and anxious, i know) but there is a timeline for the nexus s > kernel sources to be uploaded?
> Sorry for the question, but this was one of the most awaited releases from > google :D
> Best Regards,
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
I haven't tested mixing-and-matching platform source and proprietary binaries (other than the baseband and bootloader). I have no idea what would happen if you ran 4.0.3 on older binaries.
On Fri, Dec 16, 2011 at 3:44 PM, Kenneth Crudup <kcru...@gmail.com> wrote:
> On Friday, December 16, 2011 3:31:10 PM UTC-8, JBQ wrote:
>> ... but other [functionalities] are missing at this point .... Google is >> working with the various companies involved to secure distribution contracts >> for the missing binaries as quickly as possible.
> If you've already got a unit and can extract the existing binaries, does > that help? Other than video, are there big enough changes in the framework > that will prevent drivers that work with your current working kernel to > work, albeit perhaps with reduced functionality?
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
On Friday, December 16, 2011 3:39:33 PM UTC-8, JBQ wrote:
> There's a kernel binary in the source tree
Oh yeah, that's right.
> I'll be pushing the matching source tree as soon as can.
Dude, serious thanks- those kernel source bits are probably the best Xmas present I'll get this year!
(I'd merged up to 2.6.36.4 and have been cherry-picking all over the "common" and "tegra" repos and various 2.6.29 bits since summer, but I suspect that wouldn't be enough for ICS.)
On Fri, Dec 16, 2011 at 22:42, Jean-Baptiste Queru <j...@android.com> wrote: > For Xoom: I know that the camera and HDMI don't work. The rest of the > device seems functional (wifi, 3G, sensors, audio, OpenGL). There > might be some trickiness with the variety of bootloaders and > basebands, I haven't been able to test those broadly as Xoom is a bit > ticklish in that domain and you might need to edit your board-info.txt > accordingly.
Missing firmware files like the Galaxy Nexus? (HDMI is not that important, just the camera)
Indeed, getting the camera to work on Xoom requires either a proprietary library or a bit of firmware (I'm not sure which) which I can't distribute without having a proper license from the owner of the file in question.
On Fri, Dec 16, 2011 at 3:48 PM, Carlos Silva <r3...@r3pek.org> wrote: > On Fri, Dec 16, 2011 at 22:42, Jean-Baptiste Queru <j...@android.com> wrote:
>> For Xoom: I know that the camera and HDMI don't work. The rest of the >> device seems functional (wifi, 3G, sensors, audio, OpenGL). There >> might be some trickiness with the variety of bootloaders and >> basebands, I haven't been able to test those broadly as Xoom is a bit >> ticklish in that domain and you might need to edit your board-info.txt >> accordingly.
> Missing firmware files like the Galaxy Nexus? (HDMI is not that important, > just the camera)
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> I'm pushing the source code for Android 4.0.3 to AOSP. This matches > build IML74K. Kernel sources will follow as soon as practical.
> Over the years, I've released 50 different versions of Android in > AOSP, not counting the SDK and CTS, and I think that this is the best > release ever.
> Some noteworthy items:
> -This version of Android is optimized for a wide range of devices. It > works on phones. It works on tablets. It works on devices that don't > quite have the horsepower of a Galaxy Nexus.
> -From a straight AOSP, it works on Galaxy Nexus (the ones sold with > mysid and yakju builds), on Motorola Xoom (US variants), and on Nexus > S (all variants). Proprietary binaries will soon be available for > those devices at the usual location.
> -Out of the box, this is the first time that AOSP works on 3 different > device families, the first time that it works on tablets, the first > time that it works directly on a device that's neither an ADP nor a > Nexus, and the first time that it works on Verizon devices.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
