ICS in AOSP: we're live, feel free to sync
Jean-Baptiste Queru
I strongly recommend syncing new clients: our implementation of git
and repo can deal with those better, so you're likely to sync a new
client faster than an incremental one.
The branches that you care about:
-android-4.0.1_r1 is the release branch, ITL41D, that is expected to
ship on Galaxy Nexus. That's the one you want to be using to port to
devices.
-ics-mr0 is the ICS development branch. It contains a few changes that
aren't in the release branch, so it might not be as stable. That's the
one you want to use if you plan to contribute to CTS.
-master is the usual master branch, it contains all of ics-mr0 plus a
few extra changes. That's the branch that you should use if you want
to contribute to the platform.
A few notes:
-All the external contributions that had been accepted in AOSP before
the servers went down have been merged into ICS.
-The release and development branch require the "classic" host
configurations (Ubuntu 10.04, or MacOS 10.6 with XCode 3). The master
branch had a few tweaks to make it work better on newer systems
(Ubuntu 11.10, Mac OS 10.7 with XCode 4.2) but it's not 100% there
yet.
-In addition to the usual emulator targets and Galaxy Nexus (a.k.a.
maguro), the master branch works experimentally on PandaBoard too
(a.k.a. panda).
-Proprietary binaries for 4.0.1 will be available in the next few
hours from their usual location
http://code.google.com/android/nexus/drivers.html
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.
Dominic Binks
I'm seeing this error - am I being stupid (again) or is something missing?
fatal: '../platform/abi/cpp.git' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
error: Cannot fetch platform/abi/cpp
--
Dominic Binks: dbi...@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
Jean-Baptiste Queru
the new AOSP manifests.
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
From there, in a clean directory, you should be able to sync a new client.
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
Manish Shakya
Initializing project platform/abi/cpp ...
fatal: '../platform/abi/cpp.git' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
error: Cannot fetch platform/abi/cpp
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
--
Manish Shakya
http://www.manishshakya.com.np
http://secs.oakland.edu/~ganesan/iMX/
Sandeep
Running on Ubuntu 11.04
Exception in thread Thread-8:
Traceback (most recent call last):
File "/usr/lib/python2.6/threading.py", line 532, in
__bootstrap_inner
self.run()
File "/usr/lib/python2.6/threading.py", line 484, in run
self.__target(*self.__args, **self.__kwargs)
File "/data/ssp/ics-aosp/.repo/repo/subcmds/sync.py", line 182, in
_FetchHelper
success = project.Sync_NetworkHalf(quiet=opt.quiet)
File "/data/ssp/ics-aosp/.repo/repo/project.py", line 926, in
Sync_NetworkHalf
if alt_dir is None and self._ApplyCloneBundle(initial=is_new,
quiet=quiet):
File "/data/ssp/ics-aosp/.repo/repo/project.py", line 1444, in
_ApplyCloneBundle
exist_dst = self._FetchBundle(bundle_url, bundle_tmp, bundle_dst,
quiet)
File "/data/ssp/ics-aosp/.repo/repo/project.py", line 1506, in
_FetchBundle
raise DownloadError('HTTP %s%s' % (e.code, msg))
DownloadError: HTTP 403 (Forbidden: Request forbidden -- authorization
will not help)
> >> JBQ
>
> > --
> > Dominic Binks: dbi...@codeaurora.org
> > Employee of Qualcomm Innovation Center, Inc.
> > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > --
> > You received this message because you are subscribed to the "Android
> > Building" mailing list.
>
> --
> Manish Shakyahttp://www.manishshakya.com.nphttp://secs.oakland.edu/~ganesan/iMX/
Paul Little
Thanks!
Jean-Baptiste Queru
to play with security holes to install a custom OS on it.
Beyond that, though, Nexus One is considered obsolete for the purpose
of AOSP, but I wouldn't be surprised to see some creatively
enterprising community members find a way to make things somewhat
work.
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
Kenneth Crudup
> I have repo version v1.7.7.6, but I keep getting the following error.
someone's changed their minds about us having it :) ); my ongoing
"repo sync" stopped in its tracks, and my other machine can't even get
off the ground.
morrildl
looking into it. Sit tight for a bit.
Karim Yaghmour
EXCELLENT!!! Thanks so much ... sync in progress :D
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
David Wang
Are the proprietary graphics binaries needed to support hardware
acceleration?
Meaning if I wanted to get this to run on my Nexus S, would I need the
nexus S 4.0 graphics binaries in order to get the hardware
acceleration features of ICS?
moontain
einmus
Jean-Baptiste Queru
graphics drivers for Nexus S, and if you get the basic system running
you'll probably run into some "interesting" performance issues.
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 Queru
closely, and we don't have such a release for Nexus S at the moment.
JBQ
TheMrRoxtar
a galaxy s 2 and wanted to know if i sync this will.i get ics. i want
to know what this is for and have a need to learn from you guys.
please help thmx so much.
Conley Owens
> god i shouldnt even be asking this but i am new to this a bit. i have
> a galaxy s 2 and wanted to know if i sync this will.i get ics. i want
> to know what this is for and have a need to learn from you guys.
> please help thmx so much.
Syncing refers to downloading ICS source code. If you have an
unsupported (non-nexus) phone, you may not be able to build the source
code to run on your device.
Kenneth Crudup
> The servers are fine, actually. We know what is causing this, we're looking into it. Sit tight for a bit.
blunden
It is the same GPU after all, albeit with a much lower clock speed and
I assume that doesn't get set by the GPU driver.
Also, is there any documentation for the changes you implemented in
ICS compared to GB for the GPU drivers that could be helpful in
determining if it's even feasible to try getting the GB drivers to
work?
I am getting a Galaxy Nexus (hopefully a 32GB GSM version if that ever
turns up) but it would still be nice to be able to experiment with the
N1.
cddykes10
ok thnx so much that helps much thank u
Jean-Baptiste Queru
Nexus to Nexus S. Interestingly in fact, the GPU libraries that ship
on Galaxy Nexus don't work on PandaBoard, even though those are both
OMAP44x0 systems, and PandaBoard uses a specific set of libraries.
I don't have any deeper insight in the exact changes in the graphics
pipeline since Gingerbread, sorry.
JBQ
yjwong92
Is there going to be a build configuration for Exynos? Or SMDK310.
Regards,
Wong Yong Jie
Conley Owens
> Hi,
>
> Is there going to be a build configuration for Exynos? Or SMDK310.
Sorry, but we can really only provide support for nexus devices.
Jean-Baptiste Queru
that Google is involved in, and no flagship devices were based on
those chips. You'd have to ask the manufacturers of those chips to
provide the appropriate source files.
Thanks,
JBQ
einmus
use a fresh repo. It'll be fine.
> >> JBQ
>
> > --
> > Dominic Binks: dbi...@codeaurora.org
> > Employee of Qualcomm Innovation Center, Inc.
> > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > --
> > You received this message because you are subscribed to the "Android
> > Building" mailing list.
Matt Oakes
blunden
Since I've never seen that kind of thing documented, I would assume
one has to try to determine it using the "staring at code"
approach. ;)
Do you have any idea if the emulator drivers would work to give
software rendering at least (I know it would be dirt slow)? If so,
that would at least allow it to boot up and allow you to try the newer
build.
Michael Payne
the Nexus S. Are the binaries going to be following soon? I really
don't want my first build on my PandaBoard :/
Jean-Baptiste Queru
still polishing that build.
We had to make a choice: release ITL41D in its Galaxy-Nexus-only
state, or wait until we have a build that also works on Nexus S. There
are pros and cons to either approach, and we picked the former.
JBQ
Bzbit
Can somone please tell me what kernel is used for ICS and where to
clone it from.
I like to build the kernel from source.
Thx
> > >http://groups.google.com/**group/android-building?hl=en<http://groups.google.com/group/android-building?hl=en>
>
> > --
>
> - Show quoted text -
Ne0
So does this mean i can't sync from a previous repo? I tried and get
the same issue.
On Nov 14, 11:27 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> You need a recent version of repo, 1.7.7 or newer, to be able to parse
> the new AOSP manifests.
>
> curlhttps://dl-ssl.google.com/dl/googlesource/git-repo/repo> ~/bin/repo
>
> From there, in a clean directory, you should be able to sync a new client.
>
> JBQ
>
> >> JBQ
>
> > --
> > Dominic Binks: dbi...@codeaurora.org
> > Employee of Qualcomm Innovation Center, Inc.
> > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > --
> > You received this message because you are subscribed to the "Android
> > Building" mailing list.
Jean-Baptiste Queru
for a few weeks), that should be all transparent.
If that's an older previous repo that hasn't been synced in months. It
is theoretically possible to update an existing client to use the new
repo. In .repo/repo/.git/config, under remote "origin", change the url
to be https://android.googlesource.com/tools/repo
JBQ
Jean-Baptiste Queru
what happens on that front, which isn't something that I'm involved
in.
JBQ
On Tue, Nov 15, 2011 at 3:55 AM, Matt Oakes <oak...@googlemail.com> wrote:
> Does this mean we will be getting support for crespo in ASOP ICS in the
> future?
>
Brandon
has been covered elsewhere, I have not been able to find any
information about it.
Jean-Baptiste Queru
processes and schedules, and I have no visibility over their plans.
JBQ
Matt Oakes
Perfect. That's great :-) just good to know it will be out at some point in the future. We have some nexus s devices we currently use for testing and it would be a shame to not be able to use them.
Is there any estimates on how long before it will be out?
Great work! Loving that it's out before the device :-)
Jean-Baptiste Queru
precisely enough to have any such estimate, sorry.
JBQ
Matt Oakes
It seems mines fairly good. I predicted that would be the answer ;-)
powder
I followed above suggestions, but still get the error:
repo sync
repository
fatal: The remote end hung up unexpectedly
error: Cannot fetch platform/abi/cpp
>
> > >> -master is the usual master branch, it contains all of ics-mr0 plus a
> > >> few extra changes. That's the branch that you should use if you want
> > >> to contribute to the platform.
>
> > >> A few notes:
>
> > >> -All the external contributions that had been accepted in AOSP before
> > >> the servers went down have been merged into ICS.
>
> > >> -The release and development branch require the "classic" host
> > >> configurations (Ubuntu 10.04, or MacOS 10.6 with XCode 3). The master
> > >> branch had a few tweaks to make it work better on newer systems
>
> > >> -In addition to the usual emulator targets and Galaxy Nexus (a.k.a.
> > >> maguro), the master branch works experimentally on PandaBoard too
> > >> (a.k.a. panda).
>
> > >> -Proprietary binaries for 4.0.1 will be available in the next few
> > >> hours from their usual location
> > >>http://code.google.com/**android/nexus/drivers.html<http://code.google.com/android/nexus/drivers.html>
>
> > >> JBQ
>
> > > --
> > > Dominic Binks: dbi...@codeaurora.org
> > > Employee of Qualcomm Innovation Center, Inc.
> > > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > > --
> > > You received this message because you are subscribed to the "Android
> > > Building" mailing list.
> > > To post to this group, send email to android-building@googlegroups.**com<android-...@googlegroups.com>
> > > To unsubscribe from this group, send email to
Magnus Bäck
powder <jonas....@gmail.com> wrote:
> I followed above suggestions, but still get the error:
>
> repo sync
> fatal: '../platform/abi/cpp.git' does not appear to be a git
> repository
> fatal: The remote end hung up unexpectedly
> error: Cannot fetch platform/abi/cpp
Then you're *still* using an old Repo. Start off with an empty directory
when you run "repo init", and make sure your Repo really is the latest
one. The hostname in the URL in the repo script should be
android.googlesource.com rather than android.git.kernel.org (although,
if that was the problem you wouldn't get this far in the first place).
--
Magnus B�ck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
Xianghua Xiao
xianghua
On Tue, Nov 15, 2011 at 3:16 PM, Magnus Bäck
<magnu...@sonyericsson.com> wrote:
> On Tuesday, November 15, 2011 at 21:04 CET,
> powder <jonas....@gmail.com> wrote:
>
>> I followed above suggestions, but still get the error:
>>
>> repo sync
>> fatal: '../platform/abi/cpp.git' does not appear to be a git
>> repository
>> fatal: The remote end hung up unexpectedly
>> error: Cannot fetch platform/abi/cpp
>
> Then you're *still* using an old Repo. Start off with an empty directory
> when you run "repo init", and make sure your Repo really is the latest
> one. The hostname in the URL in the repo script should be
> android.googlesource.com rather than android.git.kernel.org (although,
> if that was the problem you wouldn't get this far in the first place).
>
> --
> Magnus Bäck Opinions are my own and do not necessarily
> SW Configuration Manager represent the ones of my employer, etc.
> Sony Ericsson
>
> --
> 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
Michael Payne
binaries, as well as the Galaxy heading to me in the mail.
On Nov 15, 9:06 am, Jean-Baptiste Queru <j...@android.com> wrote:
> It's all tied to having a consumer-ready build for Nexus S, and we're
> still polishing that build.
>
> We had to make a choice: release ITL41D in its Galaxy-Nexus-only
> state, or wait until we have a build that also works on Nexus S. There
> are pros and cons to either approach, and we picked the former.
>
> JBQ
>
> On Mon, Nov 14, 2011 at 8:21 PM, Michael Payne
>