ubuntu-phone team mailing list archive

[Lukasz Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>]

Hello!

Sadly I cannot help much about the building problems you've been
encountering as for mako we are using launchpad livefs to build the
relevant parts for us (using the android packages from the ubuntu
archives). Just wanted to mention one thing here: yakkety is not a
really a supported series for Ubuntu Touch. No one is doing any QA on
yakkety ubuntu-touch so there's a high chance that the current images
will not work or boot at all. The touch development cycle is a bit
different than for normal ubuntu and baseline switches happen much
less frequently. Currently all ubuntu-touch development is ongoing on
the slightly-outdated vivid series (through a special PPA called
stable-phone-overlay), with a near-future switch to xenial.
Just saying: there is chance that the yakkety-preinstalled-* pieces
you used for flashing are not booting because the current system is
broken and building them from scratch will not change the situation.

For any experimenting we, of course, recommend using our stable
channels. We have daily images built on system-image.ubuntu.com that
can be easily used on mako by flashing through the ubuntu-device-flash
tool. Please check out ubuntu-touch/stable/ubuntu for the stable
images.

That being said, if you want to try building all the bits yourself
from scratch, everything is possible to do and I'm sure someone with
more experience could help out. Although besides the learning and
fun-factor I don't see too much reason to do that as mako is still our
supported platform. We're doing even nightly-built images for it in
the rc-proposed channel.

Cheers!


On 9 August 2016 at 00:49, ujwal satish m <ujwalsatishm89@xxxxxxxxx> wrote:
> I think for building
> 1. boot.img
> 2. recovery.img
> 3. system.img (Android LXC container)
>
> one has to follow the Ubuntu touch building web page.
>
>
> On 8 August 2016 at 09:26, Joseph Liau <joseph@xxxxxxx> wrote:
>>
>>
>>
>> On 2016-08-08 12:12 AM, Richard Somlói wrote:
>> > Hey,
>> >
>> > Why do you want to port Ubuntu Touch to Nexus4? It is an official
>> > supported device with official images.
>> I am actually curious in trying to obtain the code and made changes for
>> contribution or testing my own image.
>>
>> Are there any official instructions out there for getting the code and
>> submitting changes?
>>
>> > 2016. augusztus 8., hétfő 4:53:34 CEST, ujwal satish m
>> > <ujwalsatishm89@xxxxxxxxx> írta:
>> >> Hello,
>> >>
>> >> I have been trying to compile and build Ubuntu Touch for Nexus4. I
>> >> followed
>> >> the steps mentioned in the porting guide. When I push the system.img
>> >> [Android] using rootstock installer, the screen goes blank. So far I
>> >> have
>> >> followed these instructions:
>> >>
>> >> 1.sudo add-apt-repository ppa:phablet-team/tools
>> >>
>> >> sudo apt-get update
>> >> sudo apt-get install phablet-tools
>> >>
>> >> 2. sudo apt-get install git gnupg flex bison gperf build-essential zip
>> >> bzr curl libc6-dev libncurses5-dev:i386 x11proto-core-dev
>> >> libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386
>> >> libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown
>> >> libxml2-utils xsltproc zlib1g-dev:i386 schedtool g++-4.8-multilib
>> >>
>> >> 3.mkdir phablet phablet-dev-bootstrap phablet
>> >>
>> >> 4.export cache
>> >> 5. lunch--> mako_userdebug
>> >> 6. make -j4
>> >> 7.flash all the relevant images(boot.img,recovery.img and system.img)
>> >>
>> >> I pulled the kernel msg:
>> >> it says: 6.114329] Adding 32764k swap on /root/userdata/SWAP.img.
>> >> Priority:-1 extents:1 across:32764k SS
>> >> [   11.074286] init: could not import file 'init.mako_svelte.rc' from
>> >> '/init.mako.rc'
>> >> [   11.377811] init: cannot open '/initlogo.rle'
>> >> [   13.918083] [rmnet0] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.918815] [rmnet1] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.919487] [rmnet2] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.920067] [rmnet3] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.920891] [rmnet4] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.921471] [rmnet5] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.922173] [rmnet6] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.922997] [rmnet7] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.923729] [rev_rmnet0] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.924523] [rev_rmnet1] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.925316] [rev_rmnet2] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.926293] [rev_rmnet3] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.927178] [rev_rmnet4] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.928063] [rev_rmnet5] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.928857] [rev_rmnet6] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.929620] [rev_rmnet7] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.930321] [rev_rmnet8] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >> [   13.931115] [rmnet_smux0] error: rmnet_ioct called for unsupported
>> >> cmd[35585]
>> >>
>> >> Can somebody please guide me where I'm going wrong. Because im stuck
>> >> in this from past 2 weeks.
>> >>
>> >> Regards
>> >>
>> >> Ujwal
>> >>
>> >
>>
>>
>> --
>> 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
>
>
>
> --
> 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
>



-- 
Łukasz 'sil2100' Zemczak
 Foundations Team
 lukasz.zemczak@xxxxxxxxxxxxx
 www.canonical.com