Camera2 API Torch Plus Camera Trick Android Devs Overlook

Short answer: The Camera2 API generally does not allow the system-level torch (flashlight) to be turned on via CameraManager while an active camera session holds the camera device; instead, you must enable a torch-like light by setting the preview capture request's FLASH_MODE to TORCH (and compatible AE_MODE) on the same camera session - otherwise attempts to use setTorchMode will fail on many devices due to exclusive camera ownership and vendor firmware policies.

Why simultaneous torch often fails

The Camera2 architecture gives a camera device exclusive control of hardware resources whenever an active CameraDevice session exists; trying to toggle the global torch with CameraManager.setTorchMode while that session is open commonly returns CAMERA_IN_USE or "torch not available" errors because the hardware resource is already reserved.

Hoe lang leven zwaarlijvige katten? Door dierenarts goedgekeurde feiten ...

Some vendors and Android releases enforce a strict separation between the per-session flash control (CaptureRequest.FLASH_MODE) and the system torch API (CameraManager.setTorchMode), which means a call to the global torch will be rejected when the camera device is bound, producing inconsistent behavior across phones and OS builds.

How Camera2 expects torch to be used

Camera2 was designed to let the active capture session control flash state through CaptureRequest parameters; to keep a continuous light while previewing, set CaptureRequest.FLASH_MODE to FLASH_MODE_TORCH and set CONTROL_AE_MODE to an AE mode that does not force flash (for example CONTROL_AE_MODE_ON) within the active capture session and submit a repeating request.

Using FLASH_MODE_TORCH inside the session avoids conflicts with CameraManager-level torch toggles and maintains correct auto-exposure behavior when capturing stills or video on that same session.

Device variability and vendor behavior

Device firmware and HAL implementations vary: some phones allow CameraManager.setTorchMode while a camera is open, many reject it, and certain devices only support torch via the camera session. This variability explains why the same app can run on one phone but fail on another due to different vendor firmware and HAL policies.

Historically, early Camera2 implementations (Android 5.0-7.x) exposed more inconsistencies; manufacturers progressively hardened resource ownership rules, so reports of "works on Pixel but not on Samsung" are common in developer threads and issue trackers.

Practical implementation steps

1. Open the CameraDevice and create a CaptureRequest.Builder with TEMPLATE_PREVIEW for your preview stream; this ensures you control the same session that uses the flash hardware preview request.
2. Set the builder's FLASH_MODE to FLASH_MODE_TORCH and set CONTROL_AE_MODE to CONTROL_AE_MODE_ON (avoid AUTO_FLASH AE modes that override FLASH_MODE).
3. Call cameraCaptureSession.setRepeatingRequest(builder.build(), ...) so the torch remains on during the active session and is managed by the camera device itself.
4. When you need the system torch (global), first close or release the CameraDevice and associated session so CameraManager can access the lamp; otherwise expect CAMERA_IN_USE errors on many devices.

Troubleshooting checklist

• Confirm you have CAMERA and FLASHLIGHT permissions declared and (for Android M+) granted at runtime; missing permissions cause unexpected errors. Permissions.
• Verify device capabilities via CameraCharacteristics before assuming torch availability; some camera IDs lack a controllable flash unit. CameraCharacteristics.
• Avoid using CONTROL_AE_MODE_ON_AUTO_FLASH or similar AE modes if you want persistent torch-use CONTROL_AE_MODE_ON plus FLASH_MODE_TORCH. AE mode.
• If you observe intermittent failures after cycling cameras, ensure sessions are properly closed and callbacks completed before toggling torch state. session lifecycle.

Compatibility table (illustrative)

Representative error messages

Common runtime messages reported in logs include "CAMERA_IN_USE" from CameraAccessException and kernel-level lines such as "setTorchMode: torch mode of camera X is not available because camera is in use", both indicating that the lamp is reserved by an existing camera user and the system API cannot claim it.

Edge cases and race conditions

Cycling between front/back cameras, rapidly opening/closing sessions, or attempting to set the global torch immediately after closing a session can trigger race conditions where the HAL state is still releasing the hardware; this yields intermittent failures reported in field issues and GitHub trackers (examples reported as recently as 2026). Race conditions.

Best-practice code pattern (concept)

Use a single camera session and control torch using CaptureRequest FLASH_MODE rather than CameraManager.setTorchMode while the camera is active; ensure AE mode and capture settings are consistent across preview and still-capture requests so the torch remains stable during captures and video. Code pattern.

Quotes and historical notes

"If you want to turn on the torch while the camera is open, then use the camera API's flash mode setting." - developer guidance widely cited since early Camera2 threads (2015-2019).

Camera2 was introduced in Android 5.0 (Lollipop) to replace the legacy Camera API and brought per-request flash control; since then, community experience and vendor HAL differences (2015-2026) have shaped the practical recommendation to prefer session-level torch control to avoid conflicts. Camera2 history

Recommended diagnostics and logging

Log CameraAccessException codes, monitor CameraManager torch callbacks, and capture camera session lifecycle events with timestamps; correlate "setTorchMode" failures with camera open/close events to identify whether the problem is a timing/race condition or a strict hardware policy. Diagnostics

Quick implementation checklist

• Use CaptureRequest.FLASH_MODE_TORCH within the active session for persistent light. Checklist item.
• Avoid AE modes that auto-fire flash when using TORCH. AE caution.
• Close the camera session before calling CameraManager.setTorchMode if you need the global torch. session closure.
• Check CameraCharacteristics for flash availability on the chosen camera ID. capability check.

When to use the global torch API

Use CameraManager.setTorchMode for app-wide flashlight features that do not require an open camera session (for example a simple flashlight app), but expect the call to fail while another app or your own app's CameraDevice has an active session; design the UI to reflect this by disabling global torch controls while capturing. Global torch

Final engineering recommendation

For robust cross-device behavior, treat the flash as a per-session resource when your app uses the camera: implement torch control via the active CaptureRequest, manage AE modes carefully, and only fall back to CameraManager.setTorchMode after releasing the CameraDevice; this pattern minimizes CAMERA_IN_USE errors and aligns with the majority of device implementations. Engineering recommendation

Key concerns and solutions for Camera2 Api Torch Plus Camera Trick Android Devs Overlook

Explore More Similar Topics

Hydrogen Sulfide Dangers: What Most People Underestimate

Read More →

Hydrogen Sulfide Smell: Probiotics People Swear By

Read More →

Probiotics For Sulfur Burps-what Experts Quietly Use

Read More →

Sulfur Gas Detection Tools Pros Trust In Real Jobs

Read More →

Best Natural Treatments For Intestinal Sulfur Odor Or Just Diet?

Read More →

Sulfuric Acid Gas Exposure First Aid-Did You Miss This?

Read More →