yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] RogerPodacter:
oh for sure that is what did it. that will tax your battery hard, especially down at those lower voltages.
[Nexus One Android Development] difrnt:
You won't be getting much more battery out of the 1600 as your stock battery is 1400.
[Nexus One Android Development] RogerPodacter:
are you going by the ranges i posted above, or was your phone actually showing <5%? with your new setpoint, some things you can check now. when doing a charge from empty to full, take note what mAh you start from, and what mAh you finish at, and if it makes any jump to full or not. and also when starting at full and draining the phone all day, note what mAh you started, and where you finish at empty battery, the mAh and voltage, just to make sure your new range is being used properly. i think before you said it died at 3.8 volts, which is only like half way point lol. so it ran out of mAh. now it shouldnt do that anymore.
[Nexus One Android Development] RogerPodacter:
i think that's what we wanna check though. because from the batteryboss tests, they said the same thing. but now that we have this newly acquired knowledge of dumpreg and exact voltage setpoints, we should re-visit that. i'm wondering if those 1600mAh batteries are actually stock 1400 batteries, or if they are in fact slightly bigger, etc. that's why i'm curious about his battery!

related note, i have a newer stock battery and yesterday i did a test and managed to squeeze 1430 mAh of USABLE capacity out of that sucker, AND that was only around 3.4 volts. i bet i could have squeezed 1500 mAh out of it if i let it go down to 3 volts. i wonder if the 1600 battery is just a stock batt with lowered empty volt setpoint...? curious.
[Nexus One Android Development] RogerPodacter:
yeah dude for sure, we should try to track the different aftermarket batteries and their settings. i too have wondered if all these cheaper aftermarkets are using the same pack, and just programming with different full40 points and selling them for different prices. we know seido did that already in the palm pre thread. makes you wonder...
[Nexus One Android Development] myakove:
Now I just let the phone die and I see drop from 5% to 0%

<6>[ 2868.369445] batt: 6%, 3317 mV, -71 mA (-61 avg), 30.1 C, 84 mAh

<6>[ 2918.534057] batt: 6%, 3307 mV, -75 mA (-72 avg), 30.0 C, 83 mAh

<6>[ 2962.490081] batt: 6%, 3293 mV, -80 mA (-57 avg), 30.0 C, 83 mAh

<6>[ 3004.725555] batt: 6%, 3283 mV, -68 mA (-57 avg), 29.8 C, 81 mAh

<6>[ 3047.720123] batt: 6%, 3268 mV, -65 mA (-59 avg), 29.8 C, 80 mAh

<6>[ 3091.569458] batt: 6%, 3258 mV, -10 mA (-72 avg), 30.0 C, 80 mAh

<6>[ 3138.725219] batt: 5%, 3234 mV, -80 mA (-68 avg), 30.0 C, 78 mAh

<6>[ 3187.646270] batt: 5%, 3229 mV, -86 mA (-82 avg), 29.8 C, 76 mAh

<6>[ 3231.693115] batt: 5%, 3214 mV, -71 mA (-73 avg), 29.8 C, 76 mAh

<6>[ 3274.563018] batt: 5%, 3200 mV, -77 mA (-59 avg), 29.8 C, 75 mAh

<6>[ 3324.626464] active wake lock ds2784-battery

<6>[ 3324.633056] active wake lock ds2784-battery

<6>[ 3324.682373] batt: 5%, 3175 mV, -69 mA (-74 avg), 29.8 C, 75 mAh

<6>[ 3377.295898] batt: 5%, 3141 mV, -35 mA (-63 avg), 29.8 C, 73 mAh

<6>[ 3407.228088] batt: 5%, 3127 mV, -26 mA (-45 avg), 29.8 C, 72 mAh

<6>[ 3457.152587] active wake lock ds2784-battery

<6>[ 3457.207061] batt: 0%, 3102 mV, -49 mA (-77 avg), 30.0 C, 0 mAh
[Nexus One Android Development] RogerPodacter:
yeah may turn out that's too low and not stable enough. so maybe 3.2 volt would be the better option.
[Nexus One Android Development] myakove:
What is the set reg for 3.2?
[Nexus One Android Development] theloginwithnoname:
That's odd, as the capacity was good when the voltage initially dropped below 3.2

Observation: your mA values seem to be either rather high or rather low, depending on whether your phone was sleeping or active. My values are ~ -5 to -9mA sleeping or -100 if active (up to -500 depending on brightness of screen and foreground app - e.g. maps!)
[Nexus One Android Development] myakove:
Phone was sleep at this time
[Nexus One Android Development] RogerPodacter:
so you did a full discharge and ended up running out of mAh capacity before running out of voltage? that's what it looks like, and that means you still have additional capacity you could be using. either you set your age to 100% and see how much more that gets you. or you raise your full40 value by another 100mAh or so. basically you want to hit that empty volt point just as you run out of mAh. that's the way these batteries are programmed from stock (well except for some of these aftermarkets which are incorrect). so take note of that.

and to be technical about the above, really these batteries will shut down from 2 conditions, either hitting the empty volt point, which we want to hit, or hitting what they call "active empty mAh" point. which if you check in the dumpreg is usually about 19mAh for stock battery. and actually i'm looking at your second log and it shows you were right at 19.2 mAh when hit zero percent right before shutdown. so that all looks good. but you still had a significant amount of usable voltage, so i say do one more test and then raise your full40 value. maybe you have a 2800 battery, who knows...

last note, you found out indirectly that our battery also has a current setting for empty point, which is right around the 200mA mark (gotta check dumpreg exactly). but its a qualifier so if you hit empty volt, but your current draw is lower, it wont trip the learn flag/shut down. once current goes above that 200mA, then it trips learn flag/shutdown. curious how you were able to monitor that closely!

from data sheet:

EDIT: that's likely why you failed to hit learn mode, since you didnt hit the voltage that activates the learn flag.
[Nexus One Android Development] RogerPodacter:
setting to 3.201 volts:

0x66 a4 > setreg
[Nexus One Android Development] mtw4991:
On cm 252 and wm's 111810b avs kernel and all is smooth. Setreg 0x14 80 to set age to 100 and 0x65 06 to set empty to <20mah. Plugged into wall ac to charge and the max charge is only 30-80mah which seems very slow? Any suggestions?
[Nexus One Android Development] RogerPodacter:
I don't understand what you mean. Are you saying there is no current going into the battery? What's the current reading? Maybe post the dmesg log during charging...
[Nexus One Android Development] mtw4991:
I think I figured it out. Wm other kernel would charge below 99%, but his latest won't start until 89% or less. Back up to around 400mv on car charger.
[Nexus One Android Development] EnhancerFIN:
What do you think I should do as I'm running out of mAh:s while my battery voltage remains over 3.7v? This is with stock battery. I get a shutdown because amps go to zero.

I've tried to set age to 100, lowered AEvoltage to 3.2, shutdown mAh:s adjusted below 20 and even raised the full40 value for a test to over 2500mAh:s.
[Nexus One Android Development] samarium:
Yes, I realise that the voltage didn't get down to AEV, and thus LEARNF didn't get set.

Full charge logs:

# /d/battery_log
timestamp mV mA avg mA uAh dC % src mode reg full
16017 4182 88 87 2475200 246 91 ac fast 0x07 0
16067 4182 84 86 2476800 246 91 ac fast 0x07 0
16117 4182 81 83 2478400 246 92 ac fast 0x07 0
16167 4182 83 82 2480000 246 92 ac fast 0x07 0
16217 4182 80 81 2480000 246 92 ac fast 0x07 0
16267 4187 77 80 2481600 246 92 ac fast 0x07 0
16318 4187 79 78 2699200 246 100 ac full 0x87 1
16368 4177 -1 0 2699200 246 100 ac full 0x87 1
16418 4177 -1 -1 2699200 245 100 ac full 0x87 1
16468 4177 -1 -1 2699200 245 100 ac full 0x87 1

IIRC last time before when I was poking around with Full40 it seemed that if I reduced Full40 then the available mAh increased rather than increased. So this time I'm going to reduce the Full40 down to around 2500 mAh. What is the formula you use to derive the setreg? mAh * 0.4166, MSB=>6a, LSB=>6b? What page of the datasheet describes this?

I was monitoring using two sessions connected via ssh to dropbear on the phone.

Monitor #1 was this script on the sdcard, run using: sh /sdcard/bat.sh 3

# cat /sdcard/bat.sh
#!/system/xbin/sh
cd /sys/de*/pl*/ds*
while echo `date` ' ' `cat getvoltage` uV ' ' `cat getcurrent` uA ' ' `cat getmAh` uAh ' ' `cat statusreg`
do
sleep ${1-60}
done
#
# # run at 60 second interval
# sh /sdcard/bat.sh
#
# # run at 3 second interval
# sh /sdcard/bat.sh 3

Monitor #2 was just on the command line and something like this:

# cd /d
# while sed 1q bat* && tail -3 bat*; do sleep 3; done

Also, then the phone reboots, the last bit of the dmesg from the previous boot is available in /proc/last_kmsg, so I just did something like:

# grep batt /proc/last_kmsg | tail -20

I have the guts of an awk script to pick pieces out of dumpreg and output them, however I'm not sure about the formulas despite reading the datasheet.
[Nexus One Android Development] samarium:
I'm having the same issue, my current plan is to wait until the battery is low, and then decrease Full40, as I seem to recall that this resulted in an increase in available mAh, and since we want enough mAh to cause voltage < VAE I'm hoping this will do the trick.

I've tested reducing Full40 at the top of the charge range, and it doesn't have much effect on mAh, so I'm planning on testing at the bottom of the charge range.
[Nexus One Android Development] RogerPodacter:
what mAh are you starting at from a full charge? around 1400mAh? you should definitely set age to 100 and raise full40. but i'm not sure if you already tried that why it wouldnt work. try to grab some logs next time at full charge and then near empty. i'd say set full40 to 1500.
[Nexus One Android Development] RogerPodacter:
just keep in mind that the full40 is what the battery uses to calculate its total range. so when we set to 1452, we typically see 1440. lowering it reduces your total capacity, increasing it raises capacity. and post your results of what you find!
[Nexus One Android Development] RogerPodacter:
the full40 equation is on page 5 of this PDF:

http://pdfserv.maxim-ic.com/en/an/AN4043.pdf

its a 2-byte MSB/LSB combo, so bitshifting is involved and gets a little tricky. hit me up if you need help.
[Nexus One Android Development] samarium:
Thanks for the reference.

I've been across bit wise operations since the 80's so I'll be OK thanks.
[Nexus One Android Development] myakove:
I just notice that my age is back to 94 after I set this to 87 and now when charging it's jump from 94% > 100% and shutdown in 5%.
[Nexus One Android Development] myakove:
somehow I got this after set age to 100% when battery was on 100% (the battery go down to 94% when I set the age)

last time I only get 1250 mAh but now I got 1467 mAh

After shutdown the age was 94 again.

<6>[ 12.623352] batt: 100%, 4177 mV, -23 mA (55 avg), 32.7 C, 1467 mAh

<6>[ 12.630950] batt: charging OFF

<6>[ 16.535278] batt: charging FAST

<6>[ 63.366485] batt: 100%, 4162 mV, -67 mA (-28 avg), 32.6 C, 1465 mAh

<6>[ 116.047668] batt: 100%, 4153 mV, -146 mA (-77 avg), 33.0 C, 1465 mAh

<6>[ 143.757507] batt: age_scalar life left is: 94

<6>[ 166.157226] batt: 100%, 4172 mV, -2 mA (-10 avg), 33.5 C, 1465 mAh

<6>[ 184.911010] batt: charging OFF

<6>[ 216.469207] batt: 100%, 3986 mV, -1315 mA (-35 avg), 35.0 C, 1464 mAh

<6>[ 268.962158] batt: 100%, 3967 mV, -1121 mA (-1269 avg), 37.5 C, 1448 mAh

<6>[ 319.092926] batt: 100%, 4109 mV, -125 mA (-945 avg), 36.7 C, 1436 mAh

<6>[ 369.214080] batt: 100%, 4114 mV, -116 mA (-126 avg), 36.0 C, 1435 mAh

<6>[ 419.405090] batt: 100%, 4123 mV, -64 mA (-68 avg), 36.0 C, 1433 mAh

<6>[ 469.559020] batt: 100%, 4133 mV, -72 mA (-82 avg), 36.0 C, 1433 mAh

<6>[ 508.573760] batt: 100%, 4133 mV, -66 mA (-48 avg), 35.8 C, 1432 mAh

<6>[ 558.725036] batt: 100%, 4133 mV, -65 mA (-69 avg), 35.7 C, 1430 mAh

<6>[ 584.724029] batt: 100%, 4128 mV, -70 mA (-21 avg), 35.5 C, 1430 mAh

<6>[ 634.886505] batt: 100%, 4128 mV, -71 mA (-68 avg), 35.2 C, 1428 mAh

<6>[ 680.858642] active wake lock ds2784-battery

<6>[ 680.908935] batt: 100%, 4138 mV, -4 mA (-66 avg), 35.0 C, 1427 mAh

<6>[ 731.073272] batt: 100%, 4133 mV, -102 mA (-67 avg), 34.7 C, 1425 mAh

<6>[ 781.229522] batt: 100%, 4133 mV, -73 mA (-67 avg), 34.5 C, 1425 mAh

<6>[ 801.490264] batt: 100%, 4123 mV, -5 mA (-43 avg), 34.2 C, 1425 mAh

<6>[ 851.626831] batt: 100%, 4128 mV, -69 mA (-67 avg), 34.0 C, 1424 mAh

<6>[ 896.734100] batt: 100%, 4128 mV, -109 mA (-64 avg), 33.7 C, 1422 mAh

<6>[ 931.772155] active wake lock ds2784-battery

<6>[ 931.783966] active wake lock ds2784-battery

<6>[ 931.830993] batt: 100%, 4128 mV, -64 mA (-34 avg), 33.5 C, 1422 mAh

<6>[ 981.989898] batt: 100%, 4128 mV, -71 mA (-66 avg), 33.3 C, 1420 mAh

<6>[ 1033.844207] batt: 100%, 4123 mV, -68 mA (-67 avg), 33.2 C, 1419 mAh

<6>[ 1083.995880] batt: 100%, 4118 mV, -65 mA (-70 avg), 33.0 C, 1419 mAh

<6>[ 1094.208160] active wake lock ds2784-battery

<6>[ 1094.234710] batt: 100%, 4133 mV, -7 mA (-6 avg), 32.7 C, 1417 mAh

<6>[ 1138.926757] active wake lock ds2784-battery

<6>[ 1138.984863] batt: 100%, 4128 mV, -69 mA (-68 avg), 32.3 C, 1416 mAh

<6>[ 1191.338592] batt: 100%, 4128 mV, -71 mA (-67 avg), 32.3 C, 1416 mAh

<6>[ 1241.502410] batt: 100%, 4123 mV, -64 mA (-68 avg), 32.1 C, 1414 mAh

<6>[ 1259.473632] batt: 100%, 4128 mV, -68 mA (-20 avg), 32.1 C, 1414 mAh

<6>[ 1309.611968] batt: 100%, 4123 mV, -71 mA (-66 avg), 31.8 C, 1412 mAh

<6>[ 1360.736022] batt: 100%, 4118 mV, -74 mA (-74 avg), 31.8 C, 1411 mAh

<6>[ 1406.333404] batt: 100%, 4123 mV, -78 mA (-65 avg), 31.6 C, 1409 mAh

<6>[ 1456.515350] batt: 100%, 4123 mV, -87 mA (-69 avg), 31.6 C, 1409 mAh

<6>[ 1506.674652] batt: 100%, 4118 mV, -68 mA (-69 avg), 31.6 C, 1408 mAh
[Nexus One Android Development] RogerPodacter:
I forgot you had the extended battery, so you don't want to set full40 to 1452mAh. That's exactly what you do not wanna do lol. So your full charge log there looks ok. What does it look like down low when its about to die? You want it to be approaching 0mAh at 3416 volt, to ensure you're getting the full range of your total capacity. Seems like you're close to that, no?
[Nexus One Android Development] RogerPodacter:
Yes that's what happens when you change the age, it re adjusts your percentage meter to match the new age you set. So at age 100% you get the max range of your 1452mAh capacity. If you set your age lower, you now only get less of your full range, and the meter updates accordingly. We know stock 94% age gives 1360mAh range. Less than that gives you even less range. I like keeping my age to 100% just So I get the max range and then see how much I can actually get out of it before it dies.
[Nexus One Android Development] EnhancerFIN:
Little update on the situation:

batt: 58%, 3698 mV, -138 mA (-72 avg), 26.0 C, 1481 mAh

batt: 58%, 3718 mV, -10 mA (-68 avg), 26.0 C, 1481 mAh

batt: 58%, 3718 mV, -132 mA (-11 avg), 26.0 C, 1480 mAh

batt: 58%, 3718 mV, -25 mA (-56 avg), 26.0 C, 1480 mAh

batt: 58%, 3718 mV, -25 mA (-19 avg), 26.0 C, 1478 mAh

batt: 58%, 3698 mV, -136 mA (-58 avg), 26.1 C, 1478 mAh

batt: 58%, 3698 mV, -23 mA (-13 avg), 26.0 C, 1478 mAh

batt: 57%, 3718 mV, -10 mA (-58 avg), 26.1 C, 1476 mAh

batt: 57%, 3718 mV, -10 mA (-11 avg), 26.0 C, 1476 mAh

batt: 57%, 3718 mV, -10 mA (-41 avg), 26.0 C, 1476 mAh

batt: 57%, 3718 mV, -10 mA (-11 avg), 26.0 C, 1475 mAh

batt: 57%, 3688 mV, -119 mA (-11 avg), 26.0 C, 1475 mAh

batt: 57%, 3698 mV, -10 mA (-11 avg), 25.8 C, 1472 mAh

batt: 57%, 3718 mV, -10 mA (-11 avg), 25.8 C, 1472 mAh

batt: 57%, 3703 mV, -96 mA (-11 avg), 25.8 C, 1472 mAh

batt: 57%, 3713 mV, -10 mA (-75 avg), 25.8 C, 1470 mAh

batt: 57%, 3718 mV, -12 mA (-10 avg), 25.8 C, 1470 mAh

batt: 57%, 3708 mV, -17 mA (-58 avg), 25.8 C, 1468 mAh

batt: 57%, 3698 mV, -38 mA (-11 avg), 25.8 C, 1468 mAh

batt: 57%, 3718 mV, -10 mA (-11 avg), 25.8 C, 1467 mAh

batt: 57%, 3713 mV, -10 mA (-11 avg), 25.8 C, 1467 mAh

batt: 57%, 3713 mV, -40 mA (-55 avg), 25.8 C, 1467 mAh

batt: 57%, 3713 mV, -12 mA (-10 avg), 25.8 C, 1465 mAh

batt: 57%, 3713 mV, -11 mA (-13 avg), 25.8 C, 1465 mAh

batt: 57%, 3713 mV, -139 mA (-10 avg), 25.8 C, 1465 mAh

batt: 57%, 3693 mV, -116 mA (-17 avg), 25.8 C, 1464 mAh

batt: 57%, 3713 mV, -76 mA (-10 avg), 25.8 C, 1462 mAh

batt: 57%, 3684 mV, -142 mA (-11 avg), 25.8 C, 1462 mAh

batt: 57%, 3708 mV, -10 mA (-10 avg), 25.8 C, 1462 mAh

batt: 57%, 3684 mV, -188 mA (-38 avg), 25.8 C, 1462 mAh

batt: 57%, 3688 mV, -10 mA (-10 avg), 25.7 C, 1460 mAh

batt: 57%, 3713 mV, -10 mA (-34 avg), 25.6 C, 1459 mAh

batt: 57%, 3703 mV, -41 mA (-56 avg), 25.7 C, 1459 mAh

batt: 57%, 3688 mV, -60 mA (-71 avg), 25.7 C, 1457 mAh

batt: 57%, 3684 mV, -182 mA (-10 avg), 25.8 C, 1457 mAh

batt: 57%, 3708 mV, -10 mA (-10 avg), 25.7 C, 1457 mAh

batt: 57%, 3708 mV, -11 mA (-11 avg), 25.7 C, 1457 mAh

batt: 57%, 3708 mV, -10 mA (-54 avg), 25.7 C, 1456 mAh

batt: 57%, 3708 mV, -10 mA (-56 avg), 25.7 C, 1456 mAh

No RP, I´m not with the extended battery, this is the original one from January, which has been unused for 2-3 months or so. These are the numbers at the moment, I haven´t charged the battery after last night.

I did adjust the AEvoltage to 3.2V, raised the full40 to 2750mAh (just to test something :D) age to 100 (which resetted to 94 after off-charge).

Just thinking, now that the mAh is way too big, to what I should adjust it (and how)? With this new AEvoltage setting 1500mAh is propably too low, if we have a goal to see 3201mV with 0mAh left in the battery.
[Nexus One Android Development] temasek:
Whats the code for setfull40 to 1500 and 1600?
[Nexus One Android Development] EnhancerFIN:
Now 3488mV left, and 1286mAh.

AEvoltage is set on 3201mV, so I should get the full40 value to be set somewhere round 1550mAh to get AEvoltage and under 20mAh at the same time.

I would also need help to set full40 to 1550mAh..
[Nexus One Android Development] temasek:
Roger or anyone?

Whats the set full40 to:-

- 1452

- 1500

- 1550

- 1600

Thanks alot!
[Nexus One Android Development] EnhancerFIN:
Figured it out myself.

These are used throught root explorer / setreg:

1452 (about):

0x6a 0d

0x6b 9d

1500:

0x6a 0e

0x6b 10

1550:

0x6a 0e

0x6b 88

1600:

0x6a 0f

0x6b 00
[Nexus One Android Development] temasek:
Great thanks.........I bad with figures! Trying out now!

EDIT:- Results

0x6a 0f <----------------- resulted in 1665 mAh in full40

What is 0x6b 00 ??

Thanks!
[Nexus One Android Development] EnhancerFIN:
You have to enter both of those, first the 0x6a xx and then 0x6b xx to get the desired full40 value.
[Nexus One Android Development] temasek:
Oh lol....my bad. :)
[Nexus One Android Development] pwig:
I have had something strange happen. I bought a new OEM battery and before I started to use it I drained the previous one down until my phone shut off, then turned it back on then let it shut off again. I then loaded the new battery and charged it overnight. After that my current widget stopped working and battery stays on 100% for a looong time then plummets around 25%. I bet that someone knows what this means but I can't figure it out. Any help?
[Nexus One Android Development] RogerPodacter:
Ah I got ya. Yeah that's a cool test to do. See how much mAh you end up burning thru by the time you hit shut down at 3.2volts, and whatever that total mAh you went thru could be your new full40 value to set to. That's kinda what learn cycle does except that only updates age, not full40.

I have a second new stock battery and was able to burn thru all 1452mAh before shut down with age set to 100, so I could technically raise my full40 as that's what dictates the "rated" capacity for these batteries.

Change full40 to 1500:

echo 6a 0e > setreg

echo 6b 10 > setreg

Change to 1600:

Echo 6a 0f > setreg

Echo 6b 00 > setreg

Guys that app is basically ready, its working and need testing soon if you want. One thing it have is the option to set your full40 value yourself just entering text into the box, as well as age. But if you wanna figure out the setreg commands in the mean time its on page 5 of that pdf I posted few pages back. Or maybe we can start some type of summary page of all commands till the app comes.
[Nexus One Android Development] RogerPodacter:
Sounds weird. Post your dumpreg file for us to see what's going on. Post the full40 file as well.
[Nexus One Android Development] RogerPodacter:
Nice you got it:-). Soon we can just enter into an app in human readable form and will convert and set for us automatically. Then it won't be a support page quite so much;-) .
[Nexus One Android Development] RogerPodacter:
Dude this is pretty cool. You essentially turned our stock battery into a 1550mAh battery. This is the type of stuff to test and figure out.

I have to wonder if that 1600mAh battery for sale is nothing more than our stock battery pack programmed with these numbers...
[Nexus One Android Development] pwig:
I am afraid that I have no idea how to do that. I have tried to follow this thread but a while back it went way over my head and I haven't caught up.
[Nexus One Android Development] RogerPodacter:
as long as you are using the latest pershoot kernel, go into /sys/devices/platform/ds2784-battery/ and find the dumpreg file, and attach that to your post. in that same location you will see a getFull40 file. post that one too.
[Nexus One Android Development] samarium:
permanent setage 100%

If your phone has /system/etc/init.d/20userinit that uses /data/local/userinit.sh then you to can use it to automate setage=100% on reboot. Cut and paste the following into a shell:

d=/data/local
u=$d/userinit.sh
setreg=/sys/devices/platform/ds2784-battery/setreg
mkdir -p $d
(echo "setreg=$setreg"; echo 'test -f $setreg && echo 14 80 > $setreg') >>$u

or add the following lines to /data/local/userinit.sh

setreg=/sys/devices/platform/ds2784-battery/setreg
test -f $setreg && echo 14 80 > $setreg
[Nexus One Android Development] EnhancerFIN:
If you don´t want to publish the link just yet, feel free to pm me, I would be thrilled to test that app specially since those hex-codes are NOT so comfortable :D
[Nexus One Android Development] temasek:
I would love to test the app too.

My own test. This morning just changed full40 to 1550, setage to 100. Its been 8.5 hrs at 1196mAh 3850mV. Battery showing 78%.
[Nexus One Android Development] mtw4991:
Let it die last nite, then charged 1-2% until it died again at whivh point i slammed the charger right when shutdown started and this morning statusreg showed 0x81 so i didnt hit learn mode, right? Also, age was set back to 94% and it only got to 1361mAh.getting confusing,lol.
[Nexus One Android Development] mtw4991:
How to set full40 from 1452 to 1550?
[Nexus One Android Development] temasek:
0x6a 0e

0x6b 88
[Nexus One Android Development] chowlala:
Ok. For some reason, I'm using Root Explorer.

1) I can't change my setreg no matter what I try.

2) I fubared my setAEvoltage somehow because I tried to mod it to 3201. But the values aren't right, even if I input the same values in, and check again, the number is always something else. Lol.

Help?
[Nexus One Android Development] difrnt:
I think I should set my age to 79, can someone confirm and please explain how?

http://pastebin.com/XNKbfM4s

I have a 3200 mAh Mugen battery.
[Nexus One Android Development] myakove:
I'm ready for testing
[Nexus One Android Development] RogerPodacter:
This is interesting, your full charge voltage hit 4.19, very nice.

The time out issue is a Google bug that we have to figure out how to fix soon, cause its gonna interfere with our learn cycle.

Your full point jumped up when you hit full charge. That's not necessarily a bad thing, just that you're testing that higher full40 value so this jump is expected. This was from a full drain to empty then charge back up? I'd do one more test and make sure you can use the full mAh range of your new full40. Then you're all set.
[Nexus One Android Development] RogerPodacter:
Right learn mode got missed. Your age got reset which is why it went back to 1361mAh at full charge. These stupid nexus batteries have this reset problem. We're gonna have to make the app memorize what we set, and check that on boot up and set it back each time.