Disabling scan throttling doesn’t do anything either.
To use the warranty to return the phone and have an older firmware in return is lame but I am thinking about that if no other solution is found
After enabling WPA3 the behaviour has been a bit different for me, now the phone has been restarting on its own when the issue occurs.
Not sure if the restart happens immediately or if it takes a while, it usually happens in the middle of the night and I only notice in the morning.
I’m keen to purchase a FP6 (e/os) asap as my current iPhone is on its last legs, but as a professional wifi installer this issue really concerns me. Do we have an idea of how widespread this issue is? If it’s a software/driver issue I would guess it’s affecting all users but likely fixable with an update. It seems to have been going on for a while though…
I should probably pose this question directly to the manufacturer too to see if they can offer any reassurances in advance of purchase. Thanks in advance for any comments.
Hi,
I would guess it’s affecting all users
I’m not affect. WiFi has been working fine on my side since the beginning. So I guess this is more hardware related.
Hi @theyaman , are you also using WiFi 6 in your network?
Thanks to everyone for investigating. My mother has had the same problem for months, yesterday I completely reinstalled Android on her FP6 by unlocking the bootloader but the problem persisted.
I now downgraded their WiFi to 5, we’ll see if that changes anything. Their network does still have a single mesh repeater which I kept on.
Thanks for the feedback. It would be interesting to know whether someone who’s purchased a FP6 more recently is seeing this issue or not. I’m pinning my hopes that the cause is due to a ‘bad batch’ of early production components… (not especially optimistic about this though).
@Paulb32 I’ve been using a FP6 since end of July with all FP sw releases, a good variety of Wi-Fi networks including 6, no problems.
I think this problem is likely the result of a combination of circumstances in each case. This thread is the only one on the subject I’ve found on this forum and I’m sure we would have heard from more people if it was widespread.
Reading the thread some points recurr regularly such as Wi-Fi 6, mesh, possibly router and / or repeater hardware. Phone inactivity is also frequently mentioned. There may be problems with some router software distributions.
Anyone who encounters problems should contact official FP Support as per my posts above so that the engineers can build up a detailed picture.
EDIT To add that I use VPN most of the time.
3 Likes
Thanks for your detailed reply. Totally agree with your logic. That’s enough reassurance for me to make the change from iPhone to Fairphone - looking forward to it! Have a good evening.
2 Likes
I did not have this issue for many months now. But yesterday and today I noticed that YouTube stopped downloading my offline playlist to my SD card. The reason was that wifi was off, and not detecting any SSIDs. I had to reboot the phone to fix it but after the playlist download resumed it crashed the wifi adapter again after some minutes. I’m going to reboot again now but but I thought I’d take the time to report this because I remembered that other users had wifi issues. I’m also using a VPN. I don’t know if the heavy SD writes or the VPN could affect anything here.
Edit: The reboot fixed it again, and 15 minutes later it still hasn’t crashed the wifi while downloading the playlist. We’ll see how it goes. Oh and I’m on FP6.QREL.15.162.0
1 Like
Since I bought my Fairphone 6 it worked fine without any major issues. But after the first software upgrade (it was FP6.QREL.15.148.0) I started to experience Wifi driver crashes at random moments. Sometimes it looks like a sudden reboot of the phone, sometimes it freezes and reboots after that. But most of the time it just looses Wifi connection and stops seeing any networks. Turning wifi of and on does not help - it just stays off. It’s looks very similar to the issue reported here (and also in the comments here).
Using ADB, I found the following lines in the log
11-05 18:58:56.511 1447 1534 E android.hardware.wifi-service: Could not set interface MAC address for wlan0 (Invalid argument)
11-05 18:58:56.511 1447 1534 E android.hardware.wifi-service: Could not set interface flags for wlan0 (Invalid argument)
11-05 18:58:56.511 1447 1534 E android.hardware.wifi-service: SetUpState(true) failed. Wait for driver ready.
Turing airplane mode on and off gives the following lines:
------ airplane mode on —
11-05 19:17:10.554 1447 1534 I android.hardware.wifi-service: Adding interface handle for wifi-aware0
11-05 19:17:10.554 1447 1534 I android.hardware.wifi-service: Adding interface handle for wlan0
11-05 19:17:10.554 1447 1534 I android.hardware.wifi-service: Adding interface handle for p2p0
11-05 19:17:10.554 1447 1534 W android.hardware.wifi-service: No active wlan interfaces in use! Using default
11-05 19:17:10.609 1447 3368 I CLD80211: android.hardware.wifi-service: Sent msg on exit sock to unblock poll()
11-05 19:17:10.614 1447 3368 I android.hardware.wifi-service: Legacy HAL stop complete callback received
11-05 19:17:10.615 1447 1534 I android.hardware.wifi-service: Wifi HAL stopped
------ airplane mode off ------------
11-05 19:17:31.677 1447 1534 W android.hardware.wifi-service: AIBinder_linkToDeath is being called with a non-null cookie and no onUnlink callback set. This might not be intended. AIBinder_DeathRecipient_setOnUnlinked should be called first.
------ enter internet settings -----------
11-05 19:17:53.133 1447 1534 E android.hardware.wifi-service: Failed to write driver state control param: Invalid argument
11-05 19:17:53.133 1447 1534 E android.hardware.wifi-service: Failed to load WiFi driver
11-05 19:17:53.133 1447 1534 E android.hardware.wifi-service: Failed to initialize firmware mode controller
11-05 19:17:53.133 1447 1534 E android.hardware.wifi-service: Wifi HAL start failed
11-05 19:17:55.165 1447 1534 W android.hardware.wifi-service: AIBinder_linkToDeath is being called with a non-null cookie and no onUnlink callback set. This might not be intended. AIBinder_DeathRecipient_setOnUnlinked should be called first.
----- try to turn on Wifi in the internet settings --------------
11-05 19:18:15.665 1447 1534 E android.hardware.wifi-service: Failed to write driver state control param: Invalid argument
11-05 19:18:15.665 1447 1534 E android.hardware.wifi-service: Failed to load WiFi driver
11-05 19:18:15.665 1447 1534 E android.hardware.wifi-service: Failed to initialize firmware mode controller
11-05 19:18:15.666 1447 1534 E android.hardware.wifi-service: Wifi HAL start failed
11-05 19:18:15.684 1447 1534 W android.hardware.wifi-service: AIBinder_linkToDeath is being called with a non-null cookie and no onUnlink callback set. This might not be intended. AIBinder_DeathRecipient_setOnUnlinked should be called first.
I’ve contacted the official technical support, but without full factory reset they refuse to do anything with my report. Doing factory reset is very painful for me because some Android Apps do not support any forms of backup and you need to restore everything manually.
I’ve also tried the following steps which had no effect on my issue:
- Reset Bluetooth & Wi-Fi (from System → Reset options)
- Disable MAC randomization for my Wifi network (Privacy → Use device MAC)
Two firmware updates have been released since, but the issue remains (now in the FP6.QREL.15.162.0 version).
Maybe somebody experienced the same problem and know some workarounds?
1 Like
I have a similar issue since the first software upgrade (it was FP6.QREL.15.148.0). The difference is that in my case reboot helps for some time. I’ve contacted the official technical support, but after I refused to make a factory reset they just silently closed the ticket as “Solved” 
. Now I am upgraded to the latest firmware (FP6.QREL.15.162.0) and the problem is still there. I’ve collected the logs via adb, maybe it could be helpful.
Found very similar issues:
Some comments suggest disabling Wi-Fi 6 (802.11ax) on the router. I’ll try this to see if it makes a difference.
I also reported the issue to support but haven’t heard from them yet.
Regarding the factory reset, I performed it twice (after each update) on my phone but the issue is still there.
1 Like
Disabling Wi-Fi 6 (802.11ax) didn’t resolve the issue for me. Since I disabled 802.11ax on my router, the phone has spontaneously rebooted once and lost Wi-Fi twice. It might have become less frequent, but that could just be wishful thinking. I checked the logs via ADB, it is the same problem:
01-04 19:56:08.444 1453 1453 E android.hardware.wifi-service: Could not set interface MAC address for wlan0 (Invalid argument)
01-04 19:56:08.445 1453 1453 E android.hardware.wifi-service: Could not set interface flags for wlan0 (Invalid argument)
01-04 19:56:08.445 1453 1453 E android.hardware.wifi-service: SetUpState(true) failed. Wait for driver ready.
I would have been surprised, had a factory reset worked for Nikolay or Jovem. By that logic reinstalling android with their guide would have also resolved the issue.
Regarding WiFi6:
After downgrading the network to WiFi5 the FP6 still has the same issue as described here. I did contact support in November and have only received automated mails.
Next I will probably call them, ask for the phone to be replaced with a new one and hope for the best.
I’ve had this happen twice since new (September). Restart phone cures it
Have 2.4 and 5Gz in part of the house.
All bands in the main part of the house.
I’m a heavy WiFi user.
FWIW I kinda forgot about this issue. I put my phone on an existing 2.4GHz only SSID I had made prior for my 3D printer. I haven’t had issues since. No 5GHz wifi.
I see mixed results from others though here.
It seems I’ve found a workaround, at least for my home network. I’ve now been connected to Wi-Fi for 25 hours without any reboots! Previously, reboots happened many times a day.
In addition to disabling 802.11ax (Wi-Fi 6), I changed several router settings:
- disabled Wi-Fi band steering
- disabled automatic channel selection (set fixed channels for both 2.4 GHz and 5 GHz)
- disabled automatic bandwidth selection (set 20 MHz for 2.4 GHz and 40 MHz for 5 GHz
- disabled various features, which I assume are unrelated to the problem
Next, I plan to enable one feature at a time and see if any of them triggers the problem. Will start with Wi-Fi band steering, which I currently suspect most.
3 Likes