[Lauwer]

I have a Samsung Galaxy S7 and since the last Android upgrade I can't go to the list with available wifi connections anymore in settings. The moment I touch 'Wi-Fi', the settings crash and I get the message "Settings has stopped. Open app again"
I've reset the phone to factory settings but this didn't help.

When I click the Wifi icon from the dropdown screen at the top of the phone's screen, I am able to connect to open connections, but every time I touch the name of a secure wifi connection, the settings crash again and I get the same error message as mentioned above. The secure wifi connections that were already saved in my phone, do still work and connect automatically.
I hope someone can help me with this problem...

[B. Diddy]

Welcome to Android Central! Does this also happen in Safe Mode? https://support.t-mobile.com/docs/DOC-28008

[Alx75]

Hi,

I have the same problem.
I downloaded and installed whatever update that was new and available 2 days ago, and ever since, I cannot access the wifi seetings.
Like Lawer said, I can't see/choose the available networks anymore.

So i factory reset my phone, which took care of the problem, until I reinstalled my apps etc.. from Smart Switch.
From there, the probleme happened again.
From what I've read online, it could be related to one of my apps, but I have taken out my sd card, and uninstalled all the non-stock apps, and the problem is still there, even with a safe mode reboot.

Any ideas?
Thanks all

[Woland1]

Same exact problem on my s6 after updating to Nougat yesterday. Tried wiping system cache, started in safe mode, problem is still there. Any ideas would be appreciated.

[Lauwer]

Thanks for your response P. Diddy, I just tried safe mode and yes, still exactly the same problem :-(

I have contacted the Dutch Samsung help center but they sent me to the repair shop, I have an appointment with them tomorrow, will let you guys now if they find the problem.

[Woland1]

Thanks for your response P. Diddy, I just tried safe mode and yes, still exactly the same problem :-(

I have contacted the Dutch Samsung help center but they sent me to the repair shop, I have an appointment with them tomorrow, will let you guys now if they find the problem.

Let us know. I talked to their online support and they weren't helpful in the slightest, just suggested cache wipe/restart, which I told them I had already done. Then they just suggested factory reset.

[B. Diddy]

You could also try reinstalling the firmware using Smart Switch, in case something with the current firmware got corrupted: http://www.sammobile.com/forum/showthread.php?t=29914

[Woland1]

Found a workaround: install wifi password manager by osmanapps since it replaces the existing wifi manager.

[Lauwer]

Found a workaround: install wifi password manager by osmanapps since it replaces the existing wifi manager.

Smart thinking, thanks for letting me know!! I wasted a lot of time today at the Samsung repair shop and on the process of re-installing afterwards :-( I think they just set the phone back to factory settings, still have the same problem. Thanks again for the great tip!

[Woland1]

Another workaround I found:
1. turn off wifi
2. open the built-in wifi app while it's still off
3. turn on wifi while already in it via the slider in the top right
4. the wifi app will now work, at least for a bit

[Lauwer]

Another workaround I found:
1. turn off wifi
2. open the built-in wifi app while it's still off
3. turn on wifi while already in it via the slider in the top right
4. the wifi app will not work, at least for a bit

Ha, that trick is even better than the first one, thx for sharing!!

[Electr0]

Hey @Lauwer,

I have this problem too on the same device.

Did you ever find a fix?

[Lauwer]

Hey @Lauwer,

I have this problem too on the same device.

Did you ever find a fix?

Hi, didn't find a real fix but the 2 workarounds of Woland1 described in the replies here are great! Have been using it a lot already. Hope this helps....

[Electr0]

Hi, didn't find a real fix but the 2 workarounds of Woland1 described in the replies here are great! Have been using it a lot already. Hope this helps....

That's unfortunate.

Thanks. I'll give it a go.

I've been scouring Xda, Reddit, Google Forums, etc and it seems that a few people are experiencing it. I've tried cleaning all the different caches, booting in safe mode (still occurs) and even a master reset and nothing seems to work.

I posted here:
https://forum.xda-developers.com/gal...tings-t3585750
But got nothing.

[Electr0]

Oops, double post.

[Lauwer]

That's unfortunate.

Thanks. I'll give it a go.

I've been scouring Xda, Reddit, Google Forums, etc and it seems that a few people are experiencing it. I've tried cleaning all the different caches, booting in safe mode (still occurs) and even a master reset and nothing seems to work.

It's very weird that not that many people experience it.... I thought maybe more people would have posted about it by now. The (Dutch) Samsung helpdesk people didn't hear about the problem yet last week. I also did the exact same actions as you did and wasted a lot of time on factory resets and a useless visit to the Samsung repair center. I wonder if it's a particular app that we use that causes this!

[Electr0]

Sorry for the delayed reply, I'm travelling at the moment.

I wonder if it's a particular app that we use that causes this!

Perhaps so?

Maybe we can try and work out what's going on here together. Another user @ac Question is having the same problem over here.

All three of us have only started experiencing this problem since updating to Nougat.

I'm currently on this setup:

• Android Version: 7.0
• Baseband Version: G930FXXU1DQBH
• Kernel Version: 3.18.14-10422490, dpi@SWHE8814 #1 , Mon Mar 13 19:22:59 KST 2017
• Build Number: NRD90M.G930FXXS1DQCE
• Android Security Patch Level: 1 March 2017

Perhaps we should both compile a list of app to see which we both have?

[Electr0]

@Alx75 and @Woland1 do you still have this issue? Did either of you end up finding a fix?

If you still have the issue, would you mind filling out the following details:

• Android Version:
• Baseband Version:
• Kernel Version:
• Build Number:
• Android Security Patch Level:

[Woland1]

@Alx75 and @Woland1 do you still have this issue? Did either of you end up finding a fix?

If you still have the issue, would you mind filling out the following details:

• Android Version:
• Baseband Version:
• Kernel Version:
• Build Number:
• Android Security Patch Level:

Yep, still have it, working with the workarounds I mentioned.

Android version: 7.0
Baseband Version: G920FXXU5EQB3
Kernel Version: 3.10.61
Build Number: NRD90M
Android Security Patch Level: Feb 1, 2017

[Electr0]

Yep, still have it, working with the workarounds I mentioned.

Android version: 7.0
Baseband Version: G920FXXU5EQB3
Kernel Version: 3.10.61
Build Number: NRD90M
Android Security Patch Level: Feb 1, 2017

Cool, thanks for the info.

So it seems that this issue is related to Android 7.0 but has nothing to do with the Baseband, Kernel or Security Patch, as we both have the issue despite the aforementioned differences.

I tried to explore the option of reinstalling the firmware as @B. Diddy mentioned, but the guide using Samsung Smart Switch that he linked to does not work for the S7, at least in my case. The program states that this model of phone is not able to be initialised.

We've also established the following:

• The issue occurs while the phone is in Safe Mode - As per here* (applies to Nexus devices but it should be ok to assume Safe Mode functions the same way on the S7) this means that no download app should be causing the issue.
• Clearing the Dalvik/System Cache does not fix the issue
• Clearing the App Cache does not fix the issue
• Performing a Hard/Master reset does fix the issue (when a restoration IS completed afterwards)

Therefore we need to find out:

• Whether a Hard/Master reset fixes the issue (when a restoration is NOT completed afterwards). As per the results when using the phone in Safe Mode, the expected result is that this does NOT fix the issue.
• If reinstalling the firmware fixes the issue.

As per the above, it seems it must be an issue with the Firmware (Android Version) or one of the Stock Apps.

[B. Diddy]

If Smart Switch doesn't work, you could try using Odin, although this is more involved: http://forums.androidcentral.com/amb...interface.html

[Electr0]

Breaking News - Possible Fix Found

This morning I may have accidentally discovered a fix, by pure chance.

I turned my phone on and a message came up, along the lines of:
"You have over 200 Wifi access points saved. Would you like to delete the the oldest 259 to improve you Wifi experience?"

I pressed yes, and low and behold, my Wifi settings crash issue seems to be resolved. My Wifi also turns on an off a lot faster that is has since I've been experiencing the settings crash issue.

I've done a quick search and to do this manually it seems the following ways should work:

• Settings -> Lock screen and security -> Other security settings ->Clear credentials
• General management -> Reset -> Reset network settings
• Clear the wpa_supplicant.conf file if your phone is rooted (Guide)
• Download a Third Party Wifi connection manager, navigate to 'Known Networks' and then Clear All (no specific app noted)

* Sources: Android Central Thread, Stack Exchange Thread

I hope this can solve our issue!

@Woland1 @Lauwer @Alx75
Please try out this solution and report back if it works.

[B. Diddy]

Excellent detective work! It sure seems odd that this would be enough to cause a problem, but if you demonstrated improvement after paring down that list, that sounds like the solution!

[Zingapuro]

Hi guys,

Just wanted to thank Electr0, insight seems to have solved my problem. Just to clarify, I'm running Android 7.1.1, OxygenOS 4.1.3 on OnePlus3, and this single step solved my problem:

Settings -> Backup & Reset -> Reset Network Settings

Unfortunately, I lost all my saved WiFi passwords -- but it's worth it to stop that annoying Settings crash (sometimes it would happen 10 times in a row before I could finally access my WiFi...)

So yeah -- thanks Electr0 :-)