I switched from GrapheneOS since WiFi and Bluetooth both didn’t work. Now, on iodéOS, Bluetooth now works but WiFi doesn’t. Apparently, it is an upstream bug in AOSP that I can’t fix myself. I will post my logs here when I have time.
!?!? This seems quite strange. Probably need more detail like what your wifi security, etc. are: WPA2/3? Enterprise or Personal? 2.4Ghz / 5Ghz?
I have P6 / P7P with no issues, certainly there are many P8 users so I would think this is a problem we can get through (but my optimism sometimes comes back to bite me 
)
Okay, so here is the output of adb shell dumpsys wifi. Please note I have omitted sensitive information.
Okay, never mind.
Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, heic, heif, webp, avif, svg).
I will open an issue on GitLab if I can find the right place and will post the link here.
I have adjusted the forum settings to allow a .txt upload so try again!
Unfortunately, while all our code is viewable at our Gitlab instance, signup is restricted to team members currently. so you can look through it but this is the place to post any issues.
Thanks. Here is the file at last.
diag_wifi_husky.txt (232.6 KB)
Let’s hope and pray it’s not a hardware defect…
!!! so this indicates it is basically a thermal issue? Just keep an ice pack handy, right?
I honestly can’t do much with your log, I build images and have tracked down my fair share of wifi blobs for Linux installs over the years, but if it isn’t blacklisting a module or grabbing a tarball and installing I am out of my league I’ll link our developer here but if it is just a single case he may not have capacity to dig into it either. Certainly we will be watching if others report the issue.
I suspect Graphene has many more Pixel 8 Pro users than we do, what do you see on their forums? Are you the unlucky unicorn?
Sorry for not replying in 8 days, but I know it’s not a thermal issue. When I reflashed an OTA update, Wi-Fi works again for only a couple of hours before vanishing. Same for hotspot. And yes, GrapheneOS’s GitHub issue tracker has been flooded with them too. Here is a link to one of them.
Oh yes please do
On second thought…
I am more convinced it’s a hardware issue despite what I posted earlier. Here are a couple of quotes from the GitHub issue I mentioned earlier:
I’m having the same issue on a Pixel 8 Pro. Here’s what I’ve seen so far:
Phone with stock OS seems to be working fine. I use the phone normally for one day before flashing Graphene.
Flash GrapheneOS. On first boot during initial setup, I cannot see any WiFi networks (although I’m 100% sure I have several networks in range). Have to finish setup without WiFi.
On restarting the phone, most of the time I can see WiFi networks and connect to my home network. While using the phone normally, WiFi disconnects at some point after 5-30 min, and I stop being able to see or connect to any WiFi networks. When I enable WiFi from Setting > Network & internet > Internet, it gets disabled automatically when go to a different screen. From the quick menu, when I enable WiFi, it shows
No networks available, although there are several in range. At this point I’ve tried several things: turn off adaptive connectivity, restarting WiFi, restoring to factory settings, making sure the option to automatically disable WiFi is turned off. Nothing seems to help and the issue keeps happening.Go back to stock OS for a few hours, WiFi works normally.
Flash GrapheneOS again (using a different OS and browser in the process), issue starts happenning again.
I’m not sure if this is a Graphene issue, or a hardware problem that is exacerbated when using Graphene. Maybe if I keep using Pixel OS for long enough I would see a similar issue, but again I just got the Pixel to use Graphene so I just flashed it almost straight away. I gathered some logs that I can share --not sure if they contain anything useful though, but lmk if you’re interested.
[Edit] I think these are the relevant parts of the logs:
... 03-13 17:44:00.759 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Failed to register radio mode change callback 03-13 17:44:00.760 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Failed to get SupportedIfaceCombinations matrix from legacy HAL: NOT_SUPPORTED 03-13 17:44:00.770 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Failed to set DFS flag; DFS channels may be unavailable. 03-13 17:44:00.781 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Failed to get chip capabilities from legacy HAL: NOT_SUPPORTED ... 03-13 17:47:32.876 1000 1407 1946 E WifiSelfRecovery: Restarting wifi for reason: Subsystem Restart ... --------- switch to system 03-13 17:47:56.879 wifi 1022 1068 W vendor.google.wifi_ext-service-vendor: No active wlan interfaces in use! Using default 03-13 17:47:56.879 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Unknown iface name: wlan0 03-13 17:47:56.879 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Unknown iface name: wlan0 --------- switch to main 03-13 17:47:56.881 1000 1407 1946 I HalDevMgr: currentModeId=0, requestModeId=3, currentModeIdValid=false 03-13 17:47:56.881 wifi 1022 1068 E WifiHAL : wifi_pre_initialize 03-13 17:47:56.882 wifi 1022 1068 E WifiHAL : --- HAL version: BCMDHD vendor HAL --- 03-13 17:47:56.882 wifi 1022 1068 I WifiHAL : Creating socket 03-13 17:47:56.882 wifi 1022 1068 E WifiHAL : Could not connect handle 03-13 17:47:56.882 wifi 1022 1068 E WifiHAL : Could not create handle --------- switch to system 03-13 17:47:56.882 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Failed or timed out awaiting driver ready 03-13 17:47:56.882 wifi 1022 1068 E vendor.google.wifi_ext-service-vendor: Failed to start legacy HAL: UNKNOWN --------- switch to main 03-13 17:47:56.882 1000 1407 1946 E WifiChipAidlImpl: configureChip failed with service-specific exception: android.os.ServiceSpecificException: unknown (code 9) 03-13 17:47:56.883 1000 1407 1946 E HalDevMgr: executeChipReconfiguration: configureChip error 03-13 17:47:56.883 1000 1407 1946 E HalDevMgr: Teardown Wifi internal state 03-13 17:47:56.883 1000 1407 1946 E WifiHalAidlImpl: Unable to call isStarted because IWifi is null. 03-13 17:47:56.883 1000 1407 1946 E WifiHalAidlImpl: Unable to call isStarted because IWifi is null. 03-13 17:47:56.883 1000 1407 1946 E WifiHalAidlImpl: Unable to call isStarted because IWifi is null. 03-13 17:47:56.883 1000 1407 1946 E HalDevMgr: createIfaceIfPossible: Failed to create iface for ifaceType=0, requestorWs=WorkSource{1000 com.android.settings} 03-13 17:47:56.883 1000 1407 1946 E WifiVendorHal: Failed to create STA iface 03-13 17:47:56.884 1000 1407 1946 E WifiNative: Failed to create iface in vendor HAL 03-13 17:47:56.884 1000 1407 1946 E WifiClientModeManager[247168:unknown]: Failed to create ClientInterface. Sit in Idle 03-13 17:47:56.884 1000 1407 1946 E WifiActiveModeWarden: ClientModeManager start failed!ConcreteClientModeManager{id=247168 iface=null role=null} 03-13 17:47:56.884 1000 1407 1946 D WifiScanRequestProxy: Sending scan available broadcast: false 03-13 17:47:56.885 1000 1407 1951 I WifiScanningService: Received a request to disable scanning, UID = 1000 03-13 17:47:56.885 1000 1407 1951 I WifiScanningService: wifi driver unloaded 03-13 17:47:56.886 1000 1407 1946 I WifiScanRequestProxy: Scanning is disabled 03-13 17:47:56.887 1000 1407 1946 I WifiCountryCode: No active mode, call onDriverCountryCodeChanged with Null 03-13 17:47:56.887 1000 1407 1946 I WifiNative: Vendor HAL died. Cleaning up internal state. 03-13 17:47:56.887 1000 1407 1946 E WifiActiveModeWarden: One of the native daemons died. Triggering recovery 03-13 17:47:56.893 1000 1407 1946 D WifiConfigStore: Writing to stores completed in 5 ms. 03-13 17:47:56.894 1000 1407 1946 E WifiSelfRecovery: Triggering recovery for reason: WifiNative Failure 03-13 17:47:56.894 1000 1407 1946 E WifiSelfRecovery: Already restarted wifi 10 times in last 1 hour. Disabling wifi 03-13 17:47:56.895 1000 1407 1946 D WifiAwareStateManager: disableUsageLocal: transactionId=23, mUsageEnabled=false 03-13 17:47:56.896 1000 1407 1946 I WifiService: Receive onDriverCountryCodeChanged to null, update available channel list
Update about my comment above, in case it helps anyone: I ended up reinstalling PixelOS, and the same issue appeared after a few hours. So in my case it was a hardware issue. I got a replacement, and the new Pixel 8 Pro works just fine after a couple days with GrapheneOS.
1 Like
This seems like it may be right, i.e. a hardware issue. I didn’t get any other ideas from the developers.
Relatedly, I did laptop maintenance (software: move corrupted / pirated Windows installs to Linux of course and also lots of hardware support) for some years, and this problem like you describe would show up occasionally: it is very hard to diagnose. But effectively as the main board warms up, it will very slightly expand meaning if there is a hairline crack in a solder joint the expansion will then break the circuit. Once it cooled down, it works as it contracts and makes contact again. Then you use it and in 30 minutes the failure occurs again.
Sorry to see the issue. Too late for a return?