Dorkasdev / bluecove

Automatically exported from code.google.com/p/bluecove
1 stars 0 forks source link

Bluecove on Windows CE 6.0 #144

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Tried using bluecove 2.0.0 jar on Windows CE 6.0 for bluetooth device 
discovery.
2. Kept bluecove_ce.dll and intelbth_ce.dll in \Windows folder.
3. Tried to run simple bluetooth device discovery and service discovery for 
detecting bluetooth printer.

What is the expected output? What do you see instead?
The bluetooth printer device and its services should be discovered.
But got error while using device discovery.

What BlueCove version are you using (include build number for SNAPSHOT)?
Using bluecove-2.0.0.jar downloaded from releases from the below URL :- 

http://sourceforge.net/projects/bluecove/files/BlueCove/2.0.0/

On what operating system and jvm? Is this 64-bit or 32-bit OS and jvm?
I am using it on Windows CE 6.0 OS on Motorola Symbol MC3190 device and on 
Creme JVM 4.12

Please provide any additional information below.

I tried using bluecove-2.0.0.jar on Windows CE 6.0 device on Creme JVM 4.12 and 
put the intelbth_ce.dll and bluecove_ce.dll, extracted from the jar, in 
\Windows\ folder and try to run the application.

But when i try to get the local device thru the code
LocalDevice.getLocalDevice() 

it throws the exception as below and application hangs :

BlueCove version 2.0.0 on winsock
UnsatisfiedLinkError:socket
Exception occurred during event dispatching:
java.lang.UnsatisfiedLinkError: socket
    at com.intel.bluetooth.BluetoothStackMicrosoft.getLocalDeviceBluetoothAddress()
    at javax.bluetooth.LocalDevice.<init>()
    at javax.bluetooth.LocalDevice.getLocalDevice()

After searching on the net, i found that it may be problem that ws2.dll is not 
present in \Windows\ folder of Windows CE.
But its already present there.
Also, i tried to copy another ws2.dll, but it gives permission denied error.

Please suggest.
Thanks.

Original issue reported on code.google.com by Ankit...@gmail.com on 14 Jan 2014 at 9:25