The source code for Android 4.0.3 is now available

[Jean-Baptiste Queru]

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.

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.

[Roman]

Thank you for everything you do!

[Diego De Barbieri]

So, that means that I can update my nexus S from AT&T NOW???

And also my Verizon XOOM???

[Jean-Baptiste Queru]

All the files have replicated to the git server, you can sync at any time.

The branch/tag for 4.0.3 is android-4.0.3_r1, predictably.

Below are the direct links to the various proprietary binaries. The
web page will update in the next few hours.

https://dl.google.com/dl/android/aosp/akm-crespo-iml74k-48d943ee.tgz
https://dl.google.com/dl/android/aosp/akm-crespo4g-iml74k-2fbe47d4.tgz
https://dl.google.com/dl/android/aosp/broadcom-crespo-iml74k-4b0a7e2a.tgz
https://dl.google.com/dl/android/aosp/broadcom-crespo4g-iml74k-1d2d3325.tgz
https://dl.google.com/dl/android/aosp/broadcom-stingray-iml74k-f9178f5c.tgz
https://dl.google.com/dl/android/aosp/broadcom-wingray-iml74k-2c8a74c6.tgz
https://dl.google.com/dl/android/aosp/imgtec-crespo-iml74k-33420a2f.tgz
https://dl.google.com/dl/android/aosp/imgtec-crespo4g-iml74k-1e82efa7.tgz
https://dl.google.com/dl/android/aosp/imgtec-maguro-iml74k-a796ffae.tgz
https://dl.google.com/dl/android/aosp/imgtec-panda-iml74k-cfb7bdad.tgz
https://dl.google.com/dl/android/aosp/imgtec-toro-iml74k-21966564.tgz
https://dl.google.com/dl/android/aosp/nvidia-stingray-iml74k-96830dd7.tgz
https://dl.google.com/dl/android/aosp/nvidia-wingray-iml74k-e5226417.tgz
https://dl.google.com/dl/android/aosp/nxp-crespo-iml74k-9f2a89d1.tgz
https://dl.google.com/dl/android/aosp/nxp-crespo4g-iml74k-fdb5d911.tgz
https://dl.google.com/dl/android/aosp/samsung-crespo-iml74k-0dbf413c.tgz
https://dl.google.com/dl/android/aosp/samsung-crespo4g-iml74k-50556812.tgz
https://dl.google.com/dl/android/aosp/samsung-maguro-iml74k-de1cc439.tgz

SHA-1 checksums:

a5691c6e0b247c10785f7e4ebede2b2cc9a6a209 akm-crespo-iml74k-48d943ee.tgz
35322ee8a1fe529918f5a8299f742f4472aaa79b akm-crespo4g-iml74k-2fbe47d4.tgz
514dfba67db40c70dec8c427ea174831c0a04d1a broadcom-crespo-iml74k-4b0a7e2a.tgz
86ec8fa63f4e6bacde9bb0c0513308fc53b8d2fd broadcom-crespo4g-iml74k-1d2d3325.tgz
b18dc80b0233589794c80ab9ce1ad460a55d5cd1 broadcom-stingray-iml74k-f9178f5c.tgz
3851d88033e2cd12992eb362ba51d23ba3b49a60 broadcom-wingray-iml74k-2c8a74c6.tgz
928930d04eebe3d84ab160aa78c1b2b1f9760614 imgtec-crespo-iml74k-33420a2f.tgz
e8c93c24899a8fd4f7427915e3f70a7ee903fca8 imgtec-crespo4g-iml74k-1e82efa7.tgz
4ba930f7d592e1027993394488bb3d3ed0b8f04f imgtec-maguro-iml74k-a796ffae.tgz
151ce2d5b1467d6e8f913d35d8194757510ff4d2 imgtec-panda-iml74k-cfb7bdad.tgz
b0468fbdd64eb09d6d4a9c6f56d382a9cc904170 imgtec-toro-iml74k-21966564.tgz
1a10222e9538d36baf06c18f14924560c022ef21 nvidia-stingray-iml74k-96830dd7.tgz
07956257d3fc099fa4c2f570eb21d8ba1aef6094 nvidia-wingray-iml74k-e5226417.tgz
d8a7ff80cc9502f10cb2e9134e4cfa2aa14258fd nxp-crespo-iml74k-9f2a89d1.tgz
b63bf2d51decd6ea92398c85800e1813e4c4cd77 nxp-crespo4g-iml74k-fdb5d911.tgz
17e215aecee100603631a8834cbc2070f3ae9088 samsung-crespo-iml74k-0dbf413c.tgz
8db8d3098bc25d15d8a797ef5fd4797bfe844ff8 samsung-crespo4g-iml74k-50556812.tgz
7014f5d514a9a4b1235001e673e40e5b8a922198 samsung-maguro-iml74k-de1cc439.tgz

That's all, folks!

JBQ

[Matt Oakes]

Wow! Brilliant. I saw the nexus s news and came here to see if there was a date for the code to be release. Love the fact that it's here already :-)

Thanks for your work. Not enough people say that to you and the team. Really good work!

[jdkoreclipse]

So, i can build for the LTE Galaxy nexus nd have everything work?

Also, what branch is it?

[Kenneth Crudup]

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?

[Jean-Baptiste Queru]

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.

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

[Michał Banszel]

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>:

[Jean-Baptiste Queru]

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.

JBQ

[Jean-Baptiste Queru]

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 <dieg...@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-...@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

--

[Carlos Silva]

--
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

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?

[Jean-Baptiste Queru]

You can go right now. This wasn't as complex a push as the original
ICS, so the replication delay was much smaller.

JBQ

[Justin S]

Sweet! Let the android defragmentation begin. Thx for all of the hard
work +Android team.

On Dec 16, 5:35 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> All the files have replicated to the git server, you can sync at any time.
>
> The branch/tag for 4.0.3 is android-4.0.3_r1, predictably.
>
> Below are the direct links to the various proprietary binaries. The
> web page will update in the next few hours.
>

> https://dl.google.com/dl/android/aosp/akm-crespo-iml74k-48d943ee.tgzhttps://dl.google.com/dl/android/aosp/akm-crespo4g-iml74k-2fbe47d4.tgzhttps://dl.google.com/dl/android/aosp/broadcom-crespo-iml74k-4b0a7e2a...https://dl.google.com/dl/android/aosp/broadcom-crespo4g-iml74k-1d2d33...https://dl.google.com/dl/android/aosp/broadcom-stingray-iml74k-f9178f...https://dl.google.com/dl/android/aosp/broadcom-wingray-iml74k-2c8a74c...https://dl.google.com/dl/android/aosp/imgtec-crespo-iml74k-33420a2f.tgzhttps://dl.google.com/dl/android/aosp/imgtec-crespo4g-iml74k-1e82efa7...https://dl.google.com/dl/android/aosp/imgtec-maguro-iml74k-a796ffae.tgzhttps://dl.google.com/dl/android/aosp/imgtec-panda-iml74k-cfb7bdad.tgzhttps://dl.google.com/dl/android/aosp/imgtec-toro-iml74k-21966564.tgzhttps://dl.google.com/dl/android/aosp/nvidia-stingray-iml74k-96830dd7...https://dl.google.com/dl/android/aosp/nvidia-wingray-iml74k-e5226417.tgzhttps://dl.google.com/dl/android/aosp/nxp-crespo-iml74k-9f2a89d1.tgzhttps://dl.google.com/dl/android/aosp/nxp-crespo4g-iml74k-fdb5d911.tgzhttps://dl.google.com/dl/android/aosp/samsung-crespo-iml74k-0dbf413c.tgzhttps://dl.google.com/dl/android/aosp/samsung-crespo4g-iml74k-5055681...https://dl.google.com/dl/android/aosp/samsung-maguro-iml74k-de1cc439.tgz

[Jean-Baptiste Queru]

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

> --
> 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

--

[Carlos Silva]

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 ? 

[Jean-Baptiste Queru]

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.

JBQ

[One cosmic]

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,

[Kenneth Crudup]

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?

[Jean-Baptiste Queru]

I don't have an exact timeline, but let's just say it's "as soon as
possible", which is likely to mean "early next week".

JBQ

[Jean-Baptiste Queru]

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.

JBQ

[Kenneth Crudup]

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.)

[Carlos Silva]

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) 

[Jean-Baptiste Queru]

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.

JBQ

[richard watkins]

Any eta on Crespo 4G OTA?

[Jean-Baptiste Queru]

No estimates on the OTAs for various devices. Those are only loosely
coupled to the code drops in AOSP, and they tend to involve a lot of
additional approvals that I'm happy to know very little about.

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

--

[jdkoreclipse]

Also, Is there a kernel source for the Toro/mysid? If so, where can i
find said source?

[Jean-Baptiste Queru]

The kernel that matches ITL41D/ITL41K is in the kernel/omap project,
in the branch origin/android-omap-tuna-3.0-mr0 - I'll push the updated
version as soon as I can.

JBQ

[Carlos Silva]

I'm running into a failure compiling for Xoom on Ubuntu 11.10:

 host C++: libMesa <= external/mesa3d/src/glsl/linker.cpp

In file included from external/mesa3d/src/glsl/ir.h:38:0,

                 from external/mesa3d/src/glsl/glsl_symbol_table.h:34,

                 from external/mesa3d/src/glsl/linker.cpp:78:

external/mesa3d/src/glsl/ir_visitor.h:48:17: warning: ‘virtual void ir_visitor::visit(ir_function_signature*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:81:17: warning:   by ‘ir_control_flow_visitor::visit’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:49:17: warning: ‘virtual void ir_visitor::visit(ir_function*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:81:17: warning:   by ‘ir_control_flow_visitor::visit’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:59:17: warning: ‘virtual void ir_visitor::visit(ir_return*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:81:17: warning:   by ‘ir_control_flow_visitor::visit’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:60:17: warning: ‘virtual void ir_visitor::visit(ir_discard*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:81:17: warning:   by ‘ir_control_flow_visitor::visit’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:61:17: warning: ‘virtual void ir_visitor::visit(ir_if*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:81:17: warning:   by ‘ir_control_flow_visitor::visit’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:62:17: warning: ‘virtual void ir_visitor::visit(ir_loop*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:81:17: warning:   by ‘ir_control_flow_visitor::visit’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:63:17: warning: ‘virtual void ir_visitor::visit(ir_loop_jump*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_visitor.h:81:17: warning:   by ‘ir_control_flow_visitor::visit’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:111:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_loop*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:113:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_function_signature*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:115:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_function*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:117:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_expression*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:119:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_texture*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:121:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_swizzle*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:123:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_dereference_array*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:125:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_dereference_record*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:131:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_return*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:133:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_discard*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:135:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit_enter(ir_if*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:110:30: warning:   by ‘find_assignment_visitor::visit_enter’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:86:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit(ir_variable*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:153:30: warning:   by ‘virtual ir_visitor_status find_deref_visitor::visit(ir_dereference_variable*)’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:87:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit(ir_constant*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:153:30: warning:   by ‘virtual ir_visitor_status find_deref_visitor::visit(ir_dereference_variable*)’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:88:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit(ir_loop_jump*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:153:30: warning:   by ‘virtual ir_visitor_status find_deref_visitor::visit(ir_dereference_variable*)’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h: In function ‘void remap_variables(ir_instruction*, gl_shader*, hash_table*)’:

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:86:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit(ir_variable*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:623:33: warning:   by ‘virtual ir_visitor_status remap_variables(ir_instruction*, gl_shader*, hash_table*)::remap_visitor::visit(ir_dereference_variable*)’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:87:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit(ir_constant*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:623:33: warning:   by ‘virtual ir_visitor_status remap_variables(ir_instruction*, gl_shader*, hash_table*)::remap_visitor::visit(ir_dereference_variable*)’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/ir_hierarchical_visitor.h:88:30: warning: ‘virtual ir_visitor_status ir_hierarchical_visitor::visit(ir_loop_jump*)’ was hidden [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp:623:33: warning:   by ‘virtual ir_visitor_status remap_variables(ir_instruction*, gl_shader*, hash_table*)::remap_visitor::visit(ir_dereference_variable*)’ [-Woverloaded-virtual]

external/mesa3d/src/glsl/linker.cpp: In function ‘void assign_varying_locations(gl_shader_program*, gl_shader*, gl_shader*)’:

external/mesa3d/src/glsl/linker.cpp:1394:49: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1394:50: error: ‘varyings’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp:1394:58: error: ‘offsetof’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp:1395:48: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1412:47: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1412:48: error: ‘position’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp:1414:47: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1414:48: error: ‘pointSize’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp:1424:47: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1424:48: error: ‘position’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp:1428:47: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1428:48: error: ‘frontFacingPointCoord’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp:1431:47: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1431:48: error: ‘frontFacingPointCoord’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp: In function ‘void link_shaders(const gl_context*, gl_shader_program*)’:

external/mesa3d/src/glsl/linker.cpp:1734:49: error: expected primary-expression before ‘,’ token

external/mesa3d/src/glsl/linker.cpp:1734:50: error: ‘fragColor’ was not declared in this scope

external/mesa3d/src/glsl/linker.cpp:1734:59: error: ‘offsetof’ was not declared in this scope

make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libMesa_intermediates/src/glsl/linker.o] Error 1

make: *** Waiting for unfinished jobs....

true

Am I missing something? :-/

[Jean-Baptiste Queru]

I'm pretty sure that the 4.0.3 code (and the ics-mr1 branch) don't
build on 11.10.

I'm not 100% sure about the master branch. 4.0.3 might have introduced
a regression in that domain. Since we don't have any good way of
testing on 11.10 before the release (we only use 10.04 inside Google),
we have to wait until after the release to be able to test.

JBQ

[Michał Banszel]

@JBQ Google decided to remove go_maxspeed_load from interactive
governor and replace it with hispeed_freq?

2011/12/17 Jean-Baptiste Queru <j...@android.com>:

[Carlos Silva]

On Sat, Dec 17, 2011 at 01:01, Jean-Baptiste Queru <j...@android.com> wrote:

I'm pretty sure that the 4.0.3 code (and the ics-mr1 branch) don't
build on 11.10.

I'm not 100% sure about the master branch. 4.0.3 might have introduced
a regression in that domain. Since we don't have any good way of
testing on 11.10 before the release (we only use 10.04 inside Google),
we have to wait until after the release to be able to test.

Well, then it fails there :)

It's the master branch on 11.10 

[Jean-Baptiste Queru]

Well, it sounds like the master branch is broken again on 11.10. We'll
try to have a look next week. Sorry for the annoyance.

JBQ

[John Kirk]

I made successfully on the master branch today on 11.10. I synced the master repo last night, make at 7:44 and at 8:57 the build finished with no errors.

[Carlos Silva]

On Sat, Dec 17, 2011 at 01:14, Jean-Baptiste Queru <j...@android.com> wrote:

Well, it sounds like the master branch is broken again on 11.10. We'll
try to have a look next week. Sorry for the annoyance.

no problem :) My laptop will have a weekend to rest then :P

[Jean-Baptiste Queru]

Last night, the master branch "only" contained 4.0.1. As of about 4
hours ago, it contains the 4.0.3 "new hotness", which seems to have
introduced some unfortunate regressions.

JBQ

[John Kirk]

I thought that might have been the case.

John Kirk
636 South John Paul Street
El Paso Texas, 79938
Cell 915-204-2838
FAX 915-988-2601

[Salim Ibrahim]

Where do these binaries go in the source code folder structure? 

[sjcloutier]

So I have successfully built the Stingray version for my 4G XOOM, but...

When I go to flashall files with fastboot, I get a failure on baseband version. The latest OTA I received was HLK54F which includes baseband version CDMA_N_03.1A.54P and baseband-2 as LTEDC_U_05.19.07.

It says the update requires baseband versions: CDMA_N_03.1A.5CPS and LTEDC_U_07.19.00

So how would I go about getting these, and flashing them onto my XOOM?

[Jean-Baptiste Queru]

Run the script that's included in each .tgz from the root of the source tree, and the binaries and associated makefiles will be installed in the vendor/ directory.

JBQ

On Friday, December 16, 2011, Salim Ibrahim <sali...@gmail.com> wrote:
> Where do these binaries go in the source code folder structure? 
>

[richard watkins]

I love the openness of Android there are seven devices in the house
and it's a hobby to keep up on the development community, good things
are going to come from Linux in the future.

[Bryan Hinton]

The following will fix the mesa3d glsl build error when compiling ics
4.0.3 on a linux 32/64 box.

add the following to the top of external/mesa3d/src/glsl/linker.cpp
#include <stddef.h>

offsetof() is a standard C Macro and it's definition is not visible
from within the functions that reside in the linker.cpp file.

The linker will handle the definition of the macro's second parameter:
varyings...

ICS 4.0.3 build (toro target) on 32/64 linux host was successful after
making this modification.

Bryan Hinton

On Dec 16, 8:38 pm, John Kirk <jkirk...@gmail.com> wrote:
> I thought that might have been the case.
>
> John Kirk
> 636 South John Paul Street
> El Paso Texas, 79938
> Cell 915-204-2838
> FAX 915-988-2601
> On Dec 16, 2011 7:31 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
>
>
>
>
>
>
>
> > Last night, the master branch "only" contained 4.0.1. As of about 4
> > hours ago, it contains the 4.0.3 "new hotness", which seems to have
> > introduced some unfortunate regressions.
>
> > JBQ
>

[Spencer]

Well i am going to try my hand at building for the xoom, just ran the
extract-files.sh, and here is my output: http://pastebin.com/FZMeHJ1K
am i going to run into problems with graphics due to these:

remote object '/system/lib/egl/libGLESv2_perfhud.so' does not exist

remote object '/system/lib/egl/libEGL_perfhud.so' does not exist

remote object '/system/lib/egl/libGLESv1_CM_perfhud.so' does not exist

[Jean-Baptiste Queru]

Those scripts are my private development tools, and they only work from a 4.0.3 device. You should be using the licensed binaries from http://code.google.com/android/nexus/drivers.html instead.

JBQ

[fattire]

This seemed to get past the error:

Add to /src/glsl/linker.cpp b/src/glsl/linker.cpp

@@ -67,6 +67,7 @@
#include <cstdio>
#include <cstdarg>
#include <climits>
+#include <stddef.h>

(just the one line)

ft

On Dec 16, 7:38 pm, John Kirk <jkirk...@gmail.com> wrote:
> I thought that might have been the case.
>
> John Kirk
> 636 South John Paul Street
> El Paso Texas, 79938
> Cell 915-204-2838
> FAX 915-988-2601
> On Dec 16, 2011 7:31 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
>
>
>
>
>
>
>
> > Last night, the master branch "only" contained 4.0.1. As of about 4
> > hours ago, it contains the 4.0.3 "new hotness", which seems to have
> > introduced some unfortunate regressions.
>
> > JBQ
>

[Jean-Baptiste Queru]

One option is to flash the partitions one by one:
fastboot flash boot
fastboot flash recovery
fastboot flash system
fastboot erase cache
fastboot erase userdata
fastboot reboot

The other option is to edit device/moto/stingray/board-info.txt and remove the baseband checks, then re-run make.

JBQ

[gnufabio]

Yep, I can confirm that Android 4.0.3 is no longer compiling on Ubuntu
11.10. Any suggestion? What distro could I use to compile Android?

[Caesar]

I see the crespo4g binaries posted, will this work properly on the
Nexus S 4g?

[Jean-Baptiste Queru]

10.04 if you're in a hurry, or wait until next week and we'll try to fix it.

JBQ

[Jean-Baptiste Queru]

Yes, 4.0.3 works on Nexus S 4G if you build it with the posted binaries.

JBQ

[Simon Ponder]

While trying to pull 4.0.3 branch, I keep getting the following
errors:

simon@simon-VirtualBox:~/android$ repo sync
Fetching projects: 83% (190/228) error: Couldn't resolve host
'android.googlesource.com' while accessing
https://android.googlesource.com/platform/packages/apps/SpareParts/info/refs

fatal: HTTP request failed
error: Couldn't resolve host 'android.googlesource.com' while
accessing https://android.googlesource.com/platform/packages/apps/SpareParts/info/refs

fatal: HTTP request failed
error: Failed connect to android.googlesource.com:443; Connection
timed out while accessing https://android.googlesource.com/platform/packages/apps/QuickSearchBox/info/refs

fatal: HTTP request failed
error: Failed connect to android.googlesource.com:443; Connection
timed out while accessing https://android.googlesource.com/platform/packages/apps/Settings/info/refs

fatal: HTTP request failed
error: The requested URL returned error: 403 while accessing
https://android.googlesource.com/platform/packages/apps/SoundRecorder/info/refs

fatal: HTTP request failed
error: Cannot fetch platform/packages/apps/SpareParts
Fetching projects: 85% (194/228)
error: Exited sync due to fetch errors
simon@simon-VirtualBox:~/android$

Any Ideas?

[Bongjae Moon]

I'm not sure it's just connection problem ?

In my case, it's going well.

Thanks.

Best Regards

BJ

[sjcloutier]

Thanks for the advice JBQ.

Unfortunately, I have already succeeded at flashing ICS onto my
Motorola XOOM 4G, however - I am unable to get 3G/4G working. The
basebands/radio is not being recognized.

I attempted to enter radiooptions in shell, and any command returns:
"opening radio debug socket: connection refused"

Any recommendations?

On Dec 17, 12:39 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> One option is to flash the partitions one by one:
> fastboot flash boot
> fastboot flash recovery
> fastboot flash system
> fastboot erase cache
> fastboot erase userdata
> fastboot reboot
>
> The other option is to edit device/moto/stingray/board-info.txt and remove
> the baseband checks, then re-run make.
>
> JBQ
>

[Xianghua Xiao]

for panda board a fresh 4.0.3_r1 build led to a serial output:

[ 5.061218] PVR: Installing device LISR SGX ISR on IRQ 53 with
cookie dd4a1400
[ 5.069610] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from e0a60000
[ 5.076660] PVR: SysFinalise: Version string: SGX revision = 1.2.0
[ 5.084045] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision
(279068)/device DDK revision (5
50175).
[ 5.094726] PVR_K:(Error): PVRSRVFinaliseSystem: Failed
PVRSRVDevInitCompatCheck call (device index
: 0) [451, drivers/gpu/pvr/pvrsrv.c]
[ 5.108398] PVR_K:(Error): BridgedDispatchKM: Initialisation
failed. Driver unusable. [4795, drive
rs/gpu/pvr/bridged_pvr_bridge.c]
[ 5.954620] PVR_K:(Error): BridgedDispatchKM: Initialisation
failed. Driver unusable. [4795, drive
rs/gpu/pvr/bridged_pvr_bridge.c]
[ 5.989318] init: untracked pid 71 exited

Android is not up and running with 4.0.3 on my panda board.

xianghua

[Jean-Baptiste Queru]

You need to use the master branch, as 4.0.3 doesn't have all the
necessary support (specifically for this case, 4.0.3 has an older
kernel that doesn't work with the current graphics libraries).

That being said, there's an issue in the master branch where the
display doesn't come up. I'm trying to track it down.

JBQ

--

[Chuck Randy]

Has anyone gotten this working on a pandaboard? I can compile the
source and I extract the propriety driver stuff, but no beans. I know
that the panda will boot to android because i can adb shell into it.
But no graphics at all. Any thoughts on why this might be happening?

Could I repo with -b android-4.0.1_r1 to get the panda working again?

-CRB

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.
>
> JBQ
>

[Jean-Baptiste Queru]

There's indeed an issue on the graphics side. My best guess is that
4.0.3 has a few more graphics requirements that aren't implemented in
the panda graphics libraries that we have. Investigating this is on my
todo list.

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

--

[Xianghua Xiao]

tried the master branch and a new kernel from omap git tree, same
problem, it seems the imgtec stuff is not working in 4.0.3.

[Ashwini Singh]

Hi JBQ,

On Sat, Dec 17, 2011 at 3:23 AM, 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.

And..., that device is panda?

 

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.

--
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

Thank You.

Regards,
Ashwini Singh

[kun liu]

2011/12/18 Simon Ponder <simon....@gmail.com>

--
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

I encountered the same problem yesterday.However all these issues seem alright now. 

[pwerry]

The only issue with 11.10 that I saw was the builtin gcc 4.6.1
offsetof macro not being defined, which only affects /external/mesa3d/
src/glsl/linker.cpp

To fix add #define offsetof(st, m) __builtin_offsetof(st, m)

If you run into other issues, probably in the HOST makefile, just
google the build error and it will probably show up on the boards

On Dec 16, 11:42 pm, 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.
>
> 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.
>
> JBQ
>
>
>
>
>
>
>
>
>
> 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-...@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 Queru]

The non-Nexus device is the Motorola Xoom.

JBQ

[Jean-Baptiste Queru]

Unfortunately the only Verizon Xoom I have for testing is a 3G model.
I'm guessing that supporting 4G requires additional proprietary
binaries that I don't have a license to distribute, and (sadly) that a
4G model can't downgrade to 3G operation when those binaries are
missing.

JBQ

--

[Michał Banszel]

JBQ, is the format() command for cache partition using also "0"
parameter like system partition?

format("ext4", "EMMC",
"/dev/block/platform/omap/omap_hsmmc.0/by-name/cache", "0");

Or it should be different for cache?

Thanks!

2011/12/19 Jean-Baptiste Queru <j...@android.com>:

[Jean-Baptiste Queru]

I have no idea what that is or where that lives. I'm guessing you're
trying to modify the platform, not just to build it, so
android-platform or maybe android-porting might be better suited to
get an answer.

JBQ

[fula]

herring_defconfig is the proper defconfig as in 2.6.35?

Moussa

On Dec 16, 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.
>

> JBQ

[Jean-Baptiste Queru]

That sounds likely, but the best way to know is to ask android-kernel.

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

--

[cTrox]

This seems to be a Virtualbox problem. I had it too and switche my network adapter from NAT to bridged, now I'm able to sync without any errors.

[San Xi]

Hi JBQ,

     Is there any way to see all branch in Android SRC using repo command? Even though I know that we can list all branch in ./.git/ Indirectly.
 

2011/12/17 Jean-Baptiste Queru <j...@android.com>

All the files have replicated to the git server, you can sync at any time.

The branch/tag for 4.0.3 is android-4.0.3_r1, predictably.

Below are the direct links to the various proprietary binaries. The
web page will update in the next few hours.

https://dl.google.com/dl/android/aosp/akm-crespo-iml74k-48d943ee.tgz
https://dl.google.com/dl/android/aosp/akm-crespo4g-iml74k-2fbe47d4.tgz
https://dl.google.com/dl/android/aosp/broadcom-crespo-iml74k-4b0a7e2a.tgz
https://dl.google.com/dl/android/aosp/broadcom-crespo4g-iml74k-1d2d3325.tgz
https://dl.google.com/dl/android/aosp/broadcom-stingray-iml74k-f9178f5c.tgz
https://dl.google.com/dl/android/aosp/broadcom-wingray-iml74k-2c8a74c6.tgz
https://dl.google.com/dl/android/aosp/imgtec-crespo-iml74k-33420a2f.tgz
https://dl.google.com/dl/android/aosp/imgtec-crespo4g-iml74k-1e82efa7.tgz
https://dl.google.com/dl/android/aosp/imgtec-maguro-iml74k-a796ffae.tgz
https://dl.google.com/dl/android/aosp/imgtec-panda-iml74k-cfb7bdad.tgz
https://dl.google.com/dl/android/aosp/imgtec-toro-iml74k-21966564.tgz
https://dl.google.com/dl/android/aosp/nvidia-stingray-iml74k-96830dd7.tgz
https://dl.google.com/dl/android/aosp/nvidia-wingray-iml74k-e5226417.tgz
https://dl.google.com/dl/android/aosp/nxp-crespo-iml74k-9f2a89d1.tgz
https://dl.google.com/dl/android/aosp/nxp-crespo4g-iml74k-fdb5d911.tgz
https://dl.google.com/dl/android/aosp/samsung-crespo-iml74k-0dbf413c.tgz
https://dl.google.com/dl/android/aosp/samsung-crespo4g-iml74k-50556812.tgz
https://dl.google.com/dl/android/aosp/samsung-maguro-iml74k-de1cc439.tgz

SHA-1 checksums:

a5691c6e0b247c10785f7e4ebede2b2cc9a6a209  akm-crespo-iml74k-48d943ee.tgz
35322ee8a1fe529918f5a8299f742f4472aaa79b  akm-crespo4g-iml74k-2fbe47d4.tgz
514dfba67db40c70dec8c427ea174831c0a04d1a  broadcom-crespo-iml74k-4b0a7e2a.tgz
86ec8fa63f4e6bacde9bb0c0513308fc53b8d2fd  broadcom-crespo4g-iml74k-1d2d3325.tgz
b18dc80b0233589794c80ab9ce1ad460a55d5cd1  broadcom-stingray-iml74k-f9178f5c.tgz
3851d88033e2cd12992eb362ba51d23ba3b49a60  broadcom-wingray-iml74k-2c8a74c6.tgz
928930d04eebe3d84ab160aa78c1b2b1f9760614  imgtec-crespo-iml74k-33420a2f.tgz
e8c93c24899a8fd4f7427915e3f70a7ee903fca8  imgtec-crespo4g-iml74k-1e82efa7.tgz
4ba930f7d592e1027993394488bb3d3ed0b8f04f  imgtec-maguro-iml74k-a796ffae.tgz
151ce2d5b1467d6e8f913d35d8194757510ff4d2  imgtec-panda-iml74k-cfb7bdad.tgz
b0468fbdd64eb09d6d4a9c6f56d382a9cc904170  imgtec-toro-iml74k-21966564.tgz
1a10222e9538d36baf06c18f14924560c022ef21  nvidia-stingray-iml74k-96830dd7.tgz
07956257d3fc099fa4c2f570eb21d8ba1aef6094  nvidia-wingray-iml74k-e5226417.tgz
d8a7ff80cc9502f10cb2e9134e4cfa2aa14258fd  nxp-crespo-iml74k-9f2a89d1.tgz
b63bf2d51decd6ea92398c85800e1813e4c4cd77  nxp-crespo4g-iml74k-fdb5d911.tgz
17e215aecee100603631a8834cbc2070f3ae9088  samsung-crespo-iml74k-0dbf413c.tgz
8db8d3098bc25d15d8a797ef5fd4797bfe844ff8  samsung-crespo4g-iml74k-50556812.tgz
7014f5d514a9a4b1235001e673e40e5b8a922198  samsung-maguro-iml74k-de1cc439.tgz

That's all, folks!

JBQ

[Jean-Baptiste Queru]

Not that I know of.

You can see all the branches in the manifest project with (cd
.repo/manifests ; git branch -a) and if you want to find all the
possible manifests you'll need to go through all those branches and
find the individual manifests. Off-hand, the master branch is the only
one with multiple manifests.

JBQ

[daern]

On Dec 17, 1:34 am, Jean-Baptiste Queru <j...@android.com> wrote:
> No estimates on the OTAs for various devices. Those are only loosely
> coupled to the code drops in AOSP, and they tend to involve a lot of
> additional approvals that I'm happy to know very little about.

This might be a completely obvious question to the more experienced
builders here, but I can't find it elsewhere, so here it is:

Regarding the "yakju" GSM version of the Galaxy Nexus, what would be
the difference between the OTA ROMs published here:
http://code.google.com/android/nexus/images.html
...and what I would get if I were to build the publicly available
sources for their respective versions (e.g. 4.0.2).

Are they totally different? (e.g. there are specific performance
optimisations or blobs that are not public)
No difference at all? (i.e. it's all in there, with no "magic sauce"
held back for 3rd party licensing reasons)
Somewhere in between?

Thoughts (or flames) welcomed :-)

Daern

[Jean-Baptiste Queru]

It's somewhere in between.

AOSP contains the exact same platform source code.

The binaries available from
http://code.google.com/android/nexus/drivers.html#maguro match those
from the same retail build (but I haven't released the binaries for
4.0.2 as I jumped straight to 4.0.3). Some of those binaries are
currently held back for licensing reasons, but those aren't "magic
sauce", they're just hardware-related binaries.

AOSP doesn't contain any of the proprietary Google apps. Those are
self-contained and aren't necessary for the proper operation of the
platform code itself.

AOSP also doesn't contain the private keys that is used to sign retail builds.

JBQ

[Ron M]

Is the Xoom support available in the master branch?

[Jean-Baptiste Queru]

Yes. You can use the same IML74K binaries, they work in both branches.

JBQ

[Ron M]

I am using the Master branch as of today, with the 4.03 binaries for
the GSM version (Maguro / IML74K ) - and the camera is not working
(plus spontaneous reboots :( )
Is that a known issue?
Is there a "stable" release where all Radio/Camera/HW accel/etc. have
been verified to some extent, that would be recommended for
installation on the Galaxy Nexus, or all AOSP branches suffer from the
Camera issue?

Thanks.

[Jean-Baptiste Queru]

The camera requires a proprietary DSP firmware, which isn't available in AOSP, for licensing reasons.

JBQ

[bradgog]

What happened to Toro support in AOSP? It appears to be gone?

[Alan Surrette]

It was cleaned up along with stingray and crespo4g. 

https://android-review.googlesource.com/#/q/status:merged,n,z 

And the binaries were archived.

http://code.google.com/android/nexus/drivers.html 

Now you know as much as I do. If you find out more, let us know. It really would be nice to know... something.

Thanks.

On Fri, Feb 3, 2012 at 4:14 PM, bradgog <goga...@gmail.com> wrote:

What happened to Toro support in AOSP? It appears to be gone?

[Milton Lie]

My build without the proprietary files from the device works, but once I build with proprietary files

extracted from my Verizon Galaxy Nexus and flash the device, it get's stuck at the initial Google screen.

Is this expected behavior?  I know the CDMA device is officially not supported.  Just wanted to know 

if my build is supposed to work or not.  More details steps listed below:

1.Build OASP android-4.0.3_r1 and flash Galaxy Nexus device

  cd <platform root>

  repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.3_r1

  repo sync

  Download and run extract-imgtec-toro.sh

  source build/envsetup.sh

  lunch

   - select full_toro-userdebug

  make

  adb reboot bootloader

  fastboot -w flashall

  At this point the Galaxy Nexus device is functional minus CDMA support.

2.Restore device back to factory load "mysid-icl53f"

  cd <directory with mysid-icl53f images>

  adb reboot bootloader

  flash-all.sh

3.Extract proprietary files from device and make

  cd <platform root>

  cd device/samsung/toro

  ./extract-files.sh

  cd ../../..

  source build/envsetup.sh

  lunch

   - select full_toro-userdebug

  make

  adb reboot bootloader

  fastboot -w flashall

  Now, after the reboot the Galaxy Nexus device hangs on the initital Google

  screen (does not advance to boot animation).

[Gregory Lange]

Not sure is this would be the correct place to ask...but is the source for ICS 4.0.3 still out there for the NS4G to get?  I know its been droped but i also know it was out there at one point and i just got my development system up and running again and wanted to get it.

[Jean-Baptiste Queru]

Assuming you've got a license to extract those files, this process is
known to not work on toro (i.e. the VZW Galaxy Nexus) devices, as it
can't deal with the APKs that are part of the CDMa/LTE stack (the
files on the device aren't in a shape that can be injected back in the
build system in a way that works).

Those files are distributed at
http://code.google.com/android/nexus/drivers.html#toro in a form that
works in the build system.

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

--