On Sat, Jan 6, 2018 at 9:58 AM Aleksander Morgado
wrote:
> That idea looks good to me, yes. If that property is set, MM would
> just run one signal update query. You could reuse the same polling
> logic and just exit polling early as soon as the first successful poll
> happens.
> As for why QMI
>> > ModemManager currently relies on unsolicited MBIM_CID_SIGNAL_STATE
>> > notification to obtain signal quality updates, and it doesn't query
>> > the
>> > initial signal quality. I've observed that some MBIM modems issue a
>> > MBIM_CID_SIGNAL_STATE
>> > notification only when there is a notabl
On Fri, Jan 5, 2018 at 7:33 AM Dan Williams wrote:
> On Fri, 2018-01-05 at 06:57 +, Ben Chan wrote:
> > Hi Aleksander and Dan
> >
> > ModemManager currently relies on unsolicited MBIM_CID_SIGNAL_STATE
> > notification to obtain signal quality updates, and it doesn't query
> > the
> > initial
On Fri, 2018-01-05 at 06:57 +, Ben Chan wrote:
> Hi Aleksander and Dan
>
> ModemManager currently relies on unsolicited MBIM_CID_SIGNAL_STATE
> notification to obtain signal quality updates, and it doesn't query
> the
> initial signal quality. I've observed that some MBIM modems issue a
> MBIM
Hi Aleksander and Dan
ModemManager currently relies on unsolicited MBIM_CID_SIGNAL_STATE
notification to obtain signal quality updates, and it doesn't query the
initial signal quality. I've observed that some MBIM modems issue a
MBIM_CID_SIGNAL_STATE
notification only when there is a notable chang
