UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. PhAndersson
    P
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 12
    • Posts 95
    • Groups 0

    PhAndersson

    @PhAndersson

    19
    Reputation
    21
    Profile views
    95
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    PhAndersson Unfollow Follow

    Best posts made by PhAndersson

    • UT installation on Google Pixel 3a (step-by-step)

      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.

      Android initial setup

      • 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:

          • enable USB debugging
          • allow OEM unlocking, enter PIN to confirm
      • turn phone off

      Dev. env. installation on linux PC

      • 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>
        

      Unlock bootloader

      • 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)

      Return phone to latest Android 9

      (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)

        • DO NOT interact with device during flashing
        • it reboots to fastboot
        • reselect device in Chrome
      • flash successful -- power cycle device

      • reboot to Android 9, redo initial setup, enable dev. mode, USB debug, connect and allow PC, turn phone off

      Flash phone with UbuntuTouch

      • 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:

          • select channel
            -> 20.04/stable
          • check "wipe personal data"
          • check "Flash system partitions using fastboot" (default)
          • click OK
        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

      posted in Google Pixel 3a/3a XL
      P
      PhAndersson
    • RE: Dual-SIM + OTA-20 on Mi A2

      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.

      posted in Xiaomi Mi A2
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @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).

      posted in App Development
      P
      PhAndersson
    • RE: UBports flashing failed half-way

      @stanwood Thanks a lot for the advice.

      posted in Google Pixel 3a/3a XL
      P
      PhAndersson
    • RE: Installer crash when clicking on "Choose file" button

      @alter Thinking back about the whole sequence, I'm a bit concerned that my first failed attempt at flashing UT (before adapting the udev rules) may have left the phone in an "unexpected" state, which in turn caused the 2nd flashing attempt to fail with these ominous error messages.

      It is perhaps best at this point that use TWRP again to put Android9 back on the phone (in both slots), make sure the phone is bootable again, and retry the whole 'ubports-installer' process again.

      posted in UBports Installer
      P
      PhAndersson
    • RE: Dual-SIM + OTA-20 on Mi A2

      Just upgraded to OTA-20: the upgrade process itself went flawlessly, but the SIM card in slot #1 is no longer detected!

      • during startup, I'm prompted for only one PIN code (the prompt no longer identifies the SIM, but the code only matches SIM #2)
      • in "settings | mobile", only one SIM and matching operator is listed (the one for SIM #2)
      • same thing in the top-of-screen quick access bar
      • "setting | about" reports OTA-20

      Is there any information I could collect on the phone to help troubleshoot this?

      posted in Xiaomi Mi A2
      P
      PhAndersson
    • RE: UBports flashing failed half-way

      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.

      posted in Google Pixel 3a/3a XL
      P
      PhAndersson
    • RE: Installer crash when clicking on "Choose file" button

      Problem has been resolved -- phone is now running UT OTA-19 stable.

      Details about the fix in the device-specific post (see URL in previous post). I'll now mark this one as resolved as well.

      Many thanks to all those who helped.

      posted in UBports Installer
      P
      PhAndersson
    • RE: Dual-SIM + OTA-20 on Mi A2

      @dpitti The device initially came with Android 8.1, but I flashed it with v9 as recommended before proceeding with the UT installation.

      posted in Xiaomi Mi A2
      P
      PhAndersson
    • Any way to push contacts to car kit?

      Hello again,
      I was able to pair my newly installed Pixel 3a with the car kit of my Skoda Octavia, and I'm glad to report that everything seems to be working:

      • I'm able to use the car sound system to listen to music played by the phone (selecting Bluetooth as source on the car Media Centre)
      • the car displays the phone's battery charge and GSM network strength
      • when an incoming call is received, the ringtone comes through the car sound system
      • I'm able to take the call from the dashboard and the voice goes through the car sound system as expected

      Now for the question: is there a tool that would allow me to push my contacts to the car kit over Bluetooth?

      Thanks in advance.

      Ph. A.

      posted in Google Pixel 3a/3a XL
      P
      PhAndersson

    Latest posts made by PhAndersson

    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):

      @PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):

      certain types of D-Bus requested are blocked by AA (such as AuthorizePush

      I have actually taken a look at the ubtd code and as I understand it AuthorizePush is a method defined by ubtd for obex.

      Correct -- it's still present in my current code.

      Looking at the Ubuntu touch bluez code with some dismay, it seems that this method is defined quite officially to allow the obex daemon to send data to a client, squarely fitting your use case, so why is there no apparmor policy for that ? As a wild guess, it looks like an oversight by Canonical that was forwarded by Ubuntu Touch - or even an oversight by Debian, forwarded by Canonical, forwarded by Ubuntu Touch. Maybe a bluetooth policy should exist.

      Well, there is a bluetooth policy group, and I used it. But it doesn't seem to cover that use case.

      Or maybe it already exists ? looking at usr.sbin.cupsd in my Kubuntu 24.04 installation, I see a string 'network bluetooth'. Maybe adding that to your apparmor profile could strike gold ? Absolutely wild guess of course ๐Ÿ˜‰

      If you refer to the network and bluetooth policy groups, I already use both (as you will see in one of my earlier posts), but that was not enough.

      If there is a way to extend an app AA profile past the predefined policy groups offered by the platform, I would be interested. Can you point me to a doc. that covers it? I already tried hacking the .apparmor file provided with my app, but clickable didn't seem to approve ๐Ÿ˜•

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):

      @projectmoon said in Trying to revive 'ubtd' (Bluetooth file transfer):

      I think any spawning of external processes that are not inside the app's ~/.local/share directory require unconfined.

      If 'running an external process' means 'activating a service' via dbusk, not 'spawning', it can be done from confined I think. I did not check how exactly is working this application.

      Yes, that was my experience as well. Even with an enforcing AA profile, my app was able to ask D-Bus to start the OBEX daemon if needed.

      Only certain types of D-Bus requested are blocked by AA (such as AuthorizePush -- see log extract in one of my posts above).

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @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).

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):

      @PhAndersson

      Great ! have happy file exchanges with your car ๐Ÿ™‚

      That won't work yet, unfortunately. For this, I need the SharePlugin to work. That one still crashes as soon as I select it which causes the phone to restart.

      More troubleshooting needed ๐Ÿ˜•

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      Well, good news! With the "unconfined" AA profile, the app works ๐Ÿ™‚

      The phone successfully received a .jpeg file sent over BT from my laptop:

      screenshot20260121_110443517.png

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):

      For now, I have only one positive thing to say: in the application that worked with 16.04, the template was set to 'unconfined'; while this is not generally a great idea, to advance your testing maybe it could be worth a try to add it to the apparmor profile ?

      Yes, you're right -- it's certainly worth a try.

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      OK, yet more updates.

      As already indicated above, my app now successfully registers with D-Bus/OBEX:

      [20/01/2026 13:50] Creating a QMirClientScreen now
      [20/01/2026 13:50] reply QDBusMessage(type=MethodReturn, service=":1.28", signature="", contents=([]) )
      [20/01/2026 13:50] creating agent on dbus
      [20/01/2026 13:50] registering agent
      [20/01/2026 13:50] discovering obex service
      [20/01/2026 13:50] OBEX service not found, attempting D-Bus activation
      [20/01/2026 13:50] OBEX service activated successfully
      [20/01/2026 13:50] found OBEX service at: "org.bluez.obex"
      [20/01/2026 13:50] registering agent on obexd-server
      [20/01/2026 13:50] Agent registered successfully
      [20/01/2026 13:50] have entries: (".", "..", "HubIncoming", "qmlcache", "qtshadercache-arm64-little_endian-lp64") "/home/phablet/.cache/ratatoskr.philipa"
      [20/01/2026 13:50] file:///usr/lib/aarch64-linux-gnu/qt5/qml/Lomiri/Components/1.3/Icon.qml:115:5: QML Image: Failed to get image from provider: image://theme/network-cellular-connected
      [20/01/2026 13:50] QObject::startTimer: Timers cannot be started from another thread
      [20/01/2026 13:52] file:///usr/lib/aarch64-linux-gnu/qt5/qml/Lomiri/Components/1.3/Icon.qml:115:5: QML Image: Failed to get image from provider: image://theme/network-cellular-connected
      [20/01/2026 13:52] file:///usr/lib/aarch64-linux-gnu/qt5/qml/Lomiri/Components/1.3/Icon.qml:115:5: QML Image: Failed to get image from provider: image://theme/network-cellular-connected
      [20/01/2026 13:52] qt.qpa.mirclient: Attempted to deliver an event to a non-existent window, ignoring.
      

      But when I start the app and try to push a file from the laptop to the phone over BT, obexd logs the following:

      [20/01/2026 13:50] OBEX daemon 5.64
      [20/01/2026 13:50] Excluding pcsuite
      [20/01/2026 13:50] Excluding ftp
      [20/01/2026 13:50] Excluding irmc
      [20/01/2026 13:50] Excluding mas
      [20/01/2026 13:51] CONNECT(0x0), <unknown>(0xff)
      [20/01/2026 13:51] CONNECT(0x0), <unknown>(0x0)
      [20/01/2026 13:51] PUT(0x2), <unknown>(0xff)
      [20/01/2026 13:51] Agent replied with an error: org.freedesktop.DBus.Error.AccessDenied, An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.107" (uid=32011 pid=4463 comm="/usr/lib/bluetooth/obexd -P ftp,irmc,mas,pcsuite -" label="unconfined") interface="org.bluez.obex.Agent1" member="AuthorizePush" error name="(unset)" requested_reply="0" destination=":1.106" (uid=32011 pid=4460 comm="ratatoskr " label="ratatoskr.philipa_ratatoskr_260120124119 (enforce)")
      [20/01/2026 13:51] PUT(0x2), Forbidden(0x43)
      [20/01/2026 13:51] DISCONNECT(0x1), <unknown>(0xff)
      [20/01/2026 13:51] DISCONNECT(0x1), Success(0x20)
      [20/01/2026 13:51] disconnected: Transport got disconnected
      

      Looking in journal, another message is found right before the error reported by obexd, this one issued by dbus-daemon (here copied from an earlier test run):

      Jan 15 16:44:14 hatshepsut dbus-daemon[2372]: apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/test/agent" interface="org.bluez.obex.Agent1" member="AuthorizePush" name=":1.94" mask="receive" pid=5216 label="ratatoskr.philipa_ratatoskr_260115153557" peer_pid=3539 peer_label="unconfined"
      

      Clearly, the IPC between obexd and the agent registered by my app seems to be blocked by AppArmor. This is the current AA profile for my app:

      {
          "policy_groups": [
              "bluetooth",
              "networking",
              "content_exchange",
              "content_exchange_source"
          ],
          "policy_version": 20.04
      }
      

      Can anyone tell me what could be missing?

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):

      @PhAndersson

      the other override is needed because of the specific 24.04 problem, you should not need it.

      OK -- thanks.

      Maybe all that is needed is to enable again the service.

      What's the result of

      systemctl --user status obex

      obex.service is still enabled -- here is the requested output:

      รขย—ย obex.service - Bluetooth OBEX service
           Loaded: loaded (/usr/lib/systemd/user/obex.service; enabled; vendor preset: enabled)
          Drop-In: /usr/lib/systemd/user/obex.service.d
                   รขย”ย”รขย”ย€ubuntu-touch-session.conf
           Active: inactive (dead)
      

      also, is there a symbolic link to the service under ~/.config/systemd/user/default.target.wants ?
      if not systemd will not start it.

      Well -- that's a good hint ๐Ÿ™‚

      As it turns out, the folder called ~/.config/systemd/user/default.target.wants does not exist at all. There is a folder called graphical-session.target.wants but the symlink is not there either. The symlink is created one level above, i.e. in ~/.config/systemd/user/. Here is the ls -l output:

      total 20
      lrwxrwxrwx 1 phablet phablet   34 Jan 15 10:50 dbus-org.bluez.obex.service -> /usr/lib/systemd/user/obex.service
      -rw-rw-r-- 1 phablet phablet  768 Oct  4 16:55 dekkod-notify.service
      -rw-rw-r-- 1 phablet phablet  716 Oct  4 16:55 dekkod.service
      drwxr-xr-x 2 phablet phablet 4096 Mar 27  2025 graphical-session.target.wants
      -rw-rw-r-- 1 phablet phablet  332 Mar 27  2025 osmscout-server.service
      -rw-rw-r-- 1 phablet phablet  174 Mar 27  2025 osmscout-server.socket
      

      By way of comparison, on my laptop running openSUSE Leap 15.6, the OBEX symlink is created in the exact same place (and obexd successfully starts when I log in), so I don't know whether or not it's enough to explain why the service fails to start on the phone.

      This being said, my app is now able to start obexd by itself if not running already, so that aspect has become less critical.

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
      EDIT: after some searching, and finding this github issue, I found the trick to add another override and after setting enable-linger for phablet with loginctl, the obex service is running after a restart.

      I just tried the enable-linger trick on 20.04:

      $ loginctl enable-linger
      

      then confirmed that it was set using

      $ loginctl user-status
      

      but after power-cycling the phone, the OBEX daemon still won't start automatically even though its unit file is still enabled.

      You mentioned "another override": was there something else to do?

      posted in App Development
      P
      PhAndersson
    • RE: Trying to revive 'ubtd' (Bluetooth file transfer)

      @gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):

      @PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):
      yeah, that's a 24.04 thing. Before Ubuntu was putting the executable under /usr/lib.

      I have filed an issue on gitlab.

      Splendid! Many thanks.

      posted in App Development
      P
      PhAndersson