Archived:Controlling Bluetooth power state in notifier-initiated situations

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Tested with

Devices(s): All (S60 3rd Edition)

---

Compatibility

Platform(s): S60 3rd Edition
S60 3rd Edition, FP1

---

Article

Keywords: CBTMCMSettings

Created: User:Kbwiki (03 Nov 2009)

Last edited: hamishwillee (15 Jun 2012)

Overview

This article describes how a 3rd party application can temporarily disable Bluetooth connections.

Detailed Description

When the user activates Bluetooth from an S60 Bluetooth application, a central repository key for Bluetooth power state is updated.

To pre-empt Bluetooth connections, an application could monitor the key and set it back to the off state. However, this approach is not enough if Bluetooth is initially off and then started via a notifier; a typical use case is selecting Send via Bluetooth from the Options menu. In this case, although we do get a notification about the central repository key changes, the information is not propagated to the Bluetooth stack.

Solution

In addition to monitoring/setting the value of the central repository key, the CBTMCMSettings class is needed to control the power state of the Bluetooth module directly.

Note: :This API (CBTMCMSettings) is not part of the public SDK. It can be found in the SDK API Plug-in.

See also

How to set Bluetooth power state