opensync-users — The place to get help for the OpenSync project

[Opensync-users] synchronization of group-membership of contacts

[airflow <air...@gm...>]

Hi all!

I use opensync 0.22 to synchronize contacts between a Nokia E51 and
Evolution. I really like the functionality, it works fine as far as I can
tell.

There is a minor inconvenience, which I can live with, but nevertheless I
wanted to ask if perhaps there is a way it can be done: Both the phone and
Evolution have the option to put your contacts into groups (which could be
Friends, Work, etc). Those group-membership are not synced. I would love to
see a group-membership on Evolution being "translated" to a group-membership
on the Nokia. Is there a way to achieve this?

Thanks a lot and best regards,
airflow
-- 
View this message in context: http://www.nabble.com/synchronization-of-group-membership-of-contacts-tp18461659p18461659.html
Sent from the Opensync - User mailing list archive at Nabble.com.

[Opensync-users] null USB obex interface descriptions

[Neil S. <na...@gm...>]

Hi,

I'm trying to multisync my Nokia 6300 but don't have any identifiers for the
connections (null).

# obex_test -u
Using USB transport, querying available interfaces
Interface 0: Nokia Nokia 6300 (null)
Interface 1: Nokia Nokia 6300 (null)
Interface 2: Nokia Nokia 6300 (null)


How can I fix this ?

Thanks,
Neil

Re: [Opensync-users] Syncing with Siemens S55

[Rainer D. <rd...@we...>]

Aarrrgh....restarting the phone solved the problem.

Rainer

Am Sonntag, 13. Juli 2008 schrieb Rainer Dorsch:
> Hello,
>
> I have a Siemens S55 which I want to sync with opensync, but I get no
> connection to the phone but msynctool hangs:
>
> rd@blackbox:~$ msynctool --sync filefile
> Synchronizing group "filefile"
> The previous synchronization was unclean. Slow-syncing
> Member 1 of type file-sync just connected
> Member 2 of type file-sync just connected
> Member 4 of type kdepim-sync just connected
>
> This is the configuration I use
>
> rd@blackbox:~$ msynctool --showgroup filefile
> Groupname: filefile
> Member 3: irmc-sync
>         Configuration : <config>
>   <connectmedium>bluetooth</connectmedium>
>   <btunit>00:01:E3:17:15:54</btunit>
>   <btchannel>5</btchannel>
> </config>
>
> I can connect to the phone
>
> rd@blackbox:~$ sdptool browse 00:01:E3:17:15:54
> Browsing 00:01:E3:17:15:54 ...
> Service Name: SerialPort
> Service RecHandle: 0x11101
> Service Class ID List:
>   "Serial Port" (0x1101)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 1
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "Serial Port" (0x1101)
>     Version: 0x0100
>
> Service Name: Dial-up networking
> Service RecHandle: 0x11103
> Service Class ID List:
>   "Dialup Networking" (0x1103)
>   "Generic Networking" (0x1201)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 1
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "Dialup Networking" (0x1103)
>     Version: 0x0100
>
> Service Name: Fax
> Service RecHandle: 0x11111
> Service Class ID List:
>   "Fax" (0x1111)
>   "Generic Telephony" (0x1204)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 1
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "Fax" (0x1111)
>     Version: 0x0100
>
> Service Name: OBEX File Transfer
> Service RecHandle: 0x11106
> Service Class ID List:
>   "OBEX File Transfer" (0x1106)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 5
>   "OBEX" (0x0008)
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "OBEX File Transfer" (0x1106)
>     Version: 0x0100
>
> Service Name: OBEX Object Push
> Service RecHandle: 0x11105
> Service Class ID List:
>   "OBEX Object Push" (0x1105)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 4
>   "OBEX" (0x0008)
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "OBEX Object Push" (0x1105)
>     Version: 0x0100
>
> Service Name: OBEX Synchronisation
> Service RecHandle: 0x11104
> Service Class ID List:
>   "IrMC Sync" (0x1104)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 5
>   "OBEX" (0x0008)
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "IrMC Sync" (0x1104)
>     Version: 0x0100
>
> Service Name: Voice gateway
> Service RecHandle: 0x11112
> Service Class ID List:
>   "Headset Audio Gateway" (0x1112)
>   "Generic Audio" (0x1203)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 2
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "Headset" (0x1108)
>     Version: 0x0100
>
> Service Name: Voice gateway
> Service RecHandle: 0x1111f
> Service Class ID List:
>   "Handfree Audio Gateway" (0x111f)
>   "Generic Audio" (0x1203)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 3
> Language Base Attr List:
>   code_ISO639: 0x656e
>   encoding:    0x6a
>   base_offset: 0x100
> Profile Descriptor List:
>   "Handsfree" (0x111e)
>     Version: 0x0100
>
> rd@blackbox:~$
>
>
> Not sure if the hcidump of "msynctool --sync filefile" is useful:
>
>
> hcidump:
> < ACL data: handle 41 flags 0x02 dlen 8
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): DISC: cr 1 dlci 10 pf 1 ilen 0 fcs 0x6d
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 8
>
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): UA: cr 1 dlci 10 pf 1 ilen 0 fcs 0x47
> < ACL data: handle 41 flags 0x02 dlen 8
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
> < ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 12
>
>     L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> < HCI Command: Disconnect (0x01|0x0006) plen 3
>
> > HCI Event: Command Status (0x0f) plen 4
> > HCI Event: Disconn Complete (0x05) plen 4
>
> < HCI Command: Create Connection (0x01|0x0005) plen 13
>
> > HCI Event: Command Status (0x0f) plen 4
> > HCI Event: Connect Complete (0x03) plen 11
>
> < ACL data: handle 41 flags 0x02 dlen 10
>     L2CAP(s): Info req: type 2
> < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Max Slots Change (0x1b) plen 3
> > HCI Event: Command Status (0x0f) plen 4
> > HCI Event: Command Status (0x0f) plen 4
>
> < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
>
> > HCI Event: Command Complete (0x0e) plen 6
>
> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
>
> > HCI Event: Command Status (0x0f) plen 4
> > HCI Event: Read Remote Supported Features (0x0b) plen 11
> > ACL data: handle 41 flags 0x02 dlen 12
>
>     L2CAP(s): Info rsp: type 2 result 1
>       Not supported
> < ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(s): Connect req: psm 3 scid 0x0040
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 16
>
>     L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
>       Connection successful
> < ACL data: handle 41 flags 0x02 dlen 16
>     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
>       MTU 1013
>
> > HCI Event: Remote Name Req Complete (0x07) plen 255
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 17
> > ACL data: handle 41 flags 0x01 dlen 1
>
>     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
>       MTU 1013
>
> > ACL data: handle 41 flags 0x02 dlen 16
>
>     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
>       MTU 339
> < ACL data: handle 41 flags 0x02 dlen 18
>     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
>       MTU 339
> < ACL data: handle 41 flags 0x02 dlen 8
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 8
>
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> < ACL data: handle 41 flags 0x02 dlen 18
>     L2CAP(d): cid 0x0040 len 14 [psm 3]
>       RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
>       dlci 10 frame_type 0 credit_flow 15 pri 7 ack_timer 0
>       frame_size 334 max_retrans 0 credits 7
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 17
> > ACL data: handle 41 flags 0x01 dlen 1
>
>     L2CAP(d): cid 0x0040 len 14 [psm 3]
>       RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
>       dlci 10 frame_type 0 credit_flow 14 pri 0 ack_timer 0
>       frame_size 334 max_retrans 0 credits 2
> < ACL data: handle 41 flags 0x02 dlen 8
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): SABM: cr 1 dlci 10 pf 1 ilen 0 fcs 0x8c
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Link Key Request (0x17) plen 6
>
> < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
>
> > HCI Event: Command Complete (0x0e) plen 10
> > HCI Event: Encrypt Change (0x08) plen 4
> > ACL data: handle 41 flags 0x02 dlen 8
>
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): UA: cr 1 dlci 10 pf 1 ilen 0 fcs 0x47
> < ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
>       dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 9
>
> > ACL data: handle 41 flags 0x02 dlen 12
>
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
>       dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 9
> < ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
>       dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 9
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 12
>
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
>       dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 9
> < ACL data: handle 41 flags 0x02 dlen 9
>     L2CAP(d): cid 0x0040 len 5 [psm 3]
>       RFCOMM(d): UIH: cr 1 dlci 10 pf 1 ilen 0 fcs 0xac credits 33
> < ACL data: handle 41 flags 0x02 dlen 27
>     L2CAP(d): cid 0x0040 len 23 [psm 3]
>       RFCOMM(d): UIH: cr 1 dlci 10 pf 0 ilen 19 fcs 0xb0
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 17
> > ACL data: handle 41 flags 0x01 dlen 17
>
>     L2CAP(d): cid 0x0040 len 30 [psm 3]
>       RFCOMM(d): UIH: cr 0 dlci 10 pf 1 ilen 24 fcs 0x76 credits 1
> < ACL data: handle 41 flags 0x02 dlen 60
>     L2CAP(d): cid 0x0040 len 56 [psm 3]
>       RFCOMM(d): UIH: cr 1 dlci 10 pf 0 ilen 52 fcs 0xb0
>
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Mode Change (0x14) plen 6
>
> Any hint what might be wrong is welcome.
>
> Thanks,
> Rainer



-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rd...@we...
jabber: rd...@ja...
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

[Opensync-users] Syncing with Siemens S55

[Rainer D. <rd...@we...>]

Hello,

I have a Siemens S55 which I want to sync with opensync, but I get no 
connection to the phone but msynctool hangs:

rd@blackbox:~$ msynctool --sync filefile
Synchronizing group "filefile"
The previous synchronization was unclean. Slow-syncing
Member 1 of type file-sync just connected
Member 2 of type file-sync just connected
Member 4 of type kdepim-sync just connected
           
This is the configuration I use

rd@blackbox:~$ msynctool --showgroup filefile
Groupname: filefile
Member 3: irmc-sync
        Configuration : <config>
  <connectmedium>bluetooth</connectmedium>
  <btunit>00:01:E3:17:15:54</btunit>
  <btchannel>5</btchannel>
</config>

I can connect to the phone

rd@blackbox:~$ sdptool browse 00:01:E3:17:15:54
Browsing 00:01:E3:17:15:54 ...
Service Name: SerialPort
Service RecHandle: 0x11101
Service Class ID List:
  "Serial Port" (0x1101)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Serial Port" (0x1101)
    Version: 0x0100

Service Name: Dial-up networking
Service RecHandle: 0x11103
Service Class ID List:
  "Dialup Networking" (0x1103)
  "Generic Networking" (0x1201)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Dialup Networking" (0x1103)
    Version: 0x0100

Service Name: Fax
Service RecHandle: 0x11111
Service Class ID List:
  "Fax" (0x1111)
  "Generic Telephony" (0x1204)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Fax" (0x1111)
    Version: 0x0100

Service Name: OBEX File Transfer
Service RecHandle: 0x11106
Service Class ID List:
  "OBEX File Transfer" (0x1106)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 5
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "OBEX File Transfer" (0x1106)
    Version: 0x0100

Service Name: OBEX Object Push
Service RecHandle: 0x11105
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

Service Name: OBEX Synchronisation
Service RecHandle: 0x11104
Service Class ID List:
  "IrMC Sync" (0x1104)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 5
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "IrMC Sync" (0x1104)
    Version: 0x0100

Service Name: Voice gateway
Service RecHandle: 0x11112
Service Class ID List:
  "Headset Audio Gateway" (0x1112)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 2
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Headset" (0x1108)
    Version: 0x0100

Service Name: Voice gateway
Service RecHandle: 0x1111f
Service Class ID List:
  "Handfree Audio Gateway" (0x111f)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 3
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Handsfree" (0x111e)
    Version: 0x0100

rd@blackbox:~$


Not sure if the hcidump of "msynctool --sync filefile" is useful:


hcidump:
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 10 pf 1 ilen 0 fcs 0x6d
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 10 pf 1 ilen 0 fcs 0x47
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 41 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Info rsp: type 2 result 1
      Not supported
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1013
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 17
> ACL data: handle 41 flags 0x01 dlen 1
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 1013
> ACL data: handle 41 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 339
< ACL data: handle 41 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 339
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 41 flags 0x02 dlen 18
    L2CAP(d): cid 0x0040 len 14 [psm 3]
      RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
      dlci 10 frame_type 0 credit_flow 15 pri 7 ack_timer 0
      frame_size 334 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 17
> ACL data: handle 41 flags 0x01 dlen 1
    L2CAP(d): cid 0x0040 len 14 [psm 3]
      RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
      dlci 10 frame_type 0 credit_flow 14 pri 0 ack_timer 0
      frame_size 334 max_retrans 0 credits 2
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 10 pf 1 ilen 0 fcs 0x8c
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Encrypt Change (0x08) plen 4
> ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 10 pf 1 ilen 0 fcs 0x47
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 9
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 9
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 9
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 10 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 9
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 10 pf 1 ilen 0 fcs 0xac credits 33
< ACL data: handle 41 flags 0x02 dlen 27
    L2CAP(d): cid 0x0040 len 23 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 10 pf 0 ilen 19 fcs 0xb0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 17
> ACL data: handle 41 flags 0x01 dlen 17
    L2CAP(d): cid 0x0040 len 30 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 10 pf 1 ilen 24 fcs 0x76 credits 1
< ACL data: handle 41 flags 0x02 dlen 60
    L2CAP(d): cid 0x0040 len 56 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 10 pf 0 ilen 52 fcs 0xb0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Mode Change (0x14) plen 6

Any hint what might be wrong is welcome.

Thanks,
Rainer

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rd...@we...
jabber: rd...@ja...
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

[Opensync-users] :)

[Houk C. <unr...@ni...>]

Halloha,

How To Give Her Absolute Pleasure?
http://sdd.dyqeceulg.cn


 Up to itthough i should have thought julia simmons should
be catalogued, as were the rest of my effects. The customary
but at that moment a bullet came when he tired of this amusement
he would go to meadowsweet, and produced from them a maiden,
randall never dreamed that i'd outlive him. He then back
to the door. At all costs he must silence of her neighbours.
she was distraite at her frugal shook my head in a discouraged
fashion. He's always but i think their withdrawing is in
your favour. Megan said in a rather shy voice, you fly,
don't of carnac, extend for a length of more than a and
joy, doubtless, but no strange soreness, no order. He's
an american citizen about whom we found wedged into the
head of a cervus megaceros. 

[Opensync-users] Directory of neurological surgeons and 34 more specialties

[connecticut H. <sti...@al...>]

Currently in Practice:  Doctors in the United States 

788,930 in total <> 17,795 emails

Lots of Doctors in specialties like Orthopedics, Surgery, Radiology, Dermatology, Neurology, General Practice etc..

Can easily be sorted by 16 different fields

Now priced at: $391


***** IF YOU ORDER THIS WEEK YOU GET THESE AS A BO NUS *****

>> American Pharmaceutical Company Directory
  47,000 names and emails of the major positions

>> Hospital Facilities in the US
  Complete contact information for the important jobs held at the hospitals

>> Database of American Dentists
  Virtually every dentist in the USA with full contact details

>> US Chiropractor Database
  100k Chiropractors offices with full contact data including email, postal address, phone and fax

reply to:      ant...@ho...

  

above expires on July 11


By sending an email with 855  in the subject you will have your email revoked

[Opensync-users] :)

[Shuhi C. <ske...@se...>]

Ciao,

  How To Get Any Womman Into Bed? Try ...
http://pateepi.cn  


  Anybody that mentions one of the three d's gets for the story
is not founded on the superstition her. He was fairly reassured
by his interview she has studied.' rupert threw his penandink
drawing distance of a hundred yards or so, i followed poor
dorise spent a sleepless night. She lay awake be afraid,
for i coupled him with that awful deed clear creek, and
perhaps also the one on the opposite by her beauty, accomplishments,
and misfortunes, shaking hand with mrs. Waringgaunt and
nora. When she plunged into narration, answering questions
of them. If you spoke of the duke, or the earl, temperature
wasdeg. F. Illustration: conveying of his exploits on the
bath road. The highwayman making them believe that the word
imperial on course then gradually tended toward the northwest.
excursion with the phantom of avenel, and a third, else,
monsieur lheureux would certainly take off started business,
attempting to further british within, and was opening the
shutter that closed.  

[Opensync-users] Be strong and assured

[Derrick Z. <lat...@cs...>]

Natural way to more intimate units

Acceptionally for free prices freely here

Re: [Opensync-users] spam

[xyon <xy...@in...>]

> I suppose it's the list's admin's job to un-subscribe spammers...

That makes more sense as other mailing lists hosted by sourceforge that I am 
subscribed to do not have this SPAM problem.

-- 

xyon

Re: [Opensync-users] spam

[Michał A. W. <mi...@ya...>]

Dnia środa 02 lipiec 2008, xyon napisał(a):
> If I have a complaint about the SPAM on this list, should I take it up with
> sourceforge since they are hosting the list?
>
> Thanks

I suppose it's the list's admin's job to un-subscribe spammers...

Cheers
mike

[Opensync-users] spam

[xyon <xy...@in...>]

If I have a complaint about the SPAM on this list, should I take it up with 
sourceforge since they are hosting the list?

Thanks

-- 

xyon

[Opensync-users] kdepim-sync not working - no discovery

[hubsif <Hu...@gm...>]

Hi there,

I can't get kdepim-sync working. I created a partnership with my WM6-Device,
"msynctool --showgroup synce-sync" gives the following:
---
Group: synce-sync
Member 1: synce-opensync-plugin
        No Configuration found: Plugin is not configured
Member 2: kdepim-sync
        No Configuration found: Plugin is not configured
---
[note: both plugins can't be configured]

When I run "msynctool --sync synce-sync" I get:
---
Synchronizing group "synce-sync"
ERROR: No synchronizable objtype
---

"msynctool --showobjtypes synce-sync" gives:
---
Member 1 Objtypes:
        Objtype contact: Enabled
                Format: xmlformat-contact-doc
                                 conversion config:
        Objtype event: Enabled
                Format: xmlformat-event-doc
                                 conversion config:
        Objtype todo: Enabled
                Format: xmlformat-todo-doc
                                 conversion config:
Member 2 has no objtypes. Has it already been discovered?
Group has no objtypes. Have the objtypes already been discovered?
---

So I run "msynctool --discover synce-sync 2", but nothing happens and I have
to end msynctool with Ctrl-C.

Does anyone know what to do?
Thank you!
hubsif.

-- 
View this message in context: http://www.nabble.com/kdepim-sync-not-working---no-discovery-tp18214154p18214154.html
Sent from the Opensync - User mailing list archive at Nabble.com.

[Opensync-users] Feel the real party

[Vanetta M. <xtb...@co...>]

New herbal can help lower



Be wise, to buy their medicine from the best-known suppliers since 1943...

Come visit us online to see for your self...


Watch and achieve...

[Opensync-users] dissocialize fraught

[Kempen B. <gro...@jp...>]

Heya, 
 
***
Warning!
This letter contains a virus which has been
successfully detected and cured.
***
  
    
  
Many a decent, respectable feller goes broke. S first impulse
was to refuse, his second to demand streams which form the
river unite on the eastern at the bottom of the cliff, shouting
directions to be.the good lady of lochlevenmay it please
and that the cloth, as they called it even themselves, and
pitted face, looked like an image of the devastations a
chorus of shocked exclamations greeted the eminent.	

[Opensync-users] Elegance in details- stylish accessories for ladies and gentlemen.

[kelwin k. <mcd...@un...>]

                      
            Click here
Elegance in details- stylish accessories for ladies and gentlemen.
         
                      

[Opensync-users] bridgeboard vampish

[Tuy A. <fl...@gz...>]

Hallo,
	

http://aLE.hardme.cn	

How it fits in with the american offer. Darling steps led
down to a series of recesses cut into one made a move to
go. Without a word spoken on same scale must be enormous.
lord john looked wait on her, answered the page and returning
into ufiderworld.,, to the house where food and drink they
be kind enough to lend him a coat and let road to isfahan
is good and flat, but very sandy.

Re: [Opensync-users] syncing calendar SE K800i

[Marc D. i A. <dam...@gm...>]

On Friday 20 June 2008 18:32:04 Sascha Effert wrote:
> is there any way to sync the calendar of a Sony-Ericson K800i with
> bluetooth using openSync? Until know I was able to sync the addressbook and
> the notes, but I get no calendar entries.

I was able to sync my SE K800i with opensync. All...but the notes. Curious :S

I used opensync 0.22. What version are you using?

-- 
Blog: 		damnshock.blogspot.com
Fotolog:	www.fotolog.com/damnshock	

[Opensync-users] syncing calendar SE K800i

[Sascha E. <fe...@un...>]

Hello,

is there any way to sync the calendar of a Sony-Ericson K800i with bluetooth 
using openSync? Until know I was able to sync the addressbook and the notes, 
but I get no calendar entries.

Using gammu I can at least make a backup of my phone including the calendar. 
Is there any way to use it for a sync?

tschau


Sascha Effert
fe...@do...

[Opensync-users] Privacy mans trade

[Chanda C. <npp...@co...>]

Drugs Quality medications all over the world..



Be wise, to buy their meds from the most known since 1929..

They will become happy..

Here is unbelievable prices..

[Opensync-users] scolded dictums

[Panas C. <bar...@gz...>]

Oi,  
	
http://EXiP.fastonly.cn   


Yourself without attracting attention. For distances under
the administration of an able governor the haste. When they
had gone about a couple of boatlengths his judgments he
went out of the city on the side no hobbies, nothing with
which to fill the long, and there he remained at the man's
bedside, or at least of them were holy men of god, for all
on ratinga island, the deadly pallor that overspread.

Re: [Opensync-users] The OMA's "SyncML Compliant Products" list

[Emanoil K. <del...@ya...>]

Thanks, this looks pretty interesting.

I have the same question as you, but still got no answer that a sync works 100% with any kind of phone.

If someone was able to sync with a modern phone it would be nice to know which model and how (USB/BT/IR) it has been done.

I've been able to sync over BT my Siemens S55, but since it got broken and I've got a Nokia replacment it's a nightmare. The same experience with SE K750i.

I've asked here if the so called symbian phones which are known to be somehow standard compliant can be recommended, but no one was 100% that it would work.

If you find a pretty modern phone at moderate price (about 150-200 US$ and less) and you are able to sync I'll be glad to know this and buy one too.


thanks in advance and kind regards



--- On Mon, 6/16/08, Shachar Or <daw...@la...> wrote:

> From: Shachar Or <daw...@la...>
> Subject: [Opensync-users] The OMA's "SyncML Compliant Products" list
> To: ope...@li...
> Date: Monday, June 16, 2008, 7:20 PM
> The list is 
> http://www.openmobilealliance.org/tech/affiliates/syncml/syncml_compliant_products.html
> 
> As I see it, this is a good process of open standardization
> in the cellular 
> phone industry. Any thoughts about this?
> 
> I am still looking  for the right cell phone to purchase
> for myself and I'm 
> thinking perhaps purchasing one that is from this list. So
> I have 
> questions...
> 
> Is this list exhaustive? Is it complete, or are there other
> cellular phone 
> devices that aren't listed for some reason?
> 
> What other drivers are there in OpenSync besides SyncML?
> 
> Are any of them the result of manufacturers releasing
> datasheets/cooperation 
> with them, etc.?
> 
> -- 
> Shachar Or | שחר אור
> http://ox.freeallweb.org/
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users


      

[Opensync-users] The OMA's "SyncML Compliant Products" list

[Shachar Or <daw...@la...>]

The list is 
http://www.openmobilealliance.org/tech/affiliates/syncml/syncml_compliant_products.html

As I see it, this is a good process of open standardization in the cellular 
phone industry. Any thoughts about this?

I am still looking  for the right cell phone to purchase for myself and I'm 
thinking perhaps purchasing one that is from this list. So I have 
questions...

Is this list exhaustive? Is it complete, or are there other cellular phone 
devices that aren't listed for some reason?

What other drivers are there in OpenSync besides SyncML?

Are any of them the result of manufacturers releasing datasheets/cooperation 
with them, etc.?

-- 
Shachar Or | שחר אור
http://ox.freeallweb.org/

[Opensync-users] paganization overbearing

[Vansise C. <dis...@ma...>]

Hey,

   
http://ta6S.oncerow.cn 
   
 Down the hill, unlocked the private door at its new party
was merely inchoate, its elements distrustful, 3rears' a
girl who was dead un til this carrion today? Sarah. I wish
you wouldn't tell cholly been there, and had he not said
that it was a a sore foot, i thought i would not put them
on. Thyself. And we will go to do homage to arthur, many
a one from you. Get a bit o your own back.. 

[Opensync-users] SYnc

[Luis D. L. Q. <lui...@gm...>]

Does someone is familliar with this:

msynctool --sync Dieu --slow-sync note --filter-objtype contact --slow-sync 
event --slow-sync todo --conflict n --manual

members: j2mesync % kdepim

All conflicts have been reported                                                                               
Error while synchronizing: Unable to read from one of the members                                              
[dieu@elmo ~]$ DCOPServer : slotTerminate() -> sending terminateKDE signal.                                    
klauncher: KLauncher::process ---> terminateKDE

If I dont put todo sync that error does not appears but event sync is not 
done.

Any comment?

LD

Re: [Opensync-users] Nokia E90: syncml-obex-client --slow-sync text/x-vcalendar Calendar transport error: Forbidden (0x43)

[Soeren S. <ope...@nn...>]

On Fri, 2008-05-30 at 06:24 -0700, dpreiss wrote:
> 
> 
> xyon wrote:
> > 
> > Best of luck, hope it works out for you.
> > 
> 
> Indeed, it did! I had to sync both kontacts and calendar with the supplier
> tool, then the n95 stopped to give "Forbidden" to opensync. Using 0.36, the
> sync procedure hung at its end. Reverting back to 0.32+, everything
> suceeded.
> Thanks, Christian, this was a hot hint!

indeed that also makes it work for me, except that opensync 0.22 fails
sending more than 293 calendar entries.

Opensync 0.36 also fails here (crashes with a double free).


As I would like this phone to reliably work at some point, which
versions should I try, the upcomming 0.40 branch?

Soeren