Ah thanks, silly me, I was actually trying to import a picture instead of exporting. I can pin the icon now but when I start Signal UT the X.Org logo appears again. If I then select the Signal UT icon the app starts a new instance and doesn't go back to the already opened app. I have to select the X.Org logo to go back to the already opened Signal UT app. So you can pin the icon and start the app with it but it doesn't allow you to take you back to the app if it's already open when you select it.

If the device can't connect it does just show "WPA" in the top bar notification with a password prompt and not "WPA & WPA2 Personal" as it probably should. That doesn't mean you are trying to connect via WPA. I think it would be best to follow my instruction to remove the AP and setup.

@projectmoon said in Call for testing: calendar-app: @lduboeuf said in Call for testing: calendar-app: @projectmoon said in Call for testing: calendar-app: @lduboeuf I installed it on a Volla Quintus on the current stable 24.04. Things seem to work. I notice that all my broken accounts/calendars are now sectioned as "Local Calendars," which I cannot delete. Unfortunately, the broken online calendars for those who have already switched to 24.04 before the next release won't be automatically fixed. A work around is to remove configs file: rm -rf .config/evolution/sources then restart the phone OK, then. New bug :). I deleted it and tried to re-add my calendars. The Google account went through the add flow but then said there's already an email address associated with that Google account. Then it did not add the calendar. This should be fixed on last RC ( make sure all accounts are cleaned before, and you did the configs remove as mentionned above )

@gpatel-fr said in Thinnking of getting myself into Fairphone 5...: @Boldos If GPS is something like a deal breaker for you, some Volla phones are said to have working AGPS , something that is lacking at the moment for the FP5 so GPS is a bit of a hit and miss. The other problems you are talking about are not specific to the FP5 (some rather uncommon media types have trouble with the main media app yes but can be read if necessary with third party software, VoLTE call following is also hit and miss, focus is not very reliable for low distance (<50cm) photos but this can be worked around by switching to video mode and back, and I have no problem with my Wifi hotspot but I'm not using a variety of Wifi nodes) I can confirm that the Volla Quintus has functioning AGPS. GPS lock takes a few seconds at most, usually.

@Talkless both projects are still maintained. UT has a lot more activity, but also a vastly bigger domain, so in both cases maintainers are spread thinly. That's not because what's interesting you is not moving fast enough for your taste that people are not active on these projects, they are just caring for other aspects of the projects.

This is odd, but in a good way. I just switched back to 1.x RC to test, and I can report that my Pebbles now work! The oddness is: when it didn't work, RC 1.2 was already out, but apparently I was on RC 1.1 somehow. I don't care very much, I'm just happy to report that it works

I just had a call on whatsapp web on my laptop (linux, firefox) and it was the same very poor sound quality - so I think it is not a problem with UT but rather with linux and whatsapp web...

@kugiigi said in Ubuntu Touch 24.04 AMD64 Image Availability: While waiting for people who knows more about this, check out PDK https://github.com/ubports/ubports-pdk I haven't tried it myself but it seems to be a good tool for testing and development. Thank you! I will

@PhAndersson sorry I have only one phone so I can't give you any advice. I think that Bluetooth support could matter for you. However I have noticed that the recent kernel change for the Fairphone 5 (my phone) was entirely to fix Bluetooth support, although there was no notice of any problem with Bluetooth on the device page at ubports.com, neither can I remember having seen posts complaining about Bluetooth with the FP5 - so relying on Internet information to pick a phone can be tricky.

@Massi a mi em passa el mateix. Mira aquí: https://gitlab.com/ubports/development/core/packaging/ofono/-/issues/3

@k.nacke said in Unlock Bootloader – How To Unlock?: A good strategy is to use RSA to download the firmware file, and save that file. The path is shown in the upper right corner of the UI while the file is downloaded. Either you are fast enough and you can copy the .zip file, or you need to zip the unzip directory yourself. Ok, I've downloaded files, now I have: RomFiles/TB_X306F_S230940_240402_BMP.zip - I have to recompress directory myself. I guess it is for space saving purposes right now, right? and ToolFiles/MTK_Flash_tool_v5.1920.00.001_V2.zip Are these two files sufficient for recovery?

@gpatel-fr thanks for digging into this. So, right, it's supposed to use ncm and not rndis, but usb-moded should handle tethering with that . The file you tried to cat is restricted to root access, but even with sudo, it's not accessible, and that probably explains why the configuration script fails, falling back to charging only. Maybe the fp5 is missing the corresponding kernel module now, while it had it back in August? I created a ticket.

@jojumaxx Merci, werde mein Fühler in Richtung snap ausstrecken und danke für den ernüchternden Hinweis zum dual boot. Dann muss das wohl alles über waydroid laufen.

@linhmieu2 You need to determine the VNDK level of your Android firmware, e.g. with adb shell getprop | grep vndk or using the Treble info app. Use that number to look up the corresponding Android version, e.g. at API levels. For example, if the VNDK version is 34, then you need to put deviceinfo_halium_version="14" in your deviceinfo file. The VNDK level is the API version level, and this it what counts for halium. Note that the version derived in this way may not correspond the Android version your device displays. E.g. I have a OnePlus 11 running Android 15, but the VNDK version is still 33, which corresponds to Android 13. For this device, I need to use 13 as the halium version. You may also want to put the number as ApiLevel into the /etc/gbinder.conf file in your system overlay. There is no "Android 12 kernel". I think it would be better if you post the concrete problems you encounter. The telegram group for porters is also a good place to ask or search for answers. Kai

@idonthatevests Interesting. For what it's worth, I'm very confident that mine was glitchy before I ever installed uFirefox. I did have Ambot Installer for the more limited Lomiri toolkit, but I'm not sure whether ithas anything to do with that. Mine always seems to glitch out after notification/SMS. I always kinda figured something about my install was messed up, though I did install what I thought was the appropriate firmware and do the whole MSM&EDL mode thing. I mostly ignored this issue thinking that if it only affected my phone, it's not that important. But it'd be handy if we could pin it down.

@ma Thanks for your suggestion. Things are working now since downgrading to 24.04.1.x RC. I think the 24.04.2.x version had several things in read-only mode (only guessing from reading the logs that were generated). Even when trying commands as sudo, received similar errors "need root access, read access, etc". Appreciate your input.

The takeaway is that you should not change the DNS server for the mobile internet connection using nmcli.