[Q] SlimKat 4.4.4 and WiFi Reconnect issue - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

First, I've had this issue since Build 6.8. I was hoping a Clean Install using Philz Touch Recovery v6.48.4, which is the latest, and selected Wipe Data and select Clean to install new ROM which Formats /data, /cache, /system. I also wiped Dalvik.
Once completed I did the following:
Clean Install of Slim-d2lte-4.4.4.build.7.0-OFFICIAL-5979
I then installed
Slim_full_gapps.BETA.4.4.4.build.7.x-190
Rebooted and waited for SlimKat to boot-up. WiFi/Data both full scale. Everything Restored just fine and things are running smooth.
Then after running a few errands outside of WiFi Range, I returned home within WiFi range only to find out that WiFi had not reconnected. It tells a WiFi connection is available but will not reconnect to it. So I go into Setting and select WiFi and tried to manually reconnect. It says connecting and then goes back to Saved Connection without connecting. This same thing on other WiFi connections such as McDonald's or other open WiFi Connections.
I then do a re-boot and everything is back to normal. WiFi connects without issue and again things are fine and running smooth.
Every time I leave WiFi range and then return within WiFi range, the problem re-occurs. A Re-Boot and everything back to normal.
One thing I've always noticed when doing a Clean Install as stated above, all of my previously stored WiFi connection are still there. Same on Ringtone/Notification Tones.
With the problem I'm having, could it be something that is not being wiped/cleared out during the Clean Install process. Or wondering if it could be somehow that the WiFi Radio has gotten corrupted.
I have also tried different Kernels but again the result is the same.
Hope this is not too much of a noob question and I have searched about everything I can think of. Wondering if anyone has had this problem or have any ideas of what could cause the problem.
I really hope I can get this figured out. Thanks

If you don't have to manually reconnect and enter your password, then its not being wiped. (Or you are restoring it from a backup.) Have you tested it after the clean flash, but before restoring anything? What are you restoring and how?
It sounds like a Rom issue otherwise and you should probably ask in the rom thread.

DocHoliday77 said:
If you don't have to manually reconnect and enter your password, then its not being wiped. (Or you are restoring it from a backup.) Have you tested it after the clean flash, but before restoring anything? What are you restoring and how?
It sounds like a Rom issue otherwise and you should probably ask in the rom thread.
Click to expand...
Click to collapse
First I don't know what I've missed wiping. When I say restoring, I'm referring to letting Google re-downloading everything from the Play Store.
I know the WiFi radio are in a different location but like you, when I do a Clean Install by formatting /data /cache /system and wiping dalvik, I wasn't expecting all the stored WiFi connections to still be there, but they are.

Its possible its being restored by Google's backup, but I don't use it myself so I'm not certain about that. Its also possible the rom may save the config file elsewhere. Again though, I don't use cm/aosp based roms so I'm not too familiar with any of their specifics.
Next time you try a clean flash, do not sign into google during setup. Instead go straight to testing wifi to see if it still remembers the connections. Do you have it set to auto connect to any open networks? If so you might want to turn that off.
Have you searched or asked in the roms thread yet? It might be a known issue or something a few others have encountered and know how to fix.

DocHoliday77 said:
Its possible its being restored by Google's backup, but I don't use it myself so I'm not certain about that. Its also possible the rom may save the config file elsewhere. Again though, I don't use cm/aosp based roms so I'm not too familiar with any of their specifics.
Next time you try a clean flash, do not sign into google during setup. Instead go straight to testing wifi to see if it still remembers the connections. Do you have it set to auto connect to any open networks? If so you might want to turn that off.
Have you searched or asked in the roms thread yet? It might be a known issue or something a few others have encountered and know how to fix.
Click to expand...
Click to collapse
Ya I don't sign into Google at the initial start up after the flash because my WiFi is no able to connect. I will double check the auto connect feature. But I having this issue with other 4.4.4 ROMs also because I tired however on those ones I am amvle to toggle WiFi on but in advanced it has the region set to Europe and when I switch it to Canada it doesn't want to save the change

Related

Kindle 6.3 Broken Wi-Fi

I recently came from ICS, and having issues with wi-fi there. So I went back to stock, hoping my issues would be resolved. Awesome. They aren't!
Wi-Fi doesn't work. I have/had hashcode's latest kernel flashed. I don't know what to do. Any ideas? D:
Any help is appreciated.
Thank you!
How are you wiping when you flash roms? Maybe you have messed up how your kindle connects to wireless . There has been a Mac address issue with the new kernel maybe yours never reverted when you went back to stock. Have you tried other networks? Have you done a factory restore? Do you mean pure stock not rooted?
Thepooch said:
How are you wiping when you flash roms? Maybe you have messed up how your kindle connects to wireless . There has been a Mac address issue with the new kernel maybe yours never reverted when you went back to stock. Have you tried other networks? Have you done a factory restore? Do you mean pure stock not rooted?
Click to expand...
Click to collapse
I wipe ; Factory Reset, System, Dalvik-Cache, Cache
And basically when I go to TURN-ON Wireless, no networks show. It doesn't even fully turn it on, it gets stuck in the middle of turning on the Wi-fi.
I went back PURE stock, NO ROOT. However, it seems I may have need of getting ROOT back. :/
I'm still curious if you performed a factory restore when you returned it to stock. I suppose your case could be that something burned out the wifi adaptor of the kindle although I bet its rare but not completely unreasonable. After a new clean flash when you reroot we will see those results ?
Probably totally unrelated, but have you ever had the locate-my-kindle software installed? I got similar weird behavior after a while when using that... first wifi networks were slow to come up, then it would struggle to turn on wifi, finally it'd just give an error and crash the settings manager or whatever it's called. I had to get rid of the software. Basically it was storing every single wifi network it ever came in contact with, even for just a second, and having too many entries hosed wifi. Uninstalling it seemed to clear those extra entries and restore functionality.
I do know that restoring your account from Google to your device and letting them keep copies of your wifi passwords can also cause issues although when I was testing roms for some devs on my droidx with known wifi issues ñot allow the Google restore and backup caused similar problems.

[Q] BMB4 Wifi Issue (not wifi calling)

Since upgrading to BMB4 I am having an issue at work where my phone will not switch between access points properly. It appears to be a problem with the phone *disconnecting* from the access point when I no longer have a strong enough signal. If I walk from my desk to another part of the building, it still says I am connected with a strong signal, even though I am not connected at all.
In fact, several times when driving home I have looked down after realizing I haven't received any e-mails in a while to see that my phone still thinks I should be connected to the wifi at my desk.
The only workaround I have found so far is, if I go from my desk to another part of the building, turn wifi off and back on, then do it again when I return to my desk, or anytime I notice that my phone thinks I have a strong wireless signal but I don't.
I tried a full factory reset, but no dice. Had absolutely no problem prior to BMB4.
Anyone else seen anything similar? Any ideas? Anything buried in the service menus that could be wrong? If not, would rooting and reflashing the radio be likely to help (can you give me a link to the right one to try if so)?
Thanks!
The radio wouldn't have anything to do with it. You are probably a victim of just some simple file corruption. It happens, I see this more with OTAs than anything. That "transitioning" from one OS to another while attempting to preserve precious data.
I would recommend you root it, install "TWRP" 2.5.0.0 for your device (which is basically a recovery or "bios" for the device - or basically a kernel), and then install a ROM that has been updated to BMB4... off the top of my head, i would say you should give tweaked 2.0 a try. It's solid (others are as well, but i know for certain that one will give you zero issues similar to the one you are reporting.)
The links for twrp, with instruction on how to install can be found in the "orginal development section" and the tweaked ROM can be found in the plain "development section" of the forum here.
As I said, very likely that your issue can be resolved by starting 100% fresh. New system install (which is not formatted when you wipe data obviously)
So again, root, install twrp recovery, install tweaked 2.0. Follow directions to the T.
Good luck
I was reading and wondering if I actually wrote that question. That is EXACTLY what is happening to me since the update. I never have an issue at home, it is just moving from AP to AP at work and also being 'connected' when I am miles away from the AP. I don't really want to factory reset, so I tried turning off wifi power saving using "*#0011#" and that seems to be working...

WiFi not turning on?

Ok so a couple of days ago I installed a 4.0 ready radio on my galaxy s2 and then went on to install Jedi Knight 6 ROM (4.0.4 and radio is UVMC6) and after installation everything was working fine.. I was messing around for a while.. it worked today, I shut my phone off to charge it up real quick, and when I turned it back on my WiFi would not connect. Well not necessarly connect.. it just wont even turn on. When I go into settings and click WiFi, it just sits there saying, Turning WiFi on, and never changes.. I can't seem to imagine what could have happened to it, and I really dont wanna have to reinstall the ROM again because i just spent hours getting this one all set up to my liking...
Anyone got any ideas?
EDIT: BTW, I have tried many things.. Tried airplane mode to disable everything then turn it back on, obviously tried rebooting the phone, i have tried wiping cache in CWM recovery and also tried fix permissions in recovery (another topic said to try those..)
Nothing has worked so far, i'm about to try reflashing my radio, see if that works.. but I really really dont want to have to reflash my whole ROM.. So if anyone has any other ideas please help, i'll edit if the radio works..
EDIT 2: Reflashing the radio did nothing.. it's really wierd, the data, bt, gps.. all of it works fine, it's just the WiFi that's frozen turning on... cant get it to stop turning on and can't get it to actually turn on..
EDIT Final: Ok well, i guess nobody knows what might have been going on.. so I just wound up reflashing my ROM, which obviously fixed it.. i just had to lose all that time spent setting everything up... But oh well.. Kinda sucks nobody even tried to help..
Gopher love said:
Ok so a couple of days ago I installed a 4.0 ready radio on my galaxy s2 and then went on to install Jedi Knight 6 ROM (4.0.4 and radio is UVMC6) and after installation everything was working fine.. I was messing around for a while.. it worked today, I shut my phone off to charge it up real quick, and when I turned it back on my WiFi would not connect. Well not necessarly connect.. it just wont even turn on. When I go into settings and click WiFi, it just sits there saying, Turning WiFi on, and never changes.. I can't seem to imagine what could have happened to it, and I really dont wanna have to reinstall the ROM again because i just spent hours getting this one all set up to my liking...
Anyone got any ideas?
EDIT: BTW, I have tried many things.. Tried airplane mode to disable everything then turn it back on, obviously tried rebooting the phone, i have tried wiping cache in CWM recovery and also tried fix permissions in recovery (another topic said to try those..)
Nothing has worked so far, i'm about to try reflashing my radio, see if that works.. but I really really dont want to have to reflash my whole ROM.. So if anyone has any other ideas please help, i'll edit if the radio works..
EDIT 2: Reflashing the radio did nothing.. it's really wierd, the data, bt, gps.. all of it works fine, it's just the WiFi that's frozen turning on... cant get it to stop turning on and can't get it to actually turn on..
EDIT Final: Ok well, i guess nobody knows what might have been going on.. so I just wound up reflashing my ROM, which obviously fixed it.. i just had to lose all that time spent setting everything up... But oh well.. Kinda sucks nobody even tried to help..
Click to expand...
Click to collapse
+1 I'm going through the same thing now
I have been having this same issue as well. It started out as stock happening sporadically. One thread suggested rooting and removing my account. Problem still occurring. Tried flashing multiple ROMs and now WiFi hasn't connected at all always stuck at turning on. I have tried clear cache, fix permissions, as well as reinstalling ROM dirty and with factory reset. I'm hoping this isn't hardware failure because I just bought this phone used but it seems to be a reoccurring problem with others as well. Any NEW suggestions not given from quick Google/xda search?
stoneduser8907 said:
I have been having this same issue as well. It started out as stock happening sporadically. One thread suggested rooting and removing my account. Problem still occurring. Tried flashing multiple ROMs and now WiFi hasn't connected at all always stuck at turning on. I have tried clear cache, fix permissions, as well as reinstalling ROM dirty and with factory reset. I'm hoping this isn't hardware failure because I just bought this phone used but it seems to be a reoccurring problem with others as well. Any NEW suggestions not given from quick Google/xda search?
Click to expand...
Click to collapse
I'd suggest to check your Wireless Access Point (modem or router) wireless settings for security, check and see if it's set to use WPA/WPA2, which is common on some modems/routers, change it to either WPA or WPA2 (preferred) not both, it's a known issue with WiFi networks and having it set to using both, I had the same problem before with my phone connecting to my WiFi.
Also if you use MAC Address Filtering on the modem/router, you should disable/clear that and let phone re-connect before enabling mac filtering again.
Almite said:
I'd suggest to check your Wireless Access Point (modem or router) wireless settings for security, check and see if it's set to use WPA/WPA2, which is common on some modems/routers, change it to either WPA or WPA2 (preferred) not both, it's a known issue with WiFi networks and having it set to using both, I had the same problem before with my phone connecting to my WiFi.
Also if you use MAC Address Filtering on the modem/router, you should disable/clear that and let phone re-connect before enabling mac filtering again.
Click to expand...
Click to collapse
The problem I am having is not that it won't connect to a particular network. Wifi will not initialize on the device at all and is stuck in "Turning On..." state. I found more and more posts where people ended up having to send in to Samsung so I spoke with them and even though I purchased the phone used its thankfully still under warranty and they will be replacing it. The did not confirm whether or not it was a true known device issue but were quick to file the exchange for me.
sigh, me too!
Just started having this problem on 4.3.1
great.
In my case, I had to wipe system and data before reinstalling my ROM.
Though the only reason it was happening to me was because Beanstalk 4.4.2 didn't want to get past the splash screen when I tried to install it so I downgraded back to ICS 4.0.4 without wiping. Good luck getting this issue fixed. Also another kernel might fix thingz for you if your current one does not like your device.
I have a similar problem. After a while, WiFi gets disconnected. If I go in settings - wifi, i get the message "unfortunately, settings has stopped" and I can't get WiFi to work again until I reboot the phone. The Wifi works again for a couple of minutes then stops.
I have flashed various different ROM (CM11, PA) but keeps getting the exact same behavior.
I've rebooted in safe mode and I don't get the problem now.

[Q] Data Connection Issues

Before I start let me explain I've searched for the answer to this and have yet to find any concrete answers. I've had my Verizon G'Nex since release and had it rooted before Best Buy had even run my credit card. I've been running SlimKat 4.4.2 Build 5 official and CWM Touch. Ever since I updated the ROM (clean flash) to the 4.4.4 experimental I've had problems with both 3G and LTE connecting to data. I have signal, in some cases "4 bars" worth, but it never actually connects to data unless I reboot the phone - that will last for a couple hours to a couple days then it's back to no data. I completely wiped the phone - data, cache, system, and sdcard...everything that CWM could possibly let you wipe - and then sideloaded the previously stated Slimkat which worked for months prior without issue. The problem still persists, and has gotten worse. I cannot use LTE at all. It will not connect regardless of what I do.
So my question here is what parts of Android affect data connection? Is this entirely ROM dependent, or does kernel have something to do with it? I'd rather not go through the trouble of finding another ROM that has speed and features of SlimKat, or randomly flashing kernels just to find it doing the same thing.
UTMorpheus said:
Before I start let me explain I've searched for the answer to this and have yet to find any concrete answers. I've had my Verizon G'Nex since release and had it rooted before Best Buy had even run my credit card. I've been running SlimKat 4.4.2 Build 5 official and CWM Touch. Ever since I updated the ROM (clean flash) to the 4.4.4 experimental I've had problems with both 3G and LTE connecting to data. I have signal, in some cases "4 bars" worth, but it never actually connects to data unless I reboot the phone - that will last for a couple hours to a couple days then it's back to no data. I completely wiped the phone - data, cache, system, and sdcard...everything that CWM could possibly let you wipe - and then sideloaded the previously stated Slimkat which worked for months prior without issue. The problem still persists, and has gotten worse. I cannot use LTE at all. It will not connect regardless of what I do.
So my question here is what parts of Android affect data connection? Is this entirely ROM dependent, or does kernel have something to do with it? I'd rather not go through the trouble of finding another ROM that has speed and features of SlimKat, or randomly flashing kernels just to find it doing the same thing.
Click to expand...
Click to collapse
Well in not sure about this option being in your version of cwm.
However if it has wipe efs data as an option and you wiped it nothing that you do to try and fix your connections will work.
I found this out the hard way and had to buy a new gnex. Tried everything but couldn't get my efs data back.
DR3W5K1 said:
Well in not sure about this option being in your version of cwm.
However if it has wipe efs data as an option and you wiped it nothing that you do to try and fix your connections will work.
I found this out the hard way and had to buy a new gnex. Tried everything but couldn't get my efs data back.
Click to expand...
Click to collapse
No option about EFS. That's the thing that bothers me. I have voice and text, it can 'see' towers, it appears to be able to 'connect' to towers, but it's like it's not pulling an IP address or it can't contact DNS.

[Q] CM11 WiFi doesn't connect

Hi there, my first post.
I've used arco68's guide to root my S4 mini LTE (serranoltexx) and flashed the CyanogenMod 11 M9 snapshot (cm-11-20140804-SNAPSHOT-M9-serranoltexx.zip), but the WiFi isn't working properly. Sometimes it connects (very rarely), but most of the time it just says "Connecting", "Authenticating..." and then goes back to say "Saved, secued with WPA" and the process repeats again.
I've tried flashing the following ROMs, but the WiFi isn't working properly on either of them:
cm-11-20140804-SNAPSHOT-M9-serranoltexx.zip (current)
cm-11-20140708-SNAPSHOT-M8-serranoltexx.zip
cm-11-20140813-NIGHTLY-serranoltexx.zip
Other things I've tried so far:
Using CM File Manager to delete contents of /data/misc/wifi and rebooting, as described here, but it didn't help.
Installed SQLite Debugger, went to Settings Storage > setttings.db > Global, where I wanted to change the value of wifi_display_on to 0 as described here, but it was already set to 0, so no luck here.
Changed the Region Code in WiFi settings (as described here) to United States, then to Europe, but this didn't help either.
Installed the latest nightly update, but still nothing.
Basically, I've tried everything I could find, but the WiFi still doesn't work, and I have no idea why. I don't want to downgrade to CM 10.2, since later when I decide to upgrade to CM 11, I'd need to wipe all the data and make a clean CM11 install. Also, I don't want to flash any other ROM except CM, so telling me to install Paranoid Android or anything else wouldn't help.
If you have any ideas how to solve this, that would be great! Also, feel free to ask for any additional details.
Update: I've just discovered that it connects to open WiFi networks without any problems (though I've only tried it on 2 so far), so probably WPA encryption or my old home router can be the cause of the problem. I can only change my home router to WPA (it doesn't work with WPA2), so I've yet to try it on another router supporting WPA2. If that works, it would solve the whole problem! I'm ashamed to say I haven't thought of this earlier...
Update 2: I just tested it on a WPA2-protected WiFi network and it connects without problems. The most likely conclusion seems that CM11 has some problem with WPA, so for the time being I'll switch to another router with WPA2. Hopefully gets fixed with the next snapshot!

Categories

Resources