Database Develop

[Think Tank] Modify Kernel to fix charging

I haven't actually looked at the battery driver or even the kernel for that matter, but does it specifically state the cutoff voltages for charging the battery? If it does, we should compare those to what the phone is charging the battery to when the phone is off and make them match. Hell if you want to live on the wild side bump it up another .05 - .075V or so...

Just a question.....but do you know what you are talking about??
Froyo seemed to solve the charging 'problem' for me, then again I never had a charging problem.

Qazme said:
Just a question.....but do you know what you are talking about??
Froyo seemed to solve the charging 'problem' for me, then again I never had a charging problem.
Click to expand...
Click to collapse
Erm, how did it fix it? We still have that problem.

I believe what he is talking about is modifying the kernel to allow the battery to fully charge when powered on rather than leaving the "buffer" which requires the bump charge to get the extra 10% or so out of the battery. I'd definitely like to see this as well, but I've found performing the recalibration did help a bit.

Disclaimer: I'm a noob and don't know ****!
However, it would seem if htc (or google), put code in the kernel to prevent the phone from charging to 100% while turned on, I'm sure they had good reason. My guess would be to keep the phone from over heating.
It would seem that if the phone is on and draining the battery, but at the same time you're trying to charge the battery, achieving that last few percent might be difficult and could take considerable more time, and thus getting hotter.
Just a guess though.
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)

I'll look at the battery driver when I get home (currently at work), but I have seen devices where charging limits were invoked directly in the kernel. These could be modified if they are.
On the issue of heat, manufacturers play it VERY safe. It looks bad if someone is charging their phone in their car during the summer and the battery cooks off in the passenger seat. I'd be fairly comfortable pushing the battery to a little bit higher voltage than it is right now.

What about the charging SPEED? Myself and several others have noticed that Froyo ROMs charge at a much slower rate, plugged in to ac power, compared to 2.1 Rom. For me, it takes about twice as long to charge. Is this something that could also be addressed with a kernel fix? I literally went from being able to charge from ~10% to full in about 90 mins, to now taking about 4 hours on Froyo.

bast525 said:
What about the charging SPEED? Myself and several others have noticed that Froyo ROMs charge at a much slower rate, plugged in to ac power, compared to 2.1 Rom. For me, it takes about twice as long to charge. Is this something that could also be addressed with a kernel fix? I literally went from being able to charge from ~10% to full in about 90 mins, to now taking about 4 hours on Froyo.
Click to expand...
Click to collapse
The 2.15 radio probably broke the phone's ability to differentiate between the wall-charger (fast) and normal USB (slow). The reason I say "radio" and not "kernel" is because it charges slowly when powered off as well. Hopefully the radio included in the upcoming OTA will fix this.

I had the slow charging problem on the 2.05 radio as well but doesn't change much about what's being said about a potential fix.
Anyone able to confirm that this (something in the radio) is the reason?
Hope the OTA comes soon so I can get back to recharging in a timely fashion.
Sent from my Dinc using XDA App

Qazme said:
Just a question.....but do you know what you are talking about??
Froyo seemed to solve the charging 'problem' for me, then again I never had a charging problem.
Click to expand...
Click to collapse
Apparently you are one of the users that were lucky enough not to have this issue. This thread is not for you. Move on. And btw, Froyo did not fix this problem. Again, nothing for you to see here, move on.
For the rest of us who are interested in solving this issue we will continue to put ideas out there in the hope that a smart one figures this out. Until then, we will keep reading about how fortunate some people are and how some other unfortunate people are willing to work on this. Thanks OP.

the difference between bump charging and not never really affected me because the phone charged so damn fast, that just plugging it in for a few minutes helped out a ton. but now with froyo, it literally take 5 to 6 times longer to charge to 100%. its ridiculous

i got sick of letting my phone charge overnight then 10 min after i unplug it in the morning its down to 92%. and unless you charge it while the phone is off it rapidly drops all the way down to like 80% before it starts decreasing normally, at least for me. so i started turning it off and topping it off in the mornings for about 30-45 min before i would leave for work, doing this i noticed a HUGE difference in my battery life through out the day. that got to be a pain because sometimes i just don't have time to do that in the mornings, so i ended up buying an external charger and an extra battery. this way charge the extra battery overnight on the external charger, pop the fresh battery in the phone in the morning and i'm ready to go. but all this could be avoided if the phone would charge the battery as good as the $2 wall charger, so if you could find a fix for this battery problem it would be awesome.

I had slow charging with 2.05 and 2.15 radios, unfortunately...

Did any of you that are having this issue root and install froyo immediately after buying the phone? a friend of mine is having a similar issue. Have you tried battery recalibration? Also I would recommend checking your up time and awake times in battery info and see if there's something keeping your phone awake while charging . One last thing, try installing battery save mode toggle from market.
Sent from my ADR6300 using Tapatalk

I've been messing with the slow charge issue all night tonight, and as far as I can tell, it is not the 2.xx radio, and it must be the .32 kernel.
Slow charging started for me when I installed the first 2.2 leak which had the 2.05 radio, and remained on the the 2nd 2.2 leak and 2.15 radio. Before that I had the 2.05 radio on 2.1 and charging was normal, tonight I rolled back to complete stock 2.1/1.0 radio and charging was normal again, I kept the 1.0 radio and installed a 2.2 rom, charging slowed again, changed to 2.15 radio, still slow, so I installed the old CM6 test 8 rom which was used the old kernel with the broken camera, and sure enough, charging was fast again.
I'd really love to figure this out, if any of you get on IRC and want to discuss this, /msg digi

earthtodigi said:
I've been messing with the slow charge issue all night tonight, and as far as I can tell, it is not the 2.xx radio, and it must be the .32 kernel.
Slow charging started for me when I installed the first 2.2 leak which had the 2.05 radio, and remained on the the 2nd 2.2 leak and 2.15 radio. Before that I had the 2.05 radio on 2.1 and charging was normal, tonight I rolled back to complete stock 2.1/1.0 radio and charging was normal again, I kept the 1.0 radio and installed a 2.2 rom, charging slowed again, changed to 2.15 radio, still slow, so I installed the old CM6 test 8 rom which was used the old kernel with the broken camera, and sure enough, charging was fast again.
I'd really love to figure this out, if any of you get on IRC and want to discuss this, /msg digi
Click to expand...
Click to collapse
Great work. on testing at least...
Is there anyone out there who can help fix this? I hate these slow charge times.

I thought the issue was that the phone starts running off battery one its at 100%, not that it can't charge the last 10%...am I misunderstanding that?
I've tested this by taking it off the charger as soon as the light turns green...seems I get much better battery life this way.

This doesn't quite explain why some of us have had no problems at all either. Maybe an issue with newer devices but personally my device has been up for over 31 hours since charge and haven't noticed this issue but a friend of mine has complained of it, and he recently bought his device. Tomorrow after I charge my device I'll post with findings after charging.
Sent from my ADR6300 using Tapatalk

trunksta said:
This doesn't quite explain why some of us have had no problems at all either. Maybe an issue with newer devices but personally my device has been up for over 31 hours since charge and haven't noticed this issue but a friend of mine has complained of it, and he recently bought his device. Tomorrow after I charge my device I'll post with findings after charging.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
this has to do with 2.2 and new kernels. not stock 2.1.

trunksta said:
This doesn't quite explain why some of us have had no problems at all either. Maybe an issue with newer devices but personally my device has been up for over 31 hours since charge and haven't noticed this issue but a friend of mine has complained of it, and he recently bought his device. Tomorrow after I charge my device I'll post with findings after charging.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I pre-ordered my phone and I have the charging issue as well so it can't be new phones vs old phones. I hope it gets figured out soon.

[SOLVED]Unable to calibrate battery on 2.2.1 based ROMs

I am facing a rather "cruel" issue with my phone of late.
I am unable to calibrate my battery ever since I installed 2.2.1 based ROM. It goes upto 98% properly, and then within a minute or two shows me the "charged" message. When I pull the charger plug out, it immediately falls back to 98%.
I tried charging fully with phone on, then off, wiping battery stats using both sgs tools and CWM console more than half a dozen times till now, but am still facing this issue.
I even tried changing the battery, but even then am facing the issue. Also tried the total discharge and total charge method.
Could anyone help me please.
Note: I tried like 2 different 2.2.1 based ROMs.

in another thread someone mentioned it being a bug with all 2.2.1 roms. I'm dealing with it too. Best thing to do is use a battery theme that doesn't show the percentage that way its not bugging you. 1-2% means nothing.
Sent from my SGH-I897 using XDA App

ninjuh said:
in another thread someone mentioned it being a bug with all 2.2.1 roms. I'm dealing with it too. Best thing to do is use a battery theme that doesn't show the percentage that way its not bugging you. 1-2% means nothing.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Oh. Thank you ninjuh. So I think I would go back to 2.2 based ROM and wait till 2.2.1 is fully fixed.

Known issue 2.2.1. i would expect a fix eventually
Sent from me

I got this app called "Battery Booster" from market y'day. I started it, and put the screen "never off" and then had it on charge. It took like a good 20-30 mins to come from 98 to 99 to 100. And then it came to "charged". It stayed at 100% after I pulled the cable off.
But then, it was back to normal 98% behavior when the turned the app off.
One thing I could notice was that, once the charge hit 98%, and the turned off the screen, the "charged" message comes in under a minute. But with screen on, it took more than 20 mins.

Thread can be closed.
Looks this is a known non-issue in 2.2.1 and some latest kernels to help avoid battery overcharging.

diablo009 said:
Thread can be closed.
Looks this is a known non-issue in 2.2.1 and some latest kernels to help avoid battery overcharging.
Click to expand...
Click to collapse
Just edit your title to [SOLVED] Unable to calibrate battery on 2.2.1 based ROMs

Thank you sir.

[Q] My captivate turns off randomly subsequent to installing MIUI 4 roms?

If I leave my phone charging over night, I wake up in the morning finding it off. Which is bad because my phone is my alarm, ha. This only started happening after I flashed WEUI and then ASNET MIUI. Any ideas on how I can fix this? I'm running MIUI ASNET 1.4.4 with the latest glitch kernel.
Sent from my SGH-I897 using XDA

Captivate random shut downs
xArtanis said:
If I leave my phone charging over night, I wake up in the morning finding it off. Which is bad because my phone is my alarm, ha. This only started happening after I flashed WEUI and then ASNET MIUI. Any ideas on how I can fix this? I'm running MIUI ASNET 1.4.4 with the latest glitch kernel.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
Lots of people have this issue, seems to be a hardware related under certain conditions, like when the battery is fully charged, wifi on.
Google "Captivate random shut downs" and you will find a lot of info.
I have a Captivate running Android 4.0.2 (ICS).
I will continue searching and just asked "Captivate Keep Alive" app developer (see "Play Store") if it is compatible with ICS.

If you're on Glitch, try bumping up the voltage of the lowest frequencies by +25 mV.

jprada said:
Lots of people have this issue, seems to be a hardware related under certain conditions, like when the battery is fully charged, wifi on.
Google "Captivate random shut downs" and you will find a lot of info.
I have a Captivate running Android 4.0.2 (ICS).
I will continue searching and just asked "Captivate Keep Alive" app developer (see "Play Store") if it is compatible with ICS.
Click to expand...
Click to collapse
korockinout13 said:
If you're on Glitch, try bumping up the voltage of the lowest frequencies by +25 mV.
Click to expand...
Click to collapse
Thanks for the support. It's been about a month and I've learned to live with it. I've tried Captivate Keep Alive for a few weeks and it hasn't been much help. My main concern is having my Captivate survive the night. Nowadays, it'd turn off and the battery would discharge despite being plugged in.
As for Glitch kernel, I'm using Semaphore at the moment but I'll try that out. Thanks.

In case you are still looking. I think I'm in the same boat as you. Captivate Keep Alive worked fine for GB, but all ICS roms (and kernels) introduced the shutdown during charging. The fix is this app : Wake Lock. It does the same thing KA but it doesn't turn off when the phone is charging. Problem with Wake Lock is that you gotta control it manually.
So hopefully in the future they'll be a KA version with that option.

cfmarque said:
In case you are still looking. I think I'm in the same boat as you. Captivate Keep Alive worked fine for GB, but all ICS roms (and kernels) introduced the shutdown during charging. The fix is this app : Wake Lock. It does the same thing KA but it doesn't turn off when the phone is charging. Problem with Wake Lock is that you gotta control it manually.
So hopefully in the future they'll be a KA version with that option.
Click to expand...
Click to collapse
Thanks so much for the response. Maybe I can finally use my phone as an alarm again, ha. Which option do I choose in Wake Alarm? I'm going with CPU on, screen off, keyboard off at the moment.
Sent from my SGH-I897 using XDA

Yes, those are the same values I use.

same issues,i've try many room, kernel, i9000 bootloader, configs, etc... no good luck ATM. Gonna try using different modems...
Regards

See if rooted stock GB works.

bravomail said:
See if rooted stock GB works.
Click to expand...
Click to collapse
Also shutdowns over 80% battery.
I'm with ICS now with "captivate keep alive" app turn on at any time I go into idle state and my phone dont shutdown.

rophiroth said:
Also shutdowns over 80% battery.
I'm with ICS now with "captivate keep alive" app turn on at any time I go into idle state and my phone dont shutdown.
Click to expand...
Click to collapse
I was using "Captivate Keep Alive" some on GB Roms, but was appearing incompatible with ICS, as the app, though still present, would turn off before it was supposed to.
---------- Post added at 07:50 PM ---------- Previous post was at 07:29 PM ----------
korockinout13 said:
If you're on Glitch, try bumping up the voltage of the lowest frequencies by +25 mV.
Click to expand...
Click to collapse
I had raised my min CPU to 200 for shut downs.
Saw this post, I've never changed any of my voltage settings, never OC's, etc. I'm presuming in NS Tools, presuming from the "volt" tab, but am unsure of what to change to bump up min frequency.
Thanks

M973 said:
I was using "Captivate Keep Alive" some on GB Roms, but was appearing incompatible with ICS, as the app, though still present, would turn off before it was supposed to.
---------- Post added at 07:50 PM ---------- Previous post was at 07:29 PM ----------
I had raised my min CPU to 200 for shut downs.
Saw this post, I've never changed any of my voltage settings, never OC's, etc. I'm presuming in NS Tools, presuming from the "volt" tab, but am unsure of what to change to bump up min frequency.
Thanks
Click to expand...
Click to collapse
I even put min CPU to 1000 and nothing happens XD but Im using keep alive to 0% and no more shutdows (also use less battery than i though ), but having some bugs... after a while my phone dont receive more calls and cant make xD but i think that is some problem with modem)

Battery virtually dropping, hardware or software problem?

Hello,
for months it has been happening that when the battery usually reaches 25% (but not always sometimes even 40ish) the battery indicator drops to 19% and it could either remain stuck at that value until the charge actually drops below 19% and continue the usual drop or it will rapidly drop to lower values in big steps like (19->10->4) in minutes to finally actually automatically power off. The strange thing is that it's all fake! When I power the phone again the % will go back to where it should be before this virtual drop happened and continue its usual drop, it always worked until today when for the first time it continued the "game" non-stop until the battery ended the actual charge (for hours)! You have to consider that i was in a place in the mountains where the gsm coverage was very low/non existent so it could be connected. But it got me worried because it couldn't control it!
Apart from a solution I'm asking also what the reason could be. It could seem like a battery problem but why would the phone actually recognize the actual charge after it powers off and I restart it ? Seems like a software problem (battery driver maybe?). But I wouldn't exclude that it could be the battery maybe when the charge gets low the voltage drops dramatically under stress to a point where the phone thinks its almost empty.
I'm using cm7.2 kang 119 with standard kernel.

Have you tried wiping the battery stats..?
Sent from my Optimus 2X using xda premium

-sandro- said:
Hello,
for months it has been happening that when the battery usually reaches 25% (but not always sometimes even 40ish) the battery indicator drops to 19% and it could either remain stuck at that value until the charge actually drops below 19% and continue the usual drop or it will rapidly drop to lower values in big steps like (19->10->4) in minutes to finally actually automatically power off. The strange thing is that it's all fake! When I power the phone again the % will go back to where it should be before this virtual drop happened and continue its usual drop, it always worked until today when for the first time it continued the "game" non-stop until the battery ended the actual charge (for hours)! You have to consider that i was in a place in the mountains where the gsm coverage was very low/non existent so it could be connected. But it got me worried because it couldn't control it!
Apart from a solution I'm asking also what the reason could be. It could seem like a battery problem but why would the phone actually recognize the actual charge after it powers off and I restart it ? Seems like a software problem (battery driver maybe?). But I wouldn't exclude that it could be the battery maybe when the charge gets low the voltage drops dramatically under stress to a point where the phone thinks its almost empty.
I'm using cm7.2 kang 119 with standard kernel.
Click to expand...
Click to collapse
So you say it's done that for a while... obviously it's not possible to pinpoint an app. I guess then you have some funky cruft buildup (say, a lot of rom flashes and some settings getting squiffy) or your battery's dying. I know for sure that the rather excellent Battery Widget Reborn can give a health check on the battery as part of the widget (although I dunno if it's GB compatible). The second solution may be to try a clean wipe. It's drastic, yes, but can clean up any lingering problems if you've been updating for a long time without the occasional wipe. If you haven't...then I dunno.
xExabyte said:
Have you tried wiping the battery stats..?
Sent from my Optimus 2X using xda premium
Click to expand...
Click to collapse
Baaaaaad advice. That's just a placebo and doesn't do anything. So please don't recommend it.

Dekudan said:
Baaaaaad advice. That's just a placebo and doesn't do anything. So please don't recommend it.
Click to expand...
Click to collapse
What do you mean by this? Don't be rude, just help out if you can.
OP: is it possible you update the rom/kernel?
Sent from O2X via xda premium, beware of autocorrection

The thing is it doesn't happen at every single charge! That's confusing! Maybe I'll try to update to #135 and install symbiosis kernel and see.

coolacrille said:
What do you mean by this? Don't be rude, just help out if you can.
OP: is it possible you update the rom/kernel?
Sent from O2X via xda premium, beware of autocorrection
Click to expand...
Click to collapse
I'm not trying to be rude. It's just that battery stats are reset after every reboot, so wiping them does nothing. It's also easier to be blunt to get a message across.

-sandro- said:
Hello,
for months it has been happening that when the battery usually reaches 25% (but not always sometimes even 40ish) the battery indicator drops to 19% and it could either remain stuck at that value until the charge actually drops below 19% and continue the usual drop or it will rapidly drop to lower values in big steps like (19->10->4) in minutes to finally actually automatically power off. The strange thing is that it's all fake! When I power the phone again the % will go back to where it should be before this virtual drop happened and continue its usual drop, it always worked until today when for the first time it continued the "game" non-stop until the battery ended the actual charge (for hours)! You have to consider that i was in a place in the mountains where the gsm coverage was very low/non existent so it could be connected. But it got me worried because it couldn't control it!
Apart from a solution I'm asking also what the reason could be. It could seem like a battery problem but why would the phone actually recognize the actual charge after it powers off and I restart it ? Seems like a software problem (battery driver maybe?). But I wouldn't exclude that it could be the battery maybe when the charge gets low the voltage drops dramatically under stress to a point where the phone thinks its almost empty.
I'm using cm7.2 kang 119 with standard kernel.
Click to expand...
Click to collapse
dude i have sale some days it drops 2 a 5 times and some times not at all....

reggiexp said:
dude i have sale some days it drops 2 a 5 times and some times not at all....
Click to expand...
Click to collapse
by "sale" you meant "same"?

I have similar problems...
Mine force closes 1 out of 7 charges at a random percentage...today it was at 53%...it shows cc% but in reality the battery is drained out...I am not sure what is the problem...this showed up after I inhaled wiui 2.5.25, other than that I have minor issues with this rom...I really like it...only if I could make the radio work...

sysex said:
I have similar problems...
Mine force closes 1 out of 7 charges at a random percentage...today it was at 53%...it shows cc% but in reality the battery is drained out...I am not sure what is the problem...this showed up after I inhaled wiui 2.5.25, other than that I have minor issues with this rom...I really like it...only if I could make the radio work...
Click to expand...
Click to collapse
What kernel? Bb? Ril? Obviously your problem started when flashing wiui, have an idea what to try.....?
Sent from O2X via xda premium, beware of autocorrection

coolacrille said:
What kernel? Bb? Ril? Obviously your problem started when flashing wiui, have an idea what to try.....?
Sent from O2X via xda premium, beware of autocorrection
Click to expand...
Click to collapse
Bb=725 ril=0218(10b) the kernel is the latest OC kernel from temasek (any suggestions there, is there a better one for wiui/miui roms?).
I'll do a battery wipe after a full charge and see what happens next...

Please don't post questions in the General section
Moving to Q&A

[Q] Cynogenmod Shuts Down after Installation

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.
.........