Last Thursday I installed the 4.010.11 update from Acer and my wifi connection at work worked perfectly for one day. After the first day it switches very slowly back and forth between "Connecting" and "Scanning" but never actually connects. Looking at the active connections on the WAP we can see the MAC address of the tablet trying to connect but it won't do it.
We are using:
EAP method: PEAP
Phase 2: none
CA cert: unspecified
User cert: unspecified
Identity: my username
Anonymous identity:
Password: my password
My co-worker has a Xoom and it connects fine and both of our Android phones connect too.
We did not make any changes to the wireless configuration. The WAP I'm trying to connect to is an HP ProCurve MSM422 AP.
Today I backed everything up and did a factory reset and the A500 still won't connect. The unit connects just fine to all non 802.1x WAPs.
I have not installed the Acer wifi fix since my understanding is that it is rolled into the 4.010.11 update.
I've become pretty reliant on my tablet at work so this is driving me nuts. Anyone have any ideas?
Thanks,
Matt
same scenario for me, it appeared on the .08 update and I had hoped the .11 update would take care of this issue. However it didn't.
My Nexus One connects fine to the 802.1x connection. My A500 connects to wpa or open networks without trouble.
I don't use my A500 at work but I wish I could if I wanted to.
There is a fix for this well known issue on the Acer support site. Download the zip indicated (it's very easy to find), unzip it to your PC, and follow the instructions within.
There are also several threads on this topic that contain other ways to fix the issue, at least temporarily, but the Acer fix is meant to be a permanent one.
I ran into the same problem after trying to connect to a network that I hadn't yet properly set up. For me a factory restore solved the problem and it hasn't returned so far.
Sent from my A500 using XDA Premium App
FloatingFatMan said:
There is a fix for this well known issue on the Acer support site. Download the zip indicated (it's very easy to find), unzip it to your PC, and follow the instructions within.
There are also several threads on this topic that contain other ways to fix the issue, at least temporarily, but the Acer fix is meant to be a permanent one.
Click to expand...
Click to collapse
The threads on here don't mention 802.1x and my tablet works fine with all the other wireless protocols. The other threads also reported that it would connected and disconnect quickly. My tablet takes several minutes before it switches from "Connecting" to "Scanning" and vice verse.
I have done all the other fixes (double reset, system restore, deleting the DHCP cache (was never there to delete on mine), using static instead of DHCP, etc) and they do not help, not even temporarily. I have not flashed the fix from Acer since the PDF in the patch.zip does not list my newer version as being affected. My understanding, after reading all those other threads, is that the patch is rolled into the .11 update.
dude64 said:
I ran into the same problem after trying to connect to a network that I hadn't yet properly set up. For me a factory restore solved the problem and it hasn't returned so far.
Click to expand...
Click to collapse
I've done a factory restore and it did not help. First thing after restoring I went into my wireless settings and it would not connect. I figured since it worked for a day after doing the .11 update it would at least work temporarily after a restore but no dice.
-
Thanks to the both of you for your suggestions. I may try the Acer patch later today if I have time, I'm stuck in meetings most the day, and will report back. If anyone else has any other ideas I would be very grateful.
I might be a channel related issue. However, what EXACTLY do you mean by 802.1x? Do you refer to 802.11 a/b/g/n? Which one does your router support? IIRC, the A500 supports a/g/n variants only. Not at my tablet right now to check.
Wilda said:
Thanks to the both of you for your suggestions. I may try the Acer patch later today if I have time, I'm stuck in meetings most the day, and will report back. If anyone else has any other ideas I would be very grateful.
Click to expand...
Click to collapse
Just got done trying the patch (after all the other resets suggested on the Acer website) and it didn't work. According to the documentation with the patch, it is only for versions .07-.09.
I'd also like to add that I use WEP on my home network and I connected without a problem this morning. We also use PEAP here at work, so maybe that's the issue.
FloatingFatMan said:
I might be a channel related issue. However, what EXACTLY do you mean by 802.1x? Do you refer to 802.11 a/b/g/n? Which one does your router support? IIRC, the A500 supports a/g/n variants only. Not at my tablet right now to check.
Click to expand...
Click to collapse
802.1X is an authentication protocol originally used on wired LAN's for port authentication that is now also often deployed in corporate wifi networks to authenticate wireless client access to the network.
It should not be confused with 802.11 specs for the RF layer.
rvholland said:
802.1X is an authentication protocol originally used on wired LAN's for port authentication that is now also often deployed in corporate wifi networks to authenticate wireless client access to the network.
It should not be confused with 802.11 specs for the RF layer.
Click to expand...
Click to collapse
OK, I see what you're talking about now. The A500 only supports 802.11 b/g/n. Not sure what you connected to on the first day, but there is no listed support for 802.1X.
I'm not sure you've got a handle on the difference yet. 802.11 b/g/n is the wireless LAN spec, 802.1X is an authentication protocol used on top of the 802.11 layer instead of WEP or WPA2/WPA.
My A500, like the OP's, when running 3.0 worked fine on the network with 802.1X EAP authentication. If you are in the presence of a network running 802.1X and attempt to connect you are presented with a menu for information such as the info in the OP's first post. This info may still be entered in 3.1 for the 802.1X EAP network but it is not authenticating in 3.1 like it used to do in 3.0.
I suspect that the A500 is not presenting its entered credentials correctly such that the authentication process can complete.
I can confirm the Acer offical patch works for .11 (even though it says US .07-.09) - before I couldn't connect at work (PEAP/MSCHAPv2) but WPA and WEP worked fine - after patch 802.1x EAP worked great.
Tested on US 32gb 4.010.11_COM_GEN2
well I installed the patch and will report tomorrow on the results...
Well the wififix patch is not effective in correcting the issue I have at work with 802.1x networks. Patch installed last night and this morning the a500 will not connect.
Guess this is another issue Acer is deficient in testing.
I also tried the double reset just to make sure that it wouldn't by chance have any effect. No connect results.
To answer FloatingFatMan the WAP has two antennas which can be set independently. Right now one is set for b/g and the other for n. As was previously stated 802.1x is an authentication protocol and has nothing to do with speed. In our case it allows wireless users to be authenticated through Active Directory instead of using a password like WEP or WPA.
I'll try the Acer patch today and see if I have any better luck than rvholland.
pfc.joker said:
I can confirm the Acer offical patch works for .11 (even though it says US .07-.09) - before I couldn't connect at work (PEAP/MSCHAPv2) but WPA and WEP worked fine - after patch 802.1x EAP worked great.
Tested on US 32gb 4.010.11_COM_GEN2
Click to expand...
Click to collapse
rvholland said:
Well the wififix patch is not effective in correcting the issue I have at work with 802.1x networks. Patch installed last night and this morning the a500 will not connect.
Guess this is another issue Acer is deficient in testing.
I also tried the double reset just to make sure that it wouldn't by chance have any effect. No connect results.
Click to expand...
Click to collapse
I have the same version as pfc.joker (just the 16GB model), but I got the same results as rvholland. Went home and worked fine but at work it's borked. I haven't been able to find anything useful on the web regarding this. Anyone talked to Acer about it? I'm afraid they are going to charge me $100 for the call.
4.010.13 doesn't help
My a500 updated late yesterday to 4.010.13 and even though there was reference to some wifi tweaks it does not improve the situation I'm having on 802.1X authenticated wifi.
Retried this morning at work and the same results of scanning-connecting-disconnected and then followed by simply staying at scanning for a long time.
There is never any mention of 'obtaining ip address'. I doubt its ever connecting far enough to communicate with the dhcp server.
I received the 4.010.13 update last night and hoped it would fix the issue but like rvholland I too still cannot connect to the wireless at work. Hopefully a fix is found soon.
rvholland said:
There is never any mention of 'obtaining ip address'. I doubt its ever connecting far enough to communicate with the dhcp server.
Click to expand...
Click to collapse
Same thing here. Watching the connections on the WAP it looks like the A500 tries to connect but hangs on the authentication and therefore never gets to the point where the DHCP server can assign an IP.
My first query via online support from Acer was not helpful. They suggested the same old "use 4.010.10" update about wifi issues or "use the patch" answer.
Perhaps the second round will get someone to read the actual explanation of steps already taken before replying with the steps for a different problem.
rvholland said:
My first query via online support from Acer was not helpful. They suggested the same old "use 4.010.10" update about wifi issues or "use the patch" answer.
Perhaps the second round will get someone to read the actual explanation of steps already taken before replying with the steps for a different problem.
Click to expand...
Click to collapse
Thanks for taking the time to check in with Acer. We only have a few weeks before school starts and have a lot of projects that need to be done before the students come back so I have very little time to look into this right now. I sure hope you can get a hold of someone that actually realizes this is a separate wireless issue and is not fixed with .10 or the wifi patch on their website.
Related
Ok I have search a good bit online surfing the net, and 3 calls to Belkin 3 calls to T-mobile and nothing. Now my wifi works everywhere else, and my labtops connect just fine to the router but it seems like the Belkin N has something blocking it (even tried a shadow with original ROM and would not connect). So I took all the security opitions off along with the firewall and it still failed to connect. If anyone has any solutions or ideas I am willing to try. Thanks guys
(SOLVED WITH US FIRMWARE)
is routerset to b/g/n ?
has router got mac security set-up?
nolovelust said:
is routerset to b/g/n ?
has router got mac security set-up?
Click to expand...
Click to collapse
It is set for B/G/and N. And i dont know about the mac security set-up. But I have tried setting it to just G or B and N and nothing. Tell me more about this mac security set-up.
There is nothing wrong with your phone. The shadow/juno has an internal wireless card that only supports b/g wifi and it's currently not compatible with n radio signals. It will work perfectly with b/g wireless networks. So, if your router has a b/g/n setting, set it to that, but do not set the security settings into a newer format, stick with wep2 or wep and it should work with no problem. If you leave it on n setting only, the internal wireless card in the shadow will not support it. You also have to remember that n wireless is not that widely used and its barely catching on. Many new electronics are still being made with b/g internal wireless cards because they are widely avaliable and come in smaller sizes suitable for phones like the shadow. Currently n wireless cards are fairly expensive and i doubt it will be made avaliable on phones anytime soon as cost would be too high for manufacturing. Hope this helps.
-AC- said:
There is nothing wrong with your phone. The shadow/juno has an internal wireless card that only supports b/g wifi and it's currently not compatible with n radio signals. It will work perfectly with b/g wireless networks. So, if your router has a b/g/n setting, set it to that, but do not set the security settings into a newer format, stick with wep2 or wep and it should work with no problem. If you leave it on n setting only, the internal wireless card in the shadow will not support it. You also have to remember that n wireless is not that widely used and its barely catching on. Many new electronics are still being made with b/g internal wireless cards because they are widely avaliable and come in smaller sizes suitable for phones like the shadow. Currently n wireless cards are fairly expensive and i doubt it will be made avaliable on phones anytime soon as cost would be too high for manufacturing. Hope this helps.
Click to expand...
Click to collapse
Ok I understand that but I have tried that already with all my security off set on just G/B and by them self's also and it still will not connect. I went threw all of this on the phone with T-mobile and Belkin. But I appreciate the help.
suasp0nte said:
Ok I understand that but I have tried that already with all my security off set on just G/B and by them self's also and it still will not connect. I went threw all of this on the phone with T-mobile and Belkin. But I appreciate the help.
Click to expand...
Click to collapse
i have the same problem
d*mn!
has anyone sort this thing out yet?
i have the same issue using stock TMO's ROM...
Just for the sake of discussion, I'm assuming that all of you have T-Mobile Shadow phones that work fine with other wireless routers or public access points? Any problems when turning on security settings on other wireless networks (those that you or your friend can manage)?
If the problems persist with other wireless networks while using your Shadow, chances are that your Shadow's wireless card is faulty, which is not unheard of.
Please comment on your phone's status.
Also, which model of Belkin N router are you all having problems with?
All N routers are typically backward compatible so setting them to mixed mode (B/G/N) would not affect the Shadow's Wifi capabilities.
AC, there's never a wep2...I guess you meant WPA & WPA2.
scenarios
First scenario:
Home
NETGEAR 802.11g/b WIRELESS ROUTER WITH WPA-PSK
RESULTS: fine.. shadow is working great on TMO's and erofich's rom
Second scenario:
GirlFriends HOUSE
NEXXT WIRELESS 802.11g/b WIRELESS ROUTER WITH WEP (cheap stuff)
RESULTS: Excellent, shadow is working fine on both roms
Third Scenario
MACDONALDS ROUTER
UNKOWN ROUTER WITHOUT SECURITY
RESULTS: FINE... Shadow gets connection.
----------------------------------------------------------
Last Scenario
OFFICE
Belkin N-Wireless Router F5D8233-4v3(01) with latest firmware update
Result: No way to get Shadow connected. Even WIthout Encryption, MAC address control off, B & G & N bands, UPNP Off, but my laptop does get WiFi Connection (just 11g compliant WiFi card)
Just to point out, I have the same problem with my Belkin Wireless N router. In the office, I can jump onto our Netgear Wireless N router without a problem. I also have no problem jumping onto any free McDonalds networks, the networks at friends' places, or the free network in the CambridgeSide Galleria out here near Boston. This is definitely not an isolated issue. Nobody with a Shadow can get on my home network.
Customer Call Details Nov 13 2008 04:37
I have an HTC Touch that can connect to other hotspots, but not to my home Belkin router. Sometimes, if there is another connection available, it can see the router, and says that it is Available, but cannot connect; other times it won't even see it. I have checked for firmware updates, but I have the latest. Any help would be greatly appreciated.
Belkin Response Nov 14 2008 22:18
Hi Lilburd,
Thank you for contacting Belkin Technical Support.
We understand that the HTC Touch does not connect to the router. We apologize for the inconvenience caused.
Please follow the steps given below to update the firmware and configure the router:
We recommend that you update the firmware from a computer that is connected to the router with an ethernet cable.
Please download the latest firmware on the router from the link given below. Download the file "3.01.29":
http://www.belkin.com/uk/support/article/?lid=enu&pid=F5D8233uk4&aid=10288&scid=0
and save it to the computer.
- To update the firmware, log on to the router`s web interface by typing in http://192.168.2.1 in the address bar of the browser. The computer should be
connected to the router with an ethernet cable.
Note: If you have changed your Router’s IP address, use that IP address.
- By default, the password is blank. Click the "Submit" button.
- Click on "Firmware Upgrade" under the option "Utilities".
- Click on “Browse” and select the bin file that you have downloaded.
- Click on “update” and follow the wizard.
- After updating the firmware, restore the router to factory defaults by clicking on "Restore Factory Defaults" under "Utilities".
- Reconfigure the router.
Please follow the steps given below for configuring the router:
- Connect the computer to the "LAN" port on the router and connect the modem to the Internet/"WAN" port, using Ethernet cables.
- Take a paper clip, insert the paper clip in the reset hole of the router and hold it for 15 seconds.
- The power light will flash and then come back "ON" solid, indicating that the router is being restored to factory defaults.
- The corresponding lights on the front of the router should be lit up.
- On the computer, check if you have an IP address in the range of 192.168.2.x.
- If not, specify a static IP address, gateway and "DNS" address by following the steps given in the link-
http://web.belkin.com/support/kb/kb.asp?a=2824
- Log on to the router web interface by typing in http://192.168.2.1, in the address bar of your browser.
- By default, the password is blank.
- Click on "Connection Type" in the left hand column under "Internet WAN" heading.
If the connection type is Dynamic (cable):
- Choose "Dynamic" and then click on "Next".
- Type in your “Host Name”, if your Internet Service Provider has provided it. Else, leave it blank.
- Click on "Change WAN MAC Address".
- Click on the button "Clone".
- Click on "Apply Changes".
If the connection type is PPPOE (DSL):
- Choose "PPPOE" and click on "Next".
- Enter the user name and password given by your Internet Service Provider.
- Save the settings.
- Click on the "Home" link at the top of the screen.
Internet Status should show "Connected" on the top right hand corner of the web page.
If the problem persists, please get back to us with the following information:
1. Type of connection provided by your ISP (Is it PPPOE, Dynamic or static).
2. Name of the Internet service provider (ISP).
3. Version number of the router. You would find the version number on the bottom of the device. It would be a number in a series of thousands with a prefix “ver.”.
4. If the internet connection is stable on the computers using the router?
5. If the HTC Touch detects and connects to other networks in the neighborhood?
Lilburd, if you need further assistance please feel free to write back to us and we will be happy to assist you.
Regards,
Belkin Technical Support.
This was the response I got when I e-mailed Belkin, and it worked like a charm
You Solved This Issue
DUDE, Im using the F5D8133 4v3.. thatss the US version..
the latest firmware on the US support page was 3.01.17 if i remember right,
on the BELKIN UK Support page is 3.01.29 and guess what i updated the firmware to the one in UK site .... and....
IT DOES WORK LIKE A CHARM!
FINALLY I HAVE WIFI
bless you and the techsupport guy @ belkin uk
fenix_tx40 said:
DUDE, Im using the F5D8133 4v3.. thatss the US version..
the latest firmware on the US support page was 3.01.17 if i remember right,
on the BELKIN UK Support page is 3.01.29 and guess what i updated the firmware to the one in UK site .... and....
IT DOES WORK LIKE A CHARM!
FINALLY I HAVE WIFI
bless you and the techsupport guy @ belkin uk
Click to expand...
Click to collapse
The same happened to me. I also have a Belkin pre-n router and my HTC Tytn wouldn't get wifi, no matter how or what I tried. I read your comment yesterday and, although the no-so-great new firmware check utility on the web interface said there was no new firmware available, I checked the USA and UK sites, since the Spanish site doesn't even show this router anymore. I downloaded 3.01.29 from the USA site and now my HTC Tytn is getting wifi at last. Thanks a lot, you saved my day.
I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.
Has anyone managed to connect to a WPA2 Enterprise protected network? Using PEAP and MSCHAPV2, I haven't been successful. There seems to a bug in Froyo that was fixed after whatever build the Elocity is using: hxxp://code.google.com/p/android/issues/detail?id=8804 (I'm not yet allowed to post links).
I haven't had a chance to try the latest firmware yet.
Thanks,
..Mel
Thanks for logging this. I have the same issue. I was beating my brains trying to figure out why my Galaxy S would connect, but my A7 would not with the exact same settings.
Damn it
Noooooooooooo. I am waiting on mine being delivered and the sole purpose was to hook up to my work network which is WPA2 enterprise.
I hope someone out there has a fix for this. Donations a plenty for the person who does I tell ye.
I was able to connect to our network via PEAP just fine however this tablet does not have a proxy setting for wireless (this option is reportedly only available on models with 3g). All of my attempts at 3rd party addons to access the proxy settings screen have been unsuccessful as well.
First off let me say I love this tablet and have pleasantly surprised by its build quality and over stability. Secondly let me say I am typing this thread from a $299 Acer laptop from Newegg with 5 bars of wifi strength and has never lost connectivity......ever. The frustration I feel from the iconia every 2 minutes saying I have lost internet connectivity is becoming unbearable. I am sitting about 15ft from my Fios Router and I am not quite sure why this continues to happen. I have run the wifi analyzer app and it is all over the place. Is this something that might be fixed with a future Acer update? Does it possibly have a bad wifi radio? I see a number of people with the same issues, however it does not seem widespread. I did have a xoom for a week or so with no wifi problems whatsoever. Should I return it? I am 4 days into my 14 day return window with Best Buy. I feel bad because the xoom I had before this had a bad screen and now I will be returning this for wifi issues. I just want to be sure before I go through the trouble. Thanks for the help in advance! This is the only forums I trust that have educated Devs.
olson0827 said:
First off let me say I love this tablet and have pleasantly surprised by its build quality and over stability. Secondly let me say I am typing this thread from a $299 Acer laptop from Newegg with 5 bars of wifi strength and has never lost connectivity......ever. The frustration I feel from the iconia every 2 minutes saying I have lost internet connectivity is becoming unbearable.
Click to expand...
Click to collapse
Try a different wireless acess point. Pick up a $35 d-link or similar that is just an AP, and turn off the wireless in your router. I had that problem with a Speedstream modem/wireless/router when I got my Wii, only everything would lose connection with the Wii on. Some routers just suck.
You might try checking to see if your router has a firmware update first.
And just for giggles try turning 'n' off on your router.
Hi
Not related to the Acer A500 but I have the same problem with a Dell N5010 notebook.
At home with a Zyxel WIFI router everything is OK. At work with a D-Link 7000 wifi router it gives me every few minutes no internet access. Everything else (phone, other notebooks) work ok. So maybe it's the router a problem.
Hi there matey!
Dunno if it will help but i had many troubles with different routers over the years. One common thing i did notice was that not all devices gel too well with different encryption protocols. eg...TKIP, AES WPA2.
So have a try changing your wireless security settings or briefly leave it as an open network till you diagnose the problem.
Fingers crossed for ya matey!
TheWatchers said:
Hi there matey!
Dunno if it will help but i had many troubles with different routers over the years. One common thing i did notice was that not all devices gel too well with different encryption protocols. eg...TKIP, AES WPA2.
So have a try changing your wireless security settings or briefly leave it as an open network till you diagnose the problem.
Fingers crossed for ya matey!
Click to expand...
Click to collapse
+1. I had a problem with one of my Android devices not connecting that was solved by changing encription from WPA2 to AES. Try this first.
You're better off returning it than futzing around with it. You're well within your return date and if it not working, it's not going to work.
I have a FiOS router as well and have no issues.
Solution to Iconia Wifi connect/disconnect issue
Greetings members.
I am not a dev, I'm just I guy who loves his Android devices and now can't function without his Iconia.
I began experiencing the Iconia Wifi connect/disconnect issue this afternoon. After several reboots, I googled and found this thread. A lot of good tips but the issue has nothing to do with routers or WPA, and for the love of all that is holy, don't futz around with factory resets or replacing it. The issue is with the hardware and the Wifi drivers in the 3.1 update.
Thankfully, Acer has heard our pleas and has produced a patch and an update.
Looks like the link was blocked by admins (I have to post 7 more...), so just go to acer.com and navigate to the drivers and downloads section, navigate to the tablet/iconia tab/a500 section, go to Patch and download.
Extract and copy the zip file to the root of a microSD. There is actually a pdf with full instructions in the zip.
Bottom line, follow the instructions in the PDF and it WILL restore your Iconia Wifi.
Once the Wifi is back up, check for updates and there is another update to 3.1.
Apparently the 3.1 COM_GEN2 updates for most all countries had this flaw and these two updates are intended to fix the issues.
Just read through the PDF and then follow the steps and you'll be surfing again.
Thanks everyone for this site. Love the help and the insights. And, enjoy your A500's once again.
There are postings from some Xoom users who also had WiFi issues with the 3.1 update. Since the WiFi problems mainly started with the HC 3.1 update, I think it's safe to say most of the problems have been related to the O/S.
I'm using DD-WRT on my linksys wrt600n router at home and it's worked fairly well.
Rob
@OP +1
@Slaught3r - thanks, I've tried all the different roms and was beginning to think it was mine only.
I also get wifi connectivity problems, even after the pqtch.:'( I only got it yesterday, so it may be going back.
Could the issue instead be related to your routers? Maybe the channel you've got them configured on is crowded?
I'm just wondering because, well, I have not had any kinds of WIFI-issues at all on any of the ROMs I've tried except only where the channel has already been really crowded by several routers on the same channel.
Doubt it. I'm not using a custom rom on my A500 yet. Still the stock Acer rom. I have it configured to automatically connect me at home, work, and even at church of all places. Until yesterday, everything worked, then...weirdness. Without making changes to my routers, the patch (and subsequent OTA update) seems to have fixed the issue nicely.
Be sure to follow the instructions contained in the zip download from Acer. If you are on a custom Rom and are having this problem, most likely the dev will need to release a patch based on the Acer patch.
Thanks to Slaught3r for the info about the patch. It is important to follow the directions re: the buttons in the PDF exactly. The directions on the Acer support web site differ about when to release the power button versus the volume button, and those directions do NOT work.
Before you do this you may want to disable your router's wireless security, at least until you get the update installed.
@Slaught3r:
Acer doc suggests the problem was fixed in A500_4.010.10_COM_GEN2.
I am experiencing frequent but short Wifi disconnects with Build A500_4.010.11_COM_GEN2.
Can you tell me what build you applied your patch to and what you are now running? I am trying to decide if applying this patch is appropriate, considering I already have a later build.
Any further info from anyone reading this would be appreciated.
Slaught3r said:
Greetings members.
I am not a dev, I'm just I guy who loves his Android devices and now can't function without his Iconia.
I began experiencing the Iconia Wifi connect/disconnect issue this afternoon. After several reboots, I googled and found this thread. A lot of good tips but the issue has nothing to do with routers or WPA, and for the love of all that is holy, don't futz around with factory resets or replacing it. The issue is with the hardware and the Wifi drivers in the 3.1 update.
Thankfully, Acer has heard our pleas and has produced a patch and an update.
Looks like the link was blocked by admins (I have to post 7 more...), so just go to acer.com and navigate to the drivers and downloads section, navigate to the tablet/iconia tab/a500 section, go to Patch and download.
Extract and copy the zip file to the root of a microSD. There is actually a pdf with full instructions in the zip.
Bottom line, follow the instructions in the PDF and it WILL restore your Iconia Wifi.
Once the Wifi is back up, check for updates and there is another update to 3.1.
Apparently the 3.1 COM_GEN2 updates for most all countries had this flaw and these two updates are intended to fix the issues.
Just read through the PDF and then follow the steps and you'll be surfing again.
Thanks everyone for this site. Love the help and the insights. And, enjoy your A500's once again.
Click to expand...
Click to collapse
I had the same issue after the update to .11. However I solved my issue without the patch.
On the Acer website, I searched on wifi and came upon this link: "What can I do if I am unable to connect via WiFi after completing an Iconia Tab A500 system update?"
I tried the first suggestion of turning the wifi on and off with a restart. It didn't work. The second suggestion is to do a hardware reset with using a paper clip to the hardware switch. That worked; keep in mind that you need to perform that reset twice. The instructions are pretty clear cut.
pbaker99 said:
@Slaught3r:
Acer doc suggests the problem was fixed in A500_4.010.10_COM_GEN2.
I am experiencing frequent but short Wifi disconnects with Build A500_4.010.11_COM_GEN2.
Click to expand...
Click to collapse
@pbaker99
I was on Acer_A500_4.010.09_COM_GEN2 (pre patch where Wifi was acting up)
After the recent OTA, I'm on 4.010.10_COM_GEN2
My system shows "Up to date" so there is no .11 for me (at least not yet).
It has been a couple days since the patch and subsequent update from .09 to .10 and everything has been fine for my model. Sorry you are having the issues you are.
Many times the wifi problem is caused by incompatible router software. While you would think Acer would take care of this via software upgrade, they do so only for limited routers, apparently.
I just spoke to Dlink, the manufacturer of my router, downloaded updated firmware, works perfectly for two days.
The_Monkey_King said:
On the Acer website, I searched on wifi and came upon this link: What can I do if I am unable to connect via WiFi after completing an Iconia Tab A500 system update?"
Click to expand...
Click to collapse
Thanks for posting this. Luckily I have fixed my WIFI problems with the first step.
At some point my router had a problem that somehow stuffed up Iconia's WIFI. Just rebooting didn't help as it still couldn't connect to any network. Switching wifi off and rebooting did the trick for me.
I have reached my wit's end trying to resolve my problems, so I'm posting here for ideas on fixing this, any input is appreciated!
When this started I was on stock, rooted, ICS 4.0.3 and had been for months. My wife has a nexus s with the same config and hers works fine.
Last week, my daughters sidekick 4G stopped having wi-fi internet connectivity. I turned her wi-fi off, then back on and it was fine and has been ever since. Later that night, my nexus did the same thing, the same procedure resolved it. Ever since then, my wi-fi will only work for 1-5 minutes after turning the wi-fi on. This is the only thing I can think of that changed that could have caused this. This was the first night we connected her sidekick to wi-fi.
The wifi symbol is up there, it'll be blue for up to half an hour, but won't have internet connectivity for long. One thing I noticed pretty quickly was that even though the grey wi-fi symbol is there, I can't access the router settings at 192.168.1.1 from the phone. I thought the grey wifi symbol still indicated I was connected to the router still, but it's not working. Each time this happens, I can turn wi-fi off, back on immediately and it'll work for 1-5 minutes. It appears that the more I constantly use it after turning it back on, it seems to maintain connectivity longer.
Last weekend, just after these issues started, I visited my sister and my phone operated on her wi-fi all weekend just fine.
When I came back home, my problems started immediately.
Here's what I've tried in pretty much the order I tried them:
I started by uninstalling avast, facebook, and autostarts
selected "Forget network" in access points screen and reconnected
Factory reset
Wipe dalvik cache & fix permissions
see if it worked without sim card in (it didn't)
flash GB broadcom driver
Switched router channel from 6 to 1
flash stock 2.3.6 (wi-fi problems still present)
flash OTA ICS (still had problems)
flash stock 2.3.6
flash OTA ICS
re-root
Flash PixelROM 1.60 LiteTouch
factory reset router (No wifi problems on using open network and default SSID for 30 minutes!)
resetup WPA Personal security and rename SSID same as before
Worked for another 15 minutes or so after this
flashed stock 2.3.6
flashed OTA ICS
re-rooted
Restored nandroid backup - quit working after this step
Factory reset router - worked for about 15 minutes, I decided I was ok so I setup security and SSID as before, then it quit working again
flashed PixelRom 1.60 LiteTouch
flashed stock 2.3.6
Flashed OTA ICS - THIS time I did not restore my google backups from the cloud, fearing that this was somehow restoring something that was causing me problems. It did not help.
Changed SSID on my router and reconnected phone
I have spent countless hours trying to fix this. I don't believe it's the hardware because the router factory reset seems to help quite a bit, works fine on unencrypted default router settings, and it worked on my sister's wi-fi.
I have nmap and wireshark and have a basic working knowledge of them. I have adb setup and usable on my computer. I also have dd-wrt installed on my router and have for years. Is there any kind of IP or hardware logging I could perform with these tools to help figure out what's going on??? ANY help is GREATLY appreciated!!
Well i'm no expert with any of this, but it sounds more like a router issue.. If both your sidekick and nexus have the same characteristics of failing wifi, it cant be the devices..
If you've already reset your router and it does the same exact thing, maybe it is something wrong with the router itself. You said it connected fine at your sisters house, so it cant be any hardware within the phone.. The only thing I could think of is maybe try a different router in your house to see if it works? If that helps get rid of the connectivity issue, then you can just get a new router and be happy with the wifis
I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.
nevarDeath said:
I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.
Click to expand...
Click to collapse
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck
Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.
It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!
swamp goblin said:
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck
Click to expand...
Click to collapse
I haven't changed any settings, until this problem began, which makes this even more maddening. I appreciate your input regardless
Oogway13 said:
Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.
Click to expand...
Click to collapse
I haven't removed it. I thought I had a model that couldn't go back to stock, but I WILL be looking into this. The other devices connecting fine are Sidekick 4G, Wife's Nexus S, Acer Aspire one, HP tx2000 laptop, and my wife's HP laptop. I also have my satellite receiver connected via ethernet.
SpookyTunes said:
It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!
Click to expand...
Click to collapse
I will certainly try these settings. Thanks for the tip on the wiki page
I had this problem too, I solved only flash again my radio...
Try if solve...
Or if don't work try to make a reset.
Sent from my Nexus S using Tapatalk 2 Beta-4
SpookyTunes said:
...Try forcing "WPA2 with AES only" if all clients support i...
Click to expand...
Click to collapse
THIS FIXED IT! I tried it first since it was the simplest solution and I've been 4 days with no loss of connectivity since I changed it to AES only, which all my clients do support! Thanks so much!