Notices

Thanks for the update.

So here is a plot of my log.

Hi, Saturn
nice graph. Just one quesion:"did You run any applications over the five days???"
My n800 is not going past 24hours.

1. battery-info is useless here for graph use. it seems to continually report the same percentage battery as when its first launched, if i use -d.

2. i suspect my issue with battery-graph and a battery-info generated file using battery-info's -p option was that battery-graph got confused by the data -p adds to the resulting file.

I've noticed that when the tablet is idle, the battery percentage reported by battery-info does not change. But as soon as I wake up the tablet and run anything, the next percentage will be much lower, especially if the tablet has been idle for a long time. I don't know whether the original battery-status program had the same behaviour, but I'm going to check.

Tso: Is this the issue that you are describing? If not, please send me the output file from battery-info by private message.

that would be issue 1, yes.

i basically spotted it as i have the habit of running the log right before i go to bed to see how much use it gets over a number of idle hours (in case there is something eating battery).

so far i have found that if the battery is in the 20% range, it cant survive a 8 hour idle stretch, no matter what the idle calculations say...

oh and no, battery-status do not have this idle report issue...

Sorry for the delay..

The plan was (as a first test) to not run anything but couldn't really stick to it.

Thus,
- the drops every ~12 hours is because of checking/reading mails each time lasting ~20 min.
- the big drop on the second day was after a more prolonged use.
- the last big drop happened by just enabling the wifi.

last, I've used the battery-status to record the data.

HIH

i was told on #maemo that having the xterm window open would not allow the system to idle correctly. so, how hard would it be to turn the logging into something that can allow that?

putting the & at the end of the command (i.e.
battery-status -d 10 > /media/mmc1/battery.log &) sends it to the background and you can close the terminal safely without killing the logging.

did I misunderstood you? isn't this what you're asking?

iirc, that will not work as the terminal will still own the process...

i also tried launching it like that via personal-launcher and while battery-status stayed in memory, nothing was entered into the log file.

Run it from screen.