Gemini Live not working: check access, camera, and audio

If Gemini Live is not working, first identify the surface: the Gemini mobile app and Gemini in Chrome have different entry points, access requirements, and sharing controls. Then test audio before adding camera or screen sharing, so you know which part is failing. fenbs can keep the checks and useful outcome, letting you continue the work on another device or in another AI without repeating the diagnosis.

Which Live experience are you trying to use?

1. On a phone or tablet, open the Gemini mobile app and tap Live or swipe left.
2. On a supported computer, use Gemini in Chrome through Ask Gemini > Go Live.
3. Test a short voice question before turning on any visual input.
4. Write down whether Live is missing, audio fails, or only camera or sharing fails. Work through the matching checks below.

Google’s mobile Live guide↗ (opens in a new tab) names the mobile app, while the Chrome Live guide↗ (opens in a new tab) documents its separate browser experience. Do not infer that ordinary Gemini web chat has Live simply because Gemini in Chrome does.

Keep the first test small. For example, ask for a short explanation of a familiar topic without showing private material. If voice works there, you can investigate visual input separately rather than changing account settings, camera controls, and sharing permissions all at once.

What if Live is missing or will not start?

For mobile Live, check that you are signed in with a personal or eligible work or school account and are using the mobile app. The US appears in Google’s mobile availability information, but that does not mean every account has identical access or that changing a permission will reveal every feature.

Google’s current mobile Live help contains conflicting age wording. Use the requirements shown for your account rather than assuming one definitive minimum from a general guide. The iPhone and iPad version↗ (opens in a new tab) also contains some Android-style wording, so follow actual iOS prompts rather than an Android notification path.

For Chrome, check that you opted in to Gemini in Chrome, are using up-to-date Chrome, and are signed into a supported profile. Google’s Gemini in Chrome guide↗ (opens in a new tab) lists supported access, including US availability, while noting rollout differences. Incognito and unsigned profiles are unsupported; work or school access requires administrator enablement, and Chrome Live is unavailable to users under 18.

If your account is managed, ask the administrator to confirm access before repeatedly changing personal settings. Distinguish an unavailable entry point from a permission refusal: the first is an access question, while the second gives you a specific permission to inspect.

What should you check when audio fails?

Start with the microphone and speaker access required for the surface you are using. Chrome Live explicitly requires microphone and speaker access, plus permission to use page content. Confirm that the intended access is allowed before retrying the same short voice question.

Separate the two directions of audio in your notes. “I can hear the answer, but it does not respond to my question” is different from “it appears to respond, but I hear nothing.” That distinction keeps you from treating every sound problem as the same failure.

• Check the permission prompt that is actually shown rather than looking for an assumed operating-system label.
• Use one simple question as the test and note whether it reaches the assistant.
• Check whether the failure happens before or after you add camera or sharing.
• Change one relevant setting at a time, then repeat the same test.

Do not treat muting as a privacy stop for visual input. Google documents that muting a mobile Live chat does not stop screen sharing. If you need sharing to end, use the sharing control itself and verify what remains active.

Why did the camera turn off?

In an active mobile Live chat, use Camera to start or stop the feed; introductory instructions also call the start control Turn on video streaming. Switch to rear or front camera changes the view. These documented mobile controls do not establish camera access in an ordinary desktop web chat.

The camera stops when Live is held, when you leave the Gemini app, or when the device locks. It resumes after you continue a held chat, but returning to the app or unlocking alone does not restart it. Check which event happened before assuming the camera is broken.

For the full camera workflow, use Gemini Live camera. When testing, show an ordinary object without names, account information, or confidential papers. Ask permission before including another person, and verify an important visual answer yourself.

Why did screen or tab sharing stop?

On mobile, putting Live on hold or locking the screen stops screen sharing, and you must start sharing again. Android also requires Live notifications for this feature. Use Turn on screen sharing and follow the device prompts; the mobile feature shares the full screen, so clear anything you do not intend to show.

In Chrome, the documented feature shares selected tab or page content. Share current tab starts that sharing, while Current tab or Pause sharing current tab pauses it. Add tabs and Manage tabs control the additional shared set. Navigating within a shared current tab changes the page Gemini sees; it does not give access to an unrelated desktop app.

Follow sharing a screen with Gemini Live for setup rather than mixing mobile and browser instructions. If only a connected app action fails, use Gemini Connected Apps to investigate that separate connection. A connected tool’s availability does not prove it can be used in Live.

What should you keep if the problem continues?

Write a short, factual account: device, mobile app or Chrome, personal or managed account, the exact symptom, the check you tried, and its result. Keep the visible error text when it is safe to do so. Leave passwords, tokens, and private material out of the record.

For example: “Mobile voice works; camera stopped after switching apps; starting the camera again restored it.” That is more useful than “Gemini is unreliable.” It describes a repeatable observation without turning one device’s behavior into a claim about every account.

If Live works but a later chat lacks an earlier fact, that is a different problem covered by Gemini memory not working. For choosing how to use the assistant beyond a Live session, see ChatGPT vs Gemini for research and Claude vs Gemini for programming.

How to keep the useful result with fenbs

Keep what you learned so the work can continue from exactly where you left off, on any device or in another AI. Save the tested fix and the next action, rather than making the next assistant repeat every failed experiment.

1. Create a free account.
2. Add a task with the problem you were trying to solve and the checks that worked.
3. Connect Gemini to fenbs using the connection guides. Gemini Apps custom connections require an eligible US personal account and web setup; this does not guarantee use inside Live.
4. Save the confirmed result, any uncertainty, and what you want to do next.
5. Ask the next connected assistant to read that record before continuing the work.

Google’s custom-app guide↗ (opens in a new tab) sets the eligibility requirements, including English, age 18 or older, and Keep Activity on; work and school accounts are excluded. fenbs cannot repair Live access or change device permissions. For a one-time permission check, your device’s own controls may be all you need.

The AI at work hub has more ways to keep useful results after a session ends. The small record matters most when troubleshooting interrupted something you still need to finish.