This matches the update that has been sent to a few devices since yesterday.
As usual, the full source history is provided. Also, all changes are
merged into the master branch, from where it's possible to contribute
via https://android-review.googlesource.com/
The exact tagged version is android-4.0.4_r1.1
I expect that the push will be done by about 3pm PDT.
This opens the doors for the Android team to resume development of CTS
and of the developer tools directly in the Android Open-Source
Project.
The matching proprietary files will be available at
https://code.google.com/android/nexus/drivers.html by the end of day
(PDT). You should note that files related to CDMA devices (Nexus S 4G,
CDMA/LTE Xoom, CDMA/LTE Galaxy Nexus) have not been tested in the
context of AOSP. Of course, consumer support for those devices
continues unchanged.
I do not know the schedule for deployment to consumer devices,
especially in situations that involve additional per-operator
customizations done by the device manufacturers and/or in situations
that require operator approval prior to deployment.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
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.
Note that the baseline android-omap kernel is available in AOSP in
real time, branch android-omap-3.0 in kernel/omap
JBQ
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
JBQ
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--
JBQ
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
JBQ
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
JBQ
>> > To post to this group, send email to android-...@googlegroups.com
>> > To unsubscribe from this group, send email to
>> > android-buildi...@googlegroups.com
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
JBQ
On Wed, Mar 28, 2012 at 2:18 PM, Will Tisdale <willt...@gmail.com> wrote:
> Is there likely to be an code push to the kernel/samsung repo for 4.0.4?
>
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--
- Will
Yes, there will be pushes in the various kernel repositories to match
the platform release. The logistics of the push process prevent me
from releasing the kernel sources at the exact same time, but the
kernel pushes should happen by the end of the week.JBQ
On Wed, Mar 28, 2012 at 2:18 PM, Will Tisdale <willt...@gmail.com> wrote:
> Is there likely to be an code push to the kernel/samsung repo for 4.0.4?
>
> --
> 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
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
Blah blah forward-looking statement blah blah.
JBQ
On Wed, Mar 28, 2012 at 2:32 PM, blunden <blun...@gmail.com> wrote:
> Awesome, as always!
>
> Now I'm just waiting for factory images (or an OTA) to see if it contains
> any new radio and/or bootloader image. The code push is what's more
> important though of course.
>
>
> On Wednesday, March 28, 2012 11:24:13 PM UTC+2, Jean-Baptiste Queru wrote:
>>
>> Yes, there will be pushes in the various kernel repositories to match
>> the platform release. The logistics of the push process prevent me
>> from releasing the kernel sources at the exact same time, but the
>> kernel pushes should happen by the end of the week.
>>
>> JBQ
>>
>> On Wed, Mar 28, 2012 at 2:18 PM, Will Tisdale <willt...@gmail.com>
>> wrote:
>> > Is there likely to be an code push to the kernel/samsung repo for 4.0.4?
>> >
>> > --
>> > You received this message because you are subscribed to the "Android
>> > Building" mailing list.
>> > To post to this group, send email to android-...@googlegroups.com
>> > To unsubscribe from this group, send email to
>> > android-buildi...@googlegroups.com
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
Factory images for yakju and mysid are expected to closely follow the
OTA, which in turn is expected to closely follow operator approval.Blah blah forward-looking statement blah blah.
JBQ
On Wed, Mar 28, 2012 at 2:32 PM, blunden <blun...@gmail.com> wrote:
> Awesome, as always!
>
> Now I'm just waiting for factory images (or an OTA) to see if it contains
> any new radio and/or bootloader image. The code push is what's more
> important though of course.
>
>
> On Wednesday, March 28, 2012 11:24:13 PM UTC+2, Jean-Baptiste Queru wrote:
>>
>> Yes, there will be pushes in the various kernel repositories to match
>> the platform release. The logistics of the push process prevent me
>> from releasing the kernel sources at the exact same time, but the
>> kernel pushes should happen by the end of the week.
>>
>> JBQ
>>
>> On Wed, Mar 28, 2012 at 2:18 PM, Will Tisdale <willt...@gmail.com>
>> wrote:
>> > Is there likely to be an code push to the kernel/samsung repo for 4.0.4?
>> >
>> > --
>> > 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
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
I'll get things out once I confirm things, but that's probably going
to be tomorrow.
Thanks,
JBQ
>> >> > android-...@googlegroups.com
>> >> > To unsubscribe from this group, send email to
>> >> > android-buildi...@googlegroups.com
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/android-building?hl=en
>> >>
>> >> --
>> >> Jean-Baptiste M. "JBQ" Queru
>> >> Software Engineer, Android Open-Source Project, Google.
>> >>
>> >> 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-...@googlegroups.com
>> > To unsubscribe from this group, send email to
>> > android-buildi...@googlegroups.com
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
Factory images for yakju and mysid are expected to closely follow the
OTA, which in turn is expected to closely follow operator approval.Blah blah forward-looking statement blah blah.
JBQ
On Wed, Mar 28, 2012 at 2:32 PM, blunden <blun...@gmail.com> wrote:
> Awesome, as always!
>
> Now I'm just waiting for factory images (or an OTA) to see if it contains
> any new radio and/or bootloader image. The code push is what's more
> important though of course.
>
>
> On Wednesday, March 28, 2012 11:24:13 PM UTC+2, Jean-Baptiste Queru wrote:
>>
>> Yes, there will be pushes in the various kernel repositories to match
>> the platform release. The logistics of the push process prevent me
>> from releasing the kernel sources at the exact same time, but the
>> kernel pushes should happen by the end of the week.
>>
>> JBQ
>>
>> On Wed, Mar 28, 2012 at 2:18 PM, Will Tisdale <willt...@gmail.com>
>> wrote:
>> > Is there likely to be an code push to the kernel/samsung repo for 4.0.4?
>> >
>> > --
>> > 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
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
JBQ
>> >> > android-...@googlegroups.com
>> >> > To unsubscribe from this group, send email to
>> >> > android-buildi...@googlegroups.com
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/android-building?hl=en
>> >>
>> >> --
>> >> Jean-Baptiste M. "JBQ" Queru
>> >> Software Engineer, Android Open-Source Project, Google.
>> >>
>> >> 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-...@googlegroups.com
>> > To unsubscribe from this group, send email to
>> > android-buildi...@googlegroups.com
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
>> >> > To unsubscribe from this group, send email to
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/android-building?hl=en
>> >>
>> >> --
>> >> Jean-Baptiste M. "JBQ" Queru
>> >> Software Engineer, Android Open-Source Project, Google.
>> >>
>> >> 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
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>> >> > To unsubscribe from this group, send email to
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/android-building?hl=en
>> >>
>> >> --
>> >> Jean-Baptiste M. "JBQ" Queru
>> >> Software Engineer, Android Open-Source Project, Google.
>> >>
>> >> 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
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-building?hl=en
>>
>> --
>> Jean-Baptiste M. "JBQ" Queru
>> Software Engineer, Android Open-Source Project, Google.
>>
>> 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
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
Regards
//Ernst Sjöstrand
2012/3/28 Jean-Baptiste Queru <j...@android.com>:
> It looks like there's no ics-mr1-release branch on the manifest git in
> AOSP, but ics-mr1-release doesn't exist on all branches either from
> what I can see. How is that branch supposed to work?
The manifest branches for the releases are named like the tags
(to make "repo init -b" happy?), so for 4.0.4 you should be looking
at the android-4.0.4_r1.1 branch. The manifest pointed to by the
android-4.0.4_r1.1 branch and tag has android-4.0.4_r1.1 as the
default revision for all gits. Which branch(es), ics-mr1 and/or
ics-mr1-release, this tag is reachable from probably doesn't matter
to you.
--
Magnus B�ck
ba...@google.com
Also, I have no visibility over the update process of retail devices,
as that's not my domain of expertise.
JBQ
On Wed, Mar 28, 2012 at 11:08 AM, Jean-Baptiste Queru <j...@android.com> wrote:
> I'm in the process of pushing the Android 4.0.4 files (IMM76D) into
> the Android Open-Source Project. This represents an incremental update
> of a few hundred changes over 4.0.3.
>
> This matches the update that has been sent to a few devices since yesterday.
>
> As usual, the full source history is provided. Also, all changes are
> merged into the master branch, from where it's possible to contribute
> via https://android-review.googlesource.com/
>
> The exact tagged version is android-4.0.4_r1.1
>
> I expect that the push will be done by about 3pm PDT.
>
> This opens the doors for the Android team to resume development of CTS
> and of the developer tools directly in the Android Open-Source
> Project.
>
> The matching proprietary files will be available at
> https://code.google.com/android/nexus/drivers.html by the end of day
> (PDT). You should note that files related to CDMA devices (Nexus S 4G,
> CDMA/LTE Xoom, CDMA/LTE Galaxy Nexus) have not been tested in the
> context of AOSP. Of course, consumer support for those devices
> continues unchanged.
>
> I do not know the schedule for deployment to consumer devices,
> especially in situations that involve additional per-operator
> customizations done by the device manufacturers and/or in situations
> that require operator approval prior to deployment.
>
> JBQ
>
I suggest torospr is toro-sprint in preperation for the release in April.
When creating a local mirror of the android-4.0.4_r1.1 tag I found that
I could not sync tags from our Gerrit server unless the referenced commit
was also part of a tag. Hence, which branches a tag is reachable from actually
does matter.
Regards
//Ernst
2012/3/29 Magnus Bäck <ba...@google.com>:
> On Thursday, March 29, 2012 at 06:32 EDT,
> Magnus Bäck
> ba...@google.com
"unless the referenced commit was also part of a _branch_."
Regards
//Ernst
2012/3/30 Ernst Sjöstrand <ern...@gmail.com>:
That's exactly why each project contains the -release branches. Those
branches aren't used in any manifest, but they hold indirect
references to the tagged commits of the individual releases, so that
those commits get fetched by repo sync.
JBQ
2012/3/30 Ernst Sjöstrand <ern...@gmail.com>:
--
> Indeed. repo does a deep copy of branches, and a shallow copy of tags.
> If a tag references a commit, tree or blob that's not reachable from a
> branch, it's left dangling with an unresolved reference.
AFAIK Repo isn't involved here. It's Gerrit that makes the decision to
only advertise tags reachable from branches the user is allowed to see.
> That's exactly why each project contains the -release branches. Those
> branches aren't used in any manifest, but they hold indirect
> references to the tagged commits of the individual releases, so that
> those commits get fetched by repo sync.
Well, you'd have those branches anyway since even the automerger would
want to merge on top of a branch head. The fact that this branch comes
very handy when Gerrit doesn't evaluate ACL read access for tag objects
but rather infers it from the user's ability to read branches is more of
a bonus, right?
> 2012/3/30 Ernst Sj�strand <ern...@gmail.com>:
>
> > When creating a local mirror of the android-4.0.4_r1.1 tag I found
> > that I could not sync tags from our Gerrit server unless the
> > referenced commit was also part of a tag. Hence, which branches a
> > tag is reachable from actually does matter.
>
> Sorry,
>
> "unless the referenced commit was also part of a _branch_."
Ah, yes. I had forgotten about that. Did you also send a frustrated
email to Fredrik et al, complaining that their Gerrit server was broken
again because the tags you pushed didn't stick? :-)
For anything but completely new Android branches I resorted to just
pushing x and x-release branches for all x in all gits, then pushing
the tag. Then the manifest contents is irrelevant. If one really wants
to mirror everything, a single
repo forall -c 'git push ssh://host/$REPO_PROJECT \
--tags refs/heads/*:refs/heads/someprefix/*'
would take care of everything (assuming a workspace initialized with
--mirror).
Regards
//Ernst Sjöstand
2012/3/30 Jean-Baptiste Queru <j...@android.com>:
Now, if you want to mirror older branches, that's a different story As
an example, for 2.2.3 the count is 206575 vs 85659. Unfortunately,
there's no easy way to know which branch to mirror to get a given tag,
other than knowing ahead of time (or writing a script for that, which
sounds possible).
Apologies in advance for this: I just got dizzy and fell from reading this thread. Great information as I am interested in creating a local mirror. Is this information organized anywhere for learners like me? Thank you all for your work and input.
There's some partial information about that under "Using a local
mirror" at http://source.android.com/source/downloading.html -
specifically, note the special manifest to use for mirroring, and the
--mirror option in repo.
Note that I don't know how to set things up to serve this from a
server. It *might* work from behind a plain git-daemon, but I'm not
even sure about that.
JBQ
I'll try to do it tonight (or as soon as possible).
JBQ
Look for them by SHA-1 from the changelogs of the prebuilt kernel binaries:
repo forall device/samsung/crespo device/moto/wingray
device/samsung/tuna -pc git log --max-count=1 android-4.0.4_r1.1 --
kernel
project device/moto/wingray/
commit 22c420fc8998f1ac9764d187fea919a774154667
Author: Dmitry Shmidt <dimi...@google.com>
Date: Tue Mar 13 16:03:15 2012 -0700
stingray: Kernel prebuilt -- DO NOT MERGE
42a0480 net: wireless: bcmdhd: Fix mac setting from platform hook
Change-Id: I5940af601849a0fe0ceeea2c207b18a8d706aa8c
Signed-off-by: Dmitry Shmidt <dimi...@google.com>
project device/samsung/crespo/
commit 0d22ff6303f7876a75da90e02bccc660df6ed3f4
Author: Simon Wilson <simon...@google.com>
Date: Thu Feb 2 17:01:30 2012 -0800
new kernel + wifi prebuilt
6656123 ARM: s5pv210: herring: don't disable prox sensor during suspend
Change-Id: I6899d07b14f72c2148d9d4fac66f11c88e42466a
project device/samsung/tuna/
commit 3b50cc6d1c148210fa7b39b1ba48f54f8c5e558d
Author: Dmitry Shmidt <dimi...@google.com>
Date: Tue Mar 13 15:59:42 2012 -0700
tuna: kernel prebuilt -- DO NOT MERGE
034fec9 net: wireless: bcmdhd: Fix mac setting from platform hook
Change-Id: I45c7b3a193e652b278334b775b1d10684e1eea01
Signed-off-by: Dmitry Shmidt <dimi...@google.com>
JBQ
What's the kernel version released with 4.0.4 on Galaxy Nexus?
Does 4.0.4 have a specific Kernel dependency that would require upgrading the kernel used on 4.0.3?
Thanks,
Luciano.
tuna: kernel prebuilt -- DO NOT MERGE
034fec9 net: wireless: bcmdhd: Fix mac setting from platform hook
Change-Id: I45c7b3a193e652b278334b775b1d10684e1eea01
Signed-off-by: Dmitry Shmidt <dimi...@google.com>
You're looking for kernel 034fec9
JBQ
JBQ
I'm in the process of pushing the Android 4.0.4 files (IMM76D) into
the Android Open-Source Project. This represents an incremental update
of a few hundred changes over 4.0.3.This matches the update that has been sent to a few devices since yesterday.
As usual, the full source history is provided. Also, all changes are
merged into the master branch, from where it's possible to contribute
The exact tagged version is android-4.0.4_r1.1
I expect that the push will be done by about 3pm PDT.
This opens the doors for the Android team to resume development of CTS
and of the developer tools directly in the Android Open-Source
Project.
The matching proprietary files will be available at
https://code.google.com/android/nexus/drivers.html by the end of day
(PDT). You should note that files related to CDMA devices (Nexus S 4G,
CDMA/LTE Xoom, CDMA/LTE Galaxy Nexus) have not been tested in the
context of AOSP. Of course, consumer support for those devices
continues unchanged.
I do not know the schedule for deployment to consumer devices,
especially in situations that involve additional per-operator
customizations done by the device manufacturers and/or in situations
that require operator approval prior to deployment.JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.