Another quick update.
I'm really pleased to announce that I got the SharePlugin part of the app working as well. I successfully pushed a file from my Pixel 3a to my (Linux) laptop over BT, but even more importantly for me, I was able to push selected contacts to my car kit 
The user interface is still too rough for the app to be published as is (at this stage, you have to select the target device based on its MAC address, which is far from convenient), but I'm working on it.
The present post does not contain any question. When I flashed my first phone with UT four years ago, I struggled a bit to gather all relevant information, so I'm offering the below procedure to the community in the hope that it may ease the journey of first-time users.
Disclaimer: this is a description of what worked for me. Use at your own risk. Flashing is performed from a PC installed with openSUSE Leap 15.6 -- some commands may need to be adapted if you use a different distro.
Important: if flashing the phone with either Android Flash Tool or the flash-all.sh script hangs / fails to detect the phone, DO try from a different PC if you can (I have a Lenovo laptop and a custom-built PC both installed with openSUSE Leap 15.6: I was never able to flash from the laptop, while the PC worked like a charm). It may also be worth trying different USB cables / USB ports.
Note: in the steps below, '#' denote commands that are executed as root, '$' denote commands that are executed as a regular user.
unbox and fully charge phone (do not turn on yet)
insert SIM, turn phone on
select language (English UK)
click Get Started
connect to WiFi (provide credentials)
-> "getting your phone ready..."
"Copy apps & data" -> select "Don't copy"
Google account sign-in -> login
Accept conditions
set a PIN
Continue setup or get reminder -> get reminder
Unselect all optional apps
Settings -> System -> Updates
(Android 12, build SP2A.220505.008)
Settings -> About Phone
tap "Build number" 7 times, enter PIN to confirm
-> "you are now a developer"
Settings -> System -> Developer Options:
turn phone off
unzip 'platform-tools' archive below ~/platform-tools/
edit ~/.bashrc to add ${HOME}/platform-tools to your PATH
install (update) 'android-udev-rules' package from build service
# zypper addrepo https://download.opensuse.org/repositories/hardware/15.6/hardware.repo
# zypper refresh
# zypper install android-udev-rules-20250314-lp156.51.1.noarch
(this also installs adb and fastboot by way of dependencies)
add your own user account to 'adbusers' group:
# usermod -aG adbusers <userID>
(logout/login)
# grep adb /etc/group
adbusers:x:453:<userID>
turn phone on (regular mode). Unlock it
plug phone into PC
ADB connection detected by phone. Check box to always allow connection from PC (allow PC's RSA key fingerprint on device):
$ adb devices -l
List of devices attached
XXXXXXXXXX device usb:1-6 product:sargo model:Pixel_3a device:sargo transport_id:1
turn phone off
boot into Fastboot Mode
(volume down + power -- hold for 5")
Fastboot menu appears
$ fastboot devices -l
XXXXXXXXXX fastboot usb:1-6
unlock bootloader
$ fastboot flashing unlock
OKAY [ 0.133s]
Finished. Total time: 0.133s
phone screen prompts: do not unlock / unlock
(use volume keys to select, power button to confirm)
-> bootloader confirmed unlocked
turn phone off (use volume button to select option, power button to confirm)
(the steps below refer to the Android Flash Tool -- using the flash-all.sh script also works fine but starts with the phone booted into the bootloader)
check that 'adb' is not running
(otherwise, stop it with 'adb kill-server')
turn phone on the usual way
redo basic setup, as bootloader unlock returned it to factory default (see above)
reconnect to phone using 'adb devices' to get prompt to authorized PC and allow it
visit following URL in Chrome (authorise pop-ups in browser):
https://flash.android.com/
select device
select target build (PQ3B.190801.002)
DO NOT select to relock bootloader
click Install Build (confirm, accept license)
flash successful -- power cycle device
reboot to Android 9, redo initial setup, enable dev. mode, USB debug, connect and allow PC, turn phone off
install 'snapd' daemon
# zypper addrepo https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.6/ Snappy
# zypper refresh
# zypper in snapd
# systemctl enable snapd.apparmor.service
# systemctl start snapd.apparmor.service
# systemctl enable snapd.service
# systemctl start snapd.service
reboot
install UBports installer
# snap install ubports-installer
$ which ubports-installer
/snap/bin/ubports-installer
$ snap info ubports-installer
name: ubports-installer
summary: The easy way to install Ubuntu Touch on UBports devices.
publisher: UBports
store-url: https://snapcraft.io/ubports-installer
contact: https://github.com/ubports/ubports-installer/issues/new
license: GPL-3.0
description: |
A friendly cross-platform Installer for Ubuntu Touch. Just connect a
supported device to your PC, follow the on-screen instructions and watch
this awesome tool do all the rest.
commands:
- ubports-installer
snap-id: mq0sTMV7a8744UTRBwQHimStAqsGzbjj
tracking: latest/stable
refresh-date: 2022-09-11
channels:
latest/stable: 0.9.7-beta 2022-09-11 (435) 97MB -
latest/candidate: ?
latest/beta: 0.9.8-beta 2022-11-02 (445) 102MB -
latest/edge: 0.10.0 2023-04-23 (462) 103MB -
installed: 0.9.7-beta (435) 97MB -
switch ubports-installer to "edge" channel
$ snap refresh ubports-installer --edge
ubports-installer (edge) 0.10.0 from UBports refreshed
$ snap info ubports-installer
name: ubports-installer
summary: The easy way to install Ubuntu Touch on UBports devices.
publisher: UBports
store-url: https://snapcraft.io/ubports-installer
contact: https://github.com/ubports/ubports-installer/issues/new
license: GPL-3.0
description: |
A friendly cross-platform Installer for Ubuntu Touch. Just connect a
supported device to your PC, follow the on-screen instructions and watch
this awesome tool do all the rest.
commands:
- ubports-installer
snap-id: mq0sTMV7a8744UTRBwQHimStAqsGzbjj
tracking: latest/edge
refresh-date: today at 13:47 CET
channels:
latest/stable: 0.9.7-beta 2022-09-11 (435) 97MB -
latest/candidate: ?
latest/beta: 0.9.8-beta 2022-11-02 (445) 102MB -
latest/edge: 0.10.0 2023-04-23 (462) 103MB -
installed: 0.10.0 (462) 103MB -
start ubports-installer
$ ubports-installer
Gtk-Message: 19:40:25.179: Failed to load module "window-decorations-gtk-module"
Gtk-Message: 19:40:25.179: Failed to load module "colorreload-gtk-module"
info: Welcome to the UBports Installer version 0.10.0!
connect phone (off) via USB
click select device manually
-> Google Pixel 3a:3a XL
click "My device is unlocked"
select OS
-> Ubuntu Touch
click Install
Installation options:
info: device selected: sargo
info: Installing Ubuntu Touch on your Google Pixel 3a/3a XL (sargo)
info: configuring...
info: settings: {"bootstrap":true,"wipe":true,"channel":"20.04/arm64/android9plus/stable"}
info: Downloading 3 files
info: Downloaded file 1 of 3
info: Downloaded file 2 of 3
info: Downloaded file 3 of 3
boot phone to bootloader, click Continue
(flashing firmware)
boot to recovery, click Continue
(if button fails, try adb reboot recovery)
=> shows 3-circles recovery logo and menu
info: Downloading 12 files
info: Downloaded file 1 of 12
info: Downloaded file 2 of 12
info: Downloaded file 3 of 12
info: Downloaded file 4 of 12
info: Downloaded file 5 of 12
info: Downloaded file 6 of 12
info: Downloaded file 7 of 12
info: Downloaded file 8 of 12
info: Downloaded file 9 of 12
info: Downloaded file 10 of 12
info: Downloaded file 11 of 12
info: Downloaded file 12 of 12
info: All done! Your device will now reboot and complete the installation. Enjoy exploring Ubuntu Touch!
(pushing files to phone)
phone reboots at the end
=> goes to longish 3-circles recovery logo animation while installing (may last a few minutes -- have patience)
phone reboots again
=> this time it boots to UT and asks you to perform the initial setup
Status update:
As it happens, I took the opportunity of having the phone on the dev channel to re-test an application that typically froze the GUI (the app called "Steps" -- I already opened a bug report on that specific issue). Turns out the behaviour was the same on v763, so I wanted to force a power cycle by rebooting the phone on the recovery image (Power + Vol+).
But instead of the recovery menu, I was greeted by the spiralling animation: the phone was clearly installing something. When it finished rebooting, I was back on OTA-20, and both SIMs were still active!
Following @DPITTI suggestion, I also removed v763 from the upgrade history.
I'll now mark this post as "resolved". Many thanks to all those who contributed.
@gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
how about setting up a public directory of what you have (if you have cleared the license question) ? It'll allow me to test it under Noble and possibly send a MR to gitlab once I'm sure that it works.
Done. I've created the GitHub project, pushed my repo and tagged it v0.1.0. You can get the code here:
https://github.com/petroniusniger/ratatoskr
The README file contains instructions on how to build (build.sh is a wrapper around clickable that I needed in order to get version strings based on git tags).
I'll now start submitting the app on the OpenStore and create GitHub issues with the open items in my roadmap.
Status update:
'ratatoskr' source code has just been reviewed by @bhdouglass (OpenStore team), and two issues have been identified that should be resolved before allowing publication of the .click packages:
I'll work on resolving those 2 issues and release a v0.1.1 of the code before re-submitting it for publication.
Just upgraded to OTA-20: the upgrade process itself went flawlessly, but the SIM card in slot #1 is no longer detected!
Is there any information I could collect on the phone to help troubleshoot this?
@stanwood Thanks a lot for the advice.
@lduboeuf said in Trying to revive 'ubtd' (Bluetooth file transfer):
Congrats, So some changes are needed on UT to make it work ?
If your question is: did I need to hack my phone to make the app work in its current state, then the answer is no. As suggested by @gpatel-fr, I just gave it an "unconfined" AA profile (which I understand would prevent me from publishing it on the OpenStore).
So eventually an updated bluetooth AppArmor Policy Group would be needed, I guess (or a extra one dedicated to OBEX).
@dpitti The device initially came with Android 8.1, but I flashed it with v9 as recommended before proceeding with the UT installation.
I just installed the phone with UBP-installer v0.10.0 -- everything went like a charm this time round.
Many thanks to both of you for your support.
Status update:
'ratatoskr' source code has just been reviewed by @bhdouglass (OpenStore team), and two issues have been identified that should be resolved before allowing publication of the .click packages:
I'll work on resolving those 2 issues and release a v0.1.1 of the code before re-submitting it for publication.
@projectmoon said in Hardware recommendation for Noble:
Volla Quintus has served me well so far. It's also one of the only devices that is officially commercially supported for UT. Volla has someone working on UT for their devices.
Many thanks -- I'll give it a look. I guess flashing my first 2 phones with fastboot and adb earned me a few nerd points, but I won't complain either if the next one comes pre-installed 
@MrT10001 said in Hardware recommendation for Noble:
The Google Pixel 3a is a good device, but unfortunately lacks the VoLTE support
Indeed -- the support for that device is excellent overall. I'm very happy with it. It's just a pity that the HW specs are a bit basic.
For me and this is what you will get as everyones experience varies the devices I recommend are OP5 and OP5T, Nord N100 and Nord N10 5G, Xiaomi Redmi Note 9 Pro and Xiaomi POCO X3 NFC...
OK, thanks -- I'll have a look at those.
Anything device that has worked with Focal should clean install to Noble with a few exceptions (OP6 and OP6T and Xiaomi Mi A2).
You surprise me -- I thought the Mi A2 was never ported to Focal. I have one, but it's still on Xenial.
Hello everyone,
I'm currently using Focal on a Google Pixel 3a as daily driver, and I would prefer to wait a bit before upgrading it to Noble. But I would also like to start porting an app I'm writing to the latest UT platform.
Could you please tell me which phone would provide the best user experience (considering a scenario where it would be imaged with Noble straight away, not upgraded from Focal, and use the latest available version, not /stable)?
Side question: do we still need to start from Android 9 before installing Noble?
Thanks in advance for any recommendation.
@paulcarroty said in Trying to revive 'ubtd' (Bluetooth file transfer):
@PhAndersson there's active OpenStore matrix room.
Many thanks -- I just joined it.
@gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
as they say in open source, 'unfortunately' the MR was backported to the 24.04-1.x too late to be included in the 24.04-1.2 version
. That means that your app will not work at all in this version unless some system fiddling is done by the user.
So this means waiting for 24.04-2/stable, I guess...
@arubislander said in Trying to revive 'ubtd' (Bluetooth file transfer):
@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):
it says the official Android or iOS app is required to do this, which I don't have access to
I have heard Telegram works on Waydroid, fwiw.
Thanks for the tip -- I'll give it a look.
I've hit a snag. I'm supposed to contact the review team on Telegram to try and get my app approved for publication on the OpenStore, but it seems I can't create a Telegram account through the UT Teleports app -- it says the official Android or iOS app is required to do this, which I don't have access to.
I'll try to contact 'bhdouglass' via the forum instead.
@gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
Anyway, I tried to regenerate the click without the unconfined template. Now, the confined app can send files to the Android phone without problem at all. It's in the other direction that I get an authorization error:
Yes, I'm aware of this -- I already reported this higher up in this thread. The SharePlugin works fine with a confined AppArmor profile. It's only the main app that needs wider rights to interact with D-Bus / OBEX.
Now I don't think anymore that it's a matter of setting the system to grant the authorization. You see, in the other direction on the Android phone I get a prompt to authorize the transfer. The UT phone can't simply push files to the Android phone without any user interaction.
And I think that this should be the fix: that somehow the UT user (phablet) get a prompt to grant the other system the (temporary) right to write the file to the UT destination.
Having a prompt for the user to accept the incoming transfer is indeed needed (and already tracked through issue #6), but I don't see this as related to the fact that a confined AA profile prevents the app from issuing the "AuthorizePush" message.
This clearly needs further investigation.
@gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
note that the idea of using BT sharing instead of BT plugin is a suggestion, I think (personal opinion) it's better than 'BT plugin', but it's not necessary the best idea.
Understood -- I created the issue to make sure it doesn't slip my mind. If better suggestions are offered, they are welcome!
Also reading them reminds me that I could take a look at the confined problem. This said, it seems that the mere fact of using 'bluetooth' makes this application something to be vetted, even if it's confined.
Correct.
I don't know why, given that unrestricted applications can access Internet and (I think) the local network, it seems to me to be a risk even greater than bluetooth
In theory, unconfined applications are simply forbidden, as they could do almost anything (that the user they run as could do). I'll try to contact the review team on Telegram to get the review process started. Without that, I can't distribute the .click packages on the OpenStore.