Class Overview

This class provides Bluetooth UUIDs that an administrator can manage.

Bluetooth Profiles are services offered by a device. For two devices to interoperate, both devices must implement a common profile. Each service can be divided further into a set of features where each feature is identified by Universally Unique Identifier (UUID). UUIDs depend on the vendor of the Bluetooth stack in the device.
Examples: To connect a headset device to a mobile phone device, a headset profile is needed in both devices.
To connect to Internet from a mobile phone device through PDA device, both devices should share the same "dial-up networking" profile.
A list of Bluetooth UUIDs supported by Samsung Android devices are listed below. The corresponding UUID should be used to manage blacklists and whitelists for Bluetooth profile restrictions.

Profile UUID Types:

Advanced Audio Distribution Profile (A2DP)
Defines procedures for high-quality audio (stereo or mono) to be streamed from one device to another over a Bluetooth connection. For example, music can be streamed from a mobile phone, to a wireless headset, hearing aid and cochlear implant streamer, or car audio.
Roles:
A2DP Role (A2DP_ADVAUDIODIST_UUID) - Includes both Sink and Source roles.
Audio Source Role (A2DP_AUDIOSOURCE_UUID) - Acts as a source of digital-audio data and sends the stream to the Sink. eg:- Music player
Audio Sink Role (A2DP_AUDIOSINK_UUID) - Acts as a receiver of the digital-audio stream delivered from the Source. eg:- Wireless stereo speakers

Headset Profile (HSP)
Defines procedures to support interoperability between a headset and a mobile device, such as a cellular phone, that the headset controls through AT commands. The mobile device is the audio gateway (AG) that provides both input and output audio to the headset. The headset acts as an audio input and output mechanism for the AG, and controls the mobile device through AT commands.
Roles:
HSP Role (HSP_UUID) - Acts as Audio Gateway and Controller.
Audio Gateway Role (HSP_AG_UUID) - Acts as a audio gateway alone.
Depends on SPP.

Hands-Free Profile (HFP)
Defines procedures for using a mobile device, such as a cellular phone, in conjunction with a hands-free device over a Bluetooth link, to allow the hands-free device to act as an audio input or output device for the mobile device.
Depends on SPP.
Roles:
HFP Role (HFP_UUID) - Acts as Audio Gateway and Controller.
Audio Gateway Role (HFP_AG_UUID) - Acts as a audio gateway alone.

Audio/Video Remote Control Profile (AVRCP)
Defines procedures to provide a standard interface to control TVs, hi-fi equipment, etc. to allow a single remote control to control all of the A/V equipment to which a user has access. AVRCP may be used in concert with A2DP.
Roles:
Controller Role (AVRCP_CONTROLLER_UUID) - Allows sending command frames to a target.
Target Role (AVRCP_TARGET_UUID) - Allows receiving command frames and generating response frames.

Object Push Profile (OPP)
Defines procedures to support pushing or pulling small data objects (for example, calling card exchange) between Bluetooth devices.

File Transfer Profile (FTP)
Defines procedures to support transferring data and manipulating objects on or with a peer Bluetooth device.

Phonebook Access Profile (PBAP)
Defines procedures to allow exchange of phone book objects between devices. Designed for use between a car kit and a mobile phone.
Roles:
PBAP Role (PBAP_UUID) - Acts as both source and receiver of phone book objects.
Phone Book Server Equipment (PSE) Role (PBAP_PSE_UUID) - Acts as a phone book object source.

Basic Printing profile(BPP)
Defines procedures to send text, e-mails, vCards, or other items to printers based on print jobs. BPP differs from Hardcopy Cable Replacement Profile (HCRP) in that it needs no printer-specific drivers. This feature makes BPP more suitable for embedded devices such as mobile phones and digital cameras, which cannot easily be updated with drivers that depend on printer vendors.

Serial Port Profile (SPP)
Defines procedures required for configuring serial cable connections between peer Bluetooth devices using RFCOMM.

Dial-up Networking (DUN) Profile
Defines procedures to support the use of a wireless modem by a computer for connecting to a dial-up service such as a dial-up Internet service. Depends on SPP.

SIM Access Profile(SPP)
Defines procedures to allow devices such as car phones with built-in GSM transceivers to connect to a SIM card in a phone with Bluetooth, thus eliminating the need for car phone to have a separate SIM card.

Human Interface Device (HID) Profile
Defines procedures to support human interface devices such as a keyboard and a mouse.

Personal Area Networking User (PANU) Profile
Defines procedures to communicate with a Group Ad-hoc Network (GN), a Network Access Point (NAP), or with another Bluetooth device through a point-to-point connection.

Network Access Point (NAP) Profile
Defines procedures to route network packets between PAN Users (PANU) by using Bluetooth Network Encapsulation Protocol (BNEP) and the layer-3 routing mechanism. A NAP can also act as a bridge between Bluetooth networks and other network technologies by using the layer-2 bridging mechanism.

Bluetooth Network Encapsulation Protocol (BNEP) Profile
Defines procedures to communicate with other Bluetooth devices using standard networking protocols to transport control and data packets over a network. Devices may use protocols such as TCP, IPv4, or IPv6.

The Bluetooth profile details covered here are the most common profiles supported by Samsung Android phones. However, the Samsung design of Bluetooth profile restriction APIs is not limited to the profile UUIDs covered here; restrictions also cover blocking of non-listed Bluetooth profiles based on UUIDs as long as they are supported by the device.
Please see https://www.bluetooth.org/Technical/Specifications/adopted.htm for the complete list of Bluetooth profiles. Obtain the corresponding UUIDs from Samsung for non-listed profiles.

Summary

[Expand] Inherited Methods
From class java.lang.Object Object clone() boolean equals(Object arg0) void finalize() final Class<?> getClass() int hashCode() final void notify() final void notifyAll() String toString() final void wait(long arg0, int arg1) final void wait(long arg0) final void wait()