same problem without solution yet salsa and other htc roms the wifi works fine i wonder why not in the cm roms

Have you checked logcat? Do you get exactly the same error msg with E/wpa_supplicant?

I wonder who to ask to look at this problem... "unfortunately" not everyone seems to be affected.

Any ideas?

same here...
Elelinux-7.1.0-RC1-Hero-v2.9
63.18.55.06JU.6.35.09.26

The problem started after I wiped everything and reinstalled this rom.

By wiping everything I mean: wipe everything including a format of system, boot, data and cache. I formatted those partitions because I noticed that some fonts I installed several roms ago weren't wiped after a full wipe and factory reset. And since my hero was getting slower and slower i wanted to make sure all old stuf was gone.

I have this problem too, although I'm not on a Hero but an Incredible S (Incredible 2) but this also use to happen with my huawei tablet! Its very frustrating I can't download more than 5-6 mb before having to restart

I think it's more a ROUTER related problem:

1. Use only B or G, no mixmode
2. i Use as encryption wpa and get no problem
3. try flashing a new kernel, maybe it's a kernel related problem

Stefan

Which router is used?
Also you can try switch wifi channel.

Problems gone?

---

I just flashed Elelinux-7.1.0-RC1-Hero-v3.4 and it seems that my wifi problems are gone (nothing so far in two days of using).

Try it out and post your experiences!

Bye, Marc.

Hmm... i'm running now Elelinux v3.5 and have same problem again... anyone else?
With next opportunity i will check if v3.4 makes the difference... but strange though...

Originally Posted by marchard

Hmm... i'm running now Elelinux v3.5 and have same problem again... anyone else?
With next opportunity i will check if v3.4 makes the difference... but strange though...

Have you checked if the wifi sleep policy on the phone is set to "never"?

Sent from my HTC Hero using XDA App

I've always got the same error on the stock rom and VillainRom 13 - figured it was just the WiFi turning off while the screen was turned off for power saving. In retrospect that was maybe a stupid assumption...