aboutsummaryrefslogtreecommitdiff
path: root/docs/reference/api/ModemManager-sections.txt
diff options
context:
space:
mode:
authorAleksander Morgado <aleksander@lanedo.com>2013-08-21 13:27:41 +0200
committerAleksander Morgado <aleksander@lanedo.com>2013-08-21 13:29:50 +0200
commit7e9ae215509c7e55ca128023100258d664894c32 (patch)
tree8b5119a19df2d252840bd6f5d19c7e503107b787 /docs/reference/api/ModemManager-sections.txt
parent75aa4a0df708a981a5d2b1dafc8912dfd3af78e4 (diff)
broadband-modem-qmi: avoid processing invalid TLVs in GetSignalStrength response
E.g. in the GetSignalStrength output we get EV-DO-only TLVs, even if EV-DO is not the current access technology, what ends up generating the following: $ sudo mmcli -m 0 --signal-get /org/freedesktop/ModemManager1/Modem/0 ------------------------- Refresh rate: '5' seconds ------------------------- EV-DO | RSSI: '0.00' dBm | EcIo: '0.00' dBm | SINR: '9.00' dBm | Io: '-106.00' dB ------------------------- UMTS | RSSI: '94.00' dBm | EcIo: '-6.00' dBm Instead, we will now assume that the RSSI list always contains the valid access technologies being reported, and use that list to decide whether we process some of the per-technology TLVs. We now end up getting: $ sudo mmcli -m 0 --signal-get /org/freedesktop/ModemManager1/Modem/0 ------------------------- Refresh rate: '5' seconds ------------------------- UMTS | RSSI: '94.00' dBm | EcIo: '-8.00' dBm
Diffstat (limited to 'docs/reference/api/ModemManager-sections.txt')
0 files changed, 0 insertions, 0 deletions