isnt working for me, my pandora still forces shut down at an average of 17%, never a single sign of low or critical battery. if i quickly turn pandora back on, it does read it at 1% or something though, and i was always able to charge to 100%
This is a physical problem, I'm almost absolutely certain. The resistance being reported to the bq chip (which measures the capacity and discharge rate of the battery to arrive at a really good estimate of the remaining battery) is incorrect. When I asked if corrosion on the contacts could cause this, the TI tech I was talking to said yes. The result is that it measures a smaller rate of discharge than is actually happening, say around 15-20% which means after 4000mah have been used, it has only measured 3400 or so. It thinks there's still 600mah left when in fact the battery is completely drained.
I've got two Pandora's, one very old (one nub busted) and one fairly new. The old one has no problem handling either battery. The new one dies at about 20% for both batteries. All four cases (each battery in the old and the new) lasts for approximately the same length of time, which means it isn't actually a problem of the battery being bad or one Pandora using more power than the other, it's a reporting issue. This happens on HF4, HF5, and HF6, consistently. I haven't tried HF7 yet. My testing took a very, very, very long time.
There are two ways to fix this: recalculate the resistor value by estimating what the current should be and working backwards, a value that will differ for every Pandora that is affected (or might not be affected at all); alternatively, turn the auto adjust function which will recalculate the capacity of the battery based on the consumption. The second one is very simple: a quick command, discharge the battery, and let it sit for several hours to "normalize" or whatever. In the second case, it continues to mismeasure the discharge rate, but now it's got an equally mismeasured total capacity, so the percentage reported is at least accurate. That's what I did. Now when my battery is dead, it actually reads 0% and I still get my full usage out of it.
Anywho, the real reason I came to this thread was to ask if anyone is able to read from /dev/dsp. I used to be able to "cat /dev/dsp > /dev/dsp" to echo the microphone back to the speaker, but now attempting to cat /dev/dsp gives me an Input/Output error. arecord -L gives me only the null device. Can't seem to find the microphone at all. Is this just me, or can no one access the microphone anymore?
