All credit for this solution goes to Vlad_z from the 10.1 Forums!
There has been a lot of confusion regarding some battery issues that arose after flashing the ICS port from kallt_kaffee so I thought I'd make this post to have it easily findable instead of buried inside one of the threads.
First of all: YOUR BATTERY IS NOT BROKEN! RELAX!
Now, lets get into what causes the problem:
There is a chip in our tabs that measures the voltage and then reports to the OS.
This chip has to be calibrated properly and for some reason the ICS port discalibrated it.
To recalibrate it, it needs to take two voltage measurements to once again gauge the battery correctly.
For in depth explanation read HERE
There is a way of reading the voltage of our tab, which is the only way to correctly show the charge.
Either use terminal emulator on the tab then its:
cat /sys/class/power_supply/battery/voltage_now
or use adb (also works from recovery)
adb shell cat /sys/class/power_supply/battery/voltage_now
This will give you a number which is the current voltage of the battery.
Fully charged its around 4100 completely drained around 3400!
If your OS reports low battery and the charge reads 4000 or 3900 or some other high number you definately need to recalibrate!
Here is how you get it calibrated again:
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
Click to expand...
Click to collapse
Hope this helps you out!
Don't take any shortcuts! Let it sit for the hour while switched off! This is vital for the recalibration!
After completing this my tab now correctly shows 100% charge and looks to have normal discharge once again.
Good that you made a thread for this here. People tend to get confused with many options lying here n there.
Sent from my GT-P7300 using xda premium
I just have to say that this method did NOT work for me, and believe me I have tried many times over the last couple of weeks. The only thing that finally worked for me was to completely drain (in CWM) and then charge it to 100%, turn off, wipe battery stats (voodoo for some) and turn back on.
Idlekilla said:
I just have to say that this method did NOT work for me, and believe me I have tried many times over the last couple of weeks. The only thing that finally worked for me was to completely drain (in CWM) and then charge it to 100%, turn off, wipe battery stats (voodoo for some) and turn back on.
Click to expand...
Click to collapse
wiping battery stats has no effect on this problem. it just erases your usage data! (just thought id let you know)
the way you did it only worked for some time for me. all was looking good but soon the random "drain" started up again. hope you fixed yours for good though!
pseudoheld said:
wiping battery stats has no effect on this problem. it just erases your usage data!
Click to expand...
Click to collapse
Yes, hence the voodoo-reference, but I felt I had to add what I did in any case.
how about battery calibrate from play store, will that help?
iamalone said:
how about battery calibrate from play store, will that help?
Click to expand...
Click to collapse
Don't think so... The problem is with the chip level not os level
Is this battery fix work for ported ICS by KK or for different ROM?
usopheak said:
Is this battery fix work for ported ICS by KK or for different ROM?
Click to expand...
Click to collapse
it will work for ALL roms, seen as it is a fix on the hardware level.
but it was mostly used for the problems caused by the ics port by KK!
however if your battery life seems off with any other rom this will probably also fix it!
How to prevent this problem?
I just flash a A1 custom kernel and I have this bug again.
Wysyłane z mojego HTC Sensation XE with Beats Audio Z715e za pomocą Tapatalk 2
ibanezq said:
How to prevent this problem?
I just flash a A1 custom kernel and I have this bug again.
Wysyłane z mojego HTC Sensation XE with Beats Audio Z715e za pomocą Tapatalk 2
Click to expand...
Click to collapse
could well be that the ported 10.1 kernel is causing this. i got lucky and didn't encounter any problems after flashing A1 custom kernel.
pseudoheld said:
could well be that the ported 10.1 kernel is causing this. i got lucky and didn't encounter any problems after flashing A1 custom kernel.
Click to expand...
Click to collapse
Did you flash the kernel at 100% battery state?
ibanezq said:
Did you flash the kernel at 100% battery state?
Click to expand...
Click to collapse
yeah i think so.
im getting used to only flash with my devices fully charged. on my razr i have to do it because flashing with lower battery can result in big problems, if the initial flash goes wrong so im getting used to charging my tab fully before flashing stuff...
My phone has a little bit over 4100 when fully charged after flashing the nordic sammy release of ICS. But the battery drains fast as hell. So do I have to do this or is something wrong? And also, will going back to GB fix my problem?
Please read 1st post.
just to confirm that flashing the ported ics with 100% battery will not solve the battery issue. When the first rundown cycle happens it will last for the normal 2 days or so but when connecting to the charger, the system thinks that the battery is still empty even if getting close to 4100mV. Calibration will have to be done again.
Also, i am not able to get the adb commands in recovery. Anyone has any clue??
Try mounting /system first in recovery... Then run the adb stuff. That worked for me
Sent from my HTC Desire using xda app-developers app
pseudoheld said:
Hope this helps you out!
Click to expand...
Click to collapse
It did!
Chalk-up another satisfied customer.
Many thanks to you and Vlad_z.
There is a way of reading the voltage of our tab, which is the only way to correctly show the charge.
Either use terminal emulator on the tab then its:
cat /sys/class/power_supply/battery/voltage_now
or use adb (also works from recovery)
adb shell cat /sys/class/power_supply/battery/voltage_now
Click to expand...
Click to collapse
can someone give me a hint if i use adb shell cat /sys/class/power_supply/battery/voltage_now via adb what will show up ...??
cause when i entering adb shell cat /sys/class/power_supply/battery/voltage_now i can't find the 4digit number that indicates highest & lowest voltage on my tab that i found is 7 digit number..
Cheers
soomat said:
can someone give me a hint if i use adb shell cat /sys/class/power_supply/battery/voltage_now via adb what will show up ...??
cause when i entering adb shell cat /sys/class/power_supply/battery/voltage_now i can't find the 4digit number that indicates highest & lowest voltage on my tab that i found is 7 digit number..
Cheers
Click to expand...
Click to collapse
That's the number (you will only get one). In later kernels it seems to be reported as micro-volts instead of milli-volts. So ignore the last 3 digits.
Thus, for the number 3993123 you should just interpret it as 3993 for the purposes of this exercise.
Related
Ok, first, I looked around and tried stuff like battery calibration etc. but no luck, here's what happened:
I got my galaxy ace and rooted it with CF-ROOT, flashed it using the recovery menu that stock already had.
Phone was ok for 1 week, then it started sucking battery like crazy (also charges too fast), 100% lasts something like 5mins...
(at this point it was still stock with rooted kernel)
Flashed a CM ICS ROM from the forum => same results with battery
Went back to stock, no root anymore => battery still the same
Does anyone know how to solve this? Thanks in advance!
Pauloxzak said:
Ok, first, I looked around and tried stuff like battery calibration etc. but no luck, here's what happened:
I got my galaxy ace and rooted it with CF-ROOT, flashed it using the recovery menu that stock already had.
Phone was ok for 1 week, then it started sucking battery like crazy (also charges too fast), 100% lasts something like 5mins...
(at this point it was still stock with rooted kernel)
Flashed a CM ICS ROM from the forum => same results with battery
Went back to stock, no root anymore => battery still the same
Does anyone know how to solve this? Thanks in advance!
Click to expand...
Click to collapse
Why didn't you use the normal .zip that just adds super user? Maybe we have the same type of Ace that is completely incompatible with flashed kernels. Brings battery problems. Only kernels you can use are the ones that come with the rom you installed.
Reflash stock rom and root using any other .zip around the forums.
Because you said you charge it too fast. Try to charge it for 3 hrs. If u see 100 % that doesn't mean that it is fully charged already
Sent from my GT-S5830
Do this, full use your battery till it totally gets dry and charge it to 100% without break..note that your phone should switch off conditon while charging to 100%..
Sent From REVOLUTiON Ultimate Xperia Edition Rom..
:beer:
Clear battery cache and dalvik's cache , then consume the battery tell it reaches zero
And charge it
It worked for me
Sent from my GT-S5830 using xda premium
Is your battery swelled? I mean, is it bulging outside when you place the battery inside the phone?
If yes, then you need to get a new phone
This line is dedicated to OT thanks.RIP OT Thanks
Thanksfor the replies!
Is your battery swelled? I mean, is it bulging outside when you place the battery inside the phone?
If yes, then you need to get a new phone
Click to expand...
Click to collapse
No, the battery is ok.
Why didn't you use the normal .zip that just adds super user? Maybe we have the same type of Ace that is completely incompatible with flashed kernels. Brings battery problems. Only kernels you can use are the ones that come with the rom you installed.
Reflash stock rom and root using any other .zip around the forums.
Click to expand...
Click to collapse
What do you mean by normal zip? As I said, I flashed stock back, no more rooted kernel, but it's still draining battery, shouldn't it have gone back to normal with stock? Should I root again with this normal zip to be able to solve the problem?
Maybe your battery is "gone" (I mean cannot charge anymore). If you can try your phone with another battery borrowed from a friend or buy a new one cheap to be sure the problem is the battery and not the phone. The last option for me is to buy a new original battery a give a try. If you have a method to test the battery out of the phone is best. Good luck
Inviato dal mio GT-S5830
Do 1 thing. Recharge for a long time till 100% . Choose a stock based rom like sgs2 v10. Do full wipes, delete battery stats.bin, Format data,cache, system, sd-ext ( if any ) & flash rom. Reboot & try battery. If it's still the same, go get a new battery..
Sent from my GT-S5830 using xda premium
hey, try this app called nova battery tester. It will tell you a lot about your battery's condition.
You can find it on the play store.
Also check whether your phone is entering deep sleep.
Maybe your battery is "gone" (I mean cannot charge anymore). If you can try your phone with another battery borrowed from a friend or buy a new one cheap to be sure the problem is the battery and not the phone. The last option for me is to buy a new original battery a give a try. If you have a method to test the battery out of the phone is best. Good luck
Click to expand...
Click to collapse
I tried that, the friend's battery on my phone had the same behaviour, and my battery on friend's phone worked fine... so it can't be the battery
Why the hell it won't just work normal if I flashed stock back?
Do 1 thing. Recharge for a long time till 100% . Choose a stock based rom like sgs2 v10. Do full wipes, delete battery stats.bin, Format data,cache, system, sd-ext ( if any ) & flash rom. Reboot & try battery. If it's still the same, go get a new battery..
Click to expand...
Click to collapse
Tried recharging for long time, no luck, also tried many "battery calibration" apps also with no result.
I'm guessing buying a new battery won't solve anything either given the results with the friend's battery
Have you checked your CPU behavior ? Which states it is in, etc
Use CPU spy to find out
Sent from my GT-S5830 using xda app-developers app
Pauloxzak said:
I tried that, the friend's battery on my phone had the same behaviour, and my battery on friend's phone worked fine... so it can't be the battery
Why the hell it won't just work normal if I flashed stock back?
Tried recharging for long time, no luck, also tried many "battery calibration" apps also with no result.
I'm guessing buying a new battery won't solve anything either given the results with the friend's battery
Click to expand...
Click to collapse
Best thing... Send it back to samsung !!! Either you get a repair or a replacement ! ( Provided you are under warranty for the service to be free... )
Sent from my GT-S5830 using xda premium
Pauloxzak said:
Ok, first, I looked around and tried stuff like battery calibration etc. but no luck, here's what happened:
I got my galaxy ace and rooted it with CF-ROOT, flashed it using the recovery menu that stock already had.
Phone was ok for 1 week, then it started sucking battery like crazy (also charges too fast), 100% lasts something like 5mins...
(at this point it was still stock with rooted kernel)
Flashed a CM ICS ROM from the forum => same results with battery
Went back to stock, no root anymore => battery still the same
Does anyone know how to solve this? Thanks in advance!
Click to expand...
Click to collapse
1. Un-root then root again using the normal method which just adds SU.
2. Try charging for 2-3 hours. Sometimes it displays 100% though the battery level might be as low as 15%
3. Do you do over-night charging/ charge for very long durations/ play lots of games during charging? In that case your battery is over-charged. Check it. It should be puffed up a bit. If this is the case then, sorry mate, but you'll just have to get a new battery. And don't ignore this problem. Trust me, as bad as it is, it's all downhill from here.
Pauloxzak said:
I tried that, the friend's battery on my phone had the same behaviour, and my battery on friend's phone worked fine... so it can't be the battery
Why the hell it won't just work normal if I flashed stock back?
Tried recharging for long time, no luck, also tried many "battery calibration" apps also with no result.
I'm guessing buying a new battery won't solve anything either given the results with the friend's battery
Click to expand...
Click to collapse
JUst unroot the phone and send it to service centre !
All will be done ! and your warranty will be there if u have it still
Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
No reply... :/
Some one should have had an issue.
vivek90 said:
Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
Click to expand...
Click to collapse
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
BWolf56 said:
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
Click to expand...
Click to collapse
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
vivek90 said:
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
Click to expand...
Click to collapse
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down.
.........
BWolf56 said:
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
laughingT said:
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down..........
Click to expand...
Click to collapse
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
vivek90 said:
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
Click to expand...
Click to collapse
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
BWolf56 said:
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
Click to expand...
Click to collapse
May be yes, the phone some times just goes blank, i have to manually switch ON. The same battery works well in my frnds phone quite well.
Port dont know, i can copy files no errors even now when i plug it in on stock gingerbread the battery doesnt charge but can copy files as before.
Since the batt works well in other phone, a couple of ideas. Perhaps silly to ask, but just checking:
did you wipe battery stats in cwm after flashing?
did you clean the phone's battery terminals with a bit of alcohol?
what's the battery health,temperature and voltage history look like, if you can get it. you can log it with battery monitor widget or similar app. set to short 1 minute interval for testing.
.........
Im a sucker for AOSP Android Its smooth and simple just the way i like things. The only thing that keeps me going back to a Sense ROM (namely Nik Project X Rebirth and ARHD), is a slight battery issues. To put it simply, it either takes an extremely and painfully slow time to charge my phone from even 60% - 100% (about 6 or 7 hours which, if Im not wrong, should be the normal full charge of an HTC Incredible S stock??). After a week or two, the battery just screws up entirely. It takes EVEN longer than 5 hours to charge up like 20% of battery. Furthermore, it stops charging at 60% as if the battery was full!! I know this is not an issue with my battery because as soon as I flash any other ROM (thats not CM10.1 related) the battery starts charging up again. Dirty flashing CM10.1 nor clean install of CM10.1 seems to work for me
Does anyone know what the problem is and a possible fix?
I understand that I probably should be placing this thread in CM10.1 threads. I have posted in CM10.1 by dla5244 thread as well as the Lacoste thread. Yet no one has even RESPONDED to this issue.
072665995 said:
Im a sucker for AOSP Android Its smooth and simple just the way i like things. The only thing that keeps me going back to a Sense ROM (namely Nik Project X Rebirth and ARHD), is a slight battery issues. To put it simply, it either takes an extremely and painfully slow time to charge my phone from even 60% - 100% (about 6 or 7 hours which, if Im not wrong, should be the normal full charge of an HTC Incredible S stock??). After a week or two, the battery just screws up entirely. It takes EVEN longer than 5 hours to charge up like 20% of battery. Furthermore, it stops charging at 60% as if the battery was full!! I know this is not an issue with my battery because as soon as I flash any other ROM (thats not CM10.1 related) the battery starts charging up again. Dirty flashing CM10.1 nor clean install of CM10.1 seems to work for me
Does anyone know what the problem is and a possible fix?
I understand that I probably should be placing this thread in CM10.1 threads. I have posted in CM10.1 by dla5244 thread as well as the Lacoste thread. Yet no one has even RESPONDED to this issue.
Click to expand...
Click to collapse
May be Guidelines for Better Battery Life will help you
072665995 said:
Im a sucker for AOSP Android Its smooth and simple just the way i like things. The only thing that keeps me going back to a Sense ROM (namely Nik Project X Rebirth and ARHD), is a slight battery issues. To put it simply, it either takes an extremely and painfully slow time to charge my phone from even 60% - 100% (about 6 or 7 hours which, if Im not wrong, should be the normal full charge of an HTC Incredible S stock??). After a week or two, the battery just screws up entirely. It takes EVEN longer than 5 hours to charge up like 20% of battery. Furthermore, it stops charging at 60% as if the battery was full!! I know this is not an issue with my battery because as soon as I flash any other ROM (thats not CM10.1 related) the battery starts charging up again. Dirty flashing CM10.1 nor clean install of CM10.1 seems to work for me
Does anyone know what the problem is and a possible fix?
I understand that I probably should be placing this thread in CM10.1 threads. I have posted in CM10.1 by dla5244 thread as well as the Lacoste thread. Yet no one has even RESPONDED to this issue.
Click to expand...
Click to collapse
I am facing a similar issue, though not exactly. which you have mentioned, but recently my phone's battery does not charge beyond 60%; if the restart my phone, the battery charging status jumps to 80-85% and stays there..
srv.abhishek said:
I am facing a similar issue, though not exactly. which you have mentioned, but recently my phone's battery does not charge beyond 60%; if the restart my phone, the battery charging status jumps to 80-85% and stays there..
Click to expand...
Click to collapse
WTF m facing exactly same issue... itried every thing bt that dosent works...Changed rom, changed Kernel, changed Radio, twice revert to stock with locked bootloader... all waste ... I was thinkin take phone to HTC Care centre... m ****ed up... :crying:
Sandeep_Jagtap said:
May be Guidelines for Better Battery Life will help you
Click to expand...
Click to collapse
Thanks for your input but does not really help because my issue lies where my phone refuses to charge, not where my phone runs out of battery.
srv.abhishek said:
I am facing a similar issue, though not exactly. which you have mentioned, but recently my phone's battery does not charge beyond 60%; if the restart my phone, the battery charging status jumps to 80-85% and stays there..
Click to expand...
Click to collapse
I tried that. Just stays at 60% :/ it really sucks and I hope someone will find the source of this problem and provide a possible fix.
072665995 said:
Thanks for your input but does not really help because my issue lies where my phone refuses to charge, not where my phone runs out of battery.
I tried that. Just stays at 60% :/ it really sucks and I hope someone will find the source of this problem and provide a possible fix.
Click to expand...
Click to collapse
Try szeszo cm9 test tomorrow from his Google plus. It could be cm10 and incompatibility with our phone. So try cm9
Sent from my GT-I9300 using XDA Premium HD app
naathaanb96 said:
Try szeszo cm9 test tomorrow from his Google plus. It could be cm10 and incompatibility with our phone. So try cm9
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
Is there a link for the test? It would be great if you can post it here...
072665995 said:
Thanks for your input but does not really help because my issue lies where my phone refuses to charge, not where my phone runs out of battery.
I tried that. Just stays at 60% :/ it really sucks and I hope someone will find the source of this problem and provide a possible fix.
Click to expand...
Click to collapse
I had checked with HTC customer care.. they had asked me to discharge the battery completely, remove it for about 30 s and then charge using USB..
I performed the above steps but instead of switching on the phone, I kept it switched off while it was being charged..
What I noticed was the battery charging status jumped from 0 - 67% in 1 hour and then to 82% in next 1.5 hours.. post then it stayed there..
From what I deduce, it does not appear to be a software problem.. I am primarily facing with lots of ROM, AOKP, CM10.1, MIUI, Stock - Sabsa, Viper
Try this method
(do when you are not using mobile for long time at night)
Method 1(Normal User)
Get --Battery Calibration---from Market (Damo software)
--Keep Incs on charger
--Now open Battery Calibration--
--Chose remove battery_stats.bin---
--Now PowerOff Immidietely
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS -new battery_stats.bin will be created-You will see 100% charged Battery
Alernative Method (Advance user)
(Note:Keep desired Rom on Your SD card to flash)
--Keep Incs on charger
--Go into recovery
--Wipe all Partition except SD CARD
--Wipe Battery Stats
--Now PowerOff Immidietely By removing battery
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS Bootloader into recovery
--flash the ROM which you already saved on your sd-Card
--Reboot
--You will see 100% charged Battery
Note: Keep your charger ON in Entire Process
srv.abhishek said:
Is there a link for the test? It would be great if you can post it here...
Click to expand...
Click to collapse
U need to add him on google+ and he adds u back. Then ull find his test builds and stuff. szezso's google plus
Sandeep_Jagtap said:
Try this method
(do when you are not using mobile for long time at night)
Method 1(Normal User)
Get --Battery Calibration---from Market (Damo software)
--Keep Incs on charger
--Now open Battery Calibration--
--Chose remove battery_stats.bin---
--Now PowerOff Immidietely
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS -new battery_stats.bin will be created-You will see 100% charged Battery
Alernative Method (Advance user)
(Note:Keep desired Rom on Your SD card to flash)
--Keep Incs on charger
--Go into recovery
--Wipe all Partition except SD CARD
--Wipe Battery Stats
--Now PowerOff Immidietely By removing battery
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS Bootloader into recovery
--flash the ROM which you already saved on your sd-Card
--Reboot
--You will see 100% charged Battery
Note: Keep your charger ON in Entire Process
Click to expand...
Click to collapse
Alright Ill flash a CM10.1 ROM. When it reaches 60% and can no longer charge, ill msg u back to see if it worked (cuz it normally dont happen until like 2 or so weeks after) Thanks for the input
Sandeep_Jagtap said:
Try this method
(do when you are not using mobile for long time at night)
Method 1(Normal User)
Get --Battery Calibration---from Market (Damo software)
--Keep Incs on charger
--Now open Battery Calibration--
--Chose remove battery_stats.bin---
--Now PowerOff Immidietely
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS -new battery_stats.bin will be created-You will see 100% charged Battery
Alernative Method (Advance user)
(Note:Keep desired Rom on Your SD card to flash)
--Keep Incs on charger
--Go into recovery
--Wipe all Partition except SD CARD
--Wipe Battery Stats
--Now PowerOff Immidietely By removing battery
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS Bootloader into recovery
--flash the ROM which you already saved on your sd-Card
--Reboot
--You will see 100% charged Battery
Note: Keep your charger ON in Entire Process
Click to expand...
Click to collapse
tried charging over-nite but no luck.. charging status same as mentioned above
srv.abhishek said:
tried charging over-nite but no luck.. charging status same as mentioned above
Click to expand...
Click to collapse
ohh. Hope it get fix.
I could tell you this far only
hi.
i get only 3 hours of SOT max and the real problem is that when the battery goes down to 15% it all of a sudden gives me prompt that battery is low and then in next 3 seconds it says battery is 1% and then mobile turns off and it does not even turn on again!!!
i even try to on it but it does not that means all the charge is just gone away...
can anyone help me whats wrong? i have Dr. Ketan rom L3
here i have the screenshots now.
here are 2 images i took of the problem im talking about:
http://imgur.com/c8pna2v,I3qJfy5
in first u can see its 11% and in few seconds its 5% and then phone gone dead and will not even power on
here is same charge cycle i charged phone for like 15 min and then i see SOT here u can see its only 3 hours which is pretty low for Note 4 with very light use.
http://imgur.com/v6Wv47g,QMleogS
and here following images show the battery drainage just sitting the phone, no messages, no calls, not even time checked, i didnt even touch the phone from 6:45am to 1:30pm and drainage is 6%
http://imgur.com/koYDgL4,QAxyvSA
aami.aami said:
hi.
i get only 3 hours of SOT max and the real problem is that when the battery goes down to 15% it all of a sudden gives me prompt that battery is low and then in next 3 seconds it says battery is 1% and then mobile turns off and it does not even turn on again!!!
i even try to on it but it does not that means all the charge is just gone away...
can anyone help me whats wrong? i have Dr. Ketan rom L3
here i have the screenshots now.
here are 2 images i took of the problem im talking about:
http://imgur.com/c8pna2v,I3qJfy5
in first u can see its 11% and in few seconds its 5% and then phone gone dead and will not even power on
here is same charge cycle i charged phone for like 15 min and then i see SOT here u can see its only 3 hours which is pretty low for Note 4 with very light use.
http://imgur.com/v6Wv47g,QMleogS
and here following images show the battery drainage just sitting the phone, no messages, no calls, not even time checked, i didnt even touch the phone from 6:45am to 1:30pm and drainage is 6%
http://imgur.com/koYDgL4,QAxyvSA
Click to expand...
Click to collapse
Just flash the stock firmware and kernel, and see if it solves the problem. If not then you have a dead battery on your hands.
I also have the same problem, it also seems to happen at 30 percent. I'm pretty sure we need to change our battery
Sent from my SM-N910F using Tapatalk
Toss3 said:
Just flash the stock firmware and kernel, and see if it solves the problem. If not then you have a dead battery on your hands.
Click to expand...
Click to collapse
u mean to say that i should go stock samsung firmware and remove this rom?
aami.aami said:
u mean to say that i should go stock samsung firmware and remove this rom?
Click to expand...
Click to collapse
Well its the easiest way to see if it is rom/kernel related or if something is wrong with the hardware.
Toss3 said:
Well its the easiest way to see if it is rom/kernel related or if something is wrong with the hardware.
Click to expand...
Click to collapse
ok thank you. just one more question just to be safe, should i just download the firmware from sammobile and flash via odin in download mode right?
and another fellow here advised me to calibrate my battery to check if its hardware or software. he told me to charge to 100% and delete this file data/ system / and delete BatteryStats.bin use to 0% and then charge 100%. should i do it before going stock or not?
had the same issue a few days back (f2 stock rom and kernel), battery dropped from 17% to 0 within a few seconds.
but this occured only once, the next cycle was ok, so i guess it was a calibration issue!
aami.aami said:
ok thank you. just one more question just to be safe, should i just download the firmware from sammobile and flash via odin in download mode right?
and another fellow here advised me to calibrate my battery to check if its hardware or software. he told me to charge to 100% and delete this file data/ system / and delete BatteryStats.bin use to 0% and then charge 100%. should i do it before going stock or not?
Click to expand...
Click to collapse
Easiest to try battery calibration first. If that doesn't work after a couple of cycles then just flash the stock rom from Sammobile using Odin.
TML1504 said:
had the same issue a few days back (f2 stock rom and kernel), battery dropped from 17% to 0 within a few seconds.
but this occured only once, the next cycle was ok, so i guess it was a calibration issue!
Click to expand...
Click to collapse
Toss3 said:
Easiest to try battery calibration first. If that doesn't work after a couple of cycles then just flash the stock rom from Sammobile using Odin.
Click to expand...
Click to collapse
ok thank you guys, i guess i just have a ****ty life and very very ****ty luck happens to every phone tablet i buy. FML
There are 3 possible reasons this happens - broken phone, broken battery or software problem.
I think the first one is unlikely so you need to figure out which of the last 2 is.
Make a back up of your current rom and install an official TW software. If this still doesnt fix your problem, its most likely the battery. A new genuine battery is around 20$.
PS - i think that the battery stats bin file is automatically deleted once you fully charge the battery anyway but you can still try it altough i doubt it will fix it.
Sent from my SM-N910F using XDA Free mobile app
same problem here
And here.
This is typical of a dead battery. Your best bet is to buy a new one.
Less than a year is short but not unheard of. Overheating (especially when 100% full), deep discharge, very intensive use (especially with quick charging) and manufacturing defects all can kill a battery.
I'm on CM12.1 with this problem. I've tried battery calibration and tried a new battery but its still apparent.
Will be trying a factory reset as my last resort.
This is happening to 2 phones in my household it started after the upgrade to 5.0.1 one note is Tmobile the other sprint....highly doubt we both developed battery problems RIGHT after we both ota upgraded.
Same here at ~13%.
I do always either fast charge or QI charge.
So far I've tried:
- Battery calibration
- Bought new battery
- Factory reset
Still happens!!
Maybe I'll try TW flash or modem change
Weird, I have this exact same problem as the original post. I'm running BOC5 on the 9105. It's a sporadic problem only occurring on occasion
Sent from my SM-N910F using XDA Free mobile app
KK > LP
VuBoo said:
KK > LP
Click to expand...
Click to collapse
I've been running Lollipop for ages until this problem happened. Frankly, I still prefer Lollipop with this problem.
Hey guys
I already posted my problem in the thread related to LineageOS, but since the issue couldn't be solved I want to try it this way.
So what is my problem?
While using my phone it gets very hot. According to Powerful Monitor the CPU gets up to 65 °C and battery up to 35 °C, while under load. Besides this my battery goes down rapidly. So watching 10 minutes of YouTube sucks up 8-9 % battery. Just a plain normal video.
What is my setup?
I9295, running LineageOS 14.1-2017-06-06-UNOFFICIAL-jactivelte, OpenGApps 06-07-17 nano, only apps installed manually are GeekBench, Powerful Monitor and YouTube. Baseband is I9295XXUDOB4 (German unbranded DBT). I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
What have I already tried?
- flashed stock firmware (all available for Germany that are unbranded). With and without erasing NAND, with different Odin versions. Last time I flashed I used Odin 3.07
- different batteries: the old ones the phone came with (bought it used), the new one I bought separately, a new one from PowerCell with higher capacity (2900 mAh)
- different phones. I have a second I9295 from a friend, that worked definitely without any issues. Same problem.
- different custom ROMs: now I'm running LineageOS, but I also tried CM13 (20161228), CM12.1, MIUI and Super WizCyan (everything from xda)
Is it possible break something ciritcal when disassembling the phone? Both phones came with broken covers for the USB port, so I opened it, but only removed the screws and the mid-frame (?) and replaced the cover. Nothing was damaged, at least I was very carefully and didn't see anything that looked suspicious.
Another very strange thing I noticed:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
I really have no idea what else to do.
Any help is appreciated.
dotnano said:
Hey guys
While using my phone it gets very hot.
I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
Any help is appreciated.
Click to expand...
Click to collapse
Hey there. Well, there are tons of possible reasons why your phone acts like that. My modest opinion is that you have some sort of wakelock active in background. Install both Wakelock Detector and Gsam Battery Monitor, grant all the permissions and let it obtain data for some minutes. Than look at the results, and check if there's any Wakelock active. If instead Gsam shows an excessive consume by the kernel, try in terminal the following commands:
Code:
su
setenforce 1
setenforce 0
Then see if there's still the drain (you have to wait some minutes).
If it still doesn't work, I'd advice you to update to the latest stock firmware (doesn't matter which Country, just select a non-branded one), reinstall LOS again and verify if with nothing installed you still get the battery drain.
Anyway, IMHO it's not an hardware related problem, even messing up with the components this shouldn't happen. The only hardware fault could be the battery short-life, but 1st you said you just replaced it, 2nd it would not justify the thermal overload. Let us know
Thank you very much for your answer. I'm quite short on time next days but maybe I have a few minutes on sunday.
On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now. Maybe sunday.
But still thank you
Finally I found some time to try your suggestions
I skipped the part of trying it on the old setup, so I flashed everything new with latest stock(UDOB4-DBT, not the last one but still Android 5.0.1), then TWRP 3.1.0, after that LOS 14.1-20170606 and OpenGApps 7.1 nano from 17-06-06. Only apps I installed beside that are GSam Battery and Wakelock Detector. Root activated and granted where asked and needed.
Here I uploaded the pictures I took from GSam Battery.
So what seems strange to me:
- why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?
dotnano said:
- Why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?
Click to expand...
Click to collapse
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.
IvanCristina said:
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.
Click to expand...
Click to collapse
No need to apologise, you're doing this in your free time...
Besides that, I wasn't at home all week, so I couldn't try anything even if you had answered.
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?
dotnano said:
Thank you very much for your answer. On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now.
Click to expand...
Click to collapse
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
dotnano said:
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?
Click to expand...
Click to collapse
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About:
dotnano said:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
Click to expand...
Click to collapse
Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.
IvanCristina said:
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About: Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.
Click to expand...
Click to collapse
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.
Youre are not alone. My Phone was/is also getting hot.
Then I did a full wipe ( format also internal memory partition!)
I'm current running cm13 (CM13 (20161228)). Batterie works now / normal ok / 1 / 2 Day s ( no great usage ). But when i telephone with someone it's getting hot in 15 min. Modem Version is I2995XXUDPB3.
dotnano said:
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.
Click to expand...
Click to collapse
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)
JASONRR said:
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)
Click to expand...
Click to collapse
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.
dotnano said:
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.
Click to expand...
Click to collapse
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.
JASONRR said:
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.
Click to expand...
Click to collapse
I tried 3.10, 3.12 and 3.07 so far. Not successfully. Tried 3.09 now, we'll see.
I have a Sony Xperia Z1C as comparison, YouTube needs maybe 1% for 5 Minutes.
Cables/Chargers shouldn't be the problem. I have the original Samsung, also cable. Charged to 0 to 75 % in 90 Minutes. Same with cable and charger from Anker. So should be fine?
So no new ideas?
dotnano said:
So no new ideas?
Click to expand...
Click to collapse
I have no idea too but i have the same Trouble with mine BUT I'm still using the original Rom and didn't flash it. So maybe it is an Hardware issue.
My Battery is getting old, yes, but it is the third one. The Phone gets hotter than in its first years.
I hope you'll find a reason!
My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.
Vardion said:
My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.
Click to expand...
Click to collapse
Nah, why should it? There are a lot of i9295 users that don't have any problems.