Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

Wifi broken on FP4 after update to 1.5.1-s

  • /e/ version: 1.5.1-s
  • Device model(s): FP4
  • Developer mode enabled: yes
  • Device rooted: no
  • Trackers blocker enabled: no

Summary

Hi, I have a FP4 (bought in a Orange shop) on which I installed e/OS myself last January. The upgrade to 1.5.1-s went fine and smooth… but I have serious trouble with the Wi-Fi now. More precisely, I can connect to any network, but I can access the web only for a few minutes, after that I’m the dark. I am then connected without having access. The biggest downside of it being that it drains my battery in a few hours if I don’t disable the Wi-Fi.

I tried on different networks (personal and professional) and the behavior is the same. I did not change my network configuration, it was perfectly working before the update (and the same configuration is still working on my laptop).

The problem

Steps to reproduce

I connect to any Wi-Fi network (automatic connection according to location behaves similarly).

What is the current behavior?

I am connected to the network without access to Internet.

What is the expected correct behavior?

I should be connected to the network and be able to access Internet.

Technical informations

Relevant logs (adb logcat)

I created a log with logcat, but considering the huge variety of personal data in the file I would prefer to have a specific request (i.e., what to grep).

Relevant screenshots

Solutions

Workaround

To get it work again I have to reboot (disconnect/reconnect does not provide me internet access), it only works temporarily. A reset of my network settings works temporarily as well.

I haven't dived into an analysis of the duration, but it works for around 30 minutes I'd say.

Possible fixes

I tried to modify the DNS parameters, the MAC randomness, and on different websites. I can't retrieve my emails either.

However, pinging an IP address via Termux is successful. I guess there is an issue with the DNS setting then, that would explain why I can connect to networks without being able to access the web.