Bluetooth Broadcom Stack Support

[Sonichedgehog360]

The new HP iPAQs 110 and 210 do not carry the standard Microsoft Bluetooth stack. They carry the Broadcom stack instead. Will support for the Broadcom stack be added in a later Total Commander build or beta? Thank you.

[ghisler(Author)]

I'm sorry but this isn't currently planned. While their SDK is now free (it was very expensive in the past), I don't currently have any device with the Broadcom stack supported by the SDK for testing. The Bluetooth development is very complex, and almost impossible without a device for testing. The only device with the broadcom stack which I currently have (an older IPAQ 3870) is unfortunately not supported by the broadcom stack SDK, and older versions of the SDK are no longer available.

[Sonichedgehog360]

I can test something... just throw something at me (if realistically possible). (Sorry about the slow post!).

[ghisler(Author)]

Thanks for the offer, but as I wrote, Bluertooth development is too complex to be done without a real device.

[OMOIKANE]

I have unused iPAQ 3970 wm2003. You can grab it here ... in Moscow.
Can you?

[ghisler(Author)]

Thanks for the generous offer! Unfortunately I can't come to Moscow just to get your device, sorry. It's probably easier for me to look for one on ebay. Btw, the 3970 has WM2002, did you update it yourself to WM2003?

[OMOIKANE]

yeah, updated to 2003 with official firmware update. and intresting - i have that device 4 years and accumulator life is acceptable for now.

[ghisler(Author)]

OK, I have access to a WM5 device with Broadcom stack now!

I have installed the Broadcom stack, and there was a sample tool for OBEX transfers. However, it uses its own client+server code, so I couldn't use it directly. I have created a modified tool now which does work with standard OBEX servers (available on almost all Windows Mobile and Palm devices).

The final goal will of course be to integrate this function into Total Commander Pocket, but before I proceed, I would like to ask you to test it with your devices too.

Here you can download the tool:
https://plugins.ghisler.com/ce/blueobex.zip

See the file readme.txt for usage instructions. Please note that this is just a TEST tool. It only works with portrait mode, not landscape, and doesn't adjust its size to various screen sizes. Furthermore, it shows debug messages in a text list during the transfer.

I have also compiled the tool with EVC4 for Windows Mobile 2003, but that version doesn't work properly on Windows Mobile 5. It can see the other devices, but connections always fail. You can download the test tool for WM2003 here if you want to try it, but I couldn't test it because I don't have any WM2003 devices with the Widcom/Broadcom stack, sorry.

[ghisler(Author)]

Seems like no one is really interested in this function, so for now I haven't put it in TC Pocket 2.51...

[scorpio_cz]

I am interested bu I am too late :

I will download your test binary and test it on iPAQ 214 (WM6, BCM stack).

I will post results here in 1 or 2 days after I test.

Edit : YES it's working fine.
I have transferred a few files from PDA o PC with no problems.

I hope to be able to manage tests of Win2003 btobex on Acer N50 Plus with Win2003 SE, also with BCM stack I think, during this week ...

I will keep news posted.

[ghisler(Author)]

Ah, finally someone who can test this function! It would be nice if you could test it with a big file, e.g. an MP3 file of 5-10 Megabytes or similar, to see whether it transfer the entire file without problems.

Please note that there is a separate plugin for Win2003 SE which I couldn't test at all so far.

[scorpio_cz]

Yes, I have tested it with 5.8 MB file.
It seemed to transfer fully with no problems.

I am aware of the fact that Win2003SE plugin is separate, my father has Acer N50 with Win2003SE so I belive he can test it within couple of days as well.

I will now test the tranfer with even bigger file, let's say 10 MB

EDIT 1 : 13.5 MB file NEGATIVE.
There are problems with display of the transfer messages.
It looks like display is rewritting the whole buffer every new message.
And after few megabytes (approx 1/3 of the file) it have said CLOSE OK and the file wasn't complete yet ...

EDIT 2 : 13.5 MB file second try.
According to the progress bar, second try also "hanged" somewhere around 1/3 of the file, with stopped display. However I was ready and moved the scrollbars up and down, and voila tranfer resumed.
But now it's a real PAIN for CPU - around 70% the transfer is now very SLOW and CPU is spinning displaying the messages.
Again, around 80 % it again "hanged" on still display, again moving the scrollbars resuscicated the transfer.
Second try results - POSITIVE. So the problem is message handler - too many messages to display, the log is long.
Transferred file verified - binary identical with original

Can you, please, prepare new test module with changed display part - maybe display just last few messages and let the rest to get to logfile or simply trim the message buffer ?

[ghisler(Author)]

Thanks for your tests! I guess that the listbox is just running full with debug messages. This will of course not be in the version which I will integrate into TC...

I am aware of the fact that Win2003SE plugin is separate, my father has Acer N50 with Win2003SE so I belive he can test it within couple of days as well.

This would be nice!

Btw, could you test the Win2003SE version of the tool on your WM5 device too? According to the docs, it should work, but it doesn't here - I can see the devices, but I cannot send any files to them...

[scorpio_cz]

Win2003 module test on WM60 NEGATIVE

Code: Select all

Start send
>> Find Service: OBEX Push for: 0:1a:6b:xx:xx:xx
>> Open file:
\SD Card\temp\testfile.dat
>> OPEN:  scn: 3, ERROR: 12, server: 0:1a:6b:xx:xx:xx

Status: CObexClient::Open failed, code 12

EDIT : I got the tests of the WM2003 module on WM2003 SE => tests NEGATIVE , the testmodule hangs on PDA and cannot have been killed, only soft-reboot of the PDA removed it away.
So the WM2003 build needs some more investigation.

[ghisler(Author)]

I see - where exactly does it hang? Already at startup, or when enumerating devices, or when sending the file?