Since mamaich has extracted the stack from acer....can it be ported to the current WM5 devices...
Theoretically it is possible - Himalaya devices proove this. But you would be unable to use BT headset. Other profiles including a2dp should work.
Thanks for replying
Related
Hello,
I know It may have been asked before,But i searching a lot and I couldnt find any thread which is mentioning that a BT stack Widcomm is available for mini with PAN support.What I could find was just Bluesoleil stack which is an evaluation version
no replies for long time. Nobody knows? :?:
No, the Widcomm stack isn't running on the Magician. The PAN profile is only supported by the Toshiba and Bluesoleil stack, which are working together with the Magician. The extension of the MS stack which you can find in another thread doesn't provide the PAN profile.
Hi all,
I am programming an OBEX bluetooth program for pocketPC platform, I see that there are different bluetooth stacks (Widcomm, Microsoft,...) on different pocket pcs, also I see that there are many ways to write OBEX bluetooth apps, either Winsock or using IObex COM objects and may be others.
My question is:
1. Do I have to write two implementtions to work with Widcomm BT stack and MS BT stack?
2. I am currently implementing BT functions using IObex COM interfaces, will this work on Widcomm BT stack??
3. any suggestions?
I hope to find some help here as usual
Thanks for your time...
Mohammad
mohgdeisat said:
Hi all,
I am programming an OBEX bluetooth program for pocketPC platform, I see that there are different bluetooth stacks (Widcomm, Microsoft,...) on different pocket pcs, also I see that there are many ways to write OBEX bluetooth apps, either Winsock or using IObex COM objects and may be others.
My question is:
1. Do I have to write two implementtions to work with Widcomm BT stack and MS BT stack?
2. I am currently implementing BT functions using IObex COM interfaces, will this work on Widcomm BT stack??
3. any suggestions?
I hope to find some help here as usual
Thanks for your time...
Mohammad
Click to expand...
Click to collapse
I think your best options is to make two components, because Widcomm BT implementation is completely different of M$ BT stack.
Fortunately both SDK are available.
Cheers,
.Fred
Thanks, dotfred, but if I have to do two implementations then where can find Widcomm BT stack SDK?? is it free to download? and what approximate percentage of PPC users use Widcomm BT Stack?
Any other suggestions guys?
Mohammad
mohgdeisat said:
Thanks, dotfred, but if I have to do two implementations then where can find Widcomm BT stack SDK?? is it free to download? and what approximate percentage of PPC users use Widcomm BT Stack?
Any other suggestions guys?
Mohammad
Click to expand...
Click to collapse
I have a Widcomm that works on my XDAII (I can give it), but for the rest, I really don't know. Don't forget that both stacks can't be active at the same time on the device, so you have to play with the registry and soft reset to activate one or another.
The biggest problem with Widcomm is that the bt headset doesn't work.
And the biggest problem of M$ stack is the lack of PAN and the BT manager is useless.
I think you should try to do it first for M$, when you succeeded then do it/try it with Widcomm, but you need a device that has it.
Cheers,
.Fred
ps.: for the sdk, here is an interesting article and a download link:
http://www.pocketpcdn.com/articles/...=78&atb.set(a_id)=7800&atb.perform(details)=&
OK, enclosed is helmi's version of the broadcomm (formerly known as widcomm) bluetooth stack v1.7.6.0500 for himalaya.
This stack works perfectly with the exception of one thing. The handsfree profile won't route audio to any headset.
Apparently it's got something to do with the included wavedev.dll and audiogw.dll not being compatible with the himalaya. AFAIK, it should just be a case of tweaking the wavedev.dll file
Have any devs with himalayas (or other devices) got any ideas on how to fix this? We all know that the widcomm stack is FAR superior to the MS version. A universal widcomm stack would benefit the whole community.
Link to DL
Hey all,
I'm trying to pair a PPC with SonyEricsson's bluetooth watch MBW-150 to use moneytoo's brilliant SmartWatchM. This worked fine with my old PPC running the Microsoft bluetooth stack. My new PPC (LG KS20) uses the Widcomm/Broadcom stack, believed to be cleverer than the MS stack.
Here's the problem:
The PPC will not pair. The watch does not send out information according to the BT Service Discovery Protocol (SDP), because it was never meant to be paired with anything else than SE phones. The Microsoft stack didn't care and paired nonetheless. The Widcomm/Broadcom stack, however, will pair with BT devices only if it finds a supported profile. The watch uses the Serial Port Profile (SPP), but it doesn't say so, not sending any SDP information to the PPC. The PPC would support SPP of course, but doesn't pair as it has no way of knowing that the watch supports this profile.
In the end, when I try to pair, the PPC will see the watch but doesn't know what to do with it, and will not pair.
Is there any way of pairing (using a Widcomm/Broadcom stack) without SDP information? Can I enforce pairing with the watch? (I can easily insert serial port settings in the reg manually.)
Or can I somehow change my BT stack? I've read that the only way to do that would mean changing the ROM ... :-(
Any ideas? Any help would be greatly appreciated!
Many thanks,
N.
I'm using 32feet.NET library that supports only MS BT Stack. Fortunately I have just found this lib http://franson.com/bluetools/ that seems to support Widcomm Stack. I will try it soon.
EDIT:
What BT stack is on it? Is it Broadcom? Widcomm on Motorola Q9 is ok and lets you to pair device without any service but Broadcom on a one HP iPAQ I have tested doesnt.
EDIT2:
Not a good news. Franson Bluetools doesnt work on smartphones. I dont know much about this stuff but from what I have read it seems like pairing/bonding request is possible only in MS BT stack (via some non official function) and it's disabled in other BT stacks because of security issues.
Thanks for chiming in, moneytoo!
moneytoo said:
What BT stack is on it? Is it Broadcom? Widcomm on Motorola Q9 is ok and lets you to pair device without any service but Broadcom on a one HP iPAQ I have tested doesnt.
Click to expand...
Click to collapse
This may be a noob question but: How do I tell whether it's Broadcom or Widcomm? Is there still a difference since Broadcom bought Widcomm?
Anyway, BT manager will not pair ("no supported protocol found").
moneytoo said:
it seems like pairing/bonding request is possible only in MS BT stack (via some non official function) and it's disabled in other BT stacks because of security issues.
Click to expand...
Click to collapse
I'm afraid that's true. I haven't found anything so far that would point me to a workaround, backdoor or anything - and as my KS20 is a company phone I can hardly change the ROM
Let's hope someone comes up with an idea!
Anyone tried to install MS Bluetooth Stack?
I dont think you can just "install" a BT stack.... although I wish you could...
it is possible tbough with a lot of driver modifications.
For sure it will be required to cook the MS bluetooth stack into the ROM instead of just install, but many other parts of the rom are using the widcomm stack so it will be a big job.
Its a shame, because i found the sound via A2DP was better via the MS stack, and other users have found the widcomm stack unreliable with car kits or hands free headsets.
I think a better approach would be for a updated widcomm stack
whether they update the widcomm stack, or change it for MS, I don't care, I just wish HTC would hurry up and do it... so many people have problems with it.
I've tried and failed... The Leo and the Rhodium use different BT/Wifi chipsets that arent compatible with the MS BT Stack
Oh dear, that doesn't sound good.
Thank you very much for trying to do it anyway NRG.
NRGZ28 said:
I've tried and failed... The Leo and the Rhodium use different BT/Wifi chipsets that arent compatible with the MS BT Stack
Click to expand...
Click to collapse
Not compatible....