JBQ, on behalf of the AOSP team.
--
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.

I assume this means I can Tweet?

On 14 Nov., 22:59, Jean-Baptiste Queru <j...@android.com> wrote:
> Hi! We just released a bit of code we thought this group might be interested in.
> Over at our Android Open-Source Project git servers, the source code
> for Android version 4.0 (Ice Cream Sandwich) is now available.

The instructions are at http://source.android.com/source/downloading.html

JBQ

JBQ

$ repo init -u https://android.googlesource.com/platform/manifest -b
android-4.0.1_r1
... a lot of tags info up to android 2.3.7_r1
error: revision android-4.0.1_r1 in manifests not found

-Sam

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

error: revision android-4.0.1_r1 in manifests not found

--
Dominic Binks: dbi...@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

JBQ

However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.

Wait till I say download!

-push to master, update the master manifest.
-push to the development branch, create the matching manifest.
-push to the release branch, tag it, create the machine manifest.

I'm still in the first phase, which is the longest one.

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
>

--

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.

-sbq

-----Original Message-----
From: android-...@googlegroups.com
[mailto:android-...@googlegroups.com] On Behalf Of Jean-Baptiste Queru

On Mon, Nov 14, 2011 at 2:46 PM, Weston Weems <wwe...@gmail.com> wrote:
> Have the requirements for Ice cream sandwich been posted anywhere? I'd be
> curious to see what hardware would be capable of running it.
>

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

Great..
Thank you Mr. JBQ for the info..

Waiting for the sync process completed :)

On Mon, Nov 14, 2011 at 3:09 PM, PRO <hassan...@gmail.com> wrote:
> I guess I'm already disqualified for compiling the ICS from source which is
> a really bummer. I wanted to have fun but I guess i will be sad lol. Have
> fun guys..

The hardware suggestions are just suggestions.  You may be able to
build ICS with the hardware you have, it just might take a while.

>
> p.s If anyone here needs help or compiling ICS for Galaxy s II T-mobile or
> any other SGS II variants let me know because thats the device I was
> attempting to compile ICS for :D
>

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

--

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.

Mr. JBQ, i can still using --mirror argument to make local mirror? And just wondering, how big the ICS source?

The ICS history is about 6GB overall (though the current version is a
little bit smaller as it only supports Galaxy Nexus). A mirror would
probably be a bit larger than that.

JBQ

JBQ

On Mon, Nov 14, 2011 at 3:37 PM, Pete <peteral...@gmail.com> wrote:
> Thanks for all the efforts JBQ and the Android Team!
> When do you plan on pushing the ICS device setups for the Nexus S and 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
>

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

JBQ

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

JBQ

On Mon, Nov 14, 2011 at 2:30 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> I've got a number of tasks on my plate related to the kernel trees,
> and that's one of them.
>
> JBQ
>
> On Mon, Nov 14, 2011 at 2:25 PM, Carlos Silva <r3...@r3pek.org> wrote:
>> Just one quick question JBQ,
>> will the kernel trees come with a master tag? Right now the log and the tree
>> aren't available via gitweb because of this :/
>> Thanks

>>
>> On Mon, Nov 14, 2011 at 20:59, Jean-Baptiste Queru <j...@android.com> wrote:
>>>
>>> Hi! We just released a bit of code we thought this group might be
>>> interested in.
>>> Over at our Android Open-Source Project git servers, the source code
>>> for Android version 4.0 (Ice Cream Sandwich) is now available.
>>> Here's how to get it:Follow the instructions at
>>> http://source.android.com/source/downloading.htmlCheck out the

You should grab the newest version of repo at:
https://dl-ssl.google.com/dl/googlesource/git-repo/repo

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

Ok, Thank you very much for updating the manifest..

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

When you're done, delete your .repo directory, and restart.

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
>

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

On Nov 14, 4:59 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Hi! We just released a bit of code we thought this group might be interested in.
> Over at our Android Open-Source Project git servers, the source code
> for Android version 4.0 (Ice Cream Sandwich) is now available.

> That's it! However since this is a large push, please be aware that it
> will take some time to complete. If you sync before it's done, you'll
> get an incomplete copy that you won't be able to use, so please wait
> for us to give the all-clear before you sync.
> This is actually the source code for version 4.0.1 of Android, which
> is the specific version that will ship on the Galaxy Nexus, the first
> Android 4.0 device. In the source tree, you will find a device build
> target named "full_maguro" that you can use to build a system image
> for Galaxy Nexus. Build configurations for other devices will come
> later.
> Unfortunately we still don't have our Gerrit code review servers back
> online. That remains our top priority though, and we hope to have them
> back soon.
> This release includes the full history of the Android source code
> tree, which naturally includes all the source code for the Honeycomb
> releases. However, since Honeycomb was a little incomplete, we want
> everyone to focus on Ice Cream Sandwich. So, we haven't created any
> tags that correspond to the Honeycomb releases (even though the
> changes are present in the history.)
>
> JBQ, on behalf of the AOSP team.

I get error about "does not look like a v2 bundle file".
But the sync process is continue, that is normal?

On Monday, November 14, 2011 6:08:10 PM UTC-6, Lucky Meeh wrote:

All -

Please stop this madness. We are tired of having to hack our phones
just to get pure Android on it. I had thought that ICS was going to
fix this problem...  Please close the source and improve the OS code
so OEMs won't have to mess around with it.

Thank you,

- A consumer & developer

On Nov 14, 3:57 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> I've updated the mirror manifest, so you can sync that and then
> initialize new ICS clients from your mirror.
>
> JBQ
>
>
>
>
>
>
>
>
>
> On Mon, Nov 14, 2011 at 3:28 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> > Yes, you can still do that, but I haven't updated that manifest yet.
>
> > The ICS history is about 6GB overall (though the current version is a
> > little bit smaller as it only supports Galaxy Nexus). A mirror would
> > probably be a bit larger than that.
>
> > JBQ
>

> > On Mon, Nov 14, 2011 at 3:22 PM, Teguh Sobirin <tj.styl...@gmail.com> wrote:
> >> Mr. JBQ, i can still using --mirror argument to make local mirror? And just
> >> wondering, how big the ICS source?
>
> >> Pada 15 Nov 2011 05.19, "Jean-Baptiste Queru" <j...@android.com> menulis:
>
> >>> There's clearly been a formatting accident with my email, sorry about
> >>> that.
>

>
> >>> JBQ
>
> >>> On Mon, Nov 14, 2011 at 1:59 PM, Jean-Baptiste Queru <j...@android.com>
> >>> wrote:
> >>> > Hi! We just released a bit of code we thought this group might be
> >>> > interested in.
> >>> > Over at our Android Open-Source Project git servers, the source code
> >>> > for Android version 4.0 (Ice Cream Sandwich) is now available.
> >>> > Here's how to get it:Follow the instructions at

> >>> > 'ics-release' branch:repo init -u

On Mon, Nov 14, 2011 at 4:24 PM, bmeike <blake...@gmail.com> wrote:
> Hey, is there a special manifest for building a mirror?

repo init -u https://android.googlesource.com/platform/manifest --mirror
should create a mirror correctly

~cco3

repo init -u https://android.googlesource.com/mirror/manifest --mirror

Note that it's mirror/manifest instead of the usual platform/manifest.

Once you have a manifest, you can repo init new clients from it, e.g.:

repo init -u <mirror>/platform/manifest.git -b android-4.0.1_r1

JBQ

On Mon, Nov 14, 2011 at 23:37, Carlos Silva <r3...@r3pek.org> wrote:

 # du -hs android.git.r3pek.org

6.5G android.git.r3pek.org

^^ that's from my mirror

Wow, 6.5Gb and still syncing?
so will more big than 6Gb.
Thank you for your info.

I'm already working on it, actually.

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
>

--

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.

On Mon, Nov 14, 2011 at 8:08 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> You're the first one to actually ask for those source files :)

I bet you say that to all the developers. ;-)

Cheers,
Nathaniel

Maguro (i.e. Galaxy Nexus) is next on my 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
>

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

Ok, so the actual size is around 6.5Gb right? before you make me think is biger than 8Gb :D

thank you..

A current ICS download is about 4.6GB over-the-wire if I remember correctly.

A full mirror is probably 6.4GB, as it contains some projects that
aren't in ICS (toolchain, kernels, and projects from older releases).

That doesn't count any space you need to unpack the source code
locally, and the space you need to do a build.

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.

On Nov 14, 1:59 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Hi! We just released a bit of code we thought this group might be interested in.
> Over at our Android Open-Source Project git servers, the source code
> for Android version 4.0 (Ice Cream Sandwich) is now available.

> That's it! However since this is a large push, please be aware that it
> will take some time to complete. If you sync before it's done, you'll
> get an incomplete copy that you won't be able to use, so please wait
> for us to give the all-clear before you sync.
> This is actually the source code for version 4.0.1 of Android, which
> is the specific version that will ship on the Galaxy Nexus, the first
> Android 4.0 device. In the source tree, you will find a device build
> target named "full_maguro" that you can use to build a system image
> for Galaxy Nexus. Build configurations for other devices will come
> later.
> Unfortunately we still don't have our Gerrit code review servers back
> online. That remains our top priority though, and we hope to have them
> back soon.
> This release includes the full history of the Android source code
> tree, which naturally includes all the source code for the Honeycomb
> releases. However, since Honeycomb was a little incomplete, we want
> everyone to focus on Ice Cream Sandwich. So, we haven't created any
> tags that correspond to the Honeycomb releases (even though the
> changes are present in the history.)
>
> JBQ, on behalf of the AOSP team.

On Mon, Nov 14, 2011 at 6:20 PM, algopats <algo...@gmail.com> wrote:
> Keep getting below error for some sub directories on repo sync. I try
> deleting the below folder manually, but the error happens in another
> dir. How do i ask repo to delete ("full sync" ) as need ? thanks.
>
> "Fetching projects: 100% (221/221), done.
> error: Cannot remove project "packages/apps/AccountsAndSyncSettings":
> uncommitted changes are present
>       commit changes, then run sync again"

You have changed something in that project.  You can `cd
packages/apps/AccountsAndSyncSettings` and `git diff` to see those
changes.

If you don't care about that change, or didn't mean to create it, you
can `cd packages/apps/AccountsAndSyncSettings` `git reset --hard` and
then `repo sync`.

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

git clone https://android.googlesource.com/kernel/omap
cd omap
git checkout remotes/origin/android-omap-panda-3.0

JBQ

On Mon, Nov 14, 2011 at 6:19 PM, jazd <jaredwi...@gmail.com> wrote:
> Can someone tell me how to download this kernel? I just want to have a look
> at it without downloading 6GB+ using the repo tool.
>

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

On Mon, Nov 14, 2011 at 6:30 PM, algopats <algo...@gmail.com> wrote:
> Thanks for quick reply. This keeps happening once i clear the issue
> (either git reset or rm -rf).
> How do i automate it for all (potentially subsequent) folders for
> which it might give similar error msg. Thanks.

repo forall -c "git reset --hard"

On 14 November 2011 20:29, Jean-Baptiste Queru <j...@android.com> wrote:
> To download the panda kernel, if I'm not mistaken:
>
> git clone https://android.googlesource.com/kernel/omap
> cd omap
> git checkout remotes/origin/android-omap-panda-3.0

Will full_maguro work with this kernel on Panda?

--

Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

With a heavy hammer, "rm -rf *" from the root of a source tree. This
doesn't affect .repo, where all the synced data is actually stored.

JBQ

full_maguro is unlikely to work (but I haven't actually tried).

JBQ

yes, the space is not problem, i have big enough space to place the repo and for building. the problem is on my internet bandwidht, every Gigabyte is realy hard for me to download the repo. so the mirror function is very usefull for me :)

JBQ

I create the mirror and will share that to the local community, since the internet connection is very slow in here :)

On 14 November 2011 20:35, Jean-Baptiste Queru <j...@android.com> wrote:
> You should probably use full_panda for panda as you get started.
> Detailed instructions are in device/ti/panda/README

Ah great - thanks.

On Nov 14, 6:34 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Warning, dangerous command ahead, proceed with caution.
>
> With a heavy hammer, "rm -rf *" from the root of a source tree. This
> doesn't affect .repo, where all the synced data is actually stored.
>
> JBQ

On 14 November 2011 20:45, Zach Pfeffer <zach.p...@linaro.org> wrote:
> On 14 November 2011 20:35, Jean-Baptiste Queru <j...@android.com> wrote:
>> You should probably use full_panda for panda as you get started.
>> Detailed instructions are in device/ti/panda/README
>
> Ah great - thanks.

Hmm...is anyone else seeing:

host C++: libclangStaticAnalyzerCheckers <=
external/clang/lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp
arm-linux-androideabi-g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [out/target/product/panda/obj/STATIC_LIBRARIES/libLLVMAnalysis_intermediates/ScalarEvolution.o]
Error 1
make: *** Waiting for unfinished jobs....
arm-linux-androideabi-g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [out/target/product/panda/obj/STATIC_LIBRARIES/libLLVMCore_intermediates/Function.o]
Error 1
arm-linux-androideabi-g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [out/target/product/panda/obj/STATIC_LIBRARIES/libLLVMBitReader_2_7_intermediates/BitcodeReader.o]
Error 1
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libclangARCMigrate_intermediates/TransAutoreleasePool.o]
Error 1

...I'm using make -j32

backing off to -j16.

On 14 November 2011 20:29, Jean-Baptiste Queru <j...@android.com> wrote:

> To download the panda kernel, if I'm not mistaken:
>
> git clone https://android.googlesource.com/kernel/omap
> cd omap
> git checkout remotes/origin/android-omap-panda-3.0

Hmm... hitting:

mm/page-writeback.c: In function 'write_cache_pages':
mm/page-writeback.c:863: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.

See <http://gcc.gnu.org/bugs.html> for instructions.

with

make ARCH=arm CROSS_COMPILE=/mnt/user/ics/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
defconfig panda_defconfig
make ARCH=arm CROSS_COMPILE=/mnt/user/ics/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

Bero, do you remember the fix for this? I think you sent a bug report in.

--

Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

JBQ

On 14 November 2011 20:54, Zach Pfeffer <zach.p...@linaro.org> wrote:
> mm/page-writeback.c:863: internal compiler error: Segmentation fault

Should be fixed in our latest toolchain build:
https://android-build.linaro.org/builds/~linaro-android/toolchain-4.6-2011.11/#build=4

ttyl
bero

Getting files for Nexus S is fundamentally tied to having a matching
consumer release, which isn't my domain of expertise.

Thanks for understanding :)

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
>

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

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
>

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

JBQ

Does that mean that eventually we will get e.g an Asus Transformer or Samsung Galaxy Tab 10.1 official tree too?

JBQ

On Tue, Nov 15, 2011 at 1:17 PM, meLIanTQ <melian.t...@gmail.com> wrote:
> Thanks for the fast response.
>
> No date available ?
>

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

Flagship devices are the devices for which Google is directly involved
in the development. AOSP is created as a subset the source code for
those devices, and  device manufacturers then use that source code to
create their devices. Focusing on flagship devices allows Google to
make sure that the source code that ends up on AOSP is actually ready.

The story for Honeycomb was slightly different, but still essentially
the same: Google created a consumer-ready tablet, took a subset of
that source code and made it available to some device manufacturers,
who then used it to create their own devices.

On the tablet front, the flagship device was the Motorola Xoom,
specifically the VZW and Wifi variants in the US. The Asus Transformer
and Samsung Galaxy Tab 10.1 were developed directly by Asus and
Samsung without direct involvement from Google, and I don't have
access to the files that'd be necessary to support those in AOSP (but
I'd gladly work with Asus and Samsung if they'd like some help to
offer such support as separate downloads).

JBQ

2011/11/15 József Király <foni...@gmail.com>:

"Each set of binaries comes as a self-extracting script in a
compressed archive. After uncompressing each archive, run the included
self-extracting script from the root of the source tree, confirm that
you agree to the terms of the enclosed license agreement, and the
binaries and their matching makefiles will get installed in the
vendor/ hierarchy of the source tree."

JBQ

In my position in AOSP, I prefer to walk the talk on device openness
and let others follow if they like where I'm going. The first steps to
support devices in AOSP were rocky, but that's now quite a routine
process, and the tools I use are all Open-Source for others to look at
and re-use.

>
> "Each set of binaries comes as a self-extracting script in a
> compressed archive. After uncompressing each archive, run the included
> self-extracting script from the root of the source tree, confirm that
> you agree to the terms of the enclosed license agreement, and the
> binaries and their matching makefiles will get installed in the
> vendor/ hierarchy of the source tree."
>
> JBQ
>
>
>
>
>
>
>
>
>
> On Tue, Nov 15, 2011 at 1:55 PM, othy74 <oth...@googlemail.com> wrote:
> > The two maguro binary packages (samsung + imgtek) contain no
> > reassemble scripts. I guess I just move the extracted vendor folder
> > into my ICS folder. But how exactly does the build script find out
> > about these binaries being available now? (I am getting this message
> > from make: "No private recovery resources for TARGET_DEVICE maguro".
> > What is this supposed to tell me?)
> > My ICS system.img for maguro - without any binaries yet - has
> > 167,041,792 bytes. Does that sound reasonable? (My Gingerbread
> > system.img for crespo - including binaries drivers - has 114,662,292
> > bytes.)
> > Thanks again.
>
> > On Nov 15, 9:15 pm, Jean-Baptiste Queru <j...@android.com> wrote:

Feel free to go poke around in the vendor tree, or to look in
device/samsung/maguro/self-extractors to see how the self-extractors
themselves are created. I apologize in advance for the horrible shell
scripts, but they work well enough :)

Your numbers sound about right, 170MB for a plain AOSP build of ICS is
my rule of thumb. It is indeed significantly larger than Gingerbread.

JBQ

> Your numbers sound about right, 170MB for a plain AOSP build of ICS is
> my rule of thumb. It is indeed significantly larger than Gingerbread.

JBQ, I asked this last night but never received a response. The face unlock libs are missing from this source. They are also not in the extract-files.sh so i dont think they would be proprietary. Are these left out for a reason?

Face Unlock is a proprietary Google application, which lives above the
Android platform and isn't necessary to use the platform itself
(unlike the proprietary files that live below the platform). It goes
along with the other various proprietary applications that aren't part
of the platform and aren't distributed along with AOSP.

JBQ

On Nov 15, 9:25 pm, Bryce Walter <b.t.wal...@gmail.com> wrote:
> Okay, thanks for the response JBQ.
>
> On Tue, Nov 15, 2011 at 6:59 PM, Jean-Baptiste Queru <j...@android.com>wrote:
>
>
>
>
>
>
>
> > Sorry I didn't get a chance to reply earlier, this thread has been
> > overwhelming.
>
> > Face Unlock is a proprietary Google application, which lives above the
> > Android platform and isn't necessary to use the platform itself
> > (unlike the proprietary files that live below the platform). It goes
> > along with the other various proprietary applications that aren't part
> > of the platform and aren't distributed along with AOSP.
>
> > JBQ
>

> > wrote:
> > > JBQ, I asked this last night but never received a response. The face
> > unlock
> > > libs are missing from this source. They are also not in the
> > extract-files.sh
> > > so i dont think they would be proprietary. Are these left out for a
> > reason?
>
> > > On Nov 15, 2011 5:37 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
>
> > >> You're asking about non-technical issues that aren't really related to
> > >> AOSP, so I'm doubly unqualified to comment on that, sorry.
>
> > >> JBQ
>

> > >> > I know that page already, I was talking about if there were even a
> > >> > little
> > >> > talk about changing that part I mentioned, even if as an idea at a
> > >> > "usual
> > >> > Friday afternoon brainstorming in the office" or something like that.
> > >> > I'm
> > >> > asking, if you've ever considered considering the change of the
> > current
> > >> > rules.
>
> > >> > 2011/11/15 Jean-Baptiste Queru <j...@android.com>
>
> > >> >> Licensing information:
> >http://source.android.com/source/licenses.html
> > >> >> - there was no change of plan in that area, you can trace that line
> > >> >> all the way back to the original announcement 4 years ago.
>
> > >> >> In my position in AOSP, I prefer to walk the talk on device openness
> > >> >> and let others follow if they like where I'm going. The first steps
> > to
> > >> >> support devices in AOSP were rocky, but that's now quite a routine
> > >> >> process, and the tools I use are all Open-Source for others to look
> > at
> > >> >> and re-use.
>
> > >> >> JBQ
>

> > >> >> >> > Does that mean that eventually we will get e.g an Asus
> > Transformer
> > >> >> >> > or
> > >> >> >> > Samsung Galaxy Tab 10.1 official tree too?
>
> > >> >> >> > 2011.11.15. 22:15, "Jean-Baptiste Queru" <j...@android.com> ezt
> > >> >> >> > írta:
>
> > >> >> >> >> Yes. Releasing device support in AOSP goes together with having
> > >> >> >> >> the
> > >> >> >> >> same build available to consumers. As more of the flagship
> > >> >> >> >> devices
> > >> >> >> >> that Google is involved on get ICS, the matching support will
> > be
> > >> >> >> >> added
> > >> >> >> >> in AOSP too, and the matching binaries will be released.
>
> > >> >> >> >> JBQ
>
> > >> >> >> >> On Tue, Nov 15, 2011 at 1:05 PM, meLIanTQ

JBQ

Please note that that is not our official repository.

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

--

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.

Some community members are hosting their own mirrors, I'll let them
chime in if they want. Please be kind of them and don't abuse their
servers and bandwidth.

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
>

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

This being Google, we don't like to talk about future plans for things.

But I also miss a web browseable version of AOSP, and could see how
that may appear in the future.

On Thu, Nov 17, 2011 at 20:54, Isaac Levy <Isaac....@gmail.com> wrote:

I find http://codesearch.google.com/#/&exact_package=android unreliable.
[Say, Searching for "coreApp" does not return
packages/apps/Phone/AndroidManifest.xml]
codesearch.google.com is retiring anyway.

Until recently, I've always had my own local OpenGrok setup, with the
tip always indexed, which tremendously helped me in following the
android evolution.  Wondering what others do, to search the code...

-Jey

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

On Thu, Nov 17, 2011 at 22:55, Jey Michael <jey.m...@gmail.com> wrote:

Carlos, Do you have, or plan to add, "source search utility" as well?

On Nov 14, 1:59 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Hi! We just released a bit of code we thought this group might be interested in.
> Over at our Android Open-Source Project git servers, the source code
> for Android version 4.0 (Ice Cream Sandwich) is now available.
> Here's how to get it:Follow the instructions athttp://source.android.com/source/downloading.htmlCheckout the
> 'ics-release' branch:repo init -uhttps://android.googlesource.com/platform/manifest-b android-4.0.1_r1
> That's it! However since this is a large push, please be aware that it
> will take some time to complete. If you sync before it's done, you'll
> get an incomplete copy that you won't be able to use, so please wait
> for us to give the all-clear before you sync.
> This is actually the source code for version 4.0.1 of Android, which
> is the specific version that will ship on the Galaxy Nexus, the first
> Android 4.0 device. In the source tree, you will find a device build
> target named "full_maguro" that you can use to build a system image
> for Galaxy Nexus. Build configurations for other devices will come
> later.
> Unfortunately we still don't have our Gerrit code review servers back
> online. That remains our top priority though, and we hope to have them
> back soon.
> This release includes the full history of the Android source code
> tree, which naturally includes all the source code for the Honeycomb
> releases. However, since Honeycomb was a little incomplete, we want
> everyone to focus on Ice Cream Sandwich. So, we haven't created any
> tags that correspond to the Honeycomb releases (even though the
> changes are present in the history.)
>
> JBQ, on behalf of the AOSP team.

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

If you're looking at it from the point of view of the Android
Open-Source Project, that'd be 11/14.

If you're looking at it from the point of view of first retail
availability, that'd be 11/17.

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
>

--

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.

Any news about the x86 kernel source ?

Thanks

On Nov 16, 7:14 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Working on it. There are plenty of things on my plate at the moment,
> and I can only work on one at a time :)
>
> JBQ
>
>
>
>
>

JBQ

If it's not part of the platform, should Face Unlock be removed from the page
 http://developer.android.com/sdk/android-4.0-highlights.html since it gives the impression we have some Face Recognition APIs to develop with?

BR,
Jimmy

Thanks,
JBQ

export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=<path_to_master>/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH

git clone https://android.googlesource.com/kernel/omap
cd 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
>

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

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
>

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

JBQ

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
>

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

On Tue, Nov 15, 2011 at 21:15, Jean-Baptiste Queru <j...@android.com> wrote:
> There are some binaries for maguro available at

> get graphics, cell and wifi, nfc, sensors. notably missing are the
> camera (and other HW codecs) and GPS. We're working on filling in the
> blanks.
>
> JBQ
>

This answers my question why the camera is not working in AOSP. Is
there a way to extract the drivers from an installed version of the
factory images?

Does extract-files.sh extract those?

Regards,
Dirk

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
>

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

source build/envsetup.sh
lunch full_panda-eng
make fastboot

TARGET_PRODUCT=full_panda
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release

host C: fastboot <= system/core/fastboot/protocol.c

In file included from /usr/include/stdio.h:28:0,
                 from system/core/fastboot/protocol.c:29:
/usr/include/features.h:323:26: fatal error: bits/predefs.h: No such file or directory
compilation terminated.
make: *** [out/host/linux-x86/obj/EXECUTABLES/fastboot_intermediates/protocol.o] Error 1

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

--

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.

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

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