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

Hello,

surya is the codename of Xiaomi POCO X3 NFC,
and karna is the codename of Indian POCO X3.

You can check it by typing in a terminal

getprop | grep surya

or

getprop | grep karna

Is there a way to make VoLTE work with radioInterface = 1.4 ?

Finally, after commenting on the IMS services lines in the file init.disabled.rc the VoLTE works with radioInterface = 1.4 on POCO X3 NFC.

Some features don't seem to work properly anymore.
I will report on the issues encountered after a few days of testing.

I'm working on the POCO X3 NFC (surya) port with the maintainer and I tried Marius' changes, without success.
The device is 4G only, and there is no android.hardware.radio@1.5.so (android 10).

@mariogrip
Is there a way to make VoLTE work with radioInterface = 1.4 ?

Hi @peat_psuwit

How to check if noble image is available for poco x3 (surya) ?

I tried

system-image-cli --list-channels

but an exception occurs every time.

Hi,

As suggested by @Fuseteam, I disabled data connection and I did a new test (still without BatterySaver app):

3. Wi-Fi on, data off : 38 hours of battery lifetime

Same as Wi-Fi on and data on.
It seems that the data connection is not used while Wi-Fi is on.