Wizard wifi bug - shows all networks as available

[indiekiduk]

I found a bug in tmobile rom 1.6.2.4 and qtek ROM 1.6.7.1. When access points are out of range they still show up as available. The network "Free WiFi - Be nice!" is NOT in range, yet it continues to appear in the list. Even after a few minutes.

This prevents my software - WiFiFoFum from working properly. Could someone please confirm they also have this problem so I can rule out that its my hardware.

TIA

[fone_fanatic]

yes mine does that as well. it also tries to connect to out of range networks, it cycles through them and for some reason it attempts to connect to the "in range" network last.

[indiekiduk]

I think it trying to connect to unavailable ones is normal. This is so it can still connect to a network which is in range but not broadcasting it's SSID. Some people turn off broadcasting the SSID on their wireless routers to prevent others from discovering it.

However displaying networks not in range as available is NOT normal!!! This means that nobody with a Wizard can war drive :-(

[irblinx]

I'm pretty sure that I've seen exactly this behaviour on every HTC device I've owned, i.e. it sits there stating that it's connected to my home network despite me being 200 miles away.

[indiekiduk]

The WZC list has always been a bit screwy thats not an HTC problem its MS's. Like the first time you open the dialog it might take a few secs to show real information. However this bug is different because it continues to show APs as available. Only way to clear the available list is to power cycle wifi (or power cycle device which does the same).

[drewy]

I'm not convinced that this bug (if it is one) effects war driving....

Indie, using beta's of your latest app all ap's located at the start of a scanning run are located correctly.....It's after a few miles I start to have problems, and the problems I have are ap's located BEFORE I actually reach them....perhaps the wizards wifi drivers are telepathic

[peterweg]

I've been using the Wizard for War Walking for a month now with Wififofum. If it hits 32 Ap's connected Wififofum crashes. The only way to clear out the list of AP's to start Wififofum with the wifi off, then close Wififofum. Restarting with the wifi on will make it behave normally.

In practice I switch the wifi on and off to disconnect AP's. This is often every 20-30meters in central london. Some places there are so many AP's that simply starting Wififofum cause it to crash. The Wizard can't handle crashes so a reset is required - up to 90 seconds. Sometimes within a few minutes of the last crash.

I've collected 5000 AP's so far but quite frankly, I'm somewhat pi**ed off with it.

I tried posting this on the Wififofum forumebut their email confirm registration process failed and I've run out of email addresses to register with. I also emailed them twice as I assumed it was Wififofum bug.

[indiekiduk]

Sounds like 32 is the maximum number of APs that can be in the drivers internal access point list. Then perhaps when it sees the 33rd it crashes because it tries to add it off the end of the array? Hmm I didn't receive your emails about this bug. If you give me the username you signed up with I can activate your account. We need someone like you on our forum

[indiekiduk]

I just tested the I-mate 1.1.9.3 ROM and it also has the problem. I was hoping to find a ROM that doesnt have the problem so we could take the wifi driver from it and install it via wififofum however it doesnt look likely we'll find one.

[kilrah]

Originally Posted by peterweg The Wizard can't handle crashes so a reset is required

Usually if a program crashes most of the device becomes unresponsive, including the today screen if you manage to get to it with the hangup button. But most of the time the Start menu still responds. From there you still manage to go to Parameters, System, Memory, Running programs and kill the unresponsive app.

Works 90% of the time, this already saved me quite a lot of resets, like when I stupidly run VisualGPSce forgetting to turn on Bluetooth. This Stupid app freezes all the device until it manages to open the COM port, which obviously never happens...