Database Info

[KERNEL] USB tethering support for android-wired-tether (12/20/10)

2/22/11 Update: Froyo kernels include tethering support, so this patch is no longer necessary. A Froyo-compatible Wired Tether client is available here.
12/20/10 Update: Added patch to wired-tether client to clamp MSS. Fixes stalled connections when the network breaks fragmentation support.
10/18/10 Update: The MixUp-20101024-847 kernel now includes USB tethering (RNDIS) support. If you have this kernel installed, you should be able to USB tether by installing the modified android-wired-tether client attached here.
Troubleshooting Update: If the client force closes on you and you're using a ROM with android-wifi-tether preinstalled, then there is a library conflict. Remove android-wifi-tether from /system, and most importantly, delete (or rename) /system/lib/libnativetask.so, then android-wired-tether should work. If you want both wifi & wired tether, reinstall android-wifi-tether from the market. This will make each application use its own library so there's no more conflicts. See this post for more details.
Attached is a patch to the DI18 kernel sources to enable USB tethering support with android-wired-tether. Kernel developers, please feel free to include this patch in your kernel builds. It requires no configuration changes.
This patch requires use of a modified wired-tether agent (at least, until the change is commited upstream). A modified build of wired-tether is also attached, along with the source patches against upstream v1.4 (SVN r34).
Also attached is a build of the stock DI18 kernel with the kerel patch applied. It's compiled with CodeSourcery Lite 2009q3-68 with stock config options, stock initramfs (so no root, no clockworkmod support). It's intended for folks who want to try this right away, and know how to restore their old kernel if need be.
Directions:
To install the test kernel, look for a copy of redbend_ua in any of the kernel update.zip packages, install with:
Code:
adb push redbend_ua /data/local/tmp
adb push zImage /sdcard
adb shell
su
chmod 755 /data/local/tmp/redbend_ua
/data/local/tmp/redbend_ua restore /sdcard/zImage /dev/block/bml7
Then install the attached wired-tether-1.4-epic-2.apk. Tethering may be used with "USB debugging" enabled or disabled. However, neither mass-storage support nor ADB will be availble while actively tethering. To use:
(Windows only) Install the Samsung USB drivers. No other drivers are needed for Windows 7, and I think Windows XP SP3.
Make sure the USB cable is unplugged before starting the tether client.
Start "Wired Tether" and "Press to start tethering."
Grant the Superuser Request (if your su requires it).
Make sure tethering has started, you should see green/red "Down/Up" numbers at the bottom of the screen.
Attach the USB cable.
Select "Charging" mode if the "Select USB mode" menu comes up (it won't if USB debugging is enabled).
Tether!
When finished:
Detach the USB cable.
"Press to stop tethering."
Grant the Superuser Request (if your su requires it).
Exit the "Wired Tether" program.
Reattach the USB cable if you want to use mass-storage or ADB.
Technical details (for those interested, otherwise ignore):
The Epic kernel already provides RNDIS USB support in the USB gadget driver, however the host-side RNDIS interface is never presented. The kernel patch adds a sysfs variable that, when enabled, configures the host-side USB to exlusively present the RNDIS interfaces, and when disabled, reconfigures the host-side USB back to the previous state, either mass-storage (actually typically "KIES" mode) or ADB. You may toggle this variable manually, for example, if you wanted to use the RNDIS interface for other purposes. Just be sure to toggle when the USB cable is unplugged:
Code:
su
echo -n 1 > /sys/devices/virtual/sec/switch/rndis_enable # Enable RNDIS.
echo -n 0 > /sys/devices/virtual/sec/switch/rndis_enable # Disable RNDIS, reenable UMS or ADB.
The wired-tether patch simply toggles the sysfs varible upon starting and stopping tethering. Since the host-side USB interface will only reconfigure upon cable reinsertion (I think?), this is why the cable must be attached/detached only while tethering is enabled.
Note that the host-side RNDIS interface is exclusively presented--it may not be used simultaneously with mass-storage or ADB. This is a limitation of the Samsung Windows driver and will not be fixed. The previous version of the kernel patch (10/8) did present RNDIS alongside ADB, which is a mode of operation generally supported by Linux. However, the Samsung drivers need to be modified to support this mode (necessitating a reinstall) and as it turns out, driver bugs presents the along-side configuration from actually working. Because of this, and reports from Ubuntu users of losing ADB with the previous version, this patch only uses "blessed" host-side USB configurations.
Nitty grity details:
I'm not precisely sure what "Tethered Mode" is, that shows up in the menu when you plug in a USB cable with debugging disabled. From the USB gadget driver code, it appears to disconnect one (or both) of the 3G/4G modems and presents it over the USB interface directly, not allowing it to be shared with the phone. This may use the RNDIS interface (hence why it's "supported" in the first place), or may expose a serial UART. I've never tried it, and I'm uncertain (from the driver code) that it actually works.
Amusingly enough, it should be possible to enable the RNDIS interface even with the stock kernel. However, the gadget driver code is very buggy, and the existing sysfs interfaces do not operate as advertised. Even if you "game the bugs" to work around them, you'll lose ADB support until the phone is restarted. Since I would have to modify the kernel to fix these bugs, I decided to just present a new interface that mirrors the behavior of ADB mode, to keep the patch simple to maintain.
If you want to follow along though, the two relevant parts of the USB gadget driver are "adb_ums_acm_mtp_rndis.c" and "fsa9480_i2c.c" (in "drivers/usb/gadget"). "adb_ums_acm_mtp_rndis.c" contains host-side USB interface configurations for UMS mode (default), ACM/UMS/ADB (USB debugging), ACM/MTP (disabled), MTP (disabled), RNDIS (basically unused), and ACM only (disabled). The two functions that appear to switch between configurations are enable_adb() and enable_askon().
At first I thought enable_adb() was used by "USB debugging" mode, and enable_askon() by the "Charging/Mass Storage/Tethered Mode" menu, but this isn't the case. Turns out enable_adb() is the only of the two actually used, and enable_askon() is buggy dead code that, for example, doesn't set the current USB configuration status so it's not possible to switch back to the previous configuration.
"fsa9480_i2c.c" contains, among other things, a variety of show/store functions exported as (world-writeable!) sysfs variables in /sys/devices/virtual/sec/switch. I can't tell if these were intended for internal debugging only, or if they were intended to be used by userspace (e.g., the "Select USB mode" menu). The two interesting interfaces here are UsbMenuSel and AskOnMenuSel, which should take a USB device configuration nickname (e.g., "UMS", "KIES", "VTP") and set the host-side USB configuration accordingly. However, the "if/else if/else" lists in both functions are broken, and the "else" clause is often executed when it shouldn't. Interestingly enough, the default host-side USB mode appears to be "KIES", although I'm unsure if that's intentional or due to this bug. But this doesn't matter since the ACM/MTP configuration is disabled and UMS is used in its place.
In other words, the USB gadget driver code is a misleading rats nest of buggy/dead code. It's a wonder it actually works in the first place. I really hope the rest of the device-specific code isn't that bad, but I'm afraid to look.
Mirror links (does not require forum login):
kernel_rndis_enable.diff
kernel_rndis_enable.zip
wired-tether-1.4-epic-2.apk
wired-tether_use_stable_api.diff
wired-tether_clamp_mss.diff
wired-tether_rndis_enable.diff

Great! I was working on a patch for this earlier but didn't have the time! Thanks, t'will be in my next kernel

Sweet. Was waiting for dev to bring this so i can install wired tether

saWeet, can't wait for your updated kernel Genius!

Any ideas?
C:\Users\*****>adb shell
$ su
su
# /data/local/tmp/redbend_ua restore /sdcard/zImage /dev/block/bml7
/data/local/tmp/redbend_ua restore /sdcard/zImage /dev/block/bml7
/data/local/tmp/redbend_ua: permission denied
EDIT: Had to chmod redbend_ua to 777 first!

remount
did you remount the drive into read/write mode?
adb shell remount rw

Has any more testing been done with this? Has it been incorporated in Genius' kernel?
Sent from my SPH-D700

Forcystos said:
Has any more testing been done with this? Has it been incorporated in Genius' kernel?
Sent from my SPH-D700
Click to expand...
Click to collapse
Well, it is incorporated but I haven't released yet. I'm still adding some stuff. See my GitHub if you're curious.

Has the download speed been tested using this method? I currently get 1MB using wireless tether and would like to know if my laptop would be able to surf the net faster through this kernel and a USB cord.

The Google Code FAQ says "The client needs to support RNDIS. Windows Vista/7 comes with RDNIS-support out of the box." However when I plug in my Epic it says it needs drivers for RNDIS, and Windows Update does not find any. Anyone know where to get these drivers?
Edit: I'm on Windows 7 64-bit and Herver's Baked Snack 1.3 kernel.

ragnarokx said:
The Google Code FAQ says "The client needs to support RNDIS. Windows Vista/7 comes with RDNIS-support out of the box." However when I plug in my Epic it says it needs drivers for RNDIS, and Windows Update does not find any. Anyone know where to get these drivers?
Edit: I'm on Windows 7 64-bit and Herver's Baked Snack 1.3 kernel.
Click to expand...
Click to collapse
It's a lie.
http://www.microsoft.com/downloads/...FamilyID=46f72df1-e46a-4a5f-a791-09f07aaa1914
You need WMDC on Vista/7.

Firon said:
It's a lie.
http://www.microsoft.com/downloads/...FamilyID=46f72df1-e46a-4a5f-a791-09f07aaa1914
You need WMDC on Vista/7.
Click to expand...
Click to collapse
I plugged in my Epic via USB (with debugging mode on), ran the file from that link (drvupdate-amd64.exe), and I get an error message pop-up saying "Device driver software was not successfully installed" and under details it says
RNDIS Communications Control X No Driver found
Unidentified Device X Device unplugged
I tried this a few times, unplugging and replugging my Epic in. I also tried running the exe without the phone plugging in.

ragnarokx said:
I plugged in my Epic via USB (with debugging mode on), ran the file from that link (drvupdate-amd64.exe), and I get an error message pop-up saying "Device driver software was not successfully installed" and under details it says
RNDIS Communications Control X No Driver found
Unidentified Device X Device unplugged
I tried this a few times, unplugging and replugging my Epic in. I also tried running the exe without the phone plugging in.
Click to expand...
Click to collapse
Reboot, install the driver, reboot again and try plugging it in? Maybe you need the ADB drivers installed too.

I've updated the OP with a new kernel/patch as well as a modified version of android-wired-tether to support the new patch. I've tested it in Windows 7 with the Samsung USB drivers installed (you don't need WMDC as it turns out) and it works.
If you tried the previous kernel, you may want to uninstall/reinstall the Samsung drivers to wipe out any stale device configuration.
Sorry about that folks, I just assumed the old (simpler) patch would work on Windows, but it's very much not the case. Apparently RNDIS support on USB composite devices is flaky, and the Linux USB documentation was recently updated reflecting this.

mkasick is it possible to get a video tutorial of how to get this to work (noob)

docdg said:
mkasick is it possible to get a video tutorial of how to get this to work (noob)
Click to expand...
Click to collapse
Sorry I don't have a video camera.
Anyways, the latest MixUp kernel has USB tethering support. So if you install that, all you need to do is install wired-tether-1.4-epic-1.apk from the OP and follow the directions for starting tetherig half-way down the post; which, in short is just starting the tethering client, tapping the screen to start tethering, the connect your USB cable.
If you're running Windows, you also need the Samsung USB drivers installed (see OP). But if you're tethering with the same computer you rooted the phone with, that should already be done.

Finally got wired tether to work. When I compare the bandwidth speeds with those of easy-tether the speed seems slower. What is the best FREE tethering solution?

docdg said:
When I compare the bandwidth speeds with those of easy-tether the speed seems slower.
Click to expand...
Click to collapse
I suppose this is possible, particularly if your OS's RNDIS driver isn't very good.
I did some benchmarking. I can send data over RNDIS to my phone at 18.7 MiB/s (157 Mb/s) and receive at 14.5 MiB/s (122 Mb/s). That's a little slow relative to the USB 2.0 maximum (480 Mb/s).
However, it's quite a bit faster than the rate I can transfer over 802.11 directly: 2.2 MiB/s (18 Mb/s) sending, 2.0 MiB/s (16 Mb/s) receiving. Tethering USB <-> 802.11 is bounded to about those speeds as well.
I haven't benchmarked 3G, but my past experience suggests is no faster than 802.11. In which case the RNDIS speed should be plenty sufficient unless there's a driver problem.

Host mode support on Nexus S developments?

hey guys came across an interesting discussion! i cant post in dev boards yet... however, this guy provides some answers, maybe some of the elders may want to take a look. EDIT: i cant even post an outside link read code box i guess...
Code:
Hi All,
I've spent some time today dithering on the Nexus S and host mode and I think the way to approach this is different from the Nexus 1 host driver hack.
The Nexus S uses a Fairchild USB switch (fsa8480) to detect device connections. I believe the point is to allow the device to handle multiple functions like charging, UART and USB access simultaneously.
The Switch will detect OTG connections. Plugging in a microB to A convertor with pin 4 grounded to 5 causes the fas9480 driver to wake up and report an OTG attachment. It also calls into the S3C_UDC_OTG driver to configure it up and create a vbus session. (start charging)
The problem is that in the Nexus S kernel, this driver is device mode only. There is no code to put it into Host mode and the chip can only be in Host or device mode. It can't do both at the same time. Also, the few people that have tried to use host drivers have found that they must disable the device code (including charging capability) to get the hubs to enumerate.
It appears that the OTG core in the samsung part is from DesignWare. There are synopsis reference drivers up here:
*************check edit reason for driver link*****************
The register map appears the same, and the code supports host and device mode as well as dynamic switching based on HNP negotiation.
It seems like the best way to approach this would be to integrate this code and use the fsa9480 discovery as the hook to force host mode (when OTG is detected) or device mode when other devices are detected.
The demo we were under the gun to support will probably just use Nexus one, however I thought the rest of you guys would want to see this. I think if done right, you could have host mode, gadget mode and charging all in the same kernel.
Steve
--
Steve Modica
CTO - Small Tree Communications
---not my words, or even me. just though people may want to know!

can't connect the Tf700 as mass storage

Hi,
I just received my TF700 and trying to connect to my XP PC to copy music and movies on to it.
My computer does not succeed in installing the necessary drivers to make it look like DOK.
What am I doing wrong? This should be a simple task (how will I be able to fill my 64GB ?)
Thanks,
edit: after installing PC suit from TF101 support page it works.
But why can't we charge the TF700 via USB....?

kubeb said:
Hi,
I just received my TF700 and trying to connect to my XP PC to copy music and movies on to it.
My computer does not succeed in installing the necessary drivers to make it look like DOK.
What am I doing wrong? This should be a simple task (how will I be able to fill my 64GB ?)
Thanks,
edit: after installing PC suit from TF101 support page it works.
But why can't we charge the TF700 via USB....?
Click to expand...
Click to collapse
I could be wrong but iirc i've read somewhere that in order to charge it from USB you have to power off your device first.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

kubeb said:
Hi,
I just received my TF700 and trying to connect to my XP PC to copy music and movies on to it.
My computer does not succeed in installing the necessary drivers to make it look like DOK.
What am I doing wrong? This should be a simple task (how will I be able to fill my 64GB ?)
Thanks,
edit: after installing PC suit from TF101 support page it works.
But why can't we charge the TF700 via USB....?
Click to expand...
Click to collapse
There's simply not enough power coming from the USB port.
The reason why connecting failed is because XP doesn't support the MTP connection, which the Infinity uses, from the beginning.
Sent from my Galaxy Nexus using xda premium

kubeb said:
Hi,
I just received my TF700 and trying to connect to my XP PC to copy music and movies on to it.
My computer does not succeed in installing the necessary drivers to make it look like DOK.
What am I doing wrong? This should be a simple task (how will I be able to fill my 64GB ?)
Thanks,
edit: after installing PC suit from TF101 support page it works.
But why can't we charge the TF700 via USB....?
Click to expand...
Click to collapse
Just for reference for new users reading through this thread: you cannot access an Android 4.x+ device as a USB Mass Storage device AT ALL -- this was sacrificed for the more stable and safe MTP connection. The latter should work if you install the drivers, as the OP already has found out.

MartyHulskemper said:
Just for reference for new users reading through this thread: you cannot access an Android 4.x+ device as a USB Mass Storage device AT ALL -- this was sacrificed for the more stable and safe MTP connection. The latter should work if you install the drivers, as the OP already has found out.
Click to expand...
Click to collapse
I would have to respectfully disagree. My SGS2 running ICS has the USB mode ability. Settings / More (under data usage) / USB Utilities / USB mass storage.click the button, connect the USB cable, and there ya go!
Unfortunately, this option is either disabled or nonexistant in the transformers.

pileot said:
I would have to respectfully disagree. My SGS2 running ICS has the USB mode ability. Settings / More (under data usage) / USB Utilities / USB mass storage.click the button, connect the USB cable, and there ya go!
Unfortunately, this option is either disabled or nonexistant in the transformers.
Click to expand...
Click to collapse
I reckon that's because the SGSII is not a original 4.0 device. It came with 2.3 on the market.
However I don't know if the manufacturers are still allowed to use it in their new devices.

pileot said:
I would have to respectfully disagree. My SGS2 running ICS has the USB mode ability. Settings / More (under data usage) / USB Utilities / USB mass storage.click the button, connect the USB cable, and there ya go!
Unfortunately, this option is either disabled or nonexistant in the transformers.
Click to expand...
Click to collapse
This is because the SGS2 was not released with ICS. It was upgraded to ICS. The real reason why UMS is not available on native ICS devices (aside from mounting external SD cards with UMS) is because Google decided to use one large volume for the internal storage instead of several. Devices that were upgraded to ICS after being release still have several volumes instead of one. Trying to rewrite the partition table during an update would be destructive, causing the loss of all data, and no manufacturer would want to do that to their customer's devices.

darkkterror said:
This is because the SGS2 was not released with ICS. It was upgraded to ICS. The real reason why UMS is not available on native ICS devices (aside from mounting external SD cards with UMS) is because Google decided to use one large volume for the internal storage instead of several. Devices that were upgraded to ICS after being release still have several volumes instead of one. Trying to rewrite the partition table during an update would be destructive, causing the loss of all data, and no manufacturer would want to do that to their customer's devices.
Click to expand...
Click to collapse
When updating with kies it would copy personal data to the computer and restore that data after the update was complete. I wonder if the S3 has this functionality (usb mode). I know with the S2 there was a big deal about upgrading to ICS because it had to repartition everything, lots of warnings about losing data on the phone, never stopped us we just made backups and away we go. I dont see how the prime is much different, the USB mode COULD be put into it the same way it was put into the samsung roms, doesnt even need to be default, just there for those people like me that prefer it.

kubeb said:
Hi,
I just received my TF700 and trying to connect to my XP PC to copy music and movies on to it.
My computer does not succeed in installing the necessary drivers to make it look like DOK.
What am I doing wrong? This should be a simple task (how will I be able to fill my 64GB ?)
Thanks,
edit: after installing PC suit from TF101 support page it works.
But why can't we charge the TF700 via USB....?
Click to expand...
Click to collapse
Works fine under Win 7, tablet connected as media device, and i can confrim that the charging icon is active when connected and in config menu under battery says: charging.
kind regards,

profiler270 said:
Works fine under Win 7, tablet connected as media device, and i can confrim that the charging icon is active when connected and in config menu under battery says: charging.
kind regards,
Click to expand...
Click to collapse
As I said XP doesn't support MTP devices. Win 7 does it though.
Sent from my Galaxy Nexus using xda premium

pileot said:
I would have to respectfully disagree. My SGS2 running ICS has the USB mode ability. Settings / More (under data usage) / USB Utilities / USB mass storage.click the button, connect the USB cable, and there ya go!
Unfortunately, this option is either disabled or nonexistant in the transformers.
Click to expand...
Click to collapse
As said above, MTP mode is standard in ICS and UMS is no longer supported (and indeed the reason was the single-volume approach, and the fact that MTP makes the filesystem available to the host computer without the need for unmounting, and thus eliminates the risk for introducing filesystem errors on the host -- the Android system keeps everything under control and access to the filesystem is transparent to the host.)
Obviously, anything can be hacked together, and there are apps that seem to able to provide UMS mode.
Not a matter of disagreeing, but unfortunate reality.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
pileot said:
When updating with kies it would copy personal data to the computer and restore that data after the update was complete. I wonder if the S3 has this functionality (usb mode). I know with the S2 there was a big deal about upgrading to ICS because it had to repartition everything, lots of warnings about losing data on the phone, never stopped us we just made backups and away we go. I dont see how the prime is much different, the USB mode COULD be put into it the same way it was put into the samsung roms, doesnt even need to be default, just there for those people like me that prefer it.
Click to expand...
Click to collapse
By the way, I strongly prefer UMS mode as well, since the computers at work (hospital) are pretty much closed-off to anything included installing any software or drivers, and they disallow MTP. Previously, I could at least access my SGS2 as a thumb drive, but with my current ROM (RootBox ICS) that's no longer an option.

Nebucatnetzer said:
As I said XP doesn't support MTP devices. Win 7 does it though.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Windows XP does support MTP, but one would need to have Windows Media Player 10 or later installed (WMP10 added MTP).

hello kubeb
If you still searching, refer to my story on this thread:
http://forum.xda-developers.com/showthread.php?t=1861444
wish you succes

[Q] USB Tethering on htc Incredible w/Linaro Optimized CM9

Having a problem getting USB tethering to work on my computer running Windows 7 64-bit. My htc Droid Incredible (Verizon) has Linaro Optimized CM9 (which, by the way, is running very nicely so far). I connected it to the computer and enable tethering on the phone, and heard some Plug and Play connection noises, but when it went to load drivers it said that the RNDIS driver could not be found.
Checking Device Manager, I don't see any new network adapter that references the phone. I do see an Android ADB Interface listed under Android Phones, but there is a yellow exclamation on RNDIS, of course.
Have tried the following, based on suggestions I got on some other forums:
1) Loaded the latest version of HTC Sync to get drivers installed...no go, same issue listed in Device Manager. If I actually launch HTC Sync, it says that no phone is connected.
2) Tried an HBOOT driver from the unrevoked root wiki ... still nothing.
3) Tried installing--in Device Manager--some (but not all) of the different Microsoft RNDIS drivers that are available, but the install does not succeed. Usually says that it could not start the device, or something like that.
I'm really here, though, because someone just stated the following:
"The ROM may be your problem... since cm9 is not officially supported on the incredible...the ROM is a port from another phone, so that could be the cause of your problem... I'd make a nandroid of your current setup and try wired tethering with the official cm7 ROM."
Sounds plausible, I guess, but I would have thought that there would have been something here about this (if there was, I couldn't find it). I also have the nagging suspicion that the issue is on the computer and not the phone. So before I go backing up and changing ROMs, can anyone please confirm or refute as to whether this particular ROM would "break" USB tethering as described above?
Thanks in advance!
Mike
P.S. Wireless hotspot tethering works just fine, by the way. But I would like to be able to tether via USB cable as well.
P.P.S. Tried to post this in the pertinent thread started by mamarley, but I think I'm prohibited from doing so because I am brand new to the forum.

How to enable usb, it's disabled in my college PCs???

Micromax A87

That's a quick way of getting in trouble.
Sent from my LG-P999 using xda premium

Not sure if it is supposed to be disabled on purpose or not.
Assuming you're a local admin and it's a windows machine, you can enable the USB-controller device by going in the control pannel -> devive manager. Locate the USB controller and if disable, right-click on it, enable.
That's also a good way of "reseting" your device if you encounter errors with it.

Yeah, its windows xp sp3... and required hrdwares are also present in the machine.. but it doesn't show any "usb controller" in device manager list(supposed to be there in last)...I installed the chipset drivers in that pc...successfully... but then too not showing the PD.

There are a handful of ways to disable usb in a computer. Easy way would be to unplug it directly from the inside of a PC. It's also possible to disable it through the pc's bios. And it can also be disabled by disabling the driver like the one mentioned above. Also it could be disabled through registry and group policy if on windows machine. There are alot more ways to do it that I didn't mention.

Thanks Riyal, i'll be trying that through bios and..i'll chck if hardwre is unpuged...
Tell u nxt day..

I would first update the usb drivers. I dont know if its your computer or one in a lab or whatever but if its running XP. Its a good chance the drivers havent been updated in awhile. When you say disabled, do you mean when you plug in a usb stick nothing happens or do you see in device manager that its disabled. Also it would only be relative to the motherboard controller if your using a front access usb port, as a back usb port is built in, have you tried other ports? Lastly there is always the bios, bios is probably hasnt been updated in awhile if this is not your computer, but make sure any usb controllers and or legacy usb devices are enabled.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Moved thread to [email protected]

Nizda1 said:
I would first update the usb drivers. I dont know if its your computer or one in a lab or whatever but if its running XP. Its a good chance the drivers havent been updated in awhile. When you say disabled, do you mean when you plug in a usb stick nothing happens or do you see in device manager that its disabled. Also it would only be relative to the motherboard controller if your using a front access usb port, as a back usb port is built in, have you tried other ports? Lastly there is always the bios, bios is probably hasnt been updated in awhile if this is not your computer, but make sure any usb controllers and or legacy usb devices are enabled.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yes, the correct answer and very helpful ...