@wgarcia Hi ! Sorry, I'm not sure to understand what you mean. This aGPS function (Xtra download) only download ephemeral, like tell Vlad. So it is a pure GPS function and it don't use WiFi or Bluetooth or scanning near cell tower. For the test please disable all GPS improvement system : So in Android settings : Improve Location Accuracy = off and Wi-Fi scanning and Bluetooth scanning = off and not in High Accuracy mode. So you need to put you Android in Device only GPS to be sure to disable all other functions. It just download a satellite map at this moment. And we just need Internet data (mobile data or Wi-Fi) just one time a day. You can download the data in your home and use GPS after. We use SatStat to download aGPS (the first option in the menu). So you can do the experiment as you share at the top of the topic, or like this : I prefer this way, because we are sure that it don't use other function that ask an external server to give the location. Open Waydroid Disable GPS in Waydroid Start SatStat Download aGPS in SatStat (the first item (Recharger les données AGPS in French) like in the Vlad picture) Wait 30 seconds and after Turn off Wi-Fi and Mobile data Close SatStat Go outside Enable GPS in Android Start SatStat and look, verify that it found GPS (at the bottom) and look at the TTFF : Time To First Fix. It should be quicker than 1 minute. Is it possible for you to test it ? Thanks a lot

@gpatel-fr Perfect, thank you!

@enki Bug in the Bluetooth? That type of issue does happen intermittently. Try disabling bluetooth then rebooting, on reboot wait for the phone to settle for a few minute before enabling bluetooth and trying again. https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/-/issues/14

@gpatel-fr Thank you. I will follow that bug-report.

@Escain What android version did the phone come with? V14. I think that the issue was because I setup a fingerprint on Android before I installed UT. After several reboots and I don't know exactly what, it started working. Now, everything except GPS seems to work. Thank you for your help

@kugiigi Yes, I've noticed that too reading around forums. This is why I'm looking into open source+hardware solutions like Modos (https://www.crowdsupply.com/modos-tech/modos-paper-monitor) and others, although most don't support touch yet. Honestly, considering you're getting a 75Hz refresh rate monitor that's actually e-ink in 2025, the prices don't look that bad, although do correct me if I'm wrong. There are even ways to add touchscreen support to any monitor, but that's a whole different story, and won't be worth getting into until UT develops touch monitor support.

@mango Thunderbird and firefox will probably eat your ram.

@gpatel-fr yeah, I have things to do but in the weekend I'll refine this more the only reason I'm not taking this down is because I'm doing it on mt FP5 and it has not exploded yet... so I may be good until the weekend.

@Azura did you wait up to 20 Minutes like explained in the update blog? my FP 4 needed about 5 Minutes to reboot. have a try again and wait, maybe with installer without wipe...good luck.

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

@Faby https://forums.ubports.com/topic/11452/some-shell-programs-are-missing-in-24.04-1

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