Hi, I was wondering if someone knows what exactly is hidden behind Nokia specific SyncML profiles. When I run sdptool browse <NOKIA N9 BT Addr>
Service Name: Nokia SyncML Server Service RecHandle: 0x1000c Service Class ID List: UUID 128: 00005601-0000-1000-8000-0002ee000001 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 26 "OBEX" (0x0008) Profile Descriptor List: "" (0x00005601-0000-1000-8000-0002ee000001) Version: 0x0100 Service Name: SyncML Client Service RecHandle: 0x1000b Service Class ID List: UUID 128: 00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 25 "OBEX" (0x0008) Profile Descriptor List: "" (0x00000002-0000-1000-8000-0002ee000002) Version: 0x0100 Service Name: Nokia OBEX PC Suite Services Service RecHandle: 0x10008 Service Class ID List: UUID 128: 00005005-0000-1000-8000-0002ee000001 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 24 "OBEX" (0x0008) Profile Descriptor List: "" (0x00005005-0000-1000-8000-0002ee000001) Version: 0x0100 When I run sdptool browse <Sailfish X BT Addr> Service Name: SyncML Client Service RecHandle: 0x1000a Service Class ID List: UUID 128: 00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 25 "OBEX" (0x0008) Profile Descriptor List: "" (0x00000002-0000-1000-8000-0002ee000002) Version: 0x0100 and probably the server with UUID 00000001-0000-1000-8000-0002ee000001 on Channel 26 I'm not sure which exactly Syncevolution is using but it has been working perfectly well with the N9 in the past 8y. I think it might have been using the OBEX thing as well. Does someone know what was behind those Nokia specific services _______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org