[Rrrr7]

Hi guys,
I don't know why but since yersterday my DTEK50 connects to my usual Wifi networks but says "Connected, no internet access". It does this on my usual home networks WICH WORK 100% because I have other devices including my old Q10. It also does it on other networks wich also work 100%. I tried forgetting those networks, rebooting the phone, rebooting the router, nothing. What the hell?
Oh, and to make things more interesting, I disabled the Cellular Data and guess what, I can actually access the Internet just fine on the Wifi networks in question, even though it says "Connected, no Internet".

I disabled data limit and warning also.

AAI795
Patch level January 2017

[Johnny Dollar]

Ok 2 things...

Since this just happened recently I would speak to your cell provider/home provider re: any recent network problems or changes. 2. Download and run BlackBerry Virtual Expert to test your phones wifi.

Oh, maybe Restart the phone.

Good luck.

[YeemanBB]

Try switching off Aggressive WiFi to cell data handover (under Settings>Developer mode) if it is switched on. Developer mode can be made accessible by tapping several times rapidly on the Build number of your phone under Settings>About Phone.

[dimmi10]

Try to go to wifi settings on your dtek50 and choose help and feedback. That helps me

[Rrrr7]

Ok 2 things...

Since this just happened recently I would speak to your cell provider/home provider re: any recent network problems or changes. 2. Download and run BlackBerry Virtual Expert to test your phones wifi.

Oh, maybe Restart the phone.

Good luck.

Hi, i did several restarts including the networking equipment. I'm actually writing this on my home wifi but with the notification in the status bar, as I said the internet connection works but the phone thinks it's not.
I don't see what it has to do with my carrier, I have unlimited plan anyways.
It does work correctly on some wifi networks!
Virtual expert shows everything is okay.

[Rrrr7]

Try switching off Aggressive WiFi to cell data handover (under Settings>Developer mode) if it is switched on. Developer mode can be made accessible by tapping several times rapidly on the Build number of your phone under Settings>About Phone.

Hi, did just that. Aggressive wifi to cell data was off though. No change.

[Rrrr7]

Try to go to wifi settings on your dtek50 and choose help and feedback. That helps me

I can't seem to find help and feedback, I only see help, which sends me to some blackberry help and faq website.

[zoom6628]

I tried the solution on my brand new DTEK60 purchased yesterday
Instructions at end of this page network programming - android 6.0.1 force wifi connection with no internet access - Stack Overflow
Seems this is an Android 6.0 issue and not a DTEK issue. Copied below for convenience.

Reboot phone, connect to the non-Internet Wifi;
Go to Settings and create a new user;
Continue, continue, and continue until you see "Checking connection";
As soon as you see "checking connection", switch off your phone;
Switch on your phone again, you will be in "Owner" user, keep it;
Toggle Wifi, and the exclamation mark should disappear quickly
Remove that new user or just leave it there;

[Rrrr7]

I tried the solution on my brand new DTEK60 purchased yesterday
Instructions at end of this page network programming - android 6.0.1 force wifi connection with no internet access - Stack Overflow
Seems this is an Android 6.0 issue and not a DTEK issue. Copied below for convenience.

Reboot phone, connect to the non-Internet Wifi;
Go to Settings and create a new user;
Continue, continue, and continue until you see "Checking connection";
As soon as you see "checking connection", switch off your phone;
Switch on your phone again, you will be in "Owner" user, keep it;
Toggle Wifi, and the exclamation mark should disappear quickly
Remove that new user or just leave it there;

I'll try that! Thanks!

[Rrrr7]

The problem seems to have disappeared by itself. After about four days with the issue I noticed the wireless started to work normally again.

I also got the February patch yesterday so now it's hard to know what exactly fixed it.