[Josh]

rayaz, can you open a new thread for your request please?

It would help if you could attach a module from your device to the post - just one. The smallest one is probably "scsi_wait_scan.ko" which usually sits in "/lib/modules" (only visible with root access, e.g. with "Root Explorer").

[MarioLast]

No....its MediaTek 6577 cpu (((

[Josh]

No....its MediaTek 6577 cpu

It does not matter what the hardware is - the manufacturer of an Android device is required to provide the kernel source (including its exact configuration for the device) under the rules of the GPL.

[spinal2k]

After installing modules on OP, I got it successfully working with the following modems:

Huawei E220 (requires to put manual port to ttyUSB1)
Huawei K3765 (leave port automatic or ttyUSB0)

Cheers

[MarioLast]

No....its MediaTek 6577 cpu

It does not matter what the hardware is - the manufacturer of an Android device is required to provide the kernel source (including its exact configuration for the device) under the rules of the GPL.

May be this...

[Josh]

This is your system information, but now you have to find the kernel source release for your device.

Ask the manufacturer if you are not able to find it.

[die_for_rock_vn]

hi Josh
I tried to get pppwidget works on my Nexus 10, but not successful.
Kernel on my tablet is a custom kernel, and I don't want to go back stock kernel.
when run:
1. insmod usb_wwan.ko -> inti_module "usb_wwan.ko" failed (Exec format error)
2. dmesg and I found : usb_wwan: version magic '3.4.5-g4e6298b SMP preempt mod_unload ARMv7 p2v8 ' should be '3.4.28-KTManta-g90df6be SMP preempt mod_unload ARMv7 p2v8 '

I know the problem is the kernel name of the modules does not match with this custom kernel.
So what I have to do to make it work?
Thanks.

[Josh]

It's not just the kernel name that counts. You would also need the respective kernel source with all patches, plus the configuration used for compiling.
There are several groups of options that will affect the properties of each and every module. If these settings don't match, a crash is likely.

With custom kernels, it should be fairly easy to ask their maker for the additional modules.

[die_for_rock_vn]

It's not just the kernel name that counts. You would also need the respective kernel source with all patches, plus the configuration used for compiling.
There are several groups of options that will affect the properties of each and every module. If these settings don't match, a crash is likely.

With custom kernels, it should be fairly easy to ask their maker for the additional modules.

I run insmod usbserial.ko, usb_wwan.ko and option.ko without error, but still No dirver found

Here is log

PPP Widget version 1.2.10
USB_ModeSwitch log from Sun Feb 03 12:49:53 ICT 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 HUAWEI Technology
product HUAWEI Mobile
serial 1234567890ABCDEF
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.1446
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProductList set to 1001,1406,140b,140c,1412,141b,1432,1433,1436,14ac,1506,1511
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 12d1 -p 1446 -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= 0x12d1
DefaultProduct= 0x1446
TargetVendor= 0x12d1
TargetProduct= not set
TargetClass= not set
TargetProductList="1001,1406,140b,140c,1412,141b,1432,1433,1436,14ac,1506,1511"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
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 12d1:1446
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: HUAWEI Technology
Product: HUAWEI Mobile
Serial No.: 1234567890ABCDEF
-------------------------
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): -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.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:141b (HUAWEI Technology: HUAWEI Mobile)
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"

Checking for active driver path: /sys/bus/usb-serial/drivers/option1

Driver not active, try to find module "option"

Can't find module "option"
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

My dongle is HUAWEI E1752
Kernel build:
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_OPTION=m

[LOM]

Your drivers must then be in a non-standard library path but since you are sure you have them then it easy to fix your problem.
Copy the drivers from wherever they are into [sdcard]/pppwidget/lib

[Josh]

die_for_rock_vn,

the driver modules should be either in /system/lib/modules or in /lib/modules.

"insmod" works only if you give it the full name to the module file (or change into the module folder). So what was the path that you used?

[die_for_rock_vn]

die_for_rock_vn,

the driver modules should be either in /system/lib/modules or in /lib/modules.

"insmod" works only if you give it the full name to the module file (or change into the module folder). So what was the path that you used?

yes, the driver modules are in /system/lib/modules, and I manually run insmod successful.
Can you share link githubs for sources?

[Josh]

I don't have any kernel sources except for the current stock firmware.
You may want to ask the people who built your kernel.

If your kernel has the modules on-board, it should not be necessary to add them again.

[die_for_rock_vn]

I back to using stock kernel. no problem.
thank Josh.

[Jalize]

I had pppwidget working on my Nexus10 with JB 4.2.1, but after upgrading to JB 4.2.2 the pppwidget does not work. I now get the "driver not found" problem. I did copy the drivers into the /lib/ directory as with JB 4.2.1 but it seems that the drivers are now not compatible with new JB 4.2.2.

I have root access and my device is Huawei E1752

What can be done

Thanks