Question
Country code Romania (RO) change kills the entire 6GHz band on Quest 3.
Setup: Quest 3 (Horizon OS v2.7, build 5243367.3520.520, updated 25 Aug 2026), ASUS TUF Gaming BE9400 in Access Point mode, dedicated 6GHz SSID, WPA3-SAE, PMF required, PSC channel 37 (6135 MHz), 80 MHz width, Bucharest area, Romania.
Reproduction, verified via adb:
- With adb shell cmd wifi get-country-code returning 00, the 6GHz network is visible in list-scan-results (BSSID on 6135 MHz, RSSI -38) and the headset connects successfully: WPA3-SAE completed, Wi-Fi standard 6, link speed 1200 Mbps, stable session.
- After a reboot the next day, get-country-code returns RO (learned from neighboring APs' 802.11d beacons — dense apartment building, 10+ ISP routers around). From that moment, all 6GHz BSSIDs disappear from list-scan-results at driver level, while the same SSID remains perfectly visible on a Samsung S23 Ultra (also Wi-Fi 6E) from the same spot. 2.4/5GHz SSIDs from the same AP still scan fine.
- adb shell cmd wifi force-country-code enabled 00 fails with SecurityException: Uid 2000 does not have access — so there is no user-accessible workaround, consistent with what OP found for AT.
Important regulatory context: 6GHz (5945–6425 MHz) has been legal for Wi-Fi in Romania since 6 March 2024, per ANCOM Decision no. 111/2024 (national radio frequency allocation table, aligned with EU decision 2021/1067). So the regdb entry disabling 6GHz for country code RO is simply outdated/incorrect.
Same root cause as reported for Austria (1360526) and for Egypt (thread 1381563). Three countries now confirm the same pattern.