....WHAT THE HELL THIS BATTERY/CHARGER LIGHT/BATTERY METER PROBLEM really is!! Initially, does the battery actually charge fully and the bar graph and charger light aren't working? Or is the indicator now (after the "fix") STUCK on "full charge" and you don't ever know the actual power level? Does the charger light staying on all the time mean anything, and can any and all of these quirks actually damage the battery, charger and/or Pronto? It can't be good for a charger to keep pumping juice into a fully-charged battery!

It would sure be nice if Philips would have the balls to step up to the plate, admit this problem and help everyone iron out the kinks without us having to do it ourselves (through this EXCELLENT resource we're on!!!)!

Dean...

From prior posts it appears that the DS1000 circuitry is able to detect the true state of charge of the NiMh pak under dynamic load conditions and adjust it's rate of charge accordingly.

Question for you then... do you leave the Pronto in the DS1000 all the time or only put it in when it indicates that a charge is needed???

Last, the _initial_ charge for a virgin NiMh pack should be prox 3hrs.

-Bruce
alpha2data
on eBay

Well, I just got my Pronto 5 days ago. I installed the NIMH battery Wed. night, and the charger light only stayed on for about 20 minutes! I left it overnight and the next day the battery level graph was at about "3-4 bars" of strength.

Last night, I bent the gold battery compartment contacts out a little, reinstalled the battery carefully & properly, and all of a sudden the graph read FULL!! I found this odd, and I wondered if the battery DID originally get charged fully (and the indicator was off) OR if the indicator was now faulty and the battery WASN'T charged. I left it on the chagrger for over 2 hours, and the light never went off (I did NOT leave it on the charger overnight, however, as I was worried about overcharging). And then today, I read about others who have the indicator "stuck" on full charge, so I'me really confused!!

I don't know whether or not to re-install the firmware (I have the latest version), hoping that the reboot will fix these problems, as others said installing the new version would cure all these quirks (but I think they assumed I had an older version).