Hey everyone, just finished installing Ubuntu to my dell mini 10v netbook. I really like it so far but I have hit a problem that may be a potential deal breaker. Has anyone running Ubuntu 9.10 been able to tether their phone to their computer?. It does not seem to connect to my phone running this app for me. It sees the SSID, and i tell it to connect, and then I just get that circle thing for a couple of minutes then it gives up and connects to my main router if its in range.
Anyone have any ideas? I'm not sure if its Ubuntu or the app, it worked perfect with XP
I don't run Ubuntu on my netbook so it may be slightly different, but I have it working great on mine running Arch Linux. Wifi tether uses an Ad-Hoc mode where most routers/access points use Infrastructure mode. You may have to tell network-manager or whatever controls your wireless settings to use Ad-Hoc. If that doesn't work you could set it up manually through the command line or make a little script with those commands to do it so you don't have to type them in every time.
thanks for the reply. I did some searching and came across this page http://www.ubuntugeek.com/creating-an-adhoc-host-with-ubuntu.html and i hooked my phone up to my windows computer, copied the info verbatim to my ubuntu netbook setting up a manual connection like that page suggested and it says it connects, but my phone doesnt show anything is connected and it wont go online
I am able to tether just fine via my Dell mini9 running Ubuntu 9.10. Are you able to connect to other networks?
yeah i can connect to my home fios router just fine
FoxRacR17 i was having the same issues with my dell 1501 laptop.. Looks like your laptop might be using the bcm43xx chip-set from broadcom which doesn't support ad-hoc fully native yet on all cards.
from http://forum.xda-developers.com/showthread.php?p=1863357#post1863357
Keo-Keo said:
I was having issues trouble shooting WMWifiRouter and Ubuntu.
I couldn't pin down if it was Ubuntu or WMWifiRouter which was having the problem connecting.. I could see the Ad-Hoc network in Ubuntu when i would try to connect it would just hang. I played with all the settings in WMWifiRouter to no avail.
Turns out it was my wireless driver.
https://help.ubuntu.com/community/WifiDocs/Adhoc
http://forum.xda-developers.com/showthread.php?p=1863357#post1863357
I had to revert back to Ndiswrapper.. But it worked!!! Those having Linux issues check the driver.. I didn't have a windows box with wireless to check.. So took me longer hopefully this might save you some time!
Click to expand...
Click to collapse
https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper
Try Ndiswrapper from the windows drivers on HP's site. Let us know the results..
I'm having this problem with an atheros 5G chipset
Thanks for the replies guys, i got it fixed. I saw people saying to try the netbook remix version of ubuntu so I went ahead and installed it. At first it wasnt detecting any hardware drivers so it wasnt even giving me the option to install drivers for my wireless this time. But i went into terminal (with my ethernet cord plugged in and netbook connected to the internet) and issued "sudo apt-get update" and it went thru and downloaded a bunch of stuff that took a while, and then i went back to restricted drivers and this time I had TWO options for my wireless card, one that was licensed propitiatory from broadcom themselves labeled "Broadcom STA wirless driver" and one that was licensed as free and labeled "Broadcom B43 wireless driver" I installed the STA one and now my netbook connects perfectly to my hero and i can go online again thru my phone. Hope this helps you guys out
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.
Hi,
Recently I made an installation of the Infused ROM 2.2.3 and Infusion OC kernel on my device, but I can´t make any USB connection (mass storage) to work properly on Windows XP SP3 with Samsung Modem installed, and Samsung SGH-I997 drivers too, Kies installed and etc... when device connects and show the 2 external units, and when begin to copy files between PC and phone device disconnects automatically, and sometimes freezes the entire windows explorer... what I´m doing wrong?
This is both in Windows XP SP3 and Mac OS X 10.6.8, in mac, device simply doesn´t appears... notice that Kies on mac is on version 1.0... and in Windows is on 2.+...
rikochet33 said:
Hi,
Recently I made an installation of the Infused ROM 2.2.3 and Infusion OC kernel on my device, but I can´t make any USB connection (mass storage) to work properly on Windows XP SP3 with Samsung Modem installed, and Samsung SGH-I997 drivers too, Kies installed and etc... when device connects and show the 2 external units, and when begin to copy files between PC and phone device disconnects automatically, and sometimes freezes the entire windows explorer... what I´m doing wrong?
This is both in Windows XP SP3 and Mac OS X 10.6.8, in mac, device simply doesn´t appears... notice that Kies on mac is on version 1.0... and in Windows is on 2.+...
Click to expand...
Click to collapse
Drivers are not necessary for USB mass storage mode.
Are XP and MacOS on the same dual-boot machine or are these different machines?
I know one of the ports on my Asus laptop is weird and constantly disconnects the phone - it's limited to just one port and the rest work fine. Maybe you have something similar.
Entropy512 said:
Drivers are not necessary for USB mass storage mode.
Are XP and MacOS on the same dual-boot machine or are these different machines?
I know one of the ports on my Asus laptop is weird and constantly disconnects the phone - it's limited to just one port and the rest work fine. Maybe you have something similar.
Click to expand...
Click to collapse
I have an iMac with Mac OS X 10.6.8 (x64) Bootcamp and WinXp (x86) installed, primary boot system is XP SP3, well... I´ll check usb ports, hope this helps to solve this...
in my office machine (HP Windows XP Pro x86) I have kies and drivers installed too, but this machine works so fine all the time, when I connect the phone, explorer displays the two units and it can copy/paste files between PC/phone without disconnecting, connection is stable...
... maybe I should get the Samsumg i-9000 drivers instead of SGH-i997 due to I´m on Infused 2.2.3??
What the hell is Windows XP?
Sounds like a driver conflict kies doesn't play well with win 7 64. I know from personal experience
Try uninstalling all drivers and kies then reinstall drivers only, I think xp has generic drivers for usb mass storage so if you just need that then connect it without installing driver's.
Also make sure your data cable is good. Try a new one. They are cheap on Amazon
Sent from my SAMSUNG-SGH-I897 using xda premium
shadow65781 said:
Sounds like a driver conflict kies doesn't play well with win 7 64. I know from personal experience
Try uninstalling all drivers and kies then reinstall drivers only, I think xp has generic drivers for usb mass storage so if you just need that then connect it without installing driver's.
Also make sure your data cable is good. Try a new one. They are cheap on Amazon
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Since it affects XP and MacOS on the same dual-boot machine but doesn't affect his work machine - I suspect it's a USB port problem.
Try this...
Were you able to go into mass storage mode prior to flashing the ROM?
If so, maybe your USB Ports are looking for something that to them isn't there...every time that you connect a usb device, your computer creates a record in the usbstor section of the registry. You can manually delete these by using regedit and heading to the key:
HKEY_LOCAL_MACHINESYSTEM\CurrentControlSet\Enum\USBSTOR
Remember that making changes to your registry can have some undesired results, but this one is pretty safe.
Alternatively, you can go to this site http://www.nirsoft.net/utils/usb_devices_view.html and use USBDeview to disable any old keys or such.
Don
maybe... I don´t know why but its on both systems on iMac machine, device attempts to connect and a milisecond after that, connection rejects and reconnects then reject a bout a three times like it was shortcircuit... like I was saying, in my HP (work machine) works like a charm, even in USB debugging mode, or not, so...
wvmedic said:
Were you able to go into mass storage mode prior to flashing the ROM?
If so, maybe your USB Ports are looking for something that to them isn't there...every time that you connect a usb device, your computer creates a record in the usbstor section of the registry. You can manually delete these by using regedit and heading to the key:
HKEY_LOCAL_MACHINESYSTEM\CurrentControlSet\Enum\USBSTOR
Remember that making changes to your registry can have some undesired results, but this one is pretty safe.
Alternatively, you can go to this site http://www.nirsoft.net/utils/usb_devices_view.html and use USBDeview to disable any old keys or such.
Don
Click to expand...
Click to collapse
I will try it and see what will happens... what could it be?
a driver problem?
another thing that I forget to mention is that I installed drivers manually, actually I live in a block without any wi-fi network! and my Windows XP could not get drivers via Microsoft Update, so, I don't know if this is a factor too
Hey folks, i have a Dell Inspiron N5050 here, and it had no OS on it, so i put Windows 7 on it, and the wireless adapter is not recognized(doesn't show up in device manager). Obviously the driver won't install because the hardware isn't recognized by Windows(i got the driver from the Dell website). i was able to install the ethernet driver, so i can get online that way. I should also add that wifi works out of the box in Linux Mint booted off a USB stick. Also, wifi works fine on other machines with the same copy of Windows 7.
Linux will be my main OS, but does anyone know how to get Windows to recognize the wireless adapter?
The other thing i've noticed is that Network Controller doesn't have a driver installed, and the device is unknown and a driver can't be found,
I've definitely been scouring the internet as i always do, but haven't found the fix yet. Thanks in advance.
I got it working, the driver from Dell's website didn't work, it was a Broadcom i believe, but i found the driver for the standard Dell wireless card, and it found the hardware upon installing.
Hi! My name is Recoder. I recently brought a new Google Nexus 5 (16GB Black) and have a Tata Docomo 3G Connection (India).
I would actually like to Reverse Tether my Phone (so as to get my PC Highspeed internet on my phone, since the mobile network is a bit choppy at times, and the connection times out very frequently). But in order to reverse tether (without Root), I need to get my Phone recognized as a Tethered Mobile on my PC.
I am actually a beginner in Tethering.
1. I connected the Phone to PC via USB, and clicked on USB Tethering. (it says tethered), but my PC keeps on installed Remote NDIS Driver forever and finally says Driver not installed nor does it recognizes my Phone. (It Gets Recognized as a PTP, MTP Device)
2. I have USB Debugging Enabled (don't know whats that for). Disabling it does not make any difference.
3. I tried the Google USB Driver but it does not have the driver for Nexus 5, and with usb debug enabled, it comes as a Samsung Android ADB Composite Device.
So Please help my how to Tether my Phone (Step by step if possible, since its my first time)
I don't want to root my new Nexus.
With Warm Regards,
Super Recoder