Related
Hello everyone,
I found the solution on another forum (GalaxyTDM's post) and I wanted to share it over here because it's a PITA.
Symptoms:
1. None of the wifi toggle buttons work to turn on wifi.
2. When examining the wifi settings, the status will show either "Error" or "Turning on..."
3. If it sits on "Turning on..." for any longer that 2 minutes, it will probably stay in that state.
4. If it changes to status of "Error," it may work after several times attempting to turn it back on from the settings screen.
Apparent cause:
1. Memory is low on the device. Examining the RAM Manager, one can see less than about 45MB free of memory. This apparently is preventing the wifi from starting. Either that, or there is some other program or setting that has crept in and needs to be killed.
I found this to be the case on my device, memory was hovering at about 40MB free and wifi was sitting on status "Turning on..."
Solution:
1. Go into the RAM Manager and do a level 1 clear of the memory. If that doesn't do it, do a level 2 clear.
After I did a level 2 clear, about 80MB of memory was freed and wifi immediately connected and I saw the icon on the status bar.
Hope this helps.
Android 2.2.1
Galaxy S
Best,
Christopher
Thanks Dude...
had same problem in my xperia x10 mini pro... running custom cm7 v16... nw okie..
Same issue, but i have 370mb of internal mem avail.
(Sprint Htc Evo) I have tried the revolutionary meth. followed steps, manually flashed, due to boot loader stating that S-On, i have superuser app, retried with same problems, but anyways that's another problem I am working on solving.
I have had the WiFi Error problem since I first tried to root a few days ago, I am going to attempt to download and install ram manager via usb. But like i stated i have 370 mb of internal memory available. Any other ideas or solutions?
Not Working
Non of it working . Everytime i need to restart my phone if i want to turn on the wifi back.
had a similar issue....always wondered what the problem was
Yes!
I have a Galaxy S (T-Mobile Vibrant) running 2.2 and it worked for me. Memory was at 45 MB. I cleaned up about 20 MB and tried again. It worked. Thanks!
I solved my wi-fi error problem by flashing EZGINGERBREAD ROM.
Old G1 dream
EASY !
Same problem GS2
dirtyrob said:
(Sprint Htc Evo) I have tried the revolutionary meth. followed steps, manually flashed, due to boot loader stating that S-On, i have superuser app, retried with same problems, but anyways that's another problem I am working on solving.
I have had the WiFi Error problem since I first tried to root a few days ago, I am going to attempt to download and install ram manager via usb. But like i stated i have 370 mb of internal memory available. Any other ideas or solutions?
Click to expand...
Click to collapse
Same issue, 700mb free on Galaxy S2. Have tried multiple ROM's incl. CM7 [2.3?],Slim [4.0.4],MIUI [4.0.3], all with the same problem. WIFI continuously says "Turning on....".
The only other 'USEFUL' piece of info I've found on this is a changing a mac address on a blade phone thread saying "data/misc/wifi folder you have a file called athSavedEeprom.bin" I have no such folder or file which may be a problem.
tks
thanks. useful info.
Hi guys.
Ik don't own a SII, so IDK if this works for you also.
Open your dialer and type *#*#526#*#*
Your phone will go into Engineering Mode and reload the driver.
Apologies if this is old news, but it does the trick for me !
coby kyros mid 7010 wiFi network connection problem
Dear All,
I'm new here. please advice me. i needed your help. i got coby kyros mid 7010, which was gifted to me by my brother. it is working fine. but the only problem is wifi connection. when i try connecting to a working wireless network connection, it keep on tying and then disconnecting. but the same connection is working with my laptop. please help me what to do....
Thanks in advance
I usually click wifi off, wait for a couple of seconds and try again and that solves the problem.
Is there any other way to fix WiFi error issues? I have a Vodafone Smart Tab 7 / ZTE 71A.
It was working fine with CM10 port, but then I tried to flash Paranoid Android Jellybean which failed to boot; so I rolled back to CM10 however it appears WiFi has stopped working.
It gets stuck on "turning on...", and would crash/reboot the tablet sometimes, or just give the "Error" message...
I have tried recovering back to standard and also flashing back to stock ROM however still no luck!
It normally gives that when it can't see the wireless card, first check if blue tooth works, the wireless and bluetooth are normally bundled together.
If it does work thenstart from fresh, wipe everything apart from the sd card and installed a recommended rom, fingers crossed that'll sort out any software issues.
I had this exact problem on my old DHD, the problem was I dropped it and the wifi antennas popped off.
Sent from my HTC One X using xda premium
thnkx
Sent from my GT-I9100G
Thanks Cristobalmiguelo, I had this problem on my old phone. Sometimes after long use of the phone I couldn't connect to wifi and as you wrote, it stayed forever on "Connecting". Restart always helped and in fact, that phone had only 256MB RAM and I always had hust around 30MB free.
also have wifi error
i have the same problem on an att samsung rugby smart since i installed updated kernel and when i go into wlan test it says noset driver loaded and everything fails on the status i wish i could redo my phone to out of box state
thanks For Share :good:
i have the same problem with my samsung s2, it's showing error when access portable wifi hotspot, i have just wipe dalvik cache and wipe cache partition but it doesn't work, any idea please ? :crying:
Kernel Issue?
I believe this can be a kernel issue as well. I just came across this issue after flashing a new kernel. Flashed old kernel. All seems fine.
UPDATE - Problem sorted via philos64 thread at the top...
Should've tried that 1st, but posted here hoping someone would confirm that was the route to take, as it wasn't actually bricked... Never mind, all done..
Why??? Was out earlier so I turned my wi-fi off and my mobile on and everything was working fine..
When I got home, I turned the mobile off and tried to turn wifi back on, but it is hanging on 'Turning wifi On.'
Tried rebooted the tablet a few times and rebooting the router, (BT HomeHub 3), but still the same problem.
This N7 is rooted and running 4.2.2.
When I look at the Advanced Wifi the MAC and IP address are unavailable.
When I go into Wifi Analyzer it says the wifi needs to be turned on and tries but gets same hang and retries...
On the left of the analyzer it shows my Wifi ID with a mac address underneath with a yellow triangle and 'No Signal!' in red.
The wifi from the router is working as my phone is connected via wifi.
Any ideas please people ???
:crying:
going for the post with the most views and zero replies is not on my bucket list... So I'm going to reply to myself..
An Update....
The problem is still there, so I went into bootloader - recovery mode....Then I went into Android system Recovery.
I selected cache then wipe dta/factory reset.. Reboot then starts tablet as new with the unlocked symbol, then goes through the initial setup. Select language, then it does Select wifi and displays 'Turning on wifi'.. Hung...
Would flashing it via Nexus root toolkit sort out then problem... If so, any clues what flash and how...
If it wouldn't fix it... Is the tablet now bricked??
Please answer someone if you know..
Cheers
There have been several posts about wi-fi problems if the outer shell of the N7 is separated and not fully locked in. A loose or separated shell can cause a disconnect in the wi-fi antenna. Check for any separation and maybe squeeze the front and back together all the way around the outer edge.
I did read them and a lot of other threads but they were mainly to do with wi-fi looping and not connecting.... I couldn't find any other post regarding just 'turning it on'.... And seeing as it's sorted with just a flash of the stock rom, I can safely assume this problem had nothing to do with hardware...
Hence why I was surprised I was the only 1 with this 'type' of prob.... (but I didn't read every post so I may have missed one).
Same problem too
filking said:
I did read them and a lot of other threads but they were mainly to do with wi-fi looping and not connecting.... I couldn't find any other post regarding just 'turning it on'.... And seeing as it's sorted with just a flash of the stock rom, I can safely assume this problem had nothing to do with hardware...
Hence why I was surprised I was the only 1 with this 'type' of prob.... (but I didn't read every post so I may have missed one).
Click to expand...
Click to collapse
im experiencing the same thing. im using Samsung galaxy S4 i9505 LTE and on android 4.3/ rooted Baseband i9505XXUEMJ5. it happened when i was trying to erase all the bloatware on my phone using Trulyclean by schoolsux. after i flashed the script i started having this problem.so far ive tried to do a factory reset by using custom recovery, tried to download the modem fix and flashed it through odin and do the advanced settings on wifi and uncheck the auto network switch. The problem that i have is yes it say "connecting" for 2-3 minutes then it gives you a list of possible wifi connections and then you connect. another 2-3 minutes then it wont connect. repeat the steps and now i can connect, then if you turn off the wifi you will have to go through the whole process again. it doesnt save any wifi connections you have connected before. there are 2 other ways i havnt tried yet and that is to flash a different kernel. a custom kernel and reflashing my phone again with the android 4.3 then root:laugh: for the nth time already:fingers-crossed:
hammerthumbs said:
im experiencing the same thing. im using Samsung galaxy S4 i9505 LTE and on android 4.3/ rooted Baseband i9505XXUEMJ5. it happened when i was trying to erase all the bloatware on my phone using Trulyclean by schoolsux. after i flashed the script i started having this problem.so far ive tried to do a factory reset by using custom recovery, tried to download the modem fix and flashed it through odin and do the advanced settings on wifi and uncheck the auto network switch. The problem that i have is yes it say "connecting" for 2-3 minutes then it gives you a list of possible wifi connections and then you connect. another 2-3 minutes then it wont connect. repeat the steps and now i can connect, then if you turn off the wifi you will have to go through the whole process again. it doesnt save any wifi connections you have connected before. there are 2 other ways i havnt tried yet and that is to flash a different kernel. a custom kernel and reflashing my phone again with the android 4.3 then root:laugh: for the nth time already:fingers-crossed:
Click to expand...
Click to collapse
i have same issue with htc one x, my wifi doesn't wan't to turn on. it stuck on "turning on...", i tried to flash different roms, etc, now i think about flashing kernel, did you do that? did it help?
Same problem on N4
Have had the exact same problem not once but twice. One day it works perfectly fine. Next day, it just stops at turning on process.
On my N4 the 4.2 was working fine. Along comes the 4.3 OTA update and the wifi stops working. Does not startup or show the mac addr either.
Did factory reset, wipe cache and even reflash binary from google stock images. No relief.
One day, the wife using gmaps started the gps location service and pop the wifi started,
Now after the 4.4 OTA all seemed to work well till yesterday and pop the wifi breaks down. the earlier trick of gmaps does not seem to work. I think one of the google apps update is breaking this.
After rebooting also, the device seems to remember the wifi state and tries to read the previous history and restore for the startup. And that is killing.
Any idea how to debug this or to wipe the wifi logs or to manually start the wifi/bluetooth radio.. ya athe bluetooth is also stuck.
Thanks guys in advance
Where is the fix?
filking said:
UPDATE - Problem sorted via philos64 thread at the top...
Should've tried that 1st, but posted here hoping someone would confirm that was the route to take, as it wasn't actually bricked... Never mind, all done..
Why??? Was out earlier so I turned my wi-fi off and my mobile on and everything was working fine..
When I got home, I turned the mobile off and tried to turn wifi back on, but it is hanging on 'Turning wifi On.'
Tried rebooted the tablet a few times and rebooting the router, (BT HomeHub 3), but still the same problem.
This N7 is rooted and running 4.2.2.
When I look at the Advanced Wifi the MAC and IP address are unavailable.
When I go into Wifi Analyzer it says the wifi needs to be turned on and tries but gets same hang and retries...
On the left of the analyzer it shows my Wifi ID with a mac address underneath with a yellow triangle and 'No Signal!' in red.
The wifi from the router is working as my phone is connected via wifi.
Any ideas please people ???
:crying:
Click to expand...
Click to collapse
Hi Can you please send a link for the solution? i am still stuck with "wifi turning on" screen and cant seem to bypass it. No matter what Stock image i flash through Wug Toolkit.
i have got the same wifi errorrigictsi vanished
initially i had loaded my explorer with fly rom and everything waas working except the internal memory. i'm not even able to download at least an app and then i tried bulletsense rom for increasing the internal memory of my explorer. it's successful, and the memory increased. From there onwards, the problem started. the wifi first said error... but after reboot, it's all the time saying "turning on"..
by typing "ifconfing twlan0" it said no devices found... so i thought it might be some driver error. coueld any one port some other drivers to the below rom so that i can have both internal memory and wifi...
link to bulletsense rom ///d-h.st/xFr//// ( add https before /xxxx/)
here is a screenshot of it...///bit.ly/MMSeam///
any one please help me on this and give me a chance to raise your thanks meter...
sorry that i'm newbie and not allowed to post links.
Hey guys.. I faced similar issue in my AMOI 820 based Indian local device Micromax (rooted + custom kernal)
I fixed this stuck wifi problem by uninstalling Google apps in system by removing them using Titanium back up + and again installing them from playstore if needed.. Hangouts(in my case) if it's a system app after getting updated is the culprit .. Try removing it and reboot and test it yourself..
guess it working now!!
I was going crazy about this stuck wifi issue!!
I tried everything!! I found on the advance panel on the wifi
That the MAC address and the IP address is unavailble.
After many tries i think i fixed it!! Using:
Busybox and MacMan
MacMan changed my MAC address and now the wifi is no longer stuck!!!! Hope it will help you too. Peace
yurashi# said:
I was going crazy about this stuck wifi issue!!
I tried everything!! I found on the advance panel on the wifi
That the MAC address and the IP address is unavailble.
After many tries i think i fixed it!! Using:
Busybox and MacMan
MacMan changed my MAC address and now the wifi is no longer stuck!!!! Hope it will help you too. Peace
Click to expand...
Click to collapse
I have same problem on my nexus 5,
But macman is not working.
Any other solutions
wifi turning on problem
i have a xperia sola mobile ..
wifi is does not work ..please help
when touch the wifi option then it does not turning on ..
Hi, maybe someone has a clue:
I seem to be the only one who can't use cm10 because wifi is just not working. On cm10 it's dropping out all the time as soon as data gets transfrerred (i.e. app download) and on cm10.1 its not even dropping. there is no data throughput whatsoever.
If you need more info, just tell me which one and I'll post it. I'm desperate.
Any ideas?
Assuming you have made a clean install, with system and data wiped as well, you should check your router configuration, try changing channel and/or security parameters
Sent from my MB526 using Tapatalk 2
thanks for the suggestion. I don't have access to all the routers settings but I tried to use one even without security and the drop outs still appeared. Working well on m7.
I just realise: At the beginning of a fresh build it sometimes happens that wifi works for a couple of MB and suddenly starts dropping.
Is the Wi-Fi network used by many persons at a time? More than a couple of devices connected may cause problems because the new Wi-Fi drivers starts jamming devices, and sometimes as a result the Wi-Fi network is unable to deliver data.
Sent from my MB526 using Tapatalk 2
I wouldn't say so. Not to many and it didn't work with the old wifi driver on cm10 either. The wifi keeps working for other parties in the network - so it is not jammed.
I might try again with a new build but I'm pretty hopeless...
Here is a long post about what I tried so far:
http://forum.xda-developers.com/showpost.php?p=38869441&postcount=915
measel said:
Hi I'm sorry to bother again.
I tried to figure out whats wrong with the wifi bug I'm having: constant drop outs while using any kind of wifi traffic.
Good news:
it worked well at home with my fritzbox router. (only tried 3-4 app downloads) > after a short while it stopped working
Bad news:
in my studio we got a different router and there I got the drop outs.
What I tried so far without luck (always a reboot in between):
disable Draft-N in wpa_supplicant
compared wpa_supplicant but it's the same as in cm7
delete rgnt from system/bin
change build.prop to use all 14 channels > ro.wifi.channels=14
tried changing PowerSavePowerLevel = 0 to 1
copied tiwlan.ini from cm7 backup because a few settings are different
tried 12-12-05 Quarx build
tried 12-10-18 build (but got a bootloop and stopped trying)
tried newest 13-03-07 build
ADDED tried 13-04-09 build
tried newest build and did another factory reset AFTER installing the ROM.
searched the web and found that maybe it might have something to do with wpa2, but the router at home uses wpa2/wpa (which means it's wpa2 as well or not?) and NO I cannot change the routers settings and I don't think it is a solution because i can use but not access like a dozen routers.
checked dmesg: in the TIWLAN section after the wifi connection it says: "iface_stat: stat_update() tiwlan0 not found
is it in any way possible that some settings change because I plugged usb "charge only" in while trying to download from Playstore? because it seems that dmesg spits somthing out regarding usb... (I'm can't really read/understand the output though)
oh and btw. first connection was fine in my last try: I could update Gmail, then I connected my usb and drop outs began. but I don't think it's related.
ADDED change to static IP
ADDED change regional code in wifi settings (w/o knowing what that actually does)
ADDED tried factory reset from stock, flash sbf and start from scratch.
Things I didn't try (and don't know if it would make any sense):
replace tiwlan_drv.ko
change vsel
[...]
Click to expand...
Click to collapse
It may be something elementary, but I presume Wi-Fi optimization is configured properly right?(IT MUST BE DISABLED)
I have had this issue but setting channel manually fixed it for me. This issue I had only on jb and with a specific router only. All others work properly on every channel.
Sent from my MB526 using Tapatalk 2
Damn I can't just change all the channels in all the wifi networks I'm allowed to use... but I will try that with my own one.
I did not try to change channels, yet but I tried once more to start from scratch: wipe from stock / flash sbf / install cm10 and so on..
Reason: Someone hinted the stock wipe could help. But here is the problem:
Everytime I try to wipe from stock (before or after flashing sbf) I get the old "E:can't mount cache:recovery/..." ERROR. Something seems to be wrong and I wonder if that could prevent my wifi from working (maybe data is still unwiped...)
Any more ideas?
Stock recovery can't handle ext4, hence the read errors.
Stock recovery wipe will not help if custom recovery data wipe does not help. You can also try manually deleting the Wi-Fi folder in the data partition.
You'll have to try changing channels eventually, I think.
Sent from my MB526 using Tapatalk 2
thats a misunderstanding:
I know that stock recovery can't handle ext4. My working system is cm7 so I stockwiped from cm7 and still couldn't get rid of the errors. I even checked the filesystem with e2fsck but everything seems to be ok. And I can install everything so... I don't know.
If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
And what misunderstanding are you talking about?
Sent from my MB526 using Tapatalk 2
thekguy said:
If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
Click to expand...
Click to collapse
That does sound pretty scary.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Click to expand...
Click to collapse
I can't waste another day on hunting the /cache problem right now because of work, but as soon as I have more time I'll try a little more.
Here is some news from me: I had the chance to try it on another wifi router last night and behold: It worked nearly flawless.. a few hickups I think, but it worked. That means WIFI is not broken, but there must be some software-related problem/ or some network weirdness.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
Click to expand...
Click to collapse
This I will not do!
thekguy said:
And what misunderstanding are you talking about?
Click to expand...
Click to collapse
Just that stock over ext4 thing. Nevermind.
Thank you for helping. I wonder if there is a way to find the problem.
Did you check the channel that particular Wi-Fi router operated at? Same as or different than the problematic routers ? Because if so then we have narrowed the problem down
Sorry for the scary part
Sent from my MB526 using Tapatalk 2
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Joharnis said:
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Click to expand...
Click to collapse
Im having a similar problem, i think we have to flash a different radio ?
Still nothing
Flash a different radio? What excactly does that mean? I must admit I have not heard of that :laugh:
By the way, I just unrooted my device and relocked the bootloader, but that didn´t fix the problem either.
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
sigma392 said:
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
Click to expand...
Click to collapse
I just tried the franco R163 with prima drivers, that did not fix it. But, speaking of the bluetooth, i´ve just noticed that the same problems occurrs with that. I trie to turn it on an it stays at "turning on bluetooth" without actually turning on. Maybe that helps to know what the problem is.
What other kernel with prima drivers would you recommend?
Edit:
I´ve read through a few threads on that bluetooth-issue, which apparently is more common than my wifi issue. I was wondering if my wifi-issue could have something to do with the bluetooth, because other users who have said bluetooth issue found their bluetooth temporarily on after reboot; then after a while the bluethooth issue appeared again.
In my case the bluetooth doesn´t appear to be on, but i was thinking that maybe it is, but the software fails to display that and that that is interfering with my wifi.
Could that be a possibility?
Out of the box my nexus 4 refused to connect to my TPLINK wr941ND router, wifi was set months ago, nexus 7 works as charm same with evo 3d and others. I thought wtf and turned on wifi on broadband modem, it showed up on nexus 4.... And suddenly network from router poped up as well. I switched off wifi on modem and nexus lost wifi from router. At this moment I went for a walk... When I come back done factory reset, reboot the router, no effect. Changed settings from WPA2/QSS to WPA without QSS - no change, then I changed channel from #13 (best in my location, all my neighbours using #1 and #6) to #1 and instantly nexus found network.... So it seems that sumthing is apparently with wifi, when I changed channel back to #13 it drops the connection and says that networtk is out of range. So finally I checked all the channels from 1st to 13th and it works from #1 to #10, 11 till 13 dunt work. Maybe this info will help sumone with simillar problems.
Hi,
Right now I'm having issues with my Moto G4 Play and wifi. The problems is kind of reproducible ... after some days.
ROMs tried:
RR-N-v5.8.3-20170707-harpia-Official.zip
lineage-14.1-20170711-nightly-harpia-signed.zip
Symptoms:
- Wifi Scan doesn't work any more ... just showing SSID from some hours before
- Even not possible to connect to wifi when entering the SSID and security settings manually
- Disabling / Enabling the wifi doesn't help
Solution:
- Right now ... only a reboot fixes the problem
Anybody here facing the same problem?
Regards stefan1384
Had the same issue here as well but I swapped routers a day back and it hasn't happened again so far. Using RR-N-v5.8.3-20170707-harpia-Official.zip.
Probable solutions:
1. Reset your network settings of the modem/router if possible.
2. Flash the modem file from the latest available stock ROM and then clean flash the custom ROM.
3. Give the necessary logs (modem logs and dmesg along with the logcat) when you re produce the issue.
rileysnotz said:
Had the same issue here as well but I swapped routers a day back and it hasn't happened again so far. Using RR-N-v5.8.3-20170707-harpia-Official.zip.
Click to expand...
Click to collapse
While not questioning the fix in your specific case the loss of WiFi scanning capability at the device level has absolutely nothing to do with the local AP (router).
Hello,
thanks for your feedback. With the Wifi APs it's a little bit complicated ... can't force the company where I'm working to replace their equipment ... I'm still not sure if it's caused by my home wifi or wifi at work.
I updated now to the latest lineage build: lineage-14.1-20170718-nightly-harpia-signed.zip maybe it's already solved there otherwise I'll maybe try to install a newer SomeFeak Kernel.
I'll post updates here.
Regards