public class Bluetooth

Entry point for the Codename One Bluetooth API – adapter state, runtime permissions and the capability queries that let cross-platform code branch cleanly. Obtain the platform implementation via getInstance(); the returned subclass is owned by the active port and never null.

The API is split by role:

• com.codename1.bluetooth.le – BLE central: scanning, connections and the GATT client, plus L2CAP channels.
• com.codename1.bluetooth.le.server – BLE peripheral: advertising and the local GATT server.
• com.codename1.bluetooth.classic – classic Bluetooth: discovery and RFCOMM stream connections (Android and the simulator only).

Quick start: check support and permissions

Bluetooth bt = Bluetooth.getInstance();
if (!bt.isLeSupported()) {
    // hide the feature
    return;
}
bt.requestPermissions(BluetoothPermission.SCAN, BluetoothPermission.CONNECT)
  .onResult((granted, err) -> {
       if (err == null && granted) {
           // start scanning...
       }
  });

Threading

Every callback of the Bluetooth API – AsyncResource results, scan results, connection events, notifications, adapter state changes – is delivered on the EDT. The only exceptions are the blocking InputStream/OutputStream pairs of RFCOMM and L2CAP connections, which must be consumed off the EDT.

Platform support

• Android – full stack: BLE central + peripheral, L2CAP (API 29+), classic RFCOMM. Permissions and manifest entries are auto-injected at build time when these packages are referenced.
• iOS / Mac Catalyst – CoreBluetooth: BLE central + peripheral and L2CAP. Classic RFCOMM is not exposed by iOS. The NSBluetooth* plist entries and CoreBluetooth framework are auto-injected at build time.
• JavaSE simulator – a scriptable virtual Bluetooth stack with a full feature matrix (Simulate -> Bluetooth Simulation), plus an optional native backend that talks to the host machine’s real Bluetooth hardware (BLE central only).
• JavaScript – Web Bluetooth where the browser supports it: central role via the browser’s device chooser, GATT client and notifications.
• All other ports – this base class is returned as-is and reports Bluetooth as unsupported; every operation fails fast with BluetoothError.NOT_SUPPORTED.