[dbltap]

Been working with my Torch now since Noon Thursday and have been most impressed. But I seem to have a quirky issue. I just setup a new Trendnet 300N access point to use with a few different devices. My main wifi in on a Buffalo router with dd-wrt a/b/g. I had several different apps on the 9800 using wifi.

All seems to work on WiFi very well. I have a decent 3G signal here at my house. The issue seems to be one that pops up after a few hours on the WiFi N. As I leave the house and loose contact with the router, my AT&T signal never re-connects to the BB network on AT&T. My 9700 has good strong 3G signal on the BB network. But the 9800 will show just 3G. Even if I switch to 2G, I get the little "edge". Nothing I can try resets the BB network connection. The only solution is to do a Data Wipe of all my data. The signal will come back at that point. Then I have to go through a restore from back up, enterprise activation and reconfigure all my apps.

At this point I have excluded the WiFi N AP from connecting and back on the a/b/g router. I've removed all my Apps that can use WiFi. I'll be adding them back one at a time to see if it is apps or WiFi-N that is causing the problem.

Anyone having any issues with WiFi N?

[gtivr6r]

Might want to check for any firmware updates for your wireless router.

I have several devices connected to my Netgear 3700, but I didn't get full
usability until I installed the latest firmware upgrade.

Just a thought.

[dbltap]

Thanks. The access point for WiFi N is brand new. So latest firmware. The Buffalo running dd-wrt is the latest stable release. Not running any pre-release code there yet. And it seems to be ok on the Buffalo running a/b/g. I'm still not convinced it isn't an issue with some of the wifi apps that were fine under OS 5. I'm not so sure they are not causing issue under OS 6. IM+ Pro is back on and seems to be ok so far. I have a couple of chat messengers; KIK & PingChat that could also be the issue. Haven't put them back yet. Also might be something with SmartWiFi. Not sure. Just going to add one thing at a time back to see if I can isolate the problem more.