@tigerpro yes, should be mostly just plug and play, see https://forums.ubports.com/topic/10675/status-update-on-the-next-noble-based-ubuntu-touch-release-december-2024 for the changes that may be needed on pulse config.

@uxes sadly yes it's slightly bigger, this is something we need to figure out, ether by slimming the image down or resize partitions on the fly. LTO has been enabled on nobile, this makes the binaries smaller at the same time, so the increase comes from more code

@Keneda if it's fp5 you're referring too, yes this is pretty much daily driver ready on focal already, for noble it does require more work on the os itself, but the device port is ready. But I wouldn't use noble as your daily driver yet.

Hi all,

I'd like to start posting weekly development updates here on the forums - this is a bit of an experiment, so please let me know if you find these updates useful and what could be improved. The goal is to provide a high-level overview of our development progress.

This past week focused heavily on Noble development, with rapid changes to the image. I'm pleased to report that the latest daily build should have all hardware features working, including GPS, calling, sound, fingerprint reader, NFC, and more. We've also fixed several indicator bugs, making the 24.04 base system quite usable.

Currently, we're missing 24.04 built clicks, which is why some core apps aren't starting yet. While most of them build and run fine, we're waiting for some clickable changes to enable compilation. There are also some pending tasks related to accounts and push services, plus likely a few bugs to address.

Please test out 24.04 and report any bugs you find! Your feedback helps us improve the system.

@Inali Awesome! Here is how to enable it.

1. be on the latest devel (rev 30)
2. Install ofono-binder-plugin-ext-qti (using apt)
3. Add this extPlugin = qti to /etc/ofono/binder.d/qti.conf

Here is how the full file should look like

phablet@ubuntu-phablet:~$ cat /etc/ofono/binder.d/qti.conf 
# This device do have 2 slots, but the other is eSIM only and we currently do not have
# a way to install or modify those
[Settings]
ExpectSlots = slot1
extPlugin = qti
radioInterface = 1.5

[slot1]
path = /ril_0
slot = 0

Then reboot

@peat_psuwit done

@Enrico13011978 You need to ask the porter of the device to enable ims and this plugin.

@kristatos

1. Nope
2. I haven't tested it yet, but it should
3. Mtk has its own plugin, it should already be in devel and enabled on the newest volla devices.

@Beta-Break It will say 5G and VoLTE in the indicator

@Lakotaubp Haven't tried on my FP4 just yet, but its on my todo list.

@alagirialagiri They need to be ported to be able, see my comment above for instructions.

@tigerpro Yeah, at least LTE has to work. To test it, install ofono-binder-plugin-qti and add extPlugin = qti to binder.conf or binder.d/something.conf under [Settings]

Example from FP5

phablet@ubuntu-phablet:~$ cat /etc/ofono/binder.d/qti.conf 
# This device do have 2 slots, but the other is eSIM only and we currently do not have
# a way to install or modify those
[Settings]
ExpectSlots = slot1
extPlugin = qti
radioInterface = 1.5

[slot1]
path = /ril_0
slot = 0

Also remember to re-enable ims services that might have been disabled under porting.

@messayisto does not have to be, its the device i have used to develop and test volte for Qualcomm so i know it works. For other devices it might require some work to get it to a new device.

Has this been updated to the latest? since some of these issues should be fixed by now. We do have a system image (installer) image now.

13 is best, then we get the latest drivers. The drivers (vendor partition) are for android 11 regardless anyway. they work fine across android version due to treble and common qcom stuff.

Hi everyone,

After a brief delay caused by some medical issues on my part, I'm excited to announce that I’ve successfully developed a fully functional VoLTE implementation for Qualcomm devices. I've been using the Fairphone 5 (FP5) as my testing platform, and everything is now up and running.

I do however request some help with testing, anyone wanting to help out with that?

Hi all,

!! Experimental !!
This will modify your rootfs and make changes, DO NOT use this on your daily driver if you don't know how to recover.

I have made a crude and hacky widevine drm test if anyone wants to try, I need to gather some input on what works and what does not.

I would like to test different websites with both settings->Set desktop mode enabled and disabled in morph settings. This has the effect that it changes the user agent, this may work on some website that tries to force you on an android app.

This is done to figure out what needs a user agent override and what already works without. so please test websites that is known to use Widevine.

A quick demo to check if it all works: https://bitmovin.com/demos/drm

Please report your findings here https://pad.ubports.com/p/widevine-test

https://open-store.io/app/widenabler.mariogrip

Thank you

@domubpkm sadly i cannot do this easily, but will try.
How does this look?

There is an Ubuntu theme/skin we can try, but it's highly orange

@Lakotaubp Good catch! fixed now, was a plugin that failed on registration, but fixed now!