A laptop beside a meeting-room system can create echo when both connections capture and replay the same conversation. The second connection is not automatically harmless because it belongs to the same person. Decide which device supplies room audio before joining with another screen.
Keep one intended audio path
If the room system provides the microphone and speakers, avoid enabling a nearby laptop’s meeting audio as well. Google’s Companion mode is designed for a second-screen collaboration role with meeting microphone and speaker audio disabled. Use the room hardware to speak and listen while the laptop supplies supported chat, presentation, or activity controls.
Use ordinary echo controls when needed
If you need a normal personal connection instead, use headphones and select the intended microphone and output. Google’s troubleshooting guidance also recommends lowering speaker volume and muting when not speaking. Check for another connected device in the room rather than assuming the remote participant caused the echo.
Verify the room arrangement
Ask a remote participant whether the echo has stopped after changing one audio path. Check that the people physically present can still hear the meeting and contribute when required. A muted microphone alone may not prevent feedback if a second device’s speakers remain active near the room microphone. Companion mode is also distinct from simply turning off a camera; a normal connection can still transmit and receive audio. Keep an accessible alternative for someone who needs their own listening device. Before leaving, confirm whether the room hardware remains connected so a personal departure does not accidentally end the shared room’s participation.
References
- Troubleshoot video & audio quality in a meeting
- Use Companion mode for hybrid learning & collaboration
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.