nice geek words ndi trying to throw so much terms that no one will understand you anymore and hoping that i will say sorry your right, but your obviously are not.

You are right about the prediction on the battery graph, sometimes dropping in a straight line down. following this line would mean a battery die out within a few minutes. but fact is that when you keep using the n900 like this it in fact will die in a few minutes so the prediction is quite good! This does not mean that the battery is indeed emty. when you again fire up the n900 it will show a line up, because the battery will restore part of its power after th fast drain.

This does not mean that monitoring this behaviour cant be used to predict a remaining battery use time. And offcourse it wil flip from one hour to a few minutes. but using 100 % of the CPU power it will consume allot of power and it will die out very soon.

If you guys werent so stuburn and just write the code like i said you would see that it is quite good in predicting the remaining battery time.

You guys are really thinking to hard.

I could make this prediction myself if i knew how to write code for maemo.

You are talking about saving modes and processes and god knows what. The only thing you need to know is the use of current and prediction of mAh in a specific time frame. combined with avarages.

you use allot the battery time is very low. you stop using allot of battery the battery time will rise. whats wrong with it to show ups and downs in the battery time? thats exactly what I want..

When I fire up dosbox and i use it for an hour im sure the battery wil drain very fast. the remaining battery time program will show me this and will predict that the battery will be soon emty. when you stop dosbox. the time will rise extremely but its not far from realistic is it?

Its not that i dont understand what you are saying. when you put the n900 on the charger for 15 minutes it will show that the battery is full and it indeed will drain 5 times as fast until it reaches the real value. in this time the program i mention is not accurate. but HELL!!! the battery indicator isnt also! but after its on its normal value again you can see a pretty good prediction of when the battery will be emty.

One more example and then i stop this discussion because you guys are to geek to see this reality of the simpleness of this program.

Imagine, your n900 is in standby, the remaining battery program has calmed down and ahs a pretty nice prediction of whats going on. You need to make a trip for approx 10 hours. you wont be using your n900 allot but you wanna be sure you will manage through this time without the n900 dieing out. you look at the widget and see that it predicts a 15 hour time. so you know. that when you are not going to use dosbox or any other insane program the n900 will easily get through this trip.

Offcourse you cant charge up you n900 and then let the program say it has 48 hours left and it lets it keep that way. its an on the fly process of the time being usage that calculates a direct prediction of the usage at that moment. so playing a game and it with this drain it will last for 2 hours....

You are really missing my point on this guys! please be more open minded! and atleast give me a chance and try to write a code!

You could make the program even more complex by letting it have different modes like battery saving mode, full load mode and stuff. this way when in battery saving mode it can take earlier avarage data and use these. when in full load it wil give an on the fly prediction of that exact moment of usage.

Think with me guys, this would be something big if we could all contribute to this!