Direct answer
For the Google Pixel 7, accessory pairing state, competing hosts, profile support and radio issues should be isolated. First, forget the accessory on other hosts and pair nearby with both devices charged.
What this covers
- Google Pixel 7 (GVU6C/GQML3)
- Google Pixel family; Tensor generation, fingerprint/face unlock, modem and Pixel Feature Drop eligibility vary.
- The specific fault this record addresses: will not pair or stay connected over Bluetooth
What it does not cover
- ×The same symptom on a different Google product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The accessory is already connected to another device
What separates it It will not appear in the scan, or connects and immediately drops. Most accessories hold one active connection and reconnect automatically to whatever they saw last.
How to confirm Disable Bluetooth on every other device that has ever paired with it — a tablet in a drawer and a laptop in a bag both count. This is the most common cause by a wide margin.
- 2
The accessory is not actually in pairing mode
What separates it It is on and the phone cannot see it. Powered on and discoverable are different states, and the button sequence differs between generations of the same product.
How to confirm Follow the manufacturer's documented pairing sequence and watch for the indicator that confirms pairing mode, rather than assuming it from the device being on.
- 3
A stale pairing record on the phone
What separates it It used to work and now fails, or connects without audio. The record survives when the accessory's side has been reset or updated.
How to confirm Forget the device on the phone and pair fresh. Do this on both ends where the accessory supports it, because a one-sided forget leaves the same mismatch.
- 4
The accessory has low charge
What separates it It fails to pair or drops repeatedly, and works after charging. Radio negotiation costs more than the indicator light does.
How to confirm Charge the accessory fully before troubleshooting anything else. Intermittent pairing on a part-charged accessory is very common.
- 5
Too many stored pairings
What separates it A new device will not pair while older ones still work. Accessories have finite pairing memory, and the oldest is not always dropped gracefully.
How to confirm Clear the accessory's pairing list using its documented reset. This is an accessory-side limit that the phone cannot report.
- 6
Interference on 2.4 GHz
What separates it Audio stutters in specific places — near a microwave, a busy Wi-Fi router, or in a crowded space — and is clean elsewhere. Bluetooth shares the band with Wi-Fi and much else.
How to confirm Test in a quiet radio environment. Location-dependent stutter is interference, not a pairing fault.
- 7
The body is the obstruction
What separates it Audio cuts out when the phone is in a back pocket or on the opposite side of the body from the accessory. Bluetooth is low-power and the human body absorbs 2.4 GHz effectively.
How to confirm Move the phone to the same side as the accessory and retest. This explains a large share of 'drops while walking' reports.
- 8
A profile mismatch rather than a connection failure
What separates it It connects but audio comes from the wrong place, or the microphone does not work, or media plays and calls do not. Bluetooth carries separate profiles for media, calls and control.
How to confirm Check the per-device profile settings on the phone. Connected-but-wrong is a profile problem and no amount of re-pairing fixes it.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Every other device that has ever paired with this accessory, including ones not currently in use.
- Whether it fails to appear at all, appears and fails to connect, or connects and then misbehaves. Those are three different failures.
- The accessory's charge level at the time.
- Whether it works with a different phone, and whether a different accessory works with this phone — that cross-test isolates which side is at fault.
- Whether the problem is location-dependent, which separates interference from pairing.
- Where the phone was on the body when audio dropped.
- Whether media works while calls do not, or the reverse, which points at profiles rather than at the connection.
Turn off Bluetooth on every other device that has paired with it
ReversibleMost accessories hold one active connection and silently reconnect to whatever they saw last. A tablet in a drawer or a laptop in a bag will take the accessory back the moment it powers on, and the phone simply never sees it. This is the most common cause here by a wide margin.
Put the accessory into pairing mode deliberately
ReversiblePowered on and discoverable are different states, and the button sequence differs between generations of the same product. Watch for the indicator that confirms pairing mode rather than assuming it from the device being awake.
Charge the accessory fully before anything else
ReversibleRadio negotiation draws far more than the indicator light does, so an accessory with enough charge to blink may not have enough to complete a pairing. Intermittent pairing on a part-charged accessory is extremely common and costs an hour to exclude properly.
Forget the device on the phone and pair fresh
Signs you outA stored record that no longer matches the accessory's side produces a connection that fails or connects without working. Where the accessory supports it, clear its side too — a one-sided forget leaves exactly the mismatch you were trying to remove.
Cross-test with another phone and another accessory
ReversibleAccessory works with another phone, and another accessory works with this phone: that pair of results isolates the faulty side definitively, where any amount of single-sided fiddling only produces inference.
Separate connection failure from profile failure
ReversibleConnected but audio in the wrong place, or media working while calls do not, is a profile problem — Bluetooth carries media, calls and control separately. Re-pairing does not fix a profile mismatch, and the per-device settings do.
Test in a different radio environment
ReversibleBluetooth shares 2.4 GHz with Wi-Fi, microwaves and much else. Stutter that appears in one place and not another is interference rather than a pairing fault, and no re-pairing will change it.
Move the phone to the same side of the body as the accessory
ReversibleBluetooth is deliberately low-power and the human body absorbs 2.4 GHz effectively. A phone in a back pocket, on the opposite side from an earbud, is a genuine obstruction — and it explains most 'cuts out while walking' reports.
Clear the accessory's own pairing list if a new device will not join
Reset / data riskAccessories have finite pairing memory and do not always drop the oldest entry gracefully. This is an accessory-side limit the phone cannot see or report, and its documented reset is the only way to clear it.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- GVU6C/GQML3. Google Pixel family; Tensor generation, fingerprint/face unlock, modem and Pixel Feature Drop eligibility vary.
- Tier — base flagship (Tensor G2, no telephoto)
- The Pixel 7 — Tensor G2, main + ultrawide (no telephoto), stock Android with Pixel AI. Older flagship nearing its 5-year update-window end.
- Pixel AI + Tensor
- Pixel-exclusive AI; Tensor G2 runs warm under load — normal.
- eSIM
- Supports eSIM; connectivity issues are carrier/eSIM first.
- Connector
- USB-C. A cable that fits is not necessarily a cable rated for this phone's charging speed — USB-C carries several power profiles and a cable built for data will charge slowly or intermittently while seating perfectly.
- Biometric
- An in-display fingerprint reader, which looks through the screen. A thick or incompatible screen protector genuinely interferes with it, which is why unlock reliability often changes the day a protector is fitted rather than gradually.
- SIM
- Carries an eSIM. An eSIM does not travel with the handset the way a plastic SIM does: a phone swap, a factory reset or a repair can leave the profile behind, and restoring it is a carrier action rather than a phone setting.
- Modem
- 5G capable. In marginal 5G coverage the phone hands repeatedly between 5G and LTE, which costs more battery and generates more heat than settling on either — so the preferred-network setting is a real diagnostic lever rather than a preference.
- Charging
- Supports wireless charging. Coil alignment is tighter than it looks and a thick case, a metal plate or a card in the case defeats it entirely — so wireless charging failing while cable charging works is usually the case rather than the phone.
- Water resistance
- Rated water resistant, which is not waterproof and which degrades with age, drops and seal disturbance. The rating covers incidental exposure; it is not a guarantee, and moisture-detection warnings are deliberately conservative and can persist after the port feels dry.
- Platform
- Android, with a manufacturer interface layer over it. Battery optimisation and background-execution restrictions are applied per app and are far more aggressive than on iOS — which is why 'set this app to unrestricted' is a real fix here and has no equivalent elsewhere.
- Symptom boundary
- This record covers Google Pixel 7 when it will not pair or stay connected over Bluetooth. A different symptom on the same hardware, or this symptom on a different Google product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !The accessory fails with every phone and the phone works with every other accessory — that is the accessory, and its own support path applies.
- !The phone fails with every accessory including newly reset ones, which points at the phone's radio.
- !Bluetooth stopped working entirely after a drop or liquid exposure.
- !A car's built-in system is involved and the vehicle's own pairing list is full or cannot be cleared without the dealer.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Pixel Help publishes this as "Fix Bluetooth problems". Google's Bluetooth pairing and connection article. Probed 2026-08-23 14:37, before the help-centre crawl tripped Google's rate limit: title-verified. What that article does not carry is the model boundary — it is written for a product line, and GVU6C/GQML3 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My Pixel 7 fingerprint reader often fails to unlock.+
The Pixel 6/7 under-display fingerprint sensor is known for being slower and less reliable than a physical reader. Delete and re-enrol your fingerprint (enrolling the same finger twice helps), press firmly and fully on the sensor, keep the screen clean, use a sensor-friendly screen protector, and stay updated. Face Unlock (added via update) is an alternative for convenience. It is a characteristic of these models rather than a one-off fault.
My earbuds will not show up on my phone.+
Turn off Bluetooth on everything else that has ever paired with them — a tablet in a drawer, a laptop in a bag, a second phone. Most accessories hold a single connection and reconnect automatically to whatever they last saw, so the phone genuinely never gets a chance to see them.
It connects and then immediately disconnects.+
Two usual causes: another device is taking it back, or the accessory does not have enough charge to sustain the connection. Both are quick to exclude — turn off Bluetooth elsewhere, and charge the accessory fully — and between them they cover most of these.
It paired fine before and now it will not.+
Forget the device on the phone and pair fresh, and clear the accessory's side too if it supports that. A stored pairing record that no longer matches the other end is the classic 'worked yesterday' cause, and it appears after accessory resets and firmware updates.
The audio cuts out when I walk.+
Check where the phone is. Bluetooth is deliberately low-power and the human body absorbs 2.4 GHz well, so a phone in a back pocket on the opposite side from an earbud is a real obstruction. Moving it to the same side is often the whole fix.
It connects but there is no sound.+
That is a profile problem rather than a connection one. Bluetooth carries media, calls and control as separate profiles, and a connected device can have the wrong one selected or disabled. Re-pairing will not fix it; the per-device profile settings will.
My car will not pair with a new phone.+
Car systems have small pairing lists and frequently need an old entry deleted before a new one will fit. Clearing the vehicle's list is the fix, and it is done from the car rather than from the phone.
Audio stutters near my microwave.+
Bluetooth shares the 2.4 GHz band with microwaves, Wi-Fi and a great deal else. Stutter that appears in one place and disappears in another is interference — it is not a pairing fault and no amount of re-pairing addresses it.
How do I work out which side is broken?+
Cross-test. Try the accessory with another phone, and another accessory with this phone. Those two results together isolate the faulty side definitively, where changing settings on one device only ever produces inference.
Should I reset network settings to fix Bluetooth?+
Only as a last step. It clears every Bluetooth pairing on the phone along with every saved Wi-Fi network and VPN profile. Forgetting the single problem device achieves almost all of the benefit at a fraction of the cost.
Does Bluetooth drain the battery?+
Very little on its own — modern Bluetooth is low energy by design. What costs battery is what is being streamed over it, and an accessory that repeatedly disconnects and reconnects, because the reconnection is the expensive part.
Does this answer apply to every Google model?+
No. It is scoped to GVU6C/GQML3. Google Pixel family; Tensor generation, fingerprint/face unlock, modem and Pixel Feature Drop eligibility vary.
What should I record before troubleshooting Bluetooth or pairing?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing Bluetooth, pairing. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Stop for swollen/hot accessories or damaged charging hardware.
Answer for the exact device and software version shown above.