problems reconnecting wifi
- /e/ version: 0.19-20211027142972
- Device model(s): FP3, FP3+
- Device rooted: no
In the last time (since /e/ 0.18) I see problems reestablishing a wifi connection. Older /e/ versions were much better (!) related to this, I never had that on 0.17.
When the device has wifi switched on and leaves then the wifi environment it was connected to the current connection will be terminated. OK so far. - When the device reaches then again a known wifi environment (the same or another) the connection is reestablished automatically. The wifi symbol in the status bar appears again, everything looks good, but it isn't.
Another situation is the end of flight mode. When flight mode is switched off all connections should be reestablished. But it can happen that wifi connections are then not as expected.
The problem shows up by mysterious network failures and timeouts in several apps. The first time I had this was in F-Droid and Aurora, both could suddenly not connect to their completely different repositories at the same time. Whatever you did, they turned the wheel and couldn't connect. Then streaming apps (RadioDroid), mail (FairEmail) and Twitter client (AndStatus).
Some of these apps (FairEmail, AndStatus) have also been active and working correctly while there was no wifi connection. They did then work on cellular network. But they began struggling from that moment on when the wifi connection came back. Other apps (App stores) are normally closed and have been started after the wifi was reconnected.
I have also the impression that it affects only some apps, not all. Some apps report network problems while other apps do still work correctly. So it may be related to network protocols or security layers.
Steps to reproduce
Not easy. Doesn't happen all the time, only on some days nobody can forecast, two times a week. But I have this ongoing on two devices, an FP3 and an FP3+, both preinstalled and then OTA updated.
What is the expected correct behavior?
I would expect that a reestablished wifi connection (symbolized by the wifi symbol in the status bar) does indeed work in every app.
Especially I would expect that the wifi symbol doesn't confuse the user. It should be visible when a working connection is established and not before.
I also would expect that when a wifi connection can't be established by whatever reason a mobile connection is used as fallback. This is normally the case but not here. If wifi is on (but doesn't work correctly) the mobile connection is probably not tried at all.
Relevant logs (
Complicated because of it doesn't happen every day.
As a workaround the user can switch off wifi on the device and switch it on again, if he got wise to that it's just that phenomenon. Or reboot completely. Both helps.