Hi there,
Just wanted your point of view regarding something really strange that happened to me yesterday.
(btw, I looked it up all over the forum + google but still unabale to find a proper answer)
So basically, I droped down my phone, which crashed on the floor but nothing really serious. Ever since, every time I try and turn on the wifi, it says "Error".
I've tried rebooting it several times and still get the issue.
Do you guys think the wifi chip could have been broken? Is there any report log I could find using terminal or root explorer?
Phone specs:
Virtuous Unity v1.29.0
Android 2.3.3
Phone rooted
Bluetooth does turn on
Thanks in advance for your help
Try flashing a different rom, back up your current one first, and check out if the wifi is working without restoring any apps.
Did you ever fix this? I did the exact same thing, dropped onto hard tile. Wifi error and couldn't read data partition.
Randomly after a day or 2 it fixed itself and was fine for 2 weeks.
BUT...just happened again today. I wiped caches, reflashed ARHD, fixed all permissions. Data partition became readable again (not sure which of those fixed that) but i still get "Wifi Error" when turning wifi on.
Any help/suggestions much appreciated.
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Re-Install your Rom, first.
Update your Radios.
Simple.
alexdz said:
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Click to expand...
Click to collapse
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
vdude8 said:
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
Click to expand...
Click to collapse
I failed to mention initially, but I did try updating the radios as well. Regardless, I'm not having the problem anymore, and it's possible that there was simply something in my Titanium backups (done while on ICS) that it didn't like. I started thinking back on the timing and realized that the issue was showing up only after I went through the batch restore process, so this time I only restored a few apps that had data I didn't want to lose, and nothing else. So far so good.
Except of course that I'm now having a new problem that may be associated with a2sd, but I'll post that in that Deck's Reloaded thread...
Thanks!
I had a lot of force closes after restoring ICS backups in GB. Don't think the backups are backwards compatable...not all the time anyway.
Hello,
I tried a 4.2 rom a few days ago (Paranoid Android 3.0) and I couldn't get the wifi to work. When I accessed the wifi, it would only say "Turning Wifi on..." and never turn on.
So I tried another Rom, CM 10.1 nightly. Same problem.
Tried Kang, same problem.
Tried the OTA (rooted, deoxed, etc.) (http://forum.xda-developers.com/showthread.php?t=1737849). Same problem.
P.S. : Before flashing I always wiped data, cache and dalvik.
Am I missing something? Do I need a radio update with 4.2?
Tried again with the latest baseband, XXLJ1, and Paranoid Android 3.
Same thing. I get the message Wifi turning on and it never turns on.
And the phone freezes for 3 secs every 20-30 secs or so. Really annoying...
I've tried 3 different roms, my wifi will connect for a while but eventually will disconnect then loop through connecting 3 times before giving up. After that happens, only a reboot fixes it.
So yeah, I think wifi is glitchy on this device on 4.2 for now. On the plus side, we're all only a few months away from Galaxy S4s.
So I wanted to flash the new jedi rom on my note2. I was running myrom. Through recovery I wiped the system and then I wiped cached. The usual. I have flashed many roms so I knew what I was doing.
So then I flashed the new jedi rom. And its wasnt working because this kept popping up without even letting me use the phone-> 'android.process.acore has stopped unexpectedly'. And then I was like wth? I flashed back and recovered my previous rom and data and that rom worked just fine again.
So I did some reserch and I came across another forum that claims the fix is to flash SUPERWIPE. So I did so, then I flashed the jedirom again and it was working fine without any popups of any errors.
Then I noticed my wifi would not even turn on at all. I press the botton to turn on, and it says turning on, then it will go back to saying turn on, as if I never tried to turn it on at all. Please help guys as much as u can. Everything else works jist fine on my phone btw.
Tmobile sght889 gnote2
I was connected to my wifi, left my phone alone for a few hours, and when I came back (yesterday), i saw the wifi not connected. I go to try and reconnect it, and it says wifi turning on, and nothing else happens, it is stuck there. I can not get it to connect to my wifi. Any idea what could cause this? what can I do?
Gsm galaxy nexus, paranoid android 3.99 android 4.3.
mobile data, calls, text, etc all work great, only problem is wifi seems to be stuck. I tried rebooting, but still nothing.
Any ideas, and thanks for your help.
Been reading other threads. Going to make a nandroid backup and factory reset this baby see if that works. I will let you know. If not I will try another room or go back to stock. If anyone has any other ideas highly appreciated.
Sent from my Galaxy Nexus using Tapatalk 4
malystxy said:
Been reading other threads. Going to make a nandroid backup and factory reset this baby see if that works. I will let you know. If not I will try another room or go back to stock. If anyone has any other ideas highly appreciated.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Factory reset, nothing, restore previous nandroid from 6 months ago, noothing. Still stuck at turning on wifi, but nothing more than that happens. Would screen shots help I can post them. Last resort going to go back to pure stock see if that fixes it.
If not I am guessing hardware problem? anyone have somthing similiar happen, and what did you get to work if anything to fix it? or is my wifi module fried? Thanks any who have input.
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
malystxy said:
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
Click to expand...
Click to collapse
Could indeed be your wifi antenna. Had a similar experience with a T-Mo MyTouch3G a while back. Same symptoms.
Are you clearing all caches, factory resetting, and wiping the system partition from recovery?
Last case, you should restore to absolutely stock, relocking your bootloader and everything.
iLeopard said:
Could indeed be your wifi antenna. Had a similar experience with a T-Mo MyTouch3G a while back. Same symptoms.
Are you clearing all caches, factory resetting, and wiping the system partition from recovery?
Last case, you should restore to absolutely stock, relocking your bootloader and everything.
Click to expand...
Click to collapse
Awesome, thanks for responding, was beginning to wonder if anyone was reading it
What I tried so far (each time wiping dalvic cache, cache, and doing full factory reset from both within android and cwm):
Factory reset on paranoid android 3.99 android 4.3 = nothing
Install cyanogemod 4.3 = nothing
Restore my nandroid backup of bixie deodexed stock rom (which i used before going to paranoid) = nothing
try other version of android from 4.1, 4.2, etc. on varion roms = nothing
restore to google stock (as far stock as possible minus locking bootloader, means yes, stock recovery and everything), 4.1, 4.2, 4.3 = nothing.
ran out of ideas, learned alot though, and got more flashing experience than I care. Did learn how to adb backup, more about android backups, etc though. Some good has come out of it, but my original problem of wifi was and is still not resolved.
Unless there are other ideas, I am pretty convinced the wifi antenna/module died (and a google search confirms others have had something similiar happen, they had to replace the pcb to fix it, which is costly where i live, Argentina). So may just use it sans wifi until I get a new phone, thing has a couple years anyway and nexus 5 is about to be announced.
But I am open to any and all suggestions least I still have hpsda+ speeds 70% of the time.
malystxy said:
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
Click to expand...
Click to collapse
initialize, discoverPeers, connect : working
file trasnfer : not working
i guess, wlan driver of kernel space is missing. ex) nl80211.c & wl_cfg80211.c
my phone is android 4.1, 4.2 in AOSP.
i nothing solves it, too :crying:
somebody Help~~
This thread is over a year old, but I'm having the same problems lately. The device was reluctant to auto-connect to known wifi networks, which I attributed to the current and latest CM11 snapshot. Then, a few weeks ago, the phone became unstable, with random reboots 3 or 4 times a day. Clearing cache and Dalvik cache didn't help. I didn't want to do a full-wipe, with CM 12 on the horizon. About 2 days ago all wifi reception stopped. I could activate wifi in the software, but the device wouldn't receive any signal at all (checked with Wifi Analyzer). So I was afraid that the wifi died out permanently. This morning, in a last attempt I switched off the phone and took out the battery for a couple of minutes. On restart I was surprised to see that wifi found a known network and received an ip-address. However, an internet connection never established and the menu reported a bad reception. I then de-activated and re-activated wifi, but that didn't bring me any further. I guess I'll wait for the first CM12 nigthlies to find out if miracles still exist.