Android Flashlight Permission: Does setTorchMode Need CAMERA?

Updated 10 min read

TL;DR

  • No. On Android 6.0+, CameraManager.setTorchMode() turns on the flashlight without CAMERA permission.
  • Flashlight apps that ask for CAMERA usually do so for legacy Android 5.x support, extra features like QR scanning, or overreach.
  • On Android 12+, a green privacy dot when the flashlight turns on means the app is opening the camera.
  • Safe-Life's flashlight uses setTorchMode() and never requests CAMERA.

No. On Android 6.0 (API 23) and later, CameraManager.setTorchMode()1 turns on the flashlight without any permission. android.permission.FLASHLIGHT still exists, but current Android flags it as removed and does not enforce it.

Below I go through Android's official APIs and platform design, then Google Play policy, EU law and Korean law, and real flashlight app privacy cases. Finally, I explain how the Safe-Life app uses permissions transparently.

Does a Flashlight Need Camera Permission?

What about the FLASHLIGHT permission?

A permission named android.permission.FLASHLIGHT exists, but in today's Android source it is a hidden permission kept "for backwards compatibility" and flagged as removed, so the system does not enforce it2. setTorchMode(), which turns the light on, requires no permission at all. android.permission.CAMERA, by contrast, is a Dangerous permission that needs explicit user approval3.

Modern Approach: No CAMERA Permission Needed

On Android 6.0 (API 23) and above, the CameraManager.setTorchMode() method can control the flash without CAMERA permission4.

In AOSP's CameraManager.java, openCamera() carries @RequiresPermission(android.Manifest.permission.CAMERA), while setTorchMode() has no @RequiresPermission annotation, so the API does not require CAMERA permission. The snippets below show only the two signatures, with the bodies left out.

// Signature from CameraManager.java (API 23+, body omitted)
public void setTorchMode(String cameraId, boolean enabled)
    throws CameraAccessException {
    // no @RequiresPermission annotation
}

In contrast, the openCamera() method explicitly requires CAMERA permission:

@RequiresPermission(android.Manifest.permission.CAMERA)
public void openCamera(@NonNull String cameraId,
        @NonNull final CameraDevice.StateCallback callback, @Nullable Handler handler)
        throws CameraAccessException {
    // Requires CAMERA permission
}

Why Do Some Flashlight Apps Request Camera Permission?

Despite camera permission being technically unnecessary, many apps still request it for these reasons:

  1. Older Device Support (Android 5.x and below)

    • Below Android 6.0 there is no setTorchMode(), so apps must open the camera (Camera1, or Camera2 on 5.x), which needs CAMERA permission
    • Requesting the permission lets an app support those older devices
  2. Additional Features

    • QR code scanning
    • Photo capture
    • Magnifier functionality
  3. Excessive Permissions

    • Developer's incorrect implementation
    • Data collection purposes
    • "Just in case" defensive coding

Important points:

  • Flashlight functionality itself does not require CAMERA permission
  • Granting camera permission doesn't automatically mean photos are being taken
  • What a flashlight app actually does depends on the app's code
  • So choose a trustworthy app that follows the principle of least privilege

The Relationship Between Flashlight and Camera Hardware on Android

On Android, the LED flash used for the flashlight is not treated as an independent device. The Android Open Source Project (AOSP) Camera HAL documentation defines it as "the flash unit associated with a given camera ID"5, so in Android's APIs the flashlight is always controlled as a feature of a specific camera.

How Your Phone Turns On the Flashlight

  1. The flashlight app asks the Android system to "turn on the flash"
  2. The Android system controls the flash through the CameraManager API4
  3. The LED flash attached to the camera module turns on

In step 2, the CameraManager.setTorchMode() method, available since Android 6.0 (API 23), turns on the flash without opening the camera device, but it still works through the camera management system4. No photo is taken, but the flash is part of the camera hardware.

The flashlight itself is simple, but an app asking for camera permission can confuse or worry users. That's why laws and app stores require apps to say clearly what they use permissions and personal data for.

Google Play Policy (platform rules)

Google Play's User Data policy requires apps to disclose how they access, collect, use, handle, and share user data6. Additionally, the Permissions and Sensitive Information policy states: "You may only request permissions and APIs that access sensitive information that are necessary to implement current features"7.

European Union: GDPR

The EU General Data Protection Regulation (GDPR) specifies:

  • Purpose limitation principle (Article 5(1)(b)): Personal data shall be collected for "specified, explicit and legitimate purposes" and not further processed in a manner incompatible with those purposes8.
  • Information obligation (Article 13): Data controllers have an obligation to inform data subjects (users) about the processing of their personal data9.

South Korea: Personal Information Protection Act

South Korea's Personal Information Protection Act, Article 3 (principles of personal information protection), requires the purpose of processing to be made clear, and Article 15 (collection and use of personal information) sets the conditions for collecting it10.

Additionally, according to the Korea Communications Commission's 'Smartphone App Access Permission Privacy Protection Guidelines' (2017), app service providers must clearly distinguish between essential and optional access permissions and inform users11.

Flashlight App Privacy Breach Case Study

In December 2013, the developer of "Brightest Flashlight Free," an app downloaded tens of millions of times, settled US Federal Trade Commission (FTC) charges that it deceived consumers. The FTC alleged that the app sent users' precise location and unique device identifier to third parties, including advertising networks, without disclosing this in its privacy policy. The app offered an option not to share that information, but according to the FTC the app was already collecting and sending it before users could accept the terms, which made the option meaningless. The final order was approved in April 20141213.

In Korea, in November 2014, a free flashlight app with 2 million Korean users was reported to hide 10 commands that took the user's location, SIM chip number and saved schedule, with the data sent to overseas advertising marketing servers. The same report said the most-used flashlight app in Korea, downloaded by 10 million people, also secretly collected location data14.

To prevent this, Korea added Article 22-2 (consent to access rights) to its Network Act in March 2016, requiring apps to tell users which access permissions are essential and which are optional and to get consent15. The 2017 'Smartphone App Access Permission Privacy Protection Guidelines' explain how to meet that obligation11.

What these cases show:

  • The problem was not the name of a permission but what the app did with the data it collected
  • Choose apps that say clearly why they use each permission and follow the principle of least privilege

Safe-Life: Flashlight Without Camera Permission

Safe-Life is an emergency preparedness app for disaster supply management and offline survival guides. Safe-Life's flashlight follows the principle of least privilege.

Safe-Life's Implementation

Technology Stack:

  • Flutter package: torch_light 1.1.0
  • Android API: CameraManager.setTorchMode() (API 23+)
  • Manifest permission: a single FLASHLIGHT line (not enforced on current Android)
  • Not requested: CAMERA

AndroidManifest.xml:

<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <!-- Does NOT request CAMERA permission -->
    <uses-permission android:name="android.permission.FLASHLIGHT" />
    <uses-feature android:name="android.hardware.camera.flash"
                  android:required="false" />
</manifest>

Safe-Life's Principles

  1. Minimum permissions: does not request CAMERA permission
  2. Single purpose: the flashlight tool only controls the light (steady or SOS flashing), with no camera features such as photo capture or QR scanning
  3. No data collection: never creates, stores or sends photos, videos or any other image data
  4. Transparency: the permissions it uses, and why, are listed in its privacy policy

Android 12+ Privacy Indicator: No Green Dot

Starting with Android 12, a green dot (Privacy Indicator) appears at the top of the screen when the camera or microphone is in use.

The dot reflects actual camera use, not whether an app holds the permission16.

  • An app that opens the camera to light the flash shows the green dot every time, even though it takes no photo.
  • Safe-Life never opens the camera; it only calls setTorchMode(), so no green dot appears when the flashlight turns on.
Android quick settings: the green camera and microphone indicator at the top right opens a list of the apps using them
Image: Android Open Source Project, Apache 2.0

Supported Android Versions

Safe-Life's minSdkVersion is 24 (Android 7.0 Nougat). That is above API 23, where setTorchMode() was added, so every supported device can turn on the flashlight without CAMERA permission.

Below is the flashlight screen in Safe-Life 2.2.0. You pick Light or SOS at the top and tap the round dial to turn it on or off. It works at once, without a camera permission request.

Safe-Life flashlight screen with Light and SOS modes and a lit round dial
Safe-Life 2.2.0 flashlight screen

How to Choose a Flashlight App

When choosing a flashlight app, check the following:

  1. Permission Request: Does it request CAMERA permission?

    • Does not request it: it follows the principle of least privilege
    • Requests it: check whether it has camera features you need, such as QR scanning, or supports Android 5.x and older
  2. Android 12+ Privacy Indicator Check: Does a green dot appear when turning on the flashlight?

    • Does not appear: the app is not opening the camera
    • Appears: the app is opening the camera, so check why
  3. Additional Features: Does it have QR scanning, photo capture, etc.?

    • Verify if you need these features
  4. Developer Transparency: Does it clearly disclose permission usage purposes?

    • Is it open source?
    • Does it have a clear privacy policy?

Frequently Asked Questions (FAQ)

Is there any risk of personal information leakage?

Safe-Life requests zero Dangerous permissions. Without CAMERA, LOCATION, READ_CONTACTS or RECORD_AUDIO, the app has no access to that kind of data.

How can I check and manage app permissions on Android?

You can check and individually allow or deny permissions used by each app in Android Settings > Apps > Permissions. On Android 12 and above, you can also view usage history of camera, microphone, and location permissions through the Privacy Dashboard.

Source dates are the publication dates each source gives: the FTC releases in US time, AjuNews in Korea time.

Footnotes

  1. setTorchMode() is a method that Android gives apps. It turns the flash on or off without opening the camera.

  2. AOSP core/res/AndroidManifest.xml - android.permission.FLASHLIGHT: "@hide We need to keep this around for backwards compatibility", permissionFlags="removed" (checked 2026-10-14)

  3. Android Permissions Overview - Explanation of differences between Normal and Dangerous permissions

  4. Android CameraManager API Reference - setTorchMode(String cameraId, boolean enabled) method sets the torch mode of the flash unit without opening the camera device (added in API level 23) 2 3

  5. Android Open Source Project: camera_module Struct Reference - "Turn on or off the torch mode of the flash unit associated with a given camera ID"

  6. Google Play: User Data Policy - Disclosure requirements for user data access, collection, use, and sharing

  7. Google Play: Permissions and APIs that Access Sensitive Information - "You may only request permissions and APIs that access sensitive information that are necessary to implement current features"

  8. GDPR Article 5: Principles relating to processing of personal data - Purpose limitation principle

  9. GDPR Article 13: Information to be provided - Data controller's obligation to provide information

  10. Personal Information Protection Act (Korean) - Article 3 (principles of personal information protection), Article 15 (collection and use of personal information)

  11. Korea Communications Commission: Smartphone App Access Permission Privacy Protection Guidelines (2017) - Specifies obligation for app service providers to distinguish between essential/optional access permissions 2

  12. FTC: Android Flashlight App Developer Settles Charges (December 5, 2013) - US FTC press release: "Brightest Flashlight Free" app developer (Goldenshores Technologies, LLC) settles FTC charges

  13. FTC: Final Order Approved (April 9, 2014) - FTC final order approval against flashlight app developer

  14. AjuNews: Free Flashlight Apps 'Serious Privacy Leaks' (November 7, 2014, Korean) - a flashlight app with 2 million Korean users hid 10 commands that extracted location, SIM number and schedules, sent to overseas ad marketing servers; the most-used app, downloaded by 10 million in Korea, also secretly collected location

  15. Act on Promotion of Information and Communications Network Utilization and Information Protection, Article 22-2 (Korean) - Korean Law Information Center, added 2016-03-22

  16. Android Open Source Project: Privacy indicators - shown when an app actually uses the camera or microphone via AppOpsManager.startOp/noteOp

A flashlight that never asks for your camera

Share