Providing some options for periods

[GoogleCodeExporter]

Hey!

I just discovered this project and loved the idea. I have some 
suggestions, though.

From the screenshots I see, you're assuming the billing date is the first 
date of a month. What if, for example my operator accounts my billing 
period from 17th day of current month to 16th day of next month? Or even 
what if I have a weekly subscription (even starting counting on Xth day of 
week) instead of an monthly (that's my status)?

I hope you get my point, providing some periodical options would be great.

Original issue reported on code.google.com by gece.bekcisi@uniturk.net on 16 Jan 2009 at 9:40

[GoogleCodeExporter]

my billing is not the 1st day too...
please add this option! :D

great program BTW!

PS maybe a bw meter too? like mconnection

Original comment by diazl...@gmail.com on 25 Jan 2009 at 5:07

[GoogleCodeExporter]

Only just spotted this request!

I've done the first bit to change the billing day, that's in new 0.1.3 release. 
Let 
me know if there any problems. Don't forget to reset the packet data counter on 
the 
billing day.

I'll look into adding a weekly option.

Original comment by hugovk@gmail.com on 5 Mar 2009 at 4:33

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Great enhancement! Thanks a lot.

Would providing an "advanced" option in which we can select a custom period 
measued 
in days and a custom counting day; instead of a simple "weekly" option?

I also agree with "bw meter" idea, it'll rock then I guess.

I'd go even further and make another suggestion: how about keeping tracks of 
data 
usage from logs/or realtime system monitoring, instead of global packet data 
counter; and so providing user an option to choose different quotas and 
schedules 
for each "access point" user may want be notified about?

Original comment by gece.bekcisi@uniturk.net on 5 Mar 2009 at 4:57

[GoogleCodeExporter]

> Don't forget to reset the packet data counter on the 
> billing day.

So i have to reset the counter manually every month ?

Original comment by diazl...@gmail.com on 12 Mar 2009 at 1:53

[GoogleCodeExporter]

Please can you explain the "bw meter" to me in some more detail in a new issue?

> I'd go even further and make another suggestion: how about keeping tracks of 
data 
usage from logs/or realtime system monitoring, instead of global packet data 
counter; and so providing user an option to choose different quotas and 
schedules 
for each "access point" user may want be notified about?

That would be good, but I want to keep this application very simple and light 
weight. Keeping track of all the different access points and how much each one 
transfers would involve quite a lot of extra monitoring, and need something to 
always be running, and with that would have the problems of autostarting. At 
the 
moment it's just reading a single value that the phone is already calculating 
and 
updating, so doesn't need to be always running/ 

> So i have to reset the counter manually every month ?

Yes that's right. It's just reading the value from that Logs application, so 
you 
need to clear it in there.

Original comment by hugovk@gmail.com on 12 Mar 2009 at 3:08

[GoogleCodeExporter]

Issue 2 created for "bw meter" idea.

I understand that you want to keep this application very simple and light 
weight; 
but you can have an option to reveal advanced features to user.

And also IMHO resetting the packet data counter manually kills all the concept. 
If I 
have to do resetting the counter manually at each billing day; I don't really 
need a 
"dataquota" application since it's not providing any enough enhancements over 
the 
inbuilt packet data counter itself and becomes a bit redundant.

-----

"Keeping track of all the different access points and how much each one 
transfers 
would involve quite a lot of extra monitoring" can be done in the way described 
below which I think will work perfectly:

(1) Analyse the system log:
<1.1.1> "periodically" (for example, everyday at 04:00 am; since log might be 
huge 
(mine is set to keep track of the last 30 days' events, or 1000 entries; which 
comes 
first) and the analysing process may interrupt user experience since it'll take 
lot 
of cpu time) 
<1.1.2> or "on user request" (like when user executes the application and 
selects 
"refresh data" or when user executes the application, application can ask the 
user 
about "refreshing data") 
<1.2> for the needed time period (since the start of this week or month etc) 
<1.3> for the selected access points' events (would be great if I could select 
which 
AP I'd like to monitor and not)

(2) Save the:
<2.1> total amount of used data (again for the needed time period and which is 
calculated from analysing system log) 
<2.2> the last (date-wise) entry analysed (to stop at that entry next time 
analysing 
the log, which will save needed cpu time)

(3) Monitoring would be kept on while the application is working

(4) At exit the application should save all the values it's monitoring

Please think about these ideas...

Original comment by gece.bekcisi@uniturk.net on 12 Mar 2009 at 11:27

[GoogleCodeExporter]

I second uniturk:
in Italy there are 3 kinds of data plans
- monthly (always the same day of the month, say the 14th)
- 30 days (they last exactly 30 days, so the "billing" day changes almost every 
month)
- weekly
I'm implicitly suggesting to simply let the user specify a plan length in # of 
days.

About the advanced features he suggests: hugovk, if you ever decide to try a go 
on 
them don't worry about the autostarting (or just consider it low priority), 
there are 
already user apps that do that. It is true that it would be quite a lot of code 
to 
write, with all that bookkeeping. But yes, not having to remember to reset the 
log 
counter would be lovely :) (and there are possible use cases - in Italy - 
already in 
which it makes sense to distinguish between different access points)

Original comment by marklo...@gmail.com on 2 Jul 2009 at 11:52

[GoogleCodeExporter]

Oh, I forgot to say I've implemented part of this -- you can now change the 
billing 
day.

Original comment by hugovk@gmail.com on 28 Sep 2009 at 8:16

[GoogleCodeExporter]

I agree with others: automatic reset counter on billing day should be 
implement. User
shouldn't need to remember to reset counter manually.

Original comment by windzi...@gmail.com on 14 Oct 2009 at 9:55

[GoogleCodeExporter]

I have a contract with 50mb/day, is it possibile to reset the counter every day?
thank you

Original comment by davfe...@gmail.com on 22 Oct 2009 at 7:05

[GoogleCodeExporter]

I have a day by day counter limit, too. Can you give us the possibility to reset
counters evry day (automatically)?

Original comment by srep...@gmail.com on 29 Apr 2010 at 9:49

[GoogleCodeExporter]

I like your project, but I must say I absolutely agree with Comment 6 by 
gecebekcisi.uniturk, Mar 12, 2009, this is exactly what I expect. I never want 
to reset general data counter, it is something like log of a mobile phone life 
for me.

Original comment by pavol...@gmail.com on 11 Aug 2010 at 8:01

[GoogleCodeExporter]

My billing unit is 100 KB. And my consumption is twice as high. Is there a 
solution for this?

Original comment by FZObe...@gmail.com on 12 Aug 2010 at 7:58

[GoogleCodeExporter]

What's the current progress Hugo?

Original comment by gece.bekcisi@uniturk.net on 2 Nov 2010 at 4:13

[GoogleCodeExporter]

No progress to report. I've not had any time to spend on this especially as I'm 
not using it myself any more.

Original comment by hugovk@gmail.com on 22 Nov 2010 at 9:35

[GoogleCodeExporter]

Just when I'm planning to start using an app I see this, "I've not had any time 
to spend on this especially as I'm not using it myself any more" :(

Original comment by werds...@gmail.com on 14 Dec 2010 at 12:34

[GoogleCodeExporter]

For those of you that have a per day quota, you can now change from a monthly 
to daily quota. For details, see 
http://code.google.com/p/dataquota/issues/detail?id=20

Original comment by hugovk@gmail.com on 6 Jun 2011 at 7:53