Related
I've been banging this dilemma against search boxes for a couple days now and just can't figure out how to accomplish this gracefully. My goal is to have a profile based on power state to sign in and out of Google Talk. I just got the HTC Thunderbolt last week and after testing battery under various conditions I found that GTalk was causing over 5%/hour power consumption when running compared to less than 1%/hour when not running with normal phone usage.
So I have a context with the Power Source = Any and a the Locale Execute task (can't figure out how to replicate this in the native Component Intent task):
Code:
/system/bin/am start -a android.intent.action.MAIN -n com.google.android.talk/com.google.android.talk.SigningInActivity
This works great to start GTalk when the phone is plugged in to AC/USB power.
Now my problem is how to gracefully sign out of GTalk when the device goes back to battery power (and rely on GTalk Offline Emails to manually sign-in as needed). There is no SigningOutActivity and I don't even know if using am start command is appropriate for this. Watching logcat during a manual signout procedure did not illuminate what might be occurring in the background and how I would accomplish this.
This might help: http://www.jeffmixon.com/programmatically-sign-google-talk-android/:
Code:
am start -a android.intent.action.MAIN -n com.google.android.talk/com.google.android.talk.SignoutActivity -d content://com.google.android.providers.talk/accounts
How would you put this into Tasker? Would it go in as a script?
Have you ever tried having your phone lay on a table for some time and when you come back to pick it up, it had almost burned through the table because of the battery heat do to an app running the CPU on a constant 100%?
Or have you tried waking up two hours to late for work, because you alarm did not go off do to the phones battery running dry during the night?
Bad applications or problems with some back-end processes is a problem for most people. To get some help with this problem, I have been running the Watchdog app for the last 3 years. It is a great application that will alert you whenever an app or a process is running wild in the background. However there is one issue with this app. It only alerts you when there is a problem. This does not help much if you are to far away from the phone, if your phone is in silent mode or if you are sleeping.
I wrote the developer of the app to see if there was any plans for making a tasker plug-in so that profiles can be made to handle this. I have yet to get an answer. In the mean time, I have made a complete watchdog profile for tasker that does what the watchdog app does, only this profile will auto terminate any wild processes if the screen is turned off. If the screen is on, it will to what the watchdog app does and alert you of the problem. It could be that you was playing a game or running a benchmark, so auto terminate while the screen is on, would not be a good idea.
The profile however, will drain more battery than the watchdog app does. Because of this I have set the check interval for 15 minutes instead of the 5 minutes I used on the app. This reduces the drain to about the same amount.
And to save even more power, I have included a Data control profile that will turn off data/wifi/sync when the screen is off, as long as you are not connected to a power source or if you are downloading, uploading or streaming. In this case the profile will wait until this state changes before turning off anything. And while off, tasker will alow sync (email and such) once every 15 minutes.
Both profiles is included in the attached download below.
Important!
The watchdog profile will need a proper busybox installed with proper symlinks for sed, grep and awk. It will also need a toolbox that supports top and ps with arguments.
You can run the update script from the Busybox Installer thread to make sure that your phone will work with this profile.
Changelog (2012-11-18)
Reduced the time from where the screen turns off, to the time Data/Sync is disabled
Data/Sync will now turn back on when the screen is unlocked rather than turned on. No need to waste power if you just want to check the time or notifications (Which can be done from lock screen in Android 4.x)
Fixed the 15 minutes data check when the screen is off. It only executed once after the screen was turned off
_______________________
Wow! Your watchdog implementation looks great! Will adopt it on my phone over the weekend.
Now I have only one battery-drain-controlling dream left - being able to find out the apps holding the wakelock for too long to kill them automatically. The reason for this is that sometimes I find battery drain to go from usual 1% per hour to 10% per hour just because some badly written app has not released the wakelock.
Alte.78 said:
Wow! Your watchdog implementation looks great! Will adopt it on my phone over the weekend.
Now I have only one battery-drain-controlling dream left - being able to find out the apps holding the wakelock for too long to kill them automatically. The reason for this is that sometimes I find battery drain to go from usual 1% per hour to 10% per hour just because some badly written app has not released the wakelock.
Click to expand...
Click to collapse
Are you talking about BetterBatteryStats? I know that it tells you exactly how long since a point in time (which can be manually customized) that certain programs/tasks hold wakelocks.
But not sure about any kind of specific stratification that displays only programs that hold the lock too long to kill them automatically (assuming that's what you are wanting?).
And OP, these sound great - I'm importing them as we speak :highfive:
dk_zero-cool said:
Important!
The watchdog profile will need a proper busybox installed with proper symlinks for sed, grep and awk. It will also need a toolbox that supports top and ps with arguments.
_______________________
Click to expand...
Click to collapse
I got all excited when reading about this until I read the Important section. After watchdog everything started getting confusing . I know I read somewhere about busybox but the other terms are all new to me...could someone explain it with a little more details on what I have to get/set up in order for this to work??
2am said:
I got all excited when reading about this until I read the Important section. After watchdog everything started getting confusing . I know I read somewhere about busybox but the other terms are all new to me...could someone explain it with a little more details on what I have to get/set up in order for this to work??
Click to expand...
Click to collapse
The profile is using some linux commands to get a list of all current processes and their CPU usage. These commands needs to be available in order for the profile to work.
If you are using a custom ROM, then you are most likely to have all what is needed. Especially if you are using a more current custom ROM.
In order to test this, download a terminal app or enter an ADB shell (Hope you know what this is) and see if the command line
Code:
top -n 1 | sed -e 1,7d | grep -e '[0-9]\+%' | awk '{print $3}'
returns anything. If it does (Except errors), then you will have all that is needed.
Alternatively you could check my Better Busybox Integration thread which will make sure that your phone is setup to work with this.
dk_zero-cool said:
The profile is using some linux commands to get a list of all current processes and their CPU usage. These commands needs to be available in order for the profile to work.
If you are using a custom ROM, then you are most likely to have all what is needed. Especially if you are using a more current custom ROM.
In order to test this, download a terminal app or enter an ADB shell (Hope you know what this is) and see if the command line
Code:
top -n 1 | sed -e 1,7d | grep -e '[0-9]\+%' | awk '{print $3}'
returns anything. If it does (Except errors), then you will have all that is needed.
Alternatively you could check my Better Busybox Integration thread which will make sure that your phone is setup to work with this.
Click to expand...
Click to collapse
well I entered that command and got
invalid argument "-n". and then a bunch of other lines after that...and I checked your other thread and there's even more code language ...ugh, I think this is one of those threads that I need to leave alone because it's too much for me to handle...sucks too cause your set up sounds really awesome...thanx for trying to help me though
2am said:
well I entered that command and got
invalid argument "-n". and then a bunch of other lines after that...and I checked your other thread and there's even more code language ...ugh, I think this is one of those threads that I need to leave alone because it's too much for me to handle...sucks too cause your set up sounds really awesome...thanx for trying to help me though
Click to expand...
Click to collapse
I will make a more simple command fix for you tomorrow that will make your phone work with this without having you enter any code.
dk_zero-cool said:
I will make a more simple command fix for you tomorrow that will make your phone work with this without having you enter any code.
Click to expand...
Click to collapse
ah thank you soo much!!!
2am said:
ah thank you soo much!!!
Click to expand...
Click to collapse
I have updated the Busybox Installer script to make sure that it will work on newer devices other than MTD, and I have added a custom toolbox binary that will contain the proper options for these profiles.
Just check the first post at the buttom in the Important section. Fallow the link, download the installer and run it in your recovery. After that you can import the profiles from this thread into your Tasker application.
I originally found the fix in the SuperCharger Thread when I found that my Flush-O-Matic script wasn't working properly on my Sony Z1.
See original posting here.
zeppelinrox said:
Hey I realized yesterday that Flush O Matic doens't work properly on newer kernels.
Well it works, but it doesn't wait for the screen to go off before flushing.
A little googlie told me that the newer kernels no longer have the /sys/power/wait_for_fb_sleep file.
Normally, FOM will try and read it's contents (but it's unreadable) and it just hangs until the device goes to sleep.
When it goes to sleep, that file can be read and the script gets "unhung" and flushes.
And when the file is missing, well FOM will just spit out errors (check the log) and dump cache without uh... waiting for the fan to be turned on...
BUTT (yeah, thats a big butt!) I fingered out another way for newer kernels... heh.
Check it via PC... with the screen on do this
Code:
adb shell
su
while [ "`cat /sys/class/graphics/fb0/dynamic_fps`" ]; do sleep 1; done; echo " OK Flush Time!"
Who's your daddy!? LOL
While the screen is on it should hang there until you turn off the screen.
When the screen goes off, it will pronounce what "time" it is...
I'll probably do sleep 10 instead of sleep 1 tho to minimize battery suckage.
Click to expand...
Click to collapse
This fix would be applicable to various scripts on xda that will get outdated due to the missing wait_for_fb_sleep/wake files on some device/kernel combinations.
Currently effected hardware, that I'm aware so far: some Sony, Moto and Nexus devices using kernel version 3.3 or above.
These scripts change things or do things depending on whether the screen turns off or turns on.
Examples are cpu governor scripts or other screen state scaling scripts.
As mentioned above, it had effected my FOM script which dumps caches at a user defined interval.
However, when the time is up, it will actually wait until the screen is off if the screen happens to be on at the time.
So if you have a misbehaving script due to the missing /sys/power/wait_for_fb_sleep/wake files, you should have 2 other files that you can use.
1. /sys/class/graphics/fb0/dynamic_fps
2. /sys/class/graphics/fb0/show_blank_event
File contents with screen off:
Code:
[email protected]:/ $ cat /sys/class/graphics/fb0/dynamic_fps
[email protected]:/ $ cat /sys/class/graphics/fb0/show_blank_event
panel_power_on = 0
[email protected]:/ $
File contents with screen on:
Code:
[email protected]:/ $ cat /sys/class/graphics/fb0/dynamic_fps
60
[email protected]:/ $ cat /sys/class/graphics/fb0/show_blank_event
panel_power_on = 1
[email protected]:/ $
So when the screen is off, dynamic_fps is empty but has a value (60 in my case) when the screen is on.
I preferred to take advantage of that file.
However some may like to use the contents of show_blank_event and check whether panel_power_on = 0 (off) or panel_power_on = 1 (on).
Of course, a script will have to check and decide whether to use the wait_for_fb_sleep file or use the new way.
So a fixed script will look something like:
Code:
if [ -f "/sys/power/wait_for_fb_sleep" ]; then
echo "Android is now `cat /sys/power/wait_for_fb_sleep`!"
else while [ "`cat /sys/class/graphics/fb0/dynamic_fps`" ]; do sleep 10; done
echo "Android is now sleeping!"
fi
So if that code is ran when the screen is on, when the screen is off, the output would be Android is now sleeping! and it won't matter if you have the wait_for_fb_sleep file
Alternately, to do something when the screen turns on...
Code:
if [ -f "/sys/power/wait_for_fb_wake" ]; then
echo "Android is now `cat /sys/power/wait_for_fb_wake`!"
else while [ ! "`cat /sys/class/graphics/fb0/dynamic_fps`" ]; do sleep 10; done
echo "Android is now awake!"
fi
Of course, when the screen comes on, the output will be Android is now awake!
I used sleep 10 so that it doesn't do any needless work.
Of course sleep 1 would give an instant reaction but isn't very battery or cpu friendly.
You can decide for yourself how long is a good sleep interval between checks.
Anyhow, hope that helped
Nice! Will try on my VU
sent from my LG-P895 using Tapatalk bajakan
Thank you
I wanted this to implement a small idea of mine ,also scanned through the 11k+ lines from supercharger script but couldn't find screen off thingy
Yeah,finding a small line in FastEngineFlush.sh also was hard
But this post helped!
The reason why your are called a XDA Scripting Genius! :good:
Really useful!
Madaditya said:
I wanted this to implement a small idea of mine ,also scanned through the 11k+ lines from supercharger script but couldn't find screen off thingy
Yeah,finding a small line in FastEngineFlush.sh also was hard
But this post helped!
The reason why your are called a XDA Scripting Genius! :good:
Really useful!
Click to expand...
Click to collapse
Whats your idea?
And yeah, even the flush script is rather complex lol
zeppelinrox said:
Whats your idea?
And yeah, even the flush script is rather complex lol
Click to expand...
Click to collapse
LOL yeah.
Wanted to make a background script that turns your data connection off on screen off + one minute and enables data on screen on.
Something close to Stamina mode in Sony Devices.
Reason,i face considerable battery drain on Custom roms,and a xperia user always misses Stamina mode
Madaditya said:
LOL yeah.
Wanted to make a background script that turns your data connection off on screen off + one minute and enables data on screen on.
Something close to Stamina mode in Sony Devices.
Reason,i face considerable battery drain on Custom roms,and a xperia user always misses Stamina mode
Click to expand...
Click to collapse
Nice idea!
Whats the command to disable data?
zeppelinrox said:
Nice idea!
Whats the command to disable data?
Click to expand...
Click to collapse
svc data enable/disble
for wifi:
svc wifi enable/disable
Madaditya said:
svc data enable/disble
for wifi:
svc wifi enable/disable
Click to expand...
Click to collapse
Oh nice.
You learned me something lol
I couldn't find /sys/class/graphics/fb0/show_blank_event or /sys/class/graphics/fb0/dynamic_fps or /sys/power/wait_for_fb_wake/sleep. Instead i am using this /sys/class/leds/lcd-backlight/brightness. 0 will mean screen is off, any other value for screen on. Thanks You could add this in OP
Hello everyone,
I have used so many times the XDA forums to find some answers and I have found mostly all the answers I needed on other threads. But for once, I might have a more complicated problem to submit to the experts on this forum.
My use case is to create the lightest app that can do a job (namely taking a picture) on a regular interval of time and consume the least battery possible to be able to run for the most time without external power source (that is to say, the phone plugged in a wall outlet).
From what I experienced so far, I managed to have my application run for about 10 straight days doing the job every 10 minutes on a rooted Moto G5 phone. To achieve this, I force the phone to go in Doze mode at the beggining, by calling :
Code:
dumpsys deviceidle force-idle
Doing that, I schedule my jobs using the AlarmManager with the "setExactAndAllowWhileIdle" method thus respecting the super-9 minutes window my alarms should respect in order to be triggered correctly while the phone gets in deep sleep (following the official documentation).
For the moment, this is working as expected, because when I make a bugreport and import it into the Battery Historian tool, I can see that the phone is awake only when my job is running (for around 1 minute) and all the rest of the time, the device is sleeping and even better when I look in logcat, the phone suspends the CPU's for most of the time, which is great to consume less battery when not needed.
Now comes my problem, in order to make the app run for a longer period of time without having a wall outlet nearby, AND without touching the phone, I want to extend my battery life by using an external power bank plugged into my phone. My problem is that I cannot manage to make the phone not be awake while charging the phone. I guess that the phone is keeping some kind of wakelock when charging, so the USB connection keeps the phone awake and make my phone consume 3x more than when it goes in deep sleep, suspending the CPUs and is not awake. I tried to put some flags in a lot of files in order to trick the phone to think nothing is connected to the USB port but it didn't work. I tried those files:
Code:
"echo 0 > /sys/class/power_supply/battery/charging_enabled"
"echo 0 > /sys/devices/virtual/android_usb/android0/enable"
"echo 0 > /sys/class/power_supply/usb/present"
"echo 0 > /sys/class/power_supply/usb/ch_present"
"echo 0 > /sys/class/power_supply/usb/online"
"echo 0 > /sys/class/android_usb/android0/enable"
"echo 0 > /sys/class/android_usb/android0/remote_wakeup"
The only thing that stops the charge is when I put a 0 in the following file:
Code:
"echo 0 > /sys/class/power_supply/battery/charging_enabled"
It effectively stops the charge but the CPUs are still in an "awake" state, meaning there is probably still a wakelock being kept.
Do you have any idea how can I do, only using software, other than what I tried to stop the phone from being awake while having a charger plugged in (even if not charging) ?
Thanks a lot in advance for your answers.
Hi,
I am Aurelien, a colleague of Rafouuuuuu. Some precisions:
We use a "always-on" battery.
Phone awake = cpu is not stopped.
According to the historian report, the wakeup reason is "unknown".
These lines:
Code:
"echo 0 > /sys/class/power_supply/usb/present"
"echo 0 > /sys/class/power_supply/usb/ch_present"
"echo 0 > /sys/class/power_supply/usb/online"
"echo 0 > /sys/class/android_usb/android0/enable"
disable usb connection and charge but the cpu is always on.
We try to stop adbd service (if adbd get a wakelock if usb plugged)
We try to disable developer option.
hello friend
Sorry for my bad engish
This is the best mod for your android mobile
Control your charger using this trick
Your charger has stop charging automatically in your setting type
For example - you set your device charge 90% this modul is stoped your charger after your device is charged 90%
You also controll charger using time paired like
30 minets
1h 30m etc.
How to install it -
1. Root your device with letest magisk root
2. Go to downlod option in magisk manager
3. Download "Magic charging switch" & install it then active it
4. Reboot your device
5. download terminal emulator
6. Type "su" & then type "mcs "
Its chek your device is supported /nonsupported
Now injoy ????
Commonds for using this modul--
- Run `su` first, ALWAYS -- or make sure `su -c` goes before `mcs` (i.e., `su -c mcs -e 30m`).
- Run `su` first, ALWAYS -- or make sure `su -c` goes before `mcs` (i.e., `su -c mcs -e 30m`).
mcs [-b] [-h] [-i] [-r] [-v] [debug] [-k LEVEL] [PAUSE% RESUME%] [PAUSE%] [-m PAUSE% RESUME%] [-s --enable/disable] [-t PAUSE% RESUME%] [-d %/TIMEOUT] [-e %/TIMEOUT] [-x /path/to/switch ON_key OFF_key]
`-b` --> reset battery stats on demand (does not work on all devices)
`-h` --> mcs usage instructions
`-i` --> display battery info
`-r` --> reset cs to its initial state
`-s` --> pause/resume, --enable/disable service
`-v` --> toggle extensive (loops) verbose
`-x` --> pick a different charging switch from the database
`debug` --> gather debugging data & save it to /sdcard/mcs_debug-DEVICE.log
just `mcs` --> run MCS with default/saved settings
`-k` LEVEL --> keep/maintain battery power at a constant LEVEL (pauses MCS service)
`PAUSE% RESUME%` --> pause charging at PAUSE% value (default 90); resume if battery drops below RESUME% (default 80). This is the `initial setup command`. If auto-run is OFF, the command works as is; else, new settings are saved and automatically picked up by MCS service.
`-m/-t PAUSE% RESUME%` --> generate automation config (-m for MacroDroid; -t for Tasker -- pick one)
`-d [%/TIMEOUT (optional)]` --> disable charging on demand (pauses MCS service)
`-e [%/TIMEOUT (optional)]` --> enable charging on demand (pauses MCS service)
`-x` /path/to/switch ON_key OFF_key -- > manually set a charging switch; if keys match one of the following as is or in reverse oder -- you don't have to specify them: 1/0, enable/disable, enabled/disabled, true/false, on/off, 100/3
### Usage Examples/Tips
`mcs 85` --> pause charging at 85%; resume when battery level is less or equal to 80% (default).
`mcs 80 20` --> pause charging at 80%; resume when battery level is less or equal to 20%.
`mcs -d` --> disable charging.
`mcs -e` --> enable charging.
`mcs -d 30m` --> keep charging disabled for 30 minutes
`mcs -e 1h` --> keep charging enabled for 1 hour).
`mcs -e 80%` --> Charge until battery level equals 80%.
`mcs -d 40%` --> Charge until battery level equals 40%.
`mcs -e 120 && mcs -d 30m && mcs -e 1h` --> charge for 120 seconds, pause for 30 minutes, then charge again for 1h.
`mcs -e 30m && mcs -d 30m && mcs -e 90%` --> charge for 30 minutes, pause for 30 minutes, then charge again, but this time until battery level is greater or equal to 90%.
`mcs -e 50% && mcs -d 5h && mcs -e 80% && mcs -d 30m && mcs -e 90%` --> charge until 50%, pause for 5 hours, charge until 80%, pause for 30 minutes, charge until 90%.
Ideally, you want your battery level between 40-60% - best, 20-80% - average, 10-90% - fair.
For best convenience, stick with mcs 90 80; mcs 80 70 for a perfect balance between convenience & battery wear. If you want the longest battery lifespan, use mcs 42 41 or mcs -k 42 (best for prolonged usage -- i.e., navigation).
mcs [-b] [-h] [-i] [-r] [-v] [debug] [-k LEVEL] [PAUSE% RESUME%] [PAUSE%] [-m PAUSE% RESUME%] [-s --enable/disable] [-t PAUSE% RESUME%] [-d %/TIMEOUT] [-e %/TIMEOUT] [-x /path/to/switch ON_key OFF_key]
`-b` --> reset battery stats on demand (does not work on all devices)
`-h` --> m cs usage instructions
`-i` --> display battery info
`-r` --> resetmccs to its initial state
`-s` --> pause/resume, --enable/disable service
`-v` --> toggle extensive (loops) verbose
`-x` --> pick a different charging switch from the database
`debug` --> gather debugging data & save it to /sdcard/mcs_debug-DEVICE.log
just `mcs` --> run MCS with default/saved settings
`-k` LEVEL --> keep/maintain battery power at a constant LEVEL (pauses MCS service)
`PAUSE% RESUME%` --> pause charging at PAUSE% value (default 90); resume if battery drops below RESUME% (default 80). This is the `initial setup command`. If auto-run is OFF, the command works as is; else, new settings are saved and automatically picked up by MCS service.
`-m/-t PAUSE% RESUME%` --> generate automation config (-m for MacroDroid; -t for Tasker -- pick one)
`-d [%/TIMEOUT (optional)]` --> disable charging on demand (pauses MCS service)
`-e [%/TIMEOUT (optional)]` --> enable charging on demand (pauses CS service)
`-x` /path/to/switch ON_key OFF_key -- > manually set a charging switch; if keys match one of the following as is or in reverse oder -- you don't have to specify them: 1/0, enable/disable, enabled/disabled, true/false, on/off, 100/3
### Usage Examples/Tips
`mcs 85` --> pause charging at 85%; resume when battery level is less or equal to 80% (default).
`mcs 80 20` --> pause charging at 80%; resume when battery level is less or equal to 20%.
`mcs -d` --> disable charging.
`mcs -e` --> enable charging.
`mcs -d 30m` --> keep charging disabled for 30 minutes
`mcs -e 1h` --> keep charging enabled for 1 hour).
`mcs -e 80%` --> Charge until battery level equals 80%.
`mcs -d 40%` --> Charge until battery level equals 40%.
`mcs -e 120 && mcs -d 30m && mcs -e 1h` --> charge for 120 seconds, pause for 30 minutes, then charge again for 1h.
`mcs -e 30m && mcs -d 30m && mcs -e 90%` --> charge for 30 minutes, pause for 30 minutes, then charge again, but this time until battery level is greater or equal to 90%.
`mcs -e 50% && mcs -d 5h && mcs -e 80% && mcs -d 30m && cs -e 90%` --> charge until 50%, pause for 5 hours, charge until 80%, pause for 30 minutes, charge until 90%.
Ideally, you want your battery level between 40-60% - best, 20-80% - average, 10-90% - fair.
For best convenience, stick with mcs 90 80; mcs 80 70 for a perfect balance between convenience & battery wear. If you want the longest battery lifespan, use mcs 42 41 or mcs -k 42 (best for prolonged usage -- i.e., navigation).
-Credit -
1. Magisk devlopers for make this
2. Me for shared this post
For mor info Go to my youtube channal
D-AZ Dinesh
And watch full toturial
Dont forget to thank ||
Where can I get zip file for this old magisk module
As it was updated as acc, it seems complicated to me
I had no problem with mcs or even older cs regarding setting up lower and upper limit
prajj said:
Where can I get zip file for this old magisk module
As it was updated as acc, it seems complicated to me
I had no problem with mcs or even older cs regarding setting up lower and upper limit
Click to expand...
Click to collapse
Yes exactly what i'm thinking!!
I'm perfect with MCS, ACC is just too complicated for my simple need.
Here i have it, it was fine till idk why i can't install it with latest magisk (19.3)
iiandskater said:
Yes exactly what i'm thinking!!
I'm perfect with MCS, ACC is just too complicated for my simple need.
Here i have it, it was fine till idk why i can't install it with latest magisk (19.3)
Click to expand...
Click to collapse
I had flashed with your .zip module but it throw me error "magisk_merge.img mount point not found".