WiFi connection settings become messed after some successful connections (Workaround) - Touch Pro2, Tilt 2 Windows Mobile General

WiFi connection settings become messed after some successful connections (Workaround) - Touch Pro2, Tilt 2 Windows Mobile General

As some TP2 or other WM device owners I've noticed that WM often seems to forget WPA passwords when using WiFi. It doesn't really matter wether you use AES or TKIP and how long your preshared key is.
In my case the symptoms look like this: After I create a WiFi connection (WPA2, AES, hidden) so that my Rhodium can use my home WiFi network, everything goes just fine. But then, after having established a connection for two or three times the troubles begin. Usually it takes about 3 or 4 seconds to establish a connection. But suddenly it takes about 10 seconds after which I get a warning that the connection could not be established. If I then go to my connection settings, I allways find them completely messed up, so that I have to select WPA2 and AES and reenter my password an so on. Well, after it happends to you for three or four times, this becomes extremely annoying.
Recently, however, I've found a kind of workaround for this problem. And here it comes: After I turn on the WiFi, I simpy wait for about four seconds. If WinMo behaves nicely, 4 seconds are pretty enough to establish a connection. If, however, I don't get connected after these 4 seconds, I IMMEDIATELY turn WiFi off, wait 2 seconds, and turn it on again. With 99% probability this second try gives me a working connection. If it doesn't, I simpy repeat the same procedure once again. So, the scheme is quite simpe:
Turn WiFi on and wait 4-5 seconds (it depends). Got connected?
Yes: O.K
No: Turn WiFi off, wait a second and turn it on again.
The main thing about this trick is not to let WinMo try to establish a connection for more than 5 or 6 seconds, otherwise it will delete your connection settings.
In my case, this workaround works perfectly. For more than two weeks I've been using my home WiFi with Touch Pro 2, establishing at least 4 or 5 connections a day and not a single time my connection settings were lost. Well, surely this thing with turning WiFi on and waiting and turning it off if you don't get connected fast enough is also a little bit annoying, but nevertheless it is much less annoying then having your connection settings all messed up every single day.
I'm not sure, whether this workaround will work with other devices or WinMo versions or even firmware versions, but may be it will help at least some of you affected by this odd problem. So you may just give it a try.
I'm using Touch Pro 2 with stock O2 Germany ROM (1.19.207.0)
Thanks for reading this long post and sorry for my bad English.

Excellent! Thank you for sharing your workaround!
I do something similar, except I turn wifi off by pressing the power button if the wifi hasn't connected in a few seconds. (By default wifi turns off when it goes into standby.)
On the odd occasions where the key does need to be entered again, I keep a copy of the wifi key "somewhere" on the device. It's a copy and paste operation after that, so it doesn't take long to re-enter the key. Luckily you can use the keyboard Ctrl-V method to paste the wifi key into the TouchFLO interface.
The other observation I've made, is that if I switch on the device by sliding out the keyboard, my Touch Pro 2 has a higher chance on getting a 'lock' onto a weak wifi signal. I'm not really sure why!

I'm glad that this workaround works not only for me
Actually, I don't use Connection Manager any more, for I've recently installed Rhodium Keyboard Controller GSM 1.3.2. Using this handy tool I remapped my Home button, so that double clicking it, turns WiFi on and and double clicking it with working WiFi turns wireless off.
I guess that Rhodium Keyboard Controller uses some advanced routine to activate WiFi, because since I use it for establishing WiFi connections, I rarely have to use my workaround, for normally I get connected on the first attempt.

see similar (but not the same) problem here
http://forum.xda-developers.com/showthread.php?t=562893

Related

TomTom lock up

Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...

I am still on my S100 with tt6 6.010 (7720) and no SIM since I currently use it solely for navigation. What I experience is not really a lockup but just a big delay (almost 1 min) after tt has initialized and only if "Enable wireless data" is enabled.

UPDATE
Turns out that this was a system resource problem. I have Wisbar 2 Advance, PocketBreeze 5, Phone Alarm, and PhotoContacts Pro all active on my device. I guess this is just too much to handle for the Omap when I try to add TomTom on top of that. When I exit WA2, PA and PhotoContacts, shut the device off for about 30 seconds, then turn it back on and launch TomTom, I have no problems. I have also been able to do it only shutting down WA2 and PhotoContacts, but it still locks from time to time like this. I have to shut down all three to be safe. Leaving PocketBreeze running (with some plug-in tabs active too) seems to be a managable workload for the processor. It's kind of a pain, but at least it works! It's not like I need a nav program every day!
Later...

Glad to know you found the source of your problem.

psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??

Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?

Magic Button - Pocket PC Task Manager
This will CLOSE the program instead of MINIMIZING it to the background process.

JC#79 said:
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Click to expand...
Click to collapse
I only started putting things on the card two days ago - day two i started having tomtom problems.
I'll def give this a go though and let you know if any improvements...
Thanks!

i have the exact same problem with my dopod p800w/artemis etc etc......i found a way to eliminate the freezing and hanging.......rule of thumb is to open the program by going into its root directory and opening it from there, instead of opening it via the start/programs shortcut or today screen......basically just make sure you open the program by going into File Manager and look for the tomtom navigator.exe file (usually in the program files folder and then navigator folder) and open it that way......ever since i tried it this way i never get any freezing and the program would start all the time.......it works for me......

[Q] Is there a problem with your Wifi?

Hold the phone with the keyboard out.. if your pointer finger or any part of your hand covers the top of the device (or rather, left in the case of landscape).. does your wifi signal drop..
Often times it will drop signal completely and then come back up. I also noticed that the wifi is extremely sensitive to line of sight.. If the back of the phone is turned away from the access point.. signal drops.. turn around 180.. signal back up again. Its aggrivating.. this is when holding the phone in portrait mode..
Also..the device does not really roam all that well.. I have my wifi aps setup with all the same SSID.. so as you move through the house using lets say, my trusty HD2 running android, it will switch from ap to ap with no drop.. this also depends on roaming tendency (with computers) - but all in all.. it works perfectly. The G2 just drops the connection, and then connects to the next AP..
So.. do you have issues with your wifi?
btw.. The speeds are pretty good.. especially with PM (iwconfig eth0 power off) turned off. Its the link quality that is erratic..
I thought connectbot would be 10x more enjoyable with a keyboard.. didn't know there was a catch

Ive got lots of issues but I'm torn between if it's my phone or my router... My Vibrant does the same kinda crap but not as often as the G2 does. The PC's will be on, but not the phones.
How can I manually set my IP?? I do the Press menu in the WiFi menu and set static IP and specify what I want, but when I click on the network I'm connected to, it shows the IP that the phone chose by itself

There's a thread open here: http://forum.xda-developers.com/showthread.php?t=926132

Yeah, the wireless sucks unfortunately. I've setup a ton of new routers in my home (I have lots of media equipment and stream things constantly) and it's definitely the equipment. Sucks sooooooo much because the mobile radio sucks just as bad!!!

Pretty much every smartphone has this issue. I've noticed that my G2 drops its cellular signal if I hold it on the bottom-left corner.

Signal is fine, problem with wifi on this hardware is much worse than losing signal. When connected to some APs, screen off = wifi off, even when set to always stay on.

Stargazer418 said:
Pretty much every smartphone has this issue. I've noticed that my G2 drops its cellular signal if I hold it on the bottom-left corner.
Click to expand...
Click to collapse
I've come across the same issue. Everytime I hold the phone using my lft hand,my coverage drops from H to edge. As soon as switch to my rt hand I get back on H. Also noticed whenever I hold the phone using just my finger tips to top to bottom I always stay on H.
Sent from my CyanogenMod powered G2.

[Q] Wife issues just recently started on SM-P600

So I just purchased the tablet brand new about 2 weeks ago. Love it for the most part!
Over the past couple of days though, the wifi has really started to act up, and it's passing me off.. About every half hour or so, sometimes longer, sometimes shorter, the wifi will just stop working for a while. The bars will still be there, as will the little "download" and "upload" arrows lighting up as though data is still being sent and received. However, the wifi just isn't working. Pages won't load, speed test . net app won't work, nothing requiring wifi.
I usually have to go into wifi settings to disconnect and reconnect for it to start working again.
I haven't done anything different to my wifi router, and my other wifi connected devices don't seem to be having any trouble staying properly connected, so it doesn't seem like it'd be an interference issue.
Can anyone provide me with some help?

[Q] Galaxy Tab Pro 10.1 wifi disables and re-enables while in use

I'm about to throw this stupid thing against the wall. Since I bought this thing a couple months ago I've noticed that sometimes when I am watching youtube a box will pop up telling me that I've connected to T1 (the name of my wifi network). It seemed odd because I was already connected but whatever. Then lately I've been using the HBOgo app to watch shows, and at some point during every episode the app will freeze and I will have to back out and then resume the episode. I assumed it was the HBO app, but I've started to realize that it is the tablet itself freezing and disabling wifi. I realized this today when I was trying to download some files. Nothing too large, 60-100mb, but the downloads were always failing before they could complete so I would have to start over. I start to download a file, the download should only take a couple minutes at the most, but before it completes, somewhere between 30% to 95% downloaded, the whole tablet freezes up and becomes completely unresponsive. Then the wifi icon disappears from the top right, and the wifi button next to location, bluetooth, etc, goes from green to gray, then after a few seconds it goes back to green and a box pops up telling me that I am connected to my wifi network again. I start the download again and the exact same thing happens. I've also noticed that the tablet gets quite hot around the camera.
It does the same thing when connected to my TP Link Archer C7 (just using N, not AC) and a netgear router I had lying around. I doubt it's the network as the router has no way to forcibly disable wifi on my tablet. When I said that the wifi button goes from green to gray, it's as if I had tapped it to manually disable wifi, even though I did no such thing.
Also, it does seem like if I turn the screen off and let it sit for a while to cool down, it will work until it heats up again. Once it starts to feel hot though the wifi will start disabling itself and downloads start failing again.
I'm only about 10 feet away from the router with direct line of site.
So is it just overheating? Defective and time to send it in under warranty?
Everything is stock.
SM-T520
Adroid 4.4.2
Kernel 3.4.39-4777054
Build KOT49H.T520UEUAOD1

Having the same issue...on the exact same device.
Sent from my SM-N910C using XDA Free mobile app

http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/help/ota-weirdness-tab-pro-10-1-t3116220
looks like the most recent OTA update breaks wifi, read that thread.... i got lucky as i usually just blindly accept OTA's when prompted... but i checked here and found that it was causing problems

Autoconnect Wifi with screen turned off

This issue has been annoying me for quite some time, and after a lot of searching (and trying stuff) I've decided to make my own thread because nothing seems to help.
Let's say I'm at work and I turn on my phone's WiFi radio, this makes it connect to the work WiFi without problems. Now once I go back home, the network becomes out of range so it switches back to 3G/4G (so far so good). But when I actually get home, it takes 10-15 minutes before my phone finally decides it can connect to the WiFi there. I have certain appliances that rely on my phone making a timely WiFi connection so you can imagine this will trip a few of them because I'm long home before it finally connects. I already tried toggling various battery/power/app optimisations found across this forum, but as mentioned nothing works. Pretty sure it's because Android scans for nearby networks only once every X minutes.
Now, I can "force" it to connect by just knocking on the screen to turn it on, but I either forget this or have my hands full and am unable to knock (and shouldn't be necessary anyways). So in short: is there any way to force Android to check for networks every X seconds/minutes instead? I am rooted, if that helps in any way.

Develop Bugs

welcome