On Thu, 2017-07-06 at 15:57 +0200, Tore Anderson wrote: > * Bjørn Mork > > > Having access to the full power of QMI is an advantage if you want > > to do > > "advanced" stuff like cell monitoring etc. But if you can run QMI > > over > > MBIM, and then there is absolutely no reason to use the more > > cumbersome > > configuration. MBIM is also the safer choice based on what most > > users > > (Windows) will use. > > This reminds me: is there a way to extract any debugging logs or info > from the network activity via any of these interfaces? I.e., > something à > la «[adb] logcat -b radio» on an Android device? As an example, I > enjoy > testing IPv6 while roaming. When it doesn't work I would like to be > able to inspect the exact 3GPP cause codes returned from the network > to > try and understand why.
Not really. If it's got a QCDM interface you can get the actual 3GPP protocol packets for the various logical channels. This is probably what logcat is doing to get data. For example: https://cgit.freedesktop.org/ModemManager/ModemManager/tree/libqcdm/src/log-items.h#n224 these are literally the protocol messages from over-the-air. Unfortunately we haven't RE-d many yet, especially the LTE ones. Otherwise, you might be able to get more detailed cause codes out of QMI for the call failure. But as we know, those aren't great. Dan > > Do you see 'qmi' in the MBIM service list?: > > Yup: > > $ mbimcli -p -d /dev/cdc-wdm0 --query-device-services > [/dev/cdc-wdm0] Device services retrieved: > Max DSS sessions: '0' > Services: (12) > > [...] > Service: 'qmi' > UUID: [d1a30bc2-f97a-6e43-bf65- > c7e24fb0f0d3]: > DSS payload: 0 > Max DSS instances: 0 > CIDs: msg (1) > > Tore > _______________________________________________ > ModemManager-devel mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel _______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
