Bluetooth is a ubiquitous short-range wireless communication protocol used in Android devices for connecting peripherals, transferring files, and facilitating proximity-based services. While indispensable for consumer convenience (earbuds, smartwatches, car audio), the Bluetooth radio stack represents one of the most critical and historically vulnerable attack surfaces in strict enterprise, military, or zero-trust deployment environments (e.g., BlueBorne, BLE spoofing, MAC address tracking). On secure communication terminals, tactical field devices, or dedicated point-of-sale (POS) systems, an active Bluetooth radio provides an invisible, unauthenticated vector for remote code execution, data exfiltration, or physical location tracking by adversaries. In these scenarios, the radio MUST be permanently neutralized at the OS framework level.
This guide explains how to completely disable ‘Bluetooth’ system-wide on Android, ensuring the operating system is cryptographically prevented from powering on the radio hardware or negotiating connections.
Disable Bluetooth via Mobile Device Management (MDM)
While standard users can toggle Bluetooth off in the Quick Settings panel, this does not prevent an application with the BLUETOOTH_ADMIN permission from silently turning it back on, nor does it prevent the user from re-enabling it. To enforce a strict, irreversible block at the OS kernel level, an administrator must utilize the Android Enterprise Management API via an MDM solution.
- Access the administrative console of your organization’s MDM platform (e.g., Microsoft Intune, VMware Workspace ONE, or Google Workspace Endpoint Management).
- Navigate to the section for Android Configuration Profiles or Device Policies.
- Create a new policy (or edit an existing one) targeting Android Enterprise (Fully Managed devices).
- Locate the Device Restrictions, Connectivity, or Wireless Settings section.
- Find the policy control specifically labeled Bluetooth or Allow Bluetooth.
- Set this policy to Block or Disable. (By explicitly disabling this, you instruct the Android framework’s DevicePolicyManager to assert a permanent, system-level lock on the Bluetooth adapter state, overriding all user inputs and application requests).
- Assign the profile to the relevant device groups and initiate a push synchronization.
Verify the Configuration Lockdown
Once the MDM policy syncs with the Android device, the restriction is applied at the OS framework level.
To verify the lockdown is active, unlock the provisioned Android device and swipe down to access the Quick Settings panel. The Bluetooth toggle icon will be completely greyed out and unresponsive to touch. Navigate to Settings > Connected devices > Connection preferences > Bluetooth. The master toggle will be locked in the “Off” position, and a message stating “Action not allowed” or “Managed by your organization” will appear if the user attempts to interact with it. Furthermore, any application attempting to invoke the BluetoothAdapter.enable() API will receive a security exception. The Android device is now operating under a strict zero-trust configuration, completely neutralizing the short-range wireless attack surface.