Related
Installed the OTA update and re-applied unRevoked root. I can't maintain a wireless connection for long. I initially thought it was my router and rebooting the router actually does temporarily fix the problem but it happens again. How do I know it is not the router? My other wireless devices are working! I disable wifi on my phone and reconnect but still have no service. Rebooting the router is the only temporary fix. Gah.
I would say it may be the Rom over the OTA. That is of you're running a custom Rom or anything that's not stock. Are you running the latest radio? The .09.10,check to make sure. If your other devices are working without dropping then that eliminated the router for the equation. If you want to make sure then try connecting to any open WiFi connection to see if you have the same issue. If you do then u know for sure it's not your router.
I would try doing a nandroid first then wipe cache and davlik and flash your Rom again. Do not do a factory reset. Once you boot up just test the WiFi again b4 doing anything. If it works then just restore your apps if needed via Titanium backup.
If u have the same issue then at that point u can do a nandroid restore.
Multiple option,am confident one of them will work,good luck.
Sent from my PC36100 using Tapatalk
i had the same issue running fresh 3.3.0 .. and what i saw that my phone wasnt connecting at all but my laptop and my sisters top were all connecting. So i went into the wireless router ip address .. whatever yours may be. re-entered my password and WALA.. it started connecting to my phone again.. it was strange but thats what worked for me
Forgive me if I missed it, but I've been trying to figure out the answer to a problem with my wifi connection.
Basically I had a rooted stock release on my samsung fascinate and I wanted to get the newest official version. So I installed clockwork mod via the marketplace and downloaded the most recent official update's .zip from the web. I couldn't get clockwork to work, tried several things but just couldn't get it to flash the update, (kept saying the update.zip was unsigned). So I thought... "oh well I'll just use odin to flash back to unrooted stock, update 2 or 3 versions ota, then root again." This worked but somewhere in the mess I lost the ability for wifi to start up, just cycles on and off every couple seconds when you try to turn it on.
I flashed back to stock via odin again, then it would stay powered on. However, now while the phone can see the networks when I try to get it to connect it sits on the "obtaining IP address from..." option until it finally says unsuccessful. I've tried purposely inputing the wrong wep password but it doesn't complain it's wrong, so I don't think it's even getting that far.
That's pretty much the state of it now, however I also tried updating to both the stock and debloated versions of the leaked froyo rom from a post here with no change, and have cleared cache/hard rest several times.
Any help would be great. Thanks in advance!
What rom are you currently on, and what modem (baseband) are you currently on?
Number one, you need to flash CWM with Odin, or else you get that unsigned error. Number two, have you tried manually inputting the ip address, subnet, and gateway? If you try manually and it doesn't work, then try power cycling the router. (unplug it for 30 seconds).
Since you say you Odin-ed back to stock it's unlikely that the wifi got messed up there, so I'm more inclined to check the router. What model router is it?
I'm currently using a rom of the leaked froyo eb01 which was debloated / deodexed, with root and clockworkmod, downloaded from a post here on the site that was left by TAPOUT27 (I'd link to it but the forum will not let me). Baseband is S:500.04.V.EB01. Was considering installing superclean, but decided I don't want to keep switching it up while trying to troubleshoot.
By the time I figured out I needed to flash clockwork via odin I had already flashed back to stock... (my noob mistake)
I thought it might be the router at first too, but I've power cycled it, my other devices (laptop, wireless bridge, wifes stock fascinate) all work. and I've also tried it with a couple networks that I don't usually have a problem with in work to no avail. Also tried using a static IP on phone, but not working.
By any chance are you using a time warner modem with built in router?
The router at home is an actiontec MI424WR that Verizon fios installed, at work it's a Verizon mifi 2200.
I was able to add another piece to the puzzle today and now it only gets stranger. I tried connecting via WPA encription and it worked fine. So it looks like it's only WEP and open networks that are broken. Tried with both routers to verify.
bump......
Whoa this.one is a mystery. I'll try to think of some things to try..
I was beginning to think it was a hardware thing until it connected via WPA, now I'm sure it's got to be a software thing.
Try resetting your router..worked when I had same issue.
Bob
Sent from my SCH-I500 using XDA Premium App
Tried that, but it's not just one router, it's three, and they all work when other devices try to connect. on all settings not just WPA.
I had similar problem and i run 2. Make sure master has DHCP server on and the 2 slaves do not act as dchp servers, also make sure settings on all 3 for RIP are set to"both" and use RIP1 which is universal. That solved my issues connecting.
Rock on
kikakee said:
Tried that, but it's not just one router, it's three, and they all work when other devices try to connect. on all settings not just WPA.
Click to expand...
Click to collapse
Samsung Fascinate - EB16/Froyo.
SuperClean 2.6 Voodoo
MTM iOS keyboard
Cyanogen Boot Animation
Warning: I know just enough to be dangerous
Dalamar1320 said:
Since you say you Odin-ed back to stock it's unlikely that the wifi got messed up there, so I'm more inclined to check the router.
Click to expand...
Click to collapse
Please don't take this the wrong way, but your reasoning is backwards. When troubleshooting a problem, the most likely culprit is always whatever changed most recently. That doesn't mean that's always the answer, but in most cases, whatever changed right before the issue happened is the cause of the problem.
Restoring with Odin is a massive change, and is not foolproof. Since wifi worked fine before the Odin flash, doesn't afterward, and other wifi devices still work on the same router, the logical explanation is that something went haywire in the Odin flash. I would suggest using all available wiping methods (factory reset within the OS, and data/cache/dalvik cache within CWM), and then attempt another Odin flash using Adrynalyne's stock DI01 package, and see what happens after that.
Posted from my EB01 SuperClean Fascinate with Voodoo
Hi, I recently made an attempt to enable ad-hoc connectivity to my Acer Iconia Tab using this guide: http://forum.xda-developers.com/showthread.php?t=1060909&highlight=ad+hoc
After following these instructions I was able to connect to my phone through barnacle and I was able to surf the web on my tablet. Both Wifi and Ad-hoc were working right after I replaced my wpa_supplicant file and everything was working perfectly but around 30 minutes later when taking my tablet out of sleep I attempted to connect to my Wifi connection but it gets to "obtaining IP address" for about 4 seconds then rapidly says "disconnecting" and then back to "obtaining IP address". It does this 7 times before disabling the connection and staying on "scanning".
I have tried replacing the wpa_supplicant file with my original but the only differences that i have noticed are that it does not detect my phones ad-hoc connection and that it does the Ip address and disconnecting loop for a total of 10 times before disabling my Wifi connection.
My tablet is rooted and running the official android version 3.1.
I am using ES File Explorer to move and replace the wpa_supplicant file and to change the permissions for the modified wpa_supplicant file.
So, i was wondering if anyone else has the same problem or a solution of any kind. I was also wondering if anyone would be willing to share their stock wpa_supplicant file for the Acer iconia for 3.1 honeycomb
Download the wifi fix file on Acers support site.
FloatingFatMan said:
Download the wifi fix file on Acers support site.
Click to expand...
Click to collapse
I tried this but when running the patch the android robot appears with gears in it's center appears for a few seconds and then the gears get replaced my a warning sign and exclamation mark.
I have tried re-formatting my sd card and unrooting before running the patch but my initial problem persists along with the exclamation mark on each attempt to apply the patch. Decrypting the file results in corrupting the file and making it unable to extract it's contents.
I d/loaded the patch direct to my tab and ran it inside android. You might've curupting the file moving it.but strange
I'm having the same trouble Today. Finally got it to tether with barnacle. After doing that once I Now get the endless loop of "obtaining IP". I am at work so cannot check other wifi yet but will when I get home.
Sent from my MB860 using Tapatalk
Another fix that may work is deleting the file dhcpcd-wlan0.lease located in /data/miscellaneous/dhcp
Thanks, I ended up just restoring but if I run into this problem again I'll definitely try that
Downloading the Wifi Fix directly from Acer seemed to do the trick for me. At least for connecting to my home wifi. I'll be testing tethering at work again today to see if it repeats the problem, but hopefully it does not.
wpa supplicant for ad hoc use
Hello everyone. I am new to the forum, but have been reading the posts for over a month. I bought my Acer Iconia A500 to be more convenient than lugging around my 17" laptop. After purchasing was when I realized that I couldn't tether it to my JB iPhone 3gs. Started searching and learned how to root the tablet. Mine came with HC3.1. Rooted the tablet, found an alternant wpa-supplicaant file, followed the instructions, and pleasantly surprised that I could then tether to my phone. THEN Acer sent an ota update (4.010.11_com_Gen) I accidentally installed the update before unrooting. Messed everything up, and had to do a factory reset. After the reset I rooted again. Everything working fine until I tried to find the wpa file again. Couldn't find the same one. Used a different one. Followed the same steps as before and suddenly my wifi went wacko. Wouldn't stay connected, kept looping. Very frustrating. Undid the wpa and could connect to regular wifi. Did more research and found the original ad hoc file. Used it and now have no problem connecting and disconnecting. MORAL TO THE STORY: use the wpa supplicant ad hoc file that has XOOM in the file name. I would have saved myself a weeks worth of frustration had I just kept looking.
Btw....I tried all the 'fixes posted and nothing helped the looping until I rooted and used the correct supplicant file.
Good luck!
tesab613 said:
Btw....I tried all the 'fixes posted and nothing helped the looping until I rooted and used the correct supplicant file.
Click to expand...
Click to collapse
Could you share the file? I have one but it doesn't work so I reverted to stock.
bpivk said:
Could you share the file? I have one but it doesn't work so I reverted to stock.
Click to expand...
Click to collapse
The file attached to the first post here:http://forum.xda-developers.com/showthread.php?t=1060909&highlight=ad+hoc worked perfectly after I did factory reset. But instead of following those instructions to the letter make sure you turn on airplane mode or disable wifi before messing with the original file (renaming it to wpa_supplicant.old) and setting the permissions of the modified wpa_supplicant file to User:RWE Group:RWE Other:RW only.
I also restarted my tablet before enabling wifi just in case and my tablet has been connecting to ad-hoc and wifi connections without any issues whatsoever even after multiple restarts.
Order things went down for me were, upgrade to the OTA update from Acer... Then I rooted, used the ad-hoc wifi thinger, tethered once before getting endless loop. Then I downloaded the wifi fix directly from Acer, installed it via sd card as they say and I have not had any issues since. Tethered as I type this, 3rd time today as well.
I'm not sure if using the ad-hoc then acer update changed anything, but it works great now.
Sent from my A500 using Tapatalk
Vereynn said:
Another fix that may work is deleting the file dhcpcd-wlan0.lease located in /data/miscellaneous/dhcp
Click to expand...
Click to collapse
A500 here too and ran into same loop issue. Deleting the lease file worked like a champ, thanks! Rooted stock 3.1, haven't installed latest Acer update.
WT
I am also getting the looping IP address (DHCP) after applying the wpa_supplicant as directed. I tried to reset the Acer A500 with a pin two times like it was listed on Acer.com. That did not fix it. I tried to delete the dhcpcd-wlan0.lease but could not find it anywhere. I don't have a /data/miscellaneous directory. Only found /data/misc/ and that did not have the lease file. I then tried the wifi patch from Acer and then updated to version 4.*^*.13 (latest update) but it is still looping. Does anyone have any ideas? Is it possible I got the wrong wpa_supplicant that has a problem? I am now able to see ad-hoc networks as well as my router but with the looping problem.
Thanks,
Rich
this also happened to me
This happens to me when I switch networks.I turn off wifi del the saved networks,reboot then turn wifi back on and resetup my wifi password.I do not know a better solution.some claim this is worse with some routers.
Can't obtain ip address
Hi I'm having trouble with my sons acer iconia b1 when he first go it everything worked perfectly until I went onto it a few weeks back it isn't connecting to wifi and is saying that the IP address is unavailable. I have tried everything it has had factory reset I reset the router everything I could think of I done it. I know it's not te router as my other son has th same tablet and his works perfectly. The only thing I can think of is he has went into it and done something and I don't know how to get it back. I'm at the point where I'm close to throwing it at a wall as it's frustrating me so much
Thanks
I just recently got this tablet from someone else. (This person had no problems and is trustworthy in reporting all that was done and care taken with it, even offering on advice on things you can do with it.)
My first step was to connect to Wifi. This happened without problems.
When returning home from work where I also connected, my wireless connection(s) said "Disabled" after trying to obtain the IP where they worked fine before. The first time this happened I had to do a factory reset to solve it (hardware reset didn't do it).
Today, it is happening again. I woke it from "standby" to start using again at home and received this message. In fact, any attempted WiFi connections comes up saying "disabled" after attempting to connect and obtain an IP. Again, these are saved connections that previously worked. I know for a fact that it's not the routers.
Please help if you can. I've tried:
1) power off/up 2x in a row to no avail
2) removing and adding back the connection with the appropriate passwords
3) a factory reset but I really don't want to do that again because I'm afraid flashing it back will bring back the same problem.
3) I haven't put any new apps on it since it last worked earlier today so I can't figure that as an issue. The first time it happened a week ago was when I'd just gotten it. It has worked for almost a week without problem. I did nothing special but travel home.
SPECS:
A500 Wifi
Rooted (was unrooted when it first happened); rooted now using IconiaRoot v1.3
(previously rooted and unrooted with Gingerbreak which would no longer root)
ROM: Honeycomb 3.1 with Virtuous Picasso v.1.1.0
Kernel: 2.6.36.4-UNITY-V5-ge7dee2a-dirty
Thanks in advance.
it's a known problem with this tablet when moving from one access poin to another, introduced with the update to 3.1. you have to reset using the pin hole near the micro USB port. i use a staple.
it may take a few tries. if it never works, there's a specific file you can delete if you're rooted. if you cant do that, you will have to do a device wipe.
There is a known issue of connecting to PEAP/EAP networks, which most work networks are. After connecting successfully, often many times, it will suddenly fail to connect. It also shows the signal from the access point to be very low or non-existent. After this happens, it can also cause problems with other PEAP/EAP access points as well.
If this is what happened to you, here's the fix. Try to connect to the access point giving you problems. While it is stuck on trying to connected, click the access point name and tell the tablet to Forget it. Then enter the same access point information manually and try to reconnect. This fixed my problem, and the fix sticks for a few weeks or so until it comes back.
Interesting, I had this same problem a few weeks ago when I visited my parents house. After a couple reboots it just started magically working again and didn't think anything of it. Their router is whatever the Verizon FiOS people install when you get their service.
Thanks, GeekGuy and Falkner, but.....
I've tried both before, but I went ahead and tried both of your recommendations again (pin reset and connection attempt/forget/add). Neither fixed it.
I would like to try to delete the file that Falkner mentioned, but you didn't specify a name and/or location of it. Can you share that?
I could never find what file to delete, so I've just installed a new ROM (thanks to XDA for info on all the how to stuff).
We'll see if it repeats.
Gone from V.Picasso v.1.1.10 with HC 3.1 to Taboonay 2.1 with HC 3.2.
Thanks for the attempted help!
Just guessing but I would say your problem is solved since no reply from yesterday?
Per my last post, I've switched ROMS. As it happened randomly before, I can only wait to see if it happens again. I will post back if it does.
And....as of tonight it happened again.
Note: Different ROM working since the last post 9-26-11.
ROM Taboonay 2.1
The only thing I can wonder about is if it happens when it tries to connect to a network that is actually down such that it cannot obtain an IP that actually gets internet access. However, it was "disabled" when I brought it up before ever trying to specifically reconnect to a network to realize the ISP wasn't doing their part.
Still....no reboots, or hardware resets have worked. I'm working on an image restore of only the system from the 9.25 install of the ROM rather than a factory data reset. Not sure if that would have been better. Trying to save some of what I've done recently. Gonna have to get used to a weekly backup if this is to continue.
Grrrrr..........restoring a backup turned out to be the last ROM. After reinstalling Taboonay 2.1, I still had all my apps and found the same problem. I'm doing a factory data reset as it's the only thing that fixed it before :-(
The only "oddity" I've experienced has been since last Thursday. The Android Market doesn't even recognize now that I have another device. Have communicated with them; they are investigating and saying they have received reports of this on free downloads giving an "unable to process purchase" message. It updates installed apps, but I cannot download any new ones through market, appbrain -even the appbrain app only and not to the market app. I can download through Amazon, so it's the Market issue. Still, that shouldn't affect this issue.
If you have any constructive feedback, I'd appreciate it!
This was happening to me. I had problems with every rom I tried until the following combo: Taboonay 2.2 with Richard's Villain ROM 3.7 kernel. Every other combo would lead to erratic wifi...now it hasn't happened in 2 days. I don't know why this is happening as many of the roms I tried claim to have the wifi fix integrated. I hope this helps. Just flash the latest Taboonay and then the kernel zip file on too of it. By the way, latest rabbinate is 2.2....NOT THE ONE YOU HAVE NOW.
Sent from my A500 using xda premium
So I dont exactly know what is going on. I go to connect to a wireless network and it will start to connect, say its obtaining IP adress, and then refresh and start all over again. It never actually connects and stays connected. I know its not the router because I have tried numerous networks (that worked before) and now they just stopped working. I did have trouble with root and I re unlocked the tablet because root wasn't working. Is there anyway I messed something up? I installed the 3.2.2 rooted rom and now I flashed back to moray both with the same non-working wifi result.
Anyone know what is going on?
smith3jk said:
So I dont exactly know what is going on. I go to connect to a wireless network and it will start to connect, say its obtaining IP adress, and then refresh and start all over again. It never actually connects and stays connected. I know its not the router because I have tried numerous networks (that worked before) and now they just stopped working. I did have trouble with root and I re unlocked the tablet because root wasn't working. Is there anyway I messed something up? I installed the 3.2.2 rooted rom and now I flashed back to moray both with the same non-working wifi result.
Anyone know what is going on?
Click to expand...
Click to collapse
Did you by chance restore system apps and data through Titanium Backup? Sometimes wifi is messed up by restoring a previous version of the system app and data over a newer version supplied by a custom Rom.
You might want to just wipe everything in recovery, reflash your Rom and set it all up again fresh.
my WIFI was messed up when I swiched Kernels way back. I had forgotten to push one of the files... when you switched ROMs, did you wipe first or did you just install one over the other?
have similar issue after going from hammerhead 3.2 to moray 2.2.2.
Infrastructures wifi works fine, but whe trying to connect the xoom to an ad-hoc (from Nokia jokiuspot) just keeps displaying "obtaining IP address". Never had a problem with hammerhead? Guessing it has something to do with the dchp client on the Xoom¿
Certainly not a big problem, and something I am more than happy to live with as is.
everything else working spot on. Using a UK wifi only!