QuickSetupGuide.Com 
Home  Forums   Net Issues  Net How To   MS-MPVS   Cisco How To   Wireless  Search   About Us  Contact Us
 

 Bob Lin Photography services

Real Estate Photography services 






Internet TV

SmartPhone

Tablets

Others
Droid Phone How to and Issues

Droid Phone has a problem to sync with Facebook
Droid Phone Wi-FI issue collections
Exchange email doesn't work on droid phone
How to add an apps to droid Home
How to do factory reset on Droid
How to Transfer files between Droid and computer
How to upload videos from PC to Droid
How Setup Exchange email  in Droid Bionic Phone
Software to convert videos for Droid



Droid Phone Wi-FI issue collections

1. In many cases, Droid Wi-FI issue could be Wireless security settings. For test, you may want disable wireless security on the wireless router and re-enable it after the test.

Case 1: I am using an Airport Extreme and have security set to WEP. The Droid is unable to connect. The security on the Droid comes up as WPA/WPA2. Changing droid settings to WEP works.

Case 2: In my case, it is reverse. Setup WEP on Droid doesn’t work until I change it to WPA.

Case 3: If your router is set to WEP and droid is not auto-detecting that properly, you might have better luck with adding the network manually. In the Wi-Fi settings menu, instead of touching the network name to connect, try scrolling to the bottom of the list and choosing "Add Wi-Fi network". This will require you to type in the name manually, but it will allow you to specify that you are connecting to a WEP network by choosing WEP from the security drop-down list. Type your password under WEP hex key and press save, and hopefully your droid will be able to connect properly.

Case 4: I have some old system and they are limited to use WEB only. It might make a difference if you select "WEP ASCII" instead of "Auto" on the bottom drop-down list when adding the network. Since the airport wants 13 characters, you are definitely using a 128-bit WEP passphrase. If you were using a hex key instead for 128-bit WEP it would be 26 characters.

Case 5: I also have a DLink DIR-625 and was having the same problems with connecting to the AP but no data transfer. I changed my wifi settings from WPA/WPA2 to WPA2 only and the cipher from TKIP to AES and now the wifi works fully.

Case 6: My config is a Netgear WPN824. I found that the WiFi would not work with the Router set to WPA-PSK [TKIP] (Only). I switched it to WPA-PSK [TKIP]+WPA-PSK [AES] and the WiFi immediately started working perfectly.

Case 7: I have a DLINK DIR-655 and I was having a hard time obtaining an IP until I switched my router to use WPA2 Only vs the Auto for both WPA and WPA2. Now connection is almost instant....
Case 8: I had problems with the Cisco router and my AT&T router. Once I switched the router settings to WPA2, the android connected. Previous posts from others have stated this has worked for them as well.

2. In some cases, Droid wireless issues can be fixed by reset the phone. You can also refer to this post: How to do factory reset on Droid

Case 1: I got the WiFi working and did not require to many changes, I am using the following 3800HGV-B Gateway from ATT-UVerse. Authentication type is WPA-PSK. Encryption is TKIP. Not broad-casting SSID. I did update the phone by dialing *228. Once I applied the wireless settings to the Droid it did not seem to take effect until I powered down the phone and turned it back on. Once the phone cames up it connected to the wireless connection without any issues.

Case 2: After connecting to a public wireless, my droid phone doesn’t access to home wireless. After I took out the battery and rebooted, it connected ok.

Case 3: By default, our phones save settings, apps, and other data to Google's servers which include your "remembered" networks. If this option remains selected then you will not be able to truly "forget" a network (hopefully Google knows about this bug and will fix it in the December update). To resolve this issue and be able to connect to your network again follow these steps:

1) settings>privacy>uncheck back up my settings>press ok
2) settings>wireless & networks>wifi settings>touch and hold your network and select "forget"
3) turn wifi off and then back on, select your network and connect!
4) settings>privacy>check back up my settings (optional)

3. If Droid can connect to the wi-fi but not access the Internet, it could be DNS or web filter settings.

Case 1: In my case, it is DNS issue. My router was setup to use SBS server DNS that has been removed. After using the router IP as DNS, it works.

Case 2: My problem is MAC address filtering. I have some old laptop that doesn’t take WEP WPA so that I setup router to use MAC address filtering. After adding the phone Mac address, I can access the internet.

Case 3: My Droid can access any public wireless, but not in the office. I found out we have proxy server filter to web access.
Most routers have a page that will list all of the connected devices. If you are familiar with how to access this on your router, we might be able to learn something else from looking there. Every device on your network, including droid, has a unique MAC address (something like 08:00:28:9d:ef:0c), which you should be able to find in the router's list of devices. You can find your droid's MAC address in Settings under "About Phone" -> "Status" -> "Wi-Fi MAC address". Once you find the device, if it has a IP address assigned, it should match the one that we read above in the info from the Wi-Fi settings menu.

4. Compatible issue

Case 1: Some wireless router may not be compatible with Droid phone. The resolution is assigning static IP address, default gateway and DNS manually. To setup static IP address on the Droid phone, try these:
1) When in the Wi-Fi settings menu, press menu and select "Advanced".
2) Enter IP address, for example 192.168.1.10, Gateway: 192.168.1.1, Netmask: 255.255.255.0, DNS 1: 4.2.2.1 and DNS 2: 4.2.2.1.

Case 2: I changed the Basic Rate to 1-2 Mbps. and now I am good to go.

Case 3: You might also have some luck with changing the channel that your wireless is using on your router, this should be a number 1-11. Sometimes there will be less interference on another channel and things will work better. You shouldn't have to turn your rate down this low in order to make a connection.

Case 4: I had a similar issue to some of the users here, where the droid would successfully authenticate to the access point, receive an ip address, but subsequently no apps were actually able to use the wifi connection. The browser, for example, would time out saying page not available, etc. After an hour of debugging with tshark and google, I have found a workaround. First, let me describe my setup:

My access point is a Linux box using debian Linux (lenny release), hostapd, and the madfiwi drivers. I am using WPA2 & CCMP. Basically after the droid obtained an ip address, it would continuously send arp requests to the default router, over and over again. Replies were sent back, but apparently not received/processed by the droid. While this was happening, the droid also did not (or was not able) to respond to ping requests. The trick for me was to disable wmm (wi-fi multimedia), and u-apsd (unscheduled automatic power-save delivery). After turning these off (in Linux, this can be done via the iwpriv command), the droid was able to actually use the wi-fi connection.

So if your symptoms are similar (droid can successfully authenticate, obtain an ip address, but then fails to be able to actually send/receive any data over the wi-fi connection), you may want to search for and disable the wmm and uapsd options on your access point (if there is even a method to do this with your specific hardware/software).

Also, I would like to mention that I have a wireless printer that is able to use my access point with wmm and uapsd enabled. As such, this issue leans towards a bug/incompatibility in the droid wi-fi drivers.

Case 5: I believe my problem steamed from the Droid auto choosing between Ascii, or Hex for my WEP key which is all numbers. So I added the network manually instead of clicking on the network it found. There I manually set all of my security options, and that has been the only thing that has worked for me. Hope this helps someone.

Case 6: Upgrading my Linksys WRT54G v6 to the latest BIOS has fixed the problem with DHCP via wireless on the droid!

5. Update wireless router firmware may fix the problem.

Case 1: I am using a Netgear WPN824v3 firmware version V1.0.8_1.0.6NA. I have tried the static address and it does not work. I have also tried entering the MAC address it does not work until I upgrade the firmware on the router.

Case 2: I had a hell of a time getting it connected to a Linksys WRT54G V5 using WEP. But I could connect to 4 different open APs floating around the neighborhood. I just couldn't get an IP even after I changed my Linksys to "open". What finally worked for me was to upgrade the Linksys firmware from v1.01 to current (v1.02.7) AND entering the key in Hex (the Pass phrase didn't work). Once I did that I was fine.

6. Droid wireless slow

Case 1: I've been having WiFi issues with my DROID as well. I've verified that I am authenticating properly with WPA2 and AES, but performance was very slow. I went into my router, a WRT350N running DD-WRT, and disabled the WMM support. WiFi performance was soon much better and pages loaded very rapidly.
Case 2: I have Linksys WRT54G. Upgrade firmware fixes the slow issue.

This web is provided "AS IS" with no warranties.
Copyright © 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.