Hello fellow Ubuntistas,
I'm thinking about migrating myself to a "proper" UT device for a change,,,,,

...and I have some questions reg. FP5:

• Does it need to be unlocked in any way?
• What Android is required to be flashed in order to work properly with UT ?
  • Are there any specific Android images? Where to get those?
• Can this device be re-flashed between Adnroid and UT without a hassle? (I plan to use the device for both OSes kindof interchangeably...)
• Are there any caveats for using UT on FP5 as a daily driver? (I saw bad photo quality on some devices, hanging camera/ media recording/media playback, troubles with WiFi hotspots not working, ring tones disappearing after a period of time without reboots, etc etc...)

Thanks a lot for your comments

I understand that it's time-consuming—and often impossible—for developers to document what progress has been made.
But for “regular” users who are eagerly awaiting progress, it’s not easy to stay on board without such updates.
Perhaps the lead developers could at least publish a brief summary of the new features once a month.
This would also help demonstrate that Ubuntu Touch is making steady progress and is far from being abandoned.

I bought the official keyboard to the Volla Tablet. I have the German Keyboard Layout.
My system settings are on German language / german keyboard.
Nearly all keys are mapped correctly (The German z / y are correct, most German mappings of special keys above the numbers are correct.)

Yet there is one annoying fact:
On the keyboard markings it says that <, > and | are on the 3rd level (Alt-GR or right Alt key) of y, xresp. c.
But when I use right Alt + y, right Alt + x resp. right Alt + c the mapped keys are », « resp. ¢.
Other third level keys as µ, @ or € are working fine. There are more third level keys but I don't know their correct mapping.

This is a Volla Keyboard specific problem. My external bluetooth keyboard maps all keys correctly.

My guess is that this happens because there is the physical key missing on the smaller volla keyboard which is normally present in large keyboards for these three keys and the mapping automatically uses the next numbered key.

• Is there a temporary fix e.g. by remapping these keys?
• Shall I file a bug report somewhere or is this forum enought?

Thanks so far.

Some information, fwiw:

cat /proc/bus/input/devices

I: Bus=0019 Vendor=0001 Product=0001 Version=0001
N: Name="mtk-pmic-keys"
P: Phys=
S: Sysfs=/devices/platform/soc/10026000.pwrap/10026000.pwrap:mt6366/mtk-pmic-keys/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="mtk-kpd"
P: Phys=
S: Sysfs=/devices/platform/soc/10010000.kp/input/input1
U: Uniq=                                                                                                                                      
H: Handlers=kbd event1                                                                                                                        
B: PROP=0                                                                                                                                     
B: EV=3                                                                                                                                       
B: KEY=c000000000000 0                                                                                                                        
                                                                                                                                              
I: Bus=0000 Vendor=0000 Product=0000 Version=0000                                                                                             
N: Name="mtk-tpd"                                                                                                                             
P: Phys=                                                                                                                                      
S: Sysfs=/devices/virtual/input/input7                                                                                                        
U: Uniq=                                                                                                                                      
H: Handlers=kbd event7                                                                                                                        
B: PROP=2                                                                                                                                     
B: EV=b                                                                                                                                       
B: KEY=10 0 0 0 400 0 2000000 40000800 10004000000000 0
B: ABS=665800000000000

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="himax-stylus"
P: Phys=
S: Sysfs=/devices/virtual/input/input8
U: Uniq=
H: Handlers=event8 
B: PROP=2
B: EV=b
B: KEY=1c03 0 0 0 0 0
B: ABS=f000003

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="soc:odm:gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/soc/soc:odm/soc:odm:gpio-keys/input/input9
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="mt6789-mt6366 Headset Jack"
P: Phys=ALSA
S: Sysfs=/devices/platform/soc/soc:sound/sound/card0/input10
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=23
B: KEY=40 0 0 0 0 0 0 1000000000 c000000000000 0
B: SW=d4

I: Bus=0003 Vendor=258e Product=0066 Version=0111
N: Name="Volla Systeme GmbH"
P: Phys=usb-musb-hdrc-1.1/input0
S: Sysfs=/devices/platform/soc/mt_usb/musb-hdrc/usb2/2-1/2-1.1/2-1.1:1.0/0003:258E:0066.0007/input/input17
U: Uniq=
H: Handlers=sysrq kbd leds event2 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=258e Product=0066 Version=0111
N: Name="Volla Systeme GmbH Mouse"
P: Phys=usb-musb-hdrc-1.1/input1
S: Sysfs=/devices/platform/soc/mt_usb/musb-hdrc/usb2/2-1/2-1.1/2-1.1:1.1/0003:258E:0066.0008/input/input18
U: Uniq=
H: Handlers=event3 
B: PROP=0
B: EV=17
B: KEY=70000 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0003 Vendor=258e Product=0066 Version=0111
N: Name="Volla Systeme GmbH System Control"
P: Phys=usb-musb-hdrc-1.1/input1
S: Sysfs=/devices/platform/soc/mt_usb/musb-hdrc/usb2/2-1/2-1.1/2-1.1:1.1/0003:258E:0066.0008/input/input19
U: Uniq=
H: Handlers=kbd event4 
B: PROP=0
B: EV=13
B: KEY=c000 10000000000000 0
B: MSC=10

I: Bus=0003 Vendor=258e Product=0066 Version=0111
N: Name="Volla Systeme GmbH Consumer Control"
P: Phys=usb-musb-hdrc-1.1/input1
S: Sysfs=/devices/platform/soc/mt_usb/musb-hdrc/usb2/2-1/2-1.1/2-1.1:1.1/0003:258E:0066.0008/input/input20
U: Uniq=
H: Handlers=kbd event5 
B: PROP=0
B: EV=13
B: KEY=20000000000 0 0 1000302000000 3038d8011001 1e000000000000 0
B: MSC=10

I: Bus=0003 Vendor=258e Product=0066 Version=0111
N: Name="Volla Systeme GmbH Touchpad"
P: Phys=usb-musb-hdrc-1.1/input1
S: Sysfs=/devices/platform/soc/mt_usb/musb-hdrc/usb2/2-1/2-1.1/2-1.1:1.1/0003:258E:0066.0008/input/input21
U: Uniq=
H: Handlers=event6 
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

also there is the output of sudo snap run libinput.list-devices (after installing the snap package):

Device:           mtk-kpd
Kernel:           /dev/input/event1
Group:            1
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           mtk-pmic-keys
Kernel:           /dev/input/event0
Group:            2
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Volla Systeme GmbH
Kernel:           /dev/input/event2
Group:            3
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Volla Systeme GmbH Mouse
Kernel:           /dev/input/event3
Group:            3
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   button
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           Volla Systeme GmbH System Control
Kernel:           /dev/input/event4
Group:            3
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Volla Systeme GmbH Consumer Control
Kernel:           /dev/input/event5
Group:            3
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Volla Systeme GmbH Touchpad
Kernel:           /dev/input/event6
Group:            3
Seat:             seat0, default
Size:             96x51mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           soc:odm:gpio-keys
Kernel:           /dev/input/event9
Group:            4
Seat:             seat0, default
Capabilities:     switch
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           mt6789-mt6366 Headset Jack
Kernel:           /dev/input/event10
Group:            5
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           mtk-tpd
Kernel:           /dev/input/event7
Group:            6
Seat:             seat0, default
Capabilities:     keyboard touch 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      identity matrix
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           himax-stylus
Kernel:           /dev/input/event8
Group:            7
Seat:             seat0, default
Size:             80x128mm
Capabilities:     touch 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      identity matrix
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           ProtoArc XK01 Plus Keyboard
Kernel:           /dev/input/event11
Group:            8
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           ProtoArc XK01 Plus Consumer Control
Kernel:           /dev/input/event12
Group:            8
Seat:             seat0, default
Capabilities:     keyboard pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

as the title says i need some feedback about updating the toolkit ....i have a copy i updated it and i need to to do some things and get some verification on some things .....like i could take this code base and run any direction with it ....but that is not good for the many ....so lets talk about it

Habe versucht auf einen Xiaomi Note 9 Pro Ubuntu Touch zu installieren. Habt in einer dauert Schleife Rebooting Fastbootd und es funktioniert nur noch Fastboot Modus. Sonst geht nichts mehr. Kennt jemand eine Lösung?

Hi all! I recently got a hold of a second-hand FP4 for the sole purpose of testing out Linux-distros, and I'm starting out with Ubuntu Touch. I hope to first play around with it as a secondary phone (without a permanent SIM installed), but if it seems I would be able to daily drive it, I will attempt to do so for some weeks.

I have a couple of questions before I get started though, and was hoping these would be easy for you answer and help me get going:

1. It is stated I need to be on the Android 11-version of Fairphone OS in order to install it. The phone I got came with Android 15 installed, and before I proceed with downgrading to 11, I just wanted to confirm that this is in fact a requirement, and that it is not just a case of the instructions not having been updated since Fairphone has updated their OS.

2. On Fairphone's website, it is stated that I will brick my device if the security patch of the OS is behind whatever I have installed now (with Fairphone OS 15). Would going from Android 15 -> Android 11 -> Ubuntu Touch allow me to relock the bootloader?

3. 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.

Looking forward to trying this out.

Dear Moderators,

It appears that this forum has a flaw in the way it is moderated, and that this flaw is being exploited lastely.

Indeed, it is generally not allowed in a forum for a single individual to be able to in a few months to started ten or so threads on the same topic (with different titles).

Moreover, when this approach is intended to ensure that their negative views on the Ubuntu Touch project remain prominently displayed (and naively discussed) at the top of the forum to maximize visibility.

By trying too hard to be accommodating and open to discussion, we end up enabling and encouraging this abusive behavior.

I hope moderation can be improved to curb this problem.
(In the meantime, everyone can help by staying alert and following these guidelines:
https://forums.ubports.com/topic/12121/warning-about-a-sneaky-spamming-method-in-this-forum-and-how-to-detect-and-counter-it)

With full respect for your work and engagement

Libremax

I tried Waydroid on a VollaPhone22 (Focal) after some years, so please be patient. How can I get Internet connectivity inside Waydroid (probably sharing the one from Ubuntu)?

So I recently bought Pixel 3a to try the waters of Linux mobile. I installed UT first, but I wanted to try others as well so later installed postmarket OS. While I liked it, UT functioned bettet so got back to it. That's when the issues began.

Now when I restart, it sometimes reboot but usually just shuts down. When it reboots (or I boot it up) it gets stuck in a loop:

Boot -> google splash screen -> UT splash screen (rarely it doesn't even reach it and reboots after google screen) -> freezes (sometimes I get white screen or just flashes of white screen) - reboot - repeat.

This gets way worse with Libertine set up - it goes through after a number of cycles, then just gives up and finally doesn't reboot and stays shut down. And when I have a package installed in Libertine (tried with Firefox) it feels like it gets worse still and I'm unable to get to login at all.

Rebooting through recovery mode usually gets the device to fully boot up successfully. Did factory reset and also tried flashing UT again, issues persist.

Not sure if relevant, but when I was flashing UT the second time around, the installer didn't register the device automatically, had to select manually.

Weird thing is it worked fine the first time - but after I tried postmarketOS and went back again is when the trouble started. Not sure what I could've done wrong though and no idea how to troubleshoot. I'm pretty new to Linux, very much on a regular user level.

the home folder is a easy place to navigate to when trying to do thing with files however UT does not permit this ....for example to make a competent archival tool for UT i cannot simply make a directory tree to navigate files select or create or extract archives ....i can in the apps sandbox space but this isnt useful so my only option is to use contenthub to pass file from their location to the apps sandbox do file operation then put them back ...you see what i mean? .....its like i had a leg cut off and now im expected to run a marathon ....lol metaphorically speaking ..this is a major roadblock for development ...i can work around it but its awkward overly convoluted to do simple task .....im simply asking for a "workspace" folder in the home directory that behaves normally so when i port like a million apps to UT i simply need to point to that location not refactor the way the whole program works simply why again? ....its basically secure to the point of non operational ability ...i get and love the secureness of UT .....im not like mad or anything now but like i have the most awesome file archiver for UT ...cant use it and i had to refactor it into something i dont want to use .......idk i think this is what im asking for? ...can someone please make me understand why we are holding such a hard line on something so ....makes things damn harder than they need to be ......or am i just wrong ....be patient changes are in the works? i know they are .........hands in the air i have been banging my head on code on this for like 23 hours straight ...i ask AI ...AI:"yeah my hands are tied" ....throws keyboard** ....someone please therapy me on this lol

Hello

I'm pleased to announce I've published muttum for Lomiri today:

https://next.open-store.io/app/org.muttum.muttum-lomi/

The player has 6 attempts to retrieve a word from a dictionary. Currently the game contains 3 dictionaries: english, german and french.

If you know a dictionary for your language I can add it in next versions. The requirement is to have a plain text file with one word by line.

Some notes:

• About the NSFW tag: the end game screen contains a link to the Wiktionary page of the solution. As I do not filter/censor list of playable words, this link can target a page with violent content or explicit image.
• muttum is also available for the GNOME desktop (I made it last year) and it shares the same game engine and translations. The Lomiri version has the advantage to be responsive as the Ubuntu Touch toolkit is made for easy convergence.
• For the application id, I built it with the reversed DNS of the project website (muttum.org). As I already used the "org.muttum.muttum" id for the GNOME version, I wanted to use "org.muttum.muttum-lomiri", so you can install both version. As the Open Store disallows application ids to contain words "lomiri" and "ubports", I shortened the id with "org.muttum.muttum-lomi".

Hi, im come back to UBports after install stock rom and i have bootloop in my device, when i try remove that word in cmdline finally it works (stuck at initrd failed)

how i can do for get that work back!?

ubports.com membership-registration not working - no error messages - no response - nothing

My camera has stopped working. I don't know if this was an update or a device malfunction. Anyone else have this issue?
App loads,shows normal screen for 1/2 second, tries to start but crashes immediately.

Poco X3 NFC
24.04-1(2026-03-19)

apache2 is not installing as far as I can tell. I have developed an entertainment website - home server - that I would like to put on the device to watch movies and listen to music on a memory stick.

Thanks

PS: separately - suggest you check the meaning in French for 'Libertine'.

I cannot see the last digits of the clock time. It looks like the screen is not considering the corners curves of the physical screen. Any idea how to fix this? Thanks

In an effort to streamline information across all the sources I am working on updating device listings on the official ubuntu touch website first. I would firstly like to know from people who are running Noble on devices which are otherwise not listed with it on the main website (for eg: Pixel 3a / 3a xl). It would also be appreciated if you list any changes (things that stopped working / started working / changed in behaviour after updating).

• xcx

Hello, how to lock again the boot loader to stop viewing the warning message? Where to go in UT to do this? Thank you

Hello

I'm trying to revive the 'ubtd' app (Bluetooth file transfer) initially written by Michael Zanetti and Ian L., but I've hit a roadblock and I could use some guidance.

I'm currently targetting UT 20.04 on a Pixel 3a.

By default, the OBEX daemon doesn't run on the phone. A 'systemd' unit file is supposed to start it (/usr/lib/systemd/user/dbus-org.bluez.obex.service), but it is reported as "loaded / inactive (dead)" by 'systemctl' -- I'm not sure why as I was unable to find relevant log entries.

I can manually start the OBEX daemon using the following command:

$ systemctl --user start obex.service

In this case, the 'obexd' daemon keeps running and uses the same command-line parameters as those specified for the D-Bus related service (obexd -P ftp,irmc,mas,pcsuite -r /home/phablet).

Nonetheless, after pairing the phone with my laptop, when I start my app (the one that is supposed to receive incoming file transfers), I see the following messages in its log:

[03/01/2026 12:25] creating agent on dbus
[03/01/2026 12:25] registering agent
[03/01/2026 12:25] registering agent on obexd-server
[03/01/2026 12:25] Error registering agent for the default adapter: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.bluez.obex was not provided by any .service files")

For information, the obex.service unit file does expose "org.bluez.obex" as BusName, not as Name -- not sure how relevant that is.

On its side, the OBEX daemon logs the following:

[03/01/2026 12:25] CONNECT(0x0), <unknown>(0xff)
[03/01/2026 12:25] CONNECT(0x0), <unknown>(0x0)
[03/01/2026 12:25] PUT(0x2), <unknown>(0xff)
[03/01/2026 12:25] PUT(0x2), Forbidden(0x43)
[03/01/2026 12:25] DISCONNECT(0x1), <unknown>(0xff)
[03/01/2026 12:25] DISCONNECT(0x1), Success(0x20)
[03/01/2026 12:25] disconnected: Transport got disconnected

So 'obexd' seems to receive the file sent by the laptop (from the point of view of the laptop, the transfer succeeds), but fails to hand it over to my app, which I guess makes sense as it failed to register itself with the daemon.

Can anyone suggest a fix, further ways to troubleshoot or point me to relevant documentation?

Thanks in advance.

Today is Ubuntu Touch Q&A Day

Ubuntu Touch Q&A186 is today at 19:00 UTC please join us on YouTube: https://www.youtube.com/watch?v=QlcfHVeRRf0

Questions can still be posted here https://forums.ubports.com/topic/12083/ubuntu-touch-q-a-186-call-for-questions for priority or live in the show.

UBports@telegram
#ubports:matrix.org

#UBports #UbuntuTouch #UBportsQandA #Lomiri #OTA12 #Ubuntu #UTnoble #MobileLinux