If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
That's something I've been wondering how to do! kudos
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
Will this work for the older Pixel devices as well (such as my Pixel 4)? : o
Help The Peace said:
Will this work for the older Pixel devices as well (such as my Pixel 4)? : o
Click to expand...
Click to collapse
No reason why not looking at the command, give it a try
danw_oz said:
No reason why not looking at the command, give it a try
Click to expand...
Click to collapse
Sounds good. But will it also drain battery from then on? Or will it continually "charge" to keep it at 80%? And is your command an ADB command?
You can use this in Tasker with a "run shell" task when the device boots since this reverts to 100 if you ever reboot the device.
Does this command require root?
Other than prolonging the battery condition/longevity, is there another reason to set a charge limit?
Last question: The command stays in effect until reboot?
Thanks.
snovvman said:
Does this command require root?
Other than prolonging the battery condition/longevity, is there another reason to set a charge limit?
Last question: The command stays in effect until reboot?
Thanks.
Click to expand...
Click to collapse
I believe it does require a root, yes
I don't know any other benefit for limiting charge other than preserving the battery's long-term, overall health. Not allowing your battery to go too low or too high will help keep its maximum charge for a longer time
And yes, the setting will revert back to the default 100 after a reboot. I use Tasker to run the command on each boot, gotta love automation!
does limiting the charge affect the battery optimization algorithms?
thanks for this. if only every phone was this easy
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
Thank you!
For what it's worth, this works with the Battery Charge Limit [ROOT] app (XDA thread). Go into the app's settings, enable Configurable CTRL File Data, click Configure Control Data, click I Understand, paste "/sys/devices/platform/google,charger/charge_stop_level" (without quotes) in the Set Path to Desired File, and since this app expects you to set values for Enabled and Disabled, I set both to 75, since that's what I want my battery to charge up to.
If I start using an automation app like Tasker, then I can set it a different way, but I kinda like this app method anyway.
Edit:
Now I am using the Advanced Charging Controller (ACC) Magisk Module and the AccA app which is a front-end/GUI for configuring the module.
Forgive my ignorance I have not paid much attention to the forums over the last couple of years.
Is there a benefit to limiting the charge percent? is 90 the default recommendation?
dms76 said:
Forgive my ignorance I have not paid much attention to the forums over the last couple of years. Picked up a job where I can't slack and read ll day long.. LOL
Is there a benefit to limiting the charge percent? is 90 the default recommendation?
Click to expand...
Click to collapse
The point is to limit battery degradation. Tesla does it with their cars. Personally, I'd rather just have an alert to notify me and I use AccuBattery Pro for that. I rarely charge overnight but if I actually do, I let adaptive charging handle handle the slow charging.
nycdiplomat said:
You can use this in Tasker with a "run shell" task when the device boots since this reverts to 100 if you ever reboot the device.
Click to expand...
Click to collapse
i did that but it won't do anything. it still charges above my set value, so i was wondering.
what i did in tasker:
created a profile > event > system event > device boot
created a task > run shell > "echo 65 > /sys/devices/platform/google,charger/charge_stop_level"
i rebooted to make sure tasker was running (had battery optimization disabled on tasker), and tasker seems to run but it won't work. the "65" value was just set while i was testing it and since my phon was below 50% charge i did not want to wait that long so i started with 55, then 60 and so on. as i write this i'm waiting for it to hit 65% and hopefully stop charging. all i can think of is that i probably used the wron profile in tasker?
regards
roirraW edor ehT said:
Thank you!
For what it's worth, this works with the Battery Charge Limit [ROOT] app (XDA thread). Go into the app's settings, enable Configurable CTRL File Data, click Configure Control Data, click I Understand, paste "/sys/devices/platform/google,charger/charge_stop_level" (without quotes) in the Set Path to Desired File, and since this app expects you to set values for Enabled and Disabled, I set both to 75, since that's what I want my battery to charge up to.
If I start using an automation app like Tasker, then I can set it a different way, but I kinda like this app method anyway.
Click to expand...
Click to collapse
No problem!
Yeah for sure, that’s the beauty of android, there are several ways of going about things.
I use Tasker because that way it’s just one less app that I have on my phone. I like to have as many things inside of Tasker as possible to keep things organized and consolidated.
Although I’m currently back on iOS after being on Android for six years! I didn’t like the 6 Pro enough to keep it and I’m not going to get into details because there’s already a lot of hate threads for it - and I don’t want to add to that.
Let’s just say that I’ve been enjoying iOS more than I thought I would, especially considering I’ve been on android for so many years. So we’ll see what Google cooks up for the 7 series.
Anyways, back to topic, definitely going to miss Tasker for how much that can be done with it! The Shortcuts app on iOS is the closest thing to Tasker and it’s nowhere near as robust lol
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
does this work without root? i tried this using tasker but it did not work. how did u test it?
boxemall said:
does this work without root? i tried this using tasker but it did not work. how did u test it?
Click to expand...
Click to collapse
Yes, As far as root required.
boxemall said:
does this work without root? i tried this using tasker but it did not work. how did u test it?
Click to expand...
Click to collapse
You need root.
I just got one of these: https://chargie.org/
Seems to work well so far.
cmh714 said:
I just got one of these: https://chargie.org/
Seems to work well so far.
Click to expand...
Click to collapse
I have looked at them before but they seem very expensive for what they are, it is easier just to set a silent alarm for a few hours after you intend to get up.
Related
Screen Dimmer
The minimum screen brightness is too damn bright to use in the dark.
Run the app, click "Load" next to "n5dim", change your brightness to the minimum (and then up a bit and back down) and notice how much dimmer it is.
The brightness at all other levels stay the same.
Source: https://github.com/mzhou/n5dim
Fast Charge
This works by setting the registers on the bq24192 charger chip to allow as much input current (from USB/AC) as possible, as well as allowing as high a charge current as possible (to the battery).
From limited tests I've performed in the past, this actually isn't enough to get faster charging, so further investigation will be needed, though your testing will be much appreciated.
It will take effect on the first time you plug in after clicking "Load". If you're already plugged in, you need to unplug and replug for it to take effect.
Source: https://github.com/mzhou/n5charge
General
To use either of these, you need any kernel which supports modules (CONFIG_MODULES=y).
I've attached (modules_boot.img) a stock kernel with the config changed to support modules.
modules_441_boot.img is for 4.4.1, while modules_boot.img is for 4.4.0.
Does this dim further than setting '1' in /sys/devices/mdp.0/qcom,mdss_fb_primary.160/leds/lcd-backlight?
(Also I noticed your CSE email, a fellow UNSW student?)
Cyb3rGlitch said:
Does this dim further than setting '1' in /sys/devices/mdp.0/qcom,mdss_fb_primary.160/leds/lcd-backlight?
(Also I noticed your CSE email, a fellow UNSW student?)
Click to expand...
Click to collapse
Yes. Dragging the brightness slider to the minimum already sets 1 there.
There's values hard coded in the platform data to internally restrict the value to a minimum of 5 (but that's of little consequence).
The main gain is is from the "full scale current" (you can find an explanation in the datasheet for lm3630) which has been hard coded to 18 in the platform data. Bringing it down to 0 makes a huge difference.
(sup)
Nice work! I wonder why they limited it. Possibly to stop people putting their phone into an unusable state during the day?
Cyb3rGlitch said:
Nice work! I wonder why they limited it. Possibly to stop people putting their phone into an unusable state during the day?
Click to expand...
Click to collapse
I've done it to myself many times when I did this to my old phone.
Also updated the attachment in the OP to be compatible with more kernels.
Tested working on Franco.
Very cool! :good:
AWESOME! Is there maybe a mod like this for the NN7 (new nexus 7 )
Is there any advantage to this method over using an app like lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
adzjwarner said:
Is there any advantage to this method over using an app like lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No app will be able to get the backlight this dark.
I'm not sure what Lux does, but if it modifies the colours to produce a darkening effect, then the contrast will be very bad.
adzjwarner said:
Is there any advantage to this method over using an app like lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey there, I'm actually the developer of Lux. The main purpose of Lux is to replace your auto brightness system without the need for root access. That being said, there's no reason why this neat kernel module couldn't be added to a root plugin for Lux.
Cyb3rGlitch said:
Hey there, I'm actually the developer of Lux. The main purpose of Lux is to replace your auto brightness system without the need for root access. That being said, there's no reason why this neat kernel module couldn't be added to a root plugin for Lux.
Click to expand...
Click to collapse
Ah cool.
I tried out Lux and I'm not sure if it's a limitation in the free version, but it only sets the backlight brightness (/sys/class/leds/lcd-backlight/brightness) to a minimum of 10 before it starts doing colour adjustment instead.
My module treats the value 1 as special for making the backlight super dark. Dragging Android's built in brightness slider uses the full range of values 1-225 inclusive.
There's no reason it couldn't just map the full 1-255 to a wider range, but I initially wanted to lean towards keeping things as stock as possible.
arararagi said:
Ah cool.
I tried out Lux and I'm not sure if it's a limitation in the free version, but it only sets the backlight brightness (/sys/class/leds/lcd-backlight/brightness) to a minimum of 10 before it starts doing colour adjustment instead.
My module treats the value 1 as special for making the backlight super dark. Dragging Android's built in brightness slider uses the full range of values 1-225 inclusive.
There's no reason it couldn't just map the full 1-255 to a wider range, but I initially wanted to lean towards keeping things as stock as possible.
Click to expand...
Click to collapse
It does that because some devices do silly things near 0 like putting the device to sleep. You can change the minimum brightness in settings to 1 which should fix this (although I suspect it might round 0.01*255 to 2. I'll have to check my codebase).
Cyb3rGlitch said:
It does that because some devices do silly things near 0 like putting the device to sleep. You can change the minimum brightness in settings to 1 which should fix this (although I suspect it might round 0.01*255 to 2. I'll have to check my codebase).
Click to expand...
Click to collapse
Somehow overlooked that when I was skimming the settings. (And it does round to 2 ).
I could make 2 or anything less than 5 special so that Lux users can benefit. Or maybe just make it configurable with a parameter at insmod time...
arararagi said:
Somehow overlooked that when I was skimming the settings. (And it does round to 2 ).
I could make 2 or anything less than 5 special so that Lux users can benefit. Or maybe just make it configurable with a parameter at insmod time...
Click to expand...
Click to collapse
Whatever you feel works best. A parameter sounds like the most flexible solution though.
This is exactly what I was looking for!
Could I get a bit more explanation of how to install this though? Do I flash the kernel in recovery and then run the command from a shell on my phone, or on my computer?
Thanks for making this.
Sent from my Nexus 5 using xda app-developers app
I'll be watching this thread intently. I currently use lux as well.
rockingondrums said:
I'll be watching this thread intently. I currently use lux as well.
Click to expand...
Click to collapse
Ditto!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Nelsocracy said:
This is exactly what I was looking for!
Could I get a bit more explanation of how to install this though? Do I flash the kernel in recovery and then run the command from a shell on my phone, or on my computer?
Thanks for making this.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Flash the kernel in whatever normal way you choose.
Extract and copy n5din.ko to your phone.
Use root and put it in /data so that apps with SD card access can't mess with it.
Run "insmod /data/n5dim.ko" on your phone. This can be with a terminal emulator or adb or script manager.
I'm probably gonna be making more modules so I might make an app to simplify the process.
Cyb3rGlitch said:
Hey there, I'm actually the developer of Lux. The main purpose of Lux is to replace your auto brightness system without the need for root access. That being said, there's no reason why this neat kernel module couldn't be added to a root plugin for Lux.
Click to expand...
Click to collapse
OhHai! Big fan of the app, it's saved my eyes when internetting in bed for many many months now! (Though I probably should just not internet at night)
I'll leave the plugin stuff to somebody who knows how to do that and rejoice when(if) it happens. :good:
arararagi said:
Flash the kernel in whatever normal way you choose.
Extract and copy n5din.ko to your phone.
Use root and put it in /data so that apps with SD card access can't mess with it.
Run "insmod /data/n5dim.ko" on your phone. This can be with a terminal emulator or adb or script manager.
I'm probably gonna be making more modules so I might make an app to simplify the process.
Click to expand...
Click to collapse
That worked perfectly, thanks.
This is really dim! I'm impressed. If you ever decide to modify it like you mentioned earlier so that the full brightness adjustment was available I'd be interested. It would be useful to have access to all the brightness levels between yours and the ordinary minimum brightness.
Sent from my Nexus 5 using xda app-developers app
any way to edit what's on the ambient display?
would love to get a battery% on there.
Agreed. That would be nice.
Sent from my Pixel 2 XL using XDA Labs
I don't understand why Google doesn't put battery percent on the screen I would also like to be able to adjust the size
Have there been any updates on this subject now that we have the working root and TRWP?
Really love to have options to change clock colors and display battery percentage.
mngdew said:
Have there been any updates on this subject now that we have the working root and TRWP?
Really love to have options to change clock colors and display battery percentage.
Click to expand...
Click to collapse
Nope, not yet...
I want to know why the font changes. Sometimes its tall & skinny other times, short & fat.
winstonbyrd said:
I want to know why the font changes. Sometimes its tall & skinny other times, short & fat.
Click to expand...
Click to collapse
In order to prevent burn-in.
mngdew said:
In order to prevent burn-in.
Click to expand...
Click to collapse
Isn't that (also?) why it moves around?
It would be nice if Google could do something simple like say, have an automatic off setting so it's not wasting power during the night.
Must Samsung lead the way with everything Google does? Seriously?
TokyoGuy said:
It would be nice if Google could do something simple like say, have an automatic off setting so it's not wasting power during the night.
Must Samsung lead the way with everything Google does? Seriously?
Click to expand...
Click to collapse
So you'd like to see ambient display start but only run for a set amount of time? I know I've seen it get really dim, dimmer than when it starts
winstonbyrd said:
So you'd like to see ambient display start but only run for a set amount of time? I know I've seen it get really dim, dimmer than when it starts
Click to expand...
Click to collapse
Yes. It's something Samsung has had for ages now. I mean Google took the time to create a scheduled system for blue light reduction, yet couldn't bother to do the same with Ambient Display. It's either on 24-7 or off.
The best solution I've found is to put a piece of paper or such over the top sensor at night so the phone will think the device is in a pocket and turn off the screen.
TokyoGuy said:
paper or such over the top sensor
Click to expand...
Click to collapse
The best ideas are the easiest sometimes. I stay away from Samsung. I can't stand trying to figure out where they put stuff at. Why change menu structure even. I've tried several times because of the awesome hardware but never make it past about 2 months.
byproxy said:
any way to edit what's on the ambient display?
would love to get a battery% on there.
Click to expand...
Click to collapse
Want Ambient Display to show battery level? Star this issue and let Google know (but don't comment)
http://www.androidpolice.com/2017/1...how-battery-level-star-issue-let-google-know/
If you comment you *will* get spammed by Google notifications, just Star, do NOT comment. (don't ask how I know )
Google Issue Tracker
https://issuetracker.google.com/issues/62319884
Pkt_Lnt said:
Want Ambient Display to show battery level? Star this issue and let Google know (but don't comment)
http://www.androidpolice.com/2017/1...how-battery-level-star-issue-let-google-know/
If you comment you *will* get spammed by Google notifications, just Star, do NOT comment. (don't ask how I know )
Google Issue Tracker
https://issuetracker.google.com/issues/62319884
Click to expand...
Click to collapse
Cheers for the tip! :good::good: We've done my part now let's wait
I just got my pixel 2 XL and can't believe google has not enabled this already, it's a very basic item and a must have for many.
Pretty pathetic, hopefully once roms start dropping this will fix many shortcomings on the device.
As mentioned in an different thread, using Accubattery will display the battery level on the AOD. In my brief testing, Google reported the app as not consuming any measurable amount of power overnight, so no appreciable battery draw. Also, there is a root app from an XDA RC that displays the music you are currently playing/streaming on to the AOD. This is different from the existing "now playing" feature already built in, and at the end of the article HERE it says that almost any "text" can be displayed on the AOD. It's not the built in Google controls for the AOD we are expecting, but there is hope for customization for those with root, and in the coming ROMs.
Well, got this notice, just don't know what "Changed" (shrug)
https://issuetracker.google.com/issues/62319884
Changed
_______________________________
Reference Info: 62319884 [Feature request] Show battery level on active/ambient display
component: Android Public Tracker > Android Developer Preview
status: Assigned
reporter: [email protected]
assignee: [email protected]
cc: [email protected], [email protected]
type: Feature Request P4 S4
blocked by: 62436205
hotlist: Dev-Preview-O, Platform
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker issue 62319884 where you have the role: starred.
Click to expand...
Click to collapse
Pkt_Lnt said:
Well, got this notice, just don't know what "Changed" (shrug)
Click to expand...
Click to collapse
It just means there was another comment left. You will be spammed eternally! :silly:
v12xke said:
As mentioned in an different thread, using Accubattery will display the battery level on the AOD. In my brief testing, Google reported the app as not consuming any measurable amount of power overnight, so no appreciable battery draw. Also, there is a root app from an XDA RC that displays the music you are currently playing/streaming on to the AOD. This is different from the existing "now playing" feature already built in, and at the end of the article HERE it says that almost any "text" can be displayed on the AOD. It's not the built in Google controls for the AOD we are expecting, but there is hope for customization for those with root, and in the coming ROMs.
Click to expand...
Click to collapse
After I read your post I downloaded accubattery and it works quite well. Thanks for the heads up
I hope they enable the ability to keep the icon on the lockscreen while removing it from the notification panel.. that would be perfect.
sent from my Pixel 2 XL or Note FE
This app is a great substitute for OnePlus 6T and no LED. Allows you to get colorful notifications from your favorite apps.
https://play.google.com/store/apps/details?id=com.used.aoe
App Developer: jeaddh alworood
Tips and Tricks: Things that work for me
1. Battery Optimization don't optimize
2. Do not check my lock screen as background. ( helps get customized app color )
PapaMag said:
This app is a great substitute for OnePlus 6T. Allows you to get colorful notifications from your favorite apps.
https://play.google.com/store/apps/details?id=com.used.aoe
Click to expand...
Click to collapse
How much batery it eat per hour?
efkka23 said:
How much batery it eat per hour?
Click to expand...
Click to collapse
Very little, I guess that would vary depending on the duration and the amount of notifications.
Couldn't get it to work
Doesn't work for me either
meljohnsony2k said:
Couldn't get it to work
Click to expand...
Click to collapse
Augustin79 said:
Doesn't work for me either
Click to expand...
Click to collapse
Make sure you have the app set to Don't Optimize if you haven't already. I'm not sure why it isn't working for you and not sure what you have for set up.
It is an amazing app!
I'm using this, had figured it out even before this thread.
Turn on 'New Notifications' in Ambient Display and also do not optimise the app.
It works. And it's the coolest alternative to a notification LED.
efkka23 said:
How much batery it eat per hour?
Click to expand...
Click to collapse
On my 6T, it drained 6% in 3 hours..also, fingerprint unlock is not smooth with this app.
Sometime noticed issues with auto brightness turned off automatically after unlocking screen.
Fir3lordZuk0 said:
On my 6T, it drained 6% in 3 hours..also, fingerprint unlock is not smooth with this app.
Sometime noticed issues with auto brightness turned off automatically after unlocking screen.
Click to expand...
Click to collapse
Mine uses little or no battery at all. Right now I have been up for 13 hours and AOE doesn't even register and I have been getting all my notifications
Use it for 2 days because I thought plus beat not working anymore ( I accidentally turn off lock screen notifications).
AOE working well but lack of feature I want - battery full notification.
Now back to plus beat.
Paresh Kalinani said:
It is an amazing app!
I'm using this, had figured it out even before this thread.
Turn on 'New Notifications' in Ambient Display and also do not optimise the app.
Click to expand...
Click to collapse
Just installed this and it appears to be working. This is the first app that I see doing what I wanted (a very unobtrusive way of telling if notifications have arrived).
Did not need to to activate "New Notifications" under Ambient Display for it to work. Are you sure it's needed?
I'm not managing to customize the color of the colored stripes according to the app sending a notification. Not that I care too much, on Nexus 6P LED color was mostly irrelevant to me. I just needed a visual cue that something needed my attention if I missed the audio one.
gorman42 said:
Just installed this and it appears to be working. This is the first app that I see doing what I wanted (a very unobtrusive way of telling if notifications have arrived).
Did not need to to activate "New Notifications" under Ambient Display for it to work. Are you sure it's needed?
I'm not managing to customize the color of the colored stripes according to the app sending a notification. Not that I care too much, on Nexus 6P LED color was mostly irrelevant to me. I just needed a visual cue that something needed my attention if I missed the audio one.
Click to expand...
Click to collapse
I didn't do anything with new notifications either, but I am glad it's working for you.
removed
I got it working but it times out after 1 minute. I have my display set to sleep after 1 minute of inactivity but if this follows that rule it's kind of useless for notifications.
Maybe I'm missing a setting?
Edit: found the setting I was missing.
bp328i said:
I got it working but it times out after 1 minute. I have my display set to sleep after 1 minute of inactivity but if this follows that rule it's kind of useless for notifications.
Maybe I'm missing a setting?
Edit: found the setting I was missing.
Click to expand...
Click to collapse
What setting? I also see this behaving strangely. It seems that, as other apps, it gets killed in the background even if one opts not to battery optimize it.
OP behaves exactly like Apple in this regard: they get to decide how I should use *my* smarphone.
gorman42 said:
What setting? I also see this behaving strangely. It seems that, as other apps, it gets killed in the background even if one opts not to battery optimize it.
OP behaves exactly like Apple in this regard: they get to decide how I should use *my* smarphone.
Click to expand...
Click to collapse
The setting at the top when you go into select apps
gorman42 said:
What setting? I also see this behaving strangely. It seems that, as other apps, it gets killed in the background even if one opts not to battery optimize it.
OP behaves exactly like Apple in this regard: they get to decide how I should use *my* smarphone.
Click to expand...
Click to collapse
These right here let it run indefinitely. I tested last night and it was telling me I had a notification until I actually dismissed it after 30 minutes.
PapaMag said:
The setting at the top when you go into select apps
Click to expand...
Click to collapse
bp328i said:
These right here let it run indefinitely. I tested last night and it was telling me I had a notification until I actually dismissed it after 30 minutes.
Click to expand...
Click to collapse
Yeah, I set all that. Results have been inconsistent as far as working after long inactivity is concerned.
I wish OP had thought of baking something similar in their OS, when they decided to take away the LED.
gorman42 said:
Yeah, I set all that. Results have been inconsistent as far as working after long inactivity is concerned.
I wish OP had thought of baking something similar in their OS, when they decided to take away the LED.
Click to expand...
Click to collapse
I agree, I wish OnePlus had baked something like this into the stock ROM. My second screenshot doesn't look like it posted for some reason so here it is.
5% battery usage. Not cool. This with "Stable" edge styling, which should be the best for battery.
Uninstalling.
Hi all,
I am also missing a notification LED for incoming messages et al.
Well, the following might be of interest for some of you. Let me explain: I took a closer look at Automate and the flows provided by the user community there. Unfortunately all the flows for controlling the AOD there do support Samsung and LG devices only. By chance I stumbled across the correct name for the Huawei-specific variable that needs to be triggered. So, I took a working flow for LG, simply replaced the variable's name and voila, a working flow, without the need for root or something.
And it works like this: each time an incomming message (or something similar) triggers a notification, the stock AOD gets switched on, showing you the usual clock and notification icon. As soon as you are disabling the notification (by reading the message etc. pp.) the AOD gets switched off again. This works quite well, saves some battery (compared to having AOD constantly on), and you can clearly see when a new message arrives. I also didn't need to put Automate in the battery white list, it simply works as intended.
The necessary steps to get this working are as follows:
Install Automate from play store
Install the Automate extensions "network permissions", "settings permissions" and "superuser permissions" (the latter does not need root for granting the permissions indeed)
Enable "superuser permissions" via adb:
Code:
adb shell pm grant com.llamalab.automate.ext.superuser android.permission.WRITE_SECURE_SETTINGS
Switch off the AOD functionality in your devices settings
Download the (zipped) flow I have attached to this post and install it
Start the flow and grant the permissions you are asked for
If you use flow v01 switch off the logging of that flow, there are tons of data generated while the device is plugged in via USB, flow v02 works fine with loggin enabled
Enable "Automate" in Settings -> Accessibility features -> Accessibility -> Downloaded Services
I have been running this solution since late November. For me it runs smoothly, stable and battery friendly. Maybe it's also helpful for some of you. Just let me know when you have questions.
Disclaimer: I have published the flow on 25th November at android-hilfe.de and in the Automate community only recently.
Cheers.
Update:
@RoteDose has been so kind and had a closer look at the old flow and completely reworked the power charging check, so there's no log flooding anymore. So he created a v02, that I have attached here now. Thanks a bunch for your support, mate!
To do: research for AOD icons to be refreshed after disabling the notification
- Found a list of Huawei specific settings here.
- And you can list the settings by
Code:
adb shell settings list system|global|secure
Hi. I tried this for the Mate 20 X and got the following error when trying to enable superuser permissions using Terminal Emulator:
adb: inaccessible or not found
I am not rooted - any idea what the issue might be?
praveen6585 said:
Hi. I tried this for the Mate 20 X and got the following error when trying to enable superuser permissions using Terminal Emulator:
adb: inaccessible or not found
I am not rooted - any idea what the issue might be?
Click to expand...
Click to collapse
Hi. I would recommend to use adb from your PC. Here's a XDA how-to: https://www.xda-developers.com/install-adb-windows-macos-linux :good:
beggar23 said:
Hi. I would recommend to use adb from your PC. Here's a XDA how-to: https://www.xda-developers.com/install-adb-windows-macos-linux :good:
Click to expand...
Click to collapse
Thanks.. I'll try this and revert
Hi can you please give more details on no. 5, 6 and 7?
galaxy16 said:
Hi can you please give more details on no. 5, 6 and 7?
Click to expand...
Click to collapse
You can download to your phone the file "Huawei AOD switch.zip" I attached and unpack it to a path of your choice. In the Automate app you can import the unpacked "*.flo" file through the dots menu on the top right. You are then able to give permissions, switch logging and start/stop the flow.
Hope this helps. Just let me know. Cheers.
Is there anything else to do after the upload? Unfortunately, it doesn't work for me. I get a notification and nothing happens. But when I turn on the screen and lock the AOD shows. But that's not how it's supposed to work.
beginner user said:
Is there anything else to do after the upload? Unfortunately, it doesn't work for me. I get a notification and nothing happens. But when I turn on the screen and lock the AOD shows. But that's not how it's supposed to work.
Click to expand...
Click to collapse
Have you switched off AOD before starting the flow?
beggar23 said:
Have you switched off AOD before starting the flow?
Click to expand...
Click to collapse
Yes, it's still off.
beginner user said:
Unfortunately, it doesn't work for me. I get a notification and nothing happens. But when I turn on the screen and lock the AOD shows. But that's not how it's supposed to work.
Click to expand...
Click to collapse
Alright. Let's check some things. First question: How do you know, that you got a notification, when the screen or AOD doesn't light up?
beggar23 said:
Alright. Let's check some things. First question: How do you know, that you got a notification, when the screen or AOD doesn't light up?
Click to expand...
Click to collapse
I was writing a message from my wife... Generally speaking, now it's working. I don't know what was wrong before. That's great
beginner user said:
I was writing a message from my wife... Generally speaking, now it's working. I don't know what was wrong before. That's great
Click to expand...
Click to collapse
Glad to hear that! :good:
Its not working o my P30, Emui 10. I followed instruction everything allowed, AOD stock deactivated, but nothing......Automate works fine, flow is active, but...… What could be wrong......
First of all, thank you for this solution.
But I have a little problem. I don't know why, but for me doesn't work :/
AOD switched off -> started the flow (granted all the permissions) -> lock the screen -> i got a message (the phone vibrated), but the AOD doesn't switch on -> unlock the phone, just to the home screen (doesn't read the message) and lock again -> and now the AOD is switched on
The problem is solved.
Just need to enable this:
Settings -> Accessibility features -> Accessibility -> scroll down and enable Automate
razer91 said:
The problem is solved.
Just need to enable this:
Settings -> Accessibility features -> Accessibility -> scroll down and enable Automate
Click to expand...
Click to collapse
Thank you for that. I will add it to the OP.
Alexxxx1 said:
Its not working o my P30, Emui 10. I followed instruction everything allowed, AOD stock deactivated, but nothing......Automate works fine, flow is active, but...… What could be wrong......
Click to expand...
Click to collapse
Let's stop, switch on logging and restart the flow. Try enabling Automate in "Downloaded Services" as @razer91 described below your post. Maybe the log info will then help you finding out what goes wrong. Just let me know.
beggar23 said:
Let's stop, switch on logging and restart the flow. Try enabling Automate in "Downloaded Services" as @razer91 described below your post. Maybe the log info will then help you finding out what goes wrong. Just let me know.
Click to expand...
Click to collapse
Thank You very much! It works, great!
I hope that Automata will not affect on battery life.
Alexxxx1 said:
Thank You very much! It works, great!
I hope that Automata will not affect on battery life.
Click to expand...
Click to collapse
I don't think so. At least here it's all fine. Automate is not even in the battery saver white list, and going to sleep perfectly. Also, I detected no CPU wakelocks.
Yes, I checked too. The consumption of battery by Automata is minor.
Excellent work man [emoji106][emoji108]
Sent from my ELE-L29 using Tapatalk
Warning :-
I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER YOU MAY CAUSE TO YOUR DEVICE WHILE USING OR RANDOMLY EXPERIMENTING WITH THIS FIX, DONT TINKER WITH DEVICE IF U DONT KNOW WHAT U R DOING.
Q. WHAT THIS APP IS FOR ?
A. This app provides charging limit feature for f3 on any rom be it aosp or miui. That is battery will be charged till 81% then charging will be turned off.
Q. BENEFITS OF APP?
A. VERY LESS WEAR TO BATTERY RESULTING IN LONG BATTERY LIFE SPAN.
Q.HOW TO DISABLE THE FEATURE?
A. JUST CLICK THE APP IT WILL NOTIFY THAT LIMIT CHARGE IS DISABLED
REQUIREMENT
1. ROOT;
PROCEDURE TO INSTALL
Follow this :-
Install the app and deny all permission to apps they jus require root.
Then jus click the app n u r good to go no anymore worries
Q. HOW THE APP WORKS?
A. IT WORKS BY LIMITING THE PERCENTAGE TO WHICH BATTERY CAN BE CHARGED.
FOR EG - BATTERY IS CHARGED TILL 81% THEN CHARGING IS SWITCHED OFF BY THE APP. (YES, THE CHARGING IS ACTUALLY TURNED OFF , THAT IS TO SAY NO CURRENT GOES TO BATTERY)
Q.How to restore normal charging?
A. The app takes care of that ......if still any prob install "enable normal charge" app from link below n jus click it.
Resources
1. Download
Download VarX_ChargeLimiter.2.apk
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
Troubleshooting
1. App not getting lauched at boot by macro
Solution :- manually click app on every boot
Or I can provide solution by Tasker but then ppl don't like tasker
Yeah best thing about root is the charge disable capability.
I've been using the Advanced Charging Controller Magisk Module with the AccA frontend app to limit my charge which has been working flawlessly.
I'm curious if your app is a more streamlined version of that?
CrazyTape said:
Yeah best thing about root is the charge disable capability.
I've been using the Advanced Charging Controller Magisk Module with the AccA frontend app to limit my charge which has been working flawlessly.
I'm curious if your app is a more streamlined version of that?
Click to expand...
Click to collapse
My app jus requires a click....single click n no more worries......more over it is not a generic app...its customised for alioth...n man every one doesnot have free time like u....that they will spend hours setting up a app....ppl want one click solutions......here my app has its edge...velle PPL
N bro if u have such guts....make ur own app.....happy app making
varunrocks17 said:
My app jus requires a click....single click n no more worries......more over it is not a generic app...its customised for alioth...n man every one doesnot have free time like u....that they will spend hours setting up a app....ppl want one click solutions......here my app has its edge...velle PPL
Click to expand...
Click to collapse
I hardly believe that setting up AccA on your phone requires more time than setting up yours. And once it has been set up, it does not require further configuration. So mu question would be that what actually makes your app better than AccA?
TheSproker said:
I hardly believe that setting up AccA on your phone requi...re time than setting up yours. And once it has been set up, it does not require further configuration. So mu question would be that what actually makes your app better than AccA?
Click to expand...
Click to collapse
It's jus one click solution ....no heckles...that it....it's simple....jus one click n good to go....n m not here to compete...m jus sharing..u don't like it..good....go away...n In acca u need to download djs.....n configure it...again velle
varunrocks17 said:
It's jus one click solution ....no heckles...that it....it's simple....jus one click n good to go....n m not here to compete...m jus sharing..u don't like it..good....go away...n In acca u need to download djs.....n configure it...again velle
Click to expand...
Click to collapse
No, I don't need to set up any dj's in order for to limit my phone to 80% charge. I get what you are trying to do, but just because it is easier to set up does not mean it is necessarily better than AccA. Try to create something that has not already been done, for example the fingerprint reader only works, when you have already pressed the power button etc.. Since alot of custom roms would need that app.
TheSproker said:
No, I don't need to set up any dj's in order for to limit my phone to 80% charge. I get what you are trying to do, but just because it is easier to set up does not mean it is necessarily better than AccA. Try to create something that has not already been done, for example the fingerprint reader only works, when you have already pressed the power button etc.. Since alot of custom roms would need that app.
Click to expand...
Click to collapse
When I said it's better than any particular app.....m jus sharing...did I say in the post....OH MY APP IS THE BEEEEESSSST APP .....no.....have some logic dude..sic...n if u don't like....don't iinstall...who is asking u to do..sic
varunrocks17 said:
When I said it's better than any particular app.....m jus sharing...did I say in the post....OH MY APP IS THE BEEEEESSSST APP .....no.....have some logic dude..sic
Click to expand...
Click to collapse
You should improve your attitude. No one is saying that your app is bad, but creating "clones" of other apps is not going to convince users to stop using well known solutions that were created before your apps. All I am saying is that you should try to create something original, be calm and respectful with others and trust me, you will become a much better developer.
TheSproker said:
You should improve your attitude. No one is saying that your app is bad, but creating "clones" of other apps is not going to convince users to stop using well known solutions that were created before your apps. All I am saying is that you should try to create something original, be calm and respectful with others and trust me, you will become a much better developer.
Click to expand...
Click to collapse
Sorry bro my intent was not to be hurtful...