[NEW TEST] [PORTING] Ubuntu Touch

[coalwater]

1. repo init -u git://phablet.ubuntu.com/CyanogenMod/android.git -b phablet-saucy
2. create .reop/local_manifests/*.xml
   <?xml version="1.0" encoding="UTF-8"?>
   <manifest>
   
   <project path="hardware/qcom/display-legacy" name="LegacyXperia/android_hardware_qcom_display-legacy" remote="github" revision="1e890bb292ab98825f850f1ad84785a12f16b23b" />
   <project path="hardware/qcom/media-legacy" name="LegacyXperia/android_hardware_qcom_media-legacy" remote="github" revision="cm-10.2" />
   <project path="device/samsung/ariesve" name="czobor/android_device_samsung_ariesve" remote="github" />
   <project path="vendor/samsung/ariesve" name="czobor/android_vendor_samsung_ariesve" remote="github" />
   
   
   </manifest>
3. repo sync
4. cherry-pick http://review.cyanogenmod.org/#/c/34376/ and http://review.cyanogenmod.org/#/c/34375/, perhaps others, too
5. building

That's all.

How big are those repos? cause if they are too big I don't think I want to wait for them to download lol

PS: Started downloading the modified phablet saucy, will report back after testing it.

---------- Post added at 07:21 PM ---------- Previous post was at 07:01 PM ----------

The uploading have taken more than one hour, I really hope this time it'll boot...

That's why I think it is useful to have a nice cheap vps and edit remotely, no need for long download/upload times.

 

[czobor]

How big are those repos? cause if they are too big I don't think I want to wait for them to download lol

It's 4,4 GB, quite small.

 

[coalwater]

The uploading have taken more than one hour, I really hope this time it'll boot...

Flash with test 9.

http://d-h.st/oJG

Modified with this: https://github.com/w-flo/rootfs-modifier

Changelog

1. Scripts for flashing are modified to copy the rootfs tarball to /sdcard instead of /data if /data is too small (that is the case for our Desire Z). I posted a similar patch to Launchpad bug #1145984.
2. The file system table (fstab) is pre-populated with /system and /vendor partitions for the Desire Z because the script that is responsible for creating those table entries automatically doesn't work with our device. (Either because I configured the kernel in a bad way or some driver is missing some features, or for whatever reason.. /dev/block should have friendly names for the partitions, but it doesn't.)
3. Apparently, there should be /data in fstab as well, but as /data is already monted as /, this fails, so this script disables mounting of /data in the lxc boot script. Probably not the right solution, but it works for now.
4. Add configuration files for the Desire Z: DPI settings and device access rights (udev rules).
5. Disable swap and remove the swap file to save some space, our partition is really small
6. Change apt settings to save a little more space

Well I'm still trying to install it properly, but the phone always restarts before the deployment is over, so I try to reinstall it just to get a successful installation, but the second installation gets an error saying that the /data is full, for some reason I can't flash the same thing more than couple of times without wiping /data.
What's really bothering me is the restart thing, it starts installation and in the middle it just restarts without completing it, I assume it's some sort of error or something that forces the phone to restart, I'll try a couple of times more then see how it goes

 

[coalwater]

Sorry but didn't work, I was able to do a successful installation but still black.

# mount
rootfs on / type rootfs (rw)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=179744k,nr_inodes=44936,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=36204k,mode=755)

And attached kmesg

 

[Ubuntu-i9001]

My i9001 is taken from me so i will not be able to test unless i steal it back and try everything quickly

Sent from my LG-E975 but not forgetting the ultimate GT-i9001

 

[czobor]

FOR DEVS

Similar issue here: https://lists.launchpad.net/ubuntu-phone/msg04075.html

 

[coalwater]

FOR DEVS

Similar issue here: https://lists.launchpad.net/ubuntu-phone/msg04075.html

Looks promising, it's exactly what i was having.

 

[czobor]

Test 10.

Changelog

1. Sources synched
2. Added data partition device node to kernel cmdline (excepts to find data in mmcblk1p2, should fix "initrd: Couldn't find data partition. Spawning adbd ...")
3. Disabled CONFIG_VT and CONFIG_VT_CONSOLE (kernel)

http://d-h.st/5yj

It comes with 3.0 kernel with apparmor, here's the source:https://github.com/czobor/android_kernel_samsung_msm7x30-common/tree/apparmor_3.0

Flash with http://d-h.st/oJG

Please note that the sources on my github are not completely up-to-date

 

[Ubuntu-i9001]

Why today why :´( my phone is not with me if it was two hours ago i could bring my phone with me to collage

Sent from my LG-E975 but not forgetting the ultimate GT-i9001

 

[coalwater]

Test 10.

Changelog

1. Sources synched
2. Added data partition device node to kernel cmdline (excepts to find data in mmcblk1p2, should fix "initrd: Couldn't find data partition. Spawning adbd ...")
3. Disabled CONFIG_VT and CONFIG_VT_CONSOLE (kernel)

http://d-h.st/5yj

It comes with 3.0 kernel with apparmor, here's the source:https://github.com/czobor/android_kernel_samsung_msm7x30-common/tree/apparmor_3.0

Flash with http://d-h.st/oJG

Please note that the sources on my github are not completely up-to-date

I'll test it when I'm back from work

 

[veladem]

Man I would love to see you guys rock this ROM, I'll tell you right now people like me and many more are during patiently to see what happens, cause this might just help or issues on the cappy i897. Fingers crossed!

And there is some work being done on our side also, just not much support on either side.

Think everyone could collaborate, or is it I fear far to early in the game?

Sent from my SGH-I897 using XDA Premium 4 mobile app

 

[Ubuntu-i9001]

even if it got bootable it will not be good for daily use cuz it still missing some important features (i can't recall any)

Sent from my LG-E975 but not forgetting the ultimate GT-i9001

 

[coalwater]

even if it got bootable it will not be good for daily use cuz it still missing some important features (i can't recall any)

Sent from my LG-E975 but not forgetting the ultimate GT-i9001

Actually version 1 of ubuntu touch should be released on 17th this month, according to this message on their mailing list, so I'm assuming it should be good enough for normal every day usages by the time we get it working on our phones.

 

[PsychoGame]

Hello everybody,

I've also studied the Ubuntu Touch porting guide to see what needs to be done.
Theoretically this project should be possible to complete.
Also I've studied the source of this project on the Github.
This raised a questions for me:
In the device kernel configuration the following configuration flags are missing:
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
Is there a particular reason that these are not enabled in the default config, as I couldn't find the answer in this thread.
I'm currently creating a special Ubuntu Touch Porting "Virtual Box Guest" on my LMDE box to try and help in this project as well.

Greetings PsychoGame

 

[coalwater]

I'll test it when I'm back from work

Didn't boot, and what's worse is that busybox didn't start any more, when i flashed test9 back it worked, even without reinstalling the modified sausy zip

 

[PsychoGame]

Currently building my own test build as well.
Will report back how far I get when the building finishes.

Greetings PsychoGame

Update 1:
The building takes a little longer than expected.
There seem to be some differences in the ramdisk creation I think.
When building the source the process complains about a too small Boot partition.
As a workaround currently I disabled the GT-I9001 splash screen during boot and try to build the whole rom again.
Hopefully this will create the necessary space. Keep everybody updated

Update 2:
Made a stupid mistake. The problem is that the generated ramdisk.img is just a littlebit too big.
The mistake I made was assuming the contents of this where the CM ramdisk, but it's actually the ubuntu ramdisk it fails on.
First I'm going to celebrate the weekend and in the new week I will experiment with some ramdisk compressions for a new try.

 

[PsychoGame]

With a lzma compressed ramdisk, and a kernel which supports lzma ramdisk compression I was able to create a boot.img of 4.8Mb in size.
Then I installed the cyanogenmod file created by the Ubuntu Touch android sources with a total size of 28.2 Megabytes.
Unfortunatly after deployment of the ubuntu touch file and restarting the phone the screen stays completely black and the buttons on the phone are totally unresponsive.
I know that it didn't shut down again, because when I stick in the power supply the battery loading indicator doesn't come up.
Also ADB doesn't list the device at all which in my opinion means it doesn't even get to mounting the partitions before adb is started.

 

[Aldokazer]

With a lzma compressed ramdisk, and a kernel which supports lzma ramdisk compression I was able to create a boot.img of 4.8Mb in size.
Then I installed the cyanogenmod file created by the Ubuntu Touch android sources with a total size of 28.2 Megabytes.
Unfortunatly after deployment of the ubuntu touch file and restarting the phone the screen stays completely black and the buttons on the phone are totally unresponsive.
I know that it didn't shut down again, because when I stick in the power supply the battery loading indicator doesn't come up.
Also ADB doesn't list the device at all which in my opinion means it doesn't even get to mounting the partitions before adb is started.

So its hard-bricked?

 

[PsychoGame]

So its hard-bricked?

No luckily not, I was able to get it booting again but it's going in a bootloop.
Everything seems to be installed fine, but when the device boots up the buttons are lighting up this time.
Also I notice that the phone is getting very hot on the backside around the sdcard slot.
After maybe 1 or 2 minutes the phone just reboots again with Samsung logo showing and then with black screen and lit up buttons again.
Unfortunatly adb doesn't see the device, so I can't pull of a logcat to find out what's going wrong.

 

[coalwater]

Test 10.

Changelog

1. Sources synched
2. Added data partition device node to kernel cmdline (excepts to find data in mmcblk1p2, should fix "initrd: Couldn't find data partition. Spawning adbd ...")
3. Disabled CONFIG_VT and CONFIG_VT_CONSOLE (kernel)

http://d-h.st/5yj

It comes with 3.0 kernel with apparmor, here's the source:https://github.com/czobor/android_kernel_samsung_msm7x30-common/tree/apparmor_3.0

Flash with http://d-h.st/oJG

Please note that the sources on my github are not completely up-to-date

Well after reading this again, I remember that adbd didn't start on my test, does that mean that /data was found? And if it was found, how do I know what's the next thing that's making it not complete the boot ? can I reach the log somehow?