@pparent I can imagine, that Alexander is quite experienced, and together you will find good solutions. If sombody else have ideas, I think is always good to hear and discuss them. I will ask Alexander if I can give you his emailadress.

said in Enabling MAC randomization: the problem is a bit random itself actually, it's a bit clearer now; when I enable wifi, I see the whole bunch of other wifi access points around my place; if I close settings and come back after some time (don't remember, maybe half an hour) and I open wifi settings again, I don't see anymore any other access points that the one I am connected to.

@Charly said in Call for testing: Ubuntu Touch 24.04-1.1: the micro SD card is still mounted read only. i'll try to find a micro sd card in the following days to check if it's just your phone or a general problem. In the mean time, if you can ssh to your phone and have some debugging practice, you could try to use journalctl --user -e -u ciborium and/or udisksctl (a command line utility) to check a bit on how things stand. Since I have never tried to do any test at all with a working and a non-working sd card on UT I'll not be able to help much in understanding these logs / reports, it's just that I know they exists. Ah, well, you did check the sd card on another device to see if it has not developed a fault at the same moment ? I know it's unlikely, but such things do happen.

@pparent I've plugged my phone on a monitor and leverage the Ubuntu Touch desktop mode (convergence) to have Signal UT and Waydroid side by side. Then you can take picture directly with your phone. The only thing a bit hard with this setup were that Waydroid scale with a big zoom. I had to update the LineageOS display setting to reduce UI to the smallest possible value.

@kugiigi said in [Question] getprop in a confined app?: based on physical measurement I think that this physicalDotsPerInch thingy could be affected by the idea that QT has about the physical size of the screen: using my first pyqt application: from PyQt5.QtWidgets import QApplication q=QApplication(['demo']) ls = q.screens() myscr=ls[0] print(f"name={myscr.name()}") print(f"logicalDotsPerInchX={myscr.logicalDotsPerInchX()}") print(f"logicalDotsPerInchY={myscr.logicalDotsPerInchY()}") print(f"physicalDotsPerInch={myscr.physicalDotsPerInch()}") print(f"physicalDotsPerInchX={myscr.physicalDotsPerInchX()}") print(f"physicalDotsPerInchY={myscr.physicalDotsPerInchY()}") print(f"physicalSize={myscr.physicalSize()}") print(f"size={myscr.size()}") print(f"devicePixelRatio={myscr.devicePixelRatio()}") print(f"depth={myscr.depth()}") print(f"virtualSize={myscr.virtualSize()}") print(f"geometry={myscr.geometry()}") I get: name=XWAYLAND0 logicalDotsPerInchX=96.25263157894736 logicalDotsPerInchY=96.05042016806723 physicalDotsPerInch=320.48931496290584 physicalDotsPerInchX=320.51134020618554 physicalDotsPerInchY=320.46728971962614 physicalSize=PyQt5.QtCore.QSizeF(97.0, 214.0) size=PyQt5.QtCore.QSize(1224, 2700) devicePixelRatio=1.0 depth=24 virtualSize=PyQt5.QtCore.QSize(1224, 2700) geometry=PyQt5.QtCore.QRect(0, 0, 1224, 2700) since for my FP5, the physical size of the screen is supposed to be 21.4cm, that is, 8.425 inches, this gives 2700/(21.4/2.54) = 320.4672897196262 and that's physicalDotsPerInch is reporting in my test with pyqt on my FP5. Maybe Volle phones are also misreporting the physical size of the screen ? Edit: I think I understand; I am using straight qt and pyqt that has no knowledge of mir, that's why it is using xcb: printenv returns QT_QPA_PLATFORM=ubuntumirclient;wayland-egl;ecb I'll search if there is a way to get a plugin to enable my pyqt for ubuntu touch maybe it could give better results. Edit 2: not found but I now doubt that there is a good way to fix it on the FP5, Internet gave me the useful tip to use an utility called 'mirout', and it reports to me: phablet@ubuntu-phablet:~$ mirout Connected to server: <default> Output 1: LVDS, connected, 1224x2700+0+0, enabled, on, 97mm x 214mm (9.3"), normal, 3.00x, unknown, phone 1224x2700 60.00*+ Output 2: DisplayPort, disconnected Output 3: Virtual, disconnected 1920x1080 60.00*+ so the problem is indeed with the phone, not the driver.

@ubuntoutou Unfortunately you will lose your data this way to get a usable device. Boot into the bootloader (fastboot) using the key combination from power off, if I remember it is volume down and power together. Fire up the installer on the pc and manually select the device and install UT. If you leave wipe data unticked you will still end up with the old passkey.

Update 18 November 2025 (2): Apologize for the mistake. We've published Ubuntu Touch 20.04 OTA-11 RC 2 to include a fix for sending SMS on some VoLTE-enabled devices.. The release date for Ubuntu Touch 20.04 OTA-11 is still 25 November 2025.

@bbiw I think it's feature for when you listen to music through external headphones and you disconnect them to stop playing music. It also happens on Android.

Team Gold to everyone involved in the transition to a fluid Noble. It is partly transparent but you should know that the number of problems to fix in all directions and requests to validate is immeasurable !