Resurrection of Indicator Upower

paulcarroty

@Salah said in Resurrection of Indicator Upower:

Google Pixel 3a XL

Limited support only, because your device is not in the list. You can help add it by providing sys/class/power_supply and/or /sys/devices/ dirs when the charger cable is plugged in.

paulcarroty

️ https://open-store.io/app/indicator.upower.ernesst.fork

arubislander

@paulcarroty Great work!

Maybe you could explicitly mention in the description that it will not work on all devices, along with the link to the readme which is already there. Some users don't make the effort to read before posting reviews...

Salah

I would like to thank you for your effort to debut a good application which I presume it must be as a primary app in UT.

I've downloaded the app to see how it looks like and as per below attachments:

I am using Google Pixel 3a XL, as you can see it is not working properly.

Will keep this app in my device and looking forward to be updated and fully functional soon.

Thumbs Up

alagirialagiri

@paulcarroty Please give full details to add this app working in google pixel 3aXL and Poco X3,Thanking you for your Upower app. How and where to be added.? "sys/class/power_supply and/or /sys/devices/ "

paulcarroty

@alagirialagiri new release got many fixes.

Submit your device data - here's the guide.

Please give full details to add this app working

This script does the kernel data collecting and parsing, then sending it over DBus to the QML GUI.

alagirialagiri

@paulcarroty My device is 1.Google Pixel 3aXL and 2. Xiaomi POCO X 3 in focal 20.04 -Devel channel.
Thank you.

uxes

can you make a release? thanks @paulcarroty

Eric H

@uxes said in Resurrection of Indicator Upower:

can you make a release? thanks @paulcarroty

Same request, please @paulcarroty

paulcarroty

Test builds can be downloaded from Github Actions.

@alagirialagiri submit your Pixel data.

uxes

I am not sure if i grabbed working build 0.4 from today

https://dpaste.com/DJSGN2QTL

Ontario

Works on Poco X3 NFC

Eric H

@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

@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

Eric H

@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

Eric H

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

uxes

Another reboot helped, now indicator works, we can mark miatoll as working, just needed two reboot not just one

Eric H

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

paulcarroty

New release arrived, thx to all contributors.

Eric H

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