Created attachment 139095 [details]
Relevant part of the output of "ModemManager --filter-policy=STRICT --debug"
ModemManaged doesn't recognize my USB modem in strict filter mode.
Bus 002 Device 015: ID 19d2:0117 ZTE WCDMA Technologies MSM
Created attachment 139096 [details]
Relevant part of the output of "ModemManager --filter-policy=DEFAULT --debug"
The modem is recognized successfully in default filter mode.
Looks like we need to improve our strict filter somehow to catch this one. The current logic doesn't catch it because this device has only 3 TTYs, so just looking at the ports it exposes it could really be some other thing instead of a modem, so the strict filter ignores the device.
Could you get us more info from the device, e.g.:
$ sudo udevadm info -p /sys/class/tty/ttyUSB0
$ sudo udevadm info -p /sys/class/tty/ttyUSB1
$ sudo udevadm info -p /sys/class/tty/ttyUSB2
$ sudo udevadm info -p /sys/class/tty/ttyUSB0 --attribute-walk
$ sudo udevadm info -p /sys/class/tty/ttyUSB1 --attribute-walk
$ sudo udevadm info -p /sys/class/tty/ttyUSB2 --attribute-walk
$ sudo lsusb -v -d 19d2:0117
This kind of modem is a good example of a modem we expected to lose when using the strict mode.
Created attachment 139122 [details]
The attachment contains the output of these commands.
We actually had a bug in the way kernel drivers are matched. It's now fixed in MM git master and will be released with 1.8.