[Galaxy S I9000 General] Stefanauss:
At least on the SGS, batterystats.bin seems to be nothing more than an structured index with every process that has ever been active reported onto it. I always thought the recalibration thing lies in the bumps more than the wipe.

If your battery is actually very mis-calibrated, you should see improvements straight away after 2 cycles.

The gallery bug we always talked about in YABD has all to do with wrong use of the yamaha sensor.

There is another issue with the gallery as well, that is: corrupted databases. A corrupted database could lead to FC's and/or heavy power use while gallery tries to sort databases out.

Up until now i could only noticed the sensor issue side of the things.

Two fix are avaible to address this issues.

DATABASES) A script in SGS Tools that recursively wipe databases, allowing the gallery to recreate them. I modified the script to avoid reboot, i'll try it.

SENSOR) The "fix" is actually more entirely replacing stock gallery with another app, Gallery3D, avaible in SGS Tools. Will try this first.

I disagree.

If the goal here would be to make all the data somewhat comparable, than you're right, we all should set some agreed settings at night and let the phone drain. It's the closest we can get to that.

It is also very likely that doing this will results in a little bit more identifiable idle drain issues. But after that? The rest of the day? Would be just a wait for the next night, as long as this thread is concerned? It's in your own words, if datas are not comparable, than they're useless.

To me this is wrong. Datas still are and still will be useful as long as they are comparable

in the same environment, that is for the same user

. The goal here is to maximize battery lives for our environments, not to have the same battery life for all of us. So it's true, you don't have to care about how bocbaken or me or anyone else use their phones, and i don't have to care about you. What we care about is everyone can isolate the single issues

they are experiencing

(can be done in real-life scenarios; does not need default idle-scenarios; does not need datas from everyone comes from the same scenario; definitely needs everyone can analyze their own datas) and solve them (can be done in real-life scenarios because solving a draining issue means gaining concrete battery-time over those real-life scenarios; does not need default idle-scenarios since the time gained by solving the issue will be visible no matter what; does not need datas from everyone comes from the same scenario because, again, an improvement will be visible regardless of the scenario; definitely needs everyone can analyze their own datas) and correctly reporting so others can analyze that particular issue in their own scenario (can be done in real-life scenarios; does not need default idle-scenarios; does not need datas from everyone comes from the same scenario; definitely needs everyone can analyze their own datas) and solve it too.

It takes just proper behaviour and proper reporting. A user should behave to keep the data coming out meaningful and analyzable by him/her, and then should report those datas correctly for them to be analyzable by others.