We are the changelog writer Test it ! It's about 10mn installation and share what's works or not Going back to Android is about the same duration, so, 1/2 hour is enough for all stuff !

I have found help here : https://forum.xda-developers.com/google-nexus-5/general/port-ubuntu-touch-nexus-5-t2594874/page59 It's not difficult. It works with Android and Cyanogenmod. If you do it, take some note and please write it on the wiki or on the forum asking for help to edit the wiki. That would help others.

@d4Rk-r4nG3r said in OnePlus One apps crash: The second issue is the lockscreen. Once the screen is turned off, I can't turn it back on easily. When I press the power button, nothing. when I press a second time right after, the lock/welcome screen only briefly flashes, and returns to black. I can get around that, if I rapidly hit the power button. I think I see a similar behaviour on my Nexus 7. My impression is that it is sleeping /too deeply/. If the device is busy, like playing a stream in podbird, then waking up is easy. I don't how to solve it though. Sometimes I end up forcefully rebooting the device just because I can't turn on the screen.

Reading rootstock script and modifying it to your needs is good way to learn this process. I have also been doing this. Are you able to flash and use the boot and recovery partitions?

And I saw the suggestions about placing in git and assumed GitHub : ) Yes, write in one place ! Maybe here ?

@apple.muncy Oh, sorry. I assumed that the "started here" could be the same. I'll creat the threat.

So I'm using this as a notebook to keep track and also share progress. Today I tried out the rootfs of 9-20-2016 has the display corruption. So backing off to 7-28-2016 works fine as far as the display goes. Now to do some testing on it I need to set the rootfs writable to be able to install more packages but I struggle to remember the utility to do it with. To be continued....

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.