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!
Related
Hello all,
Does anyone else ever experience any complete lock ups while WiFi is active?
Just about anytime I have WiFi on my unit will lock up at some point in time. This generally happens while in PIE.
I am not overclocking and I have the 2.25 ROM.
Thanks
David
I been having the same problems also. I am not sure but I think its due to the fact that I start up wifi and have my exchange server push mail on at the same time.
I experience the exact same issue. Random lockups when wifi is enabled. Sucks.
Same here. I'm on my second one that has that problem. I guess it's good to know it's not a unique problem. I can pretty much make mine freeze on cue by opening up Internet Exploder (or anything that uses WiFi, like Agile Messenger) then making a phone call. It's annoying, and I hope future ROM updates address it.
Hello!
I know their is an issue/bug with Wifi connection,but i couldn't find some solution.
Do you guys know?
Otherwise the phone it self is amazing,i realy like the software i think that it's the future for mobiles as long as everthing is working properly
Thx!
Hey, so My wifi and bluetooth hasn't worked (so glad for the 6 gigs for 10 bucks a month fee) but anyways. I'm just wondering does this problem come with rooting \unlocking the bootloader or is this just a hardware problem from this or do people who have stock and never unlocked have this problem?
Atrixn00b said:
Hey, so My wifi and bluetooth hasn't worked (so glad for the 6 gigs for 10 bucks a month fee) but anyways. I'm just wondering does this problem come with rooting \unlocking the bootloader or is this just a hardware problem from this or do people who have stock and never unlocked have this problem?
Click to expand...
Click to collapse
I'd like to say how odd it is that this problem has suddenly flooded the forums.
I'm currently experiencing this problem and I am struggling to find a way to fix it....
yeah, when i try to turn my wifi on in catlog it says cannot failed to load wifi driver. I have flashed pds fix before, maybe that had something to do with it? Part of my touch screen doesn't work and my wifi doesn't work either. are these hardware problems or software problems?
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.
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?