Related
Description
In light of not having a dedicated notification LED I set up some Tasker profiles to toggle the Accessibility setting Flash Notifications. I don't want it flashing while I'm using my phone, or while in my car on my wireless charging mount. This consists of 2 profiles and four tasks.
First profile will disable Flash Notifications when your screen is on and enable it when your screen is off, unless the Car profile says it's in your car and on your charger.
Second profile will disable Flash Notifications when it's connected to your car's Bluetooth (be sure to set it to your cars Bluetooth address), AND it's on the charger, unless the Screen profile says the screen is on, in which case the Flash Notifications will remain disabled until you turn you screen off. In my car, I use a wireless charger, so taking it off the charger disconnects power, and putting it back on the mount reconnects power automatically. My idea was that I don't want the Flash distracting other drivers, cuz they have a hard enough time being competent as it is. If you don't use a wireless charger or don't have Bluetooth in your car, you might have to tweak the activation of this profile to your specific case.
I have never shared a Tasker Profile before, so if anyone's interested in this and it doesn't import or something let me know.
Downloads
I am providing both downloadable attachments, and links to download from Tasker's site. You must also have Tasker and Tasker's helper app "Tasker Settings" installed.
Screen Profile Download Link
Car Profile Download Link
Tasker
Tasker Settings Helper App
I don't recall having to use adb to grant Tasker special permissions, but I will be doing a fresh install of this on my wife's phone tomorrow and will update if you need to.
<Reserved>
Useful. Thanks.
lightmastertech said:
Description
In light of not having a dedicated notification LED I set up some Tasker profiles to toggle the Accessibility setting Flash Notifications. I don't want it flashing while I'm using my phone, or while in my car on my wireless charging mount. This consists of 2 profiles and four tasks.
First profile will disable Flash Notifications when your screen is on and enable it when your screen is off, unless the Car profile says it's in your car and on your charger.
Second profile will disable Flash Notifications when it's connected to your car's Bluetooth (be sure to set it to your cars Bluetooth address), AND it's on the charger, unless the Screen profile says the screen is on, in which case the Flash Notifications will remain disabled until you turn you screen off. In my car, I use a wireless charger, so taking it off the charger disconnects power, and putting it back on the mount reconnects power automatically. My idea was that I don't want the Flash distracting other drivers, cuz they have a hard enough time being competent as it is. If you don't use a wireless charger or don't have Bluetooth in your car, you might have to tweak the activation of this profile to your specific case.
I have never shared a Tasker Profile before, so if anyone's interested in this and it doesn't import or something let me know.
Downloads
I am providing both downloadable attachments, and links to download from Tasker's site. You must also have Tasker and Tasker's helper app "Tasker Settings" installed.
Screen Profile Download Link
Car Profile Download Link
Tasker
Tasker Settings Helper App
I don't recall having to use adb to grant Tasker special permissions, but I will be doing a fresh install of this on my wife's phone tomorrow and will update if you need to.
Click to expand...
Click to collapse
I'm a complete idiot when it comes to Tasker. I have compiled ROMs from source, made many Smali edits, built themes (all many years ago when I had time) but never spent the time to figure out Tasker.
I would like Tasker to disable Holey Light (see screenshot) when Do not disturb is turned on and re-enable it when Do not disturb is turned off. Would you know how to (or could you make a profile) do this?
bp328i said:
I'm a complete idiot when it comes to Tasker. I have compiled ROMs from source, made many Smali edits, built themes (all many years ago when I had time) but never spent the time to figure out Tasker.
I would like Tasker to disable Holey Light (see screenshot) when Do not disturb is turned on and re-enable it when Do not disturb is turned off. Would you know how to (or could you make a profile) do this?
Click to expand...
Click to collapse
I second this!!!!
Tasker looks like a super useful tool, but f*** why make it so complicated and not user friendly.
I recently tried MacroDroid and like it more, but its definitely limited compared to Tasker from what I've learned, but it did work while I used it.
To disable Holey Light while in DND would be very nice to have. Please advise.
elite-fusion said:
I second this!!!!
Tasker looks like a super useful tool, but f*** why make it so complicated and not user friendly.
I recently tried MacroDroid and like it more, but its definitely limited compared to Tasker from what I've learned, but it did work while I used it.
To disable Holey Light while in DND would be very nice to have. Please advise.
Click to expand...
Click to collapse
I'm not sure if Tasker can change the settings of another app without said app already being programmed to be controlled by Tasker. I'll have to see if this is possible.
Also, considering Holey Light is still in beta and being developed, you might try contacting Chainfire and seeing if he can add this setting to the app natively.
lightmastertech said:
Also, considering Holey Light is still in beta and being developed, you might try contacting Chainfire and seeing if he can add this setting to the app natively.
Click to expand...
Click to collapse
He's looking into adding Do not disturb but I already found a workaround for my problem. In Holey Light I just turn off for it to work when charging and screen is off. I charge my phone every night so it works out fine for me.
bp328i said:
He's looking into adding Do not disturb but I already found a workaround for my problem. In Holey Light I just turn off for it to work when charging and screen is off. I charge my phone every night so it works out fine for me.
Click to expand...
Click to collapse
Only way I can think of having Tasker control it as is, would be to enable disable notification permissions or Accessibility service, both of which require root to do and I have the unrootable US Snapdragon variant.
On another note, Sammy has already added a variation of ring notifications that I'm sure they will expand on. As if now, it works with system apps with screen on or off, and with user apps with screen on.
lightmastertech said:
Only way I can think of having Tasker control it as is, would be to enable disable notification permissions or Accessibility service, both of which require root to do and I have the unrootable US Snapdragon variant.
On another note, Sammy has already added a variation of ring notifications that I'm sure they will expand on. As if now, it works with system apps with screen on or off, and with user apps with screen on.
Click to expand...
Click to collapse
I appreciate it, I also have the unrootable US Snapdragon.
Samsung's current implementation of the notification light is just plain useless. It stays on for like 5 seconds.
Holey Light is working perfectly for me the way I have it set up.
While I've had many Android phones, this is the first phone that I decided to use a battery charging controller to regulate how my battery is charged. I just wanted to share my journey with others and encourage others to try this out if you are not already.
Although there are several different battery charging controllers out there (and more than one named "ACC" which makes it even more confusing) I decided to use the Advanced Charging Controller module developed by VR25. I choose this module because I felt it provided the most customization.
Step 1 - Installation
Installing the module is easy. It is listed in the Magisk repository. Simply browse the available modules and find the one titled, "Advanced Charging Controller (acc) created by VR25 @ XDA-developers". There are several ACC modules, so make sure you install the one by VR25 to follow this thread.
Magisk will flash the module and start it automatically. You don't even need to reboot, although it is the only way to clear the Magisk notification that the module will be started at the next reboot.
Step 2 - Changing the Charging Switch Setting
I found that the default charging switch setting (auto) does not work reliably with our phones. Therefore I would suggest changing it using the commands below. Personally I have choose option 2 (battery/charge_disable 0 1) but I listed all the options with the quirks that I have found with each one.
Step 2.1 - open your preferred command line app - I use Terminal Emulator.
Step 2.2 - type "su" and hit enter to gain root
Step 2.3 - type "acc -s s" and hit enter - this is the command that allows us to select another charging switch
Step 2.4 - type what number of the charging switch you want to use.
Here are the available charging switches and the issues I have found with them:
1) Automatic - this switch tries to cycle through the available switches until if find one that "works".
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: No - I found that the phone would charge anytime it was plugged in and below the Pause threshold. It did not seem to wait until the battery level was below the Resume threshold.
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:
2) battery/charge_disable 0 1 :
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:3) battery/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): No - phone begins discharging from battery when Pause threshold is reached but the phone is still plugged in
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: No - may show charging icon when phone is really discharging, especially during cooldownratio times and the chime doesn't always ring when charging resumes.
- Suffers from wakelock issues when phone is plugged in but not charging: No
- Other issues: The phone seems to follow the cooldown charge/discharge times even before reaching the cooldown threshold. I find the phone pausing for 10 seconds (my cool down ratio) when the batter level might be a 50% - long before the 60% cooldown threshold I have set in the config file.4) dc/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:5) battery/charge_control_limit 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:
Step 3 - Configuration
You can configure the ACC controller using a couple of different methods. You can do everything using command lines, you can use the beta ACC app (see note below), or you can edit a config file that ACC creates when it is installed. Personally I found that editing the config file was the quickest and easiest method to make general changes.
The ACC config file is found at /storage/emulated/0/acc The file is named "config.txt" You can open the file with a text editor. I personally use the app Root Explorer. I long click on the file name, and then press the three dot button in the upper right hand corner. Choose "Open in Text Editor" and the config file will open and allow changes to be made. Saving the file will automatically push the changes to ACC, you do not need to reboot or restart the ACC daemon for changes to take effect.
I won't go into a lot of detail about all of the different configuration options here as the developer's xda thread is the best place to get that type of information. But I will talk about the most basic setting - the "capacity" setting. It is the second setting listed in the config file and it should look something like "capacity=0, 60, 70-80". Here is a break down of what those numbers mean:
- The First Number (0): is battery level were the phone will shut off. The default setting of 0 means the phone will turn off when the battery level hits 0. Personally I don't want my battery completely draining, so I have it set at 5.
- The Second Number (60): is the battery level where the module starts it's "cool down" functionality. Cool down (listed as coolDownRatio in the config file) is where the phone will stop charging briefly and then restart charging. The default "cool down" setting is coolDownRatio=50/10 which means the phone will charge for 50 seconds, and then stop charging for 10 seconds before charging again for 50 seconds, etc, etc, etc. This is designed to keep the battery temps low. A battery with a charge level less than this number (60 in this example) will charge without pausing, but when the battery level gets to this number or above, the phone will charge and pause based on the coolDownRatio.
- The Third Number (70): is the "resume" value. If the phone's battery level is below this resume value, the phone will charge. If the battery level is at or above this resume value, the phone will not charge even while plugged in.
- The Fourth Number (80): is the "pause" value. This is the battery level where the phone will stop charging and should not charge above this value.
The default settings are set this way because research has shown that a phone's battery will last the longest with the least amount of battery capacity loss if it is charged to a max of 80% of the battery's capacity, and allowed to discharge just a small amount (10%) before being charged again. I realize this goes against the old "wives tale" that our phone's batteries have a very limited number of charges and it is best to limit the number of charges by only charging the phone when it gets to a low level. This is not true in actual battery performance however and if you charge like this, you are actually decreasing your battery's life expectancy and performance.
Obviously the default settings may not be the best setting for you. The default settings are probably only practical for a device that is plugged in 100% of the time. Personally I have changed my capacity setting to capacity=5, 60, 70-90. This means my phone will turn off when the battery level reaches 5% (something it has never dropped to yet), it is charged to a max of 90% and will discharge to 70% before charging again, and the cooldown charging cycling starts when the battery is 60% or higher. Obviously I'm not on my charger all the time, so it is very common for my battery to drop below 70%. However, if the battery is below 70% and I have a charger at my disposal, I am going to charge the phone back to 90% rather than let it the battery levels continue to fall.
Final Notes and Misc Thoughts
There are lots of other options and commands you can use in ACC. Feel free to share any changes you like to make, or post if you are having problems getting the module to work as expected on the 3a. I hope this helps some people feel give the module a try.
There is an ACC app that is available now that allows you to control some of the settings from a nice GUI. I personally did not like using it as I found it would overwrite settings in the config file that I was not intending to be changed.
There is an ACC telegram group if you want to join and have direct communication with the developer and others.
Thanks to @jellopuddingstick for educating me on what the battery idle mode does and why it is beneficial to have it working!
sic0048 said:
I just wanted to share my journey with others and encourage others to try this out if you are not already.
Click to expand...
Click to collapse
Was doing the same research when this popped up -- great job!
Can you discuss more on what unintended settings were overwritten by the app....
Also, thoughts have seem to have standardized now to lop off 40% of usuable capacity by having the battery charge btw 20-80% to extend life, such as... "capacity=20, 60, 70-80".
How were the defaults for ACC set and why have you chosen otherwise?
duh1 said:
Was doing the same research when this popped up -- great job!
Can you discuss more on what unintended settings were overwritten by the app....
Also, thoughts have seem to have standardized now to lop off 40% of usuable capacity by having the battery charge btw 20-80% to extend life, such as... "capacity=20, 60, 70-80".
How were the defaults for ACC set and why have you chosen otherwise?
Click to expand...
Click to collapse
The app works by writing to the normal config file. But it also has three profiles loaded into memory automatically when you install it. This makes it very easy to press on one of the other profiles by accident and totally change your settings. I eventually deleted all the "extra" profiles, but the charging switch isn't changeable via the app either (it seems like it defaults to auto) so the app will overwrite that setting back to auto if you aren't paying attention.
In the long run I found that using the config file was extremely easy and I found myself having the check the config file anytime I used the app to make sure it wasn't changing unintended settings, so I decided to remove the app and just use the config file.
As far as capacity, I decided to run 5, 60, 70-90. I think it is a good compromise between having a decent amount of capacity available and also not charging the phone to 100% all the time. I could probably get away with a limit of 80 or 85, but ultimately decided on 90. I do try to charge my phone when it hits 70 or below if I have a charger available vs waiting to do a larger/longer single charge.
sic0048 said:
I do try to charge my phone when it hits 70 or below if I have a charger available vs waiting to do a larger/longer single charge.
Click to expand...
Click to collapse
Don't you think 70 is too high to begin charging just to bring it back to 90. Doesn't number of charge cycles kill battery life as much as heat and fast rate charging?
Any good apps you like that intuitively monitor battery health, besides just stats and charts, that does it like apple, as a percent of remaining chargeable capacity?
Btw OT question, looking to move over my wifi connections from the previous phone and can't find the wpa_supplicant.conf file in /data/misc/wifi in the 3a. No reference online mentions that it's been moved. Any idea where they're hiding it now? Thx...
duh1 said:
Don't you think 70 is too high to begin charging just to bring it back to 90. Doesn't number of charge cycles kill battery life as much as heat and fast rate charging?
Click to expand...
Click to collapse
According to this research (https://batteryuniversity.com/index.php/learn/article/how_to_prolong_lithium_based_batteries/), the more your battery discharges, the fewer discharge cycles it will survive before really negatively effecting battery performance. So discharging your phone just 10% might give you 6000 discharge cycles, while discharging your phone 60% might reduce these discharge cycles by 90%.
Obviously I have to rely on other people's research as there is no way I can adequately test this myself. But I do trust this research as accurate. I know with other phones I've had where I did not try to control the charging system I have had to replace the batteries with pretty regular occurrence. But I would leave the phone on the charger overnight (not a good thing for battery life) and try to discharge the battery a lot before charging it back again (also not a good thing for battery life). That's why I decided to finally look into using a charging controller like ACC with this new phone.
duh1 said:
Any good apps you like that intuitively monitor battery health, besides just stats and charts, that does it like apple, as a percent of remaining chargeable capacity?
Click to expand...
Click to collapse
I've been using the ExperimentalX helper app to track battery usage. (You don't need to use their kernel to use the helper app). I like it because it breaks the battery usage stats into two parts: when the screen is on, and when the screen is off, but it doesn't attempt to give a percent of remaining chargeable capacity. I'm not aware of an app that does that (although I too would be interested to know if such and app exists).
duh1 said:
Btw OT question, looking to move over my wifi connections from the previous phone and can't find the wpa_supplicant.conf file in /data/misc/wifi in the 3a. No reference online mentions that it's been moved. Any idea where they're hiding it now? Thx...
Click to expand...
Click to collapse
I think the info you are looking for is now stored at /data/misc/wifi/WifiConfigStore.xml.
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
I've continued to edit my original post to provide as much information about the different charging switches and the issues I see with each one. Hopefully it is easy to understand.
I still find myself defaulting to the 3rd charging switch option and while it can act a little erratic sometimes, it does work normally most of the time.
Is it possible to disable/bypass the cool down period?
creeve4 said:
Is it possible to disable/bypass the cool down period?
Click to expand...
Click to collapse
The default setting is for it to be turned off I believe. Look in the config file for "coolDownRatio=" and see if it is blank. If it is not, you can remove everything after the equal sign.
Another way to do it is set the cooldown threshold number to be equal or higher than your "pause" threshold. So you might set this as "capacity=5, 100, 70-90". The 100 represents the value at which the cooldown process would start, which is higher than the pause threshold (at 90 in this example) and therefore would never kick in.
All this being said, I find that the #3 switch option seems to allow the cooldown pause/charge process to start below the set cooldown threshold. I have my cooldown threshold set at 60, yet find the phone pausing and charging at battery levels below this threshold. This should not be happening, but is something I can live with, so I haven't bothered to follow up with it.
After several more weeks of use, I've updated the initial post again. I found some quirks with the "automatic" charging switch, so I have gone back to selecting charging switch option 2 (battery/charge_disable 0 1).
Great job!
May I ask you whick kernel you are using for "battery idle mode" support? It should not be supported on stock kernel.
Thanks
Hi guys, tried the Module for Magisk + the Acc App.
The App shows the Deamon is running but, when it hits the set threshold it keeps charging. Any fix, or is the Oneplus 9 just not supported yet?
Hi
Same problem here. Tried all solutions including Battery Charge Limit and Tasker to stop charging. No working solution so far.
I ended up creating a tasker profile that gives an audible alert at a specific battery level and then I manually disconnect the charger...
MoHed said:
Hi
Same problem here. Tried all solutions including Battery Charge Limit and Tasker to stop charging. No working solution so far.
I ended up creating a tasker profile that gives an audible alert at a specific battery level and then I manually disconnect the charger...
Click to expand...
Click to collapse
Did the exact same thing with Tasker haha. Best solution for now.
Battery charge limit by sriharshaarangi now works.
Credit for the 1+9 (Pro) codes to B1tWeaver
[APP][ROOT][4.0+]Battery Charge Limit v1.1.1
Please read the following before installing the app: This app requires a rooted mobile (Android 4.0 or later) Before uninstalling the app, disable limit in the app (if forgotten, reboot after uninstalling) Usage instructions and app...
forum.xda-developers.com
Have the control file data of :
wired:
/sys/class/oplus_chg/usb/chg_enable, 1, 0
wireless:
/sys/class/oplus_chg/wireless/chg_enable, 1, 0
Working great on my 1+9 .
Not aure if you wanna try this but 3C All-In-One app has all kinds of Battery Controls and Options. Might be the way to go. Be careful like always. Couple things I did got my phone at like 115 degrees. Had to wipe and reset lol.
Good App though. I have the paid version if interested.
Any developer wants to make a kernel for games on the poco x3 pro? if possible, add the option to skip the battery, such as Rog 3, oneplus 7 (enabled by the advanced charge controller). Please!
You can try ask in the telegram group
MOD EDIT: Link Removed
Battery skip, do you mean direct power to device without charging the battery when connected with charger?
This thing will need the hardware support. As I personally try auto-detect, ACC didn't detect this support.
Maybe ask developers if they see this option possible in the firmware/kernel or not.
pl1992aw said:
You can try ask in the telegram group
MOD EDIT: Link Removed
Battery skip, do you mean direct power to device without charging the battery when connected with charger?
This thing will need the hardware support. As I personally try auto-detect, ACC didn't detect this support.
Maybe ask developers if they see this option possible in the firmware/kernel or not.
Click to expand...
Click to collapse
yes the power goes straight to the cell phone and does not charge the battery, it preserves the useful life, so I saw only the kernel support is enough I think
TheKaikera said:
yes the power goes straight to the cell phone and does not charge the battery, it preserves the useful life, so I saw only the kernel support is enough I think
Click to expand...
Click to collapse
Use Advanced Charging Controller (acc)
https://forum.xda-developers.com/t/advanced-charging-controller-acc.3668427/
It's written in the README description how to "emulate" battery idle mode
Spoiler
GenericEmulate battery idle mode with a voltage limit: acc -s pc=101 rc=0 mcv=3920. The first two arguments disable the regular charging pause/resume functionality. The last sets a voltage limit that will dictate how much the battery should charge. The battery enters a [pseudo] idle mode when its voltage peaks. Essentially, it works as a power buffer.
Limiting the charging current to 0-250 mA or so (e.g., acc -sc 0) may produce the same effect. acc -sc - restores the default limit.
Force fast charge: appy_on_boot="/sys/kernel/fast_charge/force_fast_charge::1::0 usb/boost_current::1::0 charger/boost_current::1::0"
https://github.com/VR-25/acc/blob/master/README.md
pl1992aw said:
Use Advanced Charging Controller (acc)
https://forum.xda-developers.com/t/advanced-charging-controller-acc.3668427/
It's written in the README description how to "emulate" battery idle mode
Spoiler
GenericEmulate battery idle mode with a voltage limit: acc -s pc=101 rc=0 mcv=3920. The first two arguments disable the regular charging pause/resume functionality. The last sets a voltage limit that will dictate how much the battery should charge. The battery enters a [pseudo] idle mode when its voltage peaks. Essentially, it works as a power buffer.
Limiting the charging current to 0-250 mA or so (e.g., acc -sc 0) may produce the same effect. acc -sc - restores the default limit.
Force fast charge: appy_on_boot="/sys/kernel/fast_charge/force_fast_charge::1::0 usb/boost_current::1::0 charger/boost_current::1::0"
https://github.com/VR-25/acc/blob/master/README.md
Click to expand...
Click to collapse
I've tested it and it really seems to work, but how can I make sure I'm not ruining my battery?
TheKaikera said:
I've tested it and it really seems to work, but how can I make sure I'm not ruining my battery?
Click to expand...
Click to collapse
Don't go to high on battery temperature.
Try not to use while charging.
Smart batteries now have self condition check.
Ampere app can check condition of batteries.
Try not to get battery percentage higher than 95%.
Try not to get battery percentage lower than 30%. Charge when you have access to power.
I always use the black shark cooler when I play on the charger, battery temperature at 30 C, but I'm still not sure if this idle battery "emulation" works, I saw that it depends on the cell phone kernel and I'm not sure if my phone supports it, I wanted to be sure, because I use the game charging for hours and the battery without charging can't handle
TheKaikera said:
I always use the black shark cooler when I play on the charger, battery temperature at 30 C, but I'm still not sure if this idle battery "emulation" works, I saw that it depends on the cell phone kernel and I'm not sure if my phone supports it, I wanted to be sure, because I use the game charging for hours and the battery without charging can't handle
Click to expand...
Click to collapse
ACC did not detect idle mode support on auto, it is not support by the kernel, not even in MIUI (yet).
Only emulate.
You need to take balance whether you want battery health or gaming.
You have to choose which is priority for you.
Give and take, not both.
About kernel problem, go ask in Telegram group. Find kernel authors and ask possibilities to get idle battery mode into kernel.
Is there a way to
1. Enable adaptive charging overnight even of no alarm is set
2. Disable adaptive charging even if an alarm is set
Anyone here pls?
thegios said:
Is there a way to
1. Enable adaptive charging overnight even of no alarm is set
2. Disable adaptive charging even if an alarm is set
Click to expand...
Click to collapse
Hi,
1st question: I don't know.
2nd question: disable adaptive charging.
Cheers,
Sébastien.
PS: Instead of opening multiple threads, open one with all your questions
What should adaptive charging do If no Alarm IS Set?
2. Turn of adaptive charging
I wish there was a way for it to follow bedtime mode
My adaptive charging is actually working without setting alarms. It seems that's learning my behaviour.
I don't know if it's related to this, but I'm on Android 14 beta 2.1, with all Google apps set to beta.
You can always create an alarm and set it to silent. That will do the trick until they natively implement this on Android.
gpvecchi said:
My adaptive charging is actually working without setting alarms. It seems that's learning my behaviour.
I don't know if it's related to this, but I'm on Android 14 beta 2.1, with all Google apps set to beta.
Click to expand...
Click to collapse
Yes I've read Google is about to implement this but may be only limited to beta