Never reply to these topics or messages
this is the standard advice, don't feed the troll. Unfortunately, either there is an university for trolls or they are always reinventing the counter-measure, they are replying to themselves using another alias to fake a real discussion so there is a silver bullet for vampires but none for trolls 
I have a FP5 and the 2FA app you are talking about installs without problem. Maybe it's because I'm on stable while by using daily you are exposing yourself to any fleeting update bug.
The usual cause of this problem is network error. Try to download the click by hand using Morph QT6 browser and visiting open-store.io.
If you can't download it, either your network is blocking somehow or your install is hosed (I have already warned you against this possibility, I'm still not convinced by your counter-arguments...)
If you can, navigate to the resulting file and try to install it from there using the store app.
complaints about UT not upstreaming
that's exactly that, the talking electric heater is used to put in form and make convincing prejudices. Upstreaming is good yes ? actually that's the case when what you are upstreaming is of general use.
If UT developers are stumbling into bugs in linux or systemd and they are sending fixes, that's of general use.
When PostmarketOS are writing drivers for hardware that is specific to phones, it would be of general use if there was a thriving market for linux phones. That's the prejudice I am talking about; it supposes existing something that is plainly non existent. In the mean time, drivers for these specific devices are coming when this hardware is usually no longer in use and these ten of thousands of lines of code are just loading work for the linux kernel team, useless for everyone in the linux market but PostmarketOS.
However when you are using a talking electric heater, this kind of thingy is really good at counting, especially big numbers, and the ten of thousands of lines of mostly useless drivers are litteraly drowning the small contributions of UT developers and so encode the prejudice of the person writing this trolling garbage.
That's what it is: a troll. Linking this troll into other unrelated posts leaves no doubt. Talking electric heaters have many uses, including helping writing better trolls. Thanks for this troll, it has helped me to understand the true risks of using talking electric heaters, like all tools they can be misused, language can be used to communicate but also to destroy and in bad hands language can be as dangerous as a hammer.
It is stated I need to be on the Android 11-version of Fairphone OS in order to install it.
yes it's the case. A port needs resources and updating it to accommodate any kind of Android version installed on the phone would be too much at the moment, so there is only one supported.
Would going from Android 15 -> Android 11 -> Ubuntu Touch allow me to relock the bootloader?
no you need to keep it unlocked. There are only a few phones where relocking is supported and Fairphone ones are not among these devices.
There's a lot of emphasis on proper data cables, and I've had issues with this before when installing custom ROMs. Is there a way to test the cable beforehand? Am I at risk of bricking the device if I use a bad cable? When I previously had issues, the flashing would just be unable to finish properly, but no harm was done, and I could retry with another cable.
I have done just that (using a bad cable) and I was able to restart it with a better one. As far as I know there is no sure way to test for that, most I can say is you get what you pay for, if you grab an old cable from the bottom of a drawer you are risking more than if you buy a certified cable from a known seller. From my previous bad experience, the seller had 2 qualities and I bought the more expensive one, that looked more 'qualitative' (less slim). This said more expensive meant actually 10 euros for 50cm instead of 5 euros for the less expensive one so I did not break the bank.
archival tool for UT
security implications.
Any backup tool has security implications, to backup secret information you have to be able to read it in the first place. So I'd expect that backup tools would need special warning from the store, you need some trusted person to read the code and ensure that it is not exporting the data it is able to read it to some unwanted place.
cursor keys:
option 1: use the hamburger menu and select scr, then scroll to the right you'll find arrows
option 2: touch the screen, press and move gently your finger right/left
yes that's it.
@domubpkm
you can add the fix even on stable with a systemd overlay file.
phablet@ubuntu-phablet:~$ systemctl --user cat obex
# /usr/lib/systemd/user/obex.service
[Unit]
Description=Bluetooth OBEX service
[Service]
Type=dbus
BusName=org.bluez.obex
ExecStart=/usr/libexec/bluetooth/obexd
[Install]
Alias=dbus-org.bluez.obex.service
# /usr/lib/systemd/user/obex.service.d/ubuntu-touch-session.conf
[Service]
ExecStart=
ExecStart=/usr/lib/bluetooth/obexd -P ftp,irmc,mas,pcsuite -r $HOME
# /home/phablet/.config/systemd/user/obex.service.d/xxoverride.conf
[Service]
ExecStart=
ExecStart=/usr/libexec/bluetooth/obexd -P ftp,irmc,mas,pcsuite -r $HOME
after adding the overlay, you have to restart the obex service using systemctl --user restart obex
reinstall UT (2 or 3 retries)
The point is that it is not normal to retry an installation. If your hardware is good, it should work the first time or never.
or your app was added to a white list. Such a thing exists for sure since Morph QT6 was accepted and your app was rejected at first.
you don't. This is a known way to brick your phone.
this is a known problem. There is a merge request on gitlab about that that is staying unattended since quite some time now.
USB cable, if that was the case, when installing, i guess it decompress the files. If they were corrupted, it will not work.
yet what you described was exactly this happening: installing did go to the finish without reporting an error, but wifi was not working; and after retrying, wifi and cellular happened to work.
rethinking about your problems in flashing UT to your phone, I wonder if you could have hardware problems, or possibly either flashing with a flaky USB cable, or with an unsufficiently charged battery.
I don't know what is the trick since I never had this problem, and as far as I know you are the first person to report it on this forum.
When you press the button, does the screen turn briefly black and is there a sound ? if you scroll the screeb to the left to the photo roll features, do you see results ?
what I gathered from the UT Q&A is that there is no fundamental issue with QT6 for Lomiri, it's only that for compatibility reasons it's necessary to support both QT5 and 6 for tuture versions and it's not possible without extending the rootfs for many phones and it's not easy to manage.
For now QT6 is only used with the UT browser morph and it's done by shipping the QT6 libraries via the store, outside of the rootfs. However it is currently not supported without specific authorization from the store.
shipping QT6 with a click will be blocked by the store at the moment, it needs explicit authorization.
I have no such hardware to try to repro it, but there are issues on gitlab about such problems.
Try this workaround , maybe it will work for you.
Err, where did you get a 'new' FP5 with Android 13 ? I bought mine 6 months ago and it came with Android 14.
I duly downgraded it to 13 as, well, every post in the thread you are adding this post states clearly, and Wifi and cellular both work.
can you browse next.open-store.io ?
can you ping open-store.io from the UT terminal ? if not, what's the output ?
you don't say which version of Ubuntu Touch you use.
It has been reported that last update to 24.04-1.2 broke something in USB mode changing, maybe your problem could be related ? @slowcyclist