Related
Hi Guys.
I need help for testing a new app I've been working on.
It's an app that's truely "set and forget", that makes your smartphone even smarter.
When you're tired and just wants to sleep, plug in your phone to the charger and BAM the clock app is there, ready for you to set the alarm.
It will do various tasks when you plug in a charger, eg:
Open an app you define
Activate daydream (Screensaver) after a certain interval
Enable silent mode
Enable flightmode (Requires root)
Reboot phone after certain interval (Requires root)
Go to homescreen when charger is unplugged
Play sound when charger plugged/unplugged
Sound when charger plugged/unplugged
The reboot functionality is especially useful if you (like me) forget to reboot your phone sometimes. All Android phones run low on memory over time, and a reboot is the most effective way to avoid this.
This app won't run unless the phone is in charger = Next to none impact on battery life.
Reasons for app permissions:
MODIFY_AUDIO_SETTINGS - To be able to set silent mode
BIND_DREAM_SERVICE - To be able to start DayDream (On Android 5.0+)
RECEIVE_BOOT_COMPLETED - To know when the app rebooted the device (and act accordingly)
What do you think guys? Anything you will use?
If you have any suggestions/feature requests please don't hesitate to mail me at [email protected] or put an answer below- I'm fully open to new suggestions and they are very welcome.. :victory:
Installation
Install the app from Google Play
Thanks! :victory: :laugh: :highfive:
XDA:DevDB Information
Charger Extras, App for all devices (see above for details)
Contributors
dthomasen
Version Information
Status: Alpha
Current Stable Version: This is an app is tr
Created 2015-06-26
Last Updated 2015-06-26
Testing. Suggestions:
1. Optional notification sound/vibration when plugged/unplugged.
2. Optional notification sound/vibration when: a) full charged; b) unplugged and bellow certain battery level.
3. I think it must have a timer to activate the airplane mode (not all the times we charge that it should be enabled..., perhaps only at night).
Technical said:
Testing. Suggestions:
1. Optional notification sound/vibration when plugged/unplugged.
2. Optional notification sound/vibration when: a) full charged; b) unplugged and bellow certain battery level.
3. I think it must have a timer to activate the airplane mode (not all the times we charge that it should be enabled..., perhaps only at night).
Click to expand...
Click to collapse
Thanks, I'll add them to my upcomming feature list..
I just pushed a new release to Google Play
Changelog:
Declare superuser permission in manifest
Dialog boxes for root settings
Timer for flightmode
Sound when charger plugged/unplugged
I've approved the app for production.
Installation is now only to install from Google Play..
Enjoy guys
Thanks, but the airplane mode is (yet) to be more flexible.
If some other features come, I'll be able to uninstall other apps that has "similar" functionality, for instance:
1. Battery temperature on notification.
2. Options for not warning sound while headphones are connected, or while in call.
Seems a promising app. Thanks.
Technical said:
Thanks, but the airplane mode is (yet) to be more flexible.
If some other features come, I'll be able to uninstall other apps that has "similar" functionality, for instance:
1. Battery temperature on notification.
2. Options for not warning sound while headphones are connected, or while in call.
Seems a promising app. Thanks.
Click to expand...
Click to collapse
What more flexibility do you want in the airplane mode?
You're thinking battery temperature when charging only? Or all the time?
dthomasen said:
What more flexibility do you want in the airplane mode?
Click to expand...
Click to collapse
I want to start airplane mode only when charging overnight. If any charge starts the airplane mode, I'll lose calls and messages in the middle of the day. I'm an intensive user of the phone. I need to charge frequently, not only overnight. You've add the option (timer) to start airplane mode after some seconds, but it would be good, imho, if we have a period (from time to time) where the airplane mode is started. Charging outside of this period won't trigger the airplane mode.
dthomasen said:
You're thinking battery temperature when charging only? Or all the time?
Click to expand...
Click to collapse
The more configurability the better: if the user can chose for a permanent notification, it will help to keep the app alive.
I myself would like to set a temperature level when it reaches a predefined temperature.
Technical said:
I want to start airplane mode only when charging overnight. If any charge starts the airplane mode, I'll lose calls and messages in the middle of the day. I'm an intensive user of the phone. I need to charge frequently, not only overnight. You've add the option (timer) to start airplane mode after some seconds, but it would be good, imho, if we have a period (from time to time) where the airplane mode is started. Charging outside of this period won't trigger the airplane mode.
The more configurability the better: if the user can chose for a permanent notification, it will help to keep the app alive.
I myself would like to set a temperature level when it reaches a predefined temperature.
Click to expand...
Click to collapse
Ahh like that.. I'll add it to the upcomming feature list.
Expect an update sometime next week.
Thanks. :highfive:
New version submitted to Google Play..
Should show up in a couple of hours
Changelog:
- Restructured with material UI drawer
- Soft reboot type implemented
- Set when app should be active (Time of day)
- Flurry integrated
New version submitted.
Changelog:
- Fixed time activation when using times on opposite sides of midnight
- Ability to set independent sound for plug and unplugging
- Added feature to set minimum screen brightness when charging
- Added feature to launch app when unplugging (Useful for morning news reading )
Enjoy
Just submitted a new version - With a very requested feature
Changelog:
- Activate based on charger type:
- Wireless
- USB
- AC
Enjoy.
Hello MOAR users,
I'm not sure this is a MOAR issue. Something changed and I don't know what. For some reason when I plug in w Samsung USB cable & multiple different Samsung Adaptive Fast Chargers that previously would indicate "charging", now they do not. Inductive Qi charging seems to be working, although I'm not sure it is at the faster rater. On occasion it too has not worked but restarting the phone re-enabled it. Odd. "Fast Cable Charging" slide switch is "on" within the settings\battery area of the phone. I'm using Galaxy Charging Current app, to watch charge rate. In the MOAR General tab, Adaptive Fast Charging and Wireless Fast Charging buttons are red, indicating enabled. Anyone else experience this issue? Thanks in advance.
Also, how do you get what looks like a down arrow [on the extended power menu screenshot of the MOAR main XDA page] to further expand the options in the "Extended Power Menu"? I can enable a fixed number of them after which their respective icons are off screen and you can't scroll down to tap them. Touching the screen exits out of the menu in its entirety.
see this post too which describes pretty closely my issue:
https://forum.xda-developers.com/sp...ger-fast-charging-t3325873/page2#post71160248
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
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.
Hello,
I noticed that when using the specific app on my phone (Samsung A52s 5G, Android 13), Czech GPS app mapy cz, the device charges slower than when the app is not running. E.g. on a motorcycle, the phone charges approximately 2000mA (according to Ampere). But as I start navigating in mapy.cz, after about a minute the charging current drops to 700mA and the phone charges really slowly. I can tell by the voltage that motorcycle shows too. When I close mapy.cz, after about 30 seconds the current increases again very quickly to 2000mA. No other navigation app does this. It's a free application, I tried to write to support, but so far no answer. Could there be an error in the application or in the phone settings? Thank you.
You shouldn't charge while the display is on.
If the phone is in use while charging the power controller will ramp down the charge rate to protect the battery. You can fast charge normally if the display is off and the background apps don't draw too much current.
Example; I can use Poweramp and bt to listen to music or take a phone call without fast charging disengaging as long as the display is off.
blackhawk said:
You shouldn't charge while the display is on.
If the phone is in use while charging the power controller will ramp down the charge rate to protect the battery. You can fast charge normally if the display is off and the background apps don't draw too much current.
Example; I can use Poweramp and bt to listen to music or take a phone call without fast charging disengaging as long as the display is off.
Click to expand...
Click to collapse
Thanks for the reply, but there is no charging problem with another app. For example, with the TomTom Go running, the phone normally charges around 2000mA. Today, while navigating while driving, my phone charged from 50 to 100% quite quickly.
Glerin said:
Thanks for the reply, but there is no charging problem with another app. For example, with the TomTom Go running, the phone normally charges around 2000mA. Today, while navigating while driving, my phone charged from 50 to 100% quite quickly.
Click to expand...
Click to collapse
Watch your battery temp...
WYSIWYG, charging characteristics may vary from manufacturer to manufacturer, etc.
Try turning off battery and/or data background usage in the buggy app, clearing it's cache or data... or take out the trash app.