icebike
Well-known member
- Apr 8, 2010
- 1,725
- 115
- 0
Actually NO, locking into the 2.4 will not fix the problem. My router only does 2.4, and the problem persists.
802.11B and G use 2.4. 802.11A and N can use 5ghz.
Too often, people make a change on their router and the problem goes away temporarily.
They then assume this change had something to do with it and post success all over the place.
Each time it appears to work for a while, probably because the router was rebooted more than anything else.
But the problem comes back, and few ever bother to post back.
I've tried lots of different things, including locking the router to G, which also locks it to 2.4ghz, locking router to Channel 6, (fewer drops, but same looping when it does drop), changing the encryption type. I've even tried static IPs.
All of these things seem to fail after time. Yes, even static IPs fail. They simply cut the obtaining IP step out of the loop process, but they won't stay connected any better than dynamic IPs.
Yet every other phone on the router works perfectly.
The one thing that does not fail (FOR ME) is removing security on the router and going with mac address filtering. (I use a separate router for this - a major pain).
I can always get my HTC back on line by connecting first to a neighbor who has a router with a Guest SSID (in addition to their normal SSID), then connecting back to my own router. But lots of people can't do this, or don't have another router near by.
Its not a DHCP issue. (I can and do offload DHCP to a linux server, and when the loop occurs the DHCP server never sees a request, The connection gets dropped by the router or the phone before it allows that request to go thru.)
Its not a router problem. Every other device in the house has no problem with the router. The problem resides in the phone, and has something to do with blacklist handling or hacking countermeasures code. ("Michael" countermeasures I presume).
(This is not to say that some routers (airports) aren't more forgiving, who knows why).
We all have to wait for the fix, but the end of the month can't come too soon, and this is a bone headed mistake on HTCs part expecially since they have already solved this problem a few times before in other phone models, as has Nook, Xoom, and several Moto phones. Its a well known problem.
Last edited:
Facebook
Twitter
Instagram