Socket Mobile BTM-2 Benutzerhandbuch

 

Keeping the Bluetooth hardware active during a suspend still has some issues which is why the module 
should be powered down during a suspend: 

1)  On Suspend, the KwikBlue Module should be powered down. The mechanism for power-down is 

customer implementation dependent. 

2)  On Resume, the KwikBlue Module should be powered back up. The mechanism for power-up is 

customer implementation dependent. On power-up, the KwikBlue module running at 921 Kbps 
requires approximately 800 ms to become connectable. 

3)  On Resume, BCSPStack.dll must be shutdown. A DeActivateDevice() call must be made on 

‘HKLM\Software\Socket Communications\Bluetooth\Bt Device\’ with the handle obtained earlier 
from the ActivateDevice() call. This will cause BCSPStack.dll to shutdown the rest of the stack 
(\Windows\BtDevMan.exe). 

4)  The stack must then be loaded with an ActivateDevice() call on ‘HKLM\Software\Socket 

Communications\Bluetooth\Bt Device\’. 

The following binaries comprise the Bluetooth drivers for the module case. They are placed in the 
\Windows directory of the device. 

ƒ 

BlueSocket.dll 

ƒ 

BtDevMan.exe 

ƒ 

BtDevWin.exe 

ƒ 

BTExchange.dll 

ƒ 

Btvcomm.dll 

ƒ 

ToothSocket.dll 

ƒ 

ConnectWiz.exe 

ƒ 

Drakar.dll 

ƒ 

DkUiUtils.dll 

ƒ 

BCSPStack.dll (used by embedded modules and Rev G (and higher) CF Cards With 
Bluetooth Wireless Technology) 

ƒ 

ScktIrda.cpl (IrDa Control Panel configuration utility - optional) 

Binaries that occur in the retail release but are not included in a module build: 

ƒ 

WendyStack.dll (only used by older Rev F CF Cards With Bluetooth Wireless Technology - 
not in production any more) 

ƒ 

SDBTASckt.dll (SDIO driver - SDIO slot devices only) 

ƒ 

SIO_BT.DLL (high speed serial driver - Rev G and above cards only) 

ƒ 

BtCustomSetup.dll (set-up wizard for *.cab install, not part of stack)