I found a procedure online, restarting snapd, removing locks. That didn't work. Rebooted. Didn't fix it. Manually removed snap in home. Rebooed. Nope. I managed to install again and then remove it. That fixed it.

@kristatos maybe doing some more tests. I tried it again with my phone (FP5) setup with 24.04-1.3 stable and succeeded with receiving and sending test files. However I have reproduced some of your problems. Not the obex service not known. This was not happening for me. I have seen the disconnection of Bluetooth happening though. Strangely the Bluetooth page for the device (an Android phone) was displaying the device as connected BUT with no signal, then disconnected very soon after (may seem logical given there was no signal). I removed each phone from the Bluetooth configuration of both phones, tried again and this time the signal was rated 'excellent'. It then stayed connected. Needless to say, for all these tests the phones were sitting on a table very near of each other. It looks as if the state of connection is rated with 'no signal', it's staying so even if the real connection is good. In this case the pairing had been done much before and the phones had both been off or way to distant of each other to talk with Bluetooth. After solving this connection problem, I think another trouble may be that if a transfer is not acknowledged by the receiving end, all following transfers fail. Not sure but it looks like that. This problem was happening with a transfer UT -> Android. If my impression is correct, it may be a problem with the app (the connection problem mentioned before is probably more caused by the system bluetooth stack).

@Persinto since you want to use it as android phone, then any

@fischer.poco I noticed in your attempt to "fastboot oem unlock: that you received a message "Flashing Unlock is not allowed". Do you know what model of phone you have? (e.g. within OnePlus NORD N10 5G there are 4 BE2026, BE2028 (T-Mobile), BE2029 and a 4th one (MetroPCS) I can't remember the number). Basically, you need BE2026 or BE2029 to directly unlock the bootloader without OnePlus. If you have BE2028, you have to request the bootloader from OnePlus (which has been mixed, sometimes they give you the unlock token, sometimes they don't).

@Keneda Merci pour les réponses et l'information concernant le nom du système d'exploitation. Je dois effectivement être précis dans ce que je nomme. Je suis nouveau ici et cela m'intéresse vraiment d'apprendre au mieux. J'ai envisagé effectivement le Fairphone 5 mais : est-il nettement plus performant que le 4 pour la réception GSM ? il n'est plus commercialisé par Fairphone car c'est maintenant le 6 et d'après ce que j'ai vu, Ubuntu Touch n'est pas encore "installable" dessus. N'hésite pas à me dire si tu as des informations sur ces points. Encore un grand merci et à tout bientôt !

Hi, I find the app really useful, specially due to the daemon. I would really love video call functionallity. Is there any chance it will be added soonish? It's really the only thing keeping me on Waydroid's Whatsapp app at the moment. Thank you so much for working on this, keep it up!

@Moem Looks promising, It could be just what I need. Thank you!

@KoJans said: That worked in a few minutes outside. Glad to hear it!

Thanks for the hint. Yes, both work correctly. The physical volume buttons change the playback volume. The system volume slider (volume indicator) also changes the playback volume. Only QMediaPlayer::setVolume() has no audible effect, although the property itself changes correctly. So it looks like the backend ignores the player's volume while still using the system media volume.

@sambk Have you had any luck?

Those still requiring a token after converting to the global ROM, can you check if the boot loader image flashed? Maybe try flashing it manually. Ruben says it should be called LK.IMG Ruben thinks it might not have flashed, and reflashing it might unlock it without token.

@777X yea i am using localsend now and then, its a nice clean application if it works xD

as noted elsewhere for 24.04-2, unstable now can provide the OSK to XWayland apps such as Chromium-UT, Min, UWolf.

@Ida_ That's great news!!

I just went through 'journal' events (phone is now on 24.04-2.0 beta/RC) and found the following errors/warnings related to bluetooth: Jun 23 23:29:47 ubuntu-phablet bluebinder_post.sh[2815]: Failed to get bluetooth address! Jun 23 23:29:47 ubuntu-phablet bluetoothd[2861]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Unknown Command (0x01) [...] Jun 23 23:29:50 ubuntu-phablet systemd[2767]: bluez-mpris-proxy.service - BlueZ MPRIS proxy was skipped because of an unmet condition check (ConditionPathExists=!/usr/lib/systemd/user/mpris-proxy.service). It's unclear to me whether any of those can explain the BT connection issue with the laptop, but here they are.