Hello,

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

Thanks

@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