Hi,

seems like my WiFi died completely (the scan stays stuck on searching for networks, no matter what)

I’ve tried resetting the internet settings, to no avail. Rebooted a few times as well.

Logs give me “failed to unregister death recipient! com.android.server.wifi.scanner.wifiscanningserviceimpl$internallistner@xxxxxxx”

Device is on 2024121200.

Would anyone know what’s going on and how to fix this ?

    orydeatemi Not sure, but for this kind of issue if resetting network settings doesn't work, I'd try other things like safe mode and if it's still not working, a factory reset.

    Are you able to start a wifi hotspot with the phone?

        other8026

        Thanks a lot for the pointers!

        The safe mode reboot got me connected, once, and now we're back to the old ways.

        Hotspot won't start and just says "error"

            2 months later

            other8026

            So, one thing that works is activating airplane mode, rebooting with airplane mode activated, and THEN activating Wi-Fi or hotspot.

            WiFi scans correctly and can connect, and the hotspot activates as well.

            Best I can garner for now (I'm in a place where my home provider doesn't have a roaming agreement, and I'm not switching my home sim on here) is that there's some type of upstream bug that might be linked to cell providers who don't allow connection sharing / hotspots, and that, for some reason, is then also applied to activating WiFi.

                orydeatemi Best I can garner for now (I'm in a place where my home provider doesn't have a roaming agreement, and I'm not switching my home sim on here) is that there's some type of upstream bug that might be linked to cell providers who don't allow connection sharing / hotspots, and that, for some reason, is then also applied to activating WiFi.

                I'm not sure how it works now exactly, but these kinds of things aren't applied, or are ignored, or aren't even included in carrier settings on GrapheneOS. So, it may be a bug, but I can't imagine it would be because of carrier settings, otherwise we'd be hearing about this issue from other people as well.

                If you're still having this issue after almost 2 months, I'd suggest a factory reset to see if you continue to have this same issue.

                    other8026 as I alluded to, I'm not in a place where a reset is a practical possibility, if only because reauthorizing Signal and WhatsApp would be impossible. I've been there since my initial message.

                    Bandwith and outages-wise, re-downloading both a stock image and GrapheneOS would probably take half a day. I'll definitely do it once I'm back in a more normal location, at which point I will not be putting the SIM I am using here back into the phone.

                    The workaround described here works, hence my sneaking suspicion that it might come from something upstream.

                        orydeatemi Bandwith and outages-wise, re-downloading both a stock image and GrapheneOS would probably take half a day.

                        A factory reset wouldn't require downloading anything. Not sure why you'd need to download the stock image unless you wanted to test if the same happens on the stock OS. If your carrier blocks using hotspots, then it definitely won't work on the stock OS.

                        That said, while factory resetting takes very little time, backing up apps, restoring them, and setting everything up again can take quite a while depending on the setup.

                        orydeatemi The workaround described here works, hence my sneaking suspicion that it might come from something upstream.

                        orydeatemi rebooting with airplane mode activated, and THEN activating Wi-Fi

                        These things seem strange to me. I agree that there might be some upstream bug, but I am not sure how carrier config can affect wifi like this. I'd think that the best way to figure out what's really going on would be by seeing the full system logs.

                                other8026 These things seem strange to me. I agree that there might be some upstream bug, but I am not sure how carrier config can affect wifi like this. I'd think that the best way to figure out what's really going on would be by seeing the full system logs.

                                Yeah, it's super weird, moreso since Bluetooth isn't affected, which I believe might tip the scales further towards something in software and not hardware. I'll try to upload a syslog.