I'm sorry Jani, but I'm lost :-) Please correct me if I'm wrong. That "Manual Download & Installation" tells about 3 steps: 1. Flash boot, recovery, system images. I presume these images should contains some phablet code (at least for recovery - support for autodeploy, otherwise next step could fail). This cannot be 'pure' CM/AOSP or vendor images. Thus I assume it is phablet-enabled Android side 2. Install some zip file for specific device. In case of 4 supported devices I can get it from cdimage.ubuntu.com. Alternatively, I can build it by myself (ex. for device that is not supported on cdimage.ubuntu.com, cm-..tilapia.zip) These zips contain boot.img and content of system folder. At first glance these are the same boot.img and content of system.img in step #1 3. Install some zip which in turn contain device-independent tar.gz
Step #2 seems unnecessary but does not impact the install procedure. 2013/11/6 Jani Monoses <[email protected]> > Hi > you need to download that exact zip from the Ubuntu servers. It is the > full Ubuntu userland. the cm-...tilapia.zip is the Android side, same as > system.img and boot.img but packaged in a zip for easy update via the > recovery image. > So the Ubuntu side is prrebuilt for armhf and should be almost identical > for each device. > On this page > http://cdimage.ubuntu.com/ubuntu-touch/saucy/daily-preinstalled/20131018/ > you can see boot, recovery and system.img files which are the regular ones > built from an Android tree for all four supported Nexus devices. > Then there is also > http://cdimage.ubuntu.com/ubuntu-touch/saucy/daily-preinstalled/20131018/saucy-preinstalled-touch-armhf.tar.gzwhich > is the Ubuntu rootfs and which is device independent. > > Also you do not fastboot flash system system.img . It is not the Android > image that will be the rootfs. It is Ubuntu from the above zip, and the > Android system.img lives under /var/lib/lxc/android and gets mounted only > after the Ubuntu userland is booted up. > > So first you need to make sure you boot into Ubuntu and not Android. You > have to use the ubuntu-touch-generic-initrd package as the initrd as seen > in build/core/Makefile > > Jani > > > On Wed, Nov 6, 2013 at 11:33 AM, Dmitry Smirnov <[email protected]>wrote: > >> One more question. >> >> "Manual Download & Installation" section on >> https://wiki.ubuntu.com/Touch/Install mentions >> a saucy-preinstalled-touch-armel+grouper.zip as a second step in this >> process. In case of my own port, should it become something like >> cm-10.1-20131101-UNOFFICIAL-tilapia.zip which is generated by Android build? >> >> Also, it is unclear for me whether this step is really needed after >> fastbooting recovery, boot, system in the first step? >> >> >> 2013/11/6 Jani Monoses <[email protected]> >> >>> --------- >>> >>>> Either way, you'll need the Ubuntu preinstalled image besides the one >>>> you're going to build with the instructions below. You can find the Ubuntu >>>> preinstalled images >>>> here<http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/> >>>> . >>>> -------- >>>> Probably there should be some instructions where to put it (I mean for >>>> usual recovery procedure) >>>> >>>> >>> I agree the documentation leaves a lot to be desired. >>> I mostly inspected the installed software on a flashed nexus4 , but for >>> people porting to new hardware without seeing Ubuntu on one of the >>> supported devices the docs by themselves are indeed confusing. >>> >>> Jani >>> >> >> >
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
