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

@paulcarroty
A merge request has been proposed on surya, but another (global) solution is suggested in the comments :
https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3/xiaomi-surya/-/merge_requests/20

@paulcarroty
According to https://android.stackexchange.com/questions/200032/difference-between-system-files-charging-enabled-vs-battery-charging-enabled battery-charging-enabled has a different behavior than charging-enabled.
So I will just make a MR to add the above udev rule in surya and karna.
Thanks for your work

@paulcarroty
The udev rule is working properly:
-rw-rw-r-- 1 phablet system 4096 janv. 23 09:08 /sys/class/power_supply/battery/charging_enabled
And the content of charging_enabled goes well from 1 to 0 when the charge exceeds 85%.

But, despite this, the device continues to charge beyond 85 % !

(I believe that, on surya and karna, we must have to write in another file.
I will try with `/sys/class/power_supply/battery/battery_charging_enabled )

@nonobike
It should work !
Please, take a look a these issues and their solutions.
https://github.com/fredldotme/snapz0r/issues

@paulcarroty
I think it's indeed the right approach.
I will confirm today that it works.

@nonobike
Indeed.
If you want to check on your phone you can type in terminal.app :

zgrep -i squashfs /proc/config.gz

@nonobike

in OnePlus Nord N100 kernel config, the following lines are already present :
CONFIG_SQUASHFS=y
CONFIG_SQUASHFS_XZ=y
CONFIG_SQUASHFS_LZO=y

@paulcarroty
I tested the 0.5 release on surya and I can confirm that it works as expected.

Regarding the udev rule, it works perfectly with permissions 0666.
But if I try 0664, it no longer works…
What is the group of the /sys/class/power_supply/battery/charging_enabled file on other devices?

@paulcarroty
Ok.
Thanks for your work.

@paulcarroty
I can see on github that v0.5 has been released.
But only v0.4 seems to be available on the open store.

@Eric-H said in Resurrection of Indicator Upower:

/bin/sh: 1: cannot create /sys/class/power_supply/battery/charging_enabled: Permission denied

@paulcarroty I'm currently experimenting a udev rules :

# Set charging permissions so indicator-upower can access it
ACTION=="add|change", SUBSYSTEM=="power_supply", KERNEL=="battery", RUN+="/bin/chmod 0666 /sys/class/power_supply/%k/charging_enabled"

It seems to work. I will confirm later.

@uxes It was just an idea.
Sorry for the inconvenience.

@paulcarroty
I installed test build for surya.
It seems to work but it does not stop charging when limit is reached.

Is it related to the following message ?

/bin/sh: 1: cannot create /sys/class/power_supply/battery/charging_enabled: Permission denied

@uxes
Shouldn't device names be curtana, joyeuse, excalibur or gram instead of miatoll ?
https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-redmi-note-9-pro/xiaomi-miatoll/-/tree/focal/overlay/system/etc/deviceinfo/devices?ref_type=heads

@uxes said in Resurrection of Indicator Upower:

can you make a release? thanks @paulcarroty

Same request, please @paulcarroty

It is more than recommended to downgrade to the needed V12.0.9.0.QJGMIXM Android 10 version.