Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0

Get PDF Book Print View

Document Information

Getting Started

Java ME Platform SDK Features

Using Sample Projects

Creating and Editing Projects

Viewing and Editing Project Properties

Running Projects in the Emulator

Searching the WURFL Device Database

Finding Files in the Multiple User Environment

Profiling Applications

Monitoring Network Traffic

Lightweight UI Toolkit

Security and MIDlet Signing

BD-J Support

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator

On-device Debugging

Command Line Reference


JSR Support

JSR 75: PDA Optional Packages

JSR 82: Bluetooth and OBEX Support

Bluetooth Simulation Environment

OBEX Over Infrared

Setting Bluetooth and OBEX Preferences

OBEX Preferences

Bluetooth Internal Properties

Bluetooth System Properties

Bluetooth BCC Properties

Running the Bluetooth Demo

JSR 135: Mobile Media API Support

JSR 172: Web Services Support

JSR 177: Smart Card Security (SATSA)

JSR 179: Location API Support

JSRs 184, 226, and 239: Graphics Capabilities

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 238: Mobile Internationalization API (MIA)

JSR 229: Payment API Support

JSR 256: Mobile Sensor API Support


Bluetooth BCC Properties

The Bluetooth Control Center (BCC) controls Bluetooth settings. Some devices might provide a GUI to customize Bluetooth settings. In the Java ME Platform SDK, the BCC is configured using the BCC Properties tab of the Bluetooth preferences. The properties are as follows.

BCC Properties  
Enable Bluetooth support
If this property is disabled, LocalDevice.getLocalDevice() throws a BluetoothStateException and no connections can be created. This is useful to test the behavior of your application on devices that support JSR 82 but might have the Bluetooth feature turned off.
Device is discoverable
Indicates whether or not this emulator can be discovered by other emulators.
Friendly name
A human-readable name for the emulator in the simulated Bluetooth environment. If the name is left blank, the emulator does not support the friendly name feature.
Determines whether connection encryption is supported (on) or not (off). In addition, the force settings means all connections must be encrypted. See the documentation for RemoteDevice’s encrypt() method for details.
Similar to the Encryption property. See RemoteDevice’s authorize() method.
Similar to Encryption and Authorization. See RemoteDevice’s authenticate() method.