USB_ModeSwitch

Ah, no - you need to be in the folder "/sdcard/pppwidget/lib". In your test, the module file is not even found because you are in the top folder named "/" ...

Run these commands: The error message at the bottom of "dmesg" afterwards will clearly point to a module problem, I think.

Oops! Sorry, I didn't know that.

Well, here is the message from within the folder.

u0_a165@android:/ $ su
u0_a165@android:/ # cd /sdcard/pppwidget/lib
b_wwan.ko <
insmod: init_module 'usb_wwan.ko' failed (Exec format error)
255|u0_a165@android:/sdcard/pppwidget/lib # dmesg
3.059570] C1 [ kworker/u:4] suspend: enter suspend
<7>[86653.059600] C1 [ kworker/u:4] PM: Preparing system for mem sleep
.......
.......
<6>[86868.441650] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[86872.264099] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86872.283905] C0 [ AudioOut_2] wm8994-codec wm8994-codec: Moving to audio clocking settings
<6>[86872.283935] C0 [ AudioOut_2] wm8994-codec wm8994-codec: _wm8994_set_fll ++
<6>[86872.401519] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0u0_a165@android:/sdcard/pppwidget/lib #

I hope I got it right this time.

Thanks for your patience.

Sigh ...

Yes, you did it all right - but I did not take into account the extreme verbosity of Samsung's logging ...

It seems to log every single 'finger' touch and release on the screen, so by the time you typed "d-m-e-s-g-enter", there are already 12 or more new log messages after the "insmod" error!

So we need the last line(s) in the dmesg log that doesn't mention a 'finger' or a 'codec'.

Sorry about that tedious process!

Does this help Josh?
All this is Greek to me. I simply copied some more of the last bit of the log.

......
<6>[86853.772247] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86853.792144] C0 [ AudioOut_2] wm8994-codec wm8994-codec: Moving to audio clocking settings
<6>[86853.792175] C0 [ AudioOut_2] wm8994-codec wm8994-codec: _wm8994_set_fll ++
<6>[86853.970703] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0usb_wwan: disagrees about version of symbol module_layout
<7>[86860.797332] C0 [ swapper] IPC-RX: 7f 0b 00 00 08 00 ff 57 07 06 03 3a 7e
<7>[86863.626586] C0 [ swapper] IPC-RX: 7f 0b 00 00 08 00 ff 57 07 06 03 38 7e
<6>[86864.125976] C0 [ kworker/0:2] max17042 7-0036: VCELL : 3725, data : 0xba40
<6>[86864.126708] C0 [ kworker/0:2] max17042 7-0036: AVG Current : -409, data :0xf5c2
<6>[86864.127471] C0 [ kworker/0:2] max17042 7-0036: Current : -402, data :0xf5ef
<6>[86864.128204] C0 [ kworker/0:2] max17042 7-0036: SOC : 32, data : 0x20cc
<6>[86864.130432] C0 [ kworker/0:2] max17042 7-0036: TEMPERATURE : 287, data :0x1cc0
<6>[86864.195648] C0 [ kworker/0:2] battery_manager battery_manager: vcell = 3725000 soc = 32 current = -402 avg_current = -409 status = 2 health = 1 temp = 287 discharge status = 0, limit time : 0, bootmode : 0
<6>[86865.511566] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86865.521301] C1 [ watchdog] !@Sync 2891
<6>[86865.530792] C0 [ AudioOut_2] wm8994-codec wm8994-codec: Moving to audio clocking settings
<6>[86865.530822] C0 [ AudioOut_2] wm8994-codec wm8994-codec: _wm8994_set_fll ++
<6>[86865.679504] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[86866.386138] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86866.554321] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[86867.199829] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86867.321533] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[86867.721191] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86867.874084] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[86868.304473] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86868.441650] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[86872.264099] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[86872.283905] C0 [ AudioOut_2] wm8994-codec wm8994-codec: Moving to audio clocking settings
<6>[86872.283935] C0 [ AudioOut_2] wm8994-codec wm8994-codec: _wm8994_set_fll ++
<6>[86872.401519] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0u0_a165@android:/sdcard/pppwidget/lib #

Hope we did better this time.

Yes!! You have made a catch!

"usb_wwan: disagrees about version of symbol module_layout"

Let's see what I can find out about this. It's a hint, at last ...

Oh great! So 2012 ends on a positive note. I shall look forward to something new.

For this side of the world, 2012 is still on ...

Anyway, in this year or the next one, can you post one of your existing modules (provided by Samsung) here? There might be one or more in
"/system/lib/modules".

I need this to compare the module layout.

I am not sure how to do that. There are two files in the folder you specified. The files are too large going by the rules of this forum. Here are links to both files in order of size: -

https://www.box.com/s/cdv5oc83oeoh20tfrdd7

https://www.box.com/s/z0iri0s5232vrxnyyef8

O.K., got them. Next time, I should suggest to zip those files first ...

New game, new luck ...

Can you test the modules in the attachment?
I have patched the "module_layout" CRC sum in a hex editor

It still says Driver not found

USB_ModeSwitch log from Thu Jan 03 10:48:09 IST 2013

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 4 -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/004 ...
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 (Invalid argument)
Loading support module /sdcard/pppwidget/lib/usb_wwan.ko
Error: insmod: init_module '/sdcard/pppwidget/lib/usb_wwan.ko' failed (Invalid argument)
Loading main driver module "option"
Error: insmod: init_module '/sdcard/pppwidget/lib/option.ko' failed (Invalid argument)
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device

All done, exiting

---------------------------


NOW THE DMESG log

u0_a165@android:/ $ su
u0_a165@android:/ # cd sdcard/pppwidget
u0_a165@android:/sdcard/pppwidget # cd lib
b_wwan.ko <
insmod: init_module 'usb_wwan.ko' failed (Invalid argument)
255|u0_a165@android:/sdcard/pppwidget/lib # dmesg
1461.334503] C0 [ kworker/0:0] max17042 7-0036: TEMPERATURE : 309, data :0x1ef8
<6>[ 1461.342346] C0 [ watchdog] !@Sync 48
<6>[ 1461.393157] C0 [ kworker/0:0] battery_manager battery_manager: vcell = 3676000 soc = 24 current = -513 avg_current = -557 status = 2 health = 1 temp = 309 discharge status = 0, limit time : 0, bootmode : 0
<3>[ 1464.157897] C0 [ usb-storage] usb storage -- short read transfer
..............
..............
<6>[ 2336.613281] C0 [ kworker/0:1] max17042 7-0036: AVG Current : -399, data :0xf605
<6>[ 2336.614044] C0 [ kworker/0:1] max17042 7-0036: Current : -391, data :0xf637
<6>[ 2336.614776] C0 [ kworker/0:1] max17042 7-0036: SOC : 20, data : 0x14ef
<6>[ 2336.617004] C0 [ kworker/0:1] max17042 7-0036: TEMPERATURE : 339, data :0x21f0
<6>[ 2336.674682] C0 [ kworker/0:1] battery_manager battery_manager: vcell = 3685000 soc = 20 current = -391 avg_current = -399 status = 2 health = 1 temp = 339 discharge status = 0, limit time : 0, bootmode : 0
<6>[ 2339.761901] C0 [ mmcqd/0] mmc0 LDO enable
<6>[ 2348.790740] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[ 2348.809600] C0 [ AudioOut_2] wm8994-codec wm8994-codec: Moving to audio clocking settings
<6>[ 2348.809631] C0 [ AudioOut_2] wm8994-codec wm8994-codec: _wm8994_set_fll ++
<6>[ 2348.882049] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[ 2349.933105] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[ 2350.087982] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[ 2350.474975] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[ 2350.659820] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[ 2351.139648] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[ 2351.339965] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[ 2352.051330] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[ 2352.251983] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0
<6>[ 2353.582183] C0 [irq/206-melfas_] tsp: finger 0 down remain: 1
<6>[ 2353.736022] C0 [irq/206-melfas_] tsp: finger 0 up remain: 0u0_a165@android:/sdcard/pppwidget/lib #



I hope I got the data right.
Now where are we?

Hmm, not even a dmesg error this time ...

The obstacle we are facing is that the kernel configuration of your firmware does not match the configuration that Samsung officially provides with the open source package for this device. This problem does not affect the ICS version of the source packages, but all the Jelly Bean updates (not just for the GT-P3100) seem to have this problem.

I have contacted Samsung support yesterday. Let's see what we get.

I am not going to claim I understand what you are saying. I guess I shall wait for your next update.

The simple point is that any additional modules (drivers) have to match exactly the kernel that is running on the device.

This match is not possible because Samsung screwed up. Let's see if there is an answer ...

One more try while waiting for the response from Samsung ...

This time, the modules were compiled without the "modversions" feature. This is different from the kernel on the device and from the modules you provided. Still, it's worth a try.