Resurrection of Indicator Upower
-
@paulcarroty My device is 1.Google Pixel 3aXL and 2. Xiaomi POCO X 3 in focal 20.04 -Devel channel.
Thank you. -
can you make a release? thanks @paulcarroty
-
@uxes said in Resurrection of Indicator Upower:
can you make a release? thanks @paulcarroty
Same request, please @paulcarroty
-
Test builds can be downloaded from Github Actions.
@alagirialagiri submit your Pixel data.
-
I am not sure if i grabbed working build 0.4 from today
-
Works on Poco X3 NFC
-
@uxes
Shouldn't device names becurtana,joyeuse,excaliburorgraminstead ofmiatoll?
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 -
@Eric-H it is pretty much possible i did not look how is getting device name implemented, but device is identified as miatoll in logs, and also in releases http://system-image.ubports.com/utnext/arm64/android9plus/daily/ on same level as surya
-
@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 It was just an idea.
Sorry for the inconvenience. -
Another reboot helped, now indicator works, we can mark miatoll as working, just needed two reboot not just one
-
@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.
-
New release arrived, thx to all contributors. -
@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 probably the store review still in progress.
-
@paulcarroty
Ok.
Thanks for your work. -
Hi @Eric-H
Here is an explanation:

-
@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_enabledfile on other devices? -
@Eric-H
miatoll-rwxrwxrwx 1 system system 4,0K led 19 12:40 /sys/class/power_supply/battery/charging_enabled
-
@Eric-H try the next rule with 0664:
ACTION=="add|change", SUBSYSTEM=="power_supply", KERNEL=="battery", RUN+="/bin/chmod 0664 /sys/class/power_supply/%k/charging_enabled", RUN+="/bin/chown phablet /sys/class/power_supply/%k/charging_enabled"
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login