A Pixel 8 Pro running Android 15 QPR2, tethered to a head unit via USB, drops frames hard every 90 seconds or so while roaming on a dual-SIM configuration. The map stutters, voice commands time out, and Spotify buffers mid-song. Switching to a single active SIM fixes it immediately. That pattern — dual-SIM roaming plus tethering equals Android Auto lag spikes — shows up repeatedly in bug reports on Google’s Issue Tracker and across Reddit threads dating back to late 2024. The root cause sits in how Android’s connectivity stack arbitrates between two radio interfaces while simultaneously serving a tethered downstream client.

The Dual-SIM Roaming Tether Problem in Android Auto

Android Auto relies on a stable data path between the phone and head unit. When the phone is also tethering its cellular connection — either via USB or Wi-Fi hotspot — the connectivity stack has to maintain two data sessions: one for the local Android Auto protocol traffic, and one for the upstream internet backhaul. On a single-SIM phone, this works fine. The radio stays on one network, the routing table is simple, and latency stays predictable.

The diagram above shows where the bottleneck forms. Dual-SIM devices running in DSDS (Dual SIM, Dual Standby) mode share a single modem’s radio resources between two subscriptions. When one SIM is roaming, the radio firmware periodically scans for better network candidates on that subscription. Each scan forces a brief interruption — sometimes just 50–80 milliseconds, but those interruptions stack. Android’s ConnectivityService detects the blip, re-evaluates the default network, and sometimes briefly marks the connection as “validated but degraded.” The tethering layer, which depends on the default upstream network, propagates that degradation downstream. Android Auto, sitting at the end of that chain, sees it as a latency spike or packet loss event.

The problem is worse on certain chipsets. Qualcomm’s Snapdragon modems handle DSDS scanning differently from Samsung’s Exynos or Google’s Tensor G-series (which itself uses a Samsung modem). The Pixel 8 and Pixel 9 lines, both using Tensor G3 and G4 respectively, seem particularly susceptible because their modem firmware is aggressive about neighbor-cell measurement reporting while roaming. Samsung Galaxy S24 devices with Snapdragon 8 Gen 3 show the same pattern but with shorter, less noticeable interruptions — around 30–40 ms per scan event instead of 70–80 ms.

How Android’s Network Stack Triggers the Lag

The lag isn’t random. It follows a predictable cycle tied to the roaming SIM’s network registration behavior. Android’s telephony framework, documented in the AOSP telephony architecture overview, manages each SIM subscription through a separate Phone object in the telephony service. Each Phone object maintains its own ServiceState, which tracks registration status, roaming indicators, and signal conditions.

When a SIM is roaming, the modem performs periodic Public Land Mobile Network (PLMN) searches to check whether a preferred or home network has become available. The 3GPP specification (TS 23.122) recommends these searches happen at intervals — typically every 6 minutes for manual mode and every 2–6 minutes for automatic mode, though OEMs tweak this. During each PLMN search on one SIM slot, the shared radio resources become temporarily unavailable to the other slot’s data session.

The Reddit threads captured above reflect real user experiences that line up with this technical explanation. Users consistently report the lag happens at regular intervals — not continuously — which matches the PLMN scan cycle. Several posters note that disabling the roaming SIM entirely (not just turning off data, but deactivating the SIM) eliminates the issue, which confirms the radio-sharing mechanism as the cause rather than any software-layer bug in Android Auto itself.

Here is the chain of events during a single lag spike:

1. The roaming SIM’s modem stack initiates a PLMN scan.
2. The shared radio switches context to scan neighboring cells on the roaming SIM’s frequency bands.
3. The data-active SIM’s connection stalls for 50–200 ms depending on chipset and band configuration.
4. ConnectivityService receives a NetworkCapabilities change callback from the telephony layer, potentially with the NET_CAPABILITY_NOT_SUSPENDED flag toggling.
5. The tethering module (TetheringService) re-evaluates its upstream network selection.
6. Packets queued for the Android Auto session either get delayed or, in worse cases, the TCP window collapses briefly.
7. Android Auto’s rendering pipeline stalls waiting for map tile data or media stream packets, producing a visible hitch.

The whole event takes under a second, but Android Auto’s rendering is sensitive to jitter. The protocol uses a tight timing window for frame delivery to the head unit display, and even 150 ms of added latency can cause a dropped frame or audio gap. When these events repeat every few minutes, the experience degrades from “slightly annoying” to “genuinely unusable,” especially for navigation where map continuity matters.

Diagnosing the Lag on Your Own Device

Before applying fixes, confirm that dual-SIM roaming is actually the cause. The symptoms overlap with other Android Auto issues — bad USB cables, underpowered head unit USB ports, or background app battery optimization killing the AA session.

The radar chart above compares lag severity across different tethering configurations. The dual-SIM roaming scenario produces dramatically worse results on every axis — latency spikes, jitter, packet loss, and reconnection frequency — compared to single-SIM or dual-SIM without roaming. That gap is the signature of the PLMN scan interference described above.

To confirm the diagnosis on your phone, try this sequence:

Step 1: Check your SIM status. Go to Settings → Network & internet → SIMs. If one SIM shows a roaming indicator (a small “R” or the word “Roaming” under the carrier name), that is the SIM triggering scans. Note which slot it occupies.

Step 2: Run a baseline test. Use Android Auto with tethering active for 10 minutes. Note any lag spikes, map freezes, or audio dropouts. Pay attention to whether they happen at roughly regular intervals.

Step 3: Disable the roaming SIM. Go back to SIM settings and toggle off the roaming SIM entirely — not just mobile data on that SIM, but disable the SIM itself. Repeat the 10-minute test. If the lag disappears, you have confirmed the cause.

Step 4: Check the system log (optional). For users comfortable with ADB, capturing a bug report during a lag event provides definitive evidence. Look for lines from ServiceStateTracker showing PLMN scan activity coinciding with ConnectivityService network re-evaluation events. The timestamps will correlate with the perceived lag spikes.

The breakdown above quantifies where the lag originates in each spike event. The PLMN scan itself accounts for the largest share, but the downstream cascade through ConnectivityService and the tethering stack adds measurable overhead on top of the raw radio interruption. This explains why the perceived lag is often longer than the modem scan duration alone.

Workarounds and Permanent Fixes

There is no single toggle that solves this without trade-offs. The fix depends on which SIM you need active and why.

Option 1: Set a preferred data SIM and disable roaming on the other. If you only need the second SIM for calls or texts while traveling, go to Settings → Network & internet → SIMs → [roaming SIM] → and toggle off “Roaming.” This does not disable the SIM — calls and texts still work on it when manually registered — but it tells the modem to stop performing automatic PLMN searches. The periodic scan cycle stops, and with it, the lag spikes. The downside: if your primary SIM loses coverage, the phone will not automatically fall back to the roaming SIM for data.

Option 2: Switch to DSDA mode if your hardware supports it. Some newer phones — including Pixel 8 Pro and Galaxy S24 Ultra — support Dual SIM, Dual Active (DSDA) mode, which uses two independent radio chains instead of sharing one. In DSDA mode, a PLMN scan on one SIM does not interrupt the other SIM’s data session. On Pixel devices, DSDA can be enabled through Settings → Network & internet → SIMs → “Use two SIMs at the same time.” Samsung devices may label this differently. Note that DSDA increases battery consumption noticeably — expect 15–25% more drain over a full day, which matters less when the phone is plugged into the car’s USB port anyway. Google’s DSDS/DSDA documentation for OEMs explains the architectural differences between the two modes.

Option 3: Use Wi-Fi tethering instead of USB tethering. This sounds counterintuitive — Wi-Fi adds another wireless hop — but it can actually help. When tethering over Wi-Fi, the phone’s hotspot creates a separate network interface that is somewhat buffered from the cellular upstream disruptions. The Wi-Fi link between phone and head unit (or a passenger’s device running AA wirelessly) maintains its own packet queue, which absorbs short-duration upstream stalls better than the USB tethering path does. The trade-off is slightly higher baseline latency and the need for a head unit that supports wireless Android Auto or a wireless AA adapter like the AAWireless dongle.

Option 4: Force manual network selection on the roaming SIM. Go to Settings → Network & internet → SIMs → [roaming SIM] → “Choose network” and manually select a carrier. When the network is manually selected, the modem stops performing automatic PLMN searches (since you have already told it which network to use). This eliminates the scan-induced interruptions entirely. The downside: if you drive into an area where that manually-selected carrier has weak coverage, the phone will not automatically switch to a stronger alternative. You would need to re-select manually.

Option 5: Use a travel eSIM instead of physical roaming. If the roaming SIM is a home-country SIM roaming abroad, replacing it with a local eSIM (from providers like Airalo or Holafly) that registers as a native subscriber on the local network eliminates roaming status entirely. No roaming means no PLMN searches, no radio interruptions, and no lag spikes. This is often the cleanest fix for international travelers using Android Auto with tethering. The phone treats the eSIM as a local connection, and the dual-SIM configuration behaves identically to a non-roaming setup.

The core issue — DSDS radio sharing during roaming PLMN scans — is a hardware and firmware constraint, not an Android Auto bug. Google is unlikely to fix it in a software update because the modem behavior is dictated by 3GPP standards and chipset vendor firmware. The realistic path forward is either avoiding the trigger condition (no roaming SIM active during tethering) or using hardware that supports true DSDA mode, which isolates the two radio paths completely. For anyone regularly using Android Auto while tethering on a dual-SIM phone abroad, Option 2 or Option 5 provides the most transparent fix with the fewest compromises.