No problems here with AVM.
Yesterday I did the upgrade from OS 20 to OS 21 and my phone tells me now “Android-Version 14, LineageOS-Version 21.0-20240606-microG-FP3”.
I’m using Wifi on the AVM Fritzbox 5530 Fiber and the FP3 connected without a hitch after the upgrade. Today the FP3 tells me Wifi is on 5GHz, yesterday I didn’t check. The router changes between the channels depending on the traffic.
[/quote]
Could you check what version of Fritz!OS-Firmware you are running? Just to see if there is any rhyme or reason there?
My devices (where I cannot connect are using versions 7.30, 7.31, 7.57, and 7.58.
OK, everyone hold your horses: Inspired by this post I just tried something: In my F-Box wireless network settings → Security tab, I changed the encryption setting from WPA2 + WPA3 to just WPA2 and now it works!
So, everyone affected please try this out and report back to see if this is a reliable workaround or if I just got lucky…
2 Likes
Hi and sorry for spamming so much, but i have a positive happening, too!
I can’t really say what solved my wifi working, but here are some steps i can remember:
- After installing last update and recognizing wifi not working and so i disabled wifi in network menu and left it in that state until today
Today i followed the link suggested by @Cudo, which concerns a malfunctioning wpa_supplicant. There was told that the binary from the update before would fix wifi.
- So i extracted that binary from the ota update, but failed injecting into my running system via adb shell
While trying i realized, that tinkering in a running system is not that easy as i thought. All in all i located the binary in /system/vendor/bin and tried to replace that in my running system. That failed, because that partition is mounted read only. I consider this a security strategy. Fine. Furthermore i tried to mount that specific partition read/write, but that failed. Kinda frustrated i went to the wifi knob on my phone and enabled wifi again. Out of the sudden my phone connected… Btw.: i am currently not at my home, so other router again.
Stay tuned!
Ps: Thanks to @Cudo for the nice hints on the rollback protection and of course all devs making this possible!
@Taijian , thanks for that hint. The workaround with the WPA2/3 to WPA2 only works for me!
I have a Fritzbox 7590 AX with the latest update 7.81.
It does work indeed. Cool, thank you. It is gold enough for now.
Okay so I did fix the issue on my side!
I did disable entirely IEEE802.11w on OpenWRT (even if it was just optional before) and then restarted wpad.
After that, my FairPhone 3 on Android 14 QPR3 was able to connect!
Edit: So recommended settings on your wifi router is to just set your AP to use classic WPA2-PSK AES (CCMP) without any other encryption options.
Yep, switching to WPA2 only works.
It is FRITZ!OS 7.80, and the Wifi is on WPA2 + WPA3
Now the OS is also the latest, 7.81, same settings, the FP3 is connecting.
Thanks everyone for sharing your thoughts. Happy to see that the workaround is working fine for all of you.
We will continue to investigate and see if a proper fix can be implemented soon. I shall update if there is any news on that.
Thanks.
4 Likes
One other thing I noticed about the July 10th update is that the stuttering when media player controls are visible seems to be gone.
I’ve had long time ago such issue with my printer as AVM introduced the wpa3+wpa2 feature in their firmware. It was all about not supporting Protected Management Frames on the client.
1 Like
Yes indeed! The PMF was the issues. We now have them disabled and I have requested an early build to be triggered.
So, we should have the fix in with next build.
6 Likes
I installed the new build and WLAN works again with WPA 3. well done!
1 Like
Can confirm as well. Just installed the new build and switched wifi back to WPA2/WPA3 mode. Phone happily connects again.
Thank you for your efforts!
After all those years I’ve never been able to solve the WiFi disconnect problems. After a while (usually a few minutes) the WiFi disconnects and the phone goes to 4G.
Simply activating the screen is enough to automatically connect to WiFi after a few seconds. Any ideas?
i have this on some open wifi services… but not on my home network.
maybe ‘just’ a incompatibilty between wifi ap and mobile phone? ^^v
Since 2024-08-07 update, on stock camera app, I get a message that the device could be overheating. I think it’s a bug since the phone is not hot in my hands.
Do anyone else is experiencing this issue?
1 Like
Same for me, but only using the stock camera app. The Google camera modded thingy I’m using is perfectly happy, the phone is cool to the touch, and nothing else complains.
Also, the upgrade nuked my alarm clocks, so please be aware of that when installing it!Luckily I realized it in time, but to anyone else, please check before you accidentally oversleep 