FixFlow AI logoFixFlow AI
Back to guides
Devices
4 min read

When the Camera or Mic Won't Work in Calls

Call apps fail to use your camera or mic when permissions, the wrong default device, or another app hold the hardware.

Start FixWork All guides

At a glance

  • →Most call-camera failures are permissions or a competing app, not broken hardware.
  • →A physical shutter or mute switch is the easiest thing to overlook.
  • →Setting the right default device fixes silent-mic issues instantly.

Video-call apps don't own the camera or mic directly; they ask the operating system, which checks permissions and which app currently holds the device. If another app grabbed the camera first, the call app gets nothing.

Permissions drift. An update can quietly reset a camera or mic permission to off, so a setup that worked last week suddenly shows a black screen.

Default devices matter too. If the system defaults to a virtual or disconnected mic, the call app sends silence even though a real mic is present.

Common causes

  • Camera or mic permission denied to the call app
  • Another app still holding the camera from a previous call
  • Wrong default input or output device selected
  • Privacy shutter or hardware mute switch closed

Troubleshooting tips

  1. 1Check the physical shutter or mute switch on the device first.
  2. 2Confirm the call app has camera and microphone permissions in settings.
  3. 3Quit other video apps, then rejoin the call.
  4. 4Select the correct camera and mic inside the call app's settings.

Key takeaways

  • • Most call-camera failures are permissions or a competing app, not broken hardware.
  • • A physical shutter or mute switch is the easiest thing to overlook.
  • • Setting the right default device fixes silent-mic issues instantly.

Related problems

Camera or microphone does not work in calls

Related guides

5 min readWhy Video Calls FreezeFrozen faces and robot voices are almost always about upload speed and jitter, not download speed. 4 min readWhy Audio Stops WorkingSilence is usually the wrong output device, not a broken speaker.

Questions about this guide? Open FixBuddy in the corner — it answers from this page first, so most questions never leave your browser.