Related
In a root console, "top -m 5" tells me:
PID CPU% S #THR VSS RSS PCY UID Name
2705 18% S 37 248200K 17768K fg app_21 com.android.kineto
It bounces between 8 and 20%, when idle with screen off.
It most likely is wifi-calling as that process will fc if the wifi calling apk is removed (until reboot). Uninstall wifi calling if you don't use it, reboot and see if it helps.
Thanks, although i already figured out it FC's if you delete the apk. Scared me for a little bit, phone went all wierd.
With the APK removed and the phone reooted my average standby CPU usage dropped from 25% to around 8%.
What if your uninstaller says the uninstall has failed? It dosnt stop running and takes over 20% of my battery's power.
You can also freeze it withTitanium backup, which of course makes it so if you do need it as some point you can just unfreeze it and use the app. I have found the app useful especially at a friends whose house is made of lead or somehting cuase I get no bars inside and full signal outside.
Sent from my SGH-T959 using XDA App
I'm running CM7.2 (2/10/2012) and the phone is experiencing high CPU utilization. Using top, I see that process "system_server" is constantly running at greater than 90%. I've rebooted the phone. I have also wiped it completely and reinstalled CM7.2. The high CPU utilization condition persists.
I didn't see this problem with the previous builds of CM7.2.
Any ideas on what is causing "system_server" to run constantly?
-John
User 21%, System 78%, IOW 0%, IRQ 0%
User 0 + Nice 68 + Sys 247 + Idle 0 + IOW 0 + IRQ 0 + SIRQ 0 = 315
PID CPU% S #THR VSS RSS PCY UID Name
292 96% S 63 246264K 59184K fg system system_server
20490 2% R 1 940K 396K bg root top
246 0% S 3 2780K 268K fg compass /system/bin/akmd
4 0% S 1 0K 0K fg root watchdog/0
5 0% S 1 0K 0K fg root events/0
JohnC60 said:
I'm running CM7.2 (2/10/2012) and the phone is experiencing high CPU utilization. Using top, I see that process "system_server" is constantly running at greater than 90%. I've rebooted the phone. I have also wiped it completely and reinstalled CM7.2. The high CPU utilization condition persists.
I didn't see this problem with the previous builds of CM7.2.
Any ideas on what is causing "system_server" to run constantly?
-John
User 21%, System 78%, IOW 0%, IRQ 0%
User 0 + Nice 68 + Sys 247 + Idle 0 + IOW 0 + IRQ 0 + SIRQ 0 = 315
PID CPU% S #THR VSS RSS PCY UID Name
292 96% S 63 246264K 59184K fg system system_server
20490 2% R 1 940K 396K bg root top
246 0% S 3 2780K 268K fg compass /system/bin/akmd
4 0% S 1 0K 0K fg root watchdog/0
5 0% S 1 0K 0K fg root events/0
Click to expand...
Click to collapse
I have been running this since an hour after being posted and am having no problems as you describe. Did you update from another rom and not do the standard wipes for a clean install?
The problem does not happen right away but, once it does start, it will not go away.
I had installed this build back on 2/11. Things were fine then also but one day, I noticed that my battery was draining faster than usual and also noticed that the CPU speed was stuck at 806MHz (it normally spends most of its time at 245MHz). I found "system_server" stuck at 95%+ CPU utilization. I rebooted several times with no luck in clearing the problem. So...
I re-installed CM7.2 (build 2/10) last night along with all my apps. No problems. Then a short while ago, I notice that things were a bit sluggish and sure enough "system_server" is at high CPU. And now, it will not go away.
For the CM7.2 installations, I do a full wipe and re-format system partition so it is a very clean installation.
-John
I haven't had this issue and I've been running a clean install of the 2/10 build for several days.
Are you using DC's kernel?
No, everything vanila CM.
-John
Well. It's the HTC GPS libs. I put back the orginal CM7.2 "gps.liberty.so" and the high CPU is gone.
-John
I'm using the HTC stock GPS libs as well, although I haven't used the GPS extensively since updating.
The older HTC GPS library is not playing nice with CM7.2's librpc.so. I dragged in the stock HTC version of librpc.so and that resolved the high CPU issue.
To use the HTC GPS libs, it looks like these three older files are needed:
/system/lib/hw/gps.liberty.so
/system/lib/libgps.so
/system/lib/librpc.so
-John
JohnC60 said:
The older HTC GPS library is not playing nice with CM7.2's librpc.so. I dragged in the stock HTC version of librpc.so and that resolved the high CPU issue.
To use the HTC GPS libs, it looks like these three older files are needed:
/system/lib/hw/gps.liberty.so
/system/lib/libgps.so
/system/lib/librpc.so
-John
Click to expand...
Click to collapse
Oh, I see, you were just manually replacing the files. There are some flashable zips that include all the correct files that simplify the process here:
http://forum.xda-developers.com/showpost.php?p=19106745&postcount=3688
I've installed manually on purpose. I wanted to keep as many of the current CM7.2 libs as possible.
-John
JohnC60 said:
I've installed manually on purpose. I wanted to keep as many of the current CM7.2 libs as possible.
-John
Click to expand...
Click to collapse
The three files that you mentioned are the only ones that are different. The rest are identical.
Battery drain
Hello guys,
I'm definitely trying this since im having issues with extreme battery drain but my issues are related to the display, i think, because I notice that the battery drains really fast while the display is on but if its off it lasts pretty long.
Anyone else experiencing this issue?
Yes. Ever since 2.3.4 or so, the battery drains absurdly fast with screen on. I'm talking 1.5 to 2% a minute.
drumist said:
The three files that you mentioned are the only ones that are different. The rest are identical.
Click to expand...
Click to collapse
"libc.so" and "liblog.so" are also different. However, the current files from CM7.2 seem to work just fine with the older stock HTC GPS libs.
-John
hi2u2 said:
Yes. Ever since 2.3.4 or so, the battery drains absurdly fast with screen on. I'm talking 1.5 to 2% a minute.
Click to expand...
Click to collapse
Is the brightness turned down or is set to auto? It make a big difference to kick the brightness down.
-John
JohnC60 said:
"libc.so" and "liblog.so" are also different. However, the current files from CM7.2 seem to work just fine with the older stock HTC GPS libs.
-John
Click to expand...
Click to collapse
Hmm, you're right. Sorry about that, I must have been comparing the wrong files earlier.
hi2u2 said:
Yes. Ever since 2.3.4 or so, the battery drains absurdly fast with screen on. I'm talking 1.5 to 2% a minute.
Click to expand...
Click to collapse
true, but strangely, when using sense-based ROMs, the battery is quite good
I've been fighting on and off wih horrible battery life with this phone ever since I got it. The past 2 months have been horrific. There's just no way of getting deep sleep not using battery. I usually lose about 30-40% over night. I have no idea what the culprit could be.
I don't have the usual culprits installed; Facebook, Google+, Google Search, etc. I have greenify installed and pretty much hybernating anything that I don't use all the time; Gmail, whatsapp.
I've tried countless factory resets. Something, some app is killing my battery. Gsam battery monitor claims Android OS has been awake the most, sent/received some data. Android System says some 1.5h sensor time was used, out of 8h the phone was sleeping doing nothing.
I am at my wits end here. Running CloudyStock 2.5 with simple kernel V6(tried all kernels there are, always the same thing).
HTML:
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Nov 8, 2014 9:33:58 AM
Usage Details
CPU Usage:24m 57s
CPU Usage (Background Only):24m 57s
Keep Awake:1h 22m 8s
Bytes Sent:147.53 KB
Bytes Received:666.28 KB
App UID:0
Wakelock Detail
Included Packages
Included Processes
kworker/u:2H
irq/289-wcd9xxx
migration/3
kworker/u:30
migration/2
vold
migration/1
file-storage
dhd_rxf
jbd2/mmcblk0p25
kthreadd
irq/170-msm_sdc
jbd2/mmcblk0p21
jbd2/mmcblk0p22
bdi-default
ngd_msm_ctrl_ng
kworker/u:1H
debuggerd
kworker/u:22
kworker/u:21
kworker/u:20
kworker/u:26
kworker/u:25
kworker/u:24
kworker/u:23
mmcqd/1rpmb
mdss_fb0
kworker/u:29
jbd2/mmcblk0p14
system
kworker/u:27
kworker/u:28
wl_event_handle
kworker/0:2H
kswapd0
/init
cfinteractive
irq/315-s3404
kcdrom-storaged
kworker/1:3
kworker/1:2
kworker/1:1
flush-179:0
kworker/1:0
kworker/u:3H
healthd
khubd
kworker/3:0H
kworker/u:4H
kworker/3:1
kworker/3:2
dhd_dpc
kworker/3:0
sync_supers
kworker/u:4
kworker/u:3
kworker/u:6
kworker/u:5
kworker/u:8
kworker/u:7
kworker/u:9
kworker/0:4
kworker/u:0
kworker/0:0
kworker/3:1H
kworker/0:1
kworker/u:2
kworker/0:2
kworker/u:1
kworker/0:3
daemonsu:mount:master
daemonsu:master
kworker/1:1H
bnrd
ueventd
dhd_watchdog_th
kworker/2:1H
ksoftirqd/0
ksoftirqd/1
kworker/1:0H
ksoftirqd/2
flush-0:19
ksoftirqd/3
mmcqd/1
kworker/0:1H
netd
zygote
kworker/2:0H
kworker/u:19
kworker/u:18
kworker/u:17
daemonsu:10109
thermal-engine
kworker/u:16
logwrapper
kworker/u:10
kworker/u:11
jbd2/mmcblk0p31
jbd2/mmcblk0p30
kworker/u:14
kworker/u:15
kworker/u:12
kworker/u:13
kworker/2:1
kworker/u:0H
kworker/2:0
kworker/0:0H
jbd2/mmcblk0p35
jbd2/mmcblk0p34
kworker/2:2
I flashed 20D last weekend. I did absolutely nothing on it, no root, nothing. Only whatsapp installed. For 2 days, my battery was fantastic. 48h, 4h screen time on a single charge. Next charge was again horrible, lost 30% overnight. I charged again and stil the same, deep sleep drain. Like I said I did nothing to the phone, only whatsapp installed and some music downloaded with Play Music. This morning I again went back to full stock and I'm having good battery time(but there's nothing on the phone).
I somehow think my internal memory is messed up. I believe once I download stuff and start filling up my storage, my battery goes to crap.
Got my phone back from the service center. Replaced battery. I'm happy cause know I know, I wasn't crazy.
My Nexus 6P lately has been getting really slow after being on for a few days. I ran:
Code:
adb shell
top -m 20 -s rss
And I think it looks unusual that my 'logd' is spinning out of control like this:
Code:
User 6%, System 48%, IOW 10%, IRQ 1%
User 90 + Nice 28 + Sys 928 + Idle 641 + IOW 193 + IRQ 17 + SIRQ 17 = 1914
PID PR CPU% S #THR VSS RSS PCY UID Name
348 3 0% S 7 1263224K 947564K bg logd /system/bin/logd
4866 3 1% S 110 2439336K 131284K fg system system_server
16227 0 0% S 20 1698620K 124780K fg system com.android.settings
6114 2 0% S 47 1725224K 115604K fg u0_a27 com.android.systemui
19588 0 0% S 33 2253364K 89148K bg u0_a29 com.google.android.googlequicksearchbox
7176 0 0% S 238 1826080K 82560K fg u0_a280 com.fitbit.FitbitMobile
14869 1 0% S 100 1723796K 74144K fg u0_a12 com.google.android.gms.persistent
22388 0 1% S 53 1692288K 64760K bg u0_a175 com.facebook.orca
23633 0 2% S 66 1824088K 61444K bg u0_a79 com.facebook.katana
13291 1 0% S 59 1773460K 57124K fg u0_a12 com.google.android.gms
Code:
logcat -g
main: ring buffer is 256Kb (556Mb consumed), max entry is 5120b, max payload is 4076b
system: ring buffer is 256Kb (33Mb consumed), max entry is 5120b, max payload is 4076b
crash: ring buffer is 256Kb (36Kb consumed), max entry is 5120b, max payload is 4076b
Does anyone knows what this means and how I can stop it from happening? It is ruining an otherwise great phone.
Intro:
I wanted some way to limit the charge level on my Pixel XL. I tried the BatteryChargeLimit app, but it never worked properly. Soon realized I could so the same thing as the app using Tasker after looking around in /sys/class/power_supply/battery folder.
This guide should work on all Pixel and Nexus devices. Can be adopted to other devices (See BatteryChargeLimit thread)
Why:
Not charging to 100% should in theory extend battery life. This study is starting to get outdated.
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
Prerequisites:
1. Root Access
2. Tasker
How to:
1. Open Tasker. Add a new profile. Name it whatever you want. Select State -> Power -> Power. Keep "Any" selected as Source.
2. Add Enter Task
Code:
No Charge (6)
Run Both Together
<Get Charging Source>
A1: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/charging_source
cat /sys/class/power_supply/battery/charging_source Timeout (Seconds):0 Use Root:eek:n Store Output In:%PluggedIn Store Errors In: Store Result In: Continue Task After Error:eek:n ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "0" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: Continue Task After Error:eek:n ] If [ %BATT > 79 ]
A3: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A4: Goto [ Type:Action Number Number:1 Label: ] If [ %PluggedIn neq 0 ]
3. Add Exit Task
Code:
Charge (14)
Run Both Together
A1: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "1" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: Continue Task After Error:eek:n ]
4. Long click on Profile and select Properties. Uncheck: Enforce Task Order"
5. Save everything and test it out.
How it works:
1. Enter task checks /sys/class/power_supply/charging_source to see if phone is plugged in and stores the value in a variable (%PluggedIn).
2. Writes "1" or "0" to /sys/class/power_supply/battery_charging_enabled depending on the battery level.
3. Waits 1 minute.
4. Goes back to top and runs everything over again is variable (%PluggedIn) doesnt equal 0.
Known Issues:
1. Phone could go maybe 1% over defined limit in the 60 seconds before the task runs again. Try changing the wait time to 45 or 30 seconds if this bothers you.
Misc Information and rambling:
1. I used 80% charge limit in my example. Just change it to whatever you want.
2. Having the phone check this every 60 seconds is not a big deal. The phone never sleeps when plugged in anyways. The Profile exits and nothing runs when phone is not plugged in.
3. /sys/class/power_supply/battery/charging_source
0 = Not plugged in
1 = USB
2 = A/C
4. /sys/class/power_supply/battery/constant_charge_current_max
Default value: 1600000
This is 1.6 amps constant charge. You could increase/decrease this number. I tested 2.0 amps and 1.0 amps. Could have your phone only charge at 1.0 amp, even when plugged into the factory charger.
Contributions:
sriharshaarangi
I am no longer monitoring or updating this guide. If you poke around in sys/class/power_supply/ you can most likely modify this basic script for any phone.
FYI to help anyone else.
On my Galaxy Note 4 with Modest.Rom.v6
i don't have the file "charging_source" under /sys/class/power_supply/battery/
but I do have:
"batt_charging_source" which has a value of "4" when charging by USB and "1" when not charging/connected
and
no "battery_charging_enabled" but instead the file "status" which has a value of "Charging" while charging by USB and "Discharging" when not connected.
---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------
isuelt1 said:
FYI to help anyone else.
no "battery_charging_enabled" but instead the file "status" which has a value of "Charging" while charging by USB and "Discharging" when not connected.
Click to expand...
Click to collapse
Maybe "wc_enable" would be the right file to change since I don't have "battery_charging_enabled" ??
Aaron1017 said:
Intro:
I wanted some way to limit the charge level on my Pixel XL. I tried the BatteryChargeLimit app, but it never worked properly. Soon realized I could so the same thing as the app using Tasker after looking around in /sys/class/power_supply/battery folder.
This guide should work on all Pixel and Nexus devices. Can be adopted to other devices (See BatteryChargeLimit thread)
Why:
Not charging to 100% should in theory extend battery life.
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
Prerequisites:
1. Root Access
2. Tasker
How to:
1. Open Tasker. Add a new profile. Name it whatever you want. Select State -> Power -> Power. Keep "Any" selected as Source.
2. Add Enter Task
Code:
No Charge (6)
Run Both Together
<Get Charging Source>
A1: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/charging_source
cat /sys/class/power_supply/battery/charging_source Timeout (Seconds):0 Use Root:eek:n Store Output In:%PluggedIn Store Errors In: Store Result In: Continue Task After Error:eek:n ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "0" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: Continue Task After Error:eek:n ] If [ %BATT > 79 ]
A3: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A4: Goto [ Type:Action Number Number:1 Label: ] If [ %PluggedIn neq 0 ]
3. Add Exit Task
Code:
Charge (14)
Run Both Together
A1: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "1" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: Continue Task After Error:eek:n ]
4. Long click on Profile and select Properties. Uncheck: Enforce Task Order"
5. Save everything and test it out.
How it works:
1. Enter task checks /sys/class/power_supply/charging_source to see if phone is plugged in and stores the value in a variable (%PluggedIn).
2. Writes "1" or "0" to /sys/class/power_supply/battery_charging_enabled depending on the battery level.
3. Waits 1 minute.
4. Goes back to top and runs everything over again is variable (%PluggedIn) doesnt equal 0.
Known Issues:
1. Phone could go maybe 1% over defined limit in the 60 seconds before the task runs again. Try changing the wait time to 45 or 30 seconds if this bothers you.
Misc Information and rambling:
1. I used 80% charge limit in my example. Just change it to whatever you want.
2. Having the phone check this every 60 seconds is not a big deal. The phone never sleeps when plugged in anyways. The Profile exits and nothing runs when phone is not plugged in.
3. /sys/class/power_supply/battery/charging_source
0 = Not plugged in
1 = USB
2 = A/C
4. /sys/class/power_supply/battery/constant_charge_current_max
Default value: 1600000
This is 1.6 amps constant charge. You could increase/decrease this number. I tested 2.0 amps and 1.0 amps. Could have your phone only charge at 1.0 amp, even when plugged into the factory charger.
Contributions:
sriharshaarangi
Click to expand...
Click to collapse
I've followed your directions and it works for the most part. It will automatically charge up to 80% when plugged in, however if the battery level is higher than 80% ( for example, if you charge it to 85% with device off or something and then turn it on while plugged in, , it will not charge any higher than 85% but it will not drop below 85% either... Even if the threshold is set at 80%). Not sure if my explanation makes sense.
Dollyllama said:
I've followed your directions and it works for the most part. It will automatically charge up to 80% when plugged in, however if the battery level is higher than 80% ( for example, if you charge it to 85% with device off or something and then turn it on while plugged in, , it will not charge any higher than 85% but it will not drop below 85% either... Even if the threshold is set at 80%). Not sure if my explanation makes sense.
Click to expand...
Click to collapse
Explanation makes sense and seems like expected behavior. No current is flowing to/from the battery. Phone maintaining power from source and not using the battery.
There might be a way to get the battery level to drop, but have not investigated.
Aaron1017 said:
Explanation makes sense and seems like expected behavior. No current is flowing to/from the battery. Phone maintaining power from source and not using the battery.
There might be a way to get the battery level to drop, but have not investigated.
Click to expand...
Click to collapse
I'm happy with it. Thank you for sharing it! It does what I need it to do. I first imported your xml (and it worked fine), but then I erased everything and manually programmed it into tasker to better understand the process. I set my threshold at 77% so I don't go above 78%. Works perfectly.
The only issue (and it's not even really an issue if you're aware of it is that if you reboot your phone while it is plugged in, it will charge all the way to 100% without applying the profiles. Need to manually drain the phone to below your threshold before plugging it back in...otherwise it just maintains the battery percent at whatever it is even though it is higher than what you defined.
Great guide, thank you!
One issue though, any idea why once I unplug my phone, the battery level drops to "0%", until I reboot it?
Edit: correction, stays at "0%" even after a soft reboot. Full reboot reflects accurate battery level.
Dollyllama said:
I'm happy with it. Thank you for sharing it! It does what I need it to do. I first imported your xml (and it worked fine), but then I erased everything and manually programmed it into tasker to better understand the process. I set my threshold at 77% so I don't go above 78%. Works perfectly.
The only issue (and it's not even really an issue if you're aware of it is that if you reboot your phone while it is plugged in, it will charge all the way to 100% without applying the profiles. Need to manually drain the phone to below your threshold before plugging it back in...otherwise it just maintains the battery percent at whatever it is even though it is higher than what you defined.
Click to expand...
Click to collapse
Droid_JD said:
Great guide, thank you!
One issue though, any idea why once I unplug my phone, the battery level drops to "0%", until I reboot it?
Edit: correction, stays at "0%" even after a soft reboot. Full reboot reflects accurate battery level.
Click to expand...
Click to collapse
Works fine here on my pixel XL stock with Magisk 14.0. Don't see the behavior you speak of. Maybe try importing the scripts again?
Sent from my Very Silver Pixel XL 128GB
mochamoo said:
Works fine here on my pixel XL stock with Magisk 14.0. Don't see the behavior you speak of. Maybe try importing the scripts again?
Sent from my Very Silver Pixel XL 128GB
Click to expand...
Click to collapse
I couldn't get it to import, so I just followed the directions to create the profiles.
Sent from my Pixel XL using Tapatalk
Hi dude!
I have one Huawei Nova and I'm rooted with Magisk.
I followed your steps, but changed the value to 89% and had to change the file which I have to cat, because I don't have the same as you.
I tried 2 files to cat the stat of charging/discharging:
charge_type
status
Both inside /sys/class/power_supply/battery/
charge_type give me 'N/A' when not charging and 'fast' when charging via usb/wall (I didn't test when phone is set to share files with PC, maybe it has a 'slow' value).
status give me 'discharging' or 'charging'.
I ended up using file status and setting PluggedIn neq Discharging
Everything is working fine[emoji16]
Thanks for sharing
Enviado de meu HUAWEI CAN usando Tapatalk
Great work Aaron1017!
Now one thing that's missing and wasn't working for me with BCL after upgrading to Oreo is resetting application battery usage statistics (Settings -> Battery).
Does anybody know how to add that?
I had both "battery_charging_enabled" and just "charging_enabled"
Had to change it to "charging_enabled" instead. I'm on 8.1 DP, so I imagine that could be why, and I'd imagine there's a good chance it will change to that in the final version. I just started using this, so maybe it already changed on 8.0. Just giving some info for people trying to get it to work, or who it May stop working for after an update.
Works great though... Thanks
Disregard
Ric G said:
Any updates for 8.1?
It's not working for me, as it went past 80%.
Also, I was unable to find the tweaks for amperage.
Thanks!
Click to expand...
Click to collapse
Still working as before on my pixelXL on 8.1. mine is set at 70%.
Thanks for posting this! The other method doesn't work on HTC phones. Question. I am thinking of trying this for my HTC 9 and HTC 10. I use the phone during the day as a tethering device. If this works would it still keep the tethering connection alive and well?
Works perfectly on my 10 but I don't use tethering, can't see that it would be affected though..
Just imported in the xml documents and gave it a try, doesn't work on HTC m9 running ViperRom.
I would like this task to only run Sunday through Wednesday nights. on Thursday, Friday, and saturday I'd like a full charge because I use my phone more on the weekends when I'm home. How do I do that when the profile is being triggered off a state? I need it to trigger off a state AND time.
I tried this task last night and it didn't work. Just to make sure I copied everything correctly here is my exported description:
Profile: Charge Limit (27)
State: Power [ Source:Any ]
Enter: No Charge (25)
Run Both Together
<Get Charging Source>
A1: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/charging_source
cat /sys/class/power_supply/battery/charging_source Timeout (Seconds):0 Use Rootn Store Output In:%PluggedIn Store Errors In: Store Result In: Continue Task After Errorn ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "0" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: Continue Task After Errorn ] If [ %BATT > 85 ]
A3: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A4: Goto [ Type:Action Number Number:1 Label: ] If [ %PluggedIn neq 0 ]
Exit: Charge (23)
Run Both Together
A1: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "1" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: Continue Task After Errorn ]
Schroeder09 said:
I tried this task last night and it didn't work. Just to make sure I copied everything correctly here is my exported description:
Profile: Charge Limit (27)
State: Power [ Source:Any ]
Enter: No Charge (25)
Run Both Together
<Get Charging Source>
A1: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/charging_source
cat /sys/class/power_supply/battery/charging_source Timeout (Seconds):0 Use Rootn Store Output In:%PluggedIn Store Errors In: Store Result In: Continue Task After Errorn ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "0" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: Continue Task After Errorn ] If [ %BATT > 85 ]
A3: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A4: Goto [ Type:Action Number Number:1 Label: ] If [ %PluggedIn neq 0 ]
Exit: Charge (23)
Run Both Together
A1: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ]
A2: Run Shell [ Command:su
chmod 666 /sys/class/power_supply/battery/battery_charging_enabled
echo "1" > /sys/class/power_supply/battery/battery_charging_enabled Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: Continue Task After Errorn ]
Click to expand...
Click to collapse
What phone?
Sent from my Very Silver Pixel XL 128GB
Pixel 2 XL