Symptoms
Headset shows paired, yet meetings and system sounds remain on internal speakers.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Headset shows paired, yet meetings and system sounds remain on internal speakers.
- Comparison to run: Test a system notification and a browser meeting while checking output selector.
- Pass condition: Test sound and meeting audio both route to the selected headset.
Why It Happens
A user session, managed school profile and Android container can have different access to the same hardware or files.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Paired device not chosen as output — investigate this first only if the local state or controlled comparison supports it.
- Bluetooth media profile unavailable — a second layer that may survive a simple restart and requires a targeted check.
- Meeting app overrides system audio — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Avoid deleting working pairings before recording how to reconnect an accessibility device. ChromeOS separates device capabilities, user-profile settings, Android app access and organization policy. A feature working in one profile does not prove the same permission exists elsewhere. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Test a system notification and a browser meeting while checking output selector. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Test a system notification and a browser meeting while checking output selector. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Select the headset in ChromeOS sound output settings. | This can expose or rule out paired device not chosen as output without changing several settings together. |
| Inspect the deeper layer | Inspect supported Bluetooth profile and whether microphone mode forces a switch. | Use the evidence to separate bluetooth media profile unavailable from meeting app overrides system audio; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether bluetooth media profile unavailable is consistent with the evidence. If not, investigate meeting app overrides system audio rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Headset shows paired, yet meetings and system sounds remain on internal speakers. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Test a system notification and a browser meeting while checking output selector. Do not erase logs or reset the device yet. Select the headset in ChromeOS sound output settings. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Choose the same output device in the meeting application's audio settings. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. Test sound and meeting audio both route to the selected headset. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider paired device not chosen as output, bluetooth media profile unavailable and meeting app overrides system audio separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Test a system notification and a browser meeting while checking output selector. Inspect supported Bluetooth profile and whether microphone mode forces a switch. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Compare headset behavior in guest session and after supported update. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. Test sound and meeting audio both route to the selected headset. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating paired device not chosen as output as certain before running the comparison: Test a system notification and a browser meeting while checking output selector.
- Trying several changes at once, such as modifying bluetooth media profile unavailable and meeting app overrides system audio simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Avoid deleting working pairings before recording how to reconnect an accessibility device.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
Test sound and meeting audio both route to the selected headset.
- Repeat the original failing action under equivalent conditions: Headset shows paired, yet meetings and system sounds remain on internal speakers.
- Run the control again: Test a system notification and a browser meeting while checking output selector.
- Check the positive pass condition: Test sound and meeting audio both route to the selected headset.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Inspect supported Bluetooth profile and whether microphone mode forces a switch. Compare headset behavior in guest session and after supported update.
Give Chromebook support the hardware model, ChromeOS version, whether the device is managed, and the exact difference between guest and affected profiles.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Test a system notification and a browser meeting while checking output selector.
- Preserve the corrected behavior: Test sound and meeting audio both route to the selected headset.
- Maintain ChromeOS updates through supported channels, eject external drives, and keep work or school device policies documented.
- Review configuration or hardware changes that could reintroduce paired device not chosen as output.
Frequently Asked Questions
Does this symptom prove paired device not chosen as output?
No. Start with the controlled comparison: Test a system notification and a browser meeting while checking output selector. Only treat paired device not chosen as output as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Inspect supported Bluetooth profile and whether microphone mode forces a switch. That helps determine whether bluetooth media profile unavailable or meeting app overrides system audio fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: Test sound and meeting audio both route to the selected headset. Keep a record of the working state for future troubleshooting.