Fix Android 'Camera Error: Can't connect to the camera' After Update

Cause 1: Camera permission got revoked during the update

This is the one I see most often. Android updates — especially major version jumps like Android 13 to 14, or vendor patches on Samsung One UI 6 — sometimes reset app permissions. It's not supposed to happen, but it does. The update process rewrites the permission database, and if something interrupts that write, your camera app ends up with no access to the camera hardware. The app launches, tries to open the camera, gets a permission denied from the framework, and throws "Can't connect to the camera."

What's actually happening here is the Camera2 API returns ERROR_CAMERA_DISABLED or ERROR_CAMERA_IN_USE when the permission check fails. The app doesn't distinguish between "you didn't grant permission" and "the camera is broken," so you get the same generic error either way.

The fix:

1. Open Settings → Apps → find your camera app (Camera, or the third-party app throwing the error).
2. Tap Permissions → Camera.
3. Set it to Allow only while using the app. Don't pick "Ask every time" — that re-triggers the prompt and some apps mishandle the callback.
4. Force stop the app: Settings → Apps → [Camera App] → Force stop.
5. Relaunch.

If the permission toggle is greyed out, that's a different problem — usually a device admin policy or a corrupted app install. Uninstall and reinstall the app in that case.

Cause 2: Stale camera service or cache from the previous OS version

Android's camera stack runs as a system service (cameraserver) that talks to the hardware abstraction layer. When you update the OS, the old service can linger with cached state from the previous build. The new camera app calls into it, the service returns a stale handle, and the connection fails. This is especially common on Xiaomi MIUI and older Samsung builds where the camera HAL doesn't fully reinitialize after an OTA.

You don't need to factory reset. You need to clear the camera app's cache and data, then reboot. The reboot is what actually restarts cameraserver.

1. Settings → Apps → [Camera App] → Storage & cache.
2. Tap Clear cache first. Test the camera. If it works, stop here.
3. If it still fails, tap Clear storage (this wipes app settings, not your photos).
4. Reboot the phone. Not a soft restart — a full power off and on.

On Samsung devices, there's also a hidden camera service you can clear: Settings → Apps → tap the three-dot menu → Show system apps → Camera and Cameraserver. Clear cache on both.

If you're comfortable with ADB, this command restarts the camera service without a full reboot on most devices:

adb shell su -c "stop cameraserver && start cameraserver"

That requires root on most builds. On a stock Pixel or Samsung, just reboot.

Cause 3: Another app is holding the camera, or a bad update broke the HAL

Android only lets one app use the camera at a time (with rare exceptions for multi-camera on newer flagships). If a background app grabbed the camera and didn't release it — a video call app that crashed, a QR scanner left running, even a malicious app — your camera app will fail to connect. After an update, this gets worse because apps that were running before the reboot can restart in a weird state.

Check what's using the camera:

1. Open Settings → Privacy → Permission manager → Camera. You'll see every app with camera access.
2. Revoke camera permission from anything you don't actively use — social media apps, shopping apps, that flashlight app from 2014.
3. Reboot. This kills any process holding the camera handle.

If the error persists after all that, the update itself may have flashed a broken camera HAL. This happens on custom ROMs and occasionally on carrier-branded builds where the vendor blob doesn't match the new kernel. The tell: the stock camera app works but third-party apps fail, or vice versa. In that case, check for a follow-up OTA — Google and Samsung usually push a hotfix within a week or two. If you're on a custom ROM, reflash the matching vendor image.

One more thing: if you're using a work profile, the camera permission is managed separately. Check Settings → Work profile → Apps → [Camera App] → Permissions. I've seen this trip up people on MDM-managed devices for hours.

Quick reference

Start with the permission check. It takes 30 seconds and fixes the majority of cases. If that doesn't do it, clear the cache and reboot — the reboot is non-negotiable, because that's what actually restarts the camera service. Only after both of those fail should you suspect a deeper HAL problem.