I'm running on the most recent version of Kitkat (no 5.0 for my device yet) and I've got a weird issue where I can't connect to my office's WPA2-Enterprise network, every time it comes up saying "Saved, secured" but doesn't even try to connect. Works just fine on an unofficial CM12 (Lollipop )build. Interestingly I had the same problem with my old OnePlus One on KK but that was fine too on CM12 so the issue seems to be with Kitkat.
I've tried googling it for hours but I'm not finding anything relevant to my issue. Seems weird that I've experienced it on two devices but nobody else seems to have it! Is it a common issue? Anything I can try to fix it?
Bump. Surely someone else has experienced this?
Related
Could someone please explain to me what the WiFi problem is supposed to be with the VegaComb? With mine, I can't actually connect to my home WiFi unless I'm literally 2m from the modem (which is ridiculous). It worked before from further away, and my phone's WiFi still connects so it must be to do with the VegaComb, but I haven't seen anyone else experience a problem this big. Does anyone have any advice on what to do? All else failing, I'll just wait for a patch/update but it better sort this problem out! Worried it might not because no one else seems to be having it.
Thanks all!
My i9505 has been misbehaving when trying to connect to 5GHz wifi since the 12th of October, when I flashed the then-newest official Cyanogenmod 10.2 nightly; before that it had been working with any problem on those same nightlies. Something must have been introduced between then and the 2nd of October; I didn't do any flashing during that time as I was abroad on business, so I'm not sure exactly when the change might have been introduced. Since that time I've moved to a 4.4 ROM but the problem persists.
It seems that I'm not the only one having problems with 5GHz wifi on AOSP ROMs - Google turns up various problems on different ROMs and devices. There are even suggested solutions such as editing text files in /system/etc/wifi or changing one's router's channel. None of these work for me.
The symptoms vary. Some of the time the device will simply refuse to connect to 5GHz networks. Other times it will connect and work normally for a time, anything from approx. 1 minute to 30 minutes or more (the latter making me think for a while that the problem is fixed). But, eventually, apps will stop getting a network connection and I'll be unable to ping anything. Despite this total lack of connectivity the wifi indicator will show that the device is still connected to Google's servers. Turning wifi off and on will start the cycle again, until I give up and switch back to 2.4 GHz.
This is rather frustrating and I wonder if anyone has any clue what it might be, or how it might be investigated further.
Has anyone else experienced this problem?
knirirr said:
Has anyone else experienced this problem?
Click to expand...
Click to collapse
Yes, i have similar problem. i changed few custom roms, and nothing helps. First, it works normal, for few minutes, then wi fi go automaticly off, and then i cannot connect to wi fi network
I noticed this on 4.3 all versions, but since I updated to 4.4 official on my i9505G, the problem went away. I think it may be s bug in the NON-HLOS in the 4.3 roms .. official or otherwise.
Sent from my GT-I9505G using Tapatalk
toastido said:
I noticed this on 4.3 all versions, but since I updated to 4.4 official on my i9505G, the problem went away. I think it may be s bug in the NON-HLOS in the 4.3 roms .. official or otherwise.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
I think it came in on 4.3, and I wonder why it is still affecting me on 4.4 as some people are reporting that has been fixed.
When official jfltexx CM11 nightlies come out I'll try a clean flash to see if there's any change.
I decided to try something similar - I updated to the latest UK firmware and then did a clean flash of an unofficial CM11 4.4.1. 5GHz Wi-Fi still doesn't work properly, as above.
I can get better results within a couple of metres of the AP.
Just wanted to share my personal experience in hope it will help someone else out there as well.
Problems with wi-fi appeared on my rooted N9005 out of the blue.
"Your wi-fi connection is unstable" message followed by complete halt of wi-fi. I read the forums, tried this and that, different firmwares - nothing. Annoying as it was, I gave up on the matter as it was impossible for me to solve at the time. The only band-aid was resetting my router and restarting my Note 3. Then it would work only for a limited time, until when it just wouldn't work anymore.
As a desperate move I tried disabling my AdBlock Plus app. And then a truly wtf moment - everything started working flawlessly. My wi-fi connection is rock solid. :silly:
Well, it didn't seem obvious to me, but then again I AM a newbie. Perhaps you android veterans already had this app on your radar. But listing through forums I never once encountered this as a possible fix, hence I'm sharing this here.
Hopefully it will do the trick for some of you.
Best of luck.
Hi,
I've had this Nexus 7 2012 for ages now, almost since it came out. It wasn't till Android 5.x I think that I started having some minor wifi issues. It has only gotten worse since then. I've since tried upgrading it to 6.0, and back to 5.1.1, and now 4.4.4 again, and still wifi has trouble staying active, and even if it is active, its like dns is failing or somehow data packets are just failing to get where they need to go. On my attempt to downgrade to 4.4.4, it won't get past the wizard as it can't load the login page.
Has anyone had similar issues to this? Or at least heard of it and know how to fix it?
I basically use it as a harmony remote these days as its a bit slow for much else.
I received my Nexus6P couple of days ago and let it install the latest Marshmallow update that was available through OTA at that time (MTC20L). Now since the OTAs are officially available for the Nexus6p (https://developers.google.com/android/nexus/ota) I sideloaded the Nougat NRD90U build. Since then connection to WIfi is practically not possible. Also survey just sometimes doesnt even show the wifi spots. It SOMETIMES automatically connects.
I tryed:
* tested at several locations with several Routers (2.4Ghz +5 Ghz) all of which worked without a problem on Marshmallow and my old Nexus5
* factory reset
* deleting all saved wlans
* manually forgetting the network
* pretty much tryed every naive debbuing found on sites like this: http://forums.androidcentral.com/am...roubleshooting-wi-fi-connection-problems.html
* same bug with the previous nougat build (that wasnt official, I think NRD90R or NRD90S cant remember)
The strange thing is that I cant really find reports for nougat and Wifi problems on the net. So the question, does anybody else has these issues and by chance a fix?
Something went wrong when you have make the sideload
I made an update from dp5 and have no issues like this.
What don't you try to flash everything one by one to see what happen? Radio, system etc.
Envoyé de mon Nexus 6P en utilisant Tapatalk
for3st said:
The strange thing is that I cant really find reports for nougat and Wifi problems on the net. So the question, does anybody else has these issues and by chance a fix?
Click to expand...
Click to collapse
You must have very poor searching skills. A simple search for 'nougat wifi problem' (without ' ' ) will get you several results.
However, no real solution so far, but Google is aware and a case issue (221056) has been opened on code.google.com/p/android/issues. Unfortunately, it's been more than 2 weeks and Google hasn't come up with a a solution.
I'm experiencing the same problem with my Nexus 5X after an OTA update to Nougat. Resetting network settings seems to solve the problem, that is, until I manually start adding/saving wireless networks. When I hit 12, I loose all visible networks and WiFi keeps scanning (and draining battery) for networks if I turn WiFi off and on. If I let is scan for an hour or so, a connection is established, but when I turn WiFi off and on again the problem starts over.
Some people think it has something to do with 2.4GHz and 5GHz networks, because they can't access 5GHz. Google has advised resetting to factory settings, but that doesn't seem to solve the problem for everyone.