ubuntu-phone team mailing list archive

[Sergio Schvezov <sergio.schvezov@xxxxxxxxxxxxx>]

On Wed, Mar 27, 2013 at 10:47:42AM +0200, Jani Monoses wrote:
> On Fri, Mar 22, 2013 at 2:40 PM, Sergio Schvezov <
> sergio.schvezov@xxxxxxxxxxxxx> wrote:
> 
> > On Fri, Mar 22, 2013 at 02:41:51AM -0700, Christopher Noel Hesse wrote:
> > > I guess not. Furthermore I assume we already have the latest Android
> > 4.2.1
> > > codebase from CM-10.1.
> >
> > We don't do it automatically. If there is a good reason to though as when
> > we upgraded from ICS to JB to get manta support, we will.
> >
> > > Actually, upgrading to 4.2.2 wouldn't be that clever, because we would
> > > loose the ability to use usb debugging using adb before the first actual
> > > boot.
> >
> > There are other issues as well, APIs change and it needs to be worth it
> > to move there.
> >
> 
> The reason I originally asked is not enough to balance the reasons for
> staying
> on 4.2.1 but I am mentioning it in case others encounter this issue.
> 
> For Nexus devices Google only provides 4.2.2 factory images on their site
> https://developers.google.com/android/nexus/images
> And at least for the Nexus 4, those do not work with our current 4.2.1 based
> builds as some blobs have been removed.
> Also for the Nexus 4 adb pulling from a running devices does not succeed
> for two files so those need
> to be taken from a 3rd party like this
> https://github.com/gdetal/vendor_lge_mako

We did have some issues with mako as the images were pulled from Google for 
a while and replaced with a different one at a later time.

> Any build of the Ubuntu Touch sourcecode, even for already supported Nexus
> devices requires the person building get hold of the vendor blobs from
> elsewhere
> as they are not hosted along with the project.

I'm fairly certain that you can install an Ubuntu Touch image and do the
extract process from there for the nexus devices.

Cheers
Sergio