Page 1 of 1

USB driver lost

Posted: Fri Mar 06, 2020 4:11 pm
by opkgmake
please help me to fix this

dongle model:-Huawei me909s-821 LTE
I try use that dongle in:-Xiaomi sagit AOSP10


usb log:-

2020年3月6日 下午10:06:16

Device manufacturer string: Xiaomi
Total RAM: 6000 MB. Available RAM: 2411 MB

Start manual search for USB devices
on kernel level ...
No known modem found in install mode
Start search for USB devices
visible on Android OS level ...
Looking at device: /dev/bus/usb/001/002 ...
Check device 12d1:15c1, interface 2, might be a modem
Request permission from system to handle device ...
Found possible 3G USB device 12d1:15c1
System has permitted USB device handling
New device on /dev/bus/usb/001/002
Class of interface 0 is 0xFF
Looking at USB device 12d1:15c1 with class 255
Device top dir: /sys/bus/usb/devices/1-1, active cfg: 2
Active configuration ID: 2
Device layout (config 2) - cl:00 sc:00 pr:ff
if:0 as:0 - cl:02 sc:06 pr:00 - ir:82
if:1 as:0 - cl:0a sc:06 pr:00 - bi:81 bo:01
if:2 as:0 - cl:ff sc:06 pr:10 - ir:84 bi:83 bo:02
if:3 as:0 - cl:ff sc:06 pr:13 - bi:85 bo:03
if:4 as:0 - cl:ff sc:06 pr:12 - bi:86 bo:04
if:5 as:0 - cl:ff sc:06 pr:06 - bi:87 bo:05
if:6 as:0 - cl:ff sc:06 pr:1b - bi:88 bo:06

Found 5 serial ports
Trying to switch mode of USB device 12d1:15c1 ...
Device info:
VID= 12d1
PID= 15c1
Manufact.= Huawei Technologies Co., Ltd.
Product= HUAWEI Mobile V7R11
Found matching configuration in collection: 12d1.15c1
Wait for 200 ms
Setting configuration to 0
Start search for USB devices
visible on Android OS level ...
Looking at device: /dev/bus/usb/001/002 ...
Check device 12d1:15c1, interface 2, might be a modem
Request permission from system to handle device ...
Found possible 3G USB device 12d1:15c1
System has permitted USB device handling
New device on /dev/bus/usb/001/002
Class of interface 0 is 0xFF
Looking at USB device 12d1:15c1 with class 255
Can't read bConfigurationValue, value:
Device top dir: /sys/bus/usb/devices/1-1, active cfg: 1
Active configuration ID: 1
Device layout (config 1) - cl:00 sc:00 pr:ff
if:0 as:0 - cl:ff sc:06 pr:10 - ir:82 bi:81 bo:01
if:1 as:0 - cl:ff sc:06 pr:13 - bi:83 bo:02
if:2 as:0 - cl:ff sc:06 pr:12 - bi:84 bo:03
if:3 as:0 - cl:ff sc:06 pr:16 - ir:86
if:3 as:1 - cl:ff sc:06 pr:16 - ir:86 bi:85 bo:04
if:4 as:0 - cl:ff sc:06 pr:06 - bi:87 bo:05
if:5 as:0 - cl:ff sc:06 pr:1b - bi:88 bo:06

Found 6 serial ports
No dedicated modem port found
The number of undefined serial ports is 6;
if automatic pick doesn't work, try others
See config option "Manual port selection"
Manual port index set to 0, trying to start there
Port 0 has type SER_DIAG
Port 1 has type SER_DIAG
Port 2 has type SER_DIAG
Port 3 has type SER_DIAG
Port 4 has type SER_DIAG
Port 5 has type SER_DIAG
USB driver lost!
Aborting modem initialization

I am using a USB pcie adapter board with a 3.6v voltage requirement, and I am waiting for the arrival of USB hub power.

Re: USB driver lost

Posted: Sat Mar 07, 2020 3:32 am
by LOM
opkgmake wrote:
Fri Mar 06, 2020 4:11 pm

I am using a USB pcie adapter board with a 3.6v voltage requirement, and I am waiting for the arrival of USB hub power.
Then lets wait for the arrival of the powered USB hub before we continue troubleshooting.

Re: USB driver lost

Posted: Sat Mar 07, 2020 4:41 am
by opkgmake
Android#ls /dev
ttyUSB0 ttyUSB1 ttyUSB2 ttyUSB3 ttyUSB4
Android#microcom /dev/ttyUSB0
AT
OK
I found the virtual serial port in the / dev directory, but ppp widget3 seems to be / dev / ttyACM0

Thanks a lot!

Re: USB driver lost

Posted: Mon May 18, 2020 7:25 pm
by Josh
There is a misunderstanding.

PPP Widget does not do USB driving on the kernel level because Google banned kernel module loading.
Instead it tries to do all USB traffic and protocols the Android way, with the Android USB API or a bug-free clone of it.

Bottom line: you will hardly see kernel devices if there aren't kernel-level USB drivers for your modem available - which in fact are unwanted for PPP Widget to work.