When the flashlight on an Android phone stops working, the failure usually falls into one of three buckets: the LED itself cannot be activated, Android thinks the camera is already using the flash, or the phone is deliberately blocking the light because of its current state. The useful first step is therefore not a factory reset. It is to find out whether the flashlight and camera flash fail together.
This guide uses a symptom-first approach that works across Android brands, while calling out Samsung and Pixel differences where reliable documentation exists. Menu names can vary by manufacturer and software version.
First test: flashlight or camera flash?
Open Quick Settings and try the flashlight. Then open the stock Camera app, select a normal rear-camera photo mode, set flash to on rather than auto, and take a photo in a dim area.
If the camera flash works but the Quick Settings flashlight does not, the LED is capable of producing light and the problem is more likely to be a software state or flashlight-control issue. If neither works, continue with battery, camera, Safe Mode and hardware checks.
Samsung’s current support guidance uses the same separation: it recommends testing the camera flash when the flashlight fails, and testing the flashlight when diagnosing camera-flash trouble. Samsung also notes that the phone flashlight uses the camera flash rather than a separate lamp.
1. Close the camera and apps that may be using it
If the flashlight tile is disabled or Android reports that the camera is in use, fully leave the Camera app and close apps that can access the camera, such as video calling, QR scanning, social media or document scanning apps. Wait a few seconds and try the flashlight again.
Pixel community reports show a recognizable symptom where the flashlight is grayed out with a “Camera in use” message. Community reports are not proof of one universal cause, so do not assume a specific Pixel hardware defect from that message alone. Instead, use the camera test above and the Safe Mode test below to distinguish an app conflict from a broader camera/flash failure.
2. Restart the phone
A restart clears temporary camera and flash ownership states and is a low-risk next step. Samsung’s July 3, 2026 flashlight guidance explicitly recommends restarting when the flashlight does not work or turns off unexpectedly.
After restarting, test the flashlight before opening several camera-related apps. If it works immediately after boot but fails after a particular app is opened, that app becomes a strong suspect.
3. Check the battery level and power state
Charge the phone before deeper troubleshooting. Samsung states that on some Galaxy models the flashlight may be unavailable when battery charge falls below approximately 5% or 15%, depending on the device. That threshold is manufacturer-specific, so do not apply the exact Samsung percentages to every Android phone.
If the battery is very low, connect a charger, allow the charge level to rise, and retest. Also let an unusually hot phone cool before testing again; thermal protection behavior can differ by device.
4. Remove the case and inspect the flash area
A badly aligned or unusually thick case can physically cover part of the flash. Samsung specifically recommends removing the case when troubleshooting both flashlight and camera-flash problems. This is particularly relevant after changing cases or using a case designed for a slightly different model.
Inspect the rear flash window for dirt, adhesive film or physical damage. Cleaning the outside of the flash will not repair an electrical failure, but it can eliminate a simple obstruction.
5. Check whether the rear camera works normally
Open the stock Camera app and switch between front and rear cameras. If the rear camera also fails, shows an error, or cannot be selected while the flashlight says the camera is in use, treat the two symptoms as potentially related rather than troubleshooting the flashlight in isolation.
For a broader camera failure, use our Android Camera Not Working guide. If the camera works normally and only the flashlight fails, continue below.
6. Update Android and the camera app
Install stable system updates available for your device and update the stock camera app through the manufacturer’s supported store or Google Play where applicable. Samsung recommends checking both device and Camera app updates because software fixes can resolve flash-related faults.
If the problem began immediately after an update, do not assume the update permanently damaged the phone. Restart, test the stock camera and flashlight separately, and check whether a follow-up update is available before considering destructive recovery steps.
7. Test in Safe Mode
Safe Mode is one of the best ways to separate a third-party app conflict from a system or hardware problem. The exact way to enter Safe Mode differs by manufacturer, but Android devices generally disable downloaded third-party apps while leaving core system functions available.
Samsung’s current support flow recommends Safe Mode for a failed flashlight or flash. If the light works in Safe Mode but fails after a normal boot, a downloaded app is likely interfering. Remove recently installed or recently updated camera, flashlight, QR, video-call or device-control apps one at a time rather than deleting everything.
8. Galaxy users: compare flashlight and flash behavior
On Galaxy devices, Samsung documents a few model-specific details that can otherwise look like faults. Some devices disable the flashlight at very low charge, and camera flash behavior depends on the selected camera mode. Samsung also notes that flash is not available while shooting with the ultra-wide lens on some Galaxy configurations.
For diagnosis, use the standard rear photo mode and explicitly set flash to on. If the flashlight works but a third-party camera app does not flash, update or troubleshoot that app rather than assuming the LED is broken.
9. Pixel users: take “Camera in use” literally only as a symptom
Some Pixel users report a grayed-out flashlight tile accompanied by a “Camera in use” message even when no obvious camera app is open. Google Pixel Community threads document this symptom across multiple devices, but community posts are not an official diagnosis and can include different underlying causes.
The safest diagnostic sequence is: restart; test the rear camera; test the flashlight before launching third-party apps; try Safe Mode; then use Google’s camera troubleshooting/support path if both rear camera and flashlight remain unavailable. Avoid repeated factory resets merely because another user with a superficially similar symptom tried one.
10. When does hardware become more likely?
Hardware deserves more attention when the flashlight and rear-camera flash both fail across multiple apps, the rear camera also malfunctions, the problem remains in Safe Mode, stable updates are installed, and the phone has experienced a drop, liquid exposure or repair around the camera/rear cover.
A persistent failure after those checks is a better reason to use the manufacturer’s diagnostic or repair service than to install random flashlight utilities. A third-party flashlight app cannot repair a failed LED, camera module, connector or power circuit.
What not to do first
Do not factory-reset the phone as your opening move. Do not install several flashlight apps that request unnecessary permissions. Do not assume that a grayed-out tile proves the LED is dead, and do not assume that a working camera preview proves the flash hardware is healthy.
Instead, establish four facts: does the Quick Settings flashlight work, does forced camera flash work, does the rear camera work, and does the behavior change in Safe Mode? Those four checks narrow the problem far more efficiently.
Bottom line
If your Android flashlight is not working or is grayed out, first compare it with the camera flash, close camera-using apps, restart, charge the phone and remove the case. Then test the rear camera and Safe Mode. A flashlight that works in Safe Mode points toward a downloaded-app conflict; a flashlight and camera flash that both remain unavailable alongside rear-camera errors makes a system or hardware problem more plausible.
Start the conversation
Corrections, useful experiences and focused questions are welcome. Keep discussion respectful and on topic.