Re: ppp widget newest version struck on preapre device
thanks a lot works flawlessly

Re: ppp widget newest version struck on preapre device
with the new version i can connect only once first time it'll run smoothly thenit gets the same error as before
(for the record version 0.97 worked like magic no errors at all unfortunately the network awareness issue comes with android4.2 )
here's that report pls check
and again sometimes it work
and after that its struck on no modem
this was when the device was struck on prepare device
USB_ModeSwitch log from Fri Dec 14 20:44:11 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
(for the record version 0.97 worked like magic no errors at all unfortunately the network awareness issue comes with android4.2 )
here's that report pls check
and again sometimes it work
and after that its struck on no modem
this was when the device was struck on prepare device
USB_ModeSwitch log from Fri Dec 14 20:44:11 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
Re: ppp widget newest version struck on preapre device
The usb_modeswitch log is normal, as before.
Now check your PPP log again: it is important that at the top of it, the usage of "ttyACM0" is indicated.
Regarding the preparation problems: is there any change if you disable automatic detection in the configuration? (Afterwards, touch icon to check for USB devices.)
Now check your PPP log again: it is important that at the top of it, the usage of "ttyACM0" is indicated.
Regarding the preparation problems: is there any change if you disable automatic detection in the configuration? (Afterwards, touch icon to check for USB devices.)
Re: ppp widget newest version struck on preapre device
i just flash my tab back to 4.0.4 with kernel version 3.1.10-1133979 but i got driver not found in the widget. here's the log :
USB_ModeSwitch log from Fri Dec 14 17:58:29 GMT 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 ...
Waiting for device file system (6 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
USB_ModeSwitch log from Fri Dec 14 17:58:29 GMT 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 ...
Waiting for device file system (6 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