Newer versions of udev will kill subprocesses started by rules if they are running 'too long'. I suspect this is happening in your case. Standard usb_modeswitch installations are working around this by using a systemd service file. This allows the detachment of the mode-switching process from udev s...

I have responded to the kernel bugzilla report. I'll see if I can pinpoint the reason why I introduced the "change" event in the udev rule.

Are you using a proper terminal program to issue AT commands?

I'm using "minicom" for this purpose.

Hmm, the network interface seems to be set up nicely during boot. Not sure what the problem is. It's correctly detected as a NCM device with Huawei-specific flavour, and a network interface is created (see last line in excerpt). [ 5.671792] huawei_cdc_ncm 3-2:1.1: MAC-Address: 0c:5b:8f:27:9a:64 [ 5....

It's possible that there is a NCM port exposed in that mode.

Can you post the output of "lsusb -v -d 12d1:1c05" here?

Be sure to paste the output between [code] tags to keep the formatting. The button in the editor shows '</>'.

Sorry, my mistake - that fix is not released yet. I've mixed this up with a different bug report. Anyway, the fix I linked will work if you don't want usb_modeswitch handle your device. It's not clear to me yet if you actually need usb_modeswitch to make your device work. If you don't, then the solu...

You can force a dhcp query on the interface manually.

"dhclient -4 usb0"

Can you tell which version of udev you are running on your system?

You can use the command "udevadm version".

If you are using the current or previous version of "usb-modeswitch-data", that issue should be resolved.

Other people have run into the same problem.
https://bugs.launchpad.net/ubuntu/+sour ... comments/5

I'm simply not able to remove this confirmation.

If your decision is not remembered then there is a bug in the system. This should be reported to the creators of LineageOS.

Some testing revealed that in the default "jimsh", the -dictionary parameter is not implemented for lsort.

I added a work-around where I first sort the list of files with one digit for the interface, then append the sorted list of ifaces with two digits and leave it at that ...

Exellent!

I'll include both fixes in the release version. I wouldn't have been able to test this as in my - rather extended - modem collection there is none with such an 'extreme' setup ...

I have prepared a new release of usb_modeswitch. Among some other fixes, I have changed the wrapper script to look for interfaces according to availability instead of fixed numbers. That means that the first interface may be ".2" or whatever the lowest available interface number is. If you like you ...

How could you find those 4 serial ports? I started off with usb-serial-for-android when I began work on PPP Widget 2. It's good for the initial learning but I ended up with implementing my own drivers. First thing to note is that "flow control" (the pseudo 'modem lines' provided by the respective i...

The issue is the available drivers in Android. In very early versions - like 2.x - the kernels had lots of drivers and you could post-load modules to add further drivers. Later, with 4.3 if I remember correctly, the module loading was disabled, for 'security reasons', and the modem drivers vanished ...