When I configure the irmc plugin with CFLAGS="-DOBEXFTP_DEBUG=5", I get the following on stderr after running the sync as described below.
cobex_write()
cobex_write() Data 19 bytes
cobex_write()
cobex_write() Data 50 bytes
cobex_write()
cobex_write() Data 72 bytes
cobex_disconnect()
bfb_io_close()
On seeing this, it looked to me like nothing's coming back from the modem so I had a look at cobex_handleinput(...). I'm wondering if the logic there works as intended - in that function, there are two tests to see if (c->cabletype == IRMC_CABLE_ERICSSON). The first of these returns from the function before the "Waiting for data" debug message appears. (And the second test is never reached.) I suspect this means that the multisync never picks up the response data.
I've compiled from multisync-0.82-1.tar.bz2 on the download page - perhaps I should be working off CVS?
Jason.
On Thu, 2005-12-15 at 21:37 +1100, Jason Grant wrote:
I've tried to use /dev/ttyACM0 and /dev/ttyACM1 to sync my SE K608i over USB without success.
When I specify one of these as the IrMC cable "other device", the phone wakes up with a "synchronizing" message. The multisync status reads "Getting first plugin changes...". After approximately 5 minutes, the phone reports "session failed" and multisync's IrMC log records "synchronization of 8 records succeeded". However, nothing is written by the backup plugin (which is the second plugin in my pair). After this, multisync will not connect to the phone again (reporting a "connection error"), until I replug the USB cable - I assume this is because the modem was left in an intermediate state.
Should I attempt to troubleshoot this further, or am I doing something that isn't supported by multisync? If the former, how best to gather more information what is going wrong?
Jason.
On Thu, 2005-12-15 at 16:27 +1100, Jason Grant wrote:
I have a SE K608i and would like to use multisync over USB.
I note that the connection type "cable" allows specification of "other device". I'm wondering if it is possible to somehow associate a device file with the relevant [serial] USB interface, and then refer to this device as the "other device" in the multisync UI. Does this sound plausible, and if so, how would I go about performing the preparatory step of associating the relevant USB interface with a /dev file?
Thanks,
Jason.
