What Bluetooth profiles does Windows Mobile support?

There is a huge amount of debate on the forums as to what Bluetooth profiles Windows Mobile devices support.  Below is the list that we support natively in the Microsoft Stack in AKU 1.1 of Windows Mobile 5.0 and beyond:

Generic Access Profile (GAP)
Generic Object Exchange Profile (GEOP)
Serial Port Profile (SPP)
Dial-up Networking (DUN) Profile
Hands-Free Profile (HFP)
Headset Profile (HSP)
Human Interface Device (HID) Profile
Object Push Profile (OPP)
Advanced Audio Distribution Profile (A2DP)
Audio/Video Remote Control Profile (AVRCP)

The confusion typically starts because it is up to to the OEM to choose which ones they implement or to add additional support for other profiles.

Comments (7)
  1. Keith says:

    I am an owner of a Dell AXIM x51v PDA. The ROM version is xxx.1.1.0 (WM5 AKU 1.1). Till today, the Dell PDA still has little support for the Bluetooth profiles. The only profiles that I have been able to see are : SPP, DUN, and GAP. Even though some profiles visible, the profiles do not work all the time. The only bluetooth device that works (all the time) is a GPS device which does not require pairing so no obvious profiles are visible. my $2

  2. Jason says:

    I thought A2DP was expected in AKU 2.0.

  3. Peter Foot says:

    Keith, the OEM has the last word on what profiles are supported, I also believe that some of the profiles are only part of the Phone Edition OS (such as Headset etc) so are excluded from non-phone devices such as the Dell. Some of the profiles are essentially invisible to the end user, for example when you pair with a bluetooth keyboard HID support will be used but there isn’t any specific UI to show it’s presence. Also all devices running the MS Bluetooth stack have a standard OBEX (OPP) listener which is turned on/off through the Settings > Connections > Beam page. And is used by the Beam context menu option on PIM items and files in File Explorer.

    Also I think as Jason has commented A2DP (and I assume AVRCP, although this hasn’t been mentioned before) is due in AKU 2.0. It’s not present on current AKU 1.1 devices.


  4. Zak says:

    Like I commented earlier on this blog, this "not installing bluetooth services" is in my oppinion a huge mistake from both OS and Hardware makers. Everybody is talking about networking everything together, and PDA´s ,that should be the "inteface" for all of this, can´t even get a decent BT connection?

    Just my 2 cents and a dollar…. This post is perhaps written in anger over the newest x51v ROM(06) update that still doesn´t install the AKU 2.0, but perhaps the patent infrigment claims are legit…..)

  5. Zak says:

    My question for Peter Foot:

    Why would one limit the BT services of a Headset only to work with WM% phone edition, why?

    I just can´t stand when somebody doesn´t try to reach for their full potetial, and I feel that this is what MS is lacking. because a BT headset wouldn´t make the PDA a worse machine would it?

    Like I said go to http://www.aximsite.com forums and look at what people have to say about WM 5.0

  6. Peter Foot says:

    Hey Zak

    I’m not saying I agree with the policy – just that that is the pattern it seems to follow, only Dell can really answer the question.

    One annoying fact is that you have to do a manual registry tweak to get Voice Command to work with the BT headset on a WM5 device, but once you’ve done this it’s incredibly useful, and you could also use this to control the non-phone features on the Dell if it was supported, search contacts, calendar, media etc


  7. jdee says:

    It could well be that it was technical limitations that meant no A2DP realeas in AKU1.1 devices, hence delay to AKU2. Just because its included in the AKU doesn’t mean it will automatically work in the real world with whatever hardware the ODM/OEM puts it in.

    I’d be happy to wait if it means its going to work better when it does get released.

Comments are closed.

Skip to main content