To be precise...

A number of things have been intentionally omitted or written in an imprecise way for the sake of simplicity. Here are those I know of; signal any other to sgerwk@aol.com and I will add it here (or fix the page, depending on the error).

• the examples pretend that every object (a file, a sync alert, etc.) is always sent over the air as a single packet; in reality, it may be broken in several packets;
• the UUID 0x1105 is not only used for the OBEX push service, but also for the OBEX push profile; that it can occur only in one attribute is false; it is in both the service class list and in the profile descriptor list
• the search pattern in an SDP search is not a UUID but a list of UUIDs
• a range of SDP record attributes may be requested at once
• there should be some description of what a profile is
• when inquiring, {0x33, 0x8b, 0x9e} means inquiring all devices in range; in theory, changing 0x33 would allow to inquiry only for devices of a certain type, but in practice only 0x00 is defined, to inquiry only for devices in limited discoverable mode
• the answer to an inquiry includes the class of device (CoD), which specifies some of the features of the device; some mobiles expect certain features to be available, and ignore devices not having them; this means that a computer needs to have these set in order to be connected from a mobile; just enabling inquiry and page scan may not be enough:

  hciconfig hci0 piscan
  hciconfig hci0 class 0x5a0100