Hi,
On 08 Feb 2011, Zabaluev Mikhail (Nokia-MS/Helsinki) wrote:
>> I would use fdatasync().
>
> What about ensuring that file metadata are synced as well (e.g. the
> file itself cannot be lost on the filesystem)?
Rémi already responded about fdatasync semantics, but I do
wonder a bit about direc
Hi,
On 03 Feb 2011, Denis Kenzior wrote:
>> So handling this might still be useful even if reliable re-enabling
>> of messages would not work reliably (assumption being that recycling
>> and reregistering will reliably reenable message delivery). Or do you
>
> Last I checked 27.005 mentions nothin
Hi Denis,
On 02 Feb 2011, Denis Kenzior wrote:
> Another fun fact about CMT delivery is that if you do not ack in a
> 'reasonable' amount of time, the modem _silently_ turns off SMS
> delivery. So putting acks over D-Bus is simply a bad idea.
ack, very much agreed. And now that I realized RX fra
Hello Marcel,
On 02 Feb 2011, Marcel Holtmann wrote:
>> - This relates to another TODO -> persistant storage of RX-TPDUs
>>for incomplete messages. If we've acked a TPDU to network,
>>we must have stored it to persistant storage.
>
> Where are we not doing this. We do store t
Hi,
here's a few comments about the SMS delivery part. These apply to
the history plugin interface as well, so not specifically only about
this patchset.
On 01 Feb 2011, Marcel Holtmann wrote:
> + void MessageReceived(dict info)
> +
> + Incoming text message.
> +
Hi,
On 31 Jan 2011, Sjur Brændeland wrote:
>> Sjur Brændeland wrote:
>>> + array{dict,array{dict}} QosFilters [readonly, optional]
>>> +
>>> + Information about the QoSes and associated Packet
>>> + Filters for the Default PDN and it's dedicated
> Arun Ravindran wrote:
Hi,
On 27 Jan 2011, Marcel Holtmann wrote:
>> +array{dict,array{dict}} QosFilters [readonly, optional]
>> +
>> +Information about the QoSes and associated Packet
>> +Filters for the Default PDN and it's dedicated bearers.
>> +
Hi,
On 14 Jan 2011, Marcel Holtmann wrote:
>> #include
>> @@ -700,6 +701,7 @@ static void ifx_post_sim(struct ofono_modem
>*modem)
>>
>> DBG("%p", modem);
>>
>> +ofono_ctm_create(modem, 0, "ifxmodem", data->dlcs[AUX_DLC]);
>
> so no emergency calls with CTM are possible? Or do we have
Hi,
On 13 Jan 2011, jeevaka.badrap...@elektrobit.com wrote:
>> CTM is a property of a voice call. And this makes sense as
>> TTY calls _are_ essentially voice calls, with just a bit
>> indicating to the network that the voice circuit should be
>> free of any transcoder/audioprocessing/etc that is
Hello Marcel,
On 12 Jan 2011, Marcel Holtmann wrote:
> Are we expecting that all modems will just establish a normal voice
> call
> and only later on signal that it is a TTY call? Any input from
> different
> vendors other than IFX. What about STE, ISI?
not later, but as part of standard call set
Hi,
On 05 Jan 2011, Marcel Holtmann wrote:
>> our case, we are receiving unsolicited AT commands "CTM CALL" when the
>> remote party has accepted the call as a TTY enabled device and "NO CTM
>> CALL" when the remote has accepted the call but his device is not TTY
>> enabled.
>
> I think we need a
Hi,
On 22 Dec 2010, Predon, Frederic wrote:
> 1) First, it might a good proposal to merge the TextTelephony and the
> AudioSettings atoms. Enabling and disabling CTM on a platform require
> to configure the audio settings on the modem side (audio routing
> parameters changes). Today, in my patches
Hi,
On 10 Jan 2010, Rémi Denis-Courmont wrote:
> Currently, the call direction can only be inferred from the signals.
> This adds a property to keep it visible also from GetCalls().
just adding one more do { ++votes; } while(0) for this.
telepathy-ring needs this as well when it is (re)started an
Hi,
On 16 Dec 2010, Nicola Mfb wrote:
> While testing an e169 huawei card I was able to make voice calls and
> hear something with aplay and /dev/ttyUSB1.
> On the openmoko/freerunner is a matter of HW switches, on the n900
> IIRC is done with pulseaudio.
> I guess that voice call audio routing is
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 a
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 count
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 anyway
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
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 wel
Hi,
On 23 Nov 2010, Lucas De Marchi wrote:
> +Interfaceorg.ofono.TextTelephony
[...]
> +Properties boolean Powered [readwrite]
> +
> + This property will enable or disable the text
> + telephony feature in the modem.
> +
> + Text te
Hi,
On 01 Oct 2010, Kai Vehmanen wrote:
>Subject: [PATCH 2/2] n900: Enable audio settings atom
> plugins/n900.c |2 ++
FYI, I've now added a minimal test/example application, cmtspeech_test_ofono,
to upstream libcmtspeechdata repository [1]. The app uses oFono (and the new
audio settings atom
21 matches
Mail list logo
