You set up an old Android phone as a camera at the shop door or the front entrance. The picture looks fine on the shelf. Then you check the recording: the street outside is bright and clear, and the person who walked in is a dark shape with no face.
This is not a broken camera, and it is not low light. It is backlight, and it is one of the most common reasons a phone security camera records footage you cannot use.
Why do faces come out black on a phone security camera?
Short answer: the phone sets one brightness for the whole picture. If a bright doorway, window, glass shop front or sky fills a large part of the frame, the camera darkens everything to keep that bright area from turning white. The person standing in front of it is much darker than the background, so they drop to near-black. The fix is mostly placement: put the bright light behind or beside the camera, not behind the person, and keep bright areas small in the frame.
The rest of this guide explains why, shows the numbers, gives a 10-minute test, and (for developers) lists the Camera2 controls that affect it.
What the phone is actually doing
Every Android camera runs an auto-exposure routine (AE). Its job is to pick a shutter time and sensor gain so the picture is "correctly" bright. In Android's Camera2 API, when AE is on, Google's reference says it overrides the exposure time, sensitivity and frame duration the app asks for. The phone, not the app, decides.
To decide, AE measures the brightness of the scene. How each phone weighs the frame is the manufacturer's own algorithm, and it is not published. But the basic behaviour is the same everywhere: a large bright area pulls the whole exposure down.
Brightness in photography is counted in EV (exposure value). Android's own documentation puts it simply: one EV step doubles the image brightness, and minus one EV halves it. So:
| Difference | Brightness factor |
|---|---|
| 1 EV | 2× |
| 2 EV | 4× |
| 3 EV | 8× |
| 4 EV | 16× |
| 5 EV | 32× |
A sunny street seen through a shop door is easily several EV brighter than the shaded room inside. That is the gap the camera has to deal with.
A simple model of the problem
Real phones do not just average the frame, so treat this as an illustration, not a measurement of any phone. Imagine the phone averages brightness and sets the average to its target.
- 70% of the frame is the room (brightness 1).
- 30% of the frame is the doorway, 5 EV brighter (brightness 32).
The average is 0.7 × 1 + 0.3 × 32 = 10.3. To bring that average to the target, the camera darkens everything by about 10×. The room, and the person in it, end up at roughly one tenth of normal brightness, about −3.4 EV. That is a silhouette.
The same model with other numbers:
| Bright area of frame | Bright area is… | Room/person ends up at |
|---|---|---|
| 10% | 3 EV brighter | −0.8 EV (slightly dark) |
| 10% | 5 EV brighter | −2.0 EV (dark) |
| 30% | 3 EV brighter | −1.6 EV |
| 30% | 5 EV brighter | −3.4 EV (silhouette) |
| 50% | 5 EV brighter | −4.0 EV (silhouette) |
Two things stand out. Size matters: a small bright patch does little harm. Brightness gap matters: the same doorway at dusk is fine, and at noon it ruins the shot. That is why a camera can look perfect when you set it up in the evening and fail the next afternoon.
(These figures were computed with a short script for this article. They come from the simplified averaging model above, not from any real phone.)
Why "just make it brighter" is not enough
Many camera apps and phones offer exposure compensation (the +/− brightness slider). In the model above, +2 EV brings the room from −3.4 EV to about −1.4 EV. Better, but still dark.
And the doorway, which was already above target, goes from about +1.6 EV to about +3.6 EV: now the street is plain white. You traded a black face for a white background. With a strong backlight, the phone's sensor cannot hold both ends at once. Changing the brightness only chooses which end you lose.
So the real fixes are about light and position.
Fix 1: Put the light behind the camera, not behind the person
This is the single most effective change.
- Shop with a glass front: do not mount the phone at the back of the shop looking out at the street. Mount it near the front, high up, looking in toward the counter and the door from the inside edge. Customers walking in are then lit by the daylight coming through the glass, instead of standing in front of it.
- Home entrance: point the camera at the door from the side, not from the far end of a hallway with the door's window in the middle of the frame.
- Window: a window in the frame is a bright panel all day. Turn the phone so the window is at the edge of the picture, or out of it.
Fix 2: Make the bright area smaller
If you cannot move the camera, change what it sees.
- Tilt the phone down a little so less sky, street or doorway is in frame.
- Frame tighter on the area that matters: the counter, the cash drawer, the inside of the door.
- A curtain, a blind half-closed, or a tinted film on a glass door reduces the brightness gap. You are lowering the 5 EV, not fighting it.
Fix 3: Add light on the person's side
A cheap LED bulb or tube light inside the entrance, on the camera's side, lifts the face toward the background's brightness. Narrowing the gap by even 1–2 EV can turn a silhouette into a recognisable face. In shops this often costs less than any camera upgrade.
Fix 4: Test at the worst hour
A backlit camera fails at a particular time of day, so test then.
- Find the hour when the bright area is brightest: midday for a door facing the sun, late afternoon for a west-facing window, evening if headlights shine in.
- Start the recording and stand where a visitor would stand, facing the camera, for 30 seconds. Then walk in and out once.
- Stop and play the clip. Pause on your own face. Can you recognise yourself? Can you read printed text held at chest height?
- Change one thing (angle, tilt, light) and repeat. Keep the setup that passes.
Ten minutes at the worst hour tells you more than a full day of guessing. If the camera supports live view in a browser on your Wi-Fi, you can watch the result from another phone while you adjust, without touching the camera phone.
Does this work as an offline security camera without internet?
Yes. Backlight is about light and position, and none of these fixes need internet or a cloud service. A phone recording to its own storage on a local network, or fully offline, behaves exactly the same. The test above works with no data plan at all. If you are setting up a shop camera with no internet plan, see how to watch your shop with an old Android phone, no internet plan, no subscription.
For developers: the Camera2 controls involved
If you build camera apps, here is what Android's Camera2 reference says about the controls that touch this problem. All of this is from Google's public API documentation for CaptureRequest and CameraCharacteristics.
CONTROL_AE_REGIONS, metering areas. An app can tell AE which part of the frame to measure, using weighted rectangles. A region on the doorway's inside edge, or the counter, would tell AE to expose for the person rather than the street. Two catches:
- It is only available if
CONTROL_MAX_REGIONS_AEis greater than 0. The docs only guarantee at least 1 region on FULL-capability devices. On many older budget phones (often LEGACY or LIMITED), you may get zero metering regions. Check before relying on it. - The coordinates are in the sensor's active array, not your preview. The docs warn that if the preview aspect ratio differs from the crop region (for example 16:9 preview from a 4:3 sensor), you must account for the extra crop. Get this wrong and your region meters the wrong part of the scene.
CONTROL_AE_EXPOSURE_COMPENSATION, the brightness offset. Counted in steps of CONTROL_AE_COMPENSATION_STEP (often 1/3 or 1/2 EV). If CONTROL_AE_COMPENSATION_RANGE is [0, 0], compensation is not supported. For LIMITED and FULL devices that support it, the range must reach at least −2 EV and +2 EV; the docs say LEGACY devices may support a smaller range. After a change, AE can take several frames to settle. As shown above, compensation alone cannot rescue a strong backlight.
CONTROL_AE_LOCK, freezing exposure. Tempting: set it once when the scene looks right and lock it. For a 24/7 camera that is a trap. A lock keeps the exposure from one moment, and daylight changes for hours afterwards. A setting locked at noon will be far too dark at dusk. Support is reported by CONTROL_AE_LOCK_AVAILABLE, which is guaranteed true only on devices with MANUAL_SENSOR or BURST_CAPTURE capability.
The practical lesson for app developers matches the one for users: metering tricks help at the margin, but on old phones you cannot assume they exist, and no software setting removes a 5 EV gap. Placement guidance is worth more than an exposure slider.
Related: low light is a different problem from backlight. For dark scenes, see our correction on brightening live video in low light and why night footage looks smeary. If your frame looks narrower in the recording than in the camera app, that is video stabilization cropping the edges, which also changes how much bright area ends up in the shot.
Where Background Camera RemoteStream fits
Background Camera RemoteStream turns a spare Android phone into a camera that keeps recording with the screen off, stores the video on the phone itself (no cloud account needed), and can show the camera live in a browser on your own Wi-Fi. If you want people outside your Wi-Fi to watch live, it can stream to YouTube Live. Check the Play listing for which features are in the free version and which are in Pro.
Live view is useful for exactly this job: you can stand at the door and check on another phone whether your face is visible, then move the camera until it is. More setup guides: superfunicular.com.
What this guide does not tell you
- How your phone's auto-exposure weighs the frame. That algorithm is the manufacturer's and is not published. The table above is a simplified averaging model, not a measurement.
- Whether your phone supports metering regions or exposure compensation. That depends on the camera hardware level. The only reliable answer is to query the device.
- How a specific app uses these controls. This guide describes the Android API, not any app's internals.
Sources: Android Developers API reference, CaptureRequest (CONTROL_AE_MODE, CONTROL_AE_REGIONS, CONTROL_AE_EXPOSURE_COMPENSATION, CONTROL_AE_LOCK) and CameraCharacteristics (CONTROL_AE_COMPENSATION_RANGE, CONTROL_AE_COMPENSATION_STEP, CONTROL_MAX_REGIONS_AE, CONTROL_AE_LOCK_AVAILABLE), read on 31 October 2026. EV tables computed with a short script for this article.
Top comments (0)