Indeed please do not confuse things: The stable Nexus 5 on Legacy 5.1 porting is super-stable. This thread you mentioned is about an alpha stage build for upgrading to an Android 7.1 base. Its fairly unstable but will become better and better over time. However for daily use only use the installer-provided stable image.

is there a bug tracker I could follow to see when this bug is fixed.
I really don't want to fork out for a Bluetooth keyboard for one sign in.
Sorry new to Ubports not familier with everything yet 🙂

@AppLee Nice. thx

@Lakotaubp well done to you for the work you put in on the forum - I've read a lot of installation problem posts over the past few days where you are helping out.

I've installed Ubports on a family member's phone and they have been using it successfully as a daily driver for the last couple of years, and have contributed to the foundation, so it's great to see the project go from strength to strength with the pinephone and everything else.

Hi @CAnoop,

The only thing I think about regarding your question is that one of your folder has not been properly converted in ext4
Make sure you try them 1 by 1 using "Repair" or "Change" functions
If you have an error message saying you can't convert, then try using other functions of TWRP, you should be able to convert them all 3.

Also, According to what I read in this forum, the "Android actions-> Full Factory Reset -> Wipe data" action is not always necessary.

Good luck !

@Abuabdellah

I found that :

Alternatively there is the old Ubuntu SDK IDE. Be aware that it is no longer supported by Canonical, and UBports has chosen to not support it either due to lack of manpower.

also mentioned on telegram by @dobey

74097283-fe4f-45f7-9179-7bac1e3cbd59-image.png

@domubpkm Thanks for posting that - it seems a few of us are having trouble with the installer and having a manual install option is valuable.

I ran the command in fastboot mode and got the following message:

Get https//system-image.ubports.com/channels.json: unsupported protocol scheme ""

Could you point me in the right direction?

The issue seems fixed now.

@jojuma Well done. Could you please mark the post as solved using the Topic Tools button. First choose ask as question then mark solved. This will help others.Thanks

@shapley
Glad you're back to normal.

Can you please mark your post as solved ?
You can use the "Topic Tools" mark it as a question then mark is solved.

This will help people searching for already solved issues.

@gischpelino
Thank you for that, it worked

Because I did not follow through the instructions procedure upon installing I'm kind of reluctant to use TWRP now it is installed (only changed 'Keep System Read Only' into allow changes) , frankly I'm not sure whether it'll do more harm than good going through all options available. Too scared of the unknown I guess.....

How to check if I still need to change that into ext4 format?

@stanwood For me, the most amusing thing on the workaround is, that it is just a user-agent string update. 🙂

I know this thread is old, but maybe a new comment can help those that are following it.

My tether connection is working. I have macOS Catalina and a Nexus 5 with OTA-12. A driver for OSX can be located at: https://joshuawise.com/horndis

Sometimes there may be problems and with OS updates, too. I found some good stuff at Github: https://github.com/jwise/HoRNDIS/issues/102

You may get advice that can get you going in the right direction. My internet connection is pretty fast from my Nexus 5 and I hope it continues to work.

I hope this helps someone.

Thank for your revelations Stan, that the installer is not the entire answer to getting UT on the phone, and also that I have been holding buttons in for too long awaiting a response from the phone. If the UBPorts instructions had contained that information maybe I would have been successful, however I am now pursuing the purchase of a phone with Ubuntu Touch already installed.

kugiigi: I found the file. Thanks. I'll try to figure out how to change the keyboard sound to something custom.

Hiding the SSID isn't about security. I read an article on that. I'm in a position where "out of sight out of mind" is appreciated. Thanks for any advice.

@penguining Hi,
I'm glad you got it working.
I just wanted to add that I had a similar experience, but without a happy ending. I've had different experiences depending on the installation source; from best to worst it was: AppImage, deb package and snap package.
As with you, the AppImage recognised everything and installed successfully; at least that's what the message says. The deb was similar but couldn't recognise the device initially. The snap did not work at all: didn't recognise, kept complaining of lost connection to the device and no message of successful installation.
Also, volume up + power never worked for me, only volume down + power.
So at the moment I'm stuck with the UBports recovery screen.

Cheers!

@mymike Oh okay, I thought I missed this feature 😅