2.b. should read adb reboot fastboot

Addendum 2: Of course, it could be BT, but I thought I'd check-in with you guys first before tackling the behemoth; but to be fair once you get to a actual person, I have found they were knowledgeable and helpful. Anyway, as the problem hasn't been reported here, I'll adduce it's some glitch involving BT and close this question; and my life can move on. Thanks for the (tacit) help.

@nogoogle I don't know why I didn't think of this before, but the whole reason that I left Telus was because they said that due to network changes, my device (then a Oneplus 5t) would no longer have functional MMS. https://www.telus.com/en/support/article/picture-and-group-messaging-changes The linked article says "older decices", but other communication from Public Mobile said the only way to be sure was to use a phone from a fairly small approved list, which FP4 isn't on. Maybe some kind friend who uses another network would let you briefly borrow their SIM for MMS testing, to see if changing networks would solve it.

@kugiigi thanks for your information... Better wait a while.

Best of luck, and let us know how you get on!

@wynn1212 You're the best . TBH i was hoping you would do it, because you faced the same problem. Maybe there will be a real solution soon .

I forgot to include the nmcli output: nmcli-show.txt

@Martin5 Yes, Marius already got it to work although only via CLI. You might be able to compile it yourself. It's something that's also used in other Linux distro. I haven't tried it myself though because I'm lazy and the issue doesn't bother me enought yet

@wynn1212 Thank you for your detailed reply. I was using Ubuntu 24.04.2 with Kernel Linux 6.8.0-57-generic both on and old AMD desktop first then on a Windows Surface Laptop (running same Ubuntu version) with a USB2.0 to USB C cable. Next I tried a USB C to USB C cable on a Dell laptop (also running latest Ubuntu version) and after 2 or so attempts the flash was successful (not clear why). However today, I did the same procedure with another new FP4 using the Dell Laptop and USBCtoC cable and it again failed initially. When I connected the phone (already in fastboot mode) and restarted the bootloader from fastboot when installer was asking to manually switch the phone to fastboot, I was successful. This is quite frustrating because it still is not clear to me how to exactly reproduce this issue. It is definitely not the cable or the computer used. I agree this must be an interaction between the Ubuntu version and/or kernel and the phone. It almost looks like a timing issue, restarting bootloader at the right time lets the process go through. I could not test on Windows because I only have a work laptop running windows which does not allow starting non-certified appimages.

@AppLee No not yet Marius was working on it.

I had the same issue. The solution was simple. When i received the phone there was Android 13 on it. I had to downgrade to Android 11. Do this (yes all data will be lost) https://support.fairphone.com/hc/en-us/articles/18896094650513-Install-Fairphone-OS-manually an then ubports installer again with ubuntu touch Then mobile data works fine

@nicoladastra eSim is currently work in progress, but as Kugiigi mentioned it might work in some cases...

@Papa-Emeritux Not related with Android 11. I had the same issue with an UT device running Focal. I reflashed with Noble => Fingerprint didn't work. I flashed Android 13 without doing anything except turning on the developer mode. Then used the installer. Boom, the fingerprint worked. I guess flashing Android erase the registered fingerprints. And with preexisting fingerprints, a fresh installation of Ubuntu Touch does not work...

I made some tests. Data works perfectly with 3G (on the same phone). Definitively a problem with 4G and Free operator (France).

@stanwood well, thanks. Maybe the porters can do it within a new update. I don't want to risk to much. To use fastboot in linux is fine with me, but it should be safe. Otherwise its ok like it is and thanks to all (su)porters of the FP4, it's a nice device.

I was able to boot into bootloader by long pressing power + volume up buttons on the Fairphone. Afterwards UBports installer was able to find the device and install UT OTA-8. So everything runs fine again. Thanks so much

It's been awhile since I've used the installer, it surely has changed since then. Thanks for the hints.

@gandalf and at all, thanks for your informations and tips. I am using it now and works fine. I just need firefox sometimes, so battery drain is no problem for me.

@kugiigi said in is 5G already supported on Fairphone 4?: Even 4G is gone in your place? It depends on the operator. Sure there is one having solid coverage of any signal anywhere around, but it costs 4 times more. I don't miss the slow pre-5G access anyway.