@volatius
I have a spare FP3+ that I updated to 24.04. It's been a bit unreliable, though I haven't put in a sim card, so I can't comment how that part works.

I have a FP4 and currently everything seems to work:

• data roaming abroad works
• calls / sms work
• wifi/hotspot/vpn works
• usb-c headset works (Sennheiser Momentum 4) with better volume control than on bluetooth (playback stopped when unplugging as well)

I have a spare FP3+. Pressing the power button during boot (when Ubuntu Touch with the 5 dots is shown) crashes the phone. The screen turns off and doesn't come back. Pressing the power button again for 2-3 secs starts the normal power on cycle.

Swiping out of waydroid freezes the phone. Turning the screen off and on works, but it's otherwise unresponsive.

@kristatos
I was not aware of that board, thanks

Are there plans for a 20.04-OTA11 or have development efforts fully moved on to 24.04? I'm hoping for a volte fix on my FP4

@adorsaz

There's a ticket on the fp4 port that confirms your findings:
https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-4/fairphone-fp4/-/issues/90

It's fixed on the daily branch of 24.04, but otherwise I'm not aware of any timeline for the next RCs

Video recording has been spotty for some time. While looking into volte I took a look at the dmesg out and it seems there's a camera provier service that's keeps crashing and restarting every few seconds:

$ dmesg -w
[204564.604170] init: starting service 'vendor.camera-provider-2-4'...
[204564.660417] init: Service 'vendor.camera-provider-2-4' (pid 51204) exited with status 1
[204564.660452] init: Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 51204) process group...
[204564.660729] libprocessgroup: Successfully killed process cgroup uid 1047 pid 51204 in 0ms
[204565.484399] init: Control message: Could not find 'vendor.qti.hardware.cacert@1.0::IService/default' for ctl.interface_start from pid: 37 (/system/bin/hwservicemanager)

Is this a know issue or where should I report this? If it's anything that will be looked at at all?

edit: I'm on 20.04 OTA-10

said in Does Fairphone 4 supports VoLTE ?:

@gpatel-fr

I just made a call, I got the standard ringing until the other side picked up the phone

Though again, I'm not sure if the lack of a "3g" icon is proof enough that volte is actually working Cellular Settings -> Carrier & APN -> 4G calling (VoLTE) is available and enabled

After a bit more testing it looks like that was a false positive Yes, all the settings are there, but following this thread and calling gbus it seems that volte is not actually supported:

$ cat /etc/ofono/binder.d/qti.conf 
[Settings]
ExpectSlots = slot1
extPlugin = qti
radioInterface = 1.4

[slot1]
path = /ril_0
slot = 0

$ gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties
({'Registered': <false>, 'Registration': <'auto'>, 'VoiceCapable': <false>, 'SmsCapable': <false>},)

@gpatel-fr

I just made a call, I got the standard ringing until the other side picked up the phone

Though again, I'm not sure if the lack of a "3g" icon is proof enough that volte is actually working Cellular Settings -> Carrier & APN -> 4G calling (VoLTE) is available and enabled see follow up answer

I haven't seen it documented anywhere( or I'm blind ) but it looks like VoLTE was backported(?) to 20.04-OTA10. I did one call so far and did not see the "3g" downgrade in the status bar. And the cellular settings newly offer "Connection Type: 2G/3G/4G/5G"

Hi all

I have whatsapp running in waydroid on my FP4. While this works well for chatting I have one main issue with calls. Unless I'm using headphones the calls are always on speaker and produce quite the echo for the other side. Is this a known issue and is there a solution for it? Another effect is that when waydroid is open the ringtone is played at full volume and can't be lowered, though I'm not sure it's related.

I found this topic on the fairphone forum, unfortunately there is no solution.

thanks

My daily driver is a FP4 with waydroid actively running at all times. This works but comes with a few caveats:

• with light phone usage overall I get ~10-12hrs battery life
• battery life varies drastically between any waydroid update, +- a few hours
• when locking the screen make sure any other app is in the foreground (e.g. the calendar). Not sure what's going on exactly but keeping waydroid active in the foreground costs a lot more battery life

@arubislander said in split dns/routing for personal vpn:

@gandalf Not sure about any answer to your questions, but I would suggest you research if what you want is possible on Ubuntu Desktop with NetworManager. If it is, then teh same setup should be transferable to Ubuntu Touch, as the VPN technology used is the same.

Thanks for the suggestions. I've set up openvpn and the import in UT worked without troubles.

Split dns works quite well;

• the openvpn server needs to push the default domain (eg. mylan for any server.mylan to work).
• In the vpn settings on UT select "Use this VPN for: [ x ] Its own network
• it also works in combination with the wifi hotspot (FP4), I can access my server by its domain without any changes to the laptop network settings.

tbd: keep alive, auto-reconnect, and maybe a kill switch for the local domain

@peat_psuwit said in On the subject of Ubuntu Touch versioning scheme:

We've considered 24.04 OTA-x.y. Unfortunately, (re-)using the word OTA could set the wrong expectation; by using the word OTA, many users will expect incremental, frequent updates (AKA rolling release).

Don't worry, users will expect unicorn rainbow farts anyway and while updates are a bit slow, technically UT is a rolling release

I'm really sorry that you have this sentiment. I also don't want to change the versioning scheme, but both the technical and practical reasons forced us to re-think how we will version Ubuntu Touch.

Don't be, it was mostly a joke, and, while I may not fully agree with the reasoning, it is overall a pretty minor change. I've been on the other side of this experience plenty of times. As a user I get upset about minor changes because they make up a much "larger" part of the user experience vs the experience as a developer where this is an "insignificant" side quest compared to all the development work actually being done

Also compare this change to the hot mess that is the current naming schemes from both intel and AMD

@peat_psuwit said in On the subject of Ubuntu Touch versioning scheme:

In the Board of Trustees meeting on 4th February, I've brought the release version numbering up as a discussion topic. The attendees considered the comments on this post and have agreed that it's important to still reference Ubuntu version in our versioning scheme, while it would be beneficial development-wise to have a major-minor release system in place.

As such, we've come up with a versioning scheme of "Ubuntu Touch [Ubuntu version]-[release version]" (a variant of option 3). For example, the next version of Ubuntu Touch would be referred to as "Ubuntu Touch 24.04-1.0".

We believe this versioning scheme is both understandable and practical.

I know I'm too late to the party; but if you're already staying this close to the current naming scheme why not go all the way to 24.04 OTA-1.0? Everyone is familiar with that naming convention already, and introducing a minor version number is "backwards" compatible by calling every previous OTA-x.0 if needed. And soon when UT reaches version parity with ubuntu 24.04 the colloquial OTA-x(.y) will be back in action offering an easy shortcut to identify the current release.

Aka I'm getting old and grumpy, but I really can't stand the relentless reshuffling of naming schemes that usually offer no improvement and just increase the mental load on trying to figure out wtf is going on again

I haven't run into the crash lomiri bug as I always close any app priori to rebooting just to make sure I don't dismiss anything important... I semi regularly reboot as there seems to be some buggy interaction between phone calls in UT and voice/video calls in whatsapp/waydroid :man_shrugging:

Hi all

A quick and tiny proposal; I've regularly accessed a blog posts directly form a search engine and then had to search around to find out when it was posted (aka is it recent or not). For example the announcement for RC-7. The date is there on the News page but that takes time to leave and search for the title (if it's not directly visible). Can I suggest adding the posting date to blog articles?

Thanks for your considerations and work :smiling_face_with_smiling_eyes:

p.s. equally irrelevant remark; the default sorting order for the emojis being alphabetical has the unfortunate side effect of putting all the happy faces far down the list and segregating all the :man_ :woman_ variants into distinct blocks (among other shuffling oddities)

Hi all

Small question for a small inconvenience; When rebooting my phone (FP4) it takes quite some time to shutdown before the android/unlocked bootloader splash screen shows up. On the order of 30s to a full minute. When I install an update though the restart is near instant the moment I click on install. Simple question, why?

Thanks :waving_hand:

Hi all

I'm looking into setting up an (always-on) vpn access to my home network. To that end I have a few questions.

• (1) Does UT support split routing based on the domain / "resolved IP"? Say the vpn is reachable at vpn.example.com, is it possible to resolve and send all requests for *.example.com through that vpn conenction, but nothing else?
• (2) What does "Use this VPN for" -> "its own network" in the vpn setup page do? Is that based on the IP range of the vpn network/gateway or on the domain?
• (3) I found this guide to potentially enable an always-on connection. is there a way to also enable a kill switch to block/timeout connections to *.example.com when the vpn is inactive?
• (4) If the above setup works, would that allow mutliple vpn connections to live side by side (assuming distinct ip ranges)?

Thanks in advance :waving_hand:

Hi all

I have a pair of Sennheiser Momentum 4 BT headphones and they work great for music or calls in waydroid. Unfortunately whenever I try to make or receive an actual phone call they get disconnected from UT.

Is this a known issue or (more likely) specific to this combination of FP4 + Momentum4?

Thanks in advance :waving_hand: