Rockbox Technical Forums

Support and General Use => Hardware => Topic started by: oceanboy007 on August 10, 2014, 11:34:49 PM

Title: Ipod Video Stop Charging New Battery At 23%
Post by: oceanboy007 on August 10, 2014, 11:34:49 PM
Hello Everyone.

I got complete my Ipod Video SSD mod and it draw much battery than original HDD so I continued to play around with a new 3200 Mah battery (SS Galaxy Note 3), then put all of them to a wood case. The new modded IPV worked normally until the battery run out. I plugged it in charger as usual. After 3 hour i checked system info>Battery capacity 's  at 23%, just suppose that may be cause of this much higher capacity battery. But 3 hour later, the capacity still stucked at 23%. So is guessed may be due to the charging aglorithm is not compatible with this high capacity battery, i went to battery setting and set the Bettery Capacity to highest value (1600 is highest on my rockbox version) but it's still not work.

Iam a rockbox newbie, Pls give me any help or advise for my toruble.
Sincerely appreciate.

Title: Re: Ipod Video Stop Charging New Battery At 23%
Post by: saratoga on August 11, 2014, 12:22:27 PM
Did you hook up everything correctly?  Typically chargers will want to see the thermal sensor on the battery give a reasonable temperature before they'll charge.  If you hooked up the +/- pins but not the thermistor, it may not charge.
Title: Re: Ipod Video Stop Charging New Battery At 23%
Post by: [Saint] on August 11, 2014, 07:26:19 PM
The setting you changed has absolutely nothing to do with charging whatsoever.

The only thing that setting governs is the estimated runtime, which is something most users won't even find. That's all.

On a side note: If an SSD is drawing more than a spinning platter....something is very, very wrong.


[Saint]
Title: Re: Ipod Video Stop Charging New Battery At 23%
Post by: oceanboy007 on August 11, 2014, 08:54:05 PM
Did you hook up everything correctly?  Typically chargers will want to see the thermal sensor on the battery give a reasonable temperature before they'll charge.  If you hooked up the +/- pins but not the thermistor, it may not charge.

(http://images.gittigidiyor.com/10817/Samsung-Galaxy-note-3-Batarya-Pil-n9000-Pil__108177927_3.jpg)

The galaxy note 3 battery has 4 terminal and the 1st - 3rd terminals is (+) (-).
 I soldered the first 3 terminals (1,2,3) of the battery to ipod's battery ribbon. I don't know exactly which terminal 2nd or 4th is thermistor pin. So would i have to resolder the middle wire of ribbon to the 4th terminal?

The setting you changed has absolutely nothing to do with charging whatsoever.

The only thing that setting governs is the estimated runtime, which is something most users won't even find. That's all.

On a side note: If an SSD is drawing more than a spinning platter....something is very, very wrong.


[Saint]

Sound stranger but that 's a truth. 1.8 HDD draw current less than mSata SSD. Here is some experiment from the others:
http://www.head-fi.org/t/707618/rockbox-for-ipod-video-5th-5-5th-msata-ssd-mod (http://www.head-fi.org/t/707618/rockbox-for-ipod-video-5th-5-5th-msata-ssd-mod)
Title: Re: Ipod Video Stop Charging New Battery At 23%
Post by: saratoga on August 11, 2014, 09:28:16 PM
Check and see if any of the pin combinations measure a 10k ohm resistance.  If so, thats probably the temperature sensor. 
Title: Re: Ipod Video Stop Charging New Battery At 23%
Post by: [Saint] on August 11, 2014, 09:30:18 PM
Something is VERY wrong with your setup.

You're using solid state storage, you've added a secondary battery, and you're only managing to get approximately 1 hour additional runtime vs. my iPod Video with a 240GB MK2431GAH and the original, singular, 9 year old, charge cycled a bajillion times, battery.

When one looks at the evidence we're presented with, instead of the facts we know, by rights it would make sense that your iPod would have absolutely fantastic runtime. Yet it is apparent that is quite far from the case here. You have immense battery capacity and a vastly more efficient storage medium, but neither of those things have translated to any significant gains in runtime.

...seems like a rather expensive way of kicking yourself in the nuts. ;)

As a side note, following your HF thread, unless I'm blind, you don't seem to be providing the source for the patched binary you're distributing?


[Saint]