[SailfishDevel] SyncML profile Nokia Services what is the difference

[Tone Kastlunger]

Perhaps the exposed bt profile of the syncml client matches first?

On Tue, Jul 9, 2019 at 11:51 PM deloptes <deloptes at gmail.com> wrote:
>
> Tone Kastlunger wrote:
>
> > If syncevolution works fine with n9, sfos should be working fine with it
> > too?
> >
>
> In theory yes. The problem is that many things changed since N9 on the
> mobile side. We have bluez5 and bluez5-obex and openobex. Bluez5 changed
> dramatically from bluez4 and code must be rewritten on many places, but the
> SyncML protocol itself did not change, so if you can make the two devices
> talk to each other, syncml should work as on N9.
>
> My question was related to the UUIDs used by Nokia and what is defined in
> the bueto-sync-plugins code. I went through some documents on the UUIDs and
> it requires more reading to understands how it all fits together, but from
> what I understand is that the vendor specific UUIDs are build on top of a
> generic base UUID defining the service.
>
> I've moved to working on the plugin side since yesterday and got so far that
> both "SyncML Server" and "SyncML Client" register and can be seen on the
> other side with sdptool browse:
>
> 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: SyncML Server
> Service RecHandle: 0x1000c
> Service Class ID List:
>   UUID 128: 00000001-0000-1000-8000-0002ee000001
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 26
>   "OBEX" (0x0008)
> Profile Descriptor List:
>   "" (0x00000001-0000-1000-8000-0002ee000001)
>     Version: 0x0100
>
> But it needs more work to understand few things, because I wonder now why it
> is trying to connect to "SyncML Client" and not to the server as expected
> and then it says "org.bluez.Profile1.Canceled, Canceled".
>
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/profile.c:ext_confirm()
> incoming connect from 00:11:22:33:44:55
> Jul 09 21:21:32 Sailfish bluetoothd[4649]:
> src/device.c:btd_device_add_uuid() device fujitsu, uuid
> 00000002-0000-1000-8000-0002ee000002
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/service.c:btd_service_ref()
> 0x1fa120: ref=2
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/profile.c:ext_confirm()
> SyncML Client authorizing connection from 00:11:22:33:44:55
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/profile.c:ext_auth()
> 00:11:22:33:44:55 authorized to connect to SyncML Client
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/profile.c:ext_connect()
> SyncML Client connected to 00:11:22:33:44:55
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/service.c:change_state()
> 0x1fa120: device 00:11:22:33:44:55 profile SyncML Client state changed:
> disconnected -> connecting (0)
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: SyncML Client replied with an
> error: org.bluez.Profile1.Canceled, Canceled
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/service.c:change_state()
> 0x1fa120: device 00:11:22:33:44:55 profile SyncML Client state changed:
> connecting -> disconnected (-111)
> Jul 09 21:21:32 Sailfish bluetoothd[4649]:
> src/device.c:device_profile_connected() SyncML Client Connection refused
> (111)
> Jul 09 21:21:32 Sailfish bluetoothd[4649]: src/service.c:btd_service_unref()
> 0x1fa120: ref=1
>
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org