@Futura Just want to confirm this same thing happened to me. I had been daily driving calyxos, but wanted to give the new 24.04 a try. Initial progression went like this: calyxos > fairphone 15 > ubuntu 24.04 - neither wifi nor T-Mobile data worked I messed around with a couple other things including postmarket, no avail. Tried your trick: postmarket > fairphone 13 > changed setting above > ubuntu 24.04 - wifi and LTE both work Strange, and I'm not sure I follow why that works, but can confirm it does. Thanks!

Ah thank you. This seems to have been set to tethering. I wasn't aware this would also stop file transfers when I've been looking to diagnose why. Resolved

I still don't know how to make the sdcard appear directly on my desktop computer when I connect my phone, but I have a workaround : symlink the sdcard mount point in the /home/phablet directory ( = "internal storage" on the desktop computer). This is easily done using the terminal (or adb shell). Find the exact mount point of the sdcard using the command mount; it is something like /media/phablet/XXXX-YYYY. Then enter ln -s /media/phablet/XXXX-YYYY ~/sdcard

@xforze Hello while I have not yet unraveled all the intricacies of ubports gitlab build, here is what I have found so far. Binaries are uploaded to https://system-image.ubports.com like usual with Debian dirs, there are index directories and a huge pool dir containing all the data files in compressed form (tar.xz): https://system-image.ubports.com/pool/ data files beginning by 'rootfs-' are as the name implies a frozen file system with all deb packages data files beginning by 'device-' contain the android container data files beginning by 'boot-' are the ones of interest with 2 directories: partitions: boot.img and vendor_boot.img system: here is where can be found the kernel name, under system/usr/lib/modules ls 5.4.289-qgki-g4ddb22d91965 cd 5.4.289-qgki-g4ddb22d91965/ ls source source -> /builds/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/workdir/downloads/kernel-fairphone-qcm6490 note: this is a broken link, but it shows from where is coming the built archive. If you git clone the directory (note that in the Gitlab UI the directories appear to be called 'Halium 11' but if you copy the Url you get android 11 instead) git clone https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/kernel-fairphone-qcm6490 git branch -a halium-11.0 remotes/origin/HEAD -> origin/halium-11.0 remotes/origin/halium-11.0 remotes/origin/halium-11.0-rebase so there are 2 main branches, halium-11.0 and halium-11.0-rebase on halium-11.0-rebase branch, use git log and search for 5.4.289, you'll find commit cb5f77d16c36027aa197fc26183b8d7e17c8f016 by a lineageos developer. on halium-11.0 branch, you'll not find a commit containing the string 5.4.289, the most recent with 5.4. will be 5.4.219. So what I think at the moment is that when the built is done, the fairphone-5 dir is switched to the master branch and the deviceinfo file contains 'deviceinfo_kernel_source_branch="halium-11.0-rebase" I have not found where is hidden the procedure to build for 24.04. The .gitlab-ci.yml under the fairphone-5 directory seem to build for 20.04 in all branches. That's still mysterious for me. Still it seems clear that recent dev is happening in the hallium-11.rebase branch so it must be the one. Now, 'qgki' is clear: it stands for qualcomm generic kernel image'. The prize would be to find a relationship (if any) between 'g4ddb22d91965' and a specific commit in git. No idea currently

The main thing here is that Ubuntu Touch doesn't have the latest and greatest support for Wayland/XWayland. This is needed so you can run traditional desktop apps. It will come in the future and there are already works on it on the desktop side of things. However, even with that, we can't expect for these desktop apps to magically work well on small screens with touch input. As mentioned, uWolf is in the OpenStore which is Librewolf but made to work better on phones. It still has some quirks though, caused by the same thing I mentioned earlier. It has no clipboard support and the performance isn't as good as the native browser.

@slowcyclist There is a bug report which I found later. This is supposed to be fixed now, however, it is not for me. Just sits with Server Stopped forever. I don't see how I can disable and restart the service if you can't get past "Server Stopped" to get to the menus. Seems a clean install of the app would likely fix it, but how? Is there some way to "purge" click packages; as in, remove all the configuration files when you remove them? I'm thinking it may just be easier to have a list of packages, find out how to backup my contacts, call history and messages then wipe clean? Is there some information on doing that? Maybe an app or something built into UT to do that would be nice.

99% certain this has something to do with waydroid. I get it all the time on fp4, but only after i used waydroid. Is there an open issue somewhere on gitlab?

@Thomas Yes it is. Installing from A15 is not supported, that doesn't mean you can't do it, but UT is not developed on top of A15 kernel and drivers, nor tested on it, so you could encounter failures because of this, and you will not get official support for it.

@Lakotaubp did it work? I've got a FP4 with 24.04-1 daily and would love to get VoLTE running.

@poVoq No, sorry. Only A14.

@Zardozor25 What happens when you try "fastboot devices"? Also if this is happening on Windows I had the same trouble. I resolved this by using Linux and installing android-tools. Windows absolutely refuses to see my FP5 in fastboot no matter what.

Wifi works fine on my Fairphone 5 with 24.04 (r542). USB tethering works as well.

@Futura Most of the time, yes. But I am still on Focal.

@Futura A lot of us use Cinny, a matrix client. And then matrix bridges to signal and some other services. We also heavily rely on Telegram through the app Teleports for all of the UT groups.

ok, after downgrade to Android 13 the installation of UbunTutouch went good and the OS Startet

To progress further with the initial flashlight idea, controlling the flash directly appears to work fine in the following way. #!/usr/bin/env bash flashOff() { printf '%s' "0" > /sys/class/leds/led:torch_0/brightness printf '%s' "0" > /sys/class/leds/led:switch_0/brightness } flashOn() { # 2 appears to be the minimum brightness value possible printf '%s' "2" > /sys/class/leds/led:torch_0/brightness printf '%s' "1" > /sys/class/leds/led:switch_0/brightness } So with a loop I can have a nice flashing pattern at the minimum brightness. Just need to find what to hook into so I can have it only running only while there is a green notifications icon. As for using the screen, I think the green envelope icon, possibly slowly moving along the top edge of the screen (to minimise any burn in); would be a nice option there.

@stanwood thanks I might revisit in like 6 months time and see if things have improved I actually own two FP5s (got a 2nd one recently very cheap second hand recently to muck around with) and for now I'm having fun using CalyxOS I did rather enjoy UT for my short few days using it. As it matures I'd love to re-visit it

To be honest, I don't think it's ready to be promoted as such. It should be listed there but not described as "best" since as you mentioned, it only has the devel channel and development is still active so big changes lands from time to time that may bring functionalities but could also land regressions. For example, proper sleep was implemented however there are quirks that came with it such as wifi issue while device is sleeping. Theoretically it is one, if not the best device for UT but currently I don't think it is.