Working on the battery issue... I think - New battery code based on BEHOLD II

WARNING HIGHLY EXPERIMENTAL!
This is a further modification of the battery file to allow for integer 5 reports... I tried debugging myself but didnt find any mistakes (granted i didnt find any the first time around on the other one)...
spareparts only gives 2 digit voltages.. if this holds true across the board this new patch wont work very well since some of the variables are only different in the third digit

The reporting values might be a little jumpy.. there seems to be a problem with the way the adc is read from the power supply that is making it a little jumpy.... The meter might jump a little but should be more accurate then before atleast.. this is something sammy is going to have to fix since we dont have acccess to these files

Letter i sent to
MODULE_AUTHOR("Minsung Kim <ms925.kim@samsung.com>");
MODULE_DESCRIPTION("S3C6410 battery driver");
MODULE_LICENSE("GPL");


Dear Samsung Coder,
I do not know if you still work at samsung, but you are the author listed on the S3C6410 battery driver module... This code has been modified to actually work without reporting 15% at nominal voltage. I do not know if samsung is aware of this problem (they have blown me off anytime i try to inquire) but it is a big issue. Furthermore, the header variables have been adjusted to correlate with battery voltage information from the BEHOLD II which uses the same battery, thus voltage reporting levels should be reasonably close. It would be benefical if you went back to the spica or 9bit adc value instead of the new *100/848*100 since this gives small values and makes it impossible to create percentage lists to correlate to adc values (multiple voltages would share the same adc value).. This code has been modified to report in integers of 5 (100,95,90,85,ect)...
Thank you for your time
- Numus

Tbone looks like you change batt_cal to BATT_CAL correct? that was a typo from the original coder but it still functioned the same..
Ya the first one uses the averages of the 2 reporting levels, then adds the average to the lowest value and if the number is above this, it reports the higher one.. the 2nd one just sees if the value is inbetween the 2 reporting levels it is in there.. these are waht you are talking about right?
Those are the (low)level and (mid)level as reported in debug...
The reporting difference at the lower numbers is something i was unable to think of a solution to fix due to the way it checks at lower numbers (adc values start to merge together).. if you can think of a fix that would rock..
As for the variables in 1490-1501 i had to use that naming scheme to keep myself from getting confused.. as for the adc values in teh header, those are correct even tho they seem to high...
Zef is experiencing a rapid change in the meter when plugged into usb, my only solution is for us to change the polling interval from 2 seconds to 10 seconds.. the behold 2 uses a 10 second polling interval

all those variables SHOULD be pulled from the BATT_CAL in the header file.. i am guessing they did it this way so they could change all adc values by changing only 1 variable
as for the logic being different.. one is reporting to (low)level and one is reporting to (mid)level.. what these are used for i have no fing clue... the small values (15 -> 0) need to be fixed but i have no idea how to..

BTW the first set of code that is reporting to (low)level is correct.. it is the 2nd set reporting to (mid)level that is broken

I a noob. But have experience in the past with simple code's and being able to follow instructions. Vague ones and detailed ones. So my question is this. How do i load this fix into my phone. I've read through the multiple post until my eye's bleed, and apparently i missed how to do it. I would like to be able to get this fix loaded. Appreciate the work you guys are doing. Someone, even if it's not Samsung, needs to fix the mess up's some smeg head did when they codded this awesome phone.

Edit: NVM I belive i just found my answer. I guess thats what i get for not looking around before opening my big mouth.

Thanks for the help. I'm mucking around with it right now. Will be really cool to find out if it will work for me. First time doing something like this to a phone. Kinda excited.

Hey, great work on the battery tweaks.  Since flashing to ZE08, I've noticed my phone no longer sleeps like it used to.  Could this have something to do with the polling for battery info? 

When I unplug the phone from charging and use Spare Parts, in sleep mode it states my phone is running 48% of the time.  So if I haven't touched it in 4 hours, it has run for almost 2 hours of that time.  Unlike some others are reporting, my screen does not turn on.

I have turned off everythign from auto sync, background data, wifi, gps, etc.....

Before this flash, my phone would show almost no run time while in sleep mode.  The end result is I used to get about 30-36 hours out of a battery full charge and yesterday I got about 14.

Also, this is not a complaint. I love what you guys are doing and want to let you know of something that may need tweaking.  Thanks!