yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] h2o64:
Update ...

Hi

https://github.com/h2o64/android_local_h2o64/tree/ubuntu-touch

[MENTION=5285494]akshay.ku[/MENTION]
[MENTION=3332479]eagleofdeath13[/MENTION]
[Moto G Android Development] akshay.ku:
thanks bro

will try and let know :)

i was waitting for this day since years

and now i got this
[Moto G Android Development] h2o64:
UPDATE :

- sync tutorial fixed

- link updated for Ubuntu 15.04 "Vivid"
[Moto G Android Development] dhruv7855:
Pls give commands for windows pc to flash....
[Moto G Android Development] akshay.ku:
objective taking long time

It's been more than 2 hrs

still its fetching and reciving objects.

any maz time or limit for it to complete

any file size its got

if yes then what's the size

:(

Thanks and Regards

-AK
[Moto G Android Development] eagleofdeath13:
Will try it when i get home!
[Moto G Android Development] mendozza2000:
bootloop :/
[Moto G Android Development] h2o64:
Guys... The build hasn't change... I just rebased everything
[Moto G Android Development] mendozza2000:
Sorry :)
[Moto G Android Development] h2o64:
:) no problems

I re-enable the thread in order to invite you guys to sync my work and help me building that :D
[Moto G Android Development] h2o64:
Not possible at all

Maybe we will make a nandroid dump later on.
[Moto G Android Development] eagleofdeath13:
Back home now, repo syncing, i'll send logs as soon as i can, if i remember how XD
[Moto G Android Development] eagleofdeath13:
Well, i don't achieve to build with the instructions (i've never built anything, so i don't know where i'm failing). envsetup does something, but, after that, make don't work (an error). If you can help me build it (or provide images to flash) it would be very nice :D
[Moto G Android Development] h2o64:
I'll provide new images maybe tomorrow
[Moto G Android Development] Ekril:
okay guys give some screenshots:)

i am using Linux Mint on my laptop for years and before that i used ubuntu variants.

i really want to use this. :)

but i need somethings to use it as a daily driver.

1- Phone Calls

2- Messaging (sms/mms/google talk)

3- Camera

4- ebook reader

5- telegram

can i have them?

if i can

i will just go Ubuntu :)
[Moto G Android Development] reversegear:
We are too far from the reality ;)
[Moto G Android Development] h2o64:
This isn't a request place!

Things aren't easy
[Moto G Android Development] eagleofdeath13:
If you help us by flashing and providing logs, maybe one day you'll be able to use it as a daily driver ;)

Can't wait to have those images to make the thing go further :D
[Moto G Android Development] h2o64:
I need to redo my old work on hardware qcom... So boring...
[Moto G Android Development] eagleofdeath13:
If only i could help :s

Do you want me to up my jenkins server to automate the build? (i would need your help or really precise build instructions but it would be more simple for you (no need to upload by yourself, and to build on your machine)
[Moto G Android Development] h2o64:
Later later..

I made a big progress yesterday on my own rom... It's mostly done. I'm focused on it
[Moto G Android Development] Ekril:
those weren't requests :)

i haven't seen what is working or not working :) so i asked "if" they work.

i was too excited :) i know enough to not ask about ETA or Features :)
[Moto G Android Development] blueskyder:
Is the ROM booting?
[Moto G Android Development] Ekril:
i did every step from the OP. didn't boot.

i only got Google logo with and unlocked lock image.
[Moto G Android Development] h2o64:
I'm working on it.

I'll ping you when I got a new build
[Moto G Android Development] Ekril:
ping me too (well as i subscribed to the topic i will be pinged but whatever please also ping me too )
[Moto G Android Development] Brawn_Sg:
Dude any multirom or Ubuntu progress ?
[Moto G Android Development] h2o64:
Nope.

Nothing valuable enough to be shared
[Moto G Android Development] h2o64:
News

I made progress ^^

Take a look at my github :p
[Moto G Android Development] Awesomeslayerg:
So your not gonna build it so we can test it?

Take a look at this manifest:

https://github.com/keyser84/android_local_manifest_falcon
[Moto G Android Development] h2o64:
I'm building it ^^

Your manifest use way to much Cyanogenmod.

It's more AOSP than CM
[Moto G Android Development] h2o64:
New build !

New build made and un-tested !

I upload it !

CHANGELOG :

- everything has been remade from scratch

Status : UPLOADING

All sources on my github.

Here is my manifest

PING :
[MENTION=5285494]akshay.ku[/MENTION]
[MENTION=3332479]eagleofdeath13[/MENTION]
[MENTION=4594676]mendozza2000[/MENTION]
[MENTION=874009]Ekril[/MENTION]
[MENTION=5696354]blueskyder[/MENTION]
[Moto G Android Development] TeamMex:
And now working? xD
[Moto G Android Development] Brawn_Sg:
Is it booting? And where is d link
[Moto G Android Development] h2o64:
I didn't try yet but working or not I need logs and your help ?
[Moto G Android Development] h2o64:
[MENTION=5938667]Brawn_Sg[/MENTION]
[MENTION=6035073]the_MUKe[/MENTION]
[Moto G Android Development] eagleofdeath13:
Will try it asap (later on the afternoon)

And will provide logs too, of course ;)
[Moto G Android Development] Brawn_Sg:
Can I flash it onto my falcon through windows
[Moto G Android Development] eagleofdeath13:
If you knew how to read you'd know ...
[Moto G Android Development] Brawn_Sg:
Any progress someone got it booting
[Moto G Android Development] h2o64:
Progress yes. Boot I don't know
[Moto G Android Development] Awesomeslayerg:
Before doing any of this make sure you wipe your phone using a custom recovery hopefully!

Get into fastboot mode first as well! h2o64 hows how to do it in the op.

For windows users to flash:

1. Get minimal sdk here then select which type of windows 32 bit or 64 bit OR if you already have adb sdk stuff just start cmd as adminstrator and then cd into your sdk directiory.

1b. Download the ubuntu touch files.

1c. Move the ubuntu touch files to somewhere you can find it easily

2. Install minimal sdk and follow the instructions

3. Once its installed, right click on the shortcut or in the start menu and click propeties --> open target

4. Move the ubuntu touch files to the folder that was opened or to the root of your sdk folder with adb.exe and fastboot.exe/mfastboot.exe in it.

5. If you still have your sdk terminal open just use these commands:

fastboot flash boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

6. Restart the phone and see if it boots

---------- Post added at 06:48 PM ---------- Previous post was at 06:36 PM ----------

Dosent boot.

EDIT: ATTACHED FILES
[Moto G Android Development] h2o64:
Noooope !

That's not the way you flash it.

I said it and I repeat again.

IT'S FLASHABLE ONLY ON LINUX/UBUNTU
[Moto G Android Development] eagleofdeath13:
I'm flashing it, i will send logs asap! :D
[Moto G Android Development] Awesomeslayerg:
How would you know if its flashable via windows ? You stated it was easily flashably via windows. Everything is flashable its just you need to build it via linux, You dont own a windows computer so how would you know? Sorry if i sound like a **** but its true,

[MENTION=4792450]h2o64[/MENTION]
[Moto G Android Development] h2o64:
You need a special tool provided by canonical wich add the needed arm Ubuntu packages to the system. It's written on the main post...

I always said it's not bootable in Windows. And if I said that. I correct myself
[Moto G Android Development] eagleofdeath13:
LOGS!!!

Here are my logs ! (i don't know if they're the ones from OS boot or from recovery, but i hope they'll be usefull :D

https://mega.co.nz/#F!x1gWXK5T!HV3VpMD9nftRwAzn0-z3Eg
[Moto G Android Development] h2o64:
I'm interessted in last_kmsg

Try

adb logcat

too

UPDATE : That's recovery logs xD
[Moto G Android Development] eagleofdeath13:
Well the system is maybe not booting (stuck at the white "unlocked bootloader" screen) But i'll retry (maybe i've not wait enoug)
[Moto G Android Development] eagleofdeath13:
If someone knew how to port rootstock install, yes, we could port to Windows, but since then, we cant ....

[MENTION=4792450]h2o64[/MENTION] : seems to be stuck on white "bootloader unlocked" screen

And last_kmsg isn't available, seems like recovery isn't fully working like the old one :s will try to flash the old one, to see if it can work.
[Moto G Android Development] h2o64:
I'm not the rootstock maintener ^^

Do you have adb on this screen?
[Moto G Android Development] eagleofdeath13:
I know that you aren't, but i explain to the others why we can't flash on Windows ^^

And no, no interaction at all possible, but i'm trying to flash again, from the Ubuntu recovery from 27/08/14 to see if it changes anything
[Moto G Android Development] h2o64:
Use TWRP or CWM if issues

I updated the OP a few minutes ago
[Moto G Android Development] eagleofdeath13:
Yes, but in the past, only the Ubuntu Recovery allowed us to read kmsg and dmesg from the previously running rom, Others like TWRP or CWM were overwriting it.

---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------

logs updated, still not sure if they're from recovery or os booting ^^

last_kmsg doesn't seems to exist, and adb logcat say :

/sbin/sh: exec: line 1: logcat: not found
[Moto G Android Development] El Daddy:
The mistake in the OP has been addressed and fixed. Stop arguing about it.

Thread cleaned.
[Moto G Android Development] h2o64:
Hmm hmm... I'll read those files
[Moto G Android Development] eagleofdeath13:
Well, for logcat, the mistake is mine, logcat don't work this way on ubuntu touch (source : https://bugs.launchpad.net/touch-preview-images/+bug/1200422 )

I've flashed Android back to my phone for tonight, but if you want i can flash ubuntu back tomorrow to see for logcat (or with another build if logs are usefull enough ^^)
[Moto G Android Development] h2o64:
I may upload a new build tomorrow :)

Will see
[Moto G Android Development] eagleofdeath13:
I'll wait until then so ^^
[Moto G Android Development] h2o64:
New build today.

I rebased a few things. And redo the system/core

UPDATE :

Ok guys ... I did a lot of things and I'm out of time :

- I've redone systemcore to match CAF
- I've redone hardware/qcom ([B]maybe I'll optimize the organization even more in the future)[/B]
- I've rebased frameworks/av
- A few bits & bobs on the trees/kernel/...

Here are my issues/questions :

- I disable libaudioparameter in the frameworks/av .... Maybe that's an error. UT Stock doesn't so BUT audio HAL may need it.

- I have this error I can't achieve to fix.

hardware/qcom/audio-caf/hal/audio_hw.c: In function 'enable_audio_route':
hardware/qcom/audio-caf/hal/audio_hw.c:332:5: warning: implicit declaration of function 'audio_route_apply_and_update_path' [-Wimplicit-function-declaration]
hardware/qcom/audio-caf/hal/audio_hw.c: In function 'disable_audio_route':
hardware/qcom/audio-caf/hal/audio_hw.c:354:5: warning: implicit declaration of function 'audio_route_reset_and_update_path' [-Wimplicit-function-declaration]
hardware/qcom/audio-caf/hal/audio_hw.c: In function 'adev_open_output_stream':
hardware/qcom/audio-caf/hal/audio_hw.c:2584:46: error: 'audio_offload_info_t' has no member named 'bit_width'
hardware/qcom/audio-caf/hal/audio_hw.c:2593:33: error: 'audio_offload_info_t' has no member named 'bit_width'
build/core/binary.mk:512: recipe for target '/home/louis/Dev/Ubuntu_Touch/out/target/product/falcon/obj/SHARED_LIBRARIES/audio.primary.msm8226_intermediates/audio_hw.o' failed

and this one

hardware/qcom/audio-caf/hal/msm8974/platform.c: In function 'set_echo_reference':
hardware/qcom/audio-caf/hal/msm8974/platform.c:488:9: warning: implicit declaration of function 'audio_route_apply_and_update_path' [-Wimplicit-function-declaration]
hardware/qcom/audio-caf/hal/msm8974/platform.c:490:9: warning: implicit declaration of function 'audio_route_reset_and_update_path' [-Wimplicit-function-declaration]
hardware/qcom/audio-caf/hal/msm8974/platform.c: In function 'find_index':
hardware/qcom/audio-caf/hal/msm8974/platform.c:975:30: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
hardware/qcom/audio-caf/hal/msm8974/platform.c: In function 'platform_get_compress_offload_buffer_size':
hardware/qcom/audio-caf/hal/msm8974/platform.c:2082:25: error: 'AUDIO_FORMAT_FLAC' undeclared (first use in this function)
hardware/qcom/audio-caf/hal/msm8974/platform.c:2082:25: note: each undeclared identifier is reported only once for each function it appears in
build/core/binary.mk:512: recipe for target '/home/louis/Dev/Ubuntu_Touch/out/target/product/falcon/obj/SHARED_LIBRARIES/audio.primary.msm8226_intermediates/msm8974/platform.o' failed

Ubuntu Touch definitly doesn't like Audio HAL

I wrote on my TO-DO list that I have many kernel related changes to do. Maybe that's it ?
[Moto G Android Development] the_MUKe:
audio_offload_info_t

Just checked where the audio_offload_info_t is defined:

hardware/qcom/audio/hal/audio_hw.h includes <hardware/audio.h>

hardware/libhardware/include/hardware/audio.h includes <system/audio.h>

system/core/include/system/audio.h defines audio_offload_info_t

In recent versions from CAF (also CyanogenMod) the struct contains the required field:

uint16_t bit_width; // bits per sample

See e.g. here (kk_rb5). I am not very familiar with CAF branches/tags. But maybe you should merge from one of these versions? Or possibly use the entire project from CAF?

Just noticed that the audio formats are also defined in this file:

AUDIO_FORMAT_FLAC = 0x18000000UL,
[Moto G Android Development] h2o64:
I didn't find this file ^^ thank you :)

I was looking for in frameworks

Yes. I wanted rebase on caf instead of cm....
[Moto G Android Development] the_MUKe:
Ramdisk inspection

I noticed a specific error occuring during booting into Ubuntu Touch. In particular this message in the kernel log:

initrd: Couldn't find a system partition.

This error happens when running the initial ramdisk, so I looked into it.

The ramdisk is part of the boot.img and can be extracted. However, when building from source, the ramdisk.img is already in the out directory and can be gunzipped and un-cpio-ed, i.e. create a subdirectory and then execute:

gunzip -c ../ramdisk.img | cpio -i

Interesting here is the file scripts/touch. The mentioned error message can be found at the very end of the script. It is the else-case of a rather long if-elif-construct.

The first case can be ignored because we are in boot mode "ubuntu" (as identified just above in the script).

# Only care about factory mode when using a real partition
if [ -n "$syspart" ] && [ "$BOOT_MODE" = "android" ]; then
# Factory mode, just boot directly into the android rootfs
.....

The next case is the flipped model (normal Android with Ubuntu Touch in container?):

elif [ -e /tmpmnt/system.img -o -n "$syspart" ]; then
# Loop-mounted flipped model
.....

The next case is the old flipped model (anybody knows more details?):

# Old flipped model
elif [ -d /tmpmnt/ubuntu ]; then
.....

And finally the else case with the error message:

# Possibly a re-partitioned device
else
echo "initrd: Couldn't find a system partition." >/dev/kmsg || true
panic "Couldn't find a system partition. Spawning adbd ..."
fi

So we would have to identify which case we need here.

Do we use the flipped model or the old flipped model?

Why the script does not detect the case properly?

Once we enter into of of these cases, a lot of other initialisation steps are executed and we could see how far we get then.
[Moto G Android Development] h2o64:
I looked on this file months ago.

We want the (old) flipped method.

The main issue is on the lxc container wich basically mount the partition.

I made changes on system/core and frameworks to support the MSM vendor init. Follow my github to get early informations because I do a lot in the background.

Thanks for your hard support!
[Moto G Android Development] mykehdoom:
Are there any videos or screenshots of the latest build?
[Moto G Android Development] eagleofdeath13:
How could a non-booting rom's screenshots be interesting? 0_o
[Moto G Android Development] mykehdoom:
I just wanted to know what the OS looks like...
[Moto G Android Development] h2o64:
Search on Google ^^
[Moto G Android Development] eagleofdeath13:
Any updates ? Is it testable or still in hard development? :)
[Moto G Android Development] Hugo Caixeta:
is possible build ubuntu for my moto g 2014 with tutorial ?

http://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[Moto G Android Development] eagleofdeath13:
This thread is about Moto G 2013, so not this tutorial.

With the linked tutorial, you have to try to know if it work ^^
[Moto G Android Development] h2o64:
I'm in my school period. But I know what to do when I'll have free time
[Moto G Android Development] eagleofdeath13:
Nice to hear it :D
[Moto G Android Development] the_MUKe:
Loop-mounted flipped model

Recently I took a look again at the last_kmsg log. There were some errors with mounting the data partition (which I ignored before). The errors occur because of mount options only valid for the ext4 filesystem. So I formatted the data partition with ext4 (can be done in adb or TWRP).

In this case, the touch script (inside the ramdisk) can successfully mount /data, finds the system.img and enters into the case of the loop-mounted flipped model:

elif [ -e /tmpmnt/system.img -o -n "$syspart" ]; then
# Loop-mounted flipped model

Execution of the touch script continues until line 358:

# system is a special case
echo "initrd: mounting ${rootmnt}/var/lib/lxc/android/system.img as ${rootmnt}/android/system" >/dev/kmsg || true
mount --move /android-system ${rootmnt}/android/system

Then the mount command causes a kernel panic. Anyone knows why?

I attached the corresponding last_kmsg log. The complete touch script is also attached.

Edit: The cause for the kernel panic could also be a later command, as there is no echo/log directly afterwards.
[Moto G Android Development] Hugo Caixeta:
Is possible install in moto g2 ?because moto g1 and 2 resolution ,processor even
[Moto G Android Development] eagleofdeath13:
It's not the same device, so probably not, no one knows, and it could break your device ...
[Moto G Android Development] Hugo Caixeta:
You use this ubuntu ? Any screenshots
[Moto G Android Development] eagleofdeath13:
Did you read the thread?

The rom is not working, how could i provide you screenshot?
[Moto G Android Development] Hugo Caixeta:
Ok
[Moto G Android Development] h2o64:
I need to add HAL support before going forward.

Ubuntu Touch is full aosp.

I'll rebase on caf
[Moto G Android Development] Hugo Caixeta:
hey any news

?
[Moto G Android Development] h2o64:
I'm working I'm working... If you want early news, follow my github.
[Moto G Android Development] methuselah:
Don't ask for etas you will make developer sick....
[Moto G Android Development] h2o64:
It won't.

But I definitely have to mention my signature that I only dev the weekend
[Moto G Android Development] 122393:
And about moto e xt1025? it's possible to install it?

i'm sick of this **** android, they only release new ports for the most expensive devices
[Moto G Android Development] eagleofdeath13:
Is the xt1025 a xt1032?

So how could it work?

A build is for one device, if it's not for yours, it's probably not a good idea to even try.
[Moto G Android Development] 122393:
MOTO E XT1025 bro, i want to know if there is any possibility to instal on MOTO E MOTO E MOTO E MOTO E

understand now? MOTO E
[Moto G Android Development] andogeek10:
Firstly, learn to talk properly.

Second, this is moto g forum, a device completely different to your and hence all the roms, kernels and most of the mods will not even work with your device. It is foolish to even entertain that thought.
[Moto G Android Development] eagleofdeath13:
MOTO G XT1032 MOTO G MOTO G MOTO G MOTO G

Can't you read the thread title ?

MOTO G!

(if that's how you speak, i'll answer the same way ...)
[Moto G Android Development] 122393:
You guys need to read with more attention and not try to make fun of people, i know it's about motog, sorry if you guys can't anser isnt for moto g.

I'm sorry to overestimate the intelligence of you asking hard questions
[Moto G Android Development] vritant:
Really appreciate the people working on this project. Kudos!

I wish I could help, but i don't really understand the technical stuff, although i could help with any kind of images.

But seriously, I can't wait for it.

Keep making us happy :D

p.s. Sorry for the cheesy note
[Moto G Android Development] h2o64:
?

Sorry if I am that busy
[Moto G Android Development] andogeek10:
By that same logic, you also over estimated your intelligence by asking if a mod made for a completely different phone would be compatible with your device

And if you'll read the reply again, you'll realize that your post had been understood properly and replied to as required.
[Moto G Android Development] Innocent Devil:
Really Appreciate your work [MENTION=4792450]h2o64[/MENTION].

I was running Ubuntu Touch on my old device (HTC Desire Z), it is barely usable though, but was fun.

I was eagar to make it work on Moto G.

Thanks for your hard work work.

Hoping we'l; have some builds which boots on Moto G
[Moto G Android Development] h2o64:
If I'm brave enough.

(and if I find the time)

I'll do a big part today
[Moto G Android Development] the_MUKe:
initrd successfully completes

Would be great to have a new build from h2o64. I did not get much far with the boot process.

However, I finally added some extra debug message to the touch script and repacked the new boot.img.

Suprisingly, I did not get the kernel panic anymore (don't know why). This is what I get from /proc/last_kmsg:

...
[ 4.833486,2] initrd: mounting /root/var/lib/lxc/android/system.img as /root/android/system
[ 4.836295,0] DEBUG: mounted android system
[ 4.836552,0] DEBUG: mounted Ubuntu overlay
[ 4.843813,2] DEBUG: applied device-specific udev rules
[ 4.848058,0] DEBUG: bind-mounted /lib/modules
[ 4.850827,2] DEBUG: bind-mounted /var/lib/ureadahead
[ 4.851103,2] DEBUG: setup swap device
[ 4.851715,2] DEBUG: applied customized content
[ 5.240425,3] init: ureadahead-touch main process (454) terminated with status 5
[ 10.805941,2] init: could not import file '/init.qualcommmsm8226(flatteneddevice.rc' from '/init.rc'
[ 11.332841,2] init: cannot open '/initlogo.rle'
[ 11.355910,2] init: Failed to bind socket 'property_service': Permission denied
[ 11.356241,2] init: init startup failure
[ 20.374914,0] System halted.

These last lines are already part of the actual init process. Something seems to be wrong with ureadahead-touch.

Any suggestions/ideas?
[Moto G Android Development] h2o64:
Please wait.

I'm working a lot on this project locally.

I do my best.

What did you add I boot image to get this?
[Moto G Android Development] the_MUKe:
Attached is the modified touch script (inside scripts folder of the ramdisk, without .txt ending).

I only added some debug outputs/logs towards the end of the file. Then cpio-ed and gzipped the ramdisk, and recreated the boot image with manually running the mkbootimg command. I took the required kernel command line options from the variable in device/motorola/falcon/mkbootimg.mk.
[Moto G Android Development] h2o64:
Hope Updated

I made the biggest part of the rebase

https://github.com/ubuntu-touchCAF
[Moto G Android Development] eagleofdeath13:
Yeah! Happy to see that you are closer to a runnable rom :D

Is it time for testers or not yet?
[Moto G Android Development] h2o64:
I'm building a new build
[Moto G Android Development] eagleofdeath13:
Can't wait to try it :D
[Moto G Android Development] Jhyrachy:
A quick question, how hard will be to port this to the Moto G 2014?

Same cpu/gpu/ram, i hope is not going to be so difficult
[Moto G Android Development] sub77:
/home/sub77/roms/ubuntu/out/target/product/falcon/obj/include/selinux/android.h:36:12: note: declared here

make: *** [/home/sub77/roms/ubuntu/out/target/product/falcon/obj/EXECUTABLES/debuggerd_intermediates/tombstone.o] Fehler 1

SELINUX SXXXX
[Moto G Android Development] Brawn_Sg:
Any progress

I can be a tester

But can't it be in .zip

Flashable in twrp ?