You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, download files, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
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)
ActiveSync-Over-Bluetooth
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.
I guess those who were weary of picking up a bluetooth enabled Pocket PC because of the lack of bluetooth support have less of a reason to not get one!
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)
ActiveSync-Over-Bluetooth
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.
I guess those who were weary of picking up a bluetooth enabled Pocket PC because of the lack of bluetooth support have less of a reason to not get one!
Well, that may be true, but the last sentence sums it all up, its up to the OEMs - the bluetooth profile on my x50v, upgraded to WM5 is near useless. It was much better and useful in WM2003SE.
Don
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)
ActiveSync-Over-Bluetooth
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.
I guess those who were weary of picking up a bluetooth enabled Pocket PC because of the lack of bluetooth support have less of a reason to not get one!
Well, that may be true, but the last sentence sums it all up, its up to the OEMs - the bluetooth profile on my x50v, upgraded to WM5 is near useless. It was much better and useful in WM2003SE.
Don
Don -
You're absolutely right. I remember the debate (or lack thereof) between the Motorola mpx220 and the Audiobox SMT5600. Both ran WM2003SE for Smartphone. HTC (the manufacturer of the SMT5600) blessed us with a 3rd party bluetooth stack that offered better bluetooth handling (i.e. voice dialing via bluetooth was supported, and sync with ActiveSync via bluetooth was eaiser). The mpx220 on the other hand remained with the WM2003SE default stack and therefore did not offer much. HTC didn't have to do it... but I love them so much more because they did.
I just hope that because WM 5.0 comes with this updated bluetooth stack companies wont do something stupid and disable some profiles (like your case... and what Verizon and Sprint does).
Anyone else got their bluetooth crippled after WM 5.0?
-Tim
Linear Mode
