[copvaibhav]

Bro I copied ur module to system ..lib...module and restart device after that connect button is visible but my cellular network goes disable and after pressing connect button it goes back to connect after few seconds ......here is the new log







USB_ModeSwitch log from Sun Dec 23 16:39:33 IST 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 ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
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.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
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 2 -v 19d2 -p fff5 -f $cB

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= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
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/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
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 0x0a (out) and 0x89 (in)

USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Resetting message endpoint 0x0a
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.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"

Trying to find module "option"
Loading support module /system/lib/modules/ppp_async.ko
Error: insmod: init_module '/system/lib/modules/ppp_async.ko' failed (Exec format error)
Loading support module /system/lib/modules/usb_wwan.ko
Error: insmod: init_module '/system/lib/modules/usb_wwan.ko' failed (Exec format error)
Loading main driver module "option"
Error: insmod: init_module '/system/lib/modules/option.ko' failed (Exec format error)
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed

All done, exiting

[copvaibhav]

bro terminal windows keeps saying can't execute is a directory.... m running command system/lib/modules

[Josh]

I copied ur module to system ..lib...module

Why did you do that? Please follow the instructions in the "Driver Modules" posting.

[copvaibhav]

i just thought that copying might do something.... that's why..but nothing happened excepting these strange activity m removing them from that location straight away.

[Josh]

Put the modules in "<sdcard>/pppwidget/lib". You don't need special rights for that, and there is no danger of messing with the system files.

Then continue with the test as described.

[copvaibhav]

i would like to know this that if i downgrade my tab to 4.0.4 should your drivers work if yes then which version of ICS should i load in that case which supports your kernel version

[copvaibhav]

bro i have downgraded my tab to 4.0.4 and its kernel is 3.0.8-1060938 rooted the device and installed ppp copied your drivers and bingo modem found but now a different error modem setup error ??? now whats this bro


here is the new log




USB_ModeSwitch log from Tue Dec 25 12:10:01 IST 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 ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
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.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
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 2 -v 19d2 -p fff5 -f $cB

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= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
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/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
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 0x0a (out) and 0x89 (in)

USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Resetting message endpoint 0x0a
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.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"

Trying to find module "option"
Loading support module /sdcard/pppwidget/lib/ppp_async.ko
Loading support module /sdcard/pppwidget/lib/usb_wwan.ko
Loading main driver module "option"
Module loaded successfully.
Trying to add ID to driver "option"
ID added to driver; check for new devices in /dev
Driver was bound to the device

All done, exiting

[Josh]

bro i have downgraded my tab to 4.0.4 and its kernel is 3.0.8-1060938

So did you retrieve that specific module error before downgrading?

If not, then we still don't know what the problem is.

[copvaibhav]

no i didnt..... i just thought to downgrade coz i saw one topic in this forum that ppp widget is working fine with 4.0.4 on samsung galaxy tab2 ....did u got any clues with usb mode log ...or should i paste ppp log also??

[copvaibhav]

bro i have managed to connect net and its working fine.....4.0.4 but still no clues about 4.1.1

[Josh]

Well, I need that error message that I asked you for.

[copvaibhav]

will surely tell when i upgrade my tab again to 4.1.1

[prabuddhadg]

Hi Josh. Sorry I was being lazy and hoping that copvaibhav would be able to provide you with all necessary data to get this modem working.

Basically I am getting the same error as him. No driver found.

So, I tried your suggested tests on the terminal emulator and ran su and then insmod usb_wwan.ko, insmod ppp_async.ko and insmod option.ko.

However, in all three cases, the message was "Can't open ...".

Any suggestion on what I need to do now?

For the sake of clarity, I am on a Samsung GT-P3100 tablet, Jelly bean 4.1.1 and kernel version is 3.0.31 ~ 471788.

I am attaching the log below: -

USB_ModeSwitch log from Fri Dec 28 11:48:52 IST 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 ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
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.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 19d2 -p fff5 -f $cB

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= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
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/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
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 0x0a (out) and 0x89 (in)

USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Resetting message endpoint 0x0a
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.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"

Trying to find module "option"
Loading support module /sdcard/pppwidget/lib/ppp_async.ko
Error: insmod: init_module '/sdcard/pppwidget/lib/ppp_async.ko' failed (Exec format error)
Loading support module /sdcard/pppwidget/lib/usb_wwan.ko
Error: insmod: init_module '/sdcard/pppwidget/lib/usb_wwan.ko' failed (Exec format error)
Loading main driver module "option"
Error: insmod: init_module '/sdcard/pppwidget/lib/option.ko' failed (Exec format error)
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed

All done, exiting

[Josh]

As I have told copvaibhav, I need to see the detailed error message that "dmesg" provides after the "insmod" command failed - just the last line.

[prabuddhadg]

OK, Josh, here are the first few lines and the last line.

u0_a165@android:/ $ su
u0_a165@android:/ # insmod usb_wwan.ko
insmod: can't open 'usb_wwan.ko'
255|u0_a165@android:/ # dmesg
: CLK32KG: No configuration
<4>[ 5691.445983] C0 [ kworker/u:4] Suspending console(s) (use no_console_suspend to debug)
..............many many many lines here.............
<6>[ 5859.026641] C1 [irq/206-melfas_] tsp: finger 0 up remain: 0u0_a165@android:/ #