I've been getting a lot of reports of inaccurate totals this seems to be related to the fact that we drop any data consumed that is under 1KB / min
So if an app stays just under that they never get logged.
I think this was originally done to try and prevent calculation overflows.
But since demand is high enough I have to experiment with the feasibility of logging Bytes and no longer Kilo Bytes. If all goes well the next release should have more precision.
One thing that might need to change however is the activity indicator might need some threashold so that we don't have the connection indicator going when the data rate is below 1kbps for example. Otherwise we can have a lot of hilighting for bytes / sec data.
I've been getting a lot of reports of inaccurate totals this seems to be related to the fact that we drop any data consumed that is under 1KB / min
So if an app stays just under that they never get logged.
I think this was originally done to try and prevent calculation overflows.
But since demand is high enough I have to experiment with the feasibility of logging Bytes and no longer Kilo Bytes. If all goes well the next release should have more precision.
One thing that might need to change however is the activity indicator might need some threashold so that we don't have the connection indicator going when the data rate is below 1kbps for example. Otherwise we can have a lot of hilighting for bytes / sec data.