Android Wifi Under the Hood
summary
Tracing a call from ConnectivityManager.requestNetwork to kernel reveals that a 0.1% race in driver and country‑code loading makes a car hotspot fall back to 2.4 GHz. Debugging uses logcat filtering for supplicant and hostapd, cs.android.com, adb root, and Wi‑Fi APIs like getUsableChannels. The fix is pragmatic: toggle station mode early to load the driver, poll getUsableChannels with retries to avoid a HAL crash, and then start the 5 GHz local only hotspot — solution works reliably at scale.
AI-written summary · about
chapters (11)
- 0:00Android Wi-Fi intro
- 3:34Why Android Wi-Fi matters
- 4:14Wi-Fi types and modes
- 8:53Wi-Fi frequencies explained
- 12:06Android Wi-Fi stack breakdown
- 15:16App to framework Wi-Fi
- 19:29Framework to HAL to kernel
- 23:28Country rules and Wi-Fi drivers
- 25:13Android Wi-Fi resources
- 25:34Wi-Fi AP startup issues
- 31:35Summary
related talks
41mHow ADB Wifi 2.0 works
22mWhat really happens when you connect to public Wi-Fi?
56mWi-Fi Direct To Hell: Attacking Wi-Fi Direct Protocol Implementations
30mThe Attacker Has Expensive Radio Equipment, But Your Android Phone Is Resilient
42mAndroid: Protecting the Kernel
22mPower optimization for Android
29mBuilding an Indoor Positioning App with Wi‑Fi RTT
54mExposing device features on 4G & 5G networks