[Q] Re: i9000 based GB ROM charging bug - Captivate Q&A, Help & Troubleshooting

Quick question on the charging bug seen intermittently on most/all i9000 GB ROMs:
If I primarily just swap to a fully charged battery when one is low versus charging the phone via USB, is this an issue that could be of concern to me?
TIA as I'm itching to migrate to 2.3 and trying to weigh pros/cons of each GB ROM.
i897 running Andromeda 3

Madtowndave said:
Quick question on the charging bug seen intermittently on most/all i9000 GB ROMs:
If I primarily just swap to a fully charged battery when one is low versus charging the phone via USB, is this an issue that could be of concern to me?
TIA as I'm itching to migrate to 2.3 and trying to weigh pros/cons of each GB ROM.
i897 running Andromeda 3
Click to expand...
Click to collapse
The symptoms I am seeing are; charge the battery overnight on wall charger, take off @100%, within minutes it drops to 80%.
I have tried recalibration procedures, switching kernels, switching batteries, wifi on and off, etc but the symptom is still there.
I have yet to see a cause identified.
The initial 20% drain is rapid, the remaining charge disapates slowly so it may not be an issue for you if you don't mind swapping batteries and you have a spare charger.

Lol if you're not charging the battery in the phone how can the charging bug in the phone's software effect you??
Plus that is a very chancy bug anyway. I personally have only experienced it once. Been on gb since it first leaked.

The lowest I've gotten after disconnecting the charger is 90%, which still sucks. Can anyone using atomic fusion reproduce it?

Related

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

battery issue - drains so fast. IDK what's happening..

hello guys my cousin gave me his xperia and well I was happy. But one major problem. It's battery life. May I ask you guys what is the rating of your charger. mine is a charger not made by SE. I thought that if i would buy a new original charger then battery life would improve. I also think that the ROM installed on mine is not energy efficient. IDK . I'm so new to this
charger won't improve battery life, unless its not charging fully, which if it reports 100% it probably is, if its not an official rom then yes, battery can differ a lot
I have installed a couple of custom ROMs, and after a few months battery consumption increases significantly.
Doesn't sound very scientific, but between installing/uninstalling applications, modifying settings, I find I need to start off again with a fresh ROM.
The ROMs I use have Manila/Sense, I have a suspicion that the increased power requirement is a function of something having gone wrong with Manila.
I would try reinstalling the ROM and reinstalling all your applications again (NOT a restore, since you may reintroduce the problem)
maybe you can let me know if I can use a 1A charger for xperia? and where can I buy it. I mean what are the rating of your chargers? thanks
you can use any charger, since the appliance PULLS the current it needs.
Anything from a PC USB cable, to any generic charger, including a car charger.
Yes, some will take a bit longer to reach full charge if the rating is lower (like the USB feed) - but I understand your problem is the DIScharge, not the charge in itself.
Just some feedback from my experience
Agreed totaly:
paul c said:
you can use any charger.
Anything from a PC USB cable, to any generic charger, including a car charger.
Click to expand...
Click to collapse
I am using the original charger in my home, a PC USB cable from an external hard disk at home or at work and the car charger from a Mio Navigator that is left permanently in my car. The time needed to get to 100% differs according to each method used but it does complete. So how u charge is deffinately not an issue. I can also confirm that the device heats differently in each case from relatively cool to hot.
henryfranz2005 said:
I also think that the ROM installed on mine is not energy efficient. IDK . I'm so new to this
Click to expand...
Click to collapse
The issue of draining comes mostly from different roms configuration. Keep in mind that the battery after flashing needs a couple of days to pass and get charged one or two times so as to get to its max capacity. Also keep in mind that if u use for instance the WiFi or play some games or use an app that needs system resources battery will drain as hell regardless of rom. Personally with Valkyrie and Energy roms with a normal phone and messaging use I have managed to keep my X1 on for 3 to 3.5 days max. Other times I have had to plug it 2 times the same day due to heavy use...
BTW Henry we were all new once, no need to appologize.
Mr Black'd said:
Agreed totaly:
I am using the original charger in my home, a PC USB cable from an external hard disk at home or at work and the car charger from a Mio Navigator that is left permanently in my car. The time needed to get to 100% differs according to each method used but it does complete. So how u charge is deffinately not an issue. I can also confirm that the device heats differently in each case from relatively cool to hot.
The issue of draining comes mostly from different roms configuration. Keep in mind that the battery after flashing needs a couple of days to pass and get charged one or two times so as to get to its max capacity. Also keep in mind that if u use for instance the WiFi or play some games or use an app that needs system resources battery will drain as hell regardless of rom. Personally with Valkyrie and Energy roms with a normal phone and messaging use I have managed to keep my X1 on for 3 to 3.5 days max. Other times I have had to plug it 2 times the same day due to heavy use...
BTW Henry we were all new once, no need to appologize.
Click to expand...
Click to collapse
Thank you sir. I think the problem lies in the ROM i installed 826X personally i think it is energy efficient since i just use my phone for texting. (about 400 sms a day) and about 15 mins of wifi thank you.
Can you recommend a ROM which is known for it's efficiency (energy) thanks.
I personally use Energy this period. But keep in mind that rom selection is based on ones personal prefs. All of them are custom made and each cook has his own point of view. I guess that u will have to test a few before u can say with certainty that you like one in specific. Just keep trying...
thank you sir for being so helpful I will personally try the popular roms 3 roms down!

Gingerbread Charging Issues

It seems several people have charging issues with GB. If you have this issue, regardless of rom, post what you have tried to use as a workaround, successfully or not. Also, how long it took for issue to appear. Phone configuration is optional, but there may be something a dev sees as a pattern, even if we dont. I would also encourage posters to share build date of their device.
This thread its for everyone, but I would ask if you are one of the lucky ones not affected by this issue to refrain from posting "I never had a problem...". This thread will hopefully bring more light to this issue for dev's, as currently complaints are posted only in the thread for the specific rom they are using.
To all that post, thank you.
Mods, I posted in wrong forum. Please move to general.Thank you.
reserved for later.
I've seen it, if I charge my phone to long. I'd wake up to a fully charged notification unplug and be at 74% or so.
As a workaround I charge it full right before bed and unplug it at full, since it sips battery just chilling overnight I wake up to about 94% or higher. Plug it in, hop in the shower. Unplug after and I'm good for the day ;p
Ok, since I started the thread, I guess I should post my experience.
If I have just flashed s rom, the first 2 charge cycles work perfectly. After that it goes downhill. 91%, then mid 80's, anyone s guess after that. I've tried multiple combinations of flight mode, data deactivated, and cache/Dalvik wipes. Nothing. The part that confuses me is the first 2 cycles after a flash.
Now, about my phone:
C5.3 (today), Talon 0.1.5, ext4, all tweaks except governor, oc to 1200mhz,-50 uv on all states except 1200, GingerBlue theme (thanks Viv), stock modem, auto rotate/brightness off. I use the cable that came with the phone to charge with (wall charger), and my build date is 1007.
My bug is that it always fully charges to 100%, and just keeps cooking the battery. That cant be good for the batt.
On all Froyo roms / kernels, it would drop to 98% or so like it should.
On Continuum 5.3 / Talon 1.5 it just fully charges..
I use an ammeter but also have a supply that stops blinking when the phone stops charging (long after it shows the battery full notification). Unplugging at that point will show 100%. The problem is that when it reaches full it switches to battery and drains it for several hours so you might see 80% when you unplug it in the morning if it's been running on battery for a while.
The battery gauge and notification are way off. Don't trust them, but I can assure you it's not overcharging.
Battery date 2010.07.09 (as appears on battery)

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

Odd Battery Behavior

I'm currently running latest Pure Nexus ROM and Despair Kernel on my n6. While they have both been working fine, I was wondering if someone could shed some light on why certain things are happening. Yesterday I dirty flashed the despair kernel because only 2 cores were online and the other 2 wouldn't start. After the reflash, my phone was able to barely use any battery. So when I got home and i decided to plug my phone in around 20% battery. I wake up this morning and I unplug my phone thinking i'll have as good battery as I did before I plugged it in. Well, it seems that's not the case. My phone seems to be using more battery than it needs as it's just sitting on my desk not in use.
How come my phone starts to drain battery like crazy after a full charge? Is it because I reflashed the kernel and that fixed things? Is it because I rebooted the device? Do I need to reboot the device daily (after a full charge)? Is anyone else experiencing this?
This behavior has been happening on full stock as well and that's why I rooted and flash a custom rom/kernel because I was hoping this behavior would be gone. I know it's probably too early to tell and I guess my phone is "settling" after the reflash, but how come the day of the reflash it runs fine?
shugga101 said:
I'm currently running latest Pure Nexus ROM and Despair Kernel on my n6. While they have both been working fine, I was wondering if someone could shed some light on why certain things are happening. Yesterday I dirty flashed the despair kernel because only 2 cores were online and the other 2 wouldn't start. After the reflash, my phone was able to barely use any battery. So when I got home and i decided to plug my phone in around 20% battery. I wake up this morning and I unplug my phone thinking i'll have as good battery as I did before I plugged it in. Well, it seems that's not the case. My phone seems to be using more battery than it needs as it's just sitting on my desk not in use.
How come my phone starts to drain battery like crazy after a full charge? Is it because I reflashed the kernel and that fixed things? Is it because I rebooted the device? Do I need to reboot the device daily (after a full charge)? Is anyone else experiencing this?
This behavior has been happening on full stock as well and that's why I rooted and flash a custom rom/kernel because I was hoping this behavior would be gone. I know it's probably too early to tell and I guess my phone is "settling" after the reflash, but how come the day of the reflash it runs fine?
Click to expand...
Click to collapse
signal quality relates heavily to battery drain. if your signal is great quality, youll probably have great battery. but if your signal is bad quality, you can watch your battery basically disappear.
simms22 said:
signal quality relates heavily to battery drain. if your signal is great quality, youll probably have great battery. but if your signal is bad quality, you can watch your battery basically disappear.
Click to expand...
Click to collapse
I do have pretty bad in/out signal at work, but it wasn't draining my battery that bad after I did the reflash. I'm wondering if I made a change to a kernel setting that is now letting this happen.
I'll be monitoring it today. So far I'm at 86% with 42m SoT. BBS is saying that my phone has been unplugged for 4h 25m. So that is a 3.2%/h drain. My phone has been awake for 44m (screen off). This was increasing before I changed some settings for the kernel, but now seems to not be increasing as much.

Categories

Resources