[Ubuntu-phone] Porting issues

Hi, I want to compile the kernel for my Oneplus One. I know that there is already a "working" kernel but I wanted to try it by myself. I'm using the official cyanogenmod sources with patches of the working kernel. My problem is that neither the screen is working or that I can use adb to connect

Re: [Ubuntu-phone] Porting issues

: Dmitry Smirnov >To: ubuntu-phone@lists.launchpad.net >Sent: Tuesday, November 5, 2013 8:36 AM >Subject: [Ubuntu-phone] Porting issues > > > >Hi, > > >I'm trying to port ubuntu-touch to some specific device but have issues with >this. > > >I've

[Ubuntu-phone] Porting issues

Hi, I'm trying to port ubuntu-touch to some specific 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

Re: [Ubuntu-phone] Porting issues

I Don't know... For supported device it is phablet-flash tools doing that for other??? 2013/11/18 Dmitry Smirnov > How this new-style system.img can be generated? > I'm already ported phablet changes for this new-style model, but do not > know how to create system.img > > > 2013/11/18 Franç

Re: [Ubuntu-phone] Porting issues

How this new-style system.img can be generated? I'm already ported phablet changes for this new-style model, but do not know how to create system.img 2013/11/18 François Leblanc > Yes It is that I understand... > > François. > > > 2013/11/18 Dmitry Smirnov > >> Sorry for previous message... >>

Re: [Ubuntu-phone] Porting issues

Yes It is that I understand... François. 2013/11/18 Dmitry Smirnov > Sorry for previous message... > Please correct my understanding of these models: > 1. Old-style > a. Uses original Android init > b. Ubuntu is in container, should be in /data/ubuntu > 2. New style > a. Uses Ubunt

Re: [Ubuntu-phone] Porting issues

Sorry for previous message... Please correct my understanding of these models: 1. Old-style a. Uses original Android init b. Ubuntu is in container, should be in /data/ubuntu 2. New style a. Uses Ubuntu initrd, should be in /data/system.img b. Android is in container (should be in v

Re: [Ubuntu-phone] Porting issues

Please correct my understanding of these models: 1. Old-style 2013/11/18 François Leblanc > Ah yes. > > The problem is that if the 2 ways are too differents you can make lot of > effort porting to old model and realize that isn't working in new model and > to have a real port you need to be ha

Re: [Ubuntu-phone] Porting issues

Ah yes. The problem is that if the 2 ways are too differents you can make lot of effort porting to old model and realize that isn't working in new model and to have a real port you need to be have same as official port.. surfaceflinger is a good example you can make working with it and realize th

Re: [Ubuntu-phone] Porting issues

(writing from my phone) I'm not sure if this is still true, but a few weeks ago porters were recommended to just use the old "cdimage-style" flipped model. It means to just have the extractes rootfs files in /data/ubuntu and the Android system.img copied in there, which happens automatically when

Re: [Ubuntu-phone] Porting issues

I agree this is not clear for me too. I notice some differences betwen using ubuntu dir and system.img in the structure of files and even if it is more simple to use dir ubuntu it is quite difficult to understand how system.img must be. According to touch script in build kernel they are some file

Re: [Ubuntu-phone] Porting issues

Sorry for bothering you again, but I did not understand what is meant to be new and old flipped models. 'touch' script is using /data/ubuntu as an old model (where /data is the 'userdata' partition). At the same time ubuntu_deploy.sh (included into cdimage.ubuntu.com zips) unpacks tar.gz into /data

Re: [Ubuntu-phone] Porting issues

Recovery from phablet-4.2.2_r1 seems won't work: the build does not provide the busybox-like tools (links) in recovery's system/sbin folder. Particulary, there is no 'mount' and autodeploy fails... 2013/11/6 Dmitry Smirnov > Thanks for the tip. I'll try to use it. > > > 2013/11/6 Jani Monoses

Re: [Ubuntu-phone] Porting issues

Thanks for the tip. I'll try to use it. 2013/11/6 Jani Monoses > Hi, > > while I have not tested it, I had a go at porting the recovery patches > ported to AOSP 4.2.2 in the phablet-4.2.2_r1 branch of the main > repositories and those may serve as a start for CodeAurora based trees. > > Jani >

Re: [Ubuntu-phone] Porting issues

Hi, while I have not tested it, I had a go at porting the recovery patches ported to AOSP 4.2.2 in the phablet-4.2.2_r1 branch of the main repositories and those may serve as a start for CodeAurora based trees. Jani On Wed, Nov 6, 2013 at 12:59 PM, Dmitry Smirnov wrote: > Ok, thanks for clar

Re: [Ubuntu-phone] Porting issues

Ok, thanks for clarifications! I see I need to finish porting phablet changes into recovery to make my life simpler :-) 2013/11/6 Jani Monoses > unflipped will not work anymore, all the super evil hacks it used are > >> gone from the rootfs since over 6 months, please only use (and >> recommen

Re: [Ubuntu-phone] Porting issues

hi, Am Mittwoch, den 06.11.2013, 12:49 +0200 schrieb Jani Monoses: > unflipped will not work anymore, all the super evil hacks it used are > gone from the rootfs since over 6 months, please only use (and > recommend) the flipped method. > > > > From the recent thread on t

Re: [Ubuntu-phone] Porting issues

unflipped will not work anymore, all the super evil hacks it used are > gone from the rootfs since over 6 months, please only use (and > recommend) the flipped method. > > >From the recent thread on this list saying the cdimage-legacy option of phablet-flash is to be kept around I figured that unf

Re: [Ubuntu-phone] Porting issues

hi, Am Mittwoch, den 06.11.2013, 12:36 +0200 schrieb Jani Monoses: > On Wed, Nov 6, 2013 at 12:26 PM, Dmitry Smirnov > wrote: > I'm sorry Jani, but I'm lost :-) > Please correct me if I'm wrong. > > > > Sorry, I forgot to say that what I was talking about is the newer (s

Re: [Ubuntu-phone] Porting issues

On Wed, Nov 6, 2013 at 12:26 PM, Dmitry Smirnov wrote: > I'm sorry Jani, but I'm lost :-) > Please correct me if I'm wrong. > Sorry, I forgot to say that what I was talking about is the newer (so called flipped-image) method of running Ubuntu, where Android's system.img is inside an LXC containe

Re: [Ubuntu-phone] Porting issues

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 fa

Re: [Ubuntu-phone] Porting issues

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 ide

Re: [Ubuntu-phone] Porting issues

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 gene

Re: [Ubuntu-phone] Porting issues

- > 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 > . > > Probably there should be some i

Re: [Ubuntu-phone] Porting issues

Thanks, Jani, I did not realize that I need to use this pre-installed image, maybe you could make it more clear on Porting guide page. Now I see only - 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

Re: [Ubuntu-phone] Porting issues

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

Re: [Ubuntu-phone] Porting issues

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

[Ubuntu-phone] Porting issues

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 p