On Friday 10 December 2010 20:34:47 ext Marcel Holtmann, you wrote:
> > > Personally I think the every-10sec interval is too short.
> > > It's also highly system specific when wakeups start to get
> > > too costly, so picking up one value seems difficult.
> > My take here is that a granularity of 1 minute is enough.
> There are definitely call fares with sub-minute granularity. The minute
> is definitely INSUFFICIENT.
let me repeat my question here. Does this suppose to be represent spent
time on calls (what I called talk time) or actual billing minutes.
As said earlier, this is about the talk time. The scenario is a user ejects
the battery during an already long-standing call or gets the device to crash
or reset, gets billed, and comes and complain to its operator that (s)he gets
overcharged. The counters will be much more wrong if we do not flush them to
We do not need to "implement" the billing policy for that. This is only about
the total talk time.
If we talk about correct billing minutes then you are just opening
pandora's box. Since we don't know the billing. And difference between
air time, incoming/outgoing calls, multiparty calls, hold calls etc. and
their billing schemes make this just insane.
Sure. We don't wants this.
So what is the actual requirement here. So far ever single answer
not satisfying. And that is why I proposed to just make this count the
The requirement is that the user cannot deduct (much) talk time from the call
> > Doing this every 10 seconds and displaying it on a per
> > sounds insane to me.
> So I made a lengthy call to my mum this morning, using a desk phone. And
> it was showing minute:second, not just minutes. I have never seen a
> phone that does not show seconds and it would look pretty dumb to me.
You do realize that this is NOT the feature we are talking about here.
The actual display of the duration of a call is pretty simple and
currently easy to handle inside the UI. And that can be done up to the
millisecond display if you or your UI designer wants it.
The proposed call counters here are long term counters showing your
overall time. So showing minutes seems to be precise enough.
Showing minutes, as in flushing the counters every 60 seconds might work, but
I'd rather make this a configurable knob.
That said, I do believe the stored value has to be more precise than minutes.
Otherwise per call "error" may add up far too quickly.
Nokia Devices R&D, Maemo Software, Helsinki