ubuntu-phone team mailing list archive

[Jani Monoses <jani.monoses@xxxxxxxxxxxxx>]

Hi Dmitry,

(adding back the list so others can follow and add more information)

The system.img built from the AOSP-like source tree indeed now contains
some Ubuntu components but that is ok, those are needed as the glue between
Android and the Ubuntu system.
And the image that you need to boot is the trusty-preinstalled-touch-armhf
Ubuntu image from here

http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/

That boots as a regular Ubuntu desktop, but should have the android
system.img under /var/lib/lxc/android so it can start it inside an LXC
container.

So the  var/lib/lxc/android/system.img that is created should be the
regular system.img under out/target/product/tilapia in your tree and then
you need to copy it over the device in that location.

Jani


On Wed, Nov 6, 2013 at 10:15 AM, Dmitry Smirnov <divis1969@xxxxxxxxx> wrote:

> Hi Jani,
>
> ok, so the /data/system.img is the ububtu system image and it in turn
> should contain android's system image.
>
> The problem is that after I merged phablet, I do not have the 'pure'
> android system image - it already contains ubuntu and the android.
>
> Which components of the android image will be used by ubuntu? build.prop
> and fstab.<device>?
>
> BTW, as i said I use tilapia build for comparison, I did not realize when
> this var/lib/lxc/android/system.img is created (I looked in recovery
> scripts too). Is this some bug or should I use some other device (ex. mako)
> ?
>
> Dmitry
>
>
> 2013/11/6 Jani Monoses <jani.monoses@xxxxxxxxxxxxx>
>
>> Hi,
>>
>> that system.img should be the one built from your CodeAurora tree and
>> then turned into a regular ext4 image on your build machine
>>
>> $simg2img system.img new.img
>> $resize2fs -M new.img
>>
>> In recovery mode
>> #mkdir a
>> #mount /data/system.img a
>>
>> On the host
>> $adb push new.img /a/var/lib/lxc/android/system.img
>> $adb reboot
>>
>> Jani
>>
>>
>>
>>
>> On Wed, Nov 6, 2013 at 9:40 AM, Dmitry Smirnov <divis1969@xxxxxxxxx>wrote:
>>
>>> Hi,
>>>
>>> I'm trying to port ubuntu-touch to a device but have issues with this.
>>>
>>> I've ported all the changes from phablet-saucy branch to my code base
>>> (non-CM, pure codeaurora).
>>> I decided to skip recovery procedures because I can build all the images
>>> (kernel, system, userdata, etc) and try to run the phone using just
>>> fastboot to flash the phone.
>>>
>>> The phone starts, initrd can run, but it fails to complete boot
>>> sequence: there is no /root/var/lib/lxc/android/system.img for ex. and I
>>> did not find who and when can generate it.
>>> I'm using pure phablet build for tilapia for comparison of the builds
>>> and also cannot find that /root/var/lib/lxc/android/system.img (even in
>>> recovery image)
>>> This causes device to be unrecognized ("unknown) and probably causes
>>> some other steps to fail.
>>>
>>> Also, /root is read-only for some reason and I also suspect this
>>> prevents the system to boot:
>>> + mkdir -p /root/android
>>> mkdir: can't create directory '/root/android': Read-only file system
>>>
>>> What I'm doing wrong?
>>>
>>> WBR,
>>> Dmitry
>>>
>>> --
>>> Mailing list: https://launchpad.net/~ubuntu-phone
>>> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>