@wally
On poco x3, photos are not always bad :

• https://t.me/ut_pocox3/17466
• https://t.me/ut_pocox3/17467
• https://t.me/ut_pocox3/17468

@_Joao_
It's strange on my surya I can use duck.ai without any issues under Morph and Sapot.
What type of problems have you noticed ?

Hi @wally

1. Regarding the camera, it is indeed the main drawback of the Poco X3 running Ubuntu Touch. However, it is possible to use GCam through Waydroid : https://t.me/ut_pocox3/18640
2. As long as the codename is surya (Poco X3 NFC) or karna (Poco X3), there should be no issues.
3. Concerning Canadian carriers, perhaps @Ontario can provide you with useful information.

@wally
Regarding VoLTE on the Pixel 3a, this is a new port under Android 12 that was developed to enable this feature.
However, I am not aware of the current status of this port, nor whether the effort will continue or has been abandoned.

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

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.

@jaxx
About dataqti service, take a look at :
https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3/xiaomi-surya/-/merge_requests/21

About powersaving, please see :
https://codeberg.org/EricHeintzmann/UbuntuTouch/issues/24

Any help will be welcome

@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.

@paulcarroty
For some unknown reason, today the message on stderr did not appear.

So here is the power.txt file for surya attached.
or see at https://dpaste.org/hCcZO

I can see POWER_SUPPLY_CHARGE_TYPE=Fast in udev battery info, so it seems to be a fast charge.
What should Indicator Upower display ?

@paulcarroty
I tried to generate the power.txt file but there is an error on stderr :

cat: '/sys/devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-00/c440000.qcom,spmi:qcom,pm6150@0:qcom,qpnp-smb5/power_supply/main/health': Invalid argument

The health files exists and is world readable :

phablet@ubuntu-phablet:~/tmp$ ls -al /sys/devices/platform/soc/c440000.qcom\,spmi/spmi-0/spmi0-00/c440000.qcom\,spmi\:qcom\,pm6150@0\:qcom\,qpnp-smb5/power_supply/main/health 
-r--r--r-- 1 system system 4096 mai    6 06:21 /sys/devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-00/c440000.qcom,spmi:qcom,pm6150@0:qcom,qpnp-smb5/power_supply/main/health

The error persists even if I try to

• add double quotes,
• add simple quotes
• replace cat with tail

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

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

@paulcarroty
Sorry, I couldn't do the test before today...

So I used the Xiaomi charger supplied with the phone (which fully charges in less than half an hour) with the latest version (0.7) of uPower, but it seems that fast charging is not detected and there's nothing related in the logs.

@paulcarroty
Reinstalled. It seems to work fine.
Do you need specific tests ?

About this error :
ValueError: could not convert string to float: '3,65353'

Maybe it is a localization error (french) : there is a comma instead of a point

@paulcarroty
Reinstalled.
Does not work on surya.

https://dpaste.com/G66MBRASC

@paulcarroty
I installed latest build, and the app no longer starts.

https://dpaste.com/6CTBE25DB

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)

@paulcarroty

Test 2 (with udev rules) : same results as test 1

I applied udev rules from README :

phablet@ubuntu-phablet:~$ ls -al /sys/class/power_supply/battery/{battery_,}charging_enabled
-rw-rw-r-- 1 phablet system 4096 févr. 17 17:28 /sys/class/power_supply/battery/battery_charging_enabled
-rw-rw-r-- 1 phablet system 4096 févr. 17 17:06 /sys/class/power_supply/battery/charging_enabled

• when charge is less than 85%, device charges :

  tail /sys/class/power_supply/battery/{battery_,}charging_enabled
  ==> /sys/class/power_supply/battery/battery_charging_enabled <==
  1
  
  ==> /sys/class/power_supply/battery/charging_enabled <==
  1
  

• when charge is more than 85%, device doesn't charge (and doesn't seem to discharge until unplugged) :

  tail /sys/class/power_supply/battery/{battery_,}charging_enabled
  ==> /sys/class/power_supply/battery/battery_charging_enabled <==
  0
  
  ==> /sys/class/power_supply/battery/charging_enabled <==
  1
  

(when unplugging, the values in the two files return to 1)

@paulcarroty said in Resurrection of Indicator Upower:

I need beta testers to check the limiting battery's charge.

Test 1:

• when charge is less than 85%, device charges :

  tail /sys/class/power_supply/battery/{battery_,}charging_enabled
  ==> /sys/class/power_supply/battery/battery_charging_enabled <==
  1
  
  ==> /sys/class/power_supply/battery/charging_enabled <==
  1
  

• when charge is more than 85%, device doesn't charge (and doesn't seem to discharge until unplugged)

  tail /sys/class/power_supply/battery/{battery_,}charging_enabled
  ==> /sys/class/power_supply/battery/battery_charging_enabled <==
  0
  
  ==> /sys/class/power_supply/battery/charging_enabled <==
  1
  

  (when unplugging, the values in the two files return to 1)

@paulcarroty said in Resurrection of Indicator Upower:

Ahoy, there's battery_charging_enabled support in the latest builds and I need beta testers to check the limiting battery's charge.

You need to apply new udev rule from README and install the latest build from Github Actions.

Thanks !
I installed latest build from Github Actions.

Notice that, on surya, default permissions are :

• -rwxrwxrwx 1 system system 4096 févr. 17 11:15 battery_charging_enabled
• -rw-r--r-- 1 system system 4096 févr. 17 11:15 charging_enabled

I leave them untouched for the first tests
Let me know if you need tests with different permissions