There have been loads of Posts about Android WiFi switching itself off, affecting various devices. The scenario is that the WiFi switches off spontaneously after previously working OK. Try to switch it back on, and it will switch off again after about 10 seconds.
I have tried ALL the suggestions posted in various forums but regrettably the only solution so far has been to reinstall the device Firmware.
This has happened to me twice now, so I'm trying to find a solution before it happens again which does not involve a Firmware reinstall, with the associated aggro of reinstalling Apps and setting everything up again.
SURELY there must be a method of re-initialising the WiFi via ADB or the Terminal Emulator, or something similar !
The machine in question is a Dropad A8 tablet, originally running Android 2.3 and now Android 3.0 Honeycomb. Like I said before, this has happened with both Firmwares, now on two (total) occasions.
Over to you, boffins !:good:
rasputin2011 said:
There have been loads of Posts about Android WiFi switching itself off, affecting various devices. The scenario is that the WiFi switches off spontaneously after previously working OK. Try to switch it back on, and it will switch off again after about 10 seconds.
I have tried ALL the suggestions posted in various forums but regrettably the only solution so far has been to reinstall the device Firmware.
This has happened to me twice now, so I'm trying to find a solution before it happens again which does not involve a Firmware reinstall, with the associated aggro of reinstalling Apps and setting everything up again.
SURELY there must be a method of re-initialising the WiFi via ADB or the Terminal Emulator, or something similar !
The machine in question is a Dropad A8 tablet, originally running Android 2.3 and now Android 3.0 Honeycomb. Like I said before, this has happened with both Firmwares, now on two (total) occasions.
Over to you, boffins !:good:
Click to expand...
Click to collapse
search on google play fxr wifi
Yes search fir fxr wifi
"NEVER CALL YOURSELF NOOB BE A NEWBIE"
PM me if u need help
Sent from MOON......
MOKHD said:
search on google play fxr wifi
Click to expand...
Click to collapse
Thanks for your reply.
The problem arose again yesterday evening, thankfully after I had downloaded + installed fxr wifi, plus another similar app.
Sadly neither worked, so I was stuck with doing yet another firmware install. This time I chose Android 2.3 (Genesis 3 ROM v2.1.1) which is the same as we run on another identical tablet here, and has never given problems. (Previous firmware was Android 3.0, Genesis 3)
The reinstall went OK and the WiFi started to work again ...
Any more ideas ?
Related
Hi everyone.
I have recently upgraded my SGA from original 2.2.1 to 2.3.3 XXKPE and i have detected an issue when i try to use the WPA + AES combination. The phone detects the wifi but it tries to validate the password a few times and then it is disconnected...
When i tried to connect with the older firmware (Froyo 2.2.1) i could connect the first time but when i lost the connectivity my wifi changed it's state to error and the only way to reconnect was restarting the phone.
No issue detected with WEP or WPA + TKIP.
Anyone else has the same problem? If not, can you tell me your firmware version?
Many thanks in advance
Same situation: S5830 + ASUS WL500W works only with WPA TKIP. But with TKIP speed is limited to 54mbps. Android OS 2.3.4
Just picked up a Samsung Galaxy Ace running stock Android 2.3.4 (baseband S5830LUBKP7, kernel 2.6.35.7-perf-CL366939 [email protected] #1), and seem to be having this same problem.
My home wifi is set to WPA2 Personal+AES, and when the correct passphrase is entered, the Ace just continuously cycles through "Connecting... Disconnected", over and over.
If I drop back to WPA Personal+AES, I get the exact same thing. *However*, if I drop to WPA Personal+TKIP, the phone connects immediately.
I really don't want to use TKIP, as it has known exploits. Is there a known FOTA update for a US-market, unbranded Galaxy Ace that fixes this, or is there any known workaround except "don't use AES"?
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
evilxdeadly said:
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
Click to expand...
Click to collapse
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
knoxploration said:
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
Click to expand...
Click to collapse
Just update it over the air from setting -> about/phone -> update.
Make sure you have backed up the data like contacts and sms.
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
alexnm said:
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
Click to expand...
Click to collapse
Check the OP date?
Oops, didn't see that, sorry :$
alexnm said:
Oops, didn't see that, sorry :$
Click to expand...
Click to collapse
No need to be sorry. You're replying to a thread that's current, in that I replied to it with my own problem. (And I did so because it was the only thread that came up in the Ace forum on a search for AES, which seems to be specific to the problem. Didn't seem to make sense to start a new thread when this one covers the same topic.)
Hi, I finally decided to post my question after many hours searching trough google and xda.
Two weeks ago like many of you I uptdated my x10 to pre-rooted 2.3.3 stock Rom. At this moment I successfully tested wifi hotspot and usb tethering built in fonctions.
But Recently I tried to use it again but any time I checked the option, Android activate it for a second, an then says me "error" under the option name. Usb tehter can't be reactived at all and wifi hotspot can be checked but always uncheck himslef with the error subtitle.
Anyone facing this issue or know where it can come from ? And maybe the fix of course ^^.
Hope I made my self clear because actually I'm french.
Shootereyes said:
Hi, I finally decided to post my question after many hours searching trough google and xda.
Two weeks ago like many of you I uptdated my x10 to pre-rooted 2.3.3 stock Rom. At this moment I successfully tested wifi hotspot and usb tethering built in fonctions.
But Recently I tried to use it again but any time I checked the option, Android activate it for a second, an then says me "error" under the option name. Usb tehter can't be reactived at all and wifi hotspot can be checked but always uncheck himslef with the error subtitle.
Anyone facing this issue or know where it can come from ? And maybe the fix of course ^^.
Hope I made my self clear because actually I'm french.
Click to expand...
Click to collapse
I use Baracle to solve the issue with wifi tethering
https://market.android.com/details?id=net.szym.barnacle&feature=search_result
Yeah this is the solution I used to adopte when was on 2.1. And it was the best until the update.
But as far as what I tested when built-in tether worked it's clearly better. Not just an Ah-hod network but a real hotspot. Basically it's easier for other devices to connect and remember the password without configuring everything especially on windows.
And the usb option was even better, nothing to configure, no password, battery charging during tethering.
Anyway thank for the advice, until I get the solution I'll probably continue to use this app.
When you say "solve the problem with wifi tethering", do you mean you have the same one ?
Sent from my X10i using Tapatalk
Please, no one else, am I the only one facing the issue ? Even on an other device maybe ?
Finally I used SEUS to repare and root it like azazu said. Everything is back. Didn't find any other solution
Wifi hotspot error
Shootereyes said:
wifi hotspot can be checked but always uncheck himslef with the error subtitle
Click to expand...
Click to collapse
I have the same problem and it never has been working from the start ! but USB tethering has no problem. The only way to fix it is to re-flash ?
Well I guess this is the best until someone more expert than us find a solution. I made a reparation with SEUS (sony ericsson update service) and then restore all back with Titanium Backup. Remember to save your contacts and sms before (cause Titanium doesn't). It only took one hours to get it all back just like before (root, bravia, Xloud, fps uncap...)
Hotspot error UNSOLVED 2012-02-01
Here's what I've done so far. I've suffered from this issue on two different Samsung Galaxy TAB's 7" (1 generation), two different Samsung Galaxy S2, two different HTC Desire HD, one ZTE Blade.
This issue is NOT caused by:
*Manufacture of phone
*Internet Service Provider (ISP)
*Operator
*Bluetooth ON/OFF
*root ON/OFF
*Stock Kernel
*Mod Kernel
*Stock Rom
*Mod Rom
*Stock Modem
*Mod Modem
*Android version: 2.3+ has this issue. (I've experienced a different issue on 4.0+; the Hotspot is up running although no device can connect to it.)
The only solution I've found is:
(From Clockwork Recovery):
Wipe Data(system reset)
Wipe Cache
Wipe Dalvik
Format Cache
Format Data
Format System
-Install a Rom (try a different one from what you are using right now).
Reboot
RESULT:
Hotspot working fine....for a while..
When it stops working; you'll have to do the steps above again. Install a different ROM, now you probably can return to your previously ROM which had this issue first. It will probably work. If it doesn't, switch ROM till you find one that works. Sometimes, total randomly; you will be able to use ROMS which this issue has been present earlier.
Yet, this is NOT a permanent solution. You will, no exceptions, experience this issue, on whatever ROM, modem, kernel, stock, not stock, phone, whatever, whatever you choose.
Here's one scenario which I couldn't figure out:
Galaxy TAB 7" 1st generation.
Android 2.3.4
*HOTSPOT ERROR*
WIPE/FORMAT
RE-Flashed Same Rom
*HOTSPOT WORKING*
1 hour later
*HOTSPOT ERROR*
WIPE/FORMAT
RE-Flashed Same Rom
*HOTSPOT WORKING*
5-10 minutes later
*HOTSPOT ERROR*
WIPE/FORMAT
RE-Flashed Same Rom
*HOTSPOT ERROR*
?????
I've also noticed that USB tethering is affected by this issue aswell.
If you have it working, congratulations! Use it while it lasts, nothing stays forever.
regards
/enklast
Hi, I'm having a curious problem with my S3 and I've been unable to solve it. I watched the "noob" video and tried searching these forums as well as a google search with various combinations of the wording for my problem. Nothing matching my issue turned up, I hope I didn't miss anything.
I recently bought a S3 second hand (yes, i know, i should have known better). It was rooted and running some kind of custom ROM when I first turned it on, but I was willing to deal with it until I double checked the procedure for getting it back to stock and starting again myself (nothing against the original rooting and flashing, just like to know exactly what I'm running).
When I purchased the phone I obviously checked that all of the main things worked - calling, texts, mobile data, wi-fi etc. I get home and connect to my home wi-fi and start checking things out and setting stuff up. The phone randomly rebooted. I carry on after the reboot and about 10 mins later, another restart.
To cut a long story short, there is something wrong with the wi-fi. If I turn off wi-fi in the settings menu and reboot, everything works great. No crashes, no reboots. If however I enable the wi-fi about 50% of the time it will crash while wi-fi is activating. The other 50% of the time, it will crash as it goes into the screen lock (either via timeout or pressing the button).
I've re-flashed to it's stock version of Android (using the 'Samsung GS3 Toolkit and Odin), same problem. Anyone got any ideas?
Thanks in advance
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
boomboomer said:
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
Click to expand...
Click to collapse
After much experimentation and flashing of various files to my phone I have further narrowed the problem. I've still not solved it, but getting closer I feel.
After a clean ROM flash it works like a charm regardless of how much i use the wifi etc. It's only after the first reboot that the trouble starts. It will begin randomly restarting. If I perform a factory reset from recovery mode, it works again, but starts resetting again after a reboot.
Any ideas?
Hi all,
I've been happily following the progression of ROM developments, since I got my P7510 (P4WIFI) and sampling a variety of ROM's up through the versions of Android. I recently upgraded to a 4.3 ROM and developed a problem...I could connect to wifi as always, but could not get internet access (wifi connected, but no browsing, play store, weather apps, etc.).
I worked my way back through a number of recovery backups, knowing that in all of them I didn't have this problem, but it remained.
In desperation, I unrooted and returned to stock and the problem was still there! I found a .pit file for the 7510, re-partitioned, formatted the partitions and reloaded the stock ROM...still no change.
Can anyone point me to a solution? I've googled myself stoopid on this one...
Cheers,
PF.
phantomfisho said:
Hi all,
I've been happily following the progression of ROM developments, since I got my P7510 (P4WIFI) and sampling a variety of ROM's up through the versions of Android. I recently upgraded to a 4.3 ROM and developed a problem...I could connect to wifi as always, but could not get internet access (wifi connected, but no browsing, play store, weather apps, etc.).
I worked my way back through a number of recovery backups, knowing that in all of them I didn't have this problem, but it remained.
In desperation, I unrooted and returned to stock and the problem was still there! I found a .pit file for the 7510, re-partitioned, formatted the partitions and reloaded the stock ROM...still no change.
Can anyone point me to a solution? I've googled myself stoopid on this one...
Cheers,
PF.
Click to expand...
Click to collapse
Try to toggle airplane mode on then off..not sure if it will work on our tabs...but it works on my epic 4g touch..this is just a work around though.
What stock did you return to...
I'll look around and see what I can find...
My first thought was it's a router issue. I've had the same thing happen to me and in the end all that was needed was a router reboot.
Gil81 said:
Try to toggle airplane mode on then off..not sure if it will work on our tabs...but it works on my epic 4g touch..this is just a work around though.
What stock did you return to...
I'll look around and see what I can find...
Click to expand...
Click to collapse
Thanks for the suggestion. I tried the airplane mode on/off, but it didn't help.
The stock version I'm on is Build number IMM76D.XWMPF (P7510XWMPF_P7510XSAMP1_HOME.tar.md5)... I believe the correct one for my country...? Not sure if that's a red herring, though. The problem occurred going from 4.2 to 4.3 and has stuck with every restore and rebuild I've tried since.
Benzoman said:
My first thought was it's a router issue. I've had the same thing happen to me and in the end all that was needed was a router reboot.
Click to expand...
Click to collapse
Thanks B-man.
Tried the router reboot, no dice. Also tried connecting to different WAPs and the problem remains. I tried connecting to my SGS4 as a portable hotspot, which was working fine previously...identical problem...
Hello, I used the search to try and find the answer to my question however i couldn't find a thread that seemed to cover this, sorry if this has been asked before.
I have a stock htc desire 610 running android 4.4.2 and i have been on xfinitywifi (public wifi) for a little while and it has worked fine. Yesterday my phone suddenly wont connect anymore and just cycles saying it's disabled and then when i try to connect it says saved then cycles back to disabled. I am not sure why this is happening and i have antivirus on my phone. Any help possible would be greatly appreciated.
Mystic-Entity said:
Hello, I used the search to try and find the answer to my question however i couldn't find a thread that seemed to cover this, sorry if this has been asked before.
I have a stock htc desire 610 running android 4.4.2 and i have been on xfinitywifi (public wifi) for a little while and it has worked fine. Yesterday my phone suddenly wont connect anymore and just cycles saying it's disabled and then when i try to connect it says saved then cycles back to disabled. I am not sure why this is happening and i have antivirus on my phone. Any help possible would be greatly appreciated.
Click to expand...
Click to collapse
Are you using JMZ kernel? It sounds like you're describing a pretty common issue that seemed to happen when people were using JMZ with certain firmware. Happened to me actually and I don't recall a specific fix. Sometimes rebooting wouldn't work. You might try rebooting to recovery and wiping dalvik and cache. But I'd try installing newer firmware with the stock kernel.