[Q] Charging temperature problem with Samsung Galaxy Tab (GT-P1000) - General Questions and Answers

Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti

AnttiSoininen said:
Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti
Click to expand...
Click to collapse
Hi Antti, I am just curious, how do you know your sensor is damaged and it has rusted? It may be caused by malfunction of the processor detecting from the temperature of the battery.
Secondly, your level 29% doesn't tally with 3734.0mV. Theoretically, when battery reaches almost zero, it should read close to 3200mV, fully charge it should be 4200mV. I am assuming that this is the battery percentage indication for your battery, please do a check on by going > Settings=>About Device=>Status and check battery level. If it is 29%, your battery status has gone "crazy" and so does your temperature readings.
Just leave a feedback if you have such an issue.

AnttiSoininen said:
Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti
Click to expand...
Click to collapse
so did you fixed it?

AnttiSoininen said:
Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti
Click to expand...
Click to collapse
reflash with stock rom and test again for me that is a problem with hardware...

Help
I have the same problem , any one can help me?
Sam

for me i try to buy new charger at first ok. the temp problem gone. but another come out
when it says battery full when i unplug the charger it went down to 65 or 70 then i need to plug it again after few hours say 2 hour it will indicate again battery full
at this time its really full

i am facing the same problem right now.
notification: charging problem. battery temperature too high or too low.
battery status (*#0228):
current value:-
voltage: 3739.0 (mV)
adc: 0
temperature: 7.0 ('C)
adc: 0
vf adc: 0
level: 72%
actually my phone got splashed with water and i found out that the water got into the speaker when i open the back cover, i can see (a little) water.
some suggestion on how to fix this error? maybe some software or hardware modification?
update 26/06/12:
- my gtab haven't charged for 2 days now. last night i power off, then just this afternoon i power on it back to see the status. last night battery level is >20%, when it power on just now, is says only 8%, checking *#0228#
voltage: 3832.0 (mV)
temperature: 41.9 ('C)
level: 10%
- i think the water on the motherboard/battery has dry (remarks, saltwater) and now the circuit/electronic/battery is back to normal.
- if anything wrong again i update it here.

Accessing menus?
Sorry but I must not have seen the correct page or forum yet, but where do you enter this :
battery status (*#0228):
I need to change the battery charging temperature on my gt-p1000r but I don't seem to be able to access any place to do this.
I have rooted it. And I have tried to enter various codes into memo with out any success. Just need a little help or direction with this one.
Thanks,

Need to set my battery charging temperature
jasoncummer said:
Sorry but I must not have seen the correct page or forum yet, but where do you enter this :
battery status (*#0228):
I need to change the battery charging temperature on my gt-p1000r but I don't seem to be able to access any place to do this.
I have rooted it. And I have tried to enter various codes into memo with out any success. Just need a little help or direction with this one.
Thanks,
Click to expand...
Click to collapse
Just a bump I still haven't had a response from any of the forums I've posted on.
any one have a Samsung technical repair line I can call?

A little bump in this old post.
Let me know if anyone had a work around
Sent from my GT-I9300T using Tapatalk 2

Related

[GUIDE] Maximum Battery - Maximizing your battery life with CM7 ROM by NeoLojik

UPDATE [11th September 2011]
Modified the SetCPU profiles:
Removed AC-charging Overclock (subject to temperature warnings mentioned in replies)​Reduced some MAX values (has added 5 hours of real-world battery use and makes no noticable difference in performance)​Added an optional < 101% profile to default the maximum clock speed to 729MHz (does not reduce performance, adds 2 hours effective runtime)​Specified the Priority values (which I had forgotten to mention originally)​
Introduction - The Desire S Battery Problem
As a fellow Desire S owner, you no doubt agree that it is a lovely phone: sleek, thin, relatively light, feature-filled... almost everything anyone could ever want from a phone!
However...
As a fellow Desire S owner, you no doubt agree that the battery life (on the Stock Sense ROM, regardless of how strict your PWM settings) is rather pathetic.
I have two HTC Desire S phones (one for myself, one for my wife), and both of them have almost exactly the same runtime (give or take a few minutes) when run in identical test conditions... no more than 18 hours (almost all of which with the display turned off) between charges, and less than 8 hours average with light-to-moderate screen-time when in use.
Bottom line: it's rather pathetic, and unacceptable.
Thankfully, we have options now... and this guide provides you with the option I have chosen for my Desire S phones.
Introduction - The Sacrifice
HTC Sense is (to many) considered a very "pretty" GUI, with nice animated transitions, a rounded feel etc, however it comes at a price: it's a battery hog!
I have played with many Sense 2 and Sense 3 ROMs on the Desire S, all of which share the common result of dimished battery runtime...
Bottom line: The simplest way to get more battery life is to sacrifice Sense entirely!
Just to point out: HTC Sense is the only sacrifice this guide makes in the persuit of optimal battery life! Unlike other guides, this one doesn't compromise any other features, or ANY performance (in fact, I've found performance with the setup described here to be even better than the stock ROM... noticably so!)
DISCLAIMER
I cannot (and will not) be held responsible for any losses or damages resulting from your use of this guide or the materials it contains. If you brick your phone, you've done something wrong and the fault is your own.
You should follow this guide with a fully charged battery, and if possible perform all steps involving a PC from a Laptop, with your phone connected via USB to minimize the risks associated with sudden power loss on your mains supply.
Stage 1: S-OFF
Aside from a lucky few whose Desire S came with S-OFF as a factory default, most of us have S-ON handsets.
With S-ON, you cannot flash a custom ROM onto your Desire S... but fear not, as there is now a FREE (and insanely simple) way to unlock our handsets, giving us the precious S-OFF we require.
You will require the Android SDK to be installed on your system, as well as the USB drivers for the HTC Desire S (these are installed as part of HTC Sync, though you should close HTC Sync from the system tray before proceeding as the S-OFF process will refuse to run with HTC Sync running at the same time)
Head on over to http://revolutionary.io/ to download their tool. This guide presumes you are using Windows, though it should be easy enough - if you're a Linux user - to adapt this information for your Linux platform.
Once you press the link to download Revolutionary, you will notice that a form appears asking for certain information. You'll see a screenshot of this below, but before we get to that there's something you must do...
Open a Command Prompt window from the Platform-Tools directory of the Android SDK.
From that Command Prompt window, type adb devices. Presuming you have the HTC Desire S drivers installed correctly, and your handset connected to your PC via USB, you should something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LEAVE THIS COMMAND PROMPT WINDOW OPEN, WE'LL NEED IT AGAIN SHORTLY
The third line of text begins with your handset's serial number.... you will need to enter this into the form on the Revolutionary website in order to generate your Beta key:
Once the Revolutionary zip file has downloaded, extract its contents into a folder on your PC (doesn't matter where, so long as you have access to that location).
Run revolutionary.exe following the instructions provided (it's a very quick and simple process... the automated portion of which shouldn't take more than 2 or 3 minutes to complete)
When it prompts you to install the Recovery mod, do it! You will need it for the next stage of this guide!
Your HTC Desire S now has S-OFF, is equipped with a version of ClockWork Recovery, and is ready to recieve the custom ROM! (All is good with the world).
Stage 2: The Custom ROM
IMPORTANT - THIS WILL FACTORY RESET YOUR PHONE (UNAVOIDABLE) SO DON'T FORGET TO BACK UP WHATEVER YOU NEED BEFORE YOU PROCEED WITH THIS GUIDE! YOU HAVE BEEN WARNED!
NOTE You will either need a spare MicroSD card, or to back up your existing MicroSD card and make it accessible to have files written to it from your PC (I use a card reader, but you can always use the USB Mass Storage feature of the phone itself to access the SD card in your phone from your PC)
The custom ROM of choice is NeoLojik's CyanogenMod 7, lovingly and paintakingly prepared especially for our HTC Desire S handsets, with quite probably the most prompt and spectactular support from NeoLojik himself.
I have chosen NeoLojik's CM7 ROM because it has proven (after exhastively testing other ROMs for the Desire S) to provide me with the very best battery performance, as well as all of the settings you will tweak as part of this guide.
Download (from the ROM's thread linked above):
The latest version of his ROM
The recommended Tiamat Kernel
The recommended version of the Google Apps package
To save time later, download The Android Market 3.1.3 APK
(You can download the APK from your phone directly after you've completed this portion of the guide, if you prefer)
Place the three ZIP files, as well as the Android Market APK, on the root folder of your MicroSD card (by "root" I mean the initial path of the SD card, which is whatever drive letter it mounts as on your Windows PC - e.g. "H:\")
Now, with your phone still connected to your PC via USB (and the SD card put back into your phone, if required), return to the Command Prompt window we used earlier and type adb reboot recovery
Now direct your attention to your phone
Once the Recovery Menu has loaded (should take about 30 seconds) we will follow some simple instructions below... but first, a few points on how to use Recovery:
Use the Volume Up and Down buttons on your handset to highlight one of the displayed options
Use the Power button to trigger the highlighted option.
wipe data/factory reset
wipe cache partition
apply update from sdcard
choose zip from sdcard
update-cm7.1.0-RC1-DesireS-Nexx-signed.zip (or whatever the ROM's filename is at your time of downloading... it will change as the ROM evolves)
apply update from sdcard
choose zip from sdcard
Tiamat_Saga-v1.1.2.zip (or whatever the filename is for the recommended Tiamat kernel at your time of downloading)
apply update from sdcard
choose zip from sdcard
gapps-gb-20110613.zip (again, filename might be slightly different for you)
Remembering with each selection to navigate to the "YES" option in the confirmation menu (this exists to prevent you from accidentally flashing the wrong file onto your phone)
Now, from your PC (or from the Recovery menu... doesn't matter which), you want to reboot your phone! To do this from the PC, you will just type adb reboot into the Command Line window we used previously.
Your phone will now boot with the new ROM (CyanogenMod), and has been factory reset (so you'll have to run through the first-run configuration wizard).
NOTE: Don't be scared if (after the boot animation disappears) the screen remains black for a minute or so! The first boot of the new ROM (especially with the Tiamat Kernel) does take a bit longer than every subsequent boot there-after. Just give the phone a few minutes, and press the Power button. You SHOULD see the Lock screen once the device is ready!
Run through the first-run wizard following instructions provided (fairly strait forward), though keep in mind that (at the time of writing) the wizard does not prompt for a WiFi connection until AFTER it attempts to log in to your Google account! Fear not, though, as when it fails to connect to your Google account (presuming you don't have Mobile Data available to you), it'll then prompt for a WiFi network and repeat the Google account login afterwards.
Once you have completed the first run config, open the "File Manager" app included as part of the ROM.
Navigate to /sdcard and run the com.android.vending-3.1.3.apk file. You'll be prompted to allow unknown sources, you want to tick that box and click on the APK again.
Once you've installed this, you will be running the latest (and greatest) version of Android Market, which (amongst other things) enables you to use a different Google account for your Apps (very useful if you want to install your paid applications on your wife's phone, as I have)
Welcome to CyanogenMod!....
Stage 3: Battery-saving Mega Settings [Menu-by-Menu]
The Settings I'm providing you here are the results of countless hours of experimentation (as well as logic and common sense). They have proven to provide the best degree of battery runtime with absolutely no performance or feature sacrifice!
If a menu or entry within a menu isn't mentioned, it's because it has no bearing on power saving!
Wireless & networks
Wi-Fi settings
Network notification = OFF
Press the Menu button, then Advanced
Wi-Fi sleep policy = NEVER​
Call settings
Vibrate on answer = OFF
Vibrate every 45 seconds = OFF
Vibrate on hangup = OFF (NOTE: I leave this ON as my one concession as it's the only way you will know if a call drops out on you unexpectedly!)
Vibrate call waiting = OFF
Always use proximity = OFF
Enable sensor rotation = OFF
Voicemail notifications = ON (it doesn't save power, but seriously... you want it on!)​
CyanogenMod settings
Display
Automatic backlight
Light sensor filter > Enabled = OFF (If enabled, unnecessarily drains more battery life! The feature itself is pointless as there is no difference to the UX with it Enabled or Disabled!)​Light levels
Use custom = ON
Screen dim level = 14
Allow light decrease = ON
Edit other levels...
This is what I consider to be the most optimal set of levels:
Lower | Screen | Buttons
0 | 21 | 2
160 | 31 | 2
255 | 35 | 2
320 | 40 | 0
640 | 50 | 0
1280 | 75 | 0
2600 | 90 | 0
5800 | 130 | 0
8000 | 200 | 0
10000 | 255 | 0
Press Save & apply (scroll to the top to find the button)
NOTE: You may want to play around with some of the values in this table, as screen brightness is not a "one size fits all" affair, and what I can see clearly might not be so clear for you (or vice-versa). Basically, use those levels as a starting point, and tweak them from there until you find the best settings for you in various lighting conditions.
I will say this, you don't want to set the Buttons value above 0 if you can see the buttons even faintly at a given light level. The backlighting for the buttons is a surprising battery drain (it's calculated as part of the Screen's power consumption in the Battery Usage menu). Bottom line: if you don't need any lighting on the hardware buttons in order to use them even in pitch blackness, then set the value of Buttons for each set in the table to 0 and squeeze more life out of your battery!​
Performance (press OK when the warning is displayed)
CPU settings
Available governors = SMARTASS ("SMARTASS" has been designed specifically [and brilliantly] to scale the CPU frequency with such a perfect balance of performance-on-demand versus power saving... it's the perfect choice!)
Min CPU frequency = 192
Max CPU frequency = 1036 (We'll be using SetCPU [full version, bought from the Market] to set up some magical CPU profiles later in this guide, saving us LOTS more battery life!)
Set on boot = ON​
Sound
Haptic feedback = OFF (Remember: The phone's vibrator consumes more power than playing a beep or other short tone through the speaker at even the highest volume!)​
Accounts and sync
Auto-sync = OFF (Auto-sync being disabled saves both battery power, as well as bandwidth on your Mobile Data tarif [2G and/or 3G dependant on carrier]. Really, you should just "sync on demand" as and when you want/need to!)​
This concludes the Settings portion of the guide!
Stage 4: SetCPU (for ROOT users) configuration
SetCPU for ROOT Users is available for on the Android Market for just £1.25 (or $1.99 USD). Not only does this program enable you to overclock/underclock your phone's CPU, but more importantly it enables you to provide Profiles, to scale the CPU based on the operational status of your phone.
This is well worth the infintismal pricetag, as the potential power savings (at no performance cost) is more than significant!
Open SetCPU, go to the Profiles tab:
Enable = ON
Notifications = ON (Really this is up to you! I like to have notifications for when the profile is changing to ensure that the CPU is scaling properly, and to ensure that my profiles are the best they can be for performance/battery balance)
Add Profile
Profile = Charging AC
Max = 1036800 (Potentially, you could set it up to 2GHz, but I have stability (and heat) concerns, and I can't possibly see any circumstance where 2GHz would be remotely useful! If you do elect to overclock (particularly whilst charging), you will need to add a profile (with 100% priority) to drop the Max value if the temperature exceeds 45 C)
Min = 192000
Scaling = smartass
Press Save​
Add Profile
Profile = Charging USB
Max = 1036800 (Basically 1GHz [original] CPU clock. We don't want to bleed into the minimal input of power provided by USB, so this is the best setting to use)
Min = 192000
Scaling = smartass
Press Save​
Add Profile
Profile = Battery <
Battery < = 75%
Max = 652800
Min = 192000
Scaling = smartass
Press Save​
Add Profile
Profile = Battery <
Battery < = 50%
Max = 576000
Min = 192000
Scaling = smartass
Press Save​
B]Add Profile[/B]
Profile = Battery <
Battery < = 30%
Max = 422400
Min = 192000
Scaling = smartass
Priority = 80
Press Save​
Add Profile
Profile = Screen Off
Max = 345600
Min = 192000
Scaling = smartass
Priority = 60
Press Save​
Add Profile
Profile = Time
Time = 01:00 - 08:00 (NOTE: Substitute the given range with whatever your daily sleeping hours are!)
Max = 345600
Min = 192000
Scaling = smartass
Priority = 70
Press Save​
The following profile is optional... and (if used) would specify your default clock speed
Add Profile
Profile = Battery <
Battery < = 101%
Max = 729600
Min = 192000
Scaling = smartass
Press Save​
Feel free to experiment with other profiles as well! Perhaps you may want to procedurally reduce your CPU speed based on Battery % in a more gentle way... this is certainly possible, and would squeeze even more life out of your battery.
You should also feel free to use lower MAX values for each setting (I would strongly advise against higher values) if you feel that the lower clock speed makes little-to-no noticable difference in performance as you use your phone.
Personally, I notice no difference between 729600 and 1038600!​
Stage 4: Recalibrating your Battery
Install the Battery Calibration app (FREE on the Android Market).
If your phone isn't charged, charge it up so that it is showing 100% (with the Green LED lit).
Run Battery Calibration and press the Battery Calibration button. Immediately unplug the power/USB cable from your phone, and allow it to run (as normal) until fully discharged.
Once the phone has switched itself off, plug it into the AC cable (using the mains charger).... and LEAVE YOUR PHONE SWITCHED OFF until the LED indicator is lit green!
You may want to repeat the discharge/recharge cycle one or two more times (as many people claim that this provides a better calibration)... though really that just entails running your phone on the battery until it is fully discharged, then allowing it (whilst switched off) to fully recharge on the mains adapter (AC)... which is not what most people would normally do as a routine.
Potential Stage 5: Tasker
Tasker (£3.99 on the Android Market) enables you to create profiles which automatically change various settings based on one or more given criteria. This even includes the ability to switch on and off features of your phone such as WiFi, Bluetooth, GPS, GSM, Mobile Data and Airplane Mode.
By creating suitable Tasker profiles, you can squeeze even more battery life out of your phone!
If it's of benefit to people (let me know in the comments) I can expand this guide to include step-by-step instructions on creating the various profiles I would recommend in order to squeeze more battery runtime out of your phone without sacrifising features/functionality.
General Battery Storage/Maintenance Advice (Applies to all Lithium-Ion Batteries, including those used in Laptops)
To prolong the operational lifespan of your battery, you should not really allow your battery to run for very long below 50% charge, as "topping up" a half-charged battery generates less wear and tear on the battery, prolonging its overall lifespan.
NEVER leave your phone fully discharged for more than an hour, or the LiIon cells will begin to degrade, meaning your battery will never be able to physically hold as much charge. Indeed, the longer you leave a discharged battery, the less overall capacity your battery will retain.
NEVER store your battery (even if the phone is running at the time) in cold conditions! As a general rule of thumb, if it's "a little chilly" for you, it's unhealthy for the battery!
Both of the above tips form respectively the Number 1 and 2 causes of battery death! Don't let your battery become another statistic!
If - like me - you have one or more "spare batteries", you will likely be tempted to store them when they are fully charged (100%). This sounds like a good thing to do, but actually it can have (to a slightly lesser degree) the same damaging effect on the battery as leaving it fully discharged for any prolonged period of time!
The absolute best level of charge at which you should store a battery is at 50%, or as close there-to as possible!
Dependant on how often you find yourself recharging your battery, you should recalibrate it between every 3 to 6 months (the more often you discharge/recharge, the less often you should recalibrate).
Also, you should ALWAYS recalibrate after having flashed a new (or updated) ROM and/or Kernel!
My results using the exact configuration [excluding Tasker] detailed in this guide...
As I stated above, with the way I use my Desire S, I was lucky to get 8 hours of what I would call "light-to-moderate" use whilst running on the battery!
With the configuration detailed in this guide, I have now had a successful "100% to discharged" usage of 46 hours (under the exact same usage conditions as when I was using the stock ROM factory-installed on the phone (and updated OTA ~ a week ago).
This is a VERY significant improvement, though I must stress that results will vary heavily based on how much (or what) software you're running on the phone, how often you're interacting with it, how long you spend in calls etc.
Basically, every phone is different, and every operator (me, you, everyone) is different.
Please also keep in mind that your phone won't "settle in" to the new settings in terms of battery runtime until you've done 2 or 3 discharge/recharge cycles (as explained in the Battery Calibration portion of this guide)
Conclusion
There are plenty of third-party ROMs out there, and (obviously) I can't physically test them all! I have tested what I believe anyone would consider to be a perfectly suitable number (more than a dozen now), and have found the exact combination detailed in this guide to provide the very best battery runtime for me.
I understand that some of you will likely have your own ROM preference (for various reasons), but I hope that at least some sections of this guide will be useful to you.
If you just want to get the very best battery performance out of your Desire S, and either don't particularly care what ROM you use, or (like me) happen to love Cyanogen anyway... this guide will fit you like a glove!
Need any more advice?
No problem... post your comments and questions as a reply to this guide, and I'll answer anything I can, as promptly as possible (please consider that I have a company to run, and a life beyond the Internet... so replies might not always be "instant")
I hope you like this guide, and more importantly... I hope you enjoy your new-found battery runtime!
Unfortunately, I'm a Sense fan. ...so will take persuding to move away from the interface, as been using it for many years, but, I still appreciate a piece full of insight and advice written for the communities benefit. Well done and thanks for sharing.
I'll reference this in the development INDEX next to CM7 ROMS
ben_pyett said:
Unfortunately, I'm a Sense fan. ...so will take persuding to move away from the interface, as been using it for many years, but, I still appreciate a piece full of insight and advice written for the communities benefit. Well done and thanks for sharing.
I'll reference this in the development INDEX next to CM7 ROMS
Click to expand...
Click to collapse
Yeah, I can understand why so many people strictly adhere to Sense ROMs... for me the "slight prettiness" of Sense doesn't justify the hammering of the battery... especially as I actually preffer the L&F of Cyanogen anyway
If I have gotten 18 hours with almost always screen off I returned the phone. With nomal usage my phone last more than one day. Keeping the screen almost always off last almost 2 days with wifi and sync turned on (to be honest, never reached that again). ROM is whether LBC or rooted stock whith stock HTC kernel. So I can find any problem there. Nevertheless, this is a smartphone, and I always have a charger with me
I will try CM and what the battery life is like.
Profile = Charging AC
Max = 157440 (Potentially, you could set it up to 2GHz, but I have stability concerns, and I can't possibly see any circumstance where 2GHz would be remotely useful!)
Min = 192000
Scaling = smartass
Press Save
Fried CPU kgo. Overclock + Charging = Excessive heat being generated.
zeekiz said:
Profile = Charging AC
Max = 157440 (Potentially, you could set it up to 2GHz, but I have stability concerns, and I can't possibly see any circumstance where 2GHz would be remotely useful!)
Min = 192000
Scaling = smartass
Press Save
Fried CPU kgo. Overclock + Charging = Excessive heat being generated.
Click to expand...
Click to collapse
I have tested this setting with my own phone, and the heat increase was LESS than 1 Celcius (infintismal)... sure, if you wanted, you could use a lower value.
Its your call, your thread, I just feel that it isn't a good idea. At least even consider placing a warning adjacent to it.
LaKraven said:
I have tested this setting with my own phone, and the heat increase was LESS than 1 Celcius (infintismal)... sure, if you wanted, you could use a lower value.
Click to expand...
Click to collapse
You could add a setcpu profile for limitting the temperature. I dont overclock, but when im using my phone while charging, it gets hot, so I limit the temperature at 41.1 C , so 768mhz - 245mhz , on demand.
lbc ROM, stock kernel
zeekiz said:
Its your call, your thread, I just feel that it isn't a good idea. At least even consider placing a warning adjacent to it.
Click to expand...
Click to collapse
I've updated the guide (see the update notes at the very top of the post). The on-AC overclock setting has been removed, and I have placed a warning about overclocking next to it.
Updated the post to address a typo in one of the SetCPU profiles (I missed a 0 from the end of 345600).
I will have done this process by tomorrow, I'm sure - even bought Tasker. - Hoping I wont damage something in the process since I've never dealt with an HTC phone before. :/ Since my mom bought it to me as a present, she just peeks in from time to time to check wth am I doing with it - gotta keep a satisfied grin on my face all the time while I'm figuring how to fix this problem lolz
Really you just need to follow instructions (read everything through at least twice before you begin), be patient... and double-check everything you're abuot to do before you do it.
You can't do any more than that!
I've flashed both of these phones so many times now, and the only mistake I ever made was forgetting to clear the cache (Which results in an infinite boot loop or "soft brick", easily recovered by constantly typing "adb reboot recovery" in your Command Prompt, which will eventually make the phone re-enter recovery mode (exiting the infinite boot loop), at which point you can wipe, clear cache, reflash, and relax!
LaKraven said:
Really you just need to follow instructions (read everything through at least twice before you begin), be patient... and double-check everything you're abuot to do before you do it.
You can't do any more than that!
I've flashed both of these phones so many times now, and the only mistake I ever made was forgetting to clear the cache (Which results in an infinite boot loop or "soft brick", easily recovered by constantly typing "adb reboot recovery" in your Command Prompt, which will eventually make the phone re-enter recovery mode (exiting the infinite boot loop), at which point you can wipe, clear cache, reflash, and relax!
Click to expand...
Click to collapse
Funny, so true, in fact, did just that myself about two minutes ago while testing another ROM, meant trip to PC, plug in, power on, and then sorted adb reboot recovery
Swyped from HTC Desire S using XDA Premium
ben_pyett said:
Funny, so true, in fact, did just that myself about two minutes ago while testing another ROM, meant trip to PC, plug in, power on, and then sorted adb reboot recovery
Swyped from HTC Desire S using XDA Premium
Click to expand...
Click to collapse
Good to know I'm not the only one! It's such an easy step to overlock... just a good job it's also the least fatal mistake to make!
and then this
.. Ther is no Path in User, but there is in System...Geez, so tired..What do....:/ I'm all set to flash, just this thing I think...
You need to reinstall Java JDK.
This has happened to me before!
LaKraven said:
You need to reinstall Java JDK.
This has happened to me before!
Click to expand...
Click to collapse
Thx man I did that, I also don't have any command prompts in here :
C:\Program Files (x86)\Android\android-sdk\platform-tools
Bombastc said:
Thx man I did that, I also don't have any command prompts in here :
C:\Program Files (x86)\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
Open Windows Explorer, navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools
Hold down SHIFT and RIGHT-CLICK in on that folder
Click "Open command line window here"
You're then ready to start using ADB commands
LaKraven said:
UPDATE [11th September 2011]
Potential Stage 5: Tasker
By creating suitable Tasker profiles, you can squeeze even more battery life out of your phone!
If it's of benefit to people (let me know in the comments) I can expand this guide to include step-by-step instructions on creating the various profiles I would recommend in order to squeeze more battery runtime out of your phone without sacrifising features/functionality.
Click to expand...
Click to collapse
I would really like that. Yesterday followed your guide and learning new things as i went about the CyanogenMod. I'm curious now how far my battery will bring me :-D.
At the moment i'm using the trial version of phoneweaver and automateit, which are nice programs, but if tasker is more efficient although having a steeper learning curve, i will switch in an instant.
shizuku said:
I would really like that. Yesterday followed your guide and learning new things as i went about the CyanogenMod. I'm curious now how far my battery will bring me :-D.
At the moment i'm using the trial version of phoneweaver and automateit, which are nice programs, but if tasker is more efficient although having a steeper learning curve, i will switch in an instant.
Click to expand...
Click to collapse
As a tasker convert myself, I can also say that you'll read a great review of some of its functionality and a slightly biased review of the product by wnp_79 as part of his [GUIDE] Update 28/06/11: HTC Desire S Guide (V1.03) For Newcomers to Android which is in a sticky at the top of the forum.

(Step by step) How to work out battery efficiency

Do u know how battery efficient ur smartphone is?
How is the battery efficiency of kernel X compared to that of kernel Y?
Is there an objective way to work out battery efficiency (ie. other than appealing to ur subjective impression)?
Below is my tentative solution to the above questions
Requirement:
1. You need to be able to bootup into recovery mode where u can wipe the battery stat (e.g. CWM Recovery can do that. In most cases, u need a rooted phone to obtain CWM Recovery);
2. You need to be able to take screen shots;
3. CPU Spy (by storm717, free from Google Play. Disclaimer: this author doesn't have any affiliation with the app or its creator )
4. Know the total capacity (in mAH) of ur battery (can be read from the face or the back of ur battery)
Procedure
Step 1. Calibrate the battery level indicator of ur phone
Concerning the battery level, theoretically only two points can be certain: 100% (when the battery is fully charged) and 0% (when it is totally depleted). All in the middle are extrapolations based on either the 100% or the 0% point.
Practically, the 100% point is the only point against which the battery indicator can be accurately calibrated. Below is the how:
1a. Fully charge ur phone. Switch it off when the fully charge indicator is on BUT leave the charger connected to it at this point;
1b. Half an hour later, with the charger still attached, boot up into recovery mode;
1c. Choose "Wipe battery stat" from the recovery menu: (for CWM Recovery) scroll to "advanced", then "Wipe battery stat", then scroll down to highlight "yes, wipe battery stat". When it is highlighted, WAIT FOR 1 MORE MINUTE before u press the Home button to activate it (the wait will make extra sure ur battery level is truly, totally, and absolutely 100% )
1d. When that extra 1 minute is over, press the Home button to activate "yes, wipe the battery stat" --- now, the battery level indicator is accurately calibrated to 100%. (U now can see why u can never totally accurately calibrate against the 0% point: as soon as u reach the true 0%, ur phone is out and u can't reset the battery level indicator to zero when ur phone is out. That's why )
Step 2. Monitor ur battery consumption
2a. With Step 1 completed, reboot ur phone;
2b. From this time on, DO NOT ATTACH UR PHONE TO UR PC VIA USB OR SWITCH OFF OR REBOOT UR PHONE until the whole monitoring process is over;
2c. U may then use the phone any way u wish (with exception 2b above applied), but from time to time (say for every 4 or 6 hours), run CPU Spy and take a screen shot of the results it obtains each time (see for e.g. the pictures attached);
2d. The monitoring should continue until the battery level is around 10%
Step 3. Calculate the rate of battery consumption
After Step 2, u will have multiple screen shots showing ur battery consumption at various levels of battery discharge. U may use the data obtained to calculate the rate of consumption of ur device. Below is how:
3a. Take my own consumption (battery: 2,500 mAH stock battery, phone: Samsung Galaxy Note) as an example --- see Fig 1 attached.
When the battery level is 74%, the CPU stats are as followed:
Deep Sleep: 15h 22m 55s, 90%
200Mhz: 1h 13m 21s, 7%
etc.
Understandably, the rate of battery consumption is different at different CPU frequencies. So, we will calculate the respective rates one by one (when the data obtained permit so).
3b. To calculate the rate of consumption (in mA/sec), when the phone is in Deep Sleep, C(Deep Sleep):
Amount of battery used = 2,500 mA * (100 - 74)% * 90% = 585 mA
= C(DS)*(15*60 *60 + 22*60 +55)sec
Thus, C(DS) = 0.0106 mA/sec ---------------------------------------(1a)
Similarly for C(200Mhz) (rate of battery consumption when CPU is at 200Mhz)
C(200Mhz) = 0.0103 mA/sec ----------------------------------------(2a)
In theory, we can similarly calculate the rates C(500Mhz), C(800Mhz), etc. However, becoz the consumption % for those frequencies are below 1 and CPU Spy rounds all decimals to the nearest digit, so in practice the figures obtained cannot be used.
3C. Now, let's look at Fig 2, when the battery level is at 47%. The data obtained are:
Deep Sleep: 19h 29m 27s, 81%
200Mhz : 3h 15m 1s, 13%
etc.
Thus, C(DS) = 0.0153 mA/sec ----------------------------------------(1b)
C(200Mhz) = 0.0147 mA/sec -----------------------------------(2b)
Hence in my case (Samsung Galaxy Note, GB 2.3.6, Kingdroid v5.4 ROM, Speedmod K1-5 kernel, 2,500 mAH stock battery) the rate of battery consumption is around 0.011 to 0.015 mA/sec.
Limitations
1. The results obtained from the above method to calculate rates of battery consumption is system-dependent, meaning that meaningfully comparison between results can only be made for the same combination of phone + battery (system). Say u obtain C(Deep Sleep) for certain phone, OS, ROM, kernel is, for instance, Z mA/sec, this doesn't mean that for the phone model having the same OS, ROM, kernel, C(Deep Sleep) must be Z, becoz even for the same models the hardwares may be different and the battery may also be a bit different (different batches may behave slightly differently; and more importantly, the AGE of a battery can have significant effect on its performance, so batteries of the same model and the same batch may perform different owing to their different age). Nonetheless, u may make meaningful comparison when u compare results obtained for different OS's, ROM's, or kernels u install to ur system (phone + battery).
2. The rate of battery consumption with CPU at higher frequencies may not be derivable owing to the rounding of figures by CPU Spy.
******************************
Pls click "Thanks" if u find this makes good sense
reserved for possible future use.
Interesting post!
What do you say if I only charge my phone to full, use Battery Calibration, reboot the phone. Will the phone still be 100% charged? Also, I think randomly using your phone between a certain range of battery levels, say 100-10%, doesn't really guarantee exact data for calculations. Maybe a stress-testing app will do a better job. Have you tested My Battery Drain Analyser and compared your results to its reading?
Please correct any technical fact if needed!
Your info is interesting but you may post it on the battery thread already is placed in general

GALAXY Note 10.1 brightness problem

I have problem on my Note 10.1,.when is my battery on 5 % i get low brightness.Does anyone know how to fix this,to set brightness on max when is battery low????
Samsung galaxy note 10.1 n8000 4.1.2
dekar123 said:
I have problem on my Note 10.1,.when is my battery on 5 % i get low brightness.Does anyone know how to fix this,to set brightness on max when is battery low????
Samsung galaxy note 10.1 n8000 4.1.2
Click to expand...
Click to collapse
that's a feature. Charge it
shaun298 said:
that's a feature. Charge it
Click to expand...
Click to collapse
how???? im unable to change brightness when battery is 5 %
dekar123 said:
how???? im unable to change brightness when battery is 5 %
Click to expand...
Click to collapse
Dud, just charge it up.
Aluyi said:
Dud, just charge it up.
Click to expand...
Click to collapse
It's not a solution,my chinese 9` inch tablet whith 5 % off battery could stand mabye 20 minutes,is that on all note 10`1 tablets???
Does anyone know how to get full brightness when my battery is 5 %???????
There is no way to change it.
It propably protects the battery to become too empty without getting your device plugged in time. "Too empty" means that sometimes if you drain your litium battery empty totally, it wont start to charge it at all. So it is there for protecting you and your device without having next problem not being able to charge it.
Sent from my GT-N8000 using Tapatalk 4
enigma_x said:
There is no way to change it.
Click to expand...
Click to collapse
Have you ever investigated this subject that you are so sure? If you cannot do it - don't assume that no one can.
I don't also see any relation between dimming the screen and protecting the battery of getting broken. If 5% level is a level on which the battery should be charged because of the damage risk, then it would be absurd to dim the screen (ie take an action aimed at saving the remaining power so the user can work a few minutes longer on the last remaining 5% until it reaches 0 or 1% = drain battery even more = in your theory: increasing the risk of the damage even more), and not to turn off the device at all. Be aware, that Samsung indeed implemented a protection aimed to secure the user of the risk of breaking the battery (well, I don't think it's the clue anyway - iI guess the main purpose is in preserving user of data loss/filesystem corruption, which is possible to occur when the system is being shutdown in an "immediate" way, without chance to perform shutdown sequence properly) due to full discharge, but it is triggered on 0 - 1% level and is resulting in starting a "regular" system shutdown, aimed mainly to save all the working data before user loses it *** See comment at the very end of my post for additional info about changing this behavior, which is confirmed to work by myself...
It is almost ALWAYS possible to mod behavior of the system, especially by decompiling system apps and modyfing smali, which is not extremely difficult/impossible by the way, as the community has released such a solutions for many issues/feature requests, concerning even n8000 itself (ink lockscreen, syscope disable, power menu, flashable themes...).
In this case, I can see another possibility, which is even less intrusive to the system; AFAIR the percentage level of 5% is not embedded in some system or framework app, but it is defined in one of the system's apps preferences (guess settings provider? dont remember...), in sqlite database. And sqlite database can be easily accessed and its content can be modified by sqlite tools, ie sqlite3 binary from command line, and even some apps from play store. Then, you shall be able to lower the value to, for example, 1%, so the screen backlight will be turned off with further delay, ie. at REALLY critical power level of 1%..
EDIT: Didn't found above setting, dont have time for this, but found another one (at database lying at com.android.provider.settings) - "dim_screen" which is set 1 by default. Maybe changing it to 0 with any SQL editor will force NOT to dim screen at all.
An for the begin, I have a solution that is very very very possible to work...
As for now, I have not tested it, especially if the critical battery level setting (default 5%) has direct relation to the battery level on which screen is dimmed, but I am ALMOST sure about it, as the crtitical level setting that I am talking about (no matter where it is stored...) is recognized system-wide.
Oh, almost forgot, the solution!!!
Install Xposed Framework (search for it on xda if u dunno what it is) + module XBatteryThemer - apart of other options, it has the option to lower critical battery level (as well as two other levels, which determine displaying the low battery alert popup) to as low as 1%. Your screen shall no longer dim at 5%.
*** actually, there is another one Xposed module (CriticalBatteryShutdown, or something...?) which can force the device not to turn off when battery reaches some level between 0 and 1%, which is arbitrary action by default. With this mod the device is working untile theres really no power left, which sometimes can give you additional 10 minutes. A
dekar123 said:
Does anyone know how to get full brightness when my battery is 5 %???????
Click to expand...
Click to collapse
Please correct me if I´m wrong, does that make sense to you if your battery is 5% and you thinking of raising the slider higher ? Maybe you should check your energy saving settings. My two cents.
esgie said:
Have you ever investigated this subject that you are so sure? If you cannot do it - don't assume that no one can.
I don't also see any relation between dimming the screen and protecting the battery of getting broken. If 5% level is a level on which the battery should be charged because of the damage risk, then it would be absurd to dim the screen (ie take an action aimed at saving the remaining power so the user can work a few minutes longer on the last remaining 5% until it reaches 0 or 1% = drain battery even more = in your theory: increasing the risk of the damage even more), and not to turn off the device at all. Be aware, that Samsung indeed implemented a protection aimed to secure the user of the risk of breaking the battery (well, I don't think it's the clue anyway - iI guess the main purpose is in preserving user of data loss/filesystem corruption, which is possible to occur when the system is being shutdown in an "immediate" way, without chance to perform shutdown sequence properly) due to full discharge, but it is triggered on 0 - 1% level and is resulting in starting a "regular" system shutdown, aimed mainly to save all the working data before user loses it *** See comment at the very end of my post for additional info about changing this behavior, which is confirmed to work by myself...
It is almost ALWAYS possible to mod behavior of the system, especially by decompiling system apps and modyfing smali, which is not extremely difficult/impossible by the way, as the community has released such a solutions for many issues/feature requests, concerning even n8000 itself (ink lockscreen, syscope disable, power menu, flashable themes...).
In this case, I can see another possibility, which is even less intrusive to the system; AFAIR the percentage level of 5% is not embedded in some system or framework app, but it is defined in one of the system's apps preferences (guess settings provider? dont remember...), in sqlite database. And sqlite database can be easily accessed and its content can be modified by sqlite tools, ie sqlite3 binary from command line, and even some apps from play store. Then, you shall be able to lower the value to, for example, 1%, so the screen backlight will be turned off with further delay, ie. at REALLY critical power level of 1%..
EDIT: Didn't found above setting, dont have time for this, but found another one (at database lying at com.android.provider.settings) - "dim_screen" which is set 1 by default. Maybe changing it to 0 with any SQL editor will force NOT to dim screen at all.
An for the begin, I have a solution that is very very very possible to work...
As for now, I have not tested it, especially if the critical battery level setting (default 5%) has direct relation to the battery level on which screen is dimmed, but I am ALMOST sure about it, as the crtitical level setting that I am talking about (no matter where it is stored...) is recognized system-wide.
Oh, almost forgot, the solution!!!
Install Xposed Framework (search for it on xda if u dunno what it is) + module XBatteryThemer - apart of other options, it has the option to lower critical battery level (as well as two other levels, which determine displaying the low battery alert popup) to as low as 1%. Your screen shall no longer dim at 5%.
*** actually, there is another one Xposed module (CriticalBatteryShutdown, or something...?) which can force the device not to turn off when battery reaches some level between 0 and 1%, which is arbitrary action by default. With this mod the device is working untile theres really no power left, which sometimes can give you additional 10 minutes. A
Click to expand...
Click to collapse
Did I say that 5% is the minimum level? No, I didnt. All I said it is, it gives you more time and IF you drain your battery EMPTY, it may not charge. Of course there are self-protection manager already, but as you know, they dont always work as they should. There are several questions on net what to do when the phone doesnt start charging because they drained the battery to a state to auto-shut off. I dont understand why anyone would like to drain the battery almost empty and in a bad scenario you have a dead battery. Will it happen with your device? Maybe or maybe not. And it is not even healthy for a lithium battery to let it full disharged/cycled on everytime.
And yes I have read that there are apps that allows you to change this but only if your device is rooted. Never tried, mine is not rooted.
This will explain it very well: http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
Sent from my Galaxy Note 10.1 (N8000).
---------- Post added at 07:01 PM ---------- Previous post was at 06:55 PM ----------
Aluyi said:
Please correct me if I´m wrong, does that make sense to you if your battery is 5% and you thinking of raising the slider higher ? Maybe you should check your energy saving settings. My two cents.
Click to expand...
Click to collapse
No, you cannot set the brightness by a slider when the battery level is 5%. It automatically goes to a state to save the battery. It is built in the system.
Sent from my Galaxy Note 10.1 (N8000).

[Completed] [Q] Battery temperature too low

Hello
Many of us have the same problem without a clear solution, I know that here are hundreds of post with the same issue but no solution found. I want to solve this problem and help other users.
Symptoms:
- Unable to charge (popup: Charging paused battery temperature too low)
- Unable to use camera flash (Battery temperature too low)
- Unable to charge in off mode (Yellow triangle with a thermometer)
- Thermistor reading up to -25C
Causes and possible solutions:
1. Charging port/flex/board (Dirty, short, broken wire or sensor) (Most of the people said that the problem is solved after clean the charging port with isopropyl alcohol or replace it)
2. Motherboard (Sometimes replace the charging port assembly do not solve the problem. A chemical bath could solve the problem, if not there are some components on the mother board that can be tested and replaced "Really advance technicians") image attached
3. Software (Rarely this problem begins after an upgrade or a change of rom. flash stock rom with odin)
4. Battery (I have read hundreds of post from several forums and nobody solve the problem replacing the battery. Test with another battery before buy a new one. People said that performing a battery status wipe in (home+vol down+power) could solve the problem but I couldn't find anybody that claimed that it works.
Temporal Solutions:
1. Retire the back cover and put your phone one something warm, for example you router. Dial *#0*# scroll down and press thermistor button. connect your phone to computer or wall charger and it should start charging when the CHG/BATT temperature reach -2C or -1C.
My phone normally show CHG temperatures around -7 to -5, but warming it on my router it have reached +6C.
2. Turn off your phone and press home+voldown+power at the same time and hold them until a greens letters show up. Then press vol up and you will see an android icon with the word Downloading..... plug your phone to the wall charger for a while, it will charge.
3. Buy an external charger and another battery and jut keep one of them charged.
4. To solve the flash problem you have to be root user and download Wanam Xposed that app have an option to disable the camara temperature check.
What I am looking for:
I know that should be a way to disable the low temperature warning or set the limits.
Maybe we can create a patch....
I'm not a developer but this problem could be my begining as developer hehehe
I know that the kernel or the drivers in the kernel export the battery temperature readings and status in intents in sys/class/power_supply/ and the JNI (JAVA) batteryservice read that data and make the action (shut down, pause, etc etc....)
Anybody know how to edit batterymanager or batteryervice? It should be via framework....
people said that there is a hidden menu that allow to set the temperature limits but I couldn't find it... its a myth hehehehe.
PLEASE HELP US..... SOME ONE WHO KNOWS ABOUT EDIT KERNEL OR FRAMEWORK ETC ETC.........
Tests:
I opened the phone and disconnect the flex... the battery temperature is fixed in -25C and don't change.... I connect the flex and the temperature is -10C. but constantly.... I believe that when the termistor circuit is open the limit is -25C. Then if the phone is reading less temperature than it should maybe that i due to a high resistance in the flex or board.
My phone is a Samung Galaxy S4 TMO SGH-M919 4.4.4 Stock
htp: s23.postimg.org/60pj79p3v/battery.png (I'm noob can't post images)
Hi,
You need to consider that if hundreds of threads have no solution, then there may not be one. I'd send it in under warranty myself.
But you can ask the experts who own your device for help, here...
> T-Mobile Samsung Galaxy S 4 > T-Mobile Samsung Galaxy S 4 Q&A, Help & Troubleshooting > [HELP THREAD] Samsung Galaxy S4 T Mobile Version | Ask ANY Question | Noob Friendly
Good luck!
HOPE
Darth said:
Hi,
You need to consider that if hundreds of threads have no solution, then there may not be one. I'd send it in under warranty myself.
But you can ask the experts who own your device for help, here...
Good luck!
Click to expand...
Click to collapse
hello
I don't have warranty T_T.
And I sure that it is possible to disable that warning... the thing i how???? hehehehe
I'm sure that for a developer it should be easy.
I read a topic here in XDA where someone had desactivate overheating warning, pacthing the SystemUI file fixing battery health status....
THANKS Darth
If it is possible, the thread I linked to above is where to ask. ?

[Guide]Using the Advanced Charging Controller (ACC) Magisk Module with Pixel 3a XL

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

Categories

Resources