Earbuds · Google
Google Pixel Buds Pro Won't Pair
If your Google Pixel Buds Pro refuse to pair or connect to your device, dirty charging contacts, a stale Bluetooth cache, or an incomplete factory reset are usually behind the issue.
Symptoms
- Pixel Buds Pro case LED blinks orange instead of bouncing white when pairing button is held
- Fast Pair notification fails to appear on Android devices when opening the case
- Buds connect briefly and instantly drop Bluetooth signal
- Only one Pixel Bud connects while the other stays silent or undiscovered
- Pixel Buds app shows earbuds as 'Disconnected' or offline
- Earbuds stay paired to an old device and refuse to switch to a new phone
Quick troubleshooting
Step 1
Clean Earbud Contacts and Case Pogo Pins
Inspect the brass contacts on the bottom of both Pixel Buds Pro and inside the charging case wells. Use a dry cotton swab or a swab lightly dampened with 90%+ isopropyl alcohol to remove earwax, oil, or lint. Both buds must make solid contact with the case pins for pairing mode to engage.
Step 2
Forget Device and Clear Bluetooth Cache
Go to your phone's Bluetooth settings and remove any entries for 'Pixel Buds Pro'. On Android, go to Settings > Apps > System Apps > Bluetooth and clear its cache and data. Restart your phone before trying to pair again.
Step 3
Perform a Manual Pairing Mode Trigger
Place both earbuds securely into the charging case and leave the lid open. Connect the case to a USB-C charger for at least 10 minutes. Press and hold the button on the back of the case for 3 seconds until the status light begins pulsing white, then scan for new devices on your phone.
Step 4
Execute a Hard Factory Reset on the Case
Dock both earbuds in the case with the lid open. Press and hold the back setup button for 30 seconds. Watch the status light: it will bounce white, then flash orange repeatedly; release the button once the light turns solid white. Once the light pulses white again, retry pairing.
Likely causes
- Dirty or oxidized charging pogo pins preventing the case from detecting both earbuds
- Depleted case battery unable to power the internal setup routine
- Corrupted Bluetooth cache or residual device bonding on the host phone
- Multipoint Bluetooth locked onto another nearby paired laptop or tablet
- Buds stuck in an unstable firmware loop requiring a hard case reset
- Hardware failure in an earbud's internal battery or the case setup button
What's going on
When your Google Pixel Buds Pro refuse to pair, the problem usually stems from a breakdown in communication between the earbuds, the charging case, and your host device. Google's seamless Fast Pair system relies on the charging case correctly detecting both earbuds via internal pogo pins before initiating a Bluetooth broadcast.
If the case cannot verify that both earbuds are seated, or if a previous host device is aggressively maintaining a Bluetooth Multipoint lock, the pairing handshake fails. Fortunately, most pairing lockups on Google Pixel Buds Earbuds can be solved without replacing hardware.
Symptoms people notice
- The case status LED flashes orange or stays dark when holding the rear setup button.
- Android Fast Pair pop-up card never appears when the case lid is flipped open.
- The earbuds appear in your phone's Bluetooth list but fail with a "Couldn't connect" error.
- Audio plays through only one earbud despite both being removed from the case.
- Pixel Buds Pro keep auto-connecting to a secondary device like a laptop instead of your primary phone.
Likely causes
- Dirty charging contacts: Corrosion or skin oils prevent the case from reading both earbuds as present.
- Stale host Bluetooth stack: Cached pairing keys on your smartphone or PC are corrupting the handshake.
- Low case power: The pairing routine demands stable voltage; a dying case battery aborts pairing setups.
- Interfering Multipoint connection: Active Bluetooth locks on other paired devices prevent entering discovery mode.
- Firmware state lock: An uncompleted background update left the internal microcontroller unresponsive.
Quick checks first
Before executing a full reset, check basic power and contact states:
- Plug in the case: Ensure the case is plugged into a functional USB-C cable and brick. Low-battery states often disable pairing broadcasts.
- Toggle Bluetooth: Turn off Bluetooth on your phone, wait 10 seconds, and turn it back on.
- Disable nearby devices: Turn off Bluetooth on your laptop, tablet, or secondary phone to break active Multipoint ties.
- Verify earbud seating: Drop each bud into the case and verify the LED briefly pulses to acknowledge contact.
When it's a real hardware fault
If cleaning the contacts and holding the rear button yields no LED response whatsoever—or if the case light rapidly blinks red constantly—you may be dealing with a broken physical button mechanism, a failed charging pin, or a dead lithium-ion cell in one earbud.
If one earbud completely fails to register inside the case (no status LED blink when inserted), that specific earbud's power management IC or battery has likely failed, preventing the pair from forming a unified connection.
Soft resets vs board/panel work
Because the Google Pixel Buds Pro are ultrasonically sealed units with an IPX4 water resistance rating, microscopic circuit work or battery replacement is not a practical DIY fix. Opening the earbuds or case shell almost always damages the outer plastic housing and destroys water seals.
- Soft & Hard Resets: Safe, non-intrusive software remedies that clear persistent configuration bugs and cache errors.
- Internal Micro-soldering / Battery Replacement: Not recommended for home repair. If factory resets do not clear the issue and contacts are pristine, the affected earbud or case must typically be replaced as a sealed module.
Next steps
If soft checks fail, perform the complete 30-second factory reset sequence outlined above. For broader issues related to single-earbud silence or power drops, browse our general earbuds troubleshooting section or check out our hardware breakdown guides in the reviews hub.
Next steps
Try the DIY guide if you're comfortable opening the device. Still stuck? Browse related problems for similar symptoms.

