New factory images

[Jean-Baptiste Queru]

New factory images in the usual location
https://developers.google.com/android/nexus/images

-4.1.2 JZO54K for sojua in Canada (i.e. i9020a, 850MHz Nexus S).

-4.1.1 FH05 for mysidspr, which is the Sprint Galaxy Nexus.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, 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.

[Jean-Baptiste Queru]

What kind of problems are you running into with toroplus? If you work
in the master branch (which is the only one where toroplus is
supported), the only difference you should see compared to a toro or
maguro is that the cell network doesn't work on toroplus. Everything
else should be the same.

JBQ

PS: right now the cell network doesn't work on anything in master, but
that's an unrelated issue.

On Thu, Jan 17, 2013 at 4:22 AM, Justin Buser <jus...@justinbuser.com> wrote:
> I just bought a Galaxy Nexus from Sprint under the assumption that I'd be
> able to compile and test AOSP builds on it in the hopes of being able to
> contribute and further the cause so to speak. Needless to say I was
> disappointed to discover that this is no longer possible, lesson learned I
> guess but I'd still like to make some use of this thing. That being said I'm
> just wondering if it is possible to build the same JRO03U.L700FH05 build
> that's on the device now, or failing that one that is close enough that it
> would actually be 100% functional?
>
> Also, out of curiosity, not being as familiar with the build process as I'd
> like I'm wondering if there is any sort of documentation or basic run down
> of specifically how the various third party binaries/components tie into the
> build process. I've compiled a couple of vbox images that worked out pretty
> well but nothing that included proprietary drivers etc... so I'd like to
> learn a bit more about how those are incorporated and what if anything I
> could do to help resolve the compatibility issues that are preventing
> mysidspr support.
>
> Any info would be appreciated, thanks.

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

[Michael Novak]

In terms of documentation the source website has everything you need to get started.

http://s.android.com/source/building.html

and 

http://s.android.com/source/building-devices.html

mike.

On Thu, Jan 17, 2013 at 7:22 AM, Justin Buser <jus...@justinbuser.com> wrote:

I just bought a Galaxy Nexus from Sprint under the assumption that I'd be able to compile and test AOSP builds on it in the hopes of being able to contribute and further the cause so to speak. Needless to say I was disappointed to discover that this is no longer possible, lesson learned I guess but I'd still like to make some use of this thing. That being said I'm just wondering if it is possible to build the same JRO03U.L700FH05 build that's on the device now, or failing that one that is close enough that it would actually be 100% functional? 

Also, out of curiosity, not being as familiar with the build process as I'd like I'm wondering if there is any sort of documentation or basic run down of specifically how the various third party binaries/components tie into the build process. I've compiled a couple of vbox images that worked out pretty well but nothing that included proprietary drivers etc... so I'd like to learn a bit more about how those are incorporated and what if anything I could do to help resolve the compatibility issues that are preventing mysidspr support.

Any info would be appreciated, thanks.

On Wednesday, November 7, 2012 12:47:30 PM UTC-5, Jean-Baptiste Queru wrote:

--

[Jean-Baptiste Queru]

If you have AOSP contributions that improve the situation with
toroplus, I'd love to have a look.

JBQ

On Tue, Jan 22, 2013 at 12:59 PM, Nicholas M <thefasc...@gmail.com> wrote:
> Send me a Google Plus message or an email, and I'll help you get started.
> Building for the Toroplus is 100% possible, and hardly different from the
> Toro or even Maguro. There are just a few things in the source that need
> changing to get it fully functional.
> I understand how you feel, but don't be upset with JBQ or Google, because
> it's out of their hands, quite frankly. I personally, am so incredibly
> grateful that they included it in AOSP in any form at all, because none of
> expected it to happen. They've released everything they're responsible for,
> and the rest is up to outside forces.
>
> Send me a message though, and I'll be happy to get you started.
>
> On Sunday, January 20, 2013 11:37:13 PM UTC-5, Justin Buser wrote:
>>
>> Thanks, but I guess you missed the part about having already built the
>> source a couple times. When I say "not being as familiar with the build
>> process as I'd like" you should understand that I like to know everything
>> that's knowable about anything I do. My question was specifically related to
>> proprietary binaries and how they are included/compiled during the build
>> process.