Reusing WM2003SE Widcomm BT stack extracted from dumped ROM image - anyone tried?

[beecher]

I would rather see Widcomm BT stack working for just only one thing causing it: HP BT Keyboard. Those MFs from HP don't have MS BT stack capable driver... :-(

[bigbop]

I found something very interesting today... this is a so-so translation of the Fujitsu-Siemens N560 Review by solopalmari.com. This FS has bluetooth 1.2 and the MS BT driver as you can see on the screenshots but the BT audio headset is fully working.... is the Microsoft Bluetooth driver for the Axim x51v capable of this?

http://translate.google.com/translat...&hl=en&ie=UTF8

Here is the link to the LOOX N560 Firmware update (24MB)
http://support.fujitsu-siemens.com/D...A-D53D948AFACA
Maybe someone can pull the stack from it? Or maybe not. Here is a coment from the update:

Comment: only for Pocket LOOX N500 new: Microsoft AKU 1.1.1

[thunderstreich]

I'd love to see Widcomm work in the long run, but in the short run I just want to be able to use my wireless headphones and it doesn't matter to me which stack that requires.

I was looking around buzzdev.net and I found the attached file. It seems to be a program designed to work with MSBT stack to support A2DP. I can run it and find my headphones with it, but I haven't been able to get it to connect. Has anybody seen this before and will it help at all?

[vsunlimited]

could someone tell me what's Widcomm's better????

[dvmed]

could someone tell me what's Widcomm's better????

Compared to the X51's bluetooth stack
A superior bluetooth manager
A bluetooth services manager
Personal Area Networking
A2DP profile
Audio Gateway
HFP
Configurable baud / flow rate / com port
A more reliable obex file transfer

I'd love to see Widcomm work in the long run, but in the short run I just want to be able to use my wireless headphones and it doesn't matter to me which stack that requires.

I was looking around buzzdev.net and I found the attached file. It seems to be a program designed to work with MSBT stack to support A2DP. I can run it and find my headphones with it, but I haven't been able to get it to connect. Has anybody seen this before and will it help at all?

It looks like an AKU 2.2 beta for QTek from a chinese website. It runs on a Xscale (ARM) based Windows mobile 5.0 - but that is all it does. Without supporting bluetooth stack below it there is no connection in form of A2DP.

I wunder however what an AKU 2.2 is and when Dell will make a ROM with this (year 2068 perhaps). The AKU 2.2 has a link to Microsoft's MSDN beta site - and to that you need acces with user ID and password

:-) Will

[AgentXXL]

I wunder however what an AKU 2.2 is and when Dell will make a ROM with this (year 2068 perhaps). The AKU 2.2 has a link to Microsoft's MSDN beta site - and to that you need acces with user ID and password

:-) Will

AKU 2.2 was released to OEMs within the last month. It typically takes an OEM about 3 - 6 months to implement the AKU features they desire for their devices. Estimated release of an AKU 2.2 supporting device is September. I did read a list of items that AKU 2.2 supported, but don't have the URL handy. I'll check when I get home tonight.

[d23]

AKU 2.2 was released to OEMs within the last month. It typically takes an OEM about 3 - 6 months to implement the AKU features they desire for their devices. Estimated release of an AKU 2.2 supporting device is September. I did read a list of items that AKU 2.2 supported, but don't have the URL handy. I'll check when I get home tonight.

For some reason this post has me rolling on the floor laughing.

[renhui]

I just tried on my x51v with A06 ROM, same problem, the axim could see the headphone but couldn't connect for some reason.

I'd love to see Widcomm work in the long run, but in the short run I just want to be able to use my wireless headphones and it doesn't matter to me which stack that requires.

I was looking around buzzdev.net and I found the attached file. It seems to be a program designed to work with MSBT stack to support A2DP. I can run it and find my headphones with it, but I haven't been able to get it to connect. Has anybody seen this before and will it help at all?

[AgentXXL]

For some reason this post has me rolling on the floor laughing.

I didn't say that Dell would be the OEM to release it in September. In fact, I'ld be surprised if we get the AKU 2.0 update before then. :)

Still looking for the URL listing AKU 2.2 features...

EDIT: I'm not sure where/how I stumbled on it originally, but right now it eludes me. There's a number of references to AKU 2.2 (and even a rumored 3.0!) on Google, but no 'list of features' that I've found. If/when I do come across it again, I'll post it. In the meantime, I'll (not-so) patiently wait for a working A2DP/AVRCP...

[JimboJoe]

I'm using the Widcomm stack v0.36. I tried using activesync bluetooth connection, it ends with an error : impossible to open file '1', it is either not signed or a required component is not found. Did anybody happen to activesync via this stack?

[Top_Gun]

I'm using the Widcomm stack v0.36. I tried using activesync bluetooth connection, it ends with an error : impossible to open file '1', it is either not signed or a required component is not found. Did anybody happen to activesync via this stack?

Jimbojoe, I have used AS over BT with 0.36. Initially, it did not work - the trick was to import first the platform.reg from 0.35, then again the regfile from 0.36. The registryfile in 0.36 is not complete, using the one from 0.35 and then the one from 0.36 imports all the necessary settings.

Regards,

Detlev

[JimboJoe]

Jimbojoe, I have used AS over BT with 0.36. Initially, it did not work - the trick was to import first the platform.reg from 0.35, then again the regfile from 0.36. The registryfile in 0.36 is not complete, using the one from 0.35 and then the one from 0.36 imports all the necessary settings.

Regards,

Detlev

I did that already the first time. Just did that another time. Still the same problem
Any help from a Widcomm expert? :)

EDIT : Another question Top Gun : do you launch the synchronization via activesync (like I am trying to do) or the new bluetooth manager?

Thanks to a registry key found by MikelSpikel in BTCEStack.dll I've managed to make a patch that solves the speed problem.

Now the UART connects at 921.600bps that allows to get the 733Kbps that is the max speed for the data channel on Bluetooth 1.1 and 1.2

In fact I've seen speeds up to 52KBytes/s usinf file transfer between my computer and my X51v: 52KB x 8 Bits= 416kbps that with the overload of the file transfer is near the 733 Kbps and almos six times the previous speed.

Now I need your help for testing the patch and the new speed in different profiles, and specially, to test the A2DP Stereo Audio Profile that cam work at this speed.

To install the patch, simply import this registry file.

[Patrick Y.]

Thanks to a registry key found by MikelSpikel in BTCEStack.dll I've managed to make a patch that solves the speed problem.

Now the UART connects at 921.600bps that allows to get the 733Kbps that is the max speed for the data channel on Bluetooth 1.1 and 1.2

In fact I've seen speeds up to 52KBytes/s usinf file transfer between my computer and my X51v: 52KB x 8 Bits= 416kbps that with the overload of the file transfer is near the 733 Kbps and almos six times the previous speed.

Now I need your help for testing the patch and the new speed in different profiles, and specially, to test the A2DP Stereo Audio Profile that cam work at this speed.

To install the patch, simply import this registry file.

WOW! Thanks!