[sinnedone]

Hello all. I hope I can get some help with a problem I have.

I have an android 4.4 car radio unithttp://forum.xda-developers.com/android ... d-t2865525 Running this rom http://forum.xda-developers.com/android ... d-t3266694

This is the modem I am trying to use http://www.netgear.com/service-provider ... ar_organic

The android radio does support certain usb modems natively like Huawei E303. The netgear 340u does not get detected and tried all versions of PPP widget but no modem is found.

THe rom I am currently using has usb_modeswitch v2.2.6 and per the post here http://www.draisberghof.de/usb_modeswit ... 40u#p16281 It says ppp widget added support for my modem "sierra ac340u" but requires usb_modeswitch v2.3.0.



Can I follow these http://www.draisberghof.de/usb_modeswitch/#install instructions to update the usb_modeswitch version on my android head unit or is the process different?


PLease help as my knowledge on this is very limited.

THank you

Sep 19, 2016 9:47:12 AM

Device manufacturer string: Newsmy
Start search for USB devices
visible on Android OS level ...
Check device 0403:6015, might be a modem
Check device 1199:9051, might be a modem
Found possible 3G USB device 1199:9051
New device on /dev/bus/usb/001/003
Class of interface 0 is 0xFF
Looking at USB device 1199:9051 with class 255
Device top dir: /sys/bus/usb/devices/1-1, active cfg: 2
Device layout (config 2) - cl:00 sc:00 pr:00
if:2 as:0 - cl:ff sc:00 pr:00 - ir:82 bi:81 bo:01
if:3 as:0 - cl:ff sc:00 pr:00 - ir:84 bi:83 bo:02
if:8 as:0 - cl:ff sc:ff pr:ff - ir:86 bi:85 bo:03
The table says these values define a QMI port
if:9 as:0 - cl:08 sc:06 pr:50 - bi:87 bo:04
if:0 as:0 - cl:ff sc:ff pr:ff - bi:88 bo:05
if:12 as:0 - cl:02 sc:0e pr:00 - ir:82
if:13 as:0 - cl:0a sc:00 pr:02 -
if:13 as:1 - cl:0a sc:00 pr:02 - bi:81 bo:01

Opening port type QMI
Error when opening modem port: Could not claim control interface
Aborting modem initialization

Sep 19, 2016 10:29:49 AM

Device manufacturer string: Newsmy
New device on /dev/bus/usb/001/002
Class of interface 0 is 0x08
Looking at USB device 1199:0fff with class 8
Device top dir: /sys/bus/usb/devices/1-1, active cfg: 1
Device layout (config 1) - cl:00 sc:00 pr:00
if:9 as:0 - cl:08 sc:06 pr:50 - bi:81 bo:01
if:12 as:0 - cl:02 sc:0e pr:00 - ir:82
if:13 as:0 - cl:0a sc:00 pr:02 -
if:13 as:1 - cl:0a sc:00 pr:02 - bi:81 bo:01

New device on /dev/bus/usb/001/003
Class of interface 0 is 0xFF
Looking at USB device 1199:9051 with class 255
Device top dir: /sys/bus/usb/devices/1-1, active cfg: 2
Device layout (config 2) - cl:00 sc:00 pr:00
if:2 as:0 - cl:ff sc:00 pr:00 - ir:82 bi:81 bo:01
if:3 as:0 - cl:ff sc:00 pr:00 - ir:84 bi:83 bo:02
if:8 as:0 - cl:ff sc:ff pr:ff - ir:86 bi:85 bo:03
The table says these values define a QMI port
if:9 as:0 - cl:08 sc:06 pr:50 - bi:87 bo:04
if:0 as:0 - cl:ff sc:ff pr:ff - bi:88 bo:05
if:12 as:0 - cl:02 sc:0e pr:00 - ir:82
if:13 as:0 - cl:0a sc:00 pr:02 -
if:13 as:1 - cl:0a sc:00 pr:02 - bi:81 bo:01

Opening port type QMI
Error when opening modem port: Could not claim control interface
Aborting modem initialization

[Josh]

THe rom I am currently using has usb_modeswitch v2.2.6 and per the post here http://www.draisberghof.de/usb_modeswit ... 40u#p16281 It says ppp widget added support for my modem "sierra ac340u" but requires usb_modeswitch v2.3.0.

usb_modeswitch was created for desktop Linux systems. PPP Widget 2 / 3 doesn't need it - it contains all of the respective functions; furthermore, in some cases modems have to be treated slightly differently for use in Android.

The problem we have here is a conflict about the built-in modem capability and the external app - they both compete for the modem access. This is obvious in the error message:
"Error when opening modem port: Could not claim control interface"

The system has 'grabbed' the modem so PPP Widget can't access it. I'm not sure how to solve that, other than somehow disable the whole build-in modem support in the device ...

[sinnedone]

THe rom I am currently using has usb_modeswitch v2.2.6 and per the post here http://www.draisberghof.de/usb_modeswit ... 40u#p16281 It says ppp widget added support for my modem "sierra ac340u" but requires usb_modeswitch v2.3.0.

usb_modeswitch was created for desktop Linux systems. PPP Widget 2 / 3 doesn't need it - it contains all of the respective functions; furthermore, in some cases modems have to be treated slightly differently for use in Android.

The problem we have here is a conflict about the built-in modem capability and the external app - they both compete for the modem access. This is obvious in the error message:
"Error when opening modem port: Could not claim control interface"

The system has 'grabbed' the modem so PPP Widget can't access it. I'm not sure how to solve that, other than somehow disable the whole build-in modem support in the device ...

Thank you for the response. I will try and do more research taking into consideration what you said. If you can think of anything I can do please post..

Thanks again.

[sinnedone]

THe rom I am currently using has usb_modeswitch v2.2.6 and per the post here http://www.draisberghof.de/usb_modeswit ... 40u#p16281 It says ppp widget added support for my modem "sierra ac340u" but requires usb_modeswitch v2.3.0.

usb_modeswitch was created for desktop Linux systems. PPP Widget 2 / 3 doesn't need it - it contains all of the respective functions; furthermore, in some cases modems have to be treated slightly differently for use in Android.

The problem we have here is a conflict about the built-in modem capability and the external app - they both compete for the modem access. This is obvious in the error message:
"Error when opening modem port: Could not claim control interface"

The system has 'grabbed' the modem so PPP Widget can't access it. I'm not sure how to solve that, other than somehow disable the whole build-in modem support in the device ...

Thank you for the response. I will try and do more research taking into consideration what you said. If you can think of anything I can do please post..

Thanks again.

I did some research on my unit into the /system/etc/usb_modeswitch.d folder and found this config file:

# Sierra devices (specific driver)
TargetVendor= 0x1199
TargetProductList="0017,0018,0019,0020,0021,0022,0023,[... edited ...],9011,9012,9051"
SierraMode=1
NoDriverLoading=1

DO you have any idea as how to either edit this file to work correctly with either pppwidget or natively?

According to http://www.dd-wrt.com/wiki/index.php/3G ... a_Wireless My target vendor is 1199 and product is 9051.

[Josh]

DO you have any idea as how to either edit this file to work correctly with either pppwidget or natively?

It does not make sense to change this; your modem is in the correct mode after you plugged it in. So the mode-switching has worked.

According to http://www.dd-wrt.com/wiki/index.php/3G ... a_Wireless My target vendor is 1199 and product is 9051.

As you can see from the PPP Widget log, your modem was detected with that ID. Again - this is not the problem.

Look again at the table you linked, see the entry about your modem ("AC340U"). The column "protocol" says QMI & MBIM. That means that your device will most likely never work with that modem natively.
It can only do what PPP Widget 1 / 2 does: using a serial protocol, like with an ancient wired modem.

Only PPP Widget 3 can use the QMI protocol. To make it work, the native modem capability of your device will have to be disabled, to stop it from interfering and blocking the modem ports.

I'm not sure how to do this though. The first thing you might want to check is if your system tries to access the modem on the kernel level. Use an on-device terminal emulator for this or use an "adb" shell to do it from a PC.
In the shell or the terminal, run "su" to get root rights, then run the "dmesg" command before and after plugging the modem in.

[Josh]

Just realized that there is a XDA forum for your system software. Maybe you can tell the creator about this problem.

[sinnedone]

Just realized that there is a XDA forum for your system software. Maybe you can tell the creator about this problem.

Thank you for all your help and responses on this matter.

I have already tried but my questions went unanswered. I will try again.

Thank you