@magnolia_dudeFirstly glad your all sorted and enjoy Ubuntu Touch. Windows often throws a spanner in the works unfortunately. Things get lost during the process which is why we say to use the 15 sec adb version on windows and to remove other phone drivers. Why it happens I'm not sure, I never had an issue once I had 15 sec adb installed but others have. Some don't even need the 15 sec version. Which is what makes it awkward when adding or not adding info to the install instructions. Still maybe something to keep in mind.
The snap version of the installer is in my opinion the easiest version to use and you can watch progress in the terminal.
@einstein212 thanks for the heads up! I just got the update and it fixed loads of bugs for me. Turns out I had the updates set to wifi only. I think I did that a while back to prevent things from downloading when I didn't want them to. Makes me feel silly now for doing it seeing how much smoother I've found OTA 3 to be.
Hello, This is an old post but I hope this still helps you.
Recently theres been a n update which fixes many of these issues, the browser works, wifi, and even the screen working properly, the update came out earlier this week and is available if you flash devel_rc-proposed rather then stable or rc-proposed.
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.
Hello. I tried installing Ubuntu Touch with MultiROM and TWRP recovery without kexec-hardboot support enable, with the no kexec-workaround enable in the Recovery options, which resulted in a hard brick. I just want to warm people not to do this. CM12.1, CM13.1 and CM14 do not have the corresponding adapted kernel with kexec support, so don't use them as main ROM if you plan to install Ubuntu Touch, because the workaround available in the recovery will just cause a hard brick.
Its not finished unfortunately, its not daily by a good amount, There will be an update coming at as soon as Marius can, unfortunately some new bugs in unity 8/mir had pushed him back from the original release date a few weeks ago.
Thanks again. Still not working for me. It says it's booting recovery, and boots to the OnePlus screen. I also let it sit for over an hour just to try, and when I reboot (hold down the power key) it boots to a OnePlus screen (presumably trying to reboot recovery again) and hangs. I let that sit for over an hour and reboot (hold the power key again) and it boots to Android.
I am not sure how it worked for you without booting into Ubuntu recovery to install. I understand it did work, just not sure how it's possible.
Edit: This is resolved for me. I reinstalled twrp and formatted my internal storage aka sd. Once done, installation succeeded without issue.