CM13(Haida.2016.02.27). Wifi no autoconnect to saved network.

[Jithug]

When WiFi is turned on. It doesn't automatically connect to a saved network. Rather than that need to go to settings>WiFi> and connect to already saved network mantua. Why doesn't it automatically connect when WiFi turned on? Please Fix.

[Jithug]

Spelling Correction --mantua=manually

[s0rl0v]

Just wait a bit longer. It works for me (urushi).

[MardonHH]

@mikeNG can be closed no such bug present

[bykidi]

@MardonHH nope, it's still here.

[nie11kun]

same issue on my arc s
i have to connect manually

[MardonHH]

works fine here on my anzu

[Soarexx]

I have the same problem on my Urushi. Have to manually connect each time at work and home.

[bykidi]

bugreport.zip

[ghost]

Same for me on my anzu/Lt15i.

[bykidi]

Lets wait for next build come up and test it again.

[fred777]

Just a guess, but this might be related to Marshmallow's Auto-disconnet-when-internet-is-not-available-feature. It can be disabled via wifi options.

[bykidi]

@fred777 i got this bug whatever settings i choose

[Jithug]

I have disabled avoid poor connection in wifi settings. Still wifi doesn't auto connect. Its a bug may be. Under notification drawer when wifi is turned on. And scan for available wifi network within notification drawer . It shows non ranged wifi network also. Takes some time to show real available wifi network. And need to connect to wifi network manually.. May be some kind of lag in wifi..

[fred777]

Well, it just was a quick guess...

And I do have the same reconnect-issue on my iyokan. This makes my tasker scripts worthless because wifi access cannot be automated anymore.

[Djfe]

I have the same issue. I'm using the arc s. I have experienced it in the version from february and I'm experiencing it in the current version from april

the biggest problem I have with this is, that my phone uses up mobile data while I'm @ home or @ university, I find myself downloading apps at home and then I see: Oh, damn it was still on mobile connection...

Pls take a look at this bug and fix it in future versions. That would be greatly appreciated :+1:

Here is a screenshot of how it looks when it happens:

I even connected manually after taking the screenshot and in the next 5min it disconnected and never reconnected again even though I was in the wifi settings the whole time It's not set so that it uses mobile internet instead of wifi, when the connection is bad and it's set to always on

In the log files of my system I find entries like: '''Wifi connection closed with errorCode 20 Unexpected mtu value: 0, wlan0'''

So there's definitely an issue

I'll add a log file to this post in a few minutes. I just have to edit out personal stuff/reboot my device first.

[fred777]

Well - as it turns out, this issue is not related to LX at all, but to CM13 in general. I have exactly the same issue with my shiny new (used) Motorola Droid 4 and CM13...

Also, if you activate Wifi via Settings menu, it does reconnect as expected, so we have to use this is as workaround.

Seems to be a bug in quick settings.

[Djfe]

'''Seems to be a bug in quick settings.''' I disagree, for me it didn't connect even though the wifi settings were open. No quick settings were involved at all

anyways, thx for the tip, that it's a general issue in cm13 so it will hopefully be fixed with one of the next updates (upstream)

[fred777]

Hm... For me, it almost always works with wifi switch in settings app. But I must confess: it sometimes does not.

With Quick Settings, it almost always does not work, though.

But there is a workaround at least for those who have Tasker-App: Create a Task that enables Wifi and then Reassociates Wifi.... This seems to be bullet proof.

[emadmahdi]

i have the same problem ... I am using Samsung Galaxy Exhibit SGH-T599 with Marshmallow CM13 ...

I fixed the problem by creating a job in TASKER that do "Wifi Net Associate" every 5 Minutes ... Plus another two jobs for "Screen On" and "Screen Off" that also do "Wifi Net Associate" ...