Community favourite developer:

Tobiyo Kuujikai / @Fuseteam

• for Crackle/nix contributions
• for all debClick apps including firefox
• for his work on UT Core and related issues
• for his help on UT telegram groups
• for every helpful interaction I’ve had with him

@messayisto
See this post: https://community.braxtech.net/t/building-a-new-path-for-mobile-partnering-with-ubports/2660

@chaospredictor
One option I've tested is to use Crackle to install the version of python you want
After that, you can use pip and venv.

Crackle : https://gitlab.com/tuxecure/crackle-apt/crackle

@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

@atarilinux @wally
Maybe you will be interested in Daniel Pratt's tests with T-Mobile in the USA on a Poco X3 NFC ?

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

@snailc
The 12.5.9 global MIUI is available at http://xmfirmwareupdater.com/miui/vayu/stable/V12.5.9.0.RJUMIXM/

The fastboot error is probably because of system is a logical partition and you need to use fastbootD.

fastboot reboot fastboot
fastboot flash system ubuntu.img

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

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

Hi @Jules

Have you tried to reset your APNs in System Settings?

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)

@idonthatevests hi, I installed Soty 2025.12.07 version and it works perfectly with UT Translator (french to english).

Thank you for your work.

@greg hi,
If you haven't already found them by yourself, git repositories are on gitlab: https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3

if you have any questions, join pocox3 telegram group: https://t.me/ut_pocox3

@Sentinel Hi
I'm surprised by some of the bugs you report because I don't have the same ones on my poco x3 nfc.
For example, I was able to download Android images without a problem with Waydroid Helper, waydroid has access to GPS or my fingerprint reader works perfectly...

Anyway, I'm interested in fixing poco x3 bugs, for example I'm currently testing a kernel patch that should improve the stability of waydroid.
But this being off-topic, can you join us on the Telegram Group https://t.me/ut_pocox3 (Bridged to #ut_surya:matrix.org on Matrix)?

@mariogrip IMO its a brilliant idea. Thank you.

Here are some examples of bugs that are problematic:

Core System Stuff

• device crashes
  • Daily reboots without command
  • Poco NFC X3 it reboots and disconnects the sim about every 12 hours

Basic Phone Features

• The phone application freezes when I receive a call while I'm already online (VoLTE enabled). A reboot is then necessary.
• switching to airplane mode often leads to a disconnection of the VolTE. A reboot is then necessary.
• My camera app crashes every day or so

Daily Use

• camera image quality
  • All pictures (and also videos) taken with the device have colors off and are overall poor quality
  • Camera Not Actually Fully Supported
• GPS too slow

Polish

• Rounded corners and camera notch
  • The notch covers some screen space
  • Bring indicators under camera notch
  • Lomiri must avoid rounded corners and camera notch

Nice to Have

• Docker container cannot start normally

Community favourite developer:

Tobiyo Kuujikai / @Fuseteam

• for Crackle/nix contributions
• for all debClick apps including firefox
• for his work on UT Core and related issues
• for his help on UT telegram groups
• for every helpful interaction I’ve had with him

@messayisto
See this post: https://community.braxtech.net/t/building-a-new-path-for-mobile-partnering-with-ubports/2660

@mr_growl
Iirc, an android 12 phone must have a recovery partition unless it is a slot A/B device.

for example on my device

• to check recovery partition

  $ fastboot getvar all |& grep -i recovery
  (bootloader) partition-type:recovery:raw
  (bootloader) partition-size:recovery: 0x8000000
  

• to flash recovery partition

  fastboot flash recovery recovery.img
  

• to check slots, in fastbootD mode

  $ fastboot getvar slot-count
  slot-count: 0
  

If there is no recovery partition on your phone, you probably need a recovery ramdisk.
See ramdisk-overlay directory on Volla X23 for example:
https://gitlab.com/ubports/porting/reference-device-ports/halium12/volla-x23/volla-vidofnir/-/tree/main

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

The recovery doesn't work after flashing.

To make sure to understand

• is there a recovery partition on the android 12 pixel 3a ?
• or can't you boot in recovery mode with something like that : fastboot boot recovery.img

(building ubports recovery.img has to be enabled in device info)

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

nothing ususual in dmesg

pstore (console + ram) and last_kmsg should be enabled in your kernel config, then you will be able after a boot attempt, to get logs from either console-ramoops or last_kmsg in recovery mode.