Hi,

I just realized that the interval that is set in the options is in fact the interval that Autodisconnect uses to check the connection. I was thinking, that Autodisconnect checks every minute and and looks at the <timepsan> for the amount of data. With actual behaviour the steps might get real big until it checks the next time.

An example:
time set to 5 Minutes, traffic set to 5kB.
Connection starts, some apps are downloading data, which takes 2 minutes and uses 100kB. After 3rd minute the data flow is as good as zero. In 5th minute autodisconnect checks the value the first time, counts an amount of 100kB and goes to background again. In 10th minute it checks the second time and looks at the interval minute 6 'til minute 10. The amount is less than 5kB so it will disconnect.

I'd find it much better if it would check the traffic every minute, calculating the traffic for the set timespan. With this setting in the example above it would first time check in minute 5 (~100kB), in minute 6 (~50kB) and in minute 7 (~0kB) and then closing the connection.

Reason for not setting the timespan to 1 minute: when browsing the web or even installing an update it happens often that there is no traffic for a minute or two. Having the connection getting closed immediately is not that funny.

Reason for not liking a that large interval: I use alarmed for hourly connection via gprs. Counting the additional online-time over one day might sum up to more than an hour. This is a really bad impact on battery life and might make the difference between having some battery life left in the evening or not.

It would be really nice if you could consider changing the behaviour.