(In reply to comment #24)
> Hey Patrick. I'm still at square one. I've tried resetting the phone,
> rebooting the computer, disabling sspmode, repairing, installed several
> different kernels,

I don't think it has anything to do with the host.

Have you tried "refresh-from-local" syncing of specific sources, for example
the address book?

If everything else fails, can you do a factory reset? Mind you, there's no
guarantee that you'll be able to put the data back on via SyncML afterward. But
it should help if the phone is really in a broken state.

> but still get errors like the following:
> 
> [ERROR] transport problem: SDP connection end unexpectedly
> [ERROR] transport problem: OBEX/Bluetooth transport error or problem on the
> peer
> 
> Even if there is a problem that is deeper than syncevolution, the error
> message it is emitting are not very helpful.

SyncEvolution is reporting everything that it sees (= "phone has
disconnected"). OBEX does not provide further error information in this case.