Jump to content

froyo leak: win drivers for USB teathering?


Guest LSteam

Recommended Posts

same as title :P

when i check the usb teathering in settings my windows xp says no driver found. i have installed acer usb drivers...so i think that the drivers for usb teathering are different...

i have also tried general driver for android usb teathering but it didn't work...

i need them not only for internet teathering :)

Link to comment
Share on other sites

  • 2 months later...

Hello everyone

I still have problems with all kinds of tethering.

For me USB tethering working properly would be more than enough

but

1. When I use default tethering option - nothing happens. My Liquid shows the blue tether icon but my laptop is still without Internet

2. When i use EasyLink - EasyLink would not detect my device excpet for sometimes... (do not really know why it only detects my Liquid once an hour..) and even if it detects the phone and I click connect the connection line continues to blink and i still have no Internet.

Any ideas? What can be the peroblem?

Thanks for any help

BTW: Using Roggin's Cyanogenmod 1.1 now, but I had same problems with the precedent ROMs and i have Windows 7 32bit.

Edited by Umka
Link to comment
Share on other sites

Guest rithchen

You need to edit PID and VID value in inf file,but i can't upload my inf file. :rolleyes:

The example is below, hope it helps :huh:

for example

[AndroidDevices]

; Google Nexus One without adb

%AndroidDevice% = RNDIS, USB\VID_18D1&PID_4E13

; Google Nexus One with adb

%AndroidDevice% = RNDIS, USB\VID_18D1&PID_4E14

; HTC Sapphire without adb

%AndroidDevice% = RNDIS, USB\VID_0BB4&PID_0FFE

; HTC Sapphire with adb

%AndroidDevice% = RNDIS, USB\VID_0BB4&PID_0FFC

; Motorola Sholes without adb

%AndroidDevice% = RNDIS, USB\VID_22B8&PID_41E4

; Motorola Sholes with adb

%AndroidDevice% = RNDIS, USB\VID_22B8&PID_41E5

; Acer Liquid with adb

%AndroidDevice% = RNDIS, USB\VID_0502&PID_3222

[AndroidDevices.NT.5.1]

; Google Nexus One without adb

%AndroidDevice% = RNDIS.NT.5.1, USB\VID_18D1&PID_4E13

; Google Nexus One with adb

%AndroidDevice% = RNDIS.NT.5.1, USB\VID_18D1&PID_4E14

; HTC Sapphire without adb

%AndroidDevice% = RNDIS.NT.5.1, USB\VID_0BB4&PID_0FFE

; HTC Sapphire with adb

%AndroidDevice% = RNDIS.NT.5.1, USB\VID_0BB4&PID_0FFC

; Motorola Sholes without adb

%AndroidDevice% = RNDIS.NT.5.1, USB\VID_22B8&PID_41E4

; Motorola Sholes with adb

%AndroidDevice% = RNDIS.NT.5.1, USB\VID_22B8&PID_41E5

; Acer Liquid with adb

%AndroidDevice% = RNDIS.NT.5.1, USB\VID_0502&PID_3222

Link to comment
Share on other sites

You need to edit PID and VID value in inf file,but i can't upload my inf file. :rolleyes:

thanks for reply.

Could you please let me know what INF file are you talking about?? Is this for EasyLink method, or normal USB tether without EasyLink. Where is the INF file i need to change located?

Link to comment
Share on other sites

Guest rithchen

Nope, just connect your liquid with your pc by usb cable.

And turn on the usb teathering in android settings, then enjoy it :rolleyes:

Edited by rithchen
Link to comment
Share on other sites

Nope, just connect your liquid with your pc by usb cable.

And turn on the usb teathering in android settings, then enjoy it :rolleyes:

That is what I do. I cannect USB cable, check the TETHER checkbox on my Android-Liquid - but nothing happens. No Error but not Internet connection either.... :huh:

Link to comment
Share on other sites

When you plug in your Liquid, did you see RNDIS device in your Device Manager?

post-697756-1290011783_thumb.png

No i do not... i think that is the problem (i tired on Ubuntu and it worked just fine...). Any Ideas how to isntall the correct drivers and make RNDIS device available in Device manager?

Also, should USB debugging be ON or OFF = or it does not matter?

Seems like I need the drivers after all - even if it is Windows 7....

Thanks

1.jpg

Edited by Umka
Link to comment
Share on other sites

Ok, try to remove "Android HSUSB Device", and follow the XP instruction in http://www.google.com/support/android/bin/...swer=182134#usb

Just remember to modify the section in "tetherxp.inf" as i metioned before, maybe it will solve your problem :)

Thanks for advice... :) unfrotunately still having problems.

When I am going to STEP5 of the above URL

(5.Check USB tethering. 6.When Windows XP’s New Hardware Wizard opens, select No, not at this time and click Next.)

Step 6 is not showing up. in other words, Windows’s New Hardware Wizard does not open. I have tried to install the inf file manually... but it did not help. I do not know which device i should install it for.

I removed "Android HSUSB Device" but Windows’s New Hardware Wizard did not show up. So i scanned for new devices in Device Manager, so "Android HSUSB Device" reappeared. I tried to install this INF for "Android HSUSB Device" but the error said the INF file does not contain drivers for my device....

Note: I ahve editied the INF file like you adviced above.... B)

I feel lost

Link to comment
Share on other sites

Maybe the problem is your OS or usb cable?

I think the problem is with drivers. I do not now which ones i Need - i tried Ubuntu - and it worked, so this is not a USB cable o RogginCyanogenRom issue. And I also tried on 3 different PCs... (2 of them Win7 64 and one Win7 32bit).

However i beleive OS problem can be fixed somehow.

Could you please be so kind as to send me you Device manager screenshot (with ADB interface devices, Android devices and Network adapters fully expanded)? you can send it to ummka AT ua.fm or post here B)

Thank you very much for your help.

Link to comment
Share on other sites

del B)

Yep - i tried that but got this error: ActiveSync is not compatible with Windows 7 - so I am unable to install this.... Thanks anyway. Still looking for the correct drivers

Link to comment
Share on other sites

OK,

I used teh USWB device viewer you kindly sent and determined which is my device, by pulling it back and pushing it again into the USB port.

So here are the interface descriptors I have found - and there is no RNDIS like you have. Maybe this is Modem? But i tried to install the drivers for this one - and it did not work B) :

 ===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x00

bAlternateSetting:				 0x00

bNumEndpoints:					 0x02

bInterfaceClass:				   0xFF  -> Vendor Specific Device

bInterfaceSubClass:				0xFF

*!*CAUTION:	This appears to be an invalid bInterfaceSubClass

bInterfaceProtocol:				0xFF

*!*WARNING:  must be set to PC_PROTOCOL_UNDEFINED 0 for this class

iInterface:						0x00

*!*ERROR:  0xFF is the prerelease USB Video Class ID




		  ===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x01

bAlternateSetting:				 0x00

bNumEndpoints:					 0x02

bInterfaceClass:				   0xFF  -> Vendor Specific Device

bInterfaceSubClass:				0x42

*!*CAUTION:	This appears to be an invalid bInterfaceSubClass

bInterfaceProtocol:				0x01

*!*WARNING:  must be set to PC_PROTOCOL_UNDEFINED 0 for this class

iInterface:						0x00

*!*ERROR:  0xFF is the prerelease USB Video Class ID


===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x02

bAlternateSetting:				 0x00

bNumEndpoints:					 0x03

bInterfaceClass:				   0xFF  -> Vendor Specific Device

bInterfaceSubClass:				0x00

*!*CAUTION:	This appears to be an invalid bInterfaceSubClass

bInterfaceProtocol:				0x00

iInterface:						0x00

*!*ERROR:  0xFF is the prerelease USB Video Class ID

*!*CAUTION:  This is an undefined bInterfaceSubClass


===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x03

bAlternateSetting:				 0x00

bNumEndpoints:					 0x03

bInterfaceClass:				   0xFF  -> Vendor Specific Device

bInterfaceSubClass:				0x00

*!*CAUTION:	This appears to be an invalid bInterfaceSubClass

bInterfaceProtocol:				0x00

iInterface:						0x00

*!*ERROR:  0xFF is the prerelease USB Video Class ID

*!*CAUTION:  This is an undefined bInterfaceSubClass



===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x04

bAlternateSetting:				 0x00

bNumEndpoints:					 0x02

bInterfaceClass:				   0x08  -> This is a Mass Storage USB Device Interface Class

bInterfaceSubClass:				0x06

bInterfaceProtocol:				0x50

iInterface:						0x00


===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x05

bAlternateSetting:				 0x00

bNumEndpoints:					 0x01

bInterfaceClass:				   0x02  -> This is Communications (CDC Control) USB Device Interface Class

bInterfaceSubClass:				0x06

bInterfaceProtocol:				0x00

iInterface:						0x05

	 English (United States)  "CDC Ethernet Control Model (ECM)"

  -> This is a Communications (CDC Control) USB Device Interface Class


===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x06

bAlternateSetting:				 0x00

bNumEndpoints:					 0x00

bInterfaceClass:				   0x0A  -> This is a CDC Data USB Device Interface Class

bInterfaceSubClass:				0x00

bInterfaceProtocol:				0x00

CAUTION:  This may be an invalid bInterfaceProtocol

iInterface:						0x00


		  ===>Interface Descriptor<===

bLength:						   0x09

bDescriptorType:				   0x04

bInterfaceNumber:				  0x06

bAlternateSetting:				 0x01

bNumEndpoints:					 0x02

bInterfaceClass:				   0x0A  -> This is a CDC Data USB Device Interface Class

bInterfaceSubClass:				0x00

bInterfaceProtocol:				0x00

CAUTION:  This may be an invalid bInterfaceProtocol

iInterface:						0x06

	 English (United States)  "CDC Ethernet Data"

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.