Q.:  Which profiles are offered by Broadcom BTW ? A.:  Broadcom offers several variants of its Widcomm Bluetooth software stack: a) BTW for Microsoft Windows 98 Second Edition and newer: SDK and Spy b) BTW-CE for Microsoft Windows Mobile (sometimes called BTWM) plus variants for embedded systems. BTW as of December 2010 offers OPP, FTP, IrMC, PBAP, and OMA DS. IrMC and OMA DS can be turned off by the user by turning off the PIM features, however, they are enabled on default. Together with this setting, you are able to change the PIM which is connected to this services. For each data store, another PIM can be selected. All four roles are visible as profile: SyncML-Server, SyncML-Client, IrMC-Service, IrMC-Push. Up to today, I am not able to disable PBAP. And, PBAP does not return a vCard to me. IrMC misses info.log. In BTW-CE, PBAP and IrMC work as expected, OMA DS and IrMC-Push are not offered. Q.:  How to start OMA DS over OBEX with BTW ? A.:  Although BTW is not an embedded software, the stack is quite picky. BTW expects fixed path names to access the database sources and ignores MIME media types. With OMA DS 1.2, only one database can be accessed per session. Examples: XML, WBXML, SAN for Contacts, Calendar, and Notes. The path for email is unknown. Q.:  How to start IrMC over the push service ? A.:  You connect to that service on RFComm layer. Other OBEX services do not work. You connect on the OBEX layer, and put a Push-Command as described on the IrMC specification, chapter 5.8: push.txt. Your device has to advertise a IrMC-Sync profile (UUID 1104) with a proper data store list attribute (0x0301), otherwise BTW tries to connect to a SyncML-Client service, starting the sync with a SAN.