I have just upgraded my S2 T713 to LineageOS 16 gts28vewifi, with OpenGapps pico (also tried MindTheGapps), and addsu also. Mainly because the Wifi has been a bit unreliable on version 15. Often needing a reboot to get connected again.
Things are worse! I cannot connect to WiFi at all now!
I have read all I can about this, I have tried switching Airplane Mode on and off, rebooting etc.
Any ideas or is this a hardware failure?
Replying to myself, Third time lucky!!
Installed for the Third Time, and the WiFi woke up. Hooray!!
Related
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. I successfully rooted my device and installed Team Canjica's CM10.2 ROM (4.3) from the thread on XDA Developers but the WiFi wasn't working. I then installed Maclaw's CM11 ROM (KitKat) because I thought that might solve the issue but it didn't. Here are the details:
Device scans for nearby wireless routers.
I type in the password for my home router.
Device saves router. "Saved, Secured" message displayed.
I tap on my home router in the list to connect.
Device says "Connecting" for a couple of seconds and then goes back to saying "Saved, Secured".
I browsed through the forums and some users suggested switching WiFi Frequency to Auto and turning off WiFi Optimisation but neither of those methods worked for me. The ROM was installed successfully and all other features are working properly so I don't think that is the issue. And my router settings are also alright since I am able to connect to it from my Nexus 7 (2013) properly. Can someone please provide me with a working solution for this issue? I will start receiving very high data usage bills soon because my data plan isn't unlimited. Thank you!
Is your ssid hidden (not broadcasted) by any chance? i had those troubles on hidden home network. Sometimes it worked after a while, sometimes it didn't. What helped me is to broadcast ssid for a moment, get connected with phone, remove broadcast (it will reboot router so phone will lose wifi for a moment). Then somehow it got connected normally
Sent from my SGS Adv. using xda-developers app.
idedItp from
I just checked my router settings and SSID Broadcast is enabled. I tried flashing OmniRom 4.3 thinking that this may be because of a problem with CyanogenMod but the problem still persists. Is there any additional kernel that I was supposed to install perhaps?
CyanogenMod 11 version ?
jeremymichaeldlima said:
I just checked my router settings and SSID Broadcast is enabled. I tried flashing OmniRom 4.3 thinking that this may be because of a problem with CyanogenMod but the problem still persists. Is there any additional kernel that I was supposed to install perhaps?
Click to expand...
Click to collapse
Which version CyanogenMod 11 are you using?
jeremymichaeldlima said:
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. !
Click to expand...
Click to collapse
Just a detail to those who have not upgraded to JB stock and think it is impossible to use it without problems:
All bugs and freezes in Stock JB currently are perfectly finished.
I use STOCK, only with modified kernel (cocore 8.2) without freezes or bugs in months of use.
Enjoy the developer's work (cocafe), because without it JB probably would be impossible in SGA. However we have JB 100% functional and bug-free.
About KK and WIFI bugs:
The only KK (or based) ROM that used without WIFI bugs was RR 20140313.
In fact, the only issue is incall vol. in my experience.
WiFi Direct, Camera -> Panorama is laggy , Screen Recorder not working Not Tested
I also noticed that the battery is worse durability.
But I went back to JB Stock -- personal preference.
ADR USR said:
Just a detail to those who have not upgraded to JB stock and think it is impossible to use it without problems:
All bugs and freezes in Stock JB currently are perfectly finished.
I use STOCK, only with modified kernel (cocore 8.2) without freezes or bugs in months of use.
Enjoy the developer's work (cocafe), because without it JB probably would be impossible in SGA. However we have JB 100% functional and bug-free.
About KK and WIFI bugs:
The only KK (or based) ROM that used without WIFI bugs was RR 20140313.
In fact, the only issue is incall vol. in my experience.
WiFi Direct, Camera -> Panorama is laggy , Screen Recorder not working Not Tested
I also noticed that the battery is worse durability.
But I went back to JB Stock -- personal preference.
Click to expand...
Click to collapse
Actually I did try that method. Flashed Samsung's latest stock firmware I9070XXLQL (ITV) and then rooted and installed CoCore. To be honest overall performance was much better and UI smoothness was improved. But after a couple of days of regular usage with just a few basic applications such as a note taker, train arrival time, WhatsApp etc. the device started freezing up a couple of times a day again. I admit it worked much better than before but freezes and hangs were still quite frequent. Running OmniROM 4.3 now with no issues so far except for dialer FC, laggy panorama and non functional WiFi hotspot.
jeremymichaeldlima said:
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. I successfully rooted my device and installed Team Canjica's CM10.2 ROM (4.3) from the thread on XDA Developers but the WiFi wasn't working. I then installed Maclaw's CM11 ROM (KitKat) because I thought that might solve the issue but it didn't. Here are the details:
Device scans for nearby wireless routers.
I type in the password for my home router.
Device saves router. "Saved, Secured" message displayed.
I tap on my home router in the list to connect.
Device says "Connecting" for a couple of seconds and then goes back to saying "Saved, Secured".
I browsed through the forums and some users suggested switching WiFi Frequency to Auto and turning off WiFi Optimisation but neither of those methods worked for me. The ROM was installed successfully and all other features are working properly so I don't think that is the issue. And my router settings are also alright since I am able to connect to it from my Nexus 7 (2013) properly. Can someone please provide me with a working solution for this issue? I will start receiving very high data usage bills soon because my data plan isn't unlimited. Thank you!
Click to expand...
Click to collapse
This means probably you have typed wrong password. Also check that in keyboard it capitalise first letter automatically. forget the network and connect again
WIFI not working with cm-11-20140521-UNOFFICIAL-janice and cm11.0_janice.nova.201406
Same wifi problem with cm-11-20140521-UNOFFICIAL-janice and cm11.0_janice.nova.20140601. Wifi not connecting even after giving the right password (used to work correctly with jb4.1.2 and still works with desktop) only showing saving and connecting wifi. Then the wifi connection is shown to be saved. If wifi does not work with cyanogenmod11, then what's the use of upgrading?
Is wifi is not working in any custom kitkat Rom?
Please suggest a solution.
Try couple times to connect. I remember sometimes I had to reconnect 2-3 times before it gets connection. And the problem with kernel was about WIFI not turning on at all, it was not even search SSIDs.
I've been lurking for a while and attempting to solve this problem on my own but I've run up against a brick wall and I need some help.
A bit ago, I was running an older stable CM10 build with no real issues. Then, suddenly, one day, the wi-fi stopped connecting. It sees everything broadcast and saves the network, but any time I tried to connect it would, essentially, time out. It would try for a few seconds, then go back to saying "saved". I tried a few different things to test the connection, rebooting the tablet, rebooting the router, removing all security from the router, installing a new router, and trying a public wi-fi. The results were all the same: the tablet can see all the broadcasts but not connect to any.
So, I wiped CM10 totally from the device and installed CM10.1. When I tried setting it up, the exact same thing happened. It can detect all the wi-fi broadcasts but cannot connect to any of them (and as a side note, any time it tried to connect, the wi-fi bars would drop out from full to one bar).
All in all I tried installs of CM9 (that I had used successfully before), CM10, CM10.1, CM10.2 and Evervolv 4.3.1, each from wiped touchpads. EVERY one of them had the exact same problem. The wi-fi when in WebOS works great, so I'm not thinking it's a hardware failure. There's just something odd going on with android installs and my touchpad and I need help.
If anybody has any ideas, I'm all ears. Thanks!
Hello,
A few months ago I noticed I had trouble to switching WiFi/Bluetooth on on my xperia z3+ (lineage OS 14.1) : when I slide on the WiFi slider, it load "Turning WiFi on..." until it switch back to off by itself. I don't think it's because of software update because I actually stayed on the same firmware for a while where it initially worked then started having this issue. Updating didn't solve it.
What I tried :
-Google the issue, I saw other xperia users having the same problem on different models but I didn't manage to find a fix
-Safe mode
-Wipe everything and reinstalling fresh rom
-Tapping the WiFi button furiously for a while
I'm having internet problems at home, but I can't manage to share LTE to my computer successfully, and I suspect both issues to be linked.
I tought I should ask for help before officially declaring the phone physically dead, so here I am.
Thanks for reading, any answer is much appreciated. Sorry for the long post despite it just saying "WiFi bug plz help".
Even with the latest update as of May 2022, my new Tab A8 exhibits Wi-Fi stability issues not seen on the old Tab A7.
After leaving a connected tablet to sleep, Wi-Fi for some apps won't work and only a WiFi OFF + WiFi ON reset will restore connectivity.
Anyone else encountered this problem?
Same - it just won't stay on any network for long at all. It won't connect at all to my VirginMedia router saying 'couldn't get ip number'
Doesn't happen to me from what I've seen... Have Xfinity cable internet together with a Netgear router/modem.
Have you guys done all the system updates?
Yup, up to the latest from April. Tested on 2 devices and it's the same. Factory reset doesn't help.
I'm hoping that if not before, at least the Android 12 update will resolve this.
I just updated to Android 11 firmware update from last week - X200XXU1AVG1 - but the issue remains the same
On Build number RP1A.200720.012.X200XXU1AVC1, no updates I'm aware of. When this happens to me and I toggle wifi off and back on, no networks display. If I toggle airplane mode it they will appear again.
II'm in the USA, using an asus blue cave router.
What's everyone else using?
Anyone know what wifi chipset this tablet uses?
Got the update to Build number RP1A.200720.012.X200XXU1AVG1 it still occurs, and I'm also noticing bluetooth connection issues, both are cured by cycling airplane mode on and off.
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
KoMarCek said:
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
Click to expand...
Click to collapse
I reported the issue via Samsung members app with a bunch of screenshots,
SM-X205 is now getting Android 12 but nothing available yet for SM-X200. Will probably take a couple more days
OK now SM-X200 also got the first Android 12 update and the results are... BAD! Still the same issue and I'm quite done with Samsung for now. Unbelievable that they do not test the basic functionality well enough. I expected some WiFi driver updates under the hood but it seems they are oblivious to the fact Tab A8 has issues.
Had the issue one time since the 15th it's not solved but less frequent at least
What I notice now is that the wifi will turn off randomly. If turned back on it reconnects but shortly thereafter bluetooth dies and cycling airplane mode is required
I just came across a problem after flashing the latest PixelOS update, everytime I normally connect to my 5G wifi, it'll disconnect itself sometimes, this wasn't the first time I got that issue, I got it when I was using EvoX months ago, so is there a way to fix it?