Comment 283 for bug 446146

In the end, the only way I got my E1692 to work reliably (every time) was to install the huawei mobile partner for linux that came with my key. After a reboot, it even started creating the ttyUSB* with the names that the huawei software expects (why a reboot to enable udev to follow NAME or SYMLINK rules, when RUN rules work without it?).
Too bad that the firmware update from Huawei for the E169* doesn't include the linux client. It has a working hwactivator, and a nice application - now all I need to do is to get it to use my speakers and mic to do voice calls, as it seems to support them.

So, the problem definitively isn't only kernel related. If it were, I'd have the same problem with all udev rules and all modeswitch softwares. What I've seen here instead is that modem_modeswitc never works (maybe because its udev rules are 60-*), usb-modeswitch works if I launch it by hand once and I have its rules as 10-*, and Huawei's software always works, and its rules are 10-*.