Bluetooth Classic (RFCOMM, A2DP, HID)
Pairs and talks to classic Bluetooth devices such as headsets, printers and car kits.
In one line
Can talk to headsets, printers and car kits on Android; iPhone allows only certified accessories
Pairs and talks to classic Bluetooth devices such as headsets, printers and car kits.
Classic links expose paired devices by name and address, and serial links can carry any data. iPhone apps cannot open raw Classic sockets, which blocks many hobby and industrial uses.
What it can and can't do
What the user does: You pair a headset, printer or car kit, then use the app with it
It can
- List paired devices by name and address (Android)
- Open a serial style link and exchange any data (Android)
- Use audio and hands free profiles with headsets and car kits
- Connect to Apple certified (MFi) accessories on iPhone
It cannot
- Open raw Classic Bluetooth links on iPhone
- Support many hobby and industrial gadgets on iPhone
- Connect on Android 12 and later before you allow Nearby devices
How it differs between platforms: Android lets apps open Classic links directly; iPhone limits Classic to MFi accessories and has no raw sockets.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Partial |
| First version | Android 2.0 (API 5) | iOS 3.0 |
| Permission or entitlement | BLUETOOTH_CONNECT (API 31); BLUETOOTH earlier | UISupportedExternalAccessoryProtocols (MFi), com.apple.developer.external-accessory.wireless-configuration |
| Protection level | dangerous | entitlement |
| How access is granted | prompt | entitlement |
| What the user sees | Nearby devices prompt | No raw prompt; MFi program membership and Bluetooth prompt for accessories |
| How long it lasts | Until revoked | Per accessory pairing in Settings |
| How to take it back | Settings > Apps > Permissions | Settings > Bluetooth > Forget |
| Store policy | None listed | MFi licence required to ship hardware |
| API | BluetoothSocket (RFCOMM), BluetoothAdapter, A2DP and HFP profiles | ExternalAccessory (EAAccessory), AVAudioSession routes, AccessorySetupKit |
| Notes | None | No public RFCOMM sockets; only MFi accessories speak Classic to apps. |
Data you get
What comes back: Bidirectional byte stream
Shape: stream
How often: up to about 2 to 3 Mbit/s (EDR)
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
paired device name | string | text | any | varies |
Technical limits
- iOS needs MFi membership for Classic accessories
- Pairing happens in system UI on both OS
The story
What it is
The older Bluetooth that links to headsets, printers, car kits and card readers.
For you
You pair a printer, a handheld scanner or a car kit and it just works. On iPhone only some certified accessories can use this link with apps. On Android the app can talk to many more devices.
For makers
Classic Bluetooth carries audio and plain serial data, so it is used for receipt printers, card readers and car diagnostic tools. Android gives apps room to build with it. iPhone limits it to certified accessories.
Where you see it
| Type | Example | Apps |
|---|---|---|
| payments | A shop's receipt printer pairs to the point of sale app and prints when a sale ends. | Square |
| automotive | A car diagnostic dongle reads engine codes into a phone app. | Torque Pro |
| music | Your car stereo pairs your phone for calls and music. | None named |
| enterprise | A warehouse handheld scanner sends barcodes to an inventory app. | Zebra |
| health | A pulse oximeter or older medical gadget sends numbers to a health app. | None named |
| games | A wireless game controller connects to a phone for a console style game. | Xbox Controller |
| utilities | A label printer prints parcel labels from a shipping app. | Brother |
Risks
- Paired devices expose names
- Serial links can carry anything
- Old security design
Android and iPhone in short
- Android: Android lets apps open Classic Bluetooth serial links to paired devices.
- iPhone: iPhone has no public serial link for apps. Only certified accessories (MFi) can talk Classic Bluetooth to apps.
Good uses and abuse
Legitimate uses
- Printers
- POS card readers
- OBD adapters
Known abuse
- Silent device census of paired items
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | 4 | Rough identifying entropy, when known |
History
- 2009-10, Android 2.0 (API 5): Bluetooth APIs introduced
- 2021-10, Android 12 (API 31): Runtime Nearby devices permission
Related capabilities
Related
- Bluetooth LE scan and connect. Can find and connect to nearby Bluetooth gadgets once you allow Bluetooth
- Accessory pairing without broad Bluetooth access. Can pair the one accessory you pick without seeing other Bluetooth devices nearby
Same idea on the web
- Web Bluetooth (GATT). Can connect to one nearby Bluetooth device you pick from a list
- Web Serial. Can open one serial port you pick and exchange data with it
Sources
How well checked: Based on official documentation.