I corrected all the errors: one was located in file system/core/adb/transport.c, another one in frameworks/base/libs/androidfw/AssetManager.cpp and the other four were located in file frameworks/base/libs/androidfw/ResourceType.cpp. Now I can compile with GCC 4,5,6. In few words, since c++11 has been introduced the type char16_t and GCC 6 supports -std=gnu++14 instead of -std=gnu++98. So since all the warnings are considered as errors due to -Werror a cast from const uint16_t* to const char16_t* solved all the problems. I do not why android developers did not change this. I filed a bug to CM, in particular the involved version is 12.1 aka android 5.1.

The dualboot part is working as far as i can see. The problem is the image for nexus 10. it is broken, and even though it still churns out versions, it just does not get fixed. Somehow nobody wants to try and fix this. Fine, maybe it's just too broken to bother, but then at least be honest and remove that 90% functionality from the website. At least you gave a means to dualboot a device with an ubports image, which is something. Thanks for your effort. Yougo

I'm adding a few links here so I and others can find them easily. Ubuntu Recovery partition specs Touch/Specs/RecoveryPartition last edited 2013-06-14 upgrader ImageBasedUpgrades/Upgrader l st edited 2014-07-04 After more digging I've come to the conclusion that Edify stuff is mostly dead code. I'll leave these two links until I'm certain. https://wiki.cyanogenmod.org/w/Doc:_About_Edify (http://forum.xda-developers.com/wiki/Edify_script_language) I have been working under the assumption that system-image-upgader Was written by Marius become it seemed to come from nowhere in the ubports git history. In reality launchpad does reveal its arrival three years ago. author Stéphane Graber stgraber@ubuntu.com Tue, 9 Jul 2013 15:00:00 -0500 (17:00 -0300) committer Gerrit Code Review gerrit2@hesperidium.canonical.com Fri, 7 Feb 2014 09:03:14 -0500 (14:03 +0000) It's interesting to note that six months seems to have passed before it was accepted. It then goes through much development in 2014.

When you ported the OnePlus 3 phone to Ubuntu, then it would be great to port this app too as it is very helpful for migrating data from other phone to OnePlus 3.

Hi, With new OP3t, announcing also the death of OP3, what will be the future of the OP3 porting project? Can actual work be still useful for an OP3t porting project? What can we expect in the net months? Thx in advance

@below-freezing They only changed the case, nothing about the phone.

@siclight Great. Happy hacking.

Hi guys, any news?

@tom " I flashed ubuntu over the baseband of cm12.1. I thought that was what the advice was! " Yes, I think that was the advice. My cheap advice about mixing systems -> " dual booting is just not worth the trouble."

@21347 Hi, I deleted my former post because it was out of the topic. Regarding your qmi.h issue it seems to come from hardware/qcom/wlan being a different version from fairphone's one. I am trying to get a successful build without resorting to copy-paste (apart from the binary bundle I download from code.fairphone.com) so I modified my .repo/manifests/default.xml to remove the default hardware/qcom/wlan line and replace it by the one you can find in the Fairphone Open Source release. It's still building (and will be for a while) but I am pretty sure I am past the part where it used to block ! If you want to pm me on FP's official forum so we can coordinate and avoid duplicating efforts, my handle is Arvil (with Batman on LSD as my Avatar ) EDIT : It actually goes forward until I reach an issue with hardware/qcom/audio-caf, I'm still figuring it out EDIT 2 : I removed audio-caf from the manifest and... #### make completed successfully (01:03:35 (hh:mm:ss)) #### arvil@michel:~/fp2-ut/phablet$ YESS ! Now I have to try it, I'll put the manifest in a git repo soon

If this happens to you, it's probably because the sever has gone out to lunch. https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1610650 I recommend an email to: rt@ubuntu.com asking for a restart. https://code-review.phablet.ubuntu.com/ has become unresponsive. Please, restart. Thank you. Took them less than 10 minutes : )

Not sure where this should go, I have made some comments on the launchpad bugs pages. Basically I think loads of the trouble I'm having with apps not starting, crashing or hanging after the initial loading screen is related to https://bugs.launchpad.net/ubports-android/+bug/1625832, would make sense if the web apps use Browser as a base? Not sure why uNav would hang but maybe what is crashing the Browser app is also causing calls to web services in other apps to silently fail? Telegram 100% works, so not a connectivity issue.

Old news on G+ A little old but great to hear Nexus 6 port is in the works

Hello again and sorry for my long absence to the forum. I've had a hdd crash and my linux os (secondary on the laptop) disappeared, so I was unable to read any messages. I didn't figured out any new steps to make Ubuntu Touch working on my Nexus 10. It looks like there is some part missing in all the tutorials . I will reanimate my Ubuntu biulding environment to come back to the topic and will share my progress.