@projectmoon said: what is the way to undo this? update urls set domainsuffix=null where domainsuffix='nothing.org';

OK, found the solution on 'WayDroid on Ubuntu Touch' Telegram group channel Thanks "aleasto" for sharing this solution. Start WayDroid session (by either taping "WayDroid" in launcher or waydroid session start in terminal) When WayDroid session loads, open Terminal on Ubuntu Touch Run the following commands (I think the first prop should be fine, but just in case, I set those 2 props) $ waydroid prop set persist.waydroid.cursor_on_subsurface true $ waydroid prop set persist.waydroid.cursor_force_shm true Restart the WayDroid session to apply prop changes. (By either tapping "Waydroid Stop" then "Waydroid" in launcher or waydroid session stop then waydroid session start in terminal) And from now, hovering mouse cursor to Waydroid window will no longer crashes the Waydroid window. And enabling Show taps on developer options no longer crashes Waydroid window but the taps no longer shows when touches.

I had to install back a second time Android on my Fairphone 4, this time I've took some notes shared below. TLDR: LineageOS developer options pane allows you to enable Rooted debugging. This allows you to use the adb root command which start a rooted debugging session. Then you can use adb shell to open a console on the device and run restorecon -FR /mnt/vendor/persist to restore the SELinux permissions. From Ubuntu Touch, the easiest way to go to the fastboot mode, is to open the terminal application and run: sudo reboot -f bootloader Then, I used the Android 11 factory reset image provided by Fairphone (but don't do like me, see below). Then, I wanted to install LineageOS and they require to have Android 13/15. So, I opened Android 11, go to phone information in the settings application, repeatedly touch the build number until the developer mode is enabled. Go, to the system panel in the settings application, open the developer mode and enable the ADB debugging. On my computer, I go back to the fastboot mode with: adb reboot bootloader I've installed Android 13 factory reset image provided by Fairphone as I already have downloaded it for another experiment. Then I boot Android 13 and enabled usb debugging with same steps than Android 11 (see above). Then I've followed LineageOS instructions to install it step by step: https://wiki.lineageos.org/devices/FP4/install/ Then, with LineageOS, you can enable developer options with same procedure. The LineageOS developer options have two options: USB debugging and Rooted debugging, you need the last one to be able to run commands to reset correctly permissions on the hardware drivers. Then, on my computer I was able to run, adb root to start rooted debugging, open a shell on the phone with adb shell and run in this shell restorecon -FR /mnt/vendor/persist: $ adb root restarting adbd as root $ adb shell FP4:/ # restorecon -FR /mnt/vendor/persist SELinux: Loaded file context from: /system/etc/selinux/plat_file_contexts /system_ext/etc/selinux/system_ext_file_contexts /product/etc/selinux/product_file_contexts /vendor/etc/selinux/vendor_file_contexts /odm/etc/selinux/odm_file_contexts FP4:/ # Then you need to reboot and you can check this worked by enabling the automatic rotation feature: open an application and rotate your phone, the application should follow the movement

Hi there, is it supposed to look like this? I didn't use the phone throughout the day. Fairphone 4, 24.04-1.3 Thanks [image: 1778690699922-screenshot20260513_174305134.png]

@MalocDegray said: Via the phone terminal like @tafitson recommended is possible, but the phone is no longer detected via adb via computer. When the device is in fasboot/bootloader mode it is never recognized via adb. You need to have fastboot installed and with that command it should be recognized.

Apparently @kugiigi was right in his assumption that the notch hack filled up / . Reflashing freed 52 MB in / . That turned out to be sufficient to install Kugi's Ambot Installer which is a great tool! Everything's fine and I'm happy with the result. Thanks to everyone!

@fredldotme said: I have misplaced my FP4 and cannot find it at the moment Sad, i hope you misplaced it in your house and find it anytime !

@grenudi Thanks for linking that thread, though I've not had time to read it fully now. I am aware of the Halium approach vs. the mainline Linux approach, and I am somewhat (at least superficially) familiar with the downsides and upsides of each. I will try to read it in its entirety during the week to gain more insights. I am mostly interested in a mainline distro on my phone, but my plan with this second hand device is to familiarize myself with all possibilities available that will run on my device. postmarketOS is what I plan to try after Ubuntu Touch. I've been quite stoked about the recent progress posts on Mastadon by Luca Weiss (and his FOSDEM talk) on getting stuff like the camera and the battery gauge working. I understand these things are not trivial with the locked down mobile chipsets, even for someone directly employed at Fairphone. I'm testing them out in this order in hope of being able to contribute over longer time to testing stuff for postmarketOS.

@jagdtigger said: are they any errors in journal for the lomiri system settings service? Nothing: phablet@ubuntu-phablet:~$ sudo journalctl -u lomiri-system-settings -- No entries -- well, there is no such thing as a lomiri-system-settings systemd service so it's to expect that you will find nothing in the systemd journal under this item. I'd say that if you can connect to your UT phone with ssh (it's really more to my liking that the UT terminal to do debugging) you could start bluetoothctl, take a look at the result of 'show' (your controller should be powered, discoverable and pairable), 'devices', and if you see your device 'info <bluetooth address>' - if not, see what is displayed when you disable/enable pairing on your Bluetooth device.

Just to say I switched from Hallon (Tre) to Halebop, now everything works.

Hi all, Home(assistant)... Howdo I get my password in this app... I think I miss something becouse there seems only a place for the browser addres and tis is not enough... EJ

@pparent As I like it so far I'm going to do my best. It's quite a challange and I like challenges even if they are hard... EJ

It really does seem to be a power issue. Do you have other phones that can output to a display? You can test that. Am I right that you also use a portable monitor? Even with a separate power supply to it and the dock, the flicker still happens? In my experience, sometimes the sequence of connecting the ports may change the behavior or docks and such. I didn't experience the same issue of flickering but I had some other strange behavior with my adapter when connecting the power cable. The same with my portable monitor. I need to connect my phone first then the power to the monitor so that touch would work, otherwise, only the display output works but not the external touch input.

@MrT10001 Alright, will do! Thanks!

This is gone with the new 24.04-1.1 update and voLTE support.

SOLVED !

Hopefully this way it is easy to get a variety of images such as stable or daily rather than just the devel channel on GitLab.

Hy all, In update 224 it is fixed. Glad i din't rush things... Ernst-Jan

After messing with it for a good while, I was actually able to get it working with 5G/4G on the T-Mobile network by flashing the Android 13 stock image, then using the UBports installer. Note: it did seem to have some issues entering the fastboot mode, so that took some finagling. Also, it didn't seem to like it the first install, and I think I flashed Android 15 before Android 13, THEN installed Ubuntu Touch. But mileage may vary, obviously. Now to run some documentation of all loaded kernel modules and firmware versions from dmesg, and potentially try to debug why sound doesn't work on PostMarketOS, enough eyes, every bug is shallow, etc, as I'd prefer Plasma Mobile over Loromi. (Lorimi?) [But any FOSS system over Android, so I'm happier than I'd be without Ubuntu Touch]