How to Enable Bluetooth Permission on Android | OS-Specific Fix

Bluetooth permission on Android requires a different settings path depending on whether your device runs Android 12 and newer or an older version.

One wrong tap leaves your app unable to find nearby devices, and the fix for how to enable Bluetooth permission on Android depends on one thing: which OS version you’re running. Android 12 moved Bluetooth options out of Location into a dedicated Nearby devices toggle, while older versions still tie scanning to Location access. This guide covers both paths and the mistakes that block them.

What Changed in Android 12?

Android 12 (API level 31) introduced three granular Bluetooth permissions — BLUETOOTH_SCAN, BLUETOOTH_CONNECT, and BLUETOOTH_ADVERTISE — that are no longer tied to the Location permission. Apps targeting Android 12+ declare these in their manifest and present a Nearby devices permission category in Settings instead of Location. For older Android versions, the old ACCESS_FINE_LOCATION permission still controls Bluetooth discovery. This split is the single biggest source of confusion.

How to Enable Bluetooth Permission on Android 12 and Newer

This path works on any device running Android 12 or later — Samsung Galaxy S24, Google Pixel 8, and most phones from 2022 onward. The permission lives under a dedicated Nearby devices section.

1. Open the Settings app on your device.
2. Tap Apps > All Apps (labeled See all apps on some devices).
3. Select the app that needs Bluetooth access — for example, iHeartRadio or Muse.
4. Tap Permissions.
5. Select Nearby devices. This is the new Bluetooth-permission section introduced in Android 12.
6. Toggle the Allow radio button to grant permission.

the app can now discover and connect to Bluetooth devices without touching Location settings.

How to Enable Bluetooth Permission on Android 11 and Older

Devices running Android 11, 10, or 9 — including the Google Pixel 2 and Samsung Galaxy S8 — still route Bluetooth scanning through Location. The steps are nearly identical, but the final setting differs.

1. Open Settings > Apps and select the target app.
2. Tap Permissions.
3. Select Location — not Nearby devices, which does not appear on these OS versions.
4. Choose Allow when using app to enable Bluetooth scanning.

the app can scan for Bluetooth devices while it is open. Background scanning may require a different permission level.

What About Samsung and Pixel Devices?

Samsung Galaxy and Google Pixel phones follow the same OS-version rules, but their Settings menus sometimes use slightly different labels. On a Samsung Galaxy S8 running Android 8, the path is Settings > Apps > [App Name] > Permissions. On a Google Pixel 2 running Android 10, the path can also be Settings > Privacy > Permission Manager > Location > [App Name]. In both cases, the permission toggled is Location on older OS versions.

On Samsung Galaxy S24 or any current-gen phone running Android 14, the Android 12-and-newer steps above apply exactly. Identify your OS version first — the phone brand does not change the core rule.

Common Mistakes That Block Bluetooth Access

Even with permission granted, Bluetooth may still fail. These three issues cause most of the frustration.

• Confusing Location with Nearby devices. Users on Android 12+ search for “Location” and miss the new Nearby devices toggle. If you see no Nearby devices option, double-check your Android version.
• Denying permission at first prompt. If you tapped “Deny” when the app first asked for Bluetooth access, the system remembers that choice. You must visit Settings to enable it manually — the app cannot re-prompt on its own.
• Bluetooth radio is off. Permission lets an app request Bluetooth connections, but it does not turn on the Bluetooth radio. Open Settings > Connected devices > Connection preferences > Bluetooth and toggle it on if needed.

The table below shows each major Android version’s permission path at a glance.

For full technical details covering manifest declarations, the neverForLocation flag, and legacy compatibility across API levels, Android’s official Bluetooth permissions documentation is the definitive reference.

When the App Still Can’t Find Devices

If the permission is correctly granted but the app still shows no nearby Bluetooth hardware, check these items in order.

• Hardware support. Confirm your device has Bluetooth hardware. Some tablets and budget phones omit it — if Settings shows no Bluetooth menu at all, the hardware is absent and no permission grant will help.
• Pairing requests blocked. On some Android skins, a “Bluetooth pairing requests” toggle under Connected devices > Connection preferences > Bluetooth can block incoming connections. Make sure it is enabled.
• App not updated for Android 12+. Older apps that have not been updated may still request legacy Bluetooth permissions. If the app was installed before your device updated to Android 12, a reinstall often resolves the manifest mismatch.
• Restart and re-pair. A full phone restart clears transient Bluetooth stack errors. After rebooting, open the Bluetooth settings and pair the accessory again from scratch.

Quick-Reference Checklist for Every Situation

Use this checklist when you need a fast answer on any device.