Battery Meter and Temp reading "Fix" (workaround) (6/22 Update)

[Unknownforce]

Originally Posted by sovereignty03

Sorry...never updated my post. I realized what av_index is after looking into the code some more. You know, you are trying to do something about the increase while charging, but most devices I have used just display some type of animation while charging and then display the percentage again when it is unplugged.

Sure, it just shows the animation, but when you go into the spare parts and look at the battery percentage (without my latest release) it's at least 40% higher than it should be... This is why I manipulated the code to forcibly bring that number lower. Because of this, you can charge it a lot more accurately while charging with android. I set it to be a FEW percent higher than the reading android has while on discharge, so that it will hit 100% when it's more like 95-97 and, if the code is correct, STOP charging at that percent and not fry the battery or something.

WITHOUT this fix, it would ready 100% when it's more like 50-60% and not charge beyond that because it thinks it's are 100% because of the extreme increase in the voltage reading while on the charger.

Originally Posted by sovereignty03

About keeping stable under varying loads, There is a solution that uses the output impedance of the battery. I am in the (slow) process of compiling the data to plot a curve for the output resistance as a factor of battery temperature. If one knows this curve it is painless to calculate the correct percentage of charge. I'll share it with you when I get it done. I haven't had much time to dedicate to it yet...

The problem here is that I don't think it's reading the proper discharge values as WinMo does... WinMo I believe pulls the mA that's currently being discharged and uses it in it's calculations among the temp and voltage readings, now that COULD be calculated FROM the temp and voltage readings, but again, I don't know... I still haven't had much time to do much with the dll file and see exactly what's going on... and with my limited knowledge of ARM ASM... it's going to take quite some time... which is why I'm only guessing at numbers for now to at least get it CLOSE to what it should be reading.