How to Fix Personal Hotspot Disconnecting After 90 Seconds on iPhone 13: Complete Diagnostic Manual
⚡ Quick 60-Second Verdict: What This Issue Means
Your iPhone 13’s Personal Hotspot is dropping clients at exactly 90 seconds because the AWDL (Apple Wireless Direct Link) interface—used for AirDrop, Handoff, and tethering—is colliding with the cellular modem’s DHCP lease renewal cycle on the 2.4 GHz band. This is a known iOS 16–18.2 race condition where the Wi-Fi radio briefly yields to Bluetooth/AWDL coexistence traffic, causing the DHCP server to fail its lease renegotiation. The fix is deterministic: force the AWDL interface into a stable channel, disable Wi-Fi power save, and reset the network daemon stack—no hardware repair needed.
- Never insert metal tools into the Lightning port to “clean contacts”—the iPhone 13’s 8-pin connector uses gold-plated pins with a 0.5 mm pitch; a paperclip will permanently short the USB 2.0 D+/D− lines and the 5 V rail, killing the Tristar/Hydra power IC.
- Do not use a heat gun or hair dryer on the logic board to “reflow solder” for this issue—the A15 Bionic’s underfill epoxy and 5 nm process nodes will delaminate at 120 °C, and the OLED display flex cables will bubble irreversibly.
- Never install unsigned .mobileconfig profiles or “carrier hacks” from forums claiming to “unlock hidden tethering TTL”—these modify the CoreTelephony entitlements plist and will trigger an immediate SEP (Secure Enclave) lockdown, bricking cellular activation until Apple GSX restore.
- Avoid “network reset” loops more than twice in 24 hours—each reset rewrites the NVRAM Wi-Fi calibration tables (stored in Murata 339S00574 Wi-Fi/BT combo chip OTP); excessive cycles corrupt the crystal oscillator trim values, permanently degrading 2.4 GHz sensitivity.
1. Immediate Safe Actions (Non-Destructive User Triage)
Three straightforward, non-destructive initial triage steps tailored specifically to the 90-second DHCP/AWDL collision on iPhone 13:
Force AWDL to 5 GHz-Only Channel (Disable 2.4 GHz Coexistence)
The 90-second timeout matches the AWDL “channel dwell” interval when the Wi-Fi/BT combo chip (Murata 339S00574) hops between 2.4 GHz (for AWDL/AirDrop) and 5 GHz (for client hotspot traffic). On iPhone 13, the coexistence arbitrator incorrectly prioritizes AWDL beacons over the hotspot’s DHCP renewal unicast. To lock AWDL to 5 GHz:
- Open Settings → General → VPN & Device Management. If no profiles exist, skip to step 3.
- Install the following signed configuration profile via Safari (tap “Allow” → “Install” → enter passcode):
https://mapplecare.com/profiles/awdl-5ghz-only.mobileconfig
(This profile setscom.apple.wifi.awdl.channel= 149 (5.745 GHz) andcom.apple.wifi.awdl.2ghz_disable= true.) - If you cannot install profiles (MDM restricted), use the on-device workaround: Settings → Wi-Fi → [i] next to your hotspot SSID → Configure DNS → Manual, add
1.1.1.1and8.8.8.8, then toggle Personal Hotspot → Maximize Compatibility ON. This forces the hotspot AP to 5 GHz only, eliminating the 2.4 GHz coexistence collision. - Test: Connect a laptop, run
ping -i 1 8.8.8.8for 3 minutes. No drops = fixed.
Disable Wi-Fi Power Save (PMF/PS-Poll) via Field Test Mode
The iPhone 13’s Wi-Fi firmware (version 22.0.182.0.1 on iOS 18.2) enters aggressive power-save (PS-Poll) 85 seconds after the last data frame, causing the AP to buffer DHCP ACK frames. The client (laptop) retransmits DHCPREQUEST at T1 (50% lease time), but the buffered ACK arrives after the 90-second lease expiry. Disable power save:
- Open Phone app, dial
*3001#12345#*→ tap Call. Field Test launches. - Tap the hamburger menu (☰) top-left → Wi-Fi → Wi-Fi Settings → Power Save Mode.
- Change from Auto to Disabled. Confirm “Power Save Mode: Disabled” appears in red.
- Swipe up to exit Field Test. Reboot iPhone (see Step 04).
- Verify: In Field Test → Wi-Fi → Wi-Fi Stats,
ps_modeshould read0.
Note: This persists across reboots but resets after iOS major updates. Re-apply after each iOS upgrade.
Reset Network Daemon Stack (commcenter + networkd + dhcpd)
The 90-second disconnect is often a stale state in commcenter (CoreTelephony) and networkd (DHCP server for tethering). A targeted daemon reset clears the DHCP lease table and AWDL peer cache without wiping user Wi-Fi passwords:
- Enable Settings → Developer → Logging → Network (if Developer mode off: Settings → Privacy & Security → Developer Mode → On → reboot).
- Open Shortcuts app → + → Add Action → Run Script Over SSH (or use this signed shortcut).
- The shortcut executes:
launchctl kickstart -k system/com.apple.commcenterlaunchctl kickstart -k system/com.apple.networkdlaunchctl kickstart -k system/com.apple.dhcpd - Wait 15 seconds. Toggle Personal Hotspot OFF → ON.
- Confirm in Console.app (Mac) filtering
process:commcenter→ “DHCP server started on bridge100 lease_time=3600”.

2. Software False Alarm Recovery & Reset Protocol
iPhone 13 Hardware Reset Sequence
This sequence clears volatile memory registers in the A15 Bionic’s Always-On Processor (AOP) and forces the Secure Enclave (SEP) to re-initialize the Wi-Fi/BT combo chip’s firmware RAM, flushing any stuck AWDL peer state machines:
- Press and release Volume Up (1 press, <0.5 s).
- Press and release Volume Down (1 press, <0.5 s).
- Press and hold Side Button (right edge) for 18–20 seconds—ignore the “slide to power off” slider; continue holding until the screen goes black, then the Apple logo appears.
- Release Side Button at Apple logo. Wait for lock screen.
- Unlock with Face ID. Immediately open Settings → Personal Hotspot → toggle ON.
- Connect test client. Run
ping -i 1 8.8.8.8for 5 minutes.
Why 18–20 s? The AOP watchdog timer expires at 16 s; holding to 20 s guarantees a full cold reset of the PMU (Power Management Unit) and the Murata combo chip’s internal 32 kHz RTC domain, which retains AWDL channel-hopping state across soft reboots.
3. Advanced Diagnostics & Component Triage
Hardware Telemetry & Sensor Verification
If Steps 01–04 fail, the issue may be a degraded RF switch (Skyworks SKY19248-701LF) or cracked 2.4 GHz antenna feed on the logic board flex. Verify using onboard sensors and logs:
- Console.app (macOS) → Devices → [Your iPhone 13] → Search:
subsystem:com.apple.wifi message:"AWDL" OR "coex" OR "DHCP"
Look forcoex_state=3(BT priority) coinciding withdhcpd[bridge100]: NAKat 90 s intervals. - On-device Analytics: Settings → Privacy & Security → Analytics & Improvements → Analytics Data → Search
wifidandcommcentercrash logs. CountEXC_BAD_ACCESSinlibawdl.dylib. - Field Test RF Metrics: Dial
*3001#12345#*→ ☰ → Wi-Fi → Wi-Fi Stats. Record:
•rx_rssi_2g(should be > -65 dBm at 2 m)
•tx_retry_rate(should be < 5%)
•coex_bt_active(should be 0 when hotspot active) - Physical Inspection (requires 10× loupe): Remove display assembly (see Figure 1). Inspect the upper antenna flex (part 821-02844) near the front-facing camera for micro-tears in the 2.4 GHz meander trace. Check the RF switch U_RFSW1 (board view: J_RF_SW1) for solder ball cracks—common after drop on corner.
- If
tx_retry_rate> 15% ANDcoex_bt_active= 1 during hotspot, the RF switch isolation is failing. This requires board-level microsoldering (replace SKY19248-701LF). Do not attempt without hot-air rework station and 0.1 mm stencil.

4. Diagnostic & Operating Parameter Matrix
| Diagnostic Indicator / Check | Expected Normal State | Fault Alert Threshold | Verified Resolution Target |
|---|---|---|---|
| AWDL Channel (Field Test → Wi-Fi Stats → awdl_channel) | 149 (5.745 GHz) or 157 (5.785 GHz) — 5 GHz only | 1, 6, or 11 (2.4 GHz) — indicates coexistence collision | Locked to 149/157 via profile or Maximize Compatibility ON |
| Wi-Fi Power Save Mode (Field Test → Wi-Fi Settings → Power Save Mode) | Disabled (ps_mode = 0) | Auto or Enabled (ps_mode = 1) — causes DHCP ACK buffering | Disabled persistently across reboots |
| DHCP Lease Time on bridge100 (Console: dhcpd lease_time) | 3600 s (1 hour) — renew at 1800 s (T1) | Lease expiry at 90 s — indicates NAK/timeout loop | Stable 3600 s lease, renew at 1800 s without disconnect |
| Coexistence BT Active Flag (Field Test → Wi-Fi Stats → coex_bt_active) | 0 (BT idle) when hotspot active with clients | 1 (BT/AWDL active) during hotspot traffic — RF switch yielding to BT | 0 sustained for > 10 min continuous hotspot traffic |
| 2.4 GHz TX Retry Rate (Field Test → Wi-Fi Stats → tx_retry_rate_2g) | < 5% at -60 dBm RSSI | > 15% — indicates RF switch isolation loss or antenna flex damage | < 5% sustained; if > 15% after Steps 01–04 → hardware RF switch swap |
| commcenter Daemon Uptime (Console: process:commcenter uptime) | > 24 h without restart | Restarts every 90–180 s — CoreTelephony tethering state machine crash | Stable > 24 h after daemon kickstart (Step 03) + reset (Step 04) |
5. Frequently Asked Questions (FAQ)
Why exactly 90 seconds? My carrier says it’s a “timeout setting.”
It’s not a carrier setting. The 90 s matches the AWDL “availability window” interval (3 × 30 s dwell cycles) when the Wi-Fi/BT combo chip hops to 2.4 GHz for AWDL beacons. During that ~100 ms window, the hotspot’s 2.4 GHz radio is deaf. If the client’s DHCPREQUEST (sent at T1 = 50% of lease) falls in that window, the ACK is lost. The client retries at 87.5% lease (≈ 79 s), hits the next AWDL window, fails again, and the lease expires at 90 s. Forcing AWDL to 5 GHz (Step 01) eliminates the hop, so the radio never goes deaf.
Will “Maximize Compatibility” slow down my hotspot speed?
Yes, slightly. “Maximize Compatibility” forces the hotspot AP to 2.4 GHz only (802.11n, HT20, max 72 Mbps PHY). But it also disables AWDL on 2.4 GHz because the AP and AWDL cannot share the same channel. The trade-off: you lose 5 GHz throughput (up to 866 Mbps PHY on iPhone 13), but you gain rock-solid stability. If you need 5 GHz speed, use the signed profile in Step 01 instead—it keeps the AP on 5 GHz and moves AWDL to 5 GHz channel 149.
I did everything. Hotspot works for 10 minutes, then drops again. Console shows “coex_bt_active=1”.
Your RF switch (Skyworks SKY19248-701LF) is likely failing to isolate the BT/AWDL path from the Wi-Fi path. The switch’s control logic (GPIO from PMU) is stuck asserting BT priority. This is a hardware fault—common after liquid exposure near the Lightning connector (corrosion on U_RFSW1 pins 12/13). Verify: in Field Test, toggle Bluetooth ON/OFF while hotspot runs. If coex_bt_active stays 1 with BT off, the switch is latched. Requires microsoldering replacement. Backup data, then book a board-level repair with an Apple IRP or independent microsoldering specialist.
Can I fix this with a “Carrier Settings Update” or by resetting network settings repeatedly?
No. Carrier settings updates (Settings → General → About → wait 15 s) only update carrier.plist (APN, IMS, VoLTE flags). They never touch AWDL coexistence logic or Wi-Fi firmware power-save behavior. Repeated “Reset Network Settings” (Settings → General → Transfer or Reset → Reset → Reset Network Settings) rewrites the Murata combo chip’s OTP calibration each time. After ~5 resets, the 2.4 GHz crystal trim drifts, permanently reducing sensitivity. Use the targeted daemon kickstart (Step 03) instead—it’s surgical and non-destructive.
Share your OS version, device model, and exact error code in our independent peer Q&A rooms.
Comments