Re: [Opensync-users] Working Configuration for Nokia E70

[Dr. H. E. P. <han...@um...>]

On Friday 01 September 2006 21:04,=20
ope...@li... wrote:
> Message: 5
> Date: Fri, 1 Sep 2006 11:43:05 +0200
> From: Daniel Gollub <dg...@su...>
> Subject: Re: [Opensync-users] Working Configuration for Nokia E70
> To: ope...@li...
> Message-ID: <200...@su...>
> Content-Type: text/plain; =A0charset=3D"iso-8859-1"
>
> On Thursday 31 August 2006 22:37, Dr. Hans Ekkehard Plesser wrote:
> > work. ?That is, Bluetooth works as long as computer and phone want to
> > talk to each other---sometimes it works, but mostly not. I don't quite
> > get what I need to do on the Linux side to make Bluetooth work reliably
> > (SuSE 10.0 on IBM ThinkPad T43p).
>
> Do you have other bluetooth devices to determine where exactly the problem
> is with the non-reliable bluetooth connection. Can you reproduce this with
> other devices? Is the bluetooth connection with other services reliable?
> For example Obex.

I'll try once I can get hold of another Bluetooth device.

> > Note that I need to run sync-obex-client as sudo to get access to the
> > Bluetooth/USB device. Which permissions do I need to change where to
> > access these ports as normal user (or into which group do I have to put
> > myself)? I'd be very grateful for any advice.
>
> Root access for bluetooth connection shouldn't be required.
> What does syncml-obex-client return if you run syncml-obex-client as
> non-root user?

imt-plesser-lp:plesser 106>syncml-obex-client -u 0 --identifier "PC Suite"=
=20
=2D-sync text/x-vcalendar calendar --wbxml
Received an transport error: Unable to connect to the interface
Received an transport error: Link Error
imt-plesser-lp:plesser 107>syncml-obex-client -u
Superuser privileges are required to access complete USB information.
=46ound 4 USB OBEX interfaces
Interface 0:
        Manufacturer:
        Product:
        Interface description:
Interface 1:
        Manufacturer:
        Product:
        Interface description:
Interface 2:
        Manufacturer:
        Product:
        Interface description:
Interface 3:
        Manufacturer:
        Product:
        Interface description:
Use '-u interface_number' to connect

> For usb i would recommend to add an udev rule. There is a description in
> the obex-client guide:
> http://libsyncml.opensync.org/wiki/obex-guide
> In section "Usage".

I tried that. According to information logged in the syslog, the rule is=20
identified and applied, but it does not help, I still get the errors above.=
 =20
I even tried a reboot on both sides.=20

I may have made a bit of a mess of the OBEX setup on my machine, since I=20
needed to replace the openobex that shipped with SuSE 10.0 with a newer one=
=20
(1.2).

> > I have also successfully transferred all contacts from my E70 to KDE PIM
> > using msynctool. I used the following configuration file for the
> > syncml-obex-client
> >
> > ? <type>5</type>
> > </config>
>
> Maybe your bluetooth problem is related to the wrong configuration.
> The <type>5</type> means USB connection - or did you copied your usb
> configuration? For bluetooth you should change <type> to 2.

I changed it to 2 when playing with Bluetooth.  The Bluetooth problems don'=
t=20
seem to be opensync related. I did get data sync'ed via Bluetooth once=20
yesterday, but since I have not been able to set up a stable connection.

> Maybe "calendar" in lowercase works...

No, any spelling other than "Calendar" just leads to syncml-obex-client=20
running happily without any effect ...

> Thanks for reporting and testing!
>
> You can do all a favor and add your device and known configuration at:
> http://www.opensync.org/wiki/DeviceCompatibilityList

I'll do so once my configuration is "productive".

Best,
Hans

=2D-=20
Dr. Hans Ekkehard Plesser
Associate Professor

Dept. of Mathematical Sciences and Technology
Norwegian University of Life Sciences

Phone +47 6496 5467
=46ax   +47 6496 5401
Email han...@um...
Home  http://arken.umb.no/~plesser