[WIP][DEV] Ubuntu Touch for Sony Xperia Z Ultra

Search This thread

blueether

Senior Member
Jan 21, 2011
3,391
1,639
Te Awamutu, New Zealand
Ok lets get this going:

Welcome to The Ultra Collective ;)

Development for the ZU including:
  • ROMs:
    • Carbon
    • Ubuntu Touch
    • AOSP
  • Kernels:
    • CM11 dt2w
    • BluePimp (Port of Z1 Pimped Kernel)
 

Kohelet

Member
Sep 15, 2013
35
21
Ashburn, VA
kohelet.tech
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle

Sent from my C6833 using XDA Free mobile app


It would seem that the UT wiki does somewhat describe this process. This article discusses building UT from fresh AOSP sources (making your own changes). Perhaps that is what needs to happen here.
 

KalleEatingBrain

Senior Member
Feb 1, 2013
55
80
Bremen
Better documentation incoming

Hi,
I attended the ubuntu-on-air session on tuesday and was told that some devs might take a look at the porting guide in the Ubuntu Touch Wiki which is - what the guys from cannonical admitted - hopelessly outdated. I was told, the developement went on so fast, there was no time to document it for the community. They are getting money for OEM/RTM installation of Ubuntu Touch, so they are focusing on that, even though the community ports are an essential part of the project. I will update this post, as I come to know when the update of the porting guide will happen.
Best regards,
Kalle


If someone is reading this but does not know how to contribute: Why not donate some money to donations@ubuntu.com via PayPal and claim that you want a better porting guide? Might speed up the whole affair.
 

Kohelet

Member
Sep 15, 2013
35
21
Ashburn, VA
kohelet.tech
Hi,
I attended the ubuntu-on-air session on tuesday and was told that some devs might take a look at the porting guide in the Ubuntu Touch Wiki which is - what the guys from cannonical admitted - hopelessly outdated. I was told, the developement went on so fast, there was no time to document it for the community. They are getting money for OEM/RTM installation of Ubuntu Touch, so they are focusing on that, even though the community ports are an essential part of the project. I will update this post, as I come to know when the update of the porting guide will happen.
Best regards,
Kalle


If someone is reading this but does not know how to contribute: Why not donate some money to donations@ubuntu.com via PayPal and claim that you want a better porting guide? Might speed up the whole affair.


That's good to know! In the mean time, I'll start looking at the builds for odin to see if I can determine enough from that to get a working build for togari.
 

Kohelet

Member
Sep 15, 2013
35
21
Ashburn, VA
kohelet.tech
Ok lets get this going:

Welcome to The Ultra Collective ;)

Development for the ZU including:
  • ROMs:
    • Carbon
    • Ubuntu Touch
    • AOSP
  • Kernels:
    • CM11 dt2w
    • BluePimp (Port of Z1 Pimped Kernel)

Any new developments on this front? I recently moved so I haven't been getting after it lately, but I'm still curious to see this continue....


Part of me is thinking that since the kernel sources are on github it might be easier to start with the kernel and build UT from there instead of working from the CM parts....

Thoughts?
 

KalleEatingBrain

Senior Member
Feb 1, 2013
55
80
Bremen
postponed

Hi,
Following the mailing list the RTM is more of a priority than the porting to new devices, so I'm waiting for this to pass. Anyways, I looked at the possibility to use a "handbuild" kernel and than adding system and stuff from another device. i assume there are already plenty of How-Tos and guides about decompiling the kernel and editing the ramdisk and also compiling the android kernel and adding desirable features, but if you want me to I could do a write-up in @blueether s dev thread.
Regards,
Kalle
 
  • Like
Reactions: boly007

Triflot

Senior Member
Sep 17, 2011
332
409
Actually, now that our beloved Masters of Development are getting pure AOSP sources working for our devices, I think this may be easier to do.
 

Kohelet

Member
Sep 15, 2013
35
21
Ashburn, VA
kohelet.tech
Unfortunately, it seems that the Ubuntu Touch team is primarily focused on completing work for the BQ and Meizu phones that will be sporting Ubuntu Touch. That said, significant changes have been made to the OS that make the current porting guide completely unusable for porting. Which means people who want to port are left to do a lot of heavy lifting on their own with no support from the team working on the core of the OS because, as KalleEatingBrain mentioned, porting is just not a priority of theirs at the moment.

I've been monitoring their IRC and mailing list for relevant updates when I have time, but for the moment I've found it wouldn't be a good use of time to bang my head against Ubuntu Touch. Especially when the documentation of it is seriously outdated with no sign of being updated any time soon.
 
  • Like
Reactions: Triflot

KalleEatingBrain

Senior Member
Feb 1, 2013
55
80
Bremen
Unfortunately, it seems that the Ubuntu Touch team is primarily focused on completing work for the BQ and Meizu phones that will be sporting Ubuntu Touch. That said, significant changes have been made to the OS that make the current porting guide completely unusable for porting. Which means people who want to port are left to do a lot of heavy lifting on their own with no support from the team working on the core of the OS because, as KalleEatingBrain mentioned, porting is just not a priority of theirs at the moment.

I've been monitoring their IRC and mailing list for relevant updates when I have time, but for the moment I've found it wouldn't be a good use of time to bang my head against Ubuntu Touch. Especially when the documentation of it is seriously outdated with no sign of being updated any time soon.

Thanks for having my back ;)
It's not that I stopped working on this, but I just don't make any progess and the support for porting is really bad. In the beginning I thought Ubuntu Touch might be a big thing because of the good community, but right now Cannonical is not very community friendly to anyone who doesn't have a Nexus device. Just take a look at the supported devices: Everything stopped after maybe 5 initial builds within the first 2-3 month after launch. I talked to the guy who maintains the UT build for the Xperia Tablet Z, which is like the only device that get's any updates, and he is willingly to help, but he says that it's really hard, even for someone who might have a extended knowledge of android development and linux.

Is anyone interested in joining me for porting FireFoxOS? They have a nice and clean porting guide and use Android 4.4 sources as default, so we could use CM sources. I want to have a exotic OS on my phone, that's why I started this xD
 

Kohelet

Member
Sep 15, 2013
35
21
Ashburn, VA
kohelet.tech
Thanks for having my back ;)
It's not that I stopped working on this, but I just don't make any progess and the support for porting is really bad. In the beginning I thought Ubuntu Touch might be a big thing because of the good community, but right now Cannonical is not very community friendly to anyone who doesn't have a Nexus device. Just take a look at the supported devices: Everything stopped after maybe 5 initial builds within the first 2-3 month after launch. I talked to the guy who maintains the UT build for the Xperia Tablet Z, which is like the only device that get's any updates, and he is willingly to help, but he says that it's really hard, even for someone who might have a extended knowledge of android development and linux.

Is anyone interested in joining me for porting FireFoxOS? They have a nice and clean porting guide and use Android 4.4 sources as default, so we could use CM sources. I want to have a exotic OS on my phone, that's why I started this xD

Is ffOS stable enough to be used as a daily driver?

---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------

I asked around in IRC to see if they have plans to update the porting guide any time soon. One of the devs said that once they've completed work on the devices that will have UT preinstalled (the BQ and Meizu phones), he'll work on getting a new porting guide out...At that point I'll probably give porting another shot.
 

Pallavgarg10

Senior Member
Jul 30, 2013
63
4
With all due respect if you want an exotic os i suggest SAILFISH OS
That os is in desperate need of a large screen device like z ultra
Please consider porting SAILFISH OS
Thanks
 

Kohelet

Member
Sep 15, 2013
35
21
Ashburn, VA
kohelet.tech
Any Progress in Porting Ubuntu Touch ? Someone ? :'(



I'm been working on it since the new porting guide came up. As I write this I'm actually creating a local mirror since I have multiple Xperia devices I'd like to see it on. As for my own progess, I gave it a shot about a week ago but ran into issues that I think were because I didn't have a clean aosp tree to start with. I'm going to start fresh once I have both the aosp and ubuntu source trees mirrored. We'll see how far I get...my goal at this point is just to get something that will boot on the Ultra (or the Z2 for that matter).

If you're up for the challenge I'd recommend giving the porting guide a shot. If you combine the steps in that with the steps from the sony guide for building aosp some decent progress might be made. The more people looking at it the better.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    Hi folks,
    I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
    Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
    Best regards,
    Kalle

    First Update:
    I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
    The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
    Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
    So long,
    Kalle

    Update!
    There is a new porting guide! See here
    I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
    Hope you are as excited as I am,
    Kalle

    XDA:DevDB Information
    Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra

    Contributors
    KalleEatingBrain, Kohelet
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: Unlocked Bootloader
    Based On: AOSP

    Version Information
    Status: Testing

    Created 2014-05-14
    Last Updated 2015-02-24
    5
    So I've gotten the build to start, but I'm running into issues with libhybris:

    ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
    compilation terminated.
    make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error


    I'll post here once I've found a solution.
    5
    Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
    Best regards,
    Kalle


    I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).

    Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.

    At this point I've decided to take a short break from the whole thing because it's so frustrating. :p

    Once I get motivated to work on it again, I'll probably start from scratch.



    Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):

    If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk

    Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.

    The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk

    I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.

    If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]

    You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk

    You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.

    If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk

    You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.

    You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
    3
    Unfortunately, it seems that the Ubuntu Touch team is primarily focused on completing work for the BQ and Meizu phones that will be sporting Ubuntu Touch. That said, significant changes have been made to the OS that make the current porting guide completely unusable for porting. Which means people who want to port are left to do a lot of heavy lifting on their own with no support from the team working on the core of the OS because, as KalleEatingBrain mentioned, porting is just not a priority of theirs at the moment.

    I've been monitoring their IRC and mailing list for relevant updates when I have time, but for the moment I've found it wouldn't be a good use of time to bang my head against Ubuntu Touch. Especially when the documentation of it is seriously outdated with no sign of being updated any time soon.

    Thanks for having my back ;)
    It's not that I stopped working on this, but I just don't make any progess and the support for porting is really bad. In the beginning I thought Ubuntu Touch might be a big thing because of the good community, but right now Cannonical is not very community friendly to anyone who doesn't have a Nexus device. Just take a look at the supported devices: Everything stopped after maybe 5 initial builds within the first 2-3 month after launch. I talked to the guy who maintains the UT build for the Xperia Tablet Z, which is like the only device that get's any updates, and he is willingly to help, but he says that it's really hard, even for someone who might have a extended knowledge of android development and linux.

    Is anyone interested in joining me for porting FireFoxOS? They have a nice and clean porting guide and use Android 4.4 sources as default, so we could use CM sources. I want to have a exotic OS on my phone, that's why I started this xD