Captive Portal not working since the Oreo update

  • Thread starter Thread starter Android Central Question
  • Start date Start date
A

Android Central Question

It worked perfectly before that, now it crashes everytime. Running Oreo on a Samsung A7
 
I did it all and still not working
Not sure what else to suggest. I've seen another thread where a member reported the same problem on the same phone. You could try some general troubleshooting, like wiping the cache partition or booting in safe mode, but there's a chance that the system update included a bug for that specific model.
 
Not sure what else to suggest. I've seen another thread where a member reported the same problem on the same phone. You could try some general troubleshooting, like wiping the cache partition or booting in safe mode, but there's a chance that the system update included a bug for that specific model.

Thanks, if I manage to fix it I'll post it
 
One work around I've found is to navigate to a non-secured website, meaning HTTP instead of HTTPS (I use www.weather.com ).

I have a similar issue on my V20 running nougat. The best I can figure is that the captive portal is tripped up by the security of HTTPS sites. For example, using your browser to go to Facebook won't cause the redirect to the Wi-Fi login page, but a non-secured site never fails to redirect. Once logged in to the Wi-Fi, things work normally.

Don't ask me why this happens. On a side note, this work around may get harder over time unless the underlying issue is fixed. One article I read trying to fix my issue said that Google is pushing websites to go to secured HTTPS, and most big sites already do this. I have successfully used the Wi-Fi router's correct ip address (usually 192.168.0.1) to trigger the redirect to the captive portal too.
 

Trending Posts

Members online

Forum statistics

Threads
955,961
Messages
6,966,243
Members
3,163,446
Latest member
Laurie2Megan