Re: [SyncEvolution] Syncing SonyEricsson T700 over bluetooth
Am 04.10.2010, 09:49 Uhr, schrieb Patrick Ohly <patrick.ohly(a)intel.com>:
On Sun, 2010-10-03 at 18:13 +0200, Karl Richter-Trummer wrote:
> I have installed the 1.0.99 beta from the unstable apt-repository for
> ubuntu 10.04, there i selected the sonyericsson profile, this didnt
> work,
> so i tried the older 1.1 profile too.
[Bluetooth transport error]
> Bluetooth is working, i regularly use this phone as a remote-control
> over
> bt, and on the phone, i see it gets connected when syncevolution is
> trying
> to sync.
The transport error is a bit misleading in such cases, the phone
probably doesn't like what it gets sent and then cuts the connection
prematurely.
If I read the HTML log correctly, you are only trying to synchronize
contacts. Is that correct?
I just tried all options (syncml 1.1 vs new, one-two-way, only contacts,
notes...) nothing worked. I really want to sync the calendar actually,
which doesnt work yet with syncevolution at all.
Typically this would have been my recommendation, but as you already
focus on that and have tried SyncML 1.1, I am a bit lost.
Just for completeness, can you quote your complete device config?
I appended the config.out
But somehow, yesterday, it worked for one sync, i get really strange
behavior:
I tried syncevolution --> wont work
I tried opensync (irMC) --> wont work
I tried wammu (AP) --> worked, but i cannot sync
I tried gnokii --> worked, but i cannot sync
I tried opensync with gnokii --> worked, but contacts are somehow screwed
up
I tried syncevolution --> worked just fine (no calendar)
Then somehow everything stopped working, without reconfiguration, wammu
has an error, syncevolution doesnt work (the same error as in first
tries), and opensync with irMC doesnt work
So i thought, my bluetooth must be buggy (once working, once not, while
connecting never seemed to be the problem) and installed the newest bluez
packages i could find (from 4.60 to 4.70, also updated obexd from 0.2 to
0.33) nothing changed.
Its a good idea that it might actually be the problem of the phone, i
would never have thought that, i will try a firmware update (dont know if
SE ever released one)
thank you patrick for the answer
Attachments:
- config.out (application/octet-stream — 1.5 KB)