@uxes said in Working VoLTE reports, share your experience:

after some months of using, i know that after start using volte, 4G internet sometimes stop working, maybe after call/sms only thing that helps is to disable/enable data in indicators (no reboot required)
Eric from poco reported that adding new APN may help

For those interested in activating VoLTE on the Poco X3, here are the steps I followed:

• After enabling VoLTE, I noticed errors in the logs related to context 1 of ofono. To address this, I replaced this context with a new APN "Internet & MMS" using the commands available in /usr/share/ofono/scripts/.
• I also removed an unused connection using ncli connection.

While I can't guarantee that these modifications are the solution, I haven't encountered any issues since.

It's important to note that after exiting airplane mode, the poco often struggles to reconnect to VoLTE without a reboot.

It is possible to obtain a list of all devices in devel where VoLTE is enabled by conducting a search on Gitlab :

https://gitlab.com/search?group_id=54262841&scope=blobs&search=OfonoImplementsIms%3A+true&page=1

Hello,

Will it be possible to use the Alfred's browser engine instead of QtWebengine to create webapps for UT ?

Thanks

Xiaomi POCO X3 NFC (surya)

• Calls: OK
• SMS: OK
• Cellular data: OK
• Address book app : OK (can remove pictures)
• Web browser (Morph): OK
• Wi-Fi settings: OK (WPA3 !)
• MMS
  • OK in 3G &4G
  • cannot send or receive MMS in 2G when I make call (but it's not new)

Xiaomi POCO X3 NFC (surya)
focal 20.04 devel (r581)
France, SFR

VoLTE tests : https://codeberg.org/EricHeintzmann/UbuntuTouch/issues/23

I tested version 2025-W22 on my Xiaomi POCO X3 NFC (surya), and here are my observations:

• The notification LED works normally
• Emojis display correctly.
• Waydroid functions without issues. So far, I haven't noticed any regressions.

Regarding VoLTE:

• With VoLTE disabled:
  Basic functionalities (calls, SMS, MMS, and cellular data) work perfectly.

• With VoLTE enabled:
  Basic functionalities (calls, SMS, MMS, and cellular data) also work.
  However, when the phone exits airplane mode, it often struggles to reconnect to VoLTE.

Other users have reported issues related to VoLTE that I couldn't reproduce, but I mention them here in case they might be useful:

• Inability to send SMS when VoLTE is enabled (https://forums.ubports.com/post/85788).
• Inability to download messages with Teleports when VoLTE is enabled (https://t.me/ut_pocox3/18228).
• Difficulty hanging up after a call when VoLTE is enabled (https://t.me/ut_pocox3/18506).This happened to me once and seems to occur randomly.

@Futura Pipelines are launched in STEP 2

@atarilinux
Without Telegram, it might be complicated, as almost all discussions regarding UT take place there.
If you use Matrix, I believe there are bridges to these Telegram groups.

@atarilinux said in VoLTE Implementation For Google Pixel 3a/3a XL:

I'm trying to locate the exact Android 12 version used by @fredldotme. Is this listed somewhere in the files and/or documentation? Perhaps I'm overlooking it.

Usually, this is documented on the device page of the port.
But not in this case...

Keep in mind I use bonito, and the code in the device info file only mentions sargo. I'm not sure if that would need to be updated. Some files include bonito, but this specific file only mentions sargo. Perhaps bonito and sargo share some files?

Yes, some ports share repo ( see surya and karna , or miatoll, or android 9 sargo and bonito).

For all your questions I recommend asking on UBports Telegram (Pixel 3a and Porting groups)

@atarilinux said in VoLTE Implementation For Google Pixel 3a/3a XL:

Now how do I get it from here to the phone to begin testing? Would that be this:
https://docs.ubports.com/en/latest/porting/build_and_boot/index.html

Or...has this already been done?

build step have been done in you fork - at step 2

I have the newest Ubports-installer on my Debian Linux computer. Thanks!

Currently, the new port cannot be installed by the the UBports installer.

@atarilinux
Now that the project has been forked, you can proceed to step 2.
In the new fork, in the left menu, go to Build->Pipelines

• click on new pipeline button.
• confirm.
• Wait - the build process might take several tens of minutes.
• .img files can be downloaded from the devel-flashable artifact

Next steps (make sure your phone bootloader is unlocked) :

1. on your phone flash stock android 12 ROM - use exactly the same version used by the developer.
2. flash the downloaded .img files with fastboot/fasbootD
3. test and report

@Nocflounder
Correction: acccording to the source code, yes, bonito is supported by the new android 12 port.

https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo/-/blob/main/overlay/system/etc/deviceinfo/devices/halium.yaml#L21

Hi @Nocflounder
I’m not 100% sure. It’s better to ask the developer of the new port in the Pixel 3a Telegram group.

Hi @atarilinux
It is better to rebuild the images and it is easy.
This can be done is two step.
First step, fork the repository on gilab :

• sign in/up to gitlab.com on your desktop
• go to the new port repository : https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo
• click on fork button
• click on fork project (keep the public visibility)

@ikoz
true.
The .img files seems a bit outdated.
Not sure the VoLTE/binder qti plugin was stable 8 months ago.
But yes they can be flashed and tested.

@_Joao_
If you cannot find someone who has one, you will have to wait...

• wait for a fix from duckduckgo if they accept to do it. But someone will have to report this issue first.
• or wait for a new morph version. I think Morph Qt6 will fix this issue but i guess it will take several months at least.