[u.chamara]

device - nexus 7 - 8gb - wifi only
dongle - zte mf 190b


when my nexus 7 got updated to androoid 4.2 the widget worked but only chrome seems to be working
now with the new version of the app and adroid 4.2.1 ; it is struck on prepare device

normally what should happen is

*first the red light in the dongle starts blinking then the widget says preparing device
*then the bulb tuns of and becomes constant red
*the bulb turns constant green and in the widget the button connect appears
*when i click connect widget displays "connected" and bulb in the dongle becomes blinking green

what happens now is whe i install the widget (gave su permission and everything) and plugged in the dongle ; it goes upto constant gree but the button connect does't appear ("struck on prepare device") and when i remove the dongle and plugged it again , the system doesn't even ask whether should i use ppp widget for this and the dongle displays blinking red only ;

please help
in a grave situation

ps -
worked well with the previous versions on android 4.1..

[Josh]

Can you post the logs from "usb_modeswitch"? They are created in "<sdcard>/pppwidget/log" once the logging option is enabled on the config page and the modem is re-plugged afterwards.

[u.chamara]

thanks a lot but today it works i don't know how but i disabled that (use wifi for connection stats and enabled logging and it works) thnx a lot

[u.chamara]

but i can't disconnect though (nothing happens when i click disconnect)

[u.chamara]

when i removed the device aand connected again the previous error(struck on prepare device) occured pls help

Using port ttyACM1 for connection
ATE1
OK
AT+CFUN=1
OK
AT+CGDCONT=1,"IP","mobitel"
OK
ATD*99***1#
CONNECT
Report from chat:

chat: Dec 13 10:21:15 CONNECT 7205000
Serial connection established.
using channel 1
Using interface ppp0
Connect: ppp0 <--> /dev/ttyACM1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5e1bdbd4>]
rcvd [LCP ConfReq id=0x1 <mru 1600> <auth pap> <magic 0xe3565da5> <asyncmap 0x0> <pcomp> <accomp>]
sent [LCP ConfRej id=0x1 <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x5e1bdbd4>]
rcvd [LCP ConfReq id=0x2 <mru 1600> <auth pap> <magic 0xe3565da5> <asyncmap 0x0>]
sent [LCP ConfAck id=0x2 <mru 1600> <auth pap> <magic 0xe3565da5> <asyncmap 0x0>]
sent [PAP AuthReq id=0x1 user="localhost" password=<hidden>]
rcvd [PAP AuthAck id=0x1 "Icera PPP - Password Verified OK"]
Remote message: Icera PPP - Password Verified OK
PAP authentication succeeded
sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
rcvd [IPCP ConfReq id=0x1 <addr 10.0.0.1>]
sent [IPCP ConfAck id=0x1 <addr 10.0.0.1>]
rcvd [IPCP ConfNak id=0x1 <addr 10.224.136.75> <ms-dns1 172.19.70.210> <ms-dns3 172.19.70.211>]
sent [IPCP ConfReq id=0x2 <addr 10.224.136.75> <ms-dns1 172.19.70.210> <ms-dns3 172.19.70.211>]
rcvd [IPCP ConfReq id=0x2 <addr 10.0.0.1>]
sent [IPCP ConfAck id=0x2 <addr 10.0.0.1>]
rcvd [IPCP ConfAck id=0x2 <addr 10.224.136.75> <ms-dns1 172.19.70.210> <ms-dns3 172.19.70.211>]
local IP address 10.224.136.75
remote IP address 10.0.0.1
primary DNS address 172.19.70.210
secondary DNS address 172.19.70.211
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-up started (pid 5875)
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-up finished (pid 5875), status = 0x0
Modem hangup
Connect time 4.9 minutes.
Sent 1429470 bytes, received 5547087 bytes.
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-down started (pid 6832)
Connection terminated.
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-down finished (pid 6832), status = 0xff

[spondbob]

same thing happen to my GT-P7310 using Android 4.1.2 version, stuck on "Prepare device ..." and the light on modem keep on red mode
any ideas guys?

[Josh]

Can you all please post the logs from "usb_modeswitch"? They are created in "<sdcard>/pppwidget/log" once the logging option is enabled on the config page and the modem is re-plugged afterwards.

[u.chamara]

i did can you pls check

[Josh]

No, I need the files where the name starts with "usb_modeswitch", from the folder on the device.

[u.chamara]

ohh sorry my bad



USB_ModeSwitch log from Thu Dec 13 10:33:34 IST 2012

Raw args from udev: 2-1/2-1:1.0

Using top device dir /sys/bus/usb/devices/2-1
----------------
USB values from sysfs:
manufacturer ZTE
product MF190B
serial B5DC4EA8F57585D3ECD8E1D9F4E51A2426A13A59
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.0146
! matched. Reading config data
config: TargetVendor set to 19d2
config: TargetProduct set to 0143
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 2 -v 19d2 -p 0146 -f $configBuffer

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------

Reading long config from command line

* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x19d2
DefaultProduct= 0x0146
TargetVendor= 0x19d2
TargetProduct= 0x0143
TargetClass= not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345679000000000000061b000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled


Use given bus/device number: 002/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:0146
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: ZTE
Product: MF190B
Serial No.: B5DC4EA8F57585D3ECD8E1D9F4E51A2426A13A59
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 1 (CSW) ...
OK, response successfully read (13 bytes).
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -6
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.

ok:busdev
--------------------------------
(end of usb_modeswitch output)

Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Waiting for device file system (8 sec.) ...
Waiting for device file system (9 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:0143 (ZTE: MF190B)
Device class of first interface is 02
Now checking for bound driver ...
No driver has bound to interface 0
Module loader is /system/bin/insmod
Trying to find and install main driver module "cdc_acm"
Could not find Driver module "cdc_acm"
Driver binding seems to have failed

All done, exiting

[spondbob]

here's mine on GT-P7310 using 4.1.2 :


USB_ModeSwitch log from Fri Dec 14 10:43:11 ICT 2012

Raw args from udev: 1-1/1-1:1.0

Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer Qualcomm, Incorporated
product Qualcomm CDMA Technologies MSM
serial 803817040000
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/05c6.f000
! matched. Reading config data
config: TargetVendor set to 05c6
config: TargetProduct set to 9000
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 6 -v 05c6 -p f000 -f $configBuffer

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------

Reading long config from command line

* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x05c6
DefaultProduct= 0xf000
TargetVendor= 0x05c6
TargetProduct= 0x9000
TargetClass= not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled

Use given bus/device number: 001/006 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 05c6:f000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: Qualcomm, Incorporated
Product: Qualcomm CDMA Technologies MSM
Serial No.: 803817040000
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -34
Bus/dev search active, referring success check to wrapper. Bye.

ok:busdev
--------------------------------
(end of usb_modeswitch output)

Checking success of mode switch for max. 20 seconds ...
Reading attributes ...
Reading attributes ...
Reading attributes ...
Waiting for device file system (4 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 201e:10f8 (Qualcomm, Incorporated: Qualcomm CDMA Technologies MSM)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"

Trying to find module "option"
Falling back to "usbserial"
No driver found; no more fallbacks, giving up ...

Trying to unload driver "usbserial"

Trying to load driver "usbserial" with device IDs
Error: insmod: can't open ''
Driver binding seems to have failed

All done, exiting

[Josh]

u.chamara,

try the newest update (I put it on Google Play last night). It should solve a problem with picking the wrong ttyACM port.

[Josh]

spondbob,

your device seems to lack the drivers for the serial port (not unusual with Samsung devices).

I have decided to provide driver modules for very common devices (Samsung, Nexus) on this site. Your's is not listed yet, so I need the exact kernel name (see device settings, menu entry "About Tablet").

Text please, not just a screenshot!

For examples and further instructions see the sticky topic (right on the top) about "Driver Modules" in this forum.

[spondbob]

spondbob,

your device seems to lack the drivers for the serial port (not unusual with Samsung devices).

I have decided to provide driver modules for very common devices (Samsung, Nexus) on this site. Your's is not listed yet, so I need the exact kernel name (see device settings, menu entry "About Tablet").

Text please, not just a screenshot!

For examples and further instructions see the sticky topic (right on the top) about "Driver Modules" in this forum.

my ROM isn't the official one, it's from AOSP http://forum.xda-developers.com/showthr ... ?t=1789464. is it the problem?
here's information from my tablet :

model :
GT-P7310

android version :
4.1.2

kernel version :
3.1.10-cyanogenmod+
kalltkaffe@VirtualUbuntu #13
SMP PREEMPT Sun nov 11 23:17:52 CET 2012

Build number :
AOSP-4.1.2

[spondbob]

i just update to your newest version, now the widget said no driver found. here's the log :

USB_ModeSwitch log from Fri Dec 14 15:21:12 ICT 2012

Raw args from udev: 1-1/1-1:1.0

Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer Qualcomm, Incorporated
product Qualcomm CDMA Technologies MSM
serial 803817040000
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/05c6.f000
! matched. Reading config data
config: TargetVendor set to 05c6
config: TargetProduct set to 9000
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 6 -v 05c6 -p f000 -f $configBuffer

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------

Reading long config from command line

* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x05c6
DefaultProduct= 0xf000
TargetVendor= 0x05c6
TargetProduct= 0x9000
TargetClass= not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled

Use given bus/device number: 001/006 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 05c6:f000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: Qualcomm, Incorporated
Product: Qualcomm CDMA Technologies MSM
Serial No.: 803817040000
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -34
Bus/dev search active, referring success check to wrapper. Bye.

ok:busdev
--------------------------------
(end of usb_modeswitch output)

Checking success of mode switch for max. 20 seconds ...
Reading attributes ...
Reading attributes ...
Reading attributes ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 201e:10f8 (Qualcomm, Incorporated: Qualcomm CDMA Technologies MSM)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"

Trying to find module "option"
Falling back to "usbserial"
No driver found; no more fallbacks, giving up ...

Trying to unload driver "usbserial"

Trying to load driver "usbserial" with device IDs
Error: insmod: can't open ''
Driver binding seems to have failed

All done, exiting