seanhold3n / android-wifi-tether

Automatically exported from code.google.com/p/android-wifi-tether
0 stars 0 forks source link

Does not work on Vodafone (Huawei) 845 #497

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Which device (manufacturer, type)? Vodafone (Huawei) 845

Which firmware is installed? 2.1 update 1

What version of wireless tether are you using? 2.0.5 pre 7

What steps will reproduce the problem?
1. Connecting via Wifi from OSX after enabling tethering on Android
2. OSX keeps waiting for IP adress until timeout, then assumes a default adress
3. Wifi tether would indicate no attached device

What is the expected output? What do you see instead?
not working, eventhough the log indicates that tethering is running

Please provide any additional information below.
On Bluetooth, effect is exactly the same.
Barnacle does run properly, but only if I reduce the MTU to 1260 on the OSX side

Original issue reported on code.google.com by gabor.we...@gmail.com on 7 Aug 2010 at 10:34

GoogleCodeExporter commented 9 years ago
This is a comment from here:
http://code.google.com/p/android-wifi-tether/wiki/FAQ
by a user named "n8vision"
"Mac OS X Users: I'm using a rooted Motorola XT800 in China. This device is 
similar to the Motorola Droid. Tried for a long time to get android-wifi-tether 
to work with no success. Finally discovered that setting up an ad-hoc wireless 
network of the same name and channel on your mac FIRST then turning on 
wifi-tether works perfectly!

I'm on Mac OS X 10.6 on a Macbook Pro and using Android 2.1 device. Hope this 
helps someone!"

Please try that out ...

Original comment by harald....@gmail.com on 7 Aug 2010 at 3:53

GoogleCodeExporter commented 9 years ago
I checked this trick and can confirm that it does work with the Vodafone/Huawei 
845 and OSX 10.5.8 (or 10.6.3). But after a bit of surfing, the connection will 
hang.
Another test with an iPod Touch showed that the connection does work without 
any flaws with the same Android device. Seems, there is some incompatibility 
with the OSX protocol stack.

Original comment by gabor.we...@gmail.com on 7 Aug 2010 at 5:00