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.

@manchee1017 Thanks! agree to shift apn discussion over. re reboots: yes, i am talking soft. Hard (power key hold) always brings me to reboot.

Sadly Miracast support still needs some work on Android 9 based devices. I'm sure it will get there but it's not working right now. Still, it will be the only way to support external monitors.

@hawi Anbox has been enabled now and will be released in tomorrows devel image.

@antidroid thanks for looking into that. A rather odd design decision but happy to know that also means they likely used an earspeaker that should tolerate high volumes.

@pengaro yes, icons and text (the whole UI) basically are tailored to the non-XL variant screen resolution, they will look bigger on the XL since that's the scaling value it has been set to. But you can change it with the Ubuntu Touch Tweak Tool.

@oliv thanks, I will reinstall UT soon and give it a try

@dieharddan Yes it is on. I got it working now on 3G

Thanks for the reply. It's not powering down at all. It literally goes to the Android Recovery screen briefly before the Google splash screen then boots into UT.

For anyone else, if you do a factory reset and wipe out your personal data it will reload the os and work ok. IT would be nice to figure out what app or tweak causes the issue though.

@fredldotme got it thanks!