Bug 100155

Summary: 4G-only modem gets reported "gsm-umts" capability
Product: ModemManager Reporter: Aleksander Morgado <aleksander>
Component: generalAssignee: ModemManager bug user <modemmanager>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: git master   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Aleksander Morgado 2017-03-11 09:40:43 UTC
The default logic to decide which are the current capabilities parses outputs of several commands, including +GCAP. The "+CGSM" reply in +GCAP is used to say a device is "gsm-umts", although this doesn't seem to be right; a 4G-only 3GPP modem will also reply +CGSM.


E.g.:

$ mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id '13d738ce72d62749f86308b7d620f063dd38bc47')
  -------------------------
  Hardware |   manufacturer: 'Telit'
           |          model: 'LE866-SV1'
           |       revision: '23.00.002 (M0A.00020)'
           |      supported: 'gsm-umts, lte'
           |        current: 'gsm-umts, lte'
           |   equipment id: '352613070042357'


Logs show how the AT+WS46? check does report 4G-only as supported *mode*, but still, we report 'gsm-umts' capability, which would apply only to 3GPP 2G/3G devices.

 (ttyUSB0): --> 'AT+GCAP<CR>'
 (ttyUSB0): <-- '<CR><LF>'
 (ttyUSB0): <-- '+GCAP'
 (ttyUSB0): <-- ': +CG'
 (ttyUSB0): <-- 'SM,+DS'
 (ttyUSB0): <-- ',+FCLA'
 (ttyUSB0): <-- 'SS,+MS'
 (ttyUSB0): <-- ',+ES'
 (ttyUSB0): <-- '<CR><LF>'
 (ttyUSB0): <-- '<CR><LF>OK<CR>'
 (ttyUSB0): <-- '<LF>'
 (ttyUSB0): --> 'AT+WS46=?<CR>'
 (ttyUSB0): <-- '<CR><LF>'
 (ttyUSB0): <-- '+WS46:'
 (ttyUSB0): <-- ' (28)'
 (ttyUSB0): <-- '<CR><LF>'
 (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
  loaded current capabilities: gsm-umts, lte
Comment 1 Aleksander Morgado 2017-03-12 19:53:29 UTC
*** Bug 100172 has been marked as a duplicate of this bug. ***
Comment 3 Aleksander Morgado 2017-03-24 20:37:32 UTC
Fixed in git master, mm-1-6 and mm-1-4.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.