Verizon Motorola Droid
I am a paid customer of Tether for Blackberry. I just recently purchased the Verizon Motorola Droid to replace my Verizon Blackberry Storm 1. The Storm 1 worked almost flawlessly. My pin for the BB is recorded in my panel here on the site. I received an email from Tether on March 9, 2010 about the Android Beta and it's launch. I have followed the instructions to a tee of:
1. Uninstall existing Tether software - and reboot.
2. Enable USB debugging on the Droid
3. Downloaded/installed Tether for Android (http://www.tether.com/a/setup.exe) to my desktop
4. Connected Motorla Droid when asked to do so
5. It installed the Tether for Android app on my Droid
6. Disabled ALL connections both wireless and wired
6. Start Tether on the PC and select Android USB
7. Start Tether on Android
Then I see some activity on the Tether on desktop, and on the Android it tells me it is connected successfully with PC over USB.
But no matter what, I cannot browse the Internet. I cannot ping. I cannot do nslookups, nothing.
Several minutes later on the Droid, it says: "Could not create the TCP socket: Java.net. SocketException: The operation timed out." It says this over and over and over again.
Any ideas?
Thanks so much in advance.
What is your Android OS revision?
Last week, I was running Android 2.01. I have since upgraded to 2.1. Same result no matter what :(
This likely means your PC is the culprit, what is your PC OS?
Hi there AutoBot,
I have tried three other computers: 2 - windows xp pro, and the other one is a computer running windows vista.
It should be noted that a day or so after I could not get Tether to work, I downloaded another product and it works beautifully. I have been using this other product since then.
I am a loyal client of Tether and have been so for well over a year now- since Tether was in BETA. Just before they went "public" so to speak, they even gave us a chance to "prepay" and I did just that too! ;-)
I am hoping this is resolved ASAP, and I know there are going to be bumps in the road as the Android version is BETA, but beta or no beta, I would still like it to semiwork though ;-)
Regards,
Statustray
Ok so the three other computers sort of rules out the possibility of it being PC OS related.
Is your Droid rooted?
Yes my droid is rooted, but I rooted it a few days ago. This issue of mine has been occuring since day 1 with the Droid (prior to rooting).
I just ordered a Motorola Droid and it will be delivered on May 4, I should be able to better assist you then.
I was just wondering if your Droid was rooted, Tether should still function on a rooted device.
How long does your battery hold out when you tether over wifi using one of the other tethering methods (if you do)?
It appears as if this may be a driver issue, could you download the USB drivers for Android and install them then try Tether again?
http://developer.android.com/sdk/win-usb.html
I got the Droid, enabled USB debugging, uninstalled the old Tether, ran the Tether for Android setup with the Droid plugged in over USB and that was that.
My Droid does say the following a few times:
"Failed to open the TCP input stream: java.net. SocketException: Socket is closed"
But the Moto Droid is working fine even with the errors.
Mine still is not working. I already tried to remove and reinstall the Motorola Droid USB drivers with no success. I get the same error messages you are getting, but I cannot ping, nor do anything. No data is getting pushed back and forth.
Could you tell me what is the revision of the following files on your PC and do you only have one of each?
AdbWinApi.dll
AdbWinUsbApi.dll
adb.exe
i'm getting the same tcp java error, i still can do some browsing but cant watch video or download torrents... any suggestions?
I have emailed you.
I have installed Tether on my Vista laptop to use with my Moto Droid 2.1 and neither my desktop nor my Droid see each other.
Do you have USB Debugging enabled on your Droid?
Do you see an ADB interface in the Windows Device Manager when your Droid is plugged in over USB to your PC?
I did not enable debugging because I didn't see that in the instructions. Once that was enabled it worked.
Thank you for your update.