Database Info

[TESTING] Battery charging issues investigation - Captivate/i9000 owners desired!

OK, as most of you are well aware, I've been doing a lot of poking at our battery charger/power management chipset. (The MAX8998 basically does everything in the case of our device...) This was in response to frequent complaints about slow battery charging and batteries dropping when running Navigation at full brightness on a car dock.
What I've been able to figure out so far:
1) Our stock charge current limit is 600 mA, same as the Captivate and I'm fairly certain the i9000
2) Our battery is slightly larger (1750 mAh) than the Captivate's (1500 mAh).
3) At least on our devices, CPU/screen/etc. usage count against the charge current limit. So the amount going into the battery is 600 mA MINUS whatever the phone is using to operate. This becomes a negative amount with navigation at full brightness.
Lots of Captivate users indicate that their batteries charged MUCH faster than the Infuse.
1) and 2) alone would only cause a small difference between our device and the Captivate - our device has the same charge current limit and the battery is only slightly larger.
3) can make a huge difference, especially if the Captivate doesn't count usage against the charge current limit at all. So the question is, which of the following is the behavior of the Captivate?
a) CPU/screen/etc usage don't count against charge current at all
b) They count against charge current, but the slower CPU and smaller screen mean there's less current counting against us.
So, I'm asking for help from Captivate/i9000 users to run some tests for me. What I need you to have:
1) A Captivate or i9000
2) A kernel that supports the CurrentWidget app from the market. It needs to report 0 mA when off of a charger, and a positive number when on the charger. If it reports "no data", you need a different kernel. I know that for a while MikeyMike01 was running an MIUI/CyanogenMod kernel that was missing the required support. If you get "no data", point me to some other kernels that have source posted on github (please, no kernels with only tarball sources) you can try and I'll look to see if CurrentWidget is supported in them.
Once you've got the above, plug the phone into a charger when the phone is reasonably discharged (below 70-80%, and more specifically make sure battery voltage doesn't rise above 4.05-4.10 volts when you check charge current.) Report the current in mA indicated by CurrentWidget here and I'll provide more instructions based on those results. Please report whether you had the phone connected via a wall charger or via USB - it DOES make a difference.

I came from a captivate, my dad is using it now, when I get home I can check it out..gimme an hour or so
I don't know if his rom supports current widget though. I think the last one I installed for him was mosaic v. If it is supported it shouldn't be a problem at all.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Bummer, the rom he is on doesn't support it. I don't really want to change stuff up for him, so somebody else will have to chime in. Sorry. I know that there are plenty if people on here though that have switched from a captivate, so somebody should be able to help you out. Either that or go make a thread in the captivate forum to have somebody help you out there; they're pretty friendly over there so that shouldn't be an issue. I know that different chargers make a difference, so maybe tell them to make sure and use the oem samsung wall charger.
On a side note, I'm running infused 2.0.4 and current widget is saying I'm charging at 1115-1117 mA with the oem samsung wall charger. Hmmm. I am at like 6% battery though, don't know if that means anything.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

I have my captivate standing by at home. I will be there in around 2 hrs and can install any rom you like on it. Im currently stock KF1

just waiting on my battery to die

welchertc said:
Bummer, the rom he is on doesn't support it. I don't really want to change stuff up for him, so somebody else will have to chime in. Sorry. I know that there are plenty if people on here though that have switched from a captivate, so somebody should be able to help you out. Either that or go make a thread in the captivate forum to have somebody help you out there; they're pretty friendly over there so that shouldn't be an issue. I know that different chargers make a difference, so maybe tell them to make sure and use the oem samsung wall charger.
On a side note, I'm running infused 2.0.4 and current widget is saying I'm charging at 1115-1117 mA with the oem samsung wall charger. Hmmm. I am at like 6% battery though, don't know if that means anything.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
This is why I wanted information from a partially discharged battery - During the constant-current phase (from very low up to around 90% or so), our phones and the Captivate are limited to 600 mA. However all of the ADCs have a scaling factor that is different from phone to phone. Ours is 1.83 times reality, Epic 4G is apparently something like reality divided by 2.2.
So I need to find out what the Cappy is.
TheChefSLC said:
I have my captivate standing by at home. I will be there in around 2 hrs and can install any rom you like on it. Im currently stock KF1
Click to expand...
Click to collapse
I'll poke around to see what's available. I'm not super-familiar with what ROMs are available - but with a link to kernel source I can determine if a kernel is likely to support CurrentWidget. Of course it's ideal if a few people have phones that support it already.
00mred00 said:
just waiting on my battery to die
Click to expand...
Click to collapse
Doesn't need to be dead, just needs to be low enough to get a good scale factor for CW (see above). Once we've figured out the right correction factor the region I'm looking in is the constant-voltage phase near the end of charging (starts around 90%ish). This is where voltage is held constant at nearly 4.2 volts and the current starts dropping.
In our phones, if you turn the screen on for a bit or run StabilityTest for a few minutes, the charge current goes up significantly (since CPU/screen usage count against charge current limit). So the CurrentWidget graph if you're logging with CW looks "spiky". Ideally it should look smooth - so I'm wondering if the Captivate is smooth, or just "spiking less" due to smaller screen/slower CPU.

Using infused 2.04 and bedwa's gb kernel.
1102-1115 ma
It started at 3.66 volts and went to 3.96 volts
Sent from my SAMSUNG-SGH-I997R using XDA App

00mred00 said:
Using infused 2.04 and bedwa's gb kernel.
1102-1115 ma
It started at 3.66 volts and went to 3.96 volts
Sent from my SAMSUNG-SGH-I997R using XDA App
Click to expand...
Click to collapse
I've got a fair amount of data on the Infuse itself - I'm looking for Captivate (and maybe i9000) data for comparison.
Those are about what I'd expect for an Infuse. If you set CurrentWidget to divide by 1.83 you should see it report 600 mA until voltage hits around 4.18 volts. Voltage will initially rise rapidly right after you connect the charger, then rise more slowly up to 4.18 or so. At 4.18, current will start dropping. On the Infuse it drops but with "spikes".
I'm curious if the Captivate also has "spikes" in this phase or not.

Entropy512 said:
This is why I wanted information from a partially discharged battery - During the constant-current phase (from very low up to around 90% or so), our phones and the Captivate are limited to 600 mA. However all of the ADCs have a scaling factor that is different from phone to phone. Ours is 1.83 times reality, Epic 4G is apparently something like reality divided by 2.2.
So I need to find out what the Cappy is.
I'll poke around to see what's available. I'm not super-familiar with what ROMs are available - but with a link to kernel source I can determine if a kernel is likely to support CurrentWidget. Of course it's ideal if a few people have phones that support it already.
Doesn't need to be dead, just needs to be low enough to get a good scale factor for CW (see above). Once we've figured out the right correction factor the region I'm looking in is the constant-voltage phase near the end of charging (starts around 90%ish). This is where voltage is held constant at nearly 4.2 volts and the current starts dropping.
In our phones, if you turn the screen on for a bit or run StabilityTest for a few minutes, the charge current goes up significantly (since CPU/screen usage count against charge current limit). So the CurrentWidget graph if you're logging with CW looks "spiky". Ideally it should look smooth - so I'm wondering if the Captivate is smooth, or just "spiking less" due to smaller screen/slower CPU.
Click to expand...
Click to collapse
I didnt know that 1.6 Ghz is slower than the infuse? Maybe i pushed mine a little more but my phones faster
Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.

b-eock said:
I didnt know that 1.6 Ghz is slower than the infuse? Maybe i pushed mine a little more but my phones faster
Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
Click to expand...
Click to collapse
Stock is 1...
However if it charges when cranked to full speed with the screen on, that would be interesting. I would LOVE for some CurrentWidget tests if CW is working for you.

Entropy512 said:
Stock is 1...
However if it charges when cranked to full speed with the screen on, that would be interesting. I would LOVE for some CurrentWidget tests if CW is working for you.
Click to expand...
Click to collapse
I does, but only for a bit, then it wont charge for a bit...
Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.

Driving....car charger....nav and pandora running
871 ma 3.728 vlts
Sorry...see now you are looking for captivate info
Sent from my SAMSUNG-SGH-I997R using XDA App

b-eock said:
I does, but only for a bit, then it wont charge for a bit...
Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
Click to expand...
Click to collapse
That's interesting...
Does CurrentWidget work for you?
"Plain KF1" - does that include stock kernel?
Forgive me - I'm only mildly familiar with the Captivate, just that there are LOTS of reports from others it charges significantly faster than the Infuse, so I'm trying to figure out why.

Entropy512 said:
That's interesting...
Does CurrentWidget work for you?
"Plain KF1" - does that include stock kernel?
Forgive me - I'm only mildly familiar with the Captivate, just that there are LOTS of reports from others it charges significantly faster than the Infuse, so I'm trying to figure out why.
Click to expand...
Click to collapse
Yahh stock kernel, for now. Was on MIUI a few days ago at 1.6 GHz stable(im a speed and flashing junkie) and i havent tried the widget
Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.

00mred00 said:
Driving....car charger....nav and pandora running
871 ma 3.728 vlts
Sorry...see now you are looking for captivate info
Sent from my SAMSUNG-SGH-I997R using XDA App
Click to expand...
Click to collapse
Heh. Your car charger is either being detected as USB or it's browning out (not enough current capacity). Probably USB - 871 mA becomes 475 when you divide it by the 1.83 scale factor, and that's EXACTLY what the current limit when on a USB charger is. In CurrentWidget settings, it's "Operation on Value", "Operation Type" is Divide, and "Operation Value" is 1.83 for the Infuse.
The correct settings for the Captivate are unknown. That's what the initial test (reported current on AC when reasonably discharged) is for.

Entropy512 said:
Heh. Your car charger is either being detected as USB or it's browning out (not enough current capacity). Probably USB - 871 mA becomes 475 when you divide it by the 1.83 scale factor, and that's EXACTLY what the current limit when on a USB charger is. In CurrentWidget settings, it's "Operation on Value", "Operation Type" is Divide, and "Operation Value" is 1.83 for the Infuse.
The correct settings for the Captivate are unknown. That's what the initial test (reported current on AC when reasonably discharged) is for.
Click to expand...
Click to collapse
Makes sense....my car charger is usb>into a usb car adaptor
Made the changes to /1.83
Sent from my SAMSUNG-SGH-I997R using XDA App

Entropy512 said:
Heh. Your car charger is either being detected as USB or it's browning out (not enough current capacity). Probably USB - 871 mA becomes 475 when you divide it by the 1.83 scale factor, and that's EXACTLY what the current limit when on a USB charger is. In CurrentWidget settings, it's "Operation on Value", "Operation Type" is Divide, and "Operation Value" is 1.83 for the Infuse.
The correct settings for the Captivate are unknown. That's what the initial test (reported current on AC when reasonably discharged) is for.
Click to expand...
Click to collapse
That saddens me. I was thinking about adding a USB port to my dash area to allow me to more easily keep my infuse plugged in with the car dock(the cigarette adapter blocks one of only two cupholders). If I can't use USB to charge enough, I'm screwed. ;P

araemo said:
That saddens me. I was thinking about adding a USB port to my dash area to allow me to more easily keep my infuse plugged in with the car dock(the cigarette adapter blocks one of only two cupholders). If I can't use USB to charge enough, I'm screwed. ;P
Click to expand...
Click to collapse
There's a bit of confusion here. There is a REAL USB port, there are dumb chargers that are detected as USB ports, and there are dumb chargers that are properly detected as dumb chargers. Physically, they all look exactly the same. Electrically they are different.
Real USB port - An actual USB host
Dumb charger accidentally detected as USB - who knows. The resistors that iDevices use to indicate "dumb charger" are nonstandard and frequently cause this. iPad/iPhone/iPod chargers are detected as normal USB ports by the Infuse.
Dumb charger detected as a dumb charger - In the case of our Infuse, these have USB D+ and D- shorted together. You can either fix this with a solder blob in the charger, or a cable that shorts D+ and D- for you, like AT&T's dedicated "charge only" cable.
Still looking for someone with working CurrentWidget on a Captivate or i9000...

Entropy512 said:
AT&T's dedicated "charge only" cable.
Click to expand...
Click to collapse
Why does this seem like a recipe for trouble to me? If a simple cable can cause the phone to attempt to draw over-spec, I'd imagine seeing lots of fried usb ports and simple usb chargers. (That said, we're only drawing 600mA normally? That's only 20% over spec, so they can probably handle it.)
Interesting stuff.. didn't know that the extra-power usb power ports had that simple a standard.. I had gotten the impression that there was real negotiation going on, to figure out what they're rated at. (Since they originally said up to 1A I think, but then decided they needed a way to let some devices safely draw more).
And, consider this a bump. ;P
I think a buddy of mine has a captivate, so I may be able to get you some info in a week or two if you haven't gotten it by then.

Entropy see if Andromeda 3.0 running Ursa minor kernel will do please I can test a cappy on that rom and kernel.
Sent from my SGH-I997 using XDA App

Battery drain while charging

I'm currently running Sean's latest leak/update and have noticed significant battery drain despite being plugged into the charger. I never really paid enough attention while on gb roms, so I'm not sure if this is an ics thing or not. My buddy at work has had similar issues and is completely bone stock, so I'm thinking it's just a skyrocket issue.
Anybody else notice this? It happens no matter what I'm doing on the phone and is obviously more noticeable when playing games. It seems to me that the charger should at least compensate for the usage!
It had me so baffled, I've re-flashed multiple times now with the same results.
Sent from my SAMSUNG-SGH-I727 using XDA

Your using the OEM charger? whats the max amp written on it?

kishke said:
Your using the OEM charger? whats the max amp written on it?
Click to expand...
Click to collapse
Yeah... it's 5v/1a. Same with my buddy. I thought that might be the problem, and I had switched it with an old one, but don't think so. I've used the powerskin in the past, and it's also 5v/1a... still drains with it.
I'm totally puzzled! I've changed chargers, gone with/without the powerskin, re-flashed roms, calibrated the battery and who knows what else. Only thing I hadn't done was replace the battery, but now that my buddy is having issues on stock, I don't know if that's the problem or not....
Sent from my SAMSUNG-SGH-I727 using XDA

Its probably the battery while charging check if in about phone it says its conncted to ac.
Also are you rooted?

Could also be the cable. I have had the exact issue, replaced the cable and now its fine. Its funny cause the galaxy s2 is far more picky when it comes to chargers/cables. For instance. I can plug it in and the phone won't do a think, yet when I plug it in the skyrocket it will accept the connection.

kishke said:
Its probably the battery while charging check if in about phone it says its conncted to ac.
Also are you rooted?
Click to expand...
Click to collapse
I'm thinking it's the battery... it shows it's charging. I've tried spare chargers and cable combos with the same outcome. It's just odd that my friend's is doing the same thing!
I'm rooted/rom'd & he's bone stock.
Sent from my SAMSUNG-SGH-I727 using XDA

g2tegg said:
Could also be the cable. I have had the exact issue, replaced the cable and now its fine. Its funny cause the galaxy s2 is far more picky when it comes to chargers/cables. For instance. I can plug it in and the phone won't do a think, yet when I plug it in the skyrocket it will accept the connection.
Click to expand...
Click to collapse
I've tried diff cable/charger combos... no luck. I had cable issues with my epic (sprint) and knew Samsung had issues with them in the past, so that was one of the first things that came to mind... no dice though!
Sent from my SAMSUNG-SGH-I727 using XDA

Test your receptacle with a digital multi meter . The stock charger works great. Enough so
That i spliced 3 high quality usb cable and have over a ten foot cable which charges just fine.
So its possible. U have a bad charger. Crap cables. Or overdrawn circuit whith your receptacles. No enough to trip but enough your charger cant pull 1 amp

traumaj said:
I'm currently running Sean's latest leak/update and have noticed significant battery drain despite being plugged into the charger. I never really paid enough attention while on gb roms, so I'm not sure if this is an ics thing or not. My buddy at work has had similar issues and is completely bone stock, so I'm thinking it's just a skyrocket issue.
Anybody else notice this? It happens no matter what I'm doing on the phone and is obviously more noticeable when playing games. It seems to me that the charger should at least compensate for the usage!
It had me so baffled, I've re-flashed multiple times now with the same results.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
I noticed the same issue. Dont worry, offical ics will be out very soon!
Sent from my SAMSUNG-SGH-I727 using xda premium

I did a 1.5 hour Skype video while on charge and my battery never charged it held at the same percentage. Anything else I do charging outweighs my use. Gotta be the charger or the phone itself. Even if you have no battery in it should still boot off the charger and run correct?

traumaj said:
I'm thinking it's the battery... it shows it's charging. I've tried spare chargers and cable combos with the same outcome. It's just odd that my friend's is doing the same thing!
I'm rooted/rom'd & he's bone stock.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Use any type of root explorer, while charging got to sys/class/power supply/battery
and open batt_current_xxx or something like this, I'll check it later if you get into troubles, breaking my head now with tasker at the moment. It should show a value around 8500, at least that's what it shows for me.

I'm having the same issue on Sean's latest update, my battery current adc file says 2934... I posted this in the sky ics thread
"I've been having some battery issues since coming to this ROM on update six. I'm on nine now and all is well, battery life included once I get it charged up. I'm using OEM Samsung everything, charging block, two different cables, my original battery and a 2100Mah extended for the Gnex. All Samsung, no change between them. This thing just REFUSES to charge if I'm using it while plugged in, and if I leave it alone and let it charge, it takes absolutely forever to charge either battery. The skyrocket battery won't gain one percent charge if I'm using it while plugged in, and the Gnex battery actually discharges slowly!  Any ideas? I bought this phone from a member on here and it came with superlite 5 and I don't recall it having this problem."

If the file reading is that low there must be an issue with the amp, if you tried a different charger and cables and it happened since changing roms I'd say its a pure software issue. Maybe you should try flashing a different kernel before trying to change your rom, the problem may be laying there.

I had the same issue but mine was related to the usb cable. With a new micro usb cable my phone charges without issue.
Sent from my SAMSUNG-SGH-I727 using xda premium

[Q] False Battery reading!!!!!!!!

Hi there my fellow comrades, My LG optimus 3D has a problem when it comes to reading my battery percentage, the phone will charge the battery with the corret voltage tested with a voltage meter but when the battery voltage is 4.7 volts i.e a full battery it desplays 3% on sreen.
I have tride goin into clockworkmod and deletin batterystats.bin a number of time but my fone still doesent go passed 4% on a good day and after a couple of minutes of use my fone turns off because it thinks its a low battery but the battery has a full charge, i really do think this is a softwere fault, oh and i didnt do anything to the phone when it started doin this witch was about a month ago.
the things ive done so far is
- rooted my fone
- tride a new rom still the same reasult
- deleted Bateerystats.bin then letting it charge over night to find its a 3% still
Oh and i just want to point out the day after my warrenty ran out my phone decided to do this, i really do think it is a built in time bomb so it was designed to "brake"

The problem could be battery related , your battery has some circuitry to prevent overcharging and some calculations if memory serves. Could be full but that circuit may have failed. Try a new battery if it doesn't work find an adapter that is powerful enough to start your phone (4.7 volts 1500 mah) and wire it. (Do it right do not short it and wire + to + - to - ) Then flash a stock rom and baseband unroot it and take it to a warranty service center.
In my humble opinion...
Sent from my LG-P920 using xda app-developers app

boltthrower56 said:
The problem could be battery related , your battery has some circuitry to prevent overcharging and some calculations if memory serves. Could be full but that circuit may have failed. Try a new battery if it doesn't work find an adapter that is powerful enough to start your phone (4.7 volts 1500 mah) and wire it. (Do it right do not short it and wire + to + - to - ) Then flash a stock rom and baseband unroot it and take it to a warranty service center.
In my humble opinion...
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Sorry i forget to mention that i allready tride a differant battery still the same and i allso tride a battery calibration app aswell

Does it overheat when charging ? If it doesn't read below ;
It's hard to guess but if it is software related you would need equipment to test it as battery cannot be used. First as i told you before you need an adapter.
Specs should be the same as your battery. You need to wire it to your phone as i explained before. Boot it if it still shows as 4 percent it probably is software related... Now don't remove the adapter and go back to gingerbread using guides throughout the forum. It should be fixed.
If it's not then it's time for you to go to a professional.
If you don't think you can do those steps then it's time for you to go to a professional. Don't go to LG before going back to stock roms or unrooting. They'll void your warranty otherwise. Yell at them , call their superiors , make some noise if they do. That seemed to work in my case.
Hope I Helped.
Cheers!
Sent from my LG-P920 using xda app-developers app

Desire S weird charging problem

Hello XDA members,
I bought an HTC desire S a few weeks ago. Phone works flawlessly but takes ages to charge. Phone doesnt heat up, shows proper information while charging (AC on wall charger and USB on computer) but charging is very slow. On wall charger, battery takes 5-6 hours to charge from 25-30% to 90-100%. I have tried different USB cables, batteries, chargers and even tried 3 different ROMs with different KERNEL and calibrated the battery. Once charged, battery lasts as it should. I don't think this can be caused by bad USB port because data transfer rate is normal. I tried charging after turning off the device and the charging rate was fairly quicker. So i tried flashing custom roms but that didn't solved the problem.
Any ideas what else i should do are much appreciated..

is it a new phone? mine charges like yours but the battery is almost 2 years old.

maximus84 said:
Phone works flawlessly but takes ages to charge. Phone doesnt heat up, shows proper information while charging (AC on wall charger and USB on computer) but charging is very slow. On wall charger, battery takes 5-6 hours to charge from 25-30% to 90-100%.
Click to expand...
Click to collapse
I only can say: Same thing here. Haven't really looked into this after flashing Flinny's 10.1 ROM, but with the stock HTC ROM I had the same issue. What I could see was, that the phone charged really fast up to about 80% and then the charging-progress slowed down to a crawl.

J_Schnacki said:
I only can say: Same thing here. Haven't really looked into this after flashing Flinny's 10.1 ROM, but with the stock HTC ROM I had the same issue. What I could see was, that the phone charged really fast up to about 80% and then the charging-progress slowed down to a crawl.
Click to expand...
Click to collapse
This may shed some light on your problem

amidabuddha said:
This may shed some light on your problem
Click to expand...
Click to collapse
Yes, that explains it short and clear.

psmok said:
is it a new phone? mine charges like yours but the battery is almost 2 years old.
Click to expand...
Click to collapse
yes. its a new phone. i had doubts that the battery maybe the culprit and tried an original battery out of a friends phone and then bought an new oem battery but that didnt solve the problem. The phone is charging (AC charger) at the moment. 43% to 56% in almost 1 hour.

amidabuddha said:
This may shed some light on your problem
Click to expand...
Click to collapse
I am currently on 3.0.56-ck1-amidabuddha-xl+ kernal. Any tips for me related to this problem?

maximus84 said:
I am currently on 3.0.56-ck1-amidabuddha-xl+ kernal. Any tips for me related to this problem?
Click to expand...
Click to collapse
Well Tweaked is discontinued now with a reason. Try Patched

amidabuddha said:
Well Tweaked is discontinued now with a reason. Try Patched
Click to expand...
Click to collapse
Thanx for the advice. Going to flash the patched kernel.

amidabuddha said:
Well Tweaked is discontinued now with a reason. Try Patched
Click to expand...
Click to collapse
Flashed the patched (custom, stable) kernel. Battery life has somewhat improved but charging is still awful sluggish.

maximus84 said:
Flashed the patched (custom, stable) kernel. Battery life has somewhat improved but charging is still awful sluggish.
Click to expand...
Click to collapse
Maybe it is hardware related
IDK
But as said in the kernel thread if you do not need additional features you better bet on the Stock kernel for Sense 3.6 / MIUI or B2B for Sense 4. This should give you best possible operation and is my personal choice as well
Sent from my HTC Desire S

Charging slow - Can't charge to 100% [Solved]

The problem is the middle pin on the battery connector (on the motherboard) which reads the battery temp is damaged, so only slow charging for me. the battery connector/pin is too small to resolder without the proper tools and no one is selling a 32GB Nexus 5 board currently. The few I saw last week were like $100 :crying: so can't fix for now.
OP is below
-------------------------------------------------
Hey XDA'ers,
Not sure what's wrong with my N5, the phone is charging extremely slow. the icon on the notification area shows the phone as charging. In the battery settings it says the phone is not charging. Also using apps like ampere tell me....
battery health: cold
temperature: -30C
Voltage: 3.9 - 3.95 range [normal voltage is 3.8 so seems fine]
the behavior is consistent across all ROM's, stock, etc. . and the phone only charges in bootloader mode (still slow at that) any advice would be appreciated!
Thanks

What value of current ampere shows you??
Did you try by changing charger or data cable??

LetJect said:
What value of current ampere shows you??
Did you try by changing charger or data cable??
Click to expand...
Click to collapse
value of current? I don't see that as a option. and many charger and cables they all work on other phones but the issue remains on mine.

At low battery voltage should be at about 3.6V and current drawn should be around 1150 mA. As voltage increases i.e. full charge voltage should be around 4.5 V and current drawn at 90% of battery should be around 900mA.
So just check values by app Ampere.

drago10029 said:
Hey XDA'ers,
Not sure what's wrong with my N5, the phone is charging extremely slow. the icon on the notification area shows the phone as charging. In the battery settings it says the phone is not charging. Also using apps like ampere tell me....
battery health: cold
temperature: -30C
Voltage: 3.9 - 3.95 range [normal voltage is 3.8 so seems fine]
the behavior is consistent across all ROM's, stock, etc. . and the phone only charges in bootloader mode (still slow at that) any advice would be appreciated!
Thanks
Click to expand...
Click to collapse
I heard somewhere that this is problem in battery connector or thermal sensor. There was fix for this too. I can tell you if i find it again

V4LT5U said:
I heard somewhere that this is problem in battery connector or thermal sensor. There was fix for this too. I can tell you if i find it again
Click to expand...
Click to collapse
You are correct and it could be either of the 2 actually. In my case I noticed the middle battery connector on my nexus 5 motherboard is bad so that explains why I can't get it to charge properly.
The problem now is I haven't been able to find a replacement 32GB board at all, not even ebay........ so I'm gonna make another thread to ask for some help with that.

drago10029 said:
You are correct and it could be either of the 2 actually. In my case I noticed the middle battery connector on my nexus 5 motherboard is bad so that explains why I can't get it to charge properly.
The problem now is I haven't been able to find a replacement 32GB board at all, not even ebay........ so I'm gonna make another thread to ask for some help with that.
Click to expand...
Click to collapse
Damn. Did you damage it like if you were replacing battery? Guess i have to remember to be careful if i replace mine. Btw found the thread, may not help you if the pin is like not even attached anymore but anyways here it is http://forum.xda-developers.com/google-nexus-5/help/battery-issue-charge-cold-t3100267
Edit: And here is iFixit mother/logicboard, don't if you get extra customs/fees if you don't live in USA. Not even sure do they send them from USA, or do they have like EU stock or something. No idea. And not sure if it even is worth the price. link: https://www.ifixit.com/Store/Parts/Google-Nexus-5-Motherboard/IF293-004-1
Edit 2: Aand they are out of stock.
Edit 3: You could try also to find slightly damaged n5 with working mobo but again need to think is it worth is and such. Could try also to sell the parts you didn't use from it.

V4LT5U said:
Damn. Did you damage it like if you were replacing battery? Guess i have to remember to be careful if i replace mine. Btw found the thread, may not help you if the pin is like not even attached anymore but anyways here it is http://forum.xda-developers.com/google-nexus-5/help/battery-issue-charge-cold-t3100267
Edit: And here is iFixit mother/logicboard, don't if you get extra customs/fees if you don't live in USA. Not even sure do they send them from USA, or do they have like EU stock or something. No idea. And not sure if it even is worth the price. link: https://www.ifixit.com/Store/Parts/Google-Nexus-5-Motherboard/IF293-004-1
Edit 2: Aand they are out of stock.
Edit 3: You could try also to find slightly damaged n5 with working mobo but again need to think is it worth is and such. Could try also to sell the parts you didn't use from it.
Click to expand...
Click to collapse
thanks for the advice, I removed the connector like once but gently. Our battery connector (N5) is super cheap. and reconnecting is possible with good soldering equipment, which would be better since that is the only issue. and I don't have money for anything now so I can try solder or buy another board.
or sell it for parts which might be the case for me.