reason for kcbatt was to make a util to show retu-adc value (percentage was added as a quick and dirty estimation) have you looked at my plots? (yellow is battery, pink is strictly related to charging status) http://mrrau.dyndns.org:23280/n800/kcbatt/batt2gp.png
i could have made it to show fixed 100% above certain value, and fixed 0% below other, but i wanted to have util that can show me how really that value fluctuates over time (with and without load). i'm still doing battery rundown tests, that's why no updates to algo..
last 2 plots are without wifi and with locked screen/keys, observe how quickly #8 drops under load and after getting back to idle it goes up a little (on 16/03 i made a skype call that lasted ~1h), another observation is ending part of the curve on 7/03, i have chosen 340 as a 0% in a rough guess and 570 as 100% (during charging it goes over 600, but drops quickly to ~570), and 400 is ~20% (that's when i print 'recharge suggested') i can make an update version with max set to 560 and min to 400, but what i would really like is a log of the battery rundown from anyone else (to see how batteries of different ages compare). and remember, every % is just an estimation