Database Develop

Wifi trouble with 2.17 ROM on Cingular 8125

I upgraded my Cingular 8125 last night with the excellent 2.17 rom provided by summiter. All was looking great until I tried to connect to my wireless network (Linksys WRT54GX4 SRX400 router with WPA-PSK security). I entered the key and it tried to connect, but then my wireless network switched from "Available" to "Unavailable" and dropped to the bottom of the network cards list. I could click on the network and tell it to reconnect, but it would do the same "available...unavailable" sequence every time. Wondering if it was a bad flash, I reapplied the 2.17 ROM and tried again with the same results. Not to give up too easily, I grabbed the 2.16 iMate ROM and applied it to see if the Cingular customizations could be causing the issue. Same problem.
So I disabled all security on my Linksys, cleared the net card settings on the 8125, and tried to reconnect. No luck. My neighbor has a plain Linksys WRT54G, so I tried to connect to hers and it worked just fine. At this point, I had to go back to the stock Cingular ROM because I need access to my wireless lan. All works well with the stock Cingular ROM.
Has anyone else seen this behavior with the 2.x ROMs? I'm wondering if there is a bug in the wireless networking support in the updated version of WM5 or if it is some weird incompatibility with the new Linksys WRT54GX4.
-BK
edit: corrected the router model number

At this point, I had to go back to the stock Cingular ROM because I need access to my wireless lan. All works well with the stock Cingular ROM.
Click to expand...
Click to collapse
Hey, does this ROM upgrade allow you downgrade. i have read stuff on this forum with people saying that they get an error "upgrade only" if they try to downgrade.

Way to keep the same topic going...start your own thread. :roll:

Unfortunately I don't have any feedback or value to add. I've connected successfully to a WRT54G, a Belkin Pre-N, and a Belkin Pre-N running Linksys WRT54GX firmware. No problems, but then again I use only WEP (I'm not overly concerned about the security of the traffic on this particular network, hence I use WEP instead of better encryption).
It's odd that with all encryption turned off you still can't connect. You don't by chance use MAC address inclusion/exclusion do you?

Yes, I normally use MAC filtering along with WPA to only allow certain devices onto the wireless network, but I disabled the MAC filtering for the same test where I disabled the security. The stock ROM works with both WPA and MAC filtering enabled. It's quite a strange problem. I must say that I find myself wanting the features of the newer firmware so much that I'm considering just not using the wifi connection anymore...
Thanks for putting the work into packaging the new ROMs for us. Cingular sure does drag their feet releasing their own updates.
-BK

my Cingular works good with Netgear WGR614 v5 & Linksys WTR54G

I've had the same problem with the updated roms. I'm running a D-Link 614+ rev b router using MAC filtering and no encrypton. My 8125 sees the router but it can't connect. I adjusted mty power settings but still no luck. I think everyone who has this problem should list their gear here so we can figure out a way to get around this problem.

I had WPA issues connecting my 8125 with my linksys WRT54G.
I'm in the same position as summiter, I'm really not concerned about the security of my home network, so I went back to WEP - which works fine. A combination of not broadcasting the SSID, MAC filtering, and WEP seems secure enough for my purposes.

I had the same problem after I updated my 8125's ROM. After many minutes of frustration playing with settings, I unplugged the router for a couple of minutes, and then plugged it back in and my phone began to work just fine. You may want to give this a try.

CameronJ said:
I had WPA issues connecting my 8125 with my linksys WRT54G.
I'm in the same position as summiter, I'm really not concerned about the security of my home network, so I went back to WEP - which works fine. A combination of not broadcasting the SSID, MAC filtering, and WEP seems secure enough for my purposes.
Click to expand...
Click to collapse
It's more a matter of security through obscurity, since there are tools to both find devices not broadcasting ssid, and for cracking the wep key in a matter of seconds or minutes. On the particular WiFi net I use I assume everyone can see it and don't use it for sensitive stuff. MAC filtering can be overcome, but it takes someone determined and knowledeable, and I don't think my neighbors or the casual wardriver fit that bill. =)

Hello All,
This sounds like their is some settongs on the phone are set wrong, try changing the select network setting on the top bar select the second set of settings witch are I belive my work network, then soft reset the phone it should work it did for me but not until the soft reset. you my want to setup the connection again and reset again after putting in the key. I do use the newest 2.17 rom as well seems to be good so far.
I also used this to trouble shoot it. http://www.htcamerica.net/support/cingular_8125.htm
great source of help.

I think it is definitely something with the 2.X ROM’s and this router. I have the same setup and can’t get anything but the original Cingular ROM to connect.

Using Summiters excellent 2.17 with WRT54G with no problems on QTEK 9100.

porky145 said:
I've had the same problem with the updated roms. I'm running a D-Link 614+ rev b router using MAC filtering and no encrypton. My 8125 sees the router but it can't connect. I adjusted mty power settings but still no luck. I think everyone who has this problem should list their gear here so we can figure out a way to get around this problem.
.
Click to expand...
Click to collapse
summiter
I'm having the same issue, i'm acutally using the same router as the person above, it will see the router but wont connect unless i reset the router. Plus it wont connect to any hot spots that it used to when it was on the old OEM cingular rom, so it must be something with the new 2.17 Rom. Did you make any changes in the WiFi settings?
please help us, i would love to keep the new rom on my wizard, it's so much quicker and it has all the extra bells an whistles.
thanks

Chiming in...
I actually found that the WIFI works better with the latest ROM (2.17/CF2, etc.) from summiter. There were networks that I couldn't connect to to save my life... now I can get in no problem.
Sorry you guys are having problems though.

marcini said:
porky145 said:
I've had the same problem with the updated roms. I'm running a D-Link 614+ rev b router using MAC filtering and no encrypton. My 8125 sees the router but it can't connect. I adjusted mty power settings but still no luck. I think everyone who has this problem should list their gear here so we can figure out a way to get around this problem.
.
Click to expand...
Click to collapse
summiter
I'm having the same issue, i'm acutally using the same router as the person above, it will see the router but wont connect unless i reset the router. Plus it wont connect to any hot spots that it used to when it was on the old OEM cingular rom, so it must be something with the new 2.17 Rom. Did you make any changes in the WiFi settings?
please help us, i would love to keep the new rom on my wizard, it's so much quicker and it has all the extra bells an whistles.
thanks
Click to expand...
Click to collapse
I can third this comment about he DLink 614+ and the DLink 524. My 8125 connects to the routers but then immediately locks up and I have to take the battery out to get it working again. I have not upgraded the firmware on either router so I might try doing that this weekend before doing anything. I know that DLink has upgraded some of ther routers due to some issue they had with NTP.

So far, I tested two routers with WPA: Linksys WTR54GS travel router and DLink DI-634M. And my workplace's wireless network using Cisco Access Points (54G) with no security (we use additional Cisco VPN in order to access network). All worked fine without issues. There are definitely changes in new wireless drivers. For one, it has a lot more parameters in registry. For two, it now supports LEAP. Thirdly, in the wireless networks window, it now shows signal strengths for each network. These are all positive improvements.
I haven't try to connect to a 11b router because I can't find one. Sounds like the issues are specific to DLink DI-614+ and the similar. If that's the case, time to get a new router. It's only $40 and you get much faster speed.

The router giving several of us problems is the Linksys WRT54GX4 SRX400, which is the latest MIMO router from Linksys...
-BK

foxbat121 said:
If that's the case, time to get a new router. It's only $40 and you get much faster speed.
Click to expand...
Click to collapse
I understand what you are saying but I don't think thats the point. Replacing the router is easy, but what was changed in the rom to cause this problem. And if anyone wants to know Circuit City has G routers on sale, I got a WRT54G for about $65 out the door. But i would still like to know what caused this problem

I believe there is a difference between the network adapter driver from ROM2.17 and Cingular ROM. Anyone with network connection problem after upgrade to ROM 2.17 may want to try this:
Download and install WiFiFoFum2 from Aspecto Software, then run this program everytime you turn on wifi, it will help detect and connect to your network. I can't explain why but it works for me so I hope it would work for you too. My network is Dlink-524 with WPA enabled and MAC filtering.

DD-WRT and WLAN

I don't know if anyone uses the open source DD-WRT firmware for their router, but it does not appear to work with WLAN on the wing. The wing recognizes it correctly, but, if I try to connect, it just attempts to connect for a little bit then gives up. It thinks I have a bad password but I've triple and quadruple checked that the password and encryption is right. Any ideas on a work around or a fix?

I am running DD-WRT V23SP2. Not having any problems with my Wing and WLAN.
However I am not using any encryption. I am just using MAC address athentication.

alben said:
I am running DD-WRT V23SP2. Not having any problems with my Wing and WLAN.
However I am not using any encryption. I am just using MAC address athentication.
Click to expand...
Click to collapse
It probably does have to do with the encryption then. We decided to put the old linksys firmware back on but thanks for the response.

I have also used my Wing with a Linksys WRT-54GL router running DD-WRT V23SP2 that uses WPA with a preshared key. No problem. Wing connected immediately once the key was put in.

my brother gets Artemis (p3300) with an official WM5, and when we turned WEP on on our router, his Wifi doesnt want to connect.... even when entering pass.... so we have it on Mac adres and works perfectly

WiFi unable to connect to router after 6.1

I've been running 6.1 ROM (Official) now for a month or so and am using a program on my Tilt that uses a lot of data...so while I'm at home I thought I would allow it to use my WiFi router instead of my 3G connection.
I turned on the WiFi and it can "see" my router's SSID. I enter the WPA-TKIP passcode and tell it to connect. It just sits there saying "connecting to network" but never completes the connection to acquire it's IP.
I have even gone as far as setting the IP configuration manually (Static IP) and the TILT keeps trying to connect to the network.
I have a DLink DI-624 that I have had no problems connecting the WiFi when I was running ROM 6.0.
I have done the following in trying to troubleshoot:
- Turned OFF Turbo on the Router
- Configured router for AutoChannel
- Configured TILT for Best Performance
- Rebooted Router AND TILT.
Still no go...Ideas?

I sometimes get this after flashing a new rom. It seems to affect the way it connects to WPA networks but not WEP or unsecured.
You can try changing your security to WEP and see if that works.
But when I need to solve this I usually have to do a Hard Reset and then connect the WIFI first. When it does this the phone seems to be able to auto-detect the network type (i.e without me needing to select it as WPA) and after entering the passcode it can connect.

Yep, go to WEP, this should be enough for most people and has never given me a problem.

martythebrit said:
Yep, go to WEP, this should be enough for most people and has never given me a problem.
Click to expand...
Click to collapse
Unfortunately I can't change my network to WEP. My network is not only my home network but also used for my wife's business...so for security reasons I have to keep the security up.

Drop the security just for a test and see what happens.

I am using the official ATT 6.1 ROM and it works just fine on my wifi, first with WPA-PSK then with WPA2-PSK. You could set your WAP to WEP (say that fast 3 times!) for a 5 minute test and see if it connects. Does your phone connect to other Wifi hot spots? What does ministumbler say about wifi in your area? You may have some interference with a neighbors wifi.

Well...I know that my issue is not limited to my router at home (DLink DI-624). I'm experiencing the SAME issues at work as well.
At work I'm using a NetGear WGT624 v3.
- The security is WPA-PSK (TKIP)...just like at home.
- Broadcasting SSID on Channel 11 (Fixed). There are no routers in nearby offices (I've checked using a wifi scanner on my laptop).
- I've configured a static IP in my Tilt and it just sits there at Connecting...again same as what happens at my house.
- I have also tried using DHCP with no joy.
I'll try the WEP at home to see if it's a WEP/WPA issue.
Unfortunately if it IS an issue...I don't think I'm going to get much joy from HTC on releasing a fix. Maybe there will be some way around it though...I hope!

Make sure you use the correct authentication: Use Smart Card or Certificate. That fixed mine

brynwall said:
Make sure you use the correct authentication: Use Smart Card or Certificate. That fixed mine
Click to expand...
Click to collapse
Here is what I have set in my TILT...
Connects to: The Internet
Hidden network: NOT checked
Ad-Hoc: Unselectable (Grey)
Auth: WPA-PSK
Encry: TKIP
Use IEEE: Grey (Non-Selectable)
EAP: Grey (Non-Selectable...but Smartcard or Certificate IS in the box)
(Still at work...will test WEP when I get home)

(I'm home)
Ok...Now I know for SURE that this is a WPA issue with the TILT running the AT&T ROM 6.1 (Official).
I changed my home router from WPA-PSK (TKIP) to WEP.
Made the needed changes in my TILT to change it from WPA to WEP and entered the correct key.
* IT CONNECTED TO THE ROUTER! Whoo Hoo.
I change nothing in the router except from WEP back to WPA and again I'm stuck at "connecting" on the TILT.
Ideas?

At least you know
And Knowing Is Half The Battle

clstan said:
(I'm home)
Ok...Now I know for SURE that this is a WPA issue with the TILT running the AT&T ROM 6.1 (Official).
I changed my home router from WPA-PSK (TKIP) to WEP.
Made the needed changes in my TILT to change it from WPA to WEP and entered the correct key.
* IT CONNECTED TO THE ROUTER! Whoo Hoo.
I change nothing in the router except from WEP back to WPA and again I'm stuck at "connecting" on the TILT.
Ideas?
Click to expand...
Click to collapse
Is a backing up everything and doing a hard reset too much hassle? Make sure you connect to a WPA Wifi first before installing any other programs. Its the only way I could fix it... =/ As recommended I always do another hard reset straight after flashing a new rom now.

Hey...someone...somewhere has mentioned that there might be a WPA issue in relation to removing the AT&T Bloat. Is there anything to this? I HAVE removed my bloat on my Tilt.
I don't want to have to re-Hard my Tilt...but will if I have to...but only as last resort.

What fixed with my DI-624
I found that I had to upgrade to the newest ROM from D-Link. (I had original ROM from 5 years ago.) I found that the PSK password (using WPA2) could NOT contains shift-numbers such as $, %, #. I converted the symbols to numbers (and letters)and it works fine now. I have had no problems since.

segaza said:
I found that I had to upgrade to the newest ROM from D-Link. (I had original ROM from 5 years ago.) I found that the PSK password (using WPA2) could NOT contains shift-numbers such as $, %, #. I converted the symbols to numbers (and letters)and it works fine now. I have had no problems since.
Click to expand...
Click to collapse
My home router is a DI-624 Rev E. The ONLY Firmware for the E Rev is 5.00 and I'm running it.
Even though not completely secure...my WPA password is a 20 character, lower case entry...no strange characters or whatever.
*Well folks...I had just installed the 6.1 Rom onto my Tilt about a month ago...so I don't have that much installed...and I can always reload it. So I HardReset and followed by removing bloat. WPA WORKS NOW! (Insert "Twilight Zone" theme music here.)
All in all...it just seems strange to have to HARD Reset my phone to get something like this to work again.

G1's WiFi is not "compatibale" w/ some Routers?

Hi, everyone,
I've met a strange problem these days.
I'm always following the CyanogenMod ROM and it's really nice, however, I met this "wifi cannot obtain IP address" issue on CM4.0.4 and some experimental CM builds(using donut 1.6 core)
I'm using D-link at office and TP-Link at home.
TP-Link works fine, D-Link worked fine and i cannot specify from which version of CM Build, the G1's WiFi met the "Cannot obtain IP address" under D-Link Router.
Here's the information of my G1.
T-Mobile G1, Rooted. using CyanogenMod CM4.0.4 ROM, radio and SPL are all updated.
Is there anyone who has solved this?
Thanx!

Delete and try again. I had that once at my folks place on vacation. Just had the wrong freaking password.

nope, im sure about that i entered the right password.
thank u anyway

nope, im sure about that i entered the right password.
thank u anyway

Might be the security on the router. You need to set to "WPA2 Only" on some routers. Some will work with WPA/WPA2, but others will only work with WPA2 so give that a try.

h.nocturna said:
Might be the security on the router. You need to set to "WPA2 Only" on some routers. Some will work with WPA/WPA2, but others will only work with WPA2 so give that a try.
Click to expand...
Click to collapse
now both of the TP-Link and the D-Link routers are under WEP mode...
Will WPA/WPA2 works?
I'll give it a try.
thanx.

[Q] Captivate Wifi Issue

Hi All,
I have a weird problem with my captivate of not connecting to my home network. Let me start by telling that I have searched the solutions and tried doing everything except full factory reset. I have rebooted the phone, done reset on my router (Wifi was working just fine earlier.. so I think settings was not an issue. But I still did it), I removed the file data/wifi/bcm_supp.conf and let it regenerate it. Captivate displays "Obtaining IP Address" and it just stays there. I also see that IP address is being assigned to captivate in my router
Captivate is rooted stock Froyo
Router security: WEP
form the Wifi list, I found one unsecured network and captivate connects to that router just fine (signals are very week though...). I tried removing the security on my router but it still stuck on "Obtaining IP address".
Can you please please help me?? As I mentioned earlier, It was working just fine and suddenly stopped working two days back.
These all app updates are eating away my limited data of 200M.
Thanks a millian.

What's your router model ?
What channel are you running on ?
Are others routers close to you running on the same channel ?
Have you tried another channel ?
Did you try WPA2 ?

Could be incompatibility with your router. That happened to me before with my old router. It didn't work with some cell phone wifi devices.
Sent using XDA App

Try using the app "FXR." I had the same issue a couple times and this app seemed to fix it. It took a few tries though. I think it might be a router problem. I use the Linksys wrt54g.

You could also try assigning a static IP address to your device on the router side, and then telling your phone to use that address. I've used that in the past to some success.
As a test, have you tried (temporarily) disabling the security on your router to see if it connects?

I have a similar problem since upgrading to the past 3 nightlies. My phone sees and connects to my home network and says it has strong signal, but when I try to access Market or Internet it says there's a network error and I can't get thru. My two computers (one hard wired and one wi-fi) don't seem to have any problem hooking in to the internet, just my SGS1

Moozh1 said:
Try using the app "FXR." I had the same issue a couple times and this app seemed to fix it. It took a few tries though. I think it might be a router problem. I use the Linksys wrt54g.
Click to expand...
Click to collapse
Does the 'FXR' app set up IP addresses?

The App didn't work for me. I tried that yesterday. I was reading the similar problems on some other site yesterday and I found the following that solved my issue. In case someone like me still struggling with the WiFi problem.
Delete file data/wifi/bcm_supp.conf
Delete file /data/misc/dhcp/dhcp_list
reboot the device and it will create these files again and you will have to enter your WiFi password again in order to connect.
I am really glad that my WiFi is working back again.

FYI, I'd change the WEP to WPA.

cappysw10 said:
FYI, I'd change the WEP to WPA.
Click to expand...
Click to collapse
Where do you go to change that setting? I've been all thru the wi-fi settings and advanced settings, but didn't see anything that referred to WEP or WPA.
Just realized we're talking now about the router, not the phone, duh!

Yes, I certainly need to bump up the security settings on my router.
cappysw10 said:
FYI, I'd change the WEP to WPA.
Click to expand...
Click to collapse

22andy2 said:
The App didn't work for me. I tried that yesterday. I was reading the similar problems on some other site yesterday and I found the following that solved my issue. In case someone like me still struggling with the WiFi problem.
Delete file data/wifi/bcm_supp.conf
Delete file /data/misc/dhcp/dhcp_list
reboot the device and it will create these files again and you will have to enter your WiFi password again in order to connect.
I am really glad that my WiFi is working back again.
Click to expand...
Click to collapse
I used root explorer, but could not locate the files you mentioned. Directories were there just not files. I'm still exploring the router side. Thanks for the info tho.