Hello Marcel,
I'll answer to two separates mails (of this thread) in one go:
On 10 Dec 2010, Marcel Holtmann wrote:
Kai Vehmanen wrote:
So whether this code is in oFono or elsewhere, does not matter
much (to overall power consumption). The main question is of course
how often the counters
Hello,
On 11 Dec 2010, Denis-Courmont Remi wrote:
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
Hi Remi,
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
Hi,
On 12/10/2010 12:53 AM, ext Marcel Holtmann wrote:
Hi Kai,
I share the concern for the IO/CPU cost, but I don't think it
matters much in which daemon this is done. Especially if some slack
is allowed for the timers (which should be the case), ofonod will be
scheduled when the CPU is
On Friday 10 December 2010 00:53:19 ext Marcel Holtmann, you wrote:
this is not really true. We can not wakeup ofonod every single second.
You might wanna start running powertop.
Yes we can. PulseAudio is going to be waking up the CPU 10 times per seconds
or more.
uhm, but I'm not
Hi Remi,
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
On Friday 10 December 2010 20:34:47 ext Marcel Holtmann, you wrote:
Hi Remi,
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
Hi,
On 09 Dec 2010, Marcel Holtmann wrote:
- lots of modems still handle all audio and PA will know nothing
about calls at all with these modems
actually Denis raised the same question, but then again this is for a
product specific requirement. And for that product we know that PA will
Hi Kai,
- lots of modems still handle all audio and PA will know nothing
about calls at all with these modems
actually Denis raised the same question, but then again this is for a
product specific requirement. And for that product we know that PA will
do the audio processing.
Hello Marcel,
On 09 Dec 2010, Marcel Holtmann wrote:
I share the concern for the IO/CPU cost, but I don't think it
matters much in which daemon this is done. Especially if some slack
is allowed for the timers (which should be the case), ofonod will be
scheduled when the CPU is anyways woken
Hi Kai,
I share the concern for the IO/CPU cost, but I don't think it
matters much in which daemon this is done. Especially if some slack
is allowed for the timers (which should be the case), ofonod will be
scheduled when the CPU is anyways woken up (e.g. modem/audio interrupts
wake up
Hi Aki,
Here a proposal for call counters implementation for keeping track
of the total incoming and outgoing call duration counters. Each
established call instance is contributing to either of the call
duration counters. The 2 counters are updated periodically when
there is an
Hi Marcel,
2010/12/8 Marcel Holtmann mar...@holtmann.org:
so Denis and I talked about this a little bit and I am not fine with
this at all.
Next time, can you invite me to join your little talk?
Lets take this one step and please explain to me what your requirements
and objectives are. I
Hi Aki,
so Denis and I talked about this a little bit and I am not fine with
this at all.
Next time, can you invite me to join your little talk?
because you are not sitting next to me right now ;)
Lets take this one step and please explain to me what your requirements
and objectives
Hi,
Because if your battery runs out in the middle of a 4 hour
conference
call, your timers are not updated and become worthless. Obviously,
this is a compromise between how reliable the counters are and how
many wakeups and IO we can bear.
I think this is not a good idea to have
Hi Andras,
Lets take this one step and please explain to me what your requirements
and objectives are. I also wanna see a top to bottom from UI down to the
modem usage of this API.
We need a UI showing total MO and MT call times. They also need to be
able to be reset, if the
Hi Marcel,
On 12/08/2010 06:12 PM, ext Marcel Holtmann wrote:
Hi Andras,
Lets take this one step and please explain to me what your requirements
and objectives are. I also wanna see a top to bottom from UI down to the
modem usage of this API.
We need a UI showing total MO
Hi,
On 08 Dec 2010, Marcel Holtmann wrote:
So I am actually thinking that doing that inside PulseAudio is a lot
more efficient solution.
The idea is that PA already runs in the user session and has to monitor
the uplink/downlink state (and additionally could monitor call states
as well if
Hi Andras,
The call counters are shown to the user when he or she opens up
an application/applet whatever UI component that is meant for
showing this information.
do we have a clear use case requirement from an UI point of view on how
this is expected to be working.
Hi Kai,
So I am actually thinking that doing that inside PulseAudio is a lot
more efficient solution.
The idea is that PA already runs in the user session and has to monitor
the uplink/downlink state (and additionally could monitor call states
as well if needed). So it knows when a
Hi Andras,
2010/11/22 Andras Domokos andras.domo...@nokia.com:
Here a proposal for call counters implementation for keeping track
of the total incoming and outgoing call duration counters. Each
established call instance is contributing to either of the call
duration counters. The 2 counters
Hi Aki,
On 12/07/2010 06:57 AM, Aki Niemi wrote:
Hi Andras,
2010/11/22 Andras Domokos andras.domo...@nokia.com:
Here a proposal for call counters implementation for keeping track
of the total incoming and outgoing call duration counters. Each
established call instance is contributing to
22 matches
Mail list logo
