Re: Charging voltage for droid4 battery

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

> > > Recently my Droid4 battery seems to be swelling up quite a bit. It could
> > > be of old age, but bencoh (CC) suggested that he changed the driver code
> > > in his kernel to charge until 4.2v, instead of the 4.35v that mainline
> > > currently seems to use. (After one of his batteries started to swell up too)
> > > 
> > > I assume the 4.35v value was taken from Android?
> 
> Yes the values we have been using are the values dumped from Android.
> 
> So far I have not seen anything changing the values when left connected
> to a charger, so I was assuming/hoping that the charger hardware might
> drop the voltage automatically.. But it seems that's not the case.
> 
> I too have seen at least two swollen batteries and at least one that
> seemed to happen with Cyanogenmod or LineageOS few years ago. I suspect
> it happens if left connected to a charger for a longer period of time
> like several weeks at a time.
> 
> > You can let stock android charge the battery, then read voltage from
> > mainline kernel. It seems stock uses 4.35V:
> > 
> > https://forums.lenovo.com/t5/Moto-Z/MOTO-Z-EXTREME-BATTERY-DRAIN/m-p/4435636
> > 
> > ...but maybe we should not.
> 
> OK so sounds like Motorola always keeps the voltage at 4.35V
> and there's no need to try to dump out any more charger related
> values from Android.
> 
> > https://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
> 
> Pavel, care to send out a minimal fix to lower the charge
> voltage to 4.2V since you have the related changes already?

Hmm. Related changes make it harder, not easier but.. here you
go... But... while this is simple... you are applying it at your own
risk. Untested. One potential problem is that while mainline will charge
to 4.2V, "power off charging" and Adroid will still charge to 4.35V,
leading to charge/discharge cycles even while charging is connected.

> Then later on we may want to optionally consider implementing
> support for 4.35V charge voltages assuming we scale down the
> charge voltage to 4.2V after reaching full charge.

Not sure how that would work / why we'd want to do that / what do you
consider to be full charge.

https://secondlifestorage.com/t-Li-ion-4-35V-How-much-do-we-lose-by-charging-it-at-4-20V
https://batteryuniversity.com/learn/article/confusion_with_voltages

Best regards,
								Pavel



Signed-off-by: Pavel Machek <pavel@xxxxxx>

diff --git a/drivers/power/supply/cpcap-charger.c b/drivers/power/supply/cpcap-charger.c
index cc546bc..3a82f30 100644
--- a/drivers/power/supply/cpcap-charger.c
+++ b/drivers/power/supply/cpcap-charger.c
@@ -440,7 +440,7 @@ static void cpcap_usb_detect(struct work_struct *work)
 			max_current = CPCAP_REG_CRM_ICHRG_0A532;
 
 		error = cpcap_charger_set_state(ddata,
-						CPCAP_REG_CRM_VCHRG_4V35,
+						CPCAP_REG_CRM_VCHRG_4V20,
 						max_current, 0);
 		if (error)
 			goto out_err;

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux