seanhold3n / android-wifi-tether

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

EVO 4G Froyo update breaks android-wifi-tether #473

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
android-wifi-tether no longer works on EVO 4G (Supersonic) after the Froyo 
update.  The device *does* have the capability to do master mode with the 
kernel present; Sprint's HotSpot works.  android-wifi-tether, when I attempt to 
enable tethering, acts like everything is going OK, but no access point 
actually appears.  Even when I remove the firmware file from 
/sdcard/android.tether, and allow android-wifi-tether to use the new bcm ap 
firmware shipped with the Froyo update, I still get no luck.

Here's a dmesg log from using android-wifi-tether to attempt to set up a 
connection:

[ 3216.484252] wlan: Dongle Host Driver, version 4.218.204.2
[ 3217.784179] serial_get_enabled: 0
[ 3219.035186] mmc0: queuing CIS tuple 0x91 length 3
[ 3219.035888] mmc0: new high speed SDIO card at address 0001
[ 3219.046569] wlan: DHD: dongle ram size is set to 294912(orig 294912)
[ 3219.280456] wlan: firmware version: wl0: Jul 21 2010 09:23:32 version 
4.218.207.0
[ 3219.280456]
[ 3219.416107] wlan: Enter set packet filter
[ 3219.418060] wlan: start to add pkt filter 100
[ 3219.420257] wlan: Enter set packet filter
[ 3219.422302] wlan: start to add pkt filter 102
[ 3219.424621] wlan: Enter set packet filter
[ 3219.426666] wlan: start to add pkt filter 104
[ 3219.431549] wlan: dhd_preinit_ioctls:str=0x6e756c6c207061636b657400
[ 3219.440551] wlan: eth0: Broadcom Dongle Host Driver mac=38:e7:d8:19:ba:fe
[ 3220.784637] serial_get_enabled: 0
[ 3222.474090] wlan: get AP_PROFILE_SET
[ 3222.474487] wlan: wl_iw: set ap profile:
[ 3222.475128] wlan:    ssid = '[...]'
[ 3222.475463] wlan:    security = 'wpa2-psk'
[ 3222.475830] wlan:    key = '[...]'
[ 3222.476470] wlan:    channel = 6
[ 3222.476806] wlan:    max scb = 2
[ 3222.481811] wlan: setting SOFTAP security mode:
[ 3222.482452] wlan: wl_iw: set ap profile:
[ 3222.482818] wlan:    ssid = '[...]'
[ 3222.483154] wlan:    security = 'wpa2-psk'
[ 3222.483795] wlan:    key = '[...]'
[ 3222.484130] wlan:    channel = 6
[ 3222.484466] wlan:    max scb = 2
[ 3222.599487] wlan: wl_iw_set_ap_security: passphase = [...]
[ 3222.627227] wlan: ap setup done
[ 3222.722656] init: untracked pid 1962 exited

And here's what happens when Sprint's software does it:

[ 4616.500610] mmc0: new high speed SDIO card at address 0001
[ 4616.506347] wlan: DHD: dongle ram size is set to 294912(orig 294912)
[ 4616.729125] serial_get_enabled: 0
[ 4616.735137] wlan: firmware version: wl0: Jul 21 2010 09:23:32 version 
4.218.207.0
[ 4616.735137]
[ 4616.870544] wlan: Enter set packet filter
[ 4616.873077] wlan: start to add pkt filter 100
[ 4616.875122] wlan: Enter set packet filter
[ 4616.877380] wlan: start to add pkt filter 102
[ 4616.879730] wlan: Enter set packet filter
[ 4616.881896] wlan: start to add pkt filter 104
[ 4616.889221] wlan: dhd_preinit_ioctls:str=0x6e756c6c207061636b657400
[ 4616.911132] wlan: wl0.1: Broadcom Dongle Host Driver mac=38:e7:d8:19:ba:fe
[ 4618.577758] wds: 0021 @ 01
[ 4618.577880] qmi: wds: network stopped
[ 4618.578155] rmnet_stop()
[ 4618.578887] wds: 0022 @ ff
[ 4618.579010] qmi: wds: DISCONNECTED
[ 4618.645141] wlan:  Got str param in iw_point:
[ 4618.645172]  ASCII_CMD=AP_CFG,SSID=EVO 
19BAFE,SEC=wpa-psk,KEY=8d42b098a24986eeb4979ac7a6f2c117ce551462491782d9139445d6e
032e51b,CHANNEL=0,PREAMBLE=0,MAX_SCB=2,END
[ 4618.645568] wlan: wl_iw: set ap profile:
[ 4618.645660] wlan:    ssid = 'EVO 19BAFE'
[ 4618.645782] wlan:    security = 'wpa-psk'
[ 4618.645965] wlan:    key = 
'8d42b098a24986eeb4979ac7a6f2c117ce551462491782d9139445d6e032e51b'
[ 4618.646087] wlan:    channel = 0
[ 4618.646270] wlan:    max scb = 2
[ 4619.434814] wlan: Set auto channel = 6
[ 4619.437347] wlan: setting SOFTAP security mode:
[ 4619.437530] wlan: wl_iw: set ap profile:
[ 4619.437652] wlan:    ssid = 'EVO 19BAFE'
[ 4619.437744] wlan:    security = 'wpa-psk'
[ 4619.437957] wlan:    key = 
'8d42b098a24986eeb4979ac7a6f2c117ce551462491782d9139445d6e032e51b'
[ 4619.438049] wlan:    channel = 6
[ 4619.438232] wlan:    max scb = 2
[ 4619.441436] wlan:  wsec & auth set 'wpa-psk' (TKIP), result:&d 0
[ 4619.522796] sequans_xxx: WiMAX carrier LOST [ignored]
[ 4619.522979] sequans_xxx: got RX data, card is not asleep
[ 4619.524810] wlan: wake lock 15 secs!
[ 4619.525024] wlan: Link UP
[ 4619.729431] serial_get_enabled: 0
[ 4620.238861] wlan: set AP_MAC_LIST_SET
[ 4620.262542] led_hotspot_status_value = 1
[ 4620.474334] wlan: extra:\B
[ 4620.474334] 5c:42:01:00:01:00:00:00:37:c7:d0:af:60:54:01:00
[ 4620.474365]
[ 4620.578918] wlan: get assoc count 0, ret 0
[ 4620.579040] wlan: resulting str:
[ 4620.579040] 0|
[ 4620.579040]  len:2
[ 4620.579040]
[ 4621.101989] wds: 0020 @ 01
[ 4621.101989] qmi: wds: network start failed (000e)

Any thoughts? 

Original issue reported on code.google.com by joshua.a...@gmail.com on 31 Jul 2010 at 3:09

GoogleCodeExporter commented 9 years ago
exact same for me

Original comment by chris44gw on 1 Aug 2010 at 9:26

GoogleCodeExporter commented 9 years ago
I fixed this issue with my Evo 2.2 root rom by installing the 3.7.6c 
netarchy-toastmod kernel.

http://forum.xda-developers.com/showthread.php?t=719763

Original comment by will.ty...@gmail.com on 3 Aug 2010 at 5:07

GoogleCodeExporter commented 9 years ago
Everyone with a 2.6.32 kernel (e.g. OTA 2.2) is probably broke right now.  
Downgrading the kernel by flashing netarchy-toastmod is only a work-around, not 
a fix.

Original comment by dfrai...@gmail.com on 3 Aug 2010 at 6:59

GoogleCodeExporter commented 9 years ago
Issue 474 has been merged into this issue.

Original comment by harald....@gmail.com on 3 Aug 2010 at 8:01

GoogleCodeExporter commented 9 years ago
Issue 485 has been merged into this issue.

Original comment by harald....@gmail.com on 3 Aug 2010 at 8:01

GoogleCodeExporter commented 9 years ago
Issue 479 has been merged into this issue.

Original comment by harald....@gmail.com on 3 Aug 2010 at 8:04

GoogleCodeExporter commented 9 years ago
Issue 481 has been merged into this issue.

Original comment by harald....@gmail.com on 3 Aug 2010 at 8:05

GoogleCodeExporter commented 9 years ago
Oh. I think I know what's wrong!

Original comment by harald....@gmail.com on 3 Aug 2010 at 8:38

GoogleCodeExporter commented 9 years ago
One thing I need to know ...

If you start the official hotspot-feature - is a interface named wl0.1 created?

You could check that with this command:
/data/data/android.tether/bin/iwconfig

Original comment by harald....@gmail.com on 3 Aug 2010 at 8:46

GoogleCodeExporter commented 9 years ago
Oh. I can probably answer my own question:
[ 4616.911132] wlan: wl0.1: Broadcom Dongle Host Driver mac=38:e7:d8:19:ba:fe
So yes ... you should see an interface named wl0.1 ... :=)

Original comment by harald....@gmail.com on 3 Aug 2010 at 8:50

GoogleCodeExporter commented 9 years ago
After installing the evo testing1.  the SSID is now visable.  It connects, but 
does not get an IP address assigned.  No internet access.

Hope this informations helps.

Original comment by mnflanag...@gmail.com on 4 Aug 2010 at 12:03

GoogleCodeExporter commented 9 years ago
I'm having this problem as well with my EVO running the official Froyo update.  
The SSID is no longer broadcast with version 2.0.5-pre6.  I uninstalled and 
tried 2.0.2 and it broadcasts the SSID but my laptop can't obtain an IP address.

Original comment by brian.co...@gmail.com on 4 Aug 2010 at 12:23

GoogleCodeExporter commented 9 years ago
Harald,

I've not ignored your question, but I haven't gotten a chance to reflash my 
phone again yet :) I'll do that tomorrow and make sure that I get a wl0.1 when 
I bring up their hotspot.  In the mean time, your reading of the dmesg logs 
seems like a safe bet!

If there's anything else you want me to look up while I'm at it, let me know 
and I'll do that.  I deodexed Sprint's blobs for hotspot bringup, but it looks 
like most of the interesting guts are in native code; I've not yet gotten a 
chance to disassemble that

Original comment by joshua.a...@gmail.com on 4 Aug 2010 at 5:51

GoogleCodeExporter commented 9 years ago
Please try:
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_5-pre7.apk

This requires a stock htc-kernel (Android 2.2 - FoYo). Some first tests were 
successful.

Original comment by harald....@gmail.com on 4 Aug 2010 at 9:42

GoogleCodeExporter commented 9 years ago
This version worked for me.  Running a stock htc-kernel with almost Stock ROM.
Thank you.

Original comment by mnflanag...@gmail.com on 4 Aug 2010 at 11:18

GoogleCodeExporter commented 9 years ago
just updated to froyo omj custom rom and was using wireless tether 2 0 5-pre 
4.apk ... I was only able to connect 2 items to the tether at once (i.e. 
macbook and ps3 or macbook and ipod touch) when i attmepted a 3rd item i got 
messages such as can't connect to access point, or error, or i kept getting 
prompts to insert a password. Is this limitation a function of my custom rom, 
the wireless tether application, or something else all together? I love the 
program and it's working great but this was the first time i attempted to 
attach multiple devices. One the phone i also got a red shield with an X saying 
unauthorized when attempting to connect a 3rd device. I don't need 8 devices 
like the sprint hotspot but it would be nice to have 4. Thanks you . 

Original comment by mongoos...@gmail.com on 4 Aug 2010 at 12:56

GoogleCodeExporter commented 9 years ago
@mongooseny: It's a known issue and we will see what we can do. But at this 
point I would say 2 clients are better than NO clients.

Original comment by harald....@gmail.com on 4 Aug 2010 at 1:06

GoogleCodeExporter commented 9 years ago
Thank you for the quick response. I will donate when i get the opportunity. 

Original comment by mongoos...@gmail.com on 4 Aug 2010 at 1:40

GoogleCodeExporter commented 9 years ago
pre7 works great on stock rooted Evo.  Thank you

Original comment by jvanh...@gmail.com on 4 Aug 2010 at 1:40

GoogleCodeExporter commented 9 years ago
pre7 is working like a champ on Fresh 3.1.0.1. I'm actually posting this from 
my laptop via wifi tether on my Evo! YOU GUYS ROCK!

Original comment by stiggity...@gmail.com on 4 Aug 2010 at 3:29

GoogleCodeExporter commented 9 years ago
pre7, might not be tether related, but after test tethering quickly this 
morning and then turning it off, my battery tanked... and was down to 30% 2 
hours later,  maybe it is not getting shut down completely?  Anyone else?

Original comment by jvanh...@gmail.com on 4 Aug 2010 at 3:36

GoogleCodeExporter commented 9 years ago
I was able to try pre7 and had it working in no time without any problems that 
I could tell (only tried tethering one device, using encryption, etc.).  I 
turned it off and my battery so far seems to be doing okay (dropped 1% in the 
last 20 minutes).

Original comment by dligh...@gmail.com on 4 Aug 2010 at 3:43

GoogleCodeExporter commented 9 years ago
Also posted by way of my phone.  Looks OK to me.  I'll report back with if it 
causes adverse effects on my battery life.

Original comment by joshua.a...@gmail.com on 4 Aug 2010 at 5:21

GoogleCodeExporter commented 9 years ago
It is working me also with Stock HTC kernel and rooted OTA. Will this work with 
4G also. Cannot test that as I am not in 4G area. Thanks guys

Original comment by msakhw...@gmail.com on 4 Aug 2010 at 5:41

GoogleCodeExporter commented 9 years ago
Thanks for the fix.  I had to uninstall and reinstall to get to work but it 
works.  Battery life is ok with it.  I don't see any problems as of yet other 
than connection is a bit long than before but that is liveable. Awesome job 
keep up the good work. 

Original comment by Dtamm...@gmail.com on 4 Aug 2010 at 5:44

GoogleCodeExporter commented 9 years ago
Hello all I am a noob so bear with me. I had my EVO with 2.1 rooted and Android 
Wifi Tether working but since updating to Froyo (2.2) Android Wifi Tether is no 
longer working. Any ideas?

Original comment by ijim...@gmail.com on 4 Aug 2010 at 10:47

GoogleCodeExporter commented 9 years ago
Issue 483 has been merged into this issue.

Original comment by harald....@gmail.com on 5 Aug 2010 at 8:02

GoogleCodeExporter commented 9 years ago
UPDATE: pre7 has no battery issues, was caused by the updated Facebook app I 
installed about the same time.  Thank you again for the new update.

Original comment by jvanh...@gmail.com on 5 Aug 2010 at 12:12

GoogleCodeExporter commented 9 years ago
I was able to get it working on latest netarchy kernel after wiping the app 
data and uninstalling the app, wiping the device caches and then reinstalling. 
Currently posting using the tether. Thanks for a great app.

Original comment by larry.b....@gmail.com on 5 Aug 2010 at 1:23

GoogleCodeExporter commented 9 years ago
2.0.5pre7 Works on EVO Fresh 3.1.0.1 

Original comment by smhunter1983@gmail.com on 5 Aug 2010 at 4:01

GoogleCodeExporter commented 9 years ago
I am not seeing any adverse affects on battery life.  (I did briefly, but 'top' 
indicated that com.htc.android.Mail crashed and was sucking up 100% of my CPU 
while doing nothing, causing my phone to sit at my desk and become warm, and 
drain its battery rapidly.  Uninstalling HTC's Mail client fixed this issue for 
me.)  I'd call this one closed.

Thanks!

Is there already a bug open for the two-client issue?  If not, I will open one.

Original comment by joshua.a...@gmail.com on 5 Aug 2010 at 4:15

GoogleCodeExporter commented 9 years ago
pre7 is not working for me using Ava-Launchv4 which uses the updated FRF91 
froyo release from HTC/Sprint. No SSID is broadcasted.

Original comment by kjano...@gmail.com on 9 Aug 2010 at 3:13

GoogleCodeExporter commented 9 years ago
I am trying to use wifi-tether on 2.0.5-pre8, with the stock Evo ROM rooted. 
The AndroidTether access point appears, but no data ever gets sent across it 
when I connect my computer to it. (I never get an IP address, and the 
transferred size never changes.) I have to try several times to get Windows to 
connect at all (getting several "Windows was unable to connect" error messages 
-- I am not using the Intel wireless cards that are known buggy; this is a 
Broadcom 43224.

# uname -a
uname -a
Linux localhost 2.6.32.15-g746f4f0 #58 PREEMPT Mon Jul 26 18:44:23 CST 2010 armv
7l GNU/Linux

Relevant bits from a dmesg:

<4>[ 2841.686767] wlan: firmware version: wl0: Jul 21 2010 09:23:32 version 4.21
8.207.0
<4>[ 2841.686798]
<4>[ 2841.824920] wlan: Enter set packet filter
<4>[ 2841.826965] wlan: start to add pkt filter 100
<4>[ 2841.829254] wlan: Enter set packet filter
<4>[ 2841.831481] wlan: start to add pkt filter 102
<4>[ 2841.833831] wlan: Enter set packet filter
<4>[ 2841.835845] wlan: start to add pkt filter 104
<4>[ 2841.840332] wlan: dhd_preinit_ioctls:str=0x6e756c6c207061636b657400
<4>[ 2841.848541] wlan: eth0: Broadcom Dongle Host Driver mac=38:e7:d8:xx:xx:xx
<6>[ 2844.581756] serial_get_enabled: 0
<4>[ 2844.995971] wlan: wl_iw_process_private_ascii_cmd: ASCII_CMD: offs_0:ASCII
_CMD=                      ASCII_CMD=AP_CFG,SSID=AndroidTether,SEC=open,KEY=85ce
956c3421ab4103da8aa6d186ac5a391320e7e377ca9ddd6cdde8dc0a5573,CHANNEL=6,PREAMBLE=
0,MAX_SCB=8,END, offset_32:
<4>[ 2844.996002] 'ASCII_CMD=AP_CFG,SSID=AndroidTether,SEC=open,KEY=85ce956c3421
ab4103da8aa6d186ac5a391320e7e377ca9ddd6cdde8dc0a5573,CHANNEL=6,PREAMBLE=0,MAX_SC
B=8,END'
<4>[ 2844.996490] wlan:  AP_CFG
<4>[ 2844.996612] wlan: wl_iw: set ap profile:
<4>[ 2844.996795] wlan:         ssid = 'AndroidTether'
<4>[ 2844.996917] wlan:         security = 'open'
<4>[ 2844.997009] wlan:         key = '85ce956c3421ab4103da8aa6d186ac5a391320e7e
377ca9ddd6cdde8dc0a5573'
<4>[ 2844.997222] wlan:         channel = 6
<4>[ 2844.997314] wlan:         max scb = 8
<4>[ 2845.125976] wlan: setting SOFTAP security mode:
<4>[ 2845.126342] wlan: wl_iw: set ap profile:
<4>[ 2845.126708] wlan:         ssid = 'AndroidTether'
<4>[ 2845.127349] wlan:         security = 'open'
<4>[ 2845.127685] wlan:         key = '85ce956c3421ab4103da8aa6d186ac5a391320e7e
377ca9ddd6cdde8dc0a5573'
<4>[ 2845.128326] wlan:         channel = 6
<4>[ 2845.128692] wlan:         max scb = 8
<4>[ 2845.130310] wlan: =====================
<4>[ 2845.131072] wlan:  wsec & wpa_auth set 'OPEN', result:&d 0
<4>[ 2845.131439] wlan: =====================
<4>[ 2845.133026] wlan: wake lock 15 secs!
<4>[ 2845.133697] wlan: Link UP
<4>[ 2845.228881] wlan: wl_iw_process_private_ascii_cmd: ASCII_CMD: offs_0:ASCII
_CMD=                      ASCII_CMD=AP_BSS_START,SSID=AndroidTether,SEC=open,KE
Y=85ce956c3421ab4103da8aa6d186ac5a391320e7e377ca9ddd6cdde8dc0a5573,CHANNEL=6,PRE
AMBLE=0,MAX_SCB=8,END, offset_32:
<4>[ 2845.228912] 'ASCII_CMD=AP_BSS_START,SSID=AndroidTether,SEC=open,KEY=85ce95
6c3421ab4103da8aa6d186ac5a391320e7e377ca9ddd6cdde8dc0a5573,CHANNEL=6,PREAMBLE=0,
MAX_SCB=8,END'
<4>[ 2845.229370] wlan: SOFTAP - ENABLE BSS
<4>[ 2845.229583] wlan: !!! got 'WL_AP_EN_BSS' from WPA supplicant, dev:eth0
<3>[ 2845.342376] init: untracked pid 2522 exited
<6>[ 2847.582763] serial_get_enabled: 0
<4>[ 2847.629119] wlan: wl_iw_ioctl: error in cmd=8b03 : not supported
<4>[ 2847.651611] wlan: wl_iw_ioctl: error in cmd=8b09 : not supported

I'm specifically wondering about the last lines - could I have some exotic 
version of this wireless card? (I have a hardware revision 3 evo.)

iwconfig reports no wireless extensions on any interface but eth0:

eth0      IEEE 802.11-DS  ESSID:"AndroidTether"  Nickname:""
          Mode:Master  Frequency:2.437 GHz  Access Point: 38:E7:D8:78:96:BC
          Bit Rate=54 Mb/s   Tx-Power:32 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off

Original comment by leff...@gmail.com on 15 Aug 2010 at 6:03

GoogleCodeExporter commented 9 years ago
Finally working again for me with android-wifi-tether v2.0.5-pre8, Fresh 
v3.1.0.1 ROM, 2.6.32.15netarchy-toastmod-4.0.1 kernel. Probably works on newer 
netarchy kernels as well, but I haven't bothered to upgrade since I'm happy 
with everything on this one (and it includes other goodies).

Also, remember to uninstall any previous version, reboot the device, then 
install the new one.

Original comment by zach.h...@gmail.com on 15 Aug 2010 at 6:09

GoogleCodeExporter commented 9 years ago
Forgot to add that the above setup is working on a revision 0002 Evo.

Original comment by zach.h...@gmail.com on 15 Aug 2010 at 6:19

GoogleCodeExporter commented 9 years ago
Hi everyone,

I got my EVO the beginning of June and used 'unrevoked' to root it so that I 
could use the 'wireless tether' app.  I really screwed up and did the Froyo 
update without realizing that this would take away what I so greatly loved.  
Please please please, will someone lend a hand and let me know what I need to 
do to fix what I've done. Any help or a direction where to go will be greatly 
appreciated.

Thank you all for your time,
Jesse

Original comment by jeastma...@gmail.com on 16 Aug 2010 at 1:48

GoogleCodeExporter commented 9 years ago
Thanks so much.  Finally got mine working (I can't do without tethering) using 
stock rooted Froyo, netarchy toastmod 4.1.2 kernel, version 2.0.5-pre8

Original comment by RobertSp...@gmail.com on 18 Aug 2010 at 9:25

GoogleCodeExporter commented 9 years ago
Thanks to all the info here. I had 2.2 Froyo on HTC EVO. Followed: 
http://forum.xda-developers.com/showthread.php?t=765496, then installed 
http://qap.la/~netarchy/netarchy-toastmod-4.1.8-bfs-bfq-signed.zip with the 
recovery flash method (Bootloader -> Recovery (Amon Ra) -> Flash from ZIP -> 
selected netarch's zip -  then I installed WT version 2.0.5-pre8, working 
perfectly.  Thanks!

Original comment by Liu...@gmail.com on 4 Sep 2010 at 3:41

GoogleCodeExporter commented 9 years ago
Liukus, 

netarchy-toastmod and WT ver 2.0.5-pre8 worked for me, thanks for the fix.

Original comment by dvl5...@gmail.com on 8 Sep 2010 at 5:34

GoogleCodeExporter commented 9 years ago
That solution worked for me as well. Thanks guys.

Original comment by gunn...@gmail.com on 9 Sep 2010 at 1:43

GoogleCodeExporter commented 9 years ago
2.0.5-pre87 Worked well for me too. Stock Froyo, HTC Incredible.

Original comment by carlos.b...@gmail.com on 17 Sep 2010 at 10:20

GoogleCodeExporter commented 9 years ago
2.0.5-pre9 worked for me. Stock Froyo. Evo.

Original comment by sajjad.h...@gmail.com on 22 Sep 2010 at 3:03

GoogleCodeExporter commented 9 years ago
I have an evo, just installed the OTA, and the wifi tether doesn't work. I dont 
have any access controls. I've was running the latest 2_05 pre 9 .. It worked 
before the OTA, but doesn't work now. 

What do yall think ?

Original comment by BuyU...@gmail.com on 25 Sep 2010 at 9:30

GoogleCodeExporter commented 9 years ago
I have Droid X.  Just ran Froyo upgrade from 2.1.  wifi stoped working but 
2.0.05-pre9 install fixed it.

Original comment by dubin...@gmail.com on 29 Sep 2010 at 4:05

GoogleCodeExporter commented 9 years ago
I recently upgraded my rooted 2.1 HTC/Sprint EVO to 2.2 (myn's rooted stock 
3.29.651.5 (tinyurl.com/2943hlb)) and Wireless Tether 2.0.2 (from Android 
Market) broke. Client PC could find and connect to network, but never obtained 
IP address via DHCP request.

Upgrading to Wireless Tether 2.0.5-pre15 fixed this. Working happily again.

Thanks for the tireless efforts!

Original comment by tgi...@gmail.com on 11 Dec 2010 at 9:47