I guess it was the carrier, Patriot is a "third party" and has limitations according to their support line, it never connected, and we tried for an hour, but the phone did not report a message to indicate it was SIM locked, I got an AT@T prepaid and it works great...basically same low rate too. I had reflashed to android and upgraded to Android 11 verified it worked, then flashed UT which was successful the very first try. A lot works on the Pixel too.

I have a Pixel 3a XL and using GrapheneOS, which the updates end in August 2022. At that time, I will be installing Ubuntu Touch so I am watching this page for any updates regarding a smooth installation. Thanks

@grhmhome Sorry for bumping the thread (again), but I solved my issue. Since my old account was Sprint, it wasn't going to work out of the box, but I switched to T-Mobile and it now works properly.

@crab_aesthetics First I thank you for the process you showed in your install. It is a good road map. I will be trying a similar install as soon as I get my replacement phone. I will be using a Linux laptop and my cellular provider is Visible by Verizon.

@trwidick OTA-18 Looks to have solved this. Update is available today. If so please close out this issue. Thank you.

@applee thanks. I didn't want to flag him with the use of his handle (I think he has a few other issues he is tackling at the moment) which is why I simply added his forum user page if we wanted to escalate the issue. Regardless, glad to hear he is aware. Cheers

@dieharddan Thanks for the response.

@captainzer0 Good news, please mark as solved it may help others Thanks https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved

@fredldotme I had the same problem, and after check the box 'wipe data' it worked very well. Thank you

If it works let me know. Also i would open a github issue for US cellular- CDMA. Maybe some one will have an idea.

@haimeh So I never actually had to add the route ... it seems the OTA17 fixed my issue (but no all issues). One other thing I did around the time, although don't think this has anything to do with was something I stumbled on while troubleshooting: /usr/share/ofono/scripts/set-context-property 0 Protocol IP Here are the route tables for 3G & 4G with WIFI on: (hope the formatting holds!): 3G & Wireless default 10.x.1.1 0.0.0.0 UG 600 0 0 wlan0 default 10.xx.xx.20x 0.0.0.0 UG 700 0 0 rmnet_data1 10.x.1.1 * 255.255.255.0 U 600 0 0 wlan0 10.xx.xx.20x * 255.255.255.255 UH 700 0 0 rmnet_data1 192.168.250.0 * 255.255.255.0 U 0 0 0 anbox0 4G & Wireless default 10.x.1.1 0.0.0.0 UG 600 0 0 wlan0 default 10.2xx.x6.2x5 0.0.0.0 UG 700 0 0 rmnet_data2 10.x.1.0 * 255.255.255.0 U 600 0 0 wlan0 10.2xx.x6.2x5 * 255.255.255.255 UH 700 0 0 rmnet_data2 192.168.250.0 * 255.255.255.0 U 0 0 0 anbox0 Not sure if rmnet_data1 and 2 are standard across all phones /connections. If not, you should be able to spot yours by tailing the logfile... Hope this helps! PS: to check if you are on OTA17: SystemSettings> About OS should have Ubuntu 16.04(OTA-17)

There might be minor hardware differences, too. At least on Pixel and Pixel 2 the XL variant has a different build tree with some incompatible differences.

@azraelpwnz Glad I could help! ... Very weird bug. Now if only we could find a workaround for MMS!

@tchan Thankfully, not all no, since MX4 battery hardware issue would make it a dead phone if only online charging was psossible lol.

@givemeaname sounds like a faulty cable to me then. On my Nexus 5 it also sometimes has issues with losing connection, but normally the installer resumes as well if the cable isn't super bad.

@givemeaname https://github.com/ubports/ubports-installer/releases/tag/0.8.6-beta use the snap if you can and try Ubuntu maybe, not familier with Fedora myself.. Also don't forget wipe and bootstrap when asked.

@freefrog Thx for answering. I allready switched to google free android since I needed to use my phone. I will try to reinstall Ubuntu on weekend and tell you if it worked.