Camera trouble on Android, sorted by what you see
A black frame on a phone looks like a verdict on the whole evening, yet in my experience it is almost always one switch in one menu. Android guards the camera at two levels, one inside the browser and one in the system itself. When random cam chat refuses to start, the cause sits in one of those two, or in another app still holding the lens.
Best when nobody is watching the clock
A prompt that never shows up
Say you tap the start button and nothing happens: no question about permission, only an empty frame. Most likely an earlier tap on Block is to blame, made in a hurry on some forgotten visit.
Chrome has remembered that answer ever since, with a polite sort of stubbornness. Undoing it takes one trip to the right menu, because our chat only asks for access and the decision stays with whatever you answered last.
Undoing a blocked answer in three taps
Open the site controls
Tap the little icon just before the site's name in the bar on top, a padlock on some versions and a pair of sliders on others, then choose Permissions.
Flip both switches
Camera and Microphone each get a line of their own. Move whichever one says Blocked over to Allowed and touch nothing else.
Load the page afresh
Refresh and go through the start once more. The permission question should return, and this time the right answer is Allow.
Allowed in the browser, still black
Android adds a second gate above the first, since every app on the phone needs the system's consent, browsers included. Open Settings, scroll to Apps, tap your browser, then Permissions, and switch Camera to the option that allows it during use.
A related trap hides in links opened from inside a chat app or a social feed. Those often land in a small preview browser that never hands over the camera, so pick Open in browser from its menu and continue in Chrome or Firefox.
The not-supported message
An old browser sometimes lacks what live video needs and answers with a not-supported error, even when every permission is in order. Update it to the newest version, restart it, and try again before you suspect the phone.
Permissions set? Test them for real
Once the browser lets the camera through, the quickest proof is a short run of random cam chat on this phone.
The lens is busy elsewhere
A phone camera works for one app at once, and a forgotten one can hold it for hours. Think of the camera app you opened to check your hair twenty minutes ago, or a scanner, or a video call you believed was closed.
Pull up the list of running apps and swipe those off the screen, then reload. If the lens stays busy even then, restart the phone, the oldest remedy in the book and the least glamorous, and also the one that works most often.
Video works, sound does not
Image and audio are permitted separately, so a sharp picture proves nothing about the microphone. Return to the site controls from the first fix and confirm that Microphone reads Allowed.
Then glance at the bottom edge of the phone, where a finger or a snug case can quietly muffle the pickup. For a bigger screen, the page on setting up a laptop walks through similar checks on a computer, and a checklist for the first session is worth a minute too.
Final round before retrying
Tablets, menu names and a second browser
Does a Blocked answer wear off by itself?
Not on its own. It stays until you reverse it, which is why the same site fails in the same way until you do.
My menus use different names. Where do I look?
Phone makers rename things, and tablets follow the same pattern. Look for Apps or App permissions in Settings, then the browser, then Camera. The wording shifts, but the route does not.
Is it worth switching to another browser?
Sometimes. If Chrome refuses after every fix above, Firefox starts with no earlier Block on record, and trying it costs a few minutes.
Camera working? Come back in
Our home page has a short tour if you want one first. Otherwise go straight in, answer the usual camera prompt, and enjoy the first look at your own picture.