Nokia Bluetooth Devices Driver

  • Microsoft Bluetooth Device Driver for Windows 7/Windows 8 64-bit 41,217 downloads. Bluetooth Microsoft. Windows 8 64 bit, Windows 7 64 bit.
  • Download Nokia 2720 fold Bluetooth Modem Bluetooth device drivers or install DriverPack Solution software for driver update.

Tap Settings Connected devices Connection preferences Bluetooth. Switch Bluetooth to On. Make sure the other device is switched on. You may need to start the pairing process from the other device. For details, see the user guide for the other device. To pair your phone and the device, tap the device on the list of discovered Bluetooth. A profile driver's INF file contains information about a Bluetooth device for client-side installation. For a server-side installation, the INF file specifies a device ID that corresponds to the service GUID created by the installation application. All Bluetooth devices are members of the Bluetooth class. How to get your device into this mode will vary depending on the device so you will have to consult the manual to find out how. Once your device is in pairing mode it's pretty straightforward, go into bluetooth settings on your android device and after several seconds your Bluetooth device should show up in the list of devices.

Nokia bluetooth devices drivers

Category: Bluetooth
Manufacturer: Nokia
Caution Level: Intermediate
Download File Size: Not specified
Operating System: Windows XP
Latest Version / Release Date: Not specified / Not specified

Windows device driver information for Nokia 6112 Bluetooth

Nokia Bluetooth Devices driver

Nokia 6112 Bluetooth is a mobile accessory device and a wireless communication device produced by Nokia for the Nokia 6112 cell phone. Bluetooth provides a wireless method of communication and facilitates the exchange of data over a short distance from a fixed device to a mobile device. The use of Bluetooth facilitates the creation of personal area networks (PAN). Originally, Bluetooth was developed to offer an alternative wireless communication method in lieu of the RS232 data cables. Bluetooth can link to several devices and is therefore able to overcome synchronization problems. Bluetooth enables the user to benefit from wireless communication regardless of where he or she is located. That there is no need for messy wires in order for one to be able to communicate makes Bluetooth a very convenient method of communication over a short distance. Devices which are within range of each other can communicate using Bluetooth.

Outdated Drivers?

Unless you update your drivers regularly you may face hardware performance issues.

To check your drivers you should manually verify every device on your system for driver updates

The Nokia 6112 is Bluetooth enabled and it utilizes the Bluetooth specification 2.1 along with the Hands-Free profile as well as EDR headset profile 1.1. Bluetooth specification 2.1 is a Bluetooth version which was adopted in the year 2007. Some of its features include EIR (Extended inquiry response); a features that provides additional information for the duration of the inquiry procedure to permit enhanced device filtering before connection is achieved. Sniff subrating is another feature which reduces the consumption of power when the device being used is in low-power mode, particularly on links which have asymmetric flows of data. Bluetooth 2.1 specification permits device pairs to negotiate the frequency in which they will send messages. A third feature is EPR (Encryption pause/ resume) which gives an encryption key the capability to be altered with minimal management from the blue tooth host. It is highly recommended you run a free registry scan for Windows and Nokia 6112 Bluetooth errors before installing any driver updates.



This topic is for programmers. If you are a customer experiencing Bluetooth device installation issues see Pair a Bluetooth device in Windows

There are two installation types for Bluetooth profile drivers:

  • Client-side installation for remote devices where the remote device advertises its services and the computer connects to it. Examples include: mouse devices, keyboards, and printers.

  • Server-side installation where the computer advertises services and remote devices can connect to the computer to use those services. For example, a vendor could author a server-side installation to enable a PDA to print to a printer attached to the computer.

These two installation types require different installation procedures.

Installing a Client-side Profile Driver

A user that wants to use a Bluetooth-enabled device will bring the device within range of the computer and initiate a connection from the computer to the remote device using the following installation sequence for a client-side profile driver.

  1. Launch Bluetooth Devices in Control Panel to find all devices within range of the computer.

  2. Select the device to pair with.

  3. Pair (or bond) the device with the local radio. This may or may not involve a PIN exchange.

  4. The local radio issues an SDP inquiry to identify the services supported on the remote device.

  5. The Found New Hardware Wizard searches for appropriate drivers on the local hard disk drive, and/or on Windows Update.

  6. If the Found New Hardware Wizard does not find an appropriate driver for the device, it prompts the user to insert the profile driver installation media that contains the profile driver's device setup information file (INF file).

Installing a Server-side Profile Driver

The Bluetooth driver stack supports service GUIDs as defined by the Bluetooth SIG, as well as custom GUIDs (that is, GUIDs that are not defined by the Bluetooth SIG).



The Guidgen.exe tool provided with the Microsoft Windows SDK can be used to create custom GUIDs.

A user-mode installation application must be written to expose computer functionality that remote Bluetooth devices can use.

The installation application must communicate with the Bluetooth driver stack to create a service GUID for the functionality to expose. Vendors specify the service GUID in the application and in their device installation INF file.


The installation application must call the user-mode API BluetoothSetLocalServiceInfo. Before the application can call this API the application must have the SE_LOAD_DRIVER_NAME security privilege. The following code example demonstrates how to obtain this privilege. Note that the example does not demonstrate error handling.

Nokia Bluetooth Devices Drivers

Profile Driver INF file

A profile driver's INF file contains information about a Bluetooth device for client-side installation. For a server-side installation, the INF file specifies a device ID that corresponds to the service GUID created by the installation application. All Bluetooth devices are members of the Bluetooth class. The Bluetooth class installer (Bthci.dll) assists in installing profile drivers.

For more information about creating and distributing INF files and installing drivers, see Creating an INF File and INF File Sections and Directives.

Plug and Play IDs

The Bluetooth driver stack generates hardware IDs according to the following templates:

  • BTHENUM{ ServiceGUID}_VID& nnnnnnnn

  • BTHENUM{ ServiceGUID}_VID& nnnnnnnn_PID& nnnn

  • BTHENUM{ ServiceGUID}_LOCALMFG& nnnn


The Bluetooth driver stack generates compatible IDs according to the following template:

  • BTHENUM{ ServiceGUID}

ServiceGUID is a 16-bit GUID expanded into a 128-bit GUID, as defined by the Bluetooth specification. For example, {00001124-0000-1000-8000-00805F9B34FB} corresponds to an HID device.

  • The 8 digits following VID& correspond to the vendor ID code.

  • The 4 digits following PID& correspond to the product ID code.

  • The 4 digits following LOCALMFG& correspond to the manufacturer of the local Bluetooth radio.

  • The VID/PID and LOCALMFG tags are independent of each other.

Nokia Bluetooth Devices Driver

The most generic device ID is a ServiceGUID by itself. For example:


The Bluetooth driver stack can be restricted to load your profile driver and software to run only on a specific release of a remote device by using Plug and Play IDs in both the remote device and the INF file. Note that the Bluetooth driver stack generates a VID/PID pair only if the device publishes a Plug and Play ID that the stack can detect using SDP. For example:

BTHENUM{00001124-0000-1000-8000-00805F9B34FB}_VID& nnnnnnnn_PID& nnnn

The Bluetooth driver stack can be restricted to load profile driver and software to run only on a specific local Bluetooth radio by specifying the LOCALMFG tag in the device ID in your INF file. For example:

BTHENUM{00001124-0000-1000-8000-00805F9B34FB}_LOCALMFG& nnnn