Wi-Fi connection failure

[Raspador]

Need help here, probably a lot of it

Bought my 6700 a month ago and it's been working great otherwise, got round to trying the wi-fi functionality and spent 21 hours this weekend playing and reading posts to no avail.

This is the Sprint version, had the 6.0 kitchen on it when I got it, flashed back to 5 for provisioning, then flashed the 6.1 kitchen. EVDO and Bluetooth work fine. Problem is it doesn't connect to my d-link DI-524 router at all, and only sporadically to other open points. I removed the wifirouter app that was in ROM by flashing a new 6.1 kitchen today, made no difference.

Router was originally running WPA-PSK but I ran it open unencrypted to try this. It's running mixed mode and I tried both long and short preamble. Currently it serves via wireless my desktop and my laptop, and another desktop's hard wired to it.

The HTC will try to connect, say "connecting" then give up and declare my network "unavailable". Once in a great while it will connect to a neighbor's wi-fi and work slowly-it was on all day and worked with a neighbor's linksys (I think) router for about a quarter hour, then wouldn't connect again. It connected once today to a nearby college which has a free open wi-fi. I took it over there this afternoon to see what a stronger signal would do and it wouldn't connect at all.

It seems to discover networks perfectly well.
Where is there some documentation on the "tap an adapter to modify settings" adapters?

Any ideas?

[weedahoe]

You provided great info, most people wouldnt provide (or cant) that. I think its great that you have tried unencrypted. I love searching got a linksys router as, by default, they are unsecure. I was going to advise (if you didnt know already) that the 6700 only does 802.11b but I see you said your router was already running mixed. There are no specific settings in the wireless adapter other than to specify an IP. There is nothing in there that will fine tune or tweak the device to pick up and connect to any network.

The only suggestion I have (because you have tried a lot so far) is to flash back to WM5 with a good and popular ROM (because it would have little or not bugs) and leave the DLink unencrypted but also set it just to 802.11b (so nothing else can interfere) and make sure there is no MAC filtering.

I know its likely NOT what you want to hear but my biggest question to you is about the ROM you are using and possibly causing the issues. Reme,ber in the comupter worlds (PPCs included) that software is what makes hardware work. So maybe you do not have a hardware issue but more of a software driven one.

[dray]

I have been experiencing the same problem since I got my apache with WM5. I have since flashed it to WM 6.1 hoping it would cure it to no avail. WOW this is frustrating !! I have done research on this issue and it seems this might be a known issue with the Apache 6700 models. Certainly hope it isn't.... Raspador, you mentioned you flashed back to WM5 for "provisioning". I have yet to activate my Apache but have since flashed it to WM 6.1. Does anyone know if this is going to be an issue when activating it ? As for the wifi, I am still searching for answers. Any info will be much appreciated....


Dray

[weedahoe]

Originally Posted by dray

I have done research on this issue and it seems this might be a known issue with the Apache 6700 models.

I have had three 6700s and flashed and programmed many more and never had this issue. Now while I will not go as far as to say none of the 6700s ever do this, I will say it is possibly just your device and in the minority. This is just from my own exp. when working with them. Again, hardware is software driven and every modification/hack/tweak/cooked ROM/kitchen/ECT that we do is software based and (at times) had bugs and issues. Sometimes when we do something to resolve one issue, we cause another.

This is why I had mentioned backing everything up and doing a hard reset and flash back to a well-known and popular ROM. If it is liked and popular, then the chance of it being bug-free is pretty good.

I dislike suggesting a flash of a new ROM to solve any issue but for some reason this is where my mind keeps leading me and you always should go with your first guess/thought.

[Raspador]

Thanks to both of you.

It probably is the device, since both my router and the hotspots can be accessed by others, including my desktop. Question of course is what is it in the device?

Neither of my d-links (only using one these days) can be set for just b; the choices are g and mixed. I'm not usiing MAC filtering.

The real problem is that this equipment as far as I know can't tell you why it isn't connecting.

dray: As far as I know it can't be provisioned - activated - using the 6.1 kitchen and the previous owner said it couldn't be done under the 6.0 either. Rather than play around whilst on the phone with customer service rep, I just went to 5 and it set up correctly, and didn't have to be activated again under 6.1.

I don't think that one should go with one's first thought unless subsequent thinking shows it makes sense. I've had many first thoughts that were idiotic.
And you can go around in circles easily that way.

In the absense of anything better to do I suppose I can reflash. Very time consuming but if it works then we know the hardware works. If it doesn't it really hasn't proved a thing, since the reflash won't change some of the radio settings and perhaps the wi-fi settings.

[dray]

Well my wifi issue has been resolved by setting up my router for 802.11 b/g as mentioned above. So now I have to flash my phone back to WM 5 and am not sure how to go about it. Any suggestions ? Can someone point me to the right thread ?

Thanks to you all.

Dray

[macejsc]

Mine does the same thing with Helmi's 6.0 Rom. It'll connect sometimes, to my LInksys wifi, but then sometimes it doesn't. I have two laptops and a desktop, the desktop is hardwired into the router, but the laptops are wireless. When they connect I have no problems, except having to restart the router now then due to the phone company, that's another issue though. I can connect sometimes to my wi-fi, then other times it will come up find the network and try to connect, then say it's unavailable. I do have a WPA-SK Key on there and I put it in correctly, and the initial time I tell it to connect it works. If I want to connect again, I have to remove the settings, restart the router, and reset the connection between the phone and the router for it to connect again. I'm on Alltel, but I wouldn't think that would be that much of a difference. One thing I did find out though is if you hit ##778 on our network we can access the information for the phone and a lot of the numbers and things on there were the previous owner's phone number, I changed all of those to my number and things have been running much smoother on it. Still have issues with the wi fi at times though.

[gambatte]

I've been dying to see if this works for other ppl.

Start>settings>WLAN>Power management tab and set to "Beat Performance".

The link shows that it may help connection issues.

http://forums.microsoft.com/WindowsM...4154&SiteID=65

It worked for me on another WIFI connectivity issue.

[Raspador]

Ok well I've had it working for a week now and I should write up what I did. Connecting to the open networks took two hard resets. I also happened upon a very fine program called Wi-Fi Companion (http://www.socketmobile.com/) that shows a lot of detail about wi-fi connections and also allows connecting from it. It also, in addition to Apache adjustments for "best performance" and battery life, can manage the radio itself optimally for power saving. Several have noted the Apache setting can make a difference.

I suppose I should uninstall Wi-Fi Companion for a true test but for now I'll leave well enough alone. I have no association whatever with this firm.

Anyway once I was able to talk to the open networks I still couldn't connect to my system, which was also open for this test. What to do?

Well I have a second DI-524 access point that was in a box in the basement. I did a reset of it, then hooked it to a desktop computer and nothing else. And I was able to connect with the Apache! Hmm. Now it was a simple and tedious process of comparing all the settings between the two. And I found it, eventually.

Somehow, when I originally set up the network three years ago I left the router set with the radio TX rate at 54 megs. As we should all know by now the Apache is only capable of 802.11b speeds, or 11 megs. So they would never connect. All I had to do was set the speed to "auto" and everything works!

Someone might put this info about access point speed in a guideline somewhere easier to find along with the already described info about using b or mix mode instead of g.

Thanks to all for reading and thinking about this annoyance.