[Nexus One Android Development] theloginwithnoname:
Correct and Correct, sir. I have a sneeky feeling I did, as I got the dreaded jump this afternoon. I have included the complete log until I had to use the phone/got bored (I could have gone all the way up to 1400 but then likely I would have had power off at 10%). Log from today's on-charge (pertenent bits in bold, italics) - part 1, the jump:

15527 4162 99 118 1219200 296 90 usb slow 0x07 0
15578 4162 81 113 1219200 296 90 usb slow 0x07 0
15628 4162 108 66 1220800 296 90 ac fast 0x07 0
15678 4162 102 104 1222400 296 90 ac fast 0x07 0
15729 4167 117 113 1224000 293 90 ac fast 0x07 0
15779 4167 111 115 1225600 292 90 ac fast 0x07 0
15833 4162 113 86 1227200 296 90 ac fast 0x07 0
15883 4167 108 110 1228800 295 90 ac fast 0x07 0
15936 4167 106 107 1230400 293 91 ac fast 0x07 0
15986 4172 104 105 1232000 291 91 ac fast 0x07 0
16037 4172 101 103 1233600 291 91 ac fast 0x07 0
16087 4172 100 87 1235200 291 91 ac fast 0x07 0
16137 4162 98 94 1236800 290 91 ac fast 0x07 0
16187 4172 96 91 1236800 288 91 ac fast 0x07 0
16243 4172 93 89 1236800 288 91 ac fast 0x07 0
16296 4172 90 91 1238400 288 91 ac fast 0x07 0
16346 4172 88 89 1240000 288 91 ac fast 0x07 0
16397 4172 86 87 1241600 287 91 ac fast 0x07 0
[I][B] 16447 4172 84 85 1243200 286 91 ac fast 0x07 0
16497 4172 83 83 1243200 286 92 ac fast 0x07 0
16547 4177 81 81 1244800 286 92 ac fast 0x07 0
16610 4177 78 78 1353600 286 100 ac fast 0x87 0
16660 4177 74 73 1355200 286 100 ac fast 0x87 0
[/B] [/I] 16710 4177 75 76 1356800 285 100 ac fast 0x87 0

part 2, the long, drawn-out wait for 1400:

17019 4177 64 45 1361600 283 100 ac fast 0x87 0
17069 4177 65 61 1363200 282 100 ac fast 0x87 0
17119 4177 63 64 1363200 281 100 ac fast 0x87 0
17173 4172 42 36 1364800 288 100 ac fast 0x87 0
17224 4177 47 43 1366400 293 100 ac fast 0x87 0
[B][I] 17276 4172 37 34 1366400 296 100 ac fast 0x87 0
[/I] [/B] 17326 4172 44 36 1368000 301 100 ac fast 0x87 0
17377 4177 41 43 1369600 301 100 ac fast 0x87 0
17427 4172 41 43 1369600 306 100 ac fast 0x87 0
[B][I] 17480 4172 40 2 1371200 311 100 ac fast 0x87 0
[/I] [/B] 17530 4172 43 40 1371200 312 100 ac fast 0x87 0
17580 4172 40 41 1371200 313 100 ac fast 0x87 0
17630 4177 41 41 1372800 316 100 ac fast 0x87 0
17680 4177 55 40 1372800 317 100 ac fast 0x87 0
17730 4177 53 48 1374400 313 100 ac fast 0x87 0
17781 4177 54 51 1374400 311 100 ac fast 0x87 0
17831 4177 54 54 1374400 308 100 ac fast 0x87 0
17881 4177 50 53 1374400 308 100 ac fast 0x87 0
17931 4177 30 27 1376000 310 100 ac fast 0x87 0
[B][I] 17981 4177 35 33 1377600 316 100 ac fast 0x87 0
18043 4177 34 32 1377600 318 100 ac fast 0x87 0
18096 4177 31 32 1379200 321 100 ac fast 0x87 0
18146 4177 26 27 1379200 321 100 ac fast 0x87 0
18197 4177 22 20 1379200 322 100 ac fast 0x87 0
[/I] [/B] 18261 4177 46 49 1379200 318 100 ac fast 0x87 0
18311 4177 48 44 1380800 316 100 ac fast 0x87 0
18364 4182 47 43 1380800 313 100 ac fast 0x87 0
18424 4177 46 45 1380800 313 100 ac fast 0x87 0
18476 4182 45 45 1382400 312 100 ac fast 0x87 0
18526 4182 44 22 1382400 311 100 ac fast 0x87 0
18577 4182 43 43 1382400 308 100 ac fast 0x87 0
18640 4182 40 22 1382400 307 100 ac fast 0x87 0
[B][I] 18697 4177 0 26 1382400 306 100 ac fast 0x87 0
[/I] [/B] 18747 4182 41 31 1382400 306 100 ac fast 0x87 0
18810 4182 40 40 1384000 303 100 ac fast 0x87 0
[B][I] 18860 4177 2 22 1384000 303 100 ac fast 0x87 0
18911 4182 40 22 1385600 303 100 ac fast 0x87 0
18964 4182 38 34 1385600 301 100 ac fast 0x87 0
19025 4182 37 34 1385600 301 100 ac fast 0x87 0
19077 4182 37 19 1385600 298 100 ac fast 0x87 0
19128 4182 36 36 1385600 298 100 ac fast 0x87 0
[/I] [/B]

note: the smaller values (likely the ones in bold, italic) were always whilst I had the screen on, though they never went below. The larger (~40) were when screen off and I couldn't see them hit < 10, 20, or even 30 whilst screen off.

We could perhaps probe to see if screen is on or off, and adjust threshold accordingly. However I think the effort should go towards the recalibrating work so I won't!

Would be interesting to see if there is any more useable charge when "overcharging" our batteries - i.e. do we get more life out of them even if they will die earlier, or will the life be exactly the same and more predictable if we charge til battery tells us it's full - discuss ;)

I may stick the phone back on charge and monitor to see what the absolute values are. If I do I'll report back.

Failing that, I'm moving on to outputting the additional values (that me and RP have pseudo-coded) into the battery log.