com.google.android.bluetooth Copy

The Bluetooth application as it is named when it ships inside the Bluetooth Mainline module. A copy of the platform's BluetoothComponent source, published in GrapheneOS's mirror of the Bluetooth module and carrying an Android Open Source Project copyright, says the Bluetooth application's package name "Can be either `com.android.bluetooth` or `com.google.android.bluetooth`", that the "Bluetooth apk name is different when packaged as a mainline module", and that the name is most likely com.android.bluetooth "on a non-mainline device" and com.google.android.bluetooth "on a mainline device". The AOSP manifest for the Bluetooth APK itself declares package com.android.bluetooth with the shared user ID android.uid.bluetooth, and the platform's default config_systemBluetoothStack value is com.android.bluetooth, so the Google name is the result of packaging rather than a separate code base in the sources cited here. The com.android.bluetooth package is documented separately on this site. AOSP describes the Bluetooth module as "an optional Mainline module introduced in Android 13", in APEX format, containing the Bluetooth APK defined in packages/modules/Bluetooth/android/app together with its native library and APIs. On this site the package is recorded on 17 device entries on builds from API 33 to API 37: 16 under the Google make (Pixel 6 through Pixel 10 Pro, two sdk_gphone emulator images and a "GMS on ARM64" entry) and one Samsung SM-F971B entry at API 37. Its English label is "Bluetooth" and it is not user-facing in any observation. Where this site holds signer data, which is 8 of those 17 entries and all of them Google-make, the key is classified as Google and is not one that also signs the Android framework. The aggregate signer record additionally lists HP as a make, which does not appear in this package's device list; that discrepancy could not be explained here. Version note: AOSP says that "In Android 16 and higher, the module is updatable and contains a fully certified dual-mode Bluetooth host stack". The module's build file reflects a change of container: it keeps a disabled com.android.btservices APEX described as the "Legacy Bluetooth apex prior to Baklava" and defines com.android.bt as the "Mainline bluetooth apex module" that carries the Bluetooth app. AOSP's documentation page names the module package com.google.android.bt. So the APEX that delivers this app has changed name across releases, while the lowest API level this site records for the app package is 33, in line with the Android 13 introduction. For Android Enterprise, EMM and kiosk use, this is the device's Bluetooth application where it is present, so disabling it risks removing Bluetooth function for peripherals, audio and anything else that relies on it. The documented control is policy rather than the package: the Android Management API's bluetoothDisabled setting covers "Whether bluetooth is disabled", and the reference says to prefer it over bluetoothConfigDisabled, which only disables configuring Bluetooth and "can be bypassed by the user".

• Bluetooth module - Android Open Source Project →
• BluetoothComponent.kt (Bluetooth application package names) - GrapheneOS mirror of the Bluetooth module →
• Bluetooth APK AndroidManifest.xml - Android source →
• Bluetooth module apex/Android.bp (com.android.btservices and com.android.bt) - Android source →
• Framework config.xml (config_systemBluetoothStack) - Android platform source →
• enterprises.policies (bluetoothDisabled, bluetoothConfigDisabled) - Android Management API reference →
• Package provenance for com.google.android.bluetooth - Android System App Database →

• Signed by Google's own signing key (the same key Google uses across devices), so it is a Google-provided preinstall that updates independently of the system image, though 2 different Google signing keys appear across the fleet. This certificate spans 4 device makes - the hallmark of a globally distributed Google key.
• Its largest observed manifest declares 73 permissions: 17 runtime (user-granted), 36 signature or system-level, 16 install-time and 4 vendor or uncatalogued.
• APK size ranges from 2.7 MB to 6.9 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.