FP5 cannot connect to home wifi

[eozN0921]

Today I have flashed /e/OS 3.4 on my FP5. I have left my bootloader unlocked, because I am afraid to brick my phone (I came from the latest stock Fairphone OS). Everything seems to work except for one strange flaw:

The phone “sees” my home wifi and the guest wifi, but cannot connect to them. The process is aborted after a second, and it says “Saved” next to the wifi icon. Password is correct, of course. There is no other error message or anything else from which I can deduct what might be wrong.

Even stranger: it also “sees” a public access point near my house across the street. Surprisingly I can connect to this one. At the moment this is the only way to connect to the internet. I have no SIM card in it, because mine is in another /e/OS phone - an FP4 which is working perfectly and reliably - my workhorse at the moment.

Does anyone here have an idea what is going on in the background? Is this a bug? All my other devices - computers, printers, mobile etc. have no trouble to connect to my router, and I do not have a complex network setup or complex firewall settings.

Any suggestion is greatly appreciated.

[tcecyk]

there was this thread recently - No wifi after upgrade to android 15

[eozN0921]

Thank you for pointing me to this one. Obviously I am not the only one with these problems. Surprisingly, I have been able to solve the issue, but I have no idea how and why my “solution” works, but it does so far. Without any error message you are left in the dark completely.

Here is what I did - I was just playing around and had this curious inspiration:

• I opened Settings - Wifi and Internet
• I looked at the entry for my home network/router which the phone would not connect to.
• I chose the option “Add new Wifi”
• I created an exact clone of my network SSID and password without previously deleting the existing one.
• All of a sudden the older entry had disappeared, and the phone connected to the clone immediately.
• I switched the phone off and on a couple of times in order to see if this was persistent, and it was. As of today, it still works after switching on the phone.

All I can say now is: opaque problem, opaque solution But maybe this helps other people, too - who knows…