Peter Foot: "Visually Identify Your Bluetooth Stack"

[Darius Wey]

<div class='os_post_top_link'><a href='http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=7311b52f-185c-4657-8d6d-beb8e8e32989' target='_blank'>http://blog.opennetcf.org/pfoot/Per...6d-beb8e8e32989</a><br /><br /></div><i>"Since it's such a frequently asked question I've documented it here with some images which should hopefully clear up any confusion. The following screenshots show how to identify the Bluetooth stack on your Pocket Pc without writing any code or delving into the registry or system files."</i><br /><br /><img src="http://www.pocketpcthoughts.com/images/web/2003/wey-20050124-BTStack.jpg" /><br /><br />Microsoft MVP, Peter Foot, has written a short guide in a bid to help new Pocket PC users identify their Bluetooth stack. If you have the desire to find out more, feel free to read the guide at his personal blog.

[yanathin]

What is this "OpenNETCF.Net.Bluetooth library" and how do I apply it to my PPC? I personally hate Microsoft's Bluetooth stack, which I'm stuck with on my JAM... I can't even ActiveSync with my computer via Bluetooth, and Resco File Explorer doesn't let me send files view Bluetooth.

[Vincent M Ferrari]

What is this "OpenNETCF.Net.Bluetooth library"

It's for programmers... It's a library they can use in their applications to utilize Bluetooth and isn't a replacement for the drivers already provided for your hardware.

[adamz]

What about the Toshiba stack?

[Vincent M Ferrari]

Other than Toshiba, does anyone else use it?

[cxc4u]

What would make more sense would be an easy way to understand what profiles your device will support and what peripherals will match up with those standard profiles. At this point, I don't think Bluetooth's success hinges on usability. Rather, it is a matter of transparency, from both an audit (ex. What can it do) and a user-experience perspective. I understand the latter is hard to do, but the former really just needs clarity from the device manufacturers. For example, I was digging around for the meaning of A2DP and what it meant for myself, as an h4150 owner. I found out from the Bluetooth website through no small feat in site searching that the h4150 does not have native support for the profile itself (correct me if I'm wrong, HP!). So that means any A2DP stereo profile compliant Bluetooth widget (what a mouthful!) won't work without special drivers (see HP/Logitech-OEM Stereo Headphones).

[rmac]

I found out from the Bluetooth website through no small feat in site searching that the h4150 does not have native support for the profile itself (correct me if I'm wrong, HP!). So that means any A2DP stereo profile compliant Bluetooth widget (what a mouthful!) won't work without special drivers (see HP/Logitech-OEM Stereo Headphones).

I'm not sure that the HP/Logitech-OEM Stereo Headphones are A2DP compliant. All IPaqs need a special driver. Some people have been able to get the headphones to work on other PPCs with new stacks. However, I have a stack on my laptop that supposedly supports A2DP. They connect fine but are unable to transfer sound.

[Peter Foot]

What would make more sense would be an easy way to understand what profiles your device will support and what peripherals will match up with those standard profiles. At this point, I don't think Bluetooth's success hinges on usability. Rather, it is a matter of transparency, from both an audit (ex. What can it do) and a user-experience perspective. I understand the latter is hard to do, but the former really just needs clarity from the device manufacturers. For example, I was digging around for the meaning of A2DP and what it meant for myself, as an h4150 owner. I found out from the Bluetooth website through no small feat in site searching that the h4150 does not have native support for the profile itself (correct me if I'm wrong, HP!). So that means any A2DP stereo profile compliant Bluetooth widget (what a mouthful!) won't work without special drivers (see HP/Logitech-OEM Stereo Headphones).

Thats a good idea, I will look at adding profile details at some point. As a starter the Microsoft stack on Windows Mobile 2003 supports:-
SerialPortProfile
ObexPushProfile
AudioGateway (for Headset / Handsfree) (OEM Provided)

Windows Mobile Second Edition adds a standard implementation of AudioGateway service for Pocket PC Phone Edition/Smartphone devices

The Widcomm stack varies a lot between versions but it supports all of the above profiles and
ObexFileServer
DialUpNetworking
PersonalAreaNetworking

A2DP may be available on newer versions of the Widcomm stack but I don't have a device which supports it or appropriate headphones.

Peter