On Mon, 2019-06-03 at 17:15 +0200, Aleksander Morgado wrote:
> > To answer my own question to get current band ID you can use the
> > new (1.10) option:
> >
> > qmicli -p -d /dev/cdc-wdm0 --nas-get-rf-band-info
> > [/dev/cdc-wdm0] Successfully got RF band info
> > Radio Interface: 'lte'
> > Acti
It would, if possible, also be good to get the channel bandwidth. It’s the main
thing missing if you want to make WAN predictions. Not sure if it’s exposed by
QMI.
Cheers!
> On 3 Jun 2019, at 16:15, Aleksander Morgado wrote:
>
>> To answer my own question to get current band ID you can use th
> To answer my own question to get current band ID you can use the new (1.10)
> option:
>
> qmicli -p -d /dev/cdc-wdm0 --nas-get-rf-band-info
> [/dev/cdc-wdm0] Successfully got RF band info
> Radio Interface: 'lte'
> Active Band Class: 'eutran-20'
> Active Channel:'6400'
>
Please note that
To answer my own question to get current band ID you can use the new (1.10)
option:
qmicli -p -d /dev/cdc-wdm0 --nas-get-rf-band-info
[/dev/cdc-wdm0] Successfully got RF band info
Radio Interface: 'lte'
Active Band Class: 'eutran-20'
Active Channel:'6400'
> On 2 Ju
On Sun, 2019-05-19 at 09:42 +0200, Aleksander Morgado wrote:
> Hey Dan & all,
>
> The original fix I had for this issue was to always add raw commands
> to the head of the queue inside the serial port:
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/103
>
> The new f
