intelbth_ce.dll in 2.0.3 incompletely built: not usable on windows ce / microsoft stack

[GoogleCodeExporter]

>What steps will reproduce the problem?
1. Trying to use 2.0.3 to connect to a known bluetooth address on windows 
mobile 2006 PDA with microsoft stack leads to an UnsatisfiedLinkError

Note: 2.0.2 works perfectly on the same PDA, and also the latest 2.1.x 
nightly builds.

>What is the expected output? What do you see instead?
Exception:
java.lang.UnsatisfiedLinkError: com/intel/bluetooth/
BluetoothStackMicrosoft.socket(ZZ)J at 
com.intel.bluetooth.BluetoothStackMicrosoft.connectionRfOpenClientConnection

Analysis: The exception is correct, the method is declared in the java 
class but when looking at the intelbth_ce.dll the symbols for this 
function are not present. There are many other functions also not present 
in the dll when comparing to intelbth_ce.dll from 2.0.2 (and the 2.0.3 DLL 
is also 50% smaller).

The 2.0.3 release is otherwise very good, perhaps there could be a small 
correction release 2.0.3.1 or 2.0.4 before 2.1.0? Or at least a big 
warning that the 2.0.3 is broken on Windows CE / Microsoft stack. Thanks!

Original issue reported on code.google.com by dknop...@gmail.com on 18 Dec 2008 at 6:47

[GoogleCodeExporter]

Sorry Known problem, Use 2.0.2 or 2.1 version

There are warning in mailing list for this.

Also WIDCOMM/CE stack is broken in 2.0.3 release

To solve the problem like this in future I'm planning to use build server all 
the time.
But to configure this properly takes time... Even so the hardware and VM are 
ready...

Original comment by skarzhev...@gmail.com on 18 Dec 2008 at 6:53

• Changed state: Accepted
• Added labels: OpSys-WinCE

[GoogleCodeExporter]

Hi skarzhevskyy,

Thanks for looking at this. You say that the WIDCOMM/CE stack is broken in 
2.0.3, 
but I have been using it without any problems on the iPAQ 214.

Only when I tried 2.0.3 on a different device (HTC x7510) with the Microsoft/CE 
stack the problems started. I was surprised that such a major regression was 
not 
clearly on the distribution homepage and I didn't find a bug report for it so 
that's 
why I submitted.

Is there any chance you'll have time for a fixed 2.0.3 intelbth_ce.dll build or 
are 
you totally focused on 2.1?

Original comment by dknop...@gmail.com on 18 Dec 2008 at 11:07

[GoogleCodeExporter]

I don't know what to say. Just use version 2.1 it is close to the release.
But probably you are right. I will a changed intelbth_ce.dll to download page.
See and verify attach a file.  FILEVERSION 2.0.3.100 (Original was 2.0.3.99)

And I don't do a complete regression at final build. This will take me a week 
to do
it. So many stacks to tests. I rely on build stability and everybody can 
mistakes.

The WIDCOMM/CE may not work on earlier device because the new API functions was 
used.
This may be not true on your iPAQ 214.

Original comment by skarzhev...@gmail.com on 19 Dec 2008 at 12:28

Attachments:

• intelbth_ce.dll

[GoogleCodeExporter]

Thanks for the response! This is very helpful and I understand you don't have 
time 
for a full regression test.

I'll try this build out.

Original comment by dknop...@gmail.com on 19 Dec 2008 at 10:44

[GoogleCodeExporter]

http://code.google.com/p/bluecove/downloads/list
There are 33 download for this build already.  

Nobody complains. Condensing the problem is solved.

Original comment by skarzhev...@gmail.com on 22 Dec 2008 at 8:21

• Changed state: Fixed-SNAPSHOT

[GoogleCodeExporter]

Original comment by skarzhev...@gmail.com on 26 Dec 2008 at 3:47

• Changed state: Fixed