answered
2018-01-02 19:13:46 +0300
Something is rotten in the state of Denmark!
running dbus-send --print-reply --dest=org.bluez.obex / org.freedesktop.DBus.Introspectable.Introspect
on Sailfishos X gives :
[nemo@Sailfish ~]$ dbus-send
--print-reply --dest=org.bluez.obex / org.freedesktop.DBus.Introspectable.Introspect
method return time=1514913144.642008
sender=:1.23 -> destination=:1.2251
serial=75 reply_serial=2 string
"
<node><interface name="org.freedesktop.DBus.Introspectable"><method name="Introspect"><arg direction="out" name="xml" type="s">
</arg></method></interface><interface name="org.freedesktop.DBus.ObjectManager"><method name="GetManagedObjects"><arg direction="out" name="objects" type="a{oa{sa{sv}}}"> </arg></method><signal name="InterfacesAdded"><arg name="object" type="o"> <arg name="interfaces" type="a{sa{sv}}">
</arg></arg></signal> <signal name="InterfacesRemoved"><arg name="object" type="o"> <arg name="interfaces" type="as">
</arg></arg></signal> </interface><node name="org"></node>"</node>
whereas on OTH:
[nemo@Sailfish ~]$ dbus-send --print-reply --dest=org.bluez.obex / org.freedesktop.DBus.Introspectable.Introspect
method return time=1514913161.236943 sender=:1.25 -> destination=:1.953 serial=8 reply_serial=2
string "
<node>
<interface name="org.freedesktop.DBus.Introspectable">
<method name="Introspect">
<arg direction="out" name="xml" type="s">
</arg></method>
</interface>
<interface name="org.bluez.obex.Manager">
<method name="RegisterAgent">
<arg direction="in" name="agent" type="o">
</arg></method>
<method name="UnregisterAgent">
<arg direction="in" name="agent" type="o">
</arg></method>
<signal name="TransferStarted">
<arg name="transfer" type="o">
</arg></signal>
<signal name="TransferCompleted">
<arg name="transfer" type="o">
<arg name="success" type="b">
</arg></arg></signal>
<signal name="SessionCreated">
<arg name="session" type="o">
</arg></signal>
<signal name="SessionRemoved">
<arg name="session" type="o">
</arg></signal>
</interface>
</node>
EDIT:
It seems there's a branch of msyncd with Bluez5 support:
https://git.merproject.org/mer-core/buteo-syncfw/commits/bluez5/msyncd
EDIT #2:
did a tenative rebase, built and installed on xperia. got rid of the device error BUT found this instead
https://stackoverflow.com/questions/3537252/how-to-solve-bug-scheduling-while-atomic-swapper-0x00000103-0-cpu0-in-ts
when doing hcitool info dev_addr
:[
This is definitely a kernel driver issue; my theory is that the power saving cycle conflicts with the process of the driver trying to connect to the device.