yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] eagleofdeath13:
No zip possible right now, maybe one day, but not in a close time, the priority is a working rom ^^
[Moto G Android Development] Brawn_Sg:
Yes eagerly waiting for that
[Moto G Android Development] sub77:
if someone could patch the selinux stuff...
[Moto G Android Development] Brawn_Sg:
So will he be able to fix those selinux issues in his upcoming build ?
[Moto G Android Development] eagleofdeath13:
Can't you wait for an answer from him?

If he's building right now, he could have already seen it, or it doesn't happen for him and build will work.
[Moto G Android Development] h2o64:
Please this is my work, I spent hours making those repository, fixing those patches...

I said I'm building. I got many error which I'm fixing.

I push my work to github to share my process and to be improved by someone else.

Not to let it be stolen or to be overtaken
[Moto G Android Development] sub77:
Allready stopped man. Do not cry
[Moto G Android Development] reversegear:
[MENTION=4792450]h2o64[/MENTION] some times u behave like child..

I still remember few months back one dev ported miui for moto g and u created thread with ur name without even consulting the dev

Now what happened...?
[Moto G Android Development] h2o64:
I consulted the dev before he released MIUI.

Mods fix the issue.

I'm a child. But I do way more than a child can do.

When it comes to touching at hours of my work, I'm frustrating because people had stolen my work in the past and I don't want it to him happend again

PS : With MIUI I created the first thread, called him for help. He solved the problem, and created a new thread.
[Moto G Android Development] Quasar:
Geez. Calm down. You guys can put that in a nicer way. He's worked his butt off today. It's harder than you guys think. Agreed. He's a little overprotective about his work, but with the amount if effort and dedication he puts into all his projects, he should be cut some slack,but yes. I agree he should be a little less cranky. :p
[Moto G Android Development] h2o64:
So

So .... I have finished my weekly available time

I did A HUGE AMOUNT OF WORK, I basically rebased the ROM on CAF (and added full F2FS support wich is very important)

I'm now facing hardware/qcom/media issues

LOG : http://pastebin.com/MrUYZWxN

All sources now available here : Ubuntu Touch for CAF Devices

Thanks for your support
[Moto G Android Development] sub77:
did you use caf or caf new

---------- Post added at 12:58 AM ---------- Previous post was at 12:56 AM ----------

and be afaid. iam busy with porting lp for galaxy tab 4.
[Moto G Android Development] h2o64:
First I used the CAF 4.4.2 one. I got errors so I tried caf new and I get the same errors.

Everything is on github
[Moto G Android Development] eagleofdeath13:
If you have something to make me flash, i'm ready, and i receive my 2014 moto x, so the g will become a tests device :)
[Moto G Android Development] iBART:
I would like to use ubuntu but i cannot because of the lacking of applications for sports tracking. :\
[Moto G Android Development] the_MUKe:
Build errors

I hope h2o64 is still working on this ROM. Recently I tried again to build the sources from the ubuntu-touchCAF repository.

I got a few errors with libqdMetaData_intermediates. These files are needed by several other modules. libqdutils is in hardware/qcom/display. But for some reason make does not resolve the dependencies correctly.

I could solve this problem by removing the comments in hardware/qcom/media/Android.mk to include most of the display makefiles, as similarly described here.

[MENTION=4792450]h2o64[/MENTION]: Could you update this in the GitHub repo?

I found something on the error with omx_vdec in hardware/qcom/media.

The problem with c2d.convert() is a wrong number of arguments.

omx_c2d_conv is declared in:

hardware/qcom/media/mm-video-v4l2/vidc/common/inc/vidc_color_converter.h

and implemented in:

hardware/qcom/media/mm-video-v4l2/vidc/common/src/vidc_color_converter.cpp

The change was introduced with this commit.

So I changed back only the convert() function (just copied the deleted lines from the commit log).

Now the build process finishes without any errors. Kernel, ramdisk.img and system folder are in the out directory but neither boot.img nor system.img are built. [MENTION=4792450]h2o64[/MENTION]: Do you plan to add a script/makefile to generate boot.img and system.img or should we create them manually?

I just noticed something in the CAF source. The omx_vdec.cpp was removed in this commit ("mm-video: Remove old video component"). So maybe it is better to just remove omx_vdec.cpp (and get rid of the compile error) but keep the new versions of vidc_color_converter.h and vidc_color_converter.cpp (with 6 arguments in the convert() function). Then also power_module.cpp (in mm-video-v4l2/vidc/vdec/src) should be removed (just like in the commit).

Not sure which would be the better solution in the end.
[Moto G Android Development] h2o64:
I do work on it.

I actually forget to push my un-commenting on Android.mk

Glad you fixed media issues because they made me mad.

So system.img and boot.img didn't built? I'll fix that on build.
[Moto G Android Development] Mchasard:
I dont know if this project will one day working but I follow this thread with interest thanks for you work
[Moto G Android Development] dhruv7855:
+1
[Moto G Android Development] h2o64:
If a achieve to do what I wanna do. Mostly all devices supported by CM will get Ubuntu Touch
[Moto G Android Development] eagleofdeath13:
Even m'y moto x 2014? :D
[Moto G Android Development] h2o64:
The rom will need changes. But : yes
[Moto G Android Development] keenofhiphop:
Hello,

there are several topics I wanted to address you with:

1. Would it be difficult to port this to Moto G 4G or build it for this device, as both differ only in terms of storage and modem?

2. Are you as well interested in other open source operating systems, let's say Sailfish OS or LuneOS?

I hope I don't waste your time!

Regards,

Kai
[Moto G Android Development] h2o64:
It could be easy yes.

But as far as I don't own it, I won't do it.

I was interessted in those ROMs. But my lack of time made me realised that they are only a dream for now.
[Moto G Android Development] h2o64:
New build is uploading
[Moto G Android Development] dhruv7855:
Ready
[Moto G Android Development] h2o64:
Be excited. This one have an impressive changelog
[Moto G Android Development] haky 86:
so it's works?
[Moto G Android Development] h2o64:
As always, I didn't test. Some of you wants the early build to experiment with it and make logs. So I upload as soon as I can.

I saw you're working on my work. What do you do exactly?
[Moto G Android Development] haky 86:
Good question, I am trying to mount data partition where all utouch files are saved, as small example, after build one for my s2 plus a few weeks ago which i got shell access as well but Unity doesn't start up, backing to the reason data partition doesn't mount as well, so when i flash it from recovery twrp give me a lot of errors about unmounted data/ubuntu partition, probabily is the issue of stuck.
[Moto G Android Development] h2o64:
On falcon it was because of lack of f2fs support wich I added
[Moto G Android Development] haky 86:
I don't think utouch is require F2FS to boot, when i remove it from my plus i got recovery worked.
[Moto G Android Development] h2o64:
It does because Moto G userdata is f2fs

Check your device fstab
[Moto G Android Development] h2o64:
New build !

Hellow !

It has been a long time since a build shown up. This new one is part of a full and huge rebase of the entire ROM. Here is the changelog

CHANGELOG :
- Reworked[B] device tree[/B] (new includes, udev,....)
- New [B]kernel[/B] (New source, new defconfig, ...)
- New [B]manifest / Sources[/B]
- Rebased on [B]CAF LNX.LA.3.5.2.1.5 and CM11[/B] with strategic reverts
- Few [B]patches[/B] here and there
- Add [B]f2fs support[/B] (Fix recovery)

The sources is now here : CAF Ubuntu Touch

You can build by yourself thanks to this tutorial

Please test and provide logs ;)
[Moto G Android Development] eagleofdeath13:
Will try it tomorow ^^
[Moto G Android Development] eagleofdeath13:
Touchpad? It's for moto G ^^
[Moto G Android Development] h2o64:
Yeah but if this rebase make a booting build. Every cm devices will get one
[Moto G Android Development] keenofhiphop:
Pardon.

Sorry but could you point out? Every device like every device running cm or every device that you own that has a cm build or just those devices running cm with a developer?

Regards
[Moto G Android Development] h2o64:
If the future builds boots that means that with a little amount of patches, we can convert CM devices trees to build a functionnal Ubuntu Touch.

Wich anybody can do.
[Moto G Android Development] S0bes:
the key word in your sentence is if
[Moto G Android Development] h2o64:
The key attitude of this thread is to test
[Moto G Android Development] the_MUKe:
touch script: device is unknown

The latest sources compile without any problems. However, the boot process stops at a certain point.

I saw in last_kmsg that the touch script outputs "device is unknown". This means that ro.product.device is not set. But this variable must be set for further mounting operations.

I think it should be set in build.prop, which is generated with build/tools/buildinfo.sh.

So I just added the corresponding line (see below). But this gave compile errors for some reason. Any idea of how to set the property correctly?

...
echo "# ro.build.product is obsolete; use ro.product.device"
echo "ro.build.product=$TARGET_DEVICE"
[B]echo "ro.product.device=$TARGET_DEVICE"[/B]
...
[Moto G Android Development] h2o64:
Finally somebody test! I love you! I spent hours on this projects. I have no more time to test it. But thanks God! You are here!

This is a typical aosp issue... But the problem is kind of serious...

This is normally define by the init binary (you can find its sources in the device tree.

But apparently it's not set correctly.

I'll write a script wich executed with the ramdisk and set the rights props.

Why not directly push it into the system.prop? Because there is various Moto G variant. And each one need a different device flag AND many other bits in props.

I'll update sources as soon as I can and pm when it's ready
[Moto G Android Development] eagleofdeath13:
I didn't had m'y linux computer with me, but next week it'll be good ^^
[Moto G Android Development] h2o64:
Here is my commit : https://github.com/ubuntu-touchCAF/...mmit/46985d257c936827c5ea0390bae8c1df0553a226

Now you can build :D
[Moto G Android Development] h2o64:
As soon as we talk about it

https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[Moto G Android Development] itouchables:
They make it seem so easy :D..... I wonder if I can get someone on their IRC to take a look at your builds
[Moto G Android Development] haky 86:
look like should flash from recovery, some time i am stupid.:o:o
[Moto G Android Development] eagleofdeath13:
I hope it will help you!!

(and now i'll be available for testing :D)
[Moto G Android Development] h2o64:
What do you mean ?

The tutorial is pretty much the same. (exactly the same according to me)

The biggest thing it learnt me : https://github.com/ubuntu-touchCAF/...mmit/aab3c6c88a89fbed3bafdbaffb6af97721a5a987
[Moto G Android Development] eagleofdeath13:
Ok, we're getting closer so :D
[Moto G Android Development] h2o64:
I need to get some time to test it
[Moto G Android Development] eagleofdeath13:
I know ;)
[Moto G Android Development] h2o64:
Tests and Results

So !

I finally tested the last build (the one wich is actually online + some apparmor 3 patches on kernel)

And it didn't worked !

I think we will have to hack the initrd script because he definitly causes problems.

With f2fs userdata : http://pastebin.com/zgGhETJc

With ext4 userdata : http://pastebin.com/8ihh4z4M

I'll work on it. In background, as always.
[Moto G Android Development] haky 86:
I think it's a display drivers issue, reading the new porting guide, they said surfaceflinger should switch to MIR one (i guess surfaceflinger of android is not compatible with ubuntu touch), so try with this steps

https://wiki.ubuntu.com/Touch/Testing/Mir#Easiest_way

to know:

-I since i port it to s2 plus, i found 8 failed services, 2 of them are fixed, the rest of 6 issues are coming from display drivers that crash after start up.

-so check display drivers issue from permissions and kmsg's log.

:o:o
[Moto G Android Development] h2o64:
I don't even have shell access. The surfaceflinger service come later in the scripts.
[Moto G Android Development] :
Thought, I might share some info as I was hoping you would have it solved. Been working on this for another device the past few days and fortunately have an older working port of ubuntu touch example for the device to go by.

Using the latest ubuntu touch vivid builds, my recent tests today show the old flipped model gets further into the boot process. Still no adb but there's now log info in data/ubuntu/var/log that can be used.

The boot.img (including kernel) and android-ramdisk appear to be fine [for me] as they also allow the old flipped model to get further.

That tells me that the data/system.img path is a bit broken as it fails to also boot in what seems to be similar (if not exactly) to your port. This was also confirmed by mixing in a cm11 build initramfs to the boot.img created by ubuntu touch (leaving the ubuntu created kernel). This resulted in adb showing the device upon boot (though adb shell not working) same as the whole fully working cm11 boot.img.

So the boot process reaches up to /init but fails either there or just slightly after when using data/system.img path that is being created and used via rootstock-ng. Since the /init file has not changed and it has write permission, I can only assume the problem is elsewhere or perhaps something is missing.

Hope that helps.
[Moto G Android Development] h2o64:
Thank you very much!
[Moto G Android Development] Toledo_JAB:
So I was pinged to this thread to help with the discussion.

According to the XDA rules...

As I see it this thread is moving to a designed goal of a working ROM so it is not a place holder thread with nothing for download.

However I did no find any link to the sources used to compile the kernel.

The source link is required by GPL to provide the buildable source used in your work.

I did find a link to your git hub but that is not specific enough to qualify for GPL compliance.

I also see that the OP has a big red warning telling users to beware of the dangers of trying this ROM, Thanks for this warning.

If someone has issues with a post or thread then use the report button or take it to PMs

We do not allow members, developers and especially Recognized members to take a thread off topic just to have their say.

Some of you know better and should have just hit the report button and stayed quite.

Number 1 unwritten rule on XDA....DO NOT FEED THE TROLLS.

[MENTION=5975318]Tqr[/MENTION]

You are not supposed to just go posting random off-topic junk about what you think is right.

You report things and the moderators decide what is right. You don't like our decisions then you talk to the admins about it.

The way to get a moderators attention is to use the report button and be quite.

That is how we keep finding you not being compliant with GPL, other users report you.

Now, if anyone has any questions or further comments then PM me, DO NOT POST OR QUOTE ME.

If anyone sees a post that needs the attention of a moderator then report it.

Thread cleaned
[Moto G Android Development] :
I've finally got latest ubuntu touch working on my porting device. Additional time saving tips for you =)

Easiest way was definitely going with the old flipped model.

Also, you have to have lxc fully configured in the kernel config or it stays stuck at ubuntu boot animation. The lastest porting guide is a bit lame which shouldn't surprise me. See here under LXC on Android devices -> https://www.stgraber.org/2013/12/23/lxc-1-0-some-more-advanced-container-usage/

Basically just install the lxc checking tool and run it against the config file for example -> $ CONFIG=cyanogenmod_ovation_green_defconfig /usr/bin/lxc-checkconfig

Then enable anything that's missing by changing to =y in the config and rebuild.

(Don't know if this will help out the problem with the system.img flipped model yet, but thinking not).

None of that is necessary from what I can tell you thus far and does nothing with getting a complete boot into ubuntu touch.
[Moto G Android Development] haky 86:
So probably i can get same LXC problem on my device too? :good::good:
[Moto G Android Development] :
Ubuntu touch uses lxc on all android devices, so yes :)

https://wiki.ubuntu.com/Touch/ContainerArchitecture
[Moto G Android Development] h2o64:
https://github.com/ubuntu-touchCAF/...mmit/0e8d3980fef2e2ad703e7128ab49646543ea9d72 ;)

Thank you :D (4 or 5 things were disabled)
[Moto G Android Development] h2o64:
I made what you adviced :)

I get that : http://pastebin.com/fU1EpgpU

The problem is abviously :

[ 4.620025,1] [ 5.030611,1] init: ureadahead-touch main process (368) terminated with status 5

I have to enable the DEBUG stuff on the touch script to understand it more.

This is weird too :

[ 0.001791,0] AppArmor: AppArmor disabled by boot time parameter
[Moto G Android Development] haky 86:
enable by CONFIG_SECURITY_APPARMOR=y and apparmor=0 on cmd line in boardconfig.mk
[Moto G Android Development] h2o64:
Already made
[Moto G Android Development] Innocent Devil:
AppArmour or SELinux ?? which one we enable ?

CONFIG_DEFAULT_SECURITY="selinux"
[Moto G Android Development] h2o64:
Apparmor.

The problem is on /var.

But I actually can't modify the touch script :'( ....

I don't know why, but the new boot.img (after modifying) is crashing the boot process.

I added a new repository.

I'll investigate on this touch script mofying as soon as I can (1 hour)

UPDATE : I made a build flag to allow device tree to modify the Touch ramdisk

UPDATE 2 : I tweaked the rootstock script to install udev rules in LXC container

UPDATE 3 :

Here is my kmsg error :

init: ureadahead-touch main process (537) terminated with status 5

I tried the [MENTION=4709667]Wootever[/MENTION] adbd fix fix didn't worked (here)

All my changes are pushed to the main github

Ubuntu Forums Link for this issue

[MENTION=4883214]haky 86[/MENTION]6 [MENTION=6035073]the_MUKe[/MENTION] Now that I made this flag. Feel free to customize the ramdisk from the device tree

UPDATE 4 :

I made that by the way : https://github.com/ubuntu-touchCAF/project_rootstock

UPDATE 5 :

I made the OP fancier
[Moto G Android Development] haky 86:
OK bro i will try apply changes like that on my phone, but after resync utouch source on my new machine because i got wifi issue on old one :/
[Moto G Android Development] h2o64:
Wich repo do you use ? Ubuntu ones ? They are straight AOSP. You will have a lot of difficulties to make that work :/
[Moto G Android Development] haky 86:
I was use the new source first that give me a lot of errors then I switch to phablet-4.4.2 which give me better result without errors roostock flashing is worked only with TWRP with Ubuntu recovery said device not found after transfer tar.

EDITED: [MENTION=4792450]h2o64[/MENTION] I found this guide too is important by enable cmd lines in defconfig too

CONFIG_CMDLINE_EXTEND=y

CONFIG_VT_CONSOLE=y

this guide may help you ;)

https://wiki.ubuntu.com/Touch/ContainerArchitecture
[Moto G Android Development] h2o64:
I need to know more about this old flipped model.

Do they have a WiKi about it ?

EDIT : I NEED a logcat access while booting.
[Moto G Android Development] haky 86:
I think yes, i found this script for sony z1 which utouch vivid has been ported on it, i guess you can make one for your falcon since have fastboot feature, i made an image for my i9105p and try to get a screenshot, the surfaceflinger is detected but boot is so far :)

EDITED: reboot into recovery and try with adb pull /proc/kmsg

https://gist.github.com/diclophis/cc8775c7617b060ef8e3
[Moto G Android Development] h2o64:
But I'm very interessting at getting a live logcat
[Moto G Android Development] haky 86:
I have a suggestion for you, open boardconfig.mk of your falcon and insert the following stuff

skipabi := true

TARGET_KERNEL_UBUNTU := true

TARGET_KERNEL_UBUNTU_META := linux-generic

TARGET_KERNEL_UBUNTU_SERIES := vivid

after saving file and recompile it will stuck when download ubuntu-touch generic image, so check the out/target/product/falcon/ubuntu/kernel/ and you will have 2 packages armhf.deb that cannot be copied and also you will got vmlinuz-generic too, so my idea is to investigate about this and "probably" will get the boot.
[Moto G Android Development] gameeater:
I can install on my xt1033?

Works dual sim?
[Moto G Android Development] Quasar:
Make it a habit to read the OP and the last few posts on a thread before asking such question please.
[Moto G Android Development] SH1M4BD3:
[MENTION=5937183]haky[/MENTION] glad to found you here man
[Moto G Android Development] haky 86:
This is not my profile, that you quoted xD the mine is "haky 86" not only haky :)
[Moto G Android Development] SH1M4BD3:
Any news of friendly flashing please new build
[Moto G Android Development] h2o64:
I'm updating to support Lollipop Bootloader
[Moto G Android Development] SH1M4BD3:
Yeaa i wait for that...good keep it up
[Moto G Android Development] Shaneee:
Will it also support MultiROM? Just got it installed and want to try Ubuntu Touch out.

Thanks
[Moto G Android Development] S0bes:
The real question is would it ever support moto g
[Moto G Android Development] h2o64:
It won't because of f2fs

If you aren't here to contribute. Please do not speak ☺
[Moto G Android Development] SH1M4BD3:
Hope can work on our devices..soon
[Moto G Android Development] h2o64:
Help

Hello guys.

I updated the kernel to be runable on LP Bootloader. Unfortunaely, I can't get the kernel to compile correctly because of an error

CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/version.o
CC init/do_mounts.o
In file included from include/net/sock.h:67:0,
from include/linux/tcp.h:212,
from include/linux/ipv6.h:225,
from include/net/ipv6.h:16,
from include/linux/sunrpc/clnt.h:26,
from include/linux/nfs_fs.h:57,
from init/do_mounts.c:20:
include/net/dst.h: In function 'dst_hold':
include/net/dst.h:245:2: error: size of unnamed array is negative
BUILD_BUG_ON(offsetof(struct dst_entry, __refcnt) & 63);
^
scripts/Makefile.build:307: recipe for target 'init/do_mounts.o' failed
make[1]: *** [init/do_mounts.o] Error 1
Makefile:955: recipe for target 'init' failed
make: *** [init] Error 2

Could you help me ?

Sources : https://github.com/ubuntu-touchCAF/android_kernel_motorola_msm8226
[Moto G Android Development] ghost9685:
i did according to the OP.. however when i paste this last command for instllation

$ ./project-rootstock-ng/rootstock-touch-install vivid-preinstalled-touch-armhf.tar.gz system.img

i am getting an error command not found, can any one tell me what is the problem... sorry i am new to Linux.
[Moto G Android Development] h2o64:
Please detail the error you are facing
[Moto G Android Development] ghost9685:
thats the error...

when i hit the final command on the terminal in Ubuntu 14.04 .. i am getting the error " COMMAND NOT FOUND".
[Moto G Android Development] h2o64:
Check were project-rootstock-touch is and if it is executable
[Moto G Android Development] SH1M4BD3:
Is someone have tried this on lp bootloader??what actually works/not??
[Moto G Android Development] haky 86:
seems you have some errors on "include/net/dst.h:245:2: error: size of unnamed array is negative" that i can't help with coding, do you have add extra configs in defconfig that not compatible?
[Moto G Android Development] h2o64:
Thank you I knew that was the error ^^

My config is highly change. The issue is about 64 bits
[Moto G Android Development] h2o64:
It's already uploaded (but reflash the other too)
[Moto G Android Development] h2o64:
Nope