Author Message

<  The PPP Widget Family for Android  ~  Please help Huawei E397Bu-501 won't switch.

PostPosted: Tue Apr 11, 2017 4:33 am Reply with quote
Posts: 11 Joined: Mon Sep 19, 2016 4:21 pm
Hello all. :D

I have an android radio unit running usb modeswitch version 2.3.0. The radio supports usb modems and it works with my Huawei 372 (12D1:1446, 12D1:14ac) like expected. Problem for me is that is a 3G modem and I want to use my Huawei E397Bu-501 LTE modem.

The Huawei E397Bu-501 is recognized in windows 10 and driver gets installed via its preloaded software. Once Installed in windows 10 if I go to device manager it lists its vid/pid as 12D1, 1506.

When I connect the E397 modem to android unit I run terminal command "lsusb" as super user I get vid/pid 12D1:1505.

Under system/etc/usb_modeswtich file 12D1:1505 I have this listed:

# Huawei EC156, Huawei E372u-8
TargetVendor=0x12d1
TargetProductList="140b,140c,1506,150f,150a"
HuaweiNewMode=1





Those directions do not put the E397Bu-501 into modem mode. I see commands and other instructions such as driver loading, message content, and checksuccess in other Huawei config files, how can I figure out if I need to set up other instructions to try and put the E397Bu-501 into modem mode?

I am running on Windows 10 and of course the android radio. I don't have any experience with programming or command line stuff and have been researching for weeks just to get to the point I am at. Any help would be appreciated. :)

I believe my next step would be maybe a USB sniffer program to see what commands put the E397Bu-501 into modem mode on windows 10, correct? if so what program could I use


Offline
PostPosted: Tue Apr 11, 2017 4:47 pm Reply with quote
Posts: 1175 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
I guess that the Android Radio manufacturer has a list of usb id's for the devices he has decided to support, a list which is only a subset of what usb_modeswitch supports.
The usb_modeswitch config file for 12d1:1505 is correct but that is not of much help if usb_modeswitch doesn't get called so windows usb sniffing will not get you any further.

Check your system logs (search for usb) and you should probably find a difference after system detection when you plug in the 12d1:1446 device compared to when you plug in the 12d1:1505 device.


Offline
PostPosted: Tue Apr 11, 2017 5:46 pm Reply with quote
Site Admin Posts: 6440 Joined: Sat Nov 03, 2007 12:30 am
You can try to use my app "PPP Widget 3" which also handles mode switching.

Note that it's not clear if your radio will work with your stick once it's in modem mode.


Offline
PostPosted: Wed Apr 12, 2017 4:25 am Reply with quote
Posts: 11 Joined: Mon Sep 19, 2016 4:21 pm
Thank you both for the suggestions/help.

When I plug in a modem that works on this radio (Huawei E372 12d1:1446-12D1:14AC) This is what logcat spits out:
Code:
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
D/Vold    (   95): == current usb device: 12D1/1446 ===
D/Vold    (   95): === USB Switch: /system/bin/usb_modeswitch.sh /etc/usb_modeswitch.d/12d1_1446 &
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/ContextImpl(  470): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1131 com.android.server.usb.UsbSettingsManager.deviceAttached:621 com.android.server.usb.UsbHostManager.usbDeviceAdded:156 com.android.server.usb.UsbHostManager.monitorUsbHostBus:-2 com.android.server.usb.UsbHostManager.access$000:38
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 2
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 2
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 2
D/AudioHardware(  103): AudioHardware pcm playback is exiting standby.
D/AudioHardware(  103): openPcmOut_l() mPcmOpenCnt: 0
D/alsa_route(  103): route_info->sound_card 0, route_info->devices 0 
D/alsa_pcm(  103): pcm_open(0x0003f000)
D/alsa_pcm(  103): pcm_open() card 0, device 0, Playback
D/alsa_route(  103): route_set_controls() set route 0
W/InputMethodManagerService(  470): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41a446a8 attribute=null, token = android.os.BinderProxy@42154e38
I/ActivityManager(  470): Killing 32644:com.google.android.gm/u0a46 (adj 15): empty for 1803s
D/AudioHardware(  103): AudioHardware pcm playback is going to standby.
D/AudioHardware(  103): closePcmOut_l() mPcmOpenCnt: 1
D/alsa_pcm(  103): pcm_close() card 0, device 0, Playback
D/alsa_route(  103): route_set_controls() set route 24
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
D/Vold    (   95): == current usb device: 12D1/14AC ===
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/ContextImpl(  470): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1131 com.android.server.usb.UsbSettingsManager.deviceAttached:621 com.android.server.usb.UsbHostManager.usbDeviceAdded:156 com.android.server.usb.UsbHostManager.monitorUsbHostBus:-2 com.android.server.usb.UsbHostManager.access$000:38
D/AudioHardware(  103): AudioHardware pcm playback is exiting standby.
D/AudioHardware(  103): openPcmOut_l() mPcmOpenCnt: 0
D/alsa_route(  103): route_info->sound_card 0, route_info->devices 0 
D/alsa_pcm(  103): pcm_open(0x0003f000)
D/alsa_pcm(  103): pcm_open() card 0, device 0, Playback
D/alsa_route(  103): route_set_controls() set route 0
D/KitKat_RIL_RK_V3.3( 5586): Found a device, get id
D/KitKat_RIL_RK_V3.3( 5586): device path: /sys/devices/platform/usb20_host/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0
D/KitKat_RIL_RK_V3.3( 5586): USB device path: /sys/devices/platform/usb20_host/usb2/2-1
D/KitKat_RIL_RK_V3.3( 5586): Vendor path: /sys/devices/platform/usb20_host/usb2/2-1/idVendor
D/KitKat_RIL_RK_V3.3( 5586): Product path: /sys/devices/platform/usb20_host/usb2/2-1/idProduct
D/KitKat_RIL_RK_V3.3( 5586): tty Device id is: 12D1/14AC
D/KitKat_RIL_RK_V3.3( 5586): Searching modem table...
D/KitKat_RIL_RK_V3.3( 5586): [matchModem]: match model count=9
D/KitKat_RIL_RK_V3.3( 5586): Need rematch modem later!
D/KitKat_RIL_RK_V3.3( 5586): AT[/dev/ttyUSB3] PPP[/dev/ttyUSB0]
D/KitKat_RIL_RK_V3.3( 5586): [mainLoop]: sleep 10s befor open /dev/ttyUSB3
W/InputMethodManagerService(  470): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@422c9108 attribute=null, token = android.os.BinderProxy@42154e38
I/ActivityManager(  470): Killing 1778:com.google.android.gms.unstable/u0a8 (adj 15): empty for 1801s
D/AudioHardware(  103): AudioHardware pcm playback is going to standby.
D/AudioHardware(  103): closePcmOut_l() mPcmOpenCnt: 1
D/alsa_pcm(  103): pcm_close() card 0, device 0, Playback
D/alsa_route(  103): route_set_controls() set route 24
D/AudioHardware(  103): AudioHardware pcm playback is exiting standby.
D/AudioHardware(  103): openPcmOut_l() mPcmOpenCnt: 0
D/alsa_route(  103): route_info->sound_card 0, route_info->devices 0 
D/alsa_pcm(  103): pcm_open(0x0003f000)
D/alsa_pcm(  103): pcm_open() card 0, device 0, Playback
D/alsa_route(  103): route_set_controls() set route 0
W/InputMethodManagerService(  470): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41f9dd88 attribute=null, token = android.os.BinderProxy@42154e38
D/dalvikvm(32139): GC_CONCURRENT freed 2548K, 33% free 8443K/12576K, paused 4ms+13ms, total 77ms
D/dalvikvm(32139): WAIT_FOR_CONCURRENT_GC blocked 71ms
D/KitKat_RIL_RK_V3.3( 5586): open /dev/ttyUSB3 ...
E/KitKat_RIL_RK_V3.3( 5586): E:/dev/ttyUSB* open sucess.........
I/KitKat_RIL_RK_V3.3( 5586): Device /dev/ttyUSB3 has been opened, fd=23
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^BOOT:40226160,0,0,0,99
D/KitKat_RIL_RK_V3.3( 5586): [setRadioState]: oldstate=1  newstate=0  s_closed=0
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^SRVST:1
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^MODE:5,4
D/KitKat_RIL_RK_V3.3( 5586): mode: -1 -> 5
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^RSSI:31
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^CSNR:-87,-12
D/NotificationMgr(  662): updateNetworkSelection()...state = 3 new network cricket-3G
D/NotificationMgr(  662): cancelNetworkSelection()...
D/AudioHardware(  103): AudioHardware pcm playback is going to standby.
D/AudioHardware(  103): closePcmOut_l() mPcmOpenCnt: 1
D/alsa_pcm(  103): pcm_close() card 0, device 0, Playback
D/alsa_route(  103): route_set_controls() set route 24
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^STIN:99,1,0
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^RSSI:14
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^CSNR:-86,-10
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< +PACSP1
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^SIMST:1
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^SRVST:2
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^RSSI:11
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ^CSNR:-91,-13
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< ATE0
D/KitKat_RIL_RK_V3.3( 5586): modem early init
D/KitKat_RIL_RK_V3.3( 5586): [setRadioState]: oldstate=0  newstate=2  s_closed=0
D/KitKat_RIL_RK_V3.3( 5586): [getSIMStatus]: sState=2
D/KitKat_RIL_RK_V3.3( 5586): ########check cpin ready
D/KitKat_RIL_RK_V3.3( 5586): getSIMStatus return: 2
D/KitKat_RIL_RK_V3.3( 5586): isCardNotSupported: 0
D/KitKat_RIL_RK_V3.3( 5586): [setRadioState]: oldstate=2  newstate=4  s_closed=0
D/KitKat_RIL_RK_V3.3( 5586): [getCommandResponse]: result=E372
D/KitKat_RIL_RK_V3.3( 5586): Current modem id is: E372
D/KitKat_RIL_RK_V3.3( 5586): VID/PID=0x12D1/0x14AC, ID: E372, AT=/dev/ttyUSB3, PPP=/dev/ttyUSB0
D/KitKat_RIL_RK_V3.3( 5586): [onSIMReady]: match model count=1
D/KitKat_RIL_RK_V3.3( 5586): [onSIMReady] isgsm:1
D/AudioHardware(  103): AudioHardware pcm playback is exiting standby.
D/AudioHardware(  103): openPcmOut_l() mPcmOpenCnt: 0
D/alsa_route(  103): route_info->sound_card 0, route_info->devices 0 
D/alsa_pcm(  103): pcm_open(0x0003f000)
D/alsa_pcm(  103): pcm_open() card 0, device 0, Playback
D/alsa_route(  103): route_set_controls() set route 0
I/PlayCommon( 1716): [179] com.google.android.play.a.g.e(940): Preparing logs for uploading
I/PlayCommon( 1716): [179] com.google.android.play.a.g.e(942): No file ready to send
D/KitKat_RIL_RK_V3.3( 5586): onUnsolicited <<<<<<<<<<<<<<<<< +CSMS: 1,1,1
D/dalvikvm(32139): GC_FOR_ALLOC freed 977K, 34% free 8297K/12528K, paused 38ms, total 38ms
W/InputMethodManagerService(  470): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@426daf30 attribute=null, token = android.os.BinderProxy@42154e38
D/KitKat_RIL_RK_V3.3( 5586): [initializeCallback]: === END ===
D/KitKat_RIL_RK_V3.3( 5586): [requestRadioPower]: sState=4  onOff=1
D/KitKat_RIL_RK_V3.3( 5586): [requestScreenState]: screenState=1
D/KitKat_RIL_RK_V3.3( 5586): [getCommandResponse]: result=E372
D/KitKat_RIL_RK_V3.3( 5586): [getCommandResponse]: result=353147040226161
D/KitKat_RIL_RK_V3.3( 5586): IMSI is 310150923021769
D/KitKat_RIL_RK_V3.3( 5586): info: 0x0
D/KitKat_RIL_RK_V3.3( 5586): The requestSignalStrength =11  profile=99
D/KitKat_RIL_RK_V3.3( 5586): The requestSignalStrength =11  profile=99
D/KitKat_RIL_RK_V3.3( 5586): Enter requestQueryNetworkSelectionMode
D/KitKat_RIL_RK_V3.3( 5586): Enter queryNetworkSelectionMode
D/KitKat_RIL_RK_V3.3( 5586): response=1
D/KitKat_RIL_RK_V3.3( 5586): [getSIMStatus]: sState=4
D/AlarmManagerService(  470): Kernel timezone updated to 240 minutes west of GMT
D/NotificationMgr(  662): updateNetworkSelection()...state = 0 new network cricket-3G




When I plug in the Huawei E397 (12D1:1505-12D1:1506) this is what I get:

Code:
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
D/Vold    (   95): == current usb device: 12D1/1505 ===
D/Vold    (   95): === USB Switch: /system/bin/usb_modeswitch.sh /etc/usb_modeswitch.d/12d1_1505 &
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 1
W/ContextImpl(  470): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1131 com.android.server.usb.UsbSettingsManager.deviceAttached:621 com.android.server.usb.UsbHostManager.usbDeviceAdded:156 com.android.server.usb.UsbHostManager.monitorUsbHostBus:-2 com.android.server.usb.UsbHostManager.access$000:38
D/ConnectivityService(  470): handleInetConditionChange: no active default network - ignore
I/PlayCommon( 1716): [140] com.google.android.play.a.g.e(940): Preparing logs for uploading
I/PlayCommon( 1716): [140] com.google.android.play.a.g.a(1043): Connecting to server: https://play.googleapis.com/play/log?format=raw&proto_v2=true
E/PlayCommon( 1716): [140] com.google.android.play.a.g.a(1054): Failed to connect to server: java.net.UnknownHostException: Unable to resolve host "play.googleapis.com": No address associated with hostname
I/PlayCommon( 1716): [179] com.google.android.play.a.g.e(940): Preparing logs for uploading
I/PlayCommon( 1716): [179] com.google.android.play.a.g.e(942): No file ready to send
D/ConnectivityService(  470): handleInetConditionChange: no active default network - ignore
D/dalvikvm(32139): GC_FOR_ALLOC freed 252K, 27% free 5976K/8140K, paused 24ms, total 24ms
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 2
W/Vold    (   95): subsystem found in netlink event
D/Vold    (   95): usb, 2



It doesnt seem to be switched over or detected to be. Then says no active default network???



I also tried PPP widget 3 but it does not seem to connect. When connected it says "dialing out" followed by "no modem response" Funny thing is the signal meter shows it being connected and connecting to 3g and lte. I got these usb log and ppp log after trying. (also tried the experimental Huawei mode but nothing)

Code:
Apr 11, 2017 4:41:39 PM

Device manufacturer string: Newsmy
New device on /dev/bus/usb/002/005
Class of interface 0 is 0xFF
Looking at USB device 12d1:1506 with class 255
Device top dir: /sys/bus/usb/devices/2-1, active cfg: 1
Device layout (config 1) - cl:00  sc:00  pr:00
if:0 as:0 -  cl:ff  sc:01  pr:01 -  ir:81  bi:82  bo:01
if:1 as:0 -  cl:ff  sc:01  pr:02 -  bi:83  bo:02
if:2 as:0 -  cl:ff  sc:01  pr:03 -  bi:84  bo:03
if:3 as:0 -  cl:ff  sc:01  pr:09 -  ir:85
The table says these values define a QMI port
if:4 as:0 -  cl:ff  sc:01  pr:08 -  bi:86  bo:04
if:5 as:0 -  cl:08  sc:06  pr:50 -  bi:87  bo:05
if:6 as:0 -  cl:08  sc:06  pr:50 -  bo:06  bi:88

Found 3 serial ports
Opening port type QMI


Code:
Apr 11, 2017 4:41:44 PM

Starting modem command sequence ...
>
010f0000000000062200040001010001
<
011700800000010622000c00020400000000000102000101
>
0122000001010002002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010202002000130002040001000e0010020003001104000300d107
>
0122000001010003002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010203002000130002040001000e0010020003001104000300d107
>
0122000001010004002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010204002000130002040001000e0010020003001104000300d107
>
0122000001010005002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010205002000130002040001000e0010020003001104000300d107
>
0122000001010006002000160017050064756d6d7918050064756d6d791403006e646f
>
010c0000030100070020000000
<
011f008001010206002000130002040001000e0010020003001104000300d107
>
0122000001010007002000160017050064756d6d7918050064756d6d791403006e646f
<
01180080030102070020000c0002040000000000010200bd08
<
011f008001010207002000130002040001000e0010020003001104000300d107
>
0122000001010008002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010208002000130002040001000e0010020003001104000300d107
>
0122000001010009002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010209002000130002040001000e0010020003001104000300d107
>
012200000101000a002000160017050064756d6d7918050064756d6d791403006e646f
<
011f00800101020a002000130002040001000e0010020003001104000300d107
>
012200000101000b002000160017050064756d6d7918050064756d6d791403006e646f
<
011f00800101020b002000130002040001000e0010020003001104000300d107
>
012200000101000c002000160017050064756d6d7918050064756d6d791403006e646f
<
011f00800101020c002000130002040001000e0010020003001104000300d107
>
012200000101000d002000160017050064756d6d7918050064756d6d791403006e646f
<
011f00800101020d002000130002040001000e0010020003001104000300d107
>
012200000101000e002000160017050064756d6d7918050064756d6d791403006e646f
<
011f00800101020e002000130002040001000e0010020003001104000300d107
>
012200000101000f002000160017050064756d6d7918050064756d6d791403006e646f
<
010b00800000020027000000
<
011f00800101020f002000130002040001000e0010020003001104000300d107
>
0122000001010010002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010210002000130002040001000e0010020003001104000300d107
>
0122000001010011002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010211002000130002040001000e0010020003001104000300d107
>
0122000001010012002000160017050064756d6d7918050064756d6d791403006e646f
<
011f008001010212002000130002040001000e0010020003001104000300d107
Failed to connect, cant't continue
>
0110000000000007230005000102000200
====
End of modem init sequence


This was Huawei experimental mode:
Code:
Apr 11, 2017 4:44:22 PM

Device manufacturer string: Newsmy
New device on /dev/bus/usb/002/006
Class of interface 0 is 0x08
Looking at USB device 12d1:1505 with class 8
Device top dir: /sys/bus/usb/devices/2-1, active cfg: 1
Device layout (config 1) - cl:00  sc:00  pr:00
if:0 as:0 -  cl:08  sc:06  pr:50 -  bi:81  bo:01

Found 0 serial ports
No dedicated modem port found
Preparing to switch mode of USB device 12d1:1505 ...
Device info:
VID=   12d1
PID=   1505
Manufact.= Huawei Technologies
   Product= HUAWEI Mobile
Found matching configuration in collection: 12d1.1505
Wait for 200 ms
Bulk message 1: 55534243123456780000000000000011063000000100010000000000000000
  transmitted
New device on /dev/bus/usb/002/007
Class of interface 0 is 0xFF
Looking at USB device 12d1:1001 with class 255
Device top dir: /sys/bus/usb/devices/2-1, active cfg: 1
Device layout (config 1) - cl:00  sc:00  pr:00
if:0 as:0 -  cl:ff  sc:ff  pr:ff -  ir:81  bi:82  bo:01
if:1 as:0 -  cl:ff  sc:ff  pr:ff -  bi:83  bo:02
if:2 as:0 -  cl:ff  sc:ff  pr:ff -  bi:84  bo:03
if:3 as:0 -  cl:08  sc:06  pr:50 -  bi:85  bo:04
if:4 as:0 -  cl:08  sc:06  pr:50 -  bo:05  bi:86

Found 3 serial ports
Opening port type SERIAL



Any ideas as to what I could try? :(


Offline
PostPosted: Wed Apr 12, 2017 5:37 am Reply with quote
Posts: 1175 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
sinnedone wrote:

Under system/etc/usb_modeswitch file 12D1:1505 I have this listed:

# Huawei EC156, Huawei E372u-8
TargetVendor=0x12d1
TargetProductList="140b,140c,1506,150f,150a"
HuaweiNewMode=1



sinnedone wrote:

D/Vold ( 95): == current usb device: 12D1/1505 ===
D/Vold ( 95): === USB Switch: /system/bin/usb_modeswitch.sh /etc/usb_modeswitch.d/12d1_1505 &



Different pathes! what does /etc/usb_modeswitch.d/12d1_1505 contain?


Offline
PostPosted: Wed Apr 12, 2017 8:06 am Reply with quote
Site Admin Posts: 6440 Joined: Sat Nov 03, 2007 12:30 am
LOM,
on Android there are usually symbolic file links from the root directory to respective folders under /system - so /etc is linked to /system/etc which is the actual location.

sinnedone,
my take is that the manufacturer has just dumped all of usb_modeswitch onto the device; I'm sure he does not really know what to do with your modem once it's mode-switched to 1506.

PPP Widget shows that there is no problem in switching the modem. There are obviously unrelated problems with connecting in the "1506" mode (this has to do with my QMI implementation). The "1001" mode should work however - did you try to connect after you enabled the "Huawei alternative mode"? Be sure to provide your APN though.

Anyway, to make it short - this "1001" mode can be enabled with usb_modeswitch as well, and there is a probability that the radio knows what to do with it.
You need to change the file "/etc/usb_modeswitch.d/12d1_1505" (best to make a copy and rename the original).
Code:
# Huawei EC156, Huawei E372u-8
TargetVendor=0x12d1
TargetProductList="1001,140b,140c,1506,150f,150a"
MessageContent="55534243123456780000000000000011063000000100010000000000000000"


Offline
PostPosted: Wed Apr 12, 2017 10:14 am Reply with quote
Posts: 1175 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
Running an LTE CAT3 dongle in ppp mode will not give LTE speeds which was the reason to use this dongle instead of the E372.
ppp dialup will give 25Mbps if he is lucky..


Offline
PostPosted: Wed Apr 12, 2017 1:17 pm Reply with quote
Site Admin Posts: 6440 Joined: Sat Nov 03, 2007 12:30 am
LOM wrote:
Running an LTE CAT3 dongle in ppp mode will not give LTE speeds which was the reason to use this dongle instead of the E372.
ppp dialup will give 25Mbps if he is lucky..

True.

But again, I am pretty sure that the radio has no way of handling a QMI interface ...


Offline
PostPosted: Wed Apr 12, 2017 2:14 pm Reply with quote
Posts: 1175 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
Josh wrote:
LOM wrote:
Running an LTE CAT3 dongle in ppp mode will not give LTE speeds which was the reason to use this dongle instead of the E372.
ppp dialup will give 25Mbps if he is lucky..

True.

But again, I am pretty sure that the radio has no way of handling a QMI interface ...


Agree, the radio wont do qmi.
Why can't pppwidget3 handle it? Because it is dual interface QMI?
ff/01/08 is the data interface and ff/01/09 is the control interface in case you didn't know.


Offline
PostPosted: Wed Apr 12, 2017 5:16 pm Reply with quote
Site Admin Posts: 6440 Joined: Sat Nov 03, 2007 12:30 am
LOM wrote:
Why can't pppwidget3 handle it? Because it is dual interface QMI?

No problem there - the "PPP Log" in the 4th post shows a working QMI exchange. It's just that the connection negotiation is not completed, for reasons likely related to my simplistic QMI protocol implementation (just a subset, in Java) which works fine with the Huawei modems in my personal 'zoo'.

I have yet to analyze the log in depth.


Offline
PostPosted: Thu Apr 13, 2017 1:26 am Reply with quote
Posts: 11 Joined: Mon Sep 19, 2016 4:21 pm
Thank you both again for the responses.

Josh wrote:


sinnedone,
my take is that the manufacturer has just dumped all of usb_modeswitch onto the device; I'm sure he does not really know what to do with your modem once it's mode-switched to 1506.

PPP Widget shows that there is no problem in switching the modem. There are obviously unrelated problems with connecting in the "1506" mode (this has to do with my QMI implementation). The "1001" mode should work however - did you try to connect after you enabled the "Huawei alternative mode"? Be sure to provide your APN though.

Anyway, to make it short - this "1001" mode can be enabled with usb_modeswitch as well, and there is a probability that the radio knows what to do with it.
You need to change the file "/etc/usb_modeswitch.d/12d1_1505" (best to make a copy and rename the original).
Code:
# Huawei EC156, Huawei E372u-8
TargetVendor=0x12d1
TargetProductList="1001,140b,140c,1506,150f,150a"
MessageContent="55534243123456780000000000000011063000000100010000000000000000"



I did try PPP widget3 on the Alternative mode, but still a no go. It says "building network" then a second after that "disconnected". The USB log in alternative mode is posted above and the PPP log is empty.


I swapped out the 12D1:1505 code for the one you listed but still no go for me. The modem never seems to switch into modem mode, and the logcat is the same.

Any more ideas? I'm willing to learn to be able to help myself, it's just going to take a little longer since I'm not really versed in any of this. :oops:


Offline
PostPosted: Thu Apr 13, 2017 8:01 am Reply with quote
Site Admin Posts: 6440 Joined: Sat Nov 03, 2007 12:30 am
Don't invest much more energy in this problem - I am working at PPP Widget 3 again and I'm quite certain we'll get it to connect with your modem.

I tested one of my QMI-type modems yesterday (Huawei E398) and it showed the same behaviour as your's when connecting - but only once ...
The second attempt was successful, so my assumption is that the network status is somehow involved, like the modem is not yet fully registered - or that the registering parameters are incorrect.

Anyway, now I know that type of response I can handle it on the developing side. Give me a day or two.

In the meantime, you can make sure your APN is 100% correct. Oh, and did you get a signal level indicator in PPP Widget ?


Offline
PostPosted: Thu Apr 13, 2017 12:34 pm Reply with quote
Posts: 11 Joined: Mon Sep 19, 2016 4:21 pm
I did get signal bars yes. At first is green (which I believe is 3g) then changes over to blue (LTE?)

The APN would be the same regardless of device correct? My carrier only lists one APN (ndo) The carrier is called Cricket which is AT&T. I also tried AT&T APN's. (Phone, broadband, nxtgenphone)


If there is anything I can help with as far as info for pop widget let me know. Thanks again for all your help. :)


Offline
PostPosted: Thu Apr 13, 2017 2:29 pm Reply with quote
Site Admin Posts: 6440 Joined: Sat Nov 03, 2007 12:30 am
sinnedone wrote:
I did get signal bars yes. At first is green (which I believe is 3g) then changes over to blue (LTE?)

That's good - it shows that you have network. Yes, blue means LTE (or rather 4G).
sinnedone wrote:
The APN would be the same regardless of device correct? My carrier only lists one APN (ndo) The carrier is called Cricket which is AT&T. I also tried AT&T APN's. (Phone, broadband, nxtgenphone)

The APN is related to your SIM card, regardless of the device it's in. I think "ndo" is correct, so that's not the problem here.

Again, give me a day or two ...


Offline
PostPosted: Fri Apr 14, 2017 4:06 am Reply with quote
Posts: 11 Joined: Mon Sep 19, 2016 4:21 pm
Ok thank you.

Will you be replying in this thread or is there another section I need to keep an eye on?


Offline

Display posts from previous:  Sort by:

All times are UTC+02:00
Page 1 of 2
22 posts
Go to page 1 2 Next
Users browsing this forum: No registered users and 4 guests
Search for:
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum