Thread: [Opensync-users] Connecting to Mobile over USB Cable

Status: Beta

Brought to you by: azrael2, dfriedrich, dgollub_

opensync-users

[Opensync-users] Connecting to Mobile over USB Cable

From: Habib S. <hab...@ya...> - 2008-12-12 07:38:27

Hi dear friends,

As almost all of us know, for browsing the blue-tooth services which a
cell phone provides, it suffices to type: sdptool browse $MAC, where
$MAC can be obtained using hcitool scan.

But, how can I find the services which my mobile provides over USB
Cable? Are there any commands similar to sdptool and hcitool for USB
connection?

But why I need such a command: My cell phone is Sony Ericcson P1i, It's
said that it supports SyncML protocol, but this service isn't in the
output of sdptool browse command. Therefore, I guess that it provides
SyncML only over USB? So I need a command similar to sdptool to ensure
that my cell phone provides the required service and also obtain the
proper address and channel number.

Cheers,
Habib Seifzadeh

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Christian H. <Chr...@co...> - 2008-12-12 10:51:28

Habib Seifzadeh schrieb:

> But why I need such a command: My cell phone is Sony Ericcson P1i, It's
> said that it supports SyncML protocol, but this service isn't in the
> output of sdptool browse command. Therefore, I guess that it provides
> SyncML only over USB? So I need a command similar to sdptool to ensure
> that my cell phone provides the required service and also obtain the
> proper address and channel number.

P1i is known to support only SyncML 1.2 over IP. I do not know
how to do IP over USB with Linux. I assume you use Linux as you
mention sdptool.

That means you need to use syncml-http-server. Search for P990i in the
wiki and follow the suggestions.

If possible, the using IP over BT will be the less painfull.

Also use the latest libwbxml and OpenSync from trunk.

For the initial tests please use syncml-ds-tool.

Kind regards

Christian
--
Christian Hilgers                  |ConSol*
Tel.   +49.2102.994-423            |Consulting&Solutions Software GmbH
Fax    +49.2102.994-411            |Berliner Str. 101, 40880 Ratingen
email: Chr...@co... |WWW: http://www.consol.de

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Habib S. <hab...@ya...> - 2008-12-12 19:56:09

 Dear Christian,

First of all, thank you so much for your reply,
I have got some results which want to disclose with you. It may help to solve the problem....


First, the very strange behaviour of P1i is that as I mentioned before, it doesn't list SyncML in its services when I issue "sdptool browse $MAC" command, so I
guessed that it doesn't support SyncML over BT, but when I typed
"sdptool search SYNCML", sdptool said that my cell phone privodes
SyncML service on channel 3 !!!
In your opinion, is it a normal behaviour?

After
ensuring that my cell phone provides the service I want over BT, I
tested both syncml-http-server and syncml-obex-client, but none of them
worked :-(
When I use syncml-http-server, the cell phone prompts
"Connected", but after awhile, it prompts "Cannot Communicate with
SyncML Server (The connection failed before completion)". I checked all
of settings like username and password, database names and .... times
and times. but the problem remains.

In the other hand, when I
use syncml-obex-client with different parameters(different versions,
with and without libwbxml and ....) my computer says "BT Connection
Error" and my cell phone says "SyncMLAgent closed with error code 13".
After surfing the web, one guy exactly has had the same problem (http://www.nabble.com/Sony-Ericsson-P1i-:-problems-with-syncml-obex-client-td18959082.html) but no one answered to him yet :-(
In your opinion, is it because of my cell phone firmware? Is it solved if I update its firmware, 

Sincerely yours,
Habib Seifzadeh


----- Original Message ----
> From: Christian Hilgers <Chr...@co...>
> To: ope...@li...
> Sent: Friday, December 12, 2008 2:21:17 PM
> Subject: Re: [Opensync-users] Connecting to Mobile over USB Cable
> 
> Habib Seifzadeh schrieb:
> 
> > But why I need such a command: My cell phone is Sony Ericcson P1i, It's
> > said that it supports SyncML protocol, but this service isn't in the
> > output of sdptool browse command. Therefore, I guess that it provides
> > SyncML only over USB? So I need a command similar to sdptool to ensure
> > that my cell phone provides the required service and also obtain the
> > proper address and channel number.
> 
> P1i is known to support only SyncML 1.2 over IP. I do not know
> how to do IP over USB with Linux. I assume you use Linux as you
> mention sdptool.
> 
> That means you need to use syncml-http-server. Search for P990i in the
> wiki and follow the suggestions.
> 
> If possible, the using IP over BT will be the less painfull.
> 
> Also use the latest libwbxml and OpenSync from trunk.
> 
> For the initial tests please use syncml-ds-tool.
> 
> Kind regards
> 
> Christian
> --
> Christian Hilgers                  |ConSol*
> Tel.   +49.2102.994-423            |Consulting&Solutions Software GmbH
> Fax    +49.2102.994-411            |Berliner Str. 101, 40880 Ratingen
> email: Chr...@co... |WWW: http://www.consol.de
> 
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Robin A. <ro...@bi...> - 2008-12-13 12:46:05

On Saturday 13 Dec 2008, Habib Seifzadeh wrote:

> First, the very strange behaviour of P1i is that as I mentioned before, it
> doesn't list SyncML in its services when I issue "sdptool browse $MAC"
> command, so I guessed that it doesn't support SyncML over BT, but when I
> typed
> "sdptool search SYNCML", sdptool said that my cell phone privodes
> SyncML service on channel 3 !!!
> In your opinion, is it a normal behaviour?

FWIW, I have a P1i and get the same behaviour. I also have upgraded to the 
latest firmware. :(

-Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Habib S. <hab...@ya...> - 2008-12-13 19:29:49




----- Original Message ----
> From: Robin Atwood <ro...@bi...>
> To: ope...@li...
> Sent: Saturday, December 13, 2008 4:15:52 PM
> Subject: Re: [Opensync-users] Connecting to Mobile over USB Cable
> 
> On Saturday 13 Dec 2008, Habib Seifzadeh wrote:
> 
> > First, the very strange behaviour of P1i is that as I mentioned before, it
> > doesn't list SyncML in its services when I issue "sdptool browse $MAC"
> > command, so I guessed that it doesn't support SyncML over BT, but when I
> > typed
> > "sdptool search SYNCML", sdptool said that my cell phone privodes
> > SyncML service on channel 3 !!!
> > In your opinion, is it a normal behaviour?
> 
> FWIW, I have a P1i and get the same behaviour. I also have upgraded to the 
> latest firmware. :(
> 
> -Robin
> -- 
> ----------------------------------------------------------------------
> Robin Atwood.
> 

This behavior is not very important, but could you finally sync your mobile with a linux box?
Thanks,
Habib Seifzadeh

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Robin A. <ro...@bi...> - 2008-12-14 11:45:42

On Sunday 14 Dec 2008, Habib Seifzadeh wrote:

> This behavior is not very important, but could you finally sync your mobile
> with a linux box? Thanks,
> Habib Seifzadeh

No, it has never worked for me.

-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Daniel G. <dg...@su...> - 2008-12-14 12:08:54

On Friday 12 December 2008 20:56:04 Habib Seifzadeh wrote:
> First, the very strange behaviour of P1i is that as I mentioned before, it
> doesn't list SyncML in its services when I issue "sdptool browse $MAC"
> command, so I guessed that it doesn't support SyncML over BT, but when I
> typed
> "sdptool search SYNCML", sdptool said that my cell phone privodes
> SyncML service on channel 3 !!!
> In your opinion, is it a normal behaviour?

Could you provide the output of "sdptool browse $MAC"?

TIA

best regards,
Daniel

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Robin A. <ro...@bi...> - 2008-12-15 10:26:55

On Sunday 14 Dec 2008, Daniel Gollub wrote:
> Could you provide the output of "sdptool browse $MAC"?

# sdptool browse 00:1C:A4:5A:73:D8
Browsing 00:1C:A4:5A:73:D8 ...
Service Name: AVRCP Target
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10000
Service Class ID List:
  "AV Remote Target" (0x110c)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 23
  "AVCTP" (0x0017)
    uint16: 0x100
Profile Descriptor List:
  "AV Remote" (0x110e)
    Version: 0x0100

Service Name: AVRCP Controller
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10001
Service Class ID List:
  "AV Remote" (0x110e)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 23
  "AVCTP" (0x0017)
    uint16: 0x100
Profile Descriptor List:
  "AV Remote" (0x110e)
    Version: 0x0100

Service Name: m-Router Connectivity
Service Description: m-Router Connectivity
Service Provider: Symbian Ltd.
Service RecHandle: 0x10002
Service Class ID List:
  UUID 128: a2157972-3541-4d0b-a551-b3abe639f526
  "Generic Networking" (0x1201)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100

Service Name: m-Router Connectivity
Service Description: m-Router Connectivity
Service Provider: Symbian Ltd.
Service RecHandle: 0x10003
Service Class ID List:
  "Serial Port" (0x1101)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 2
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100

Service Name: Personal Ad-hoc User Service
Service Description: Personal Ad-hoc User Service
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10004
Service Class ID List:
  "PAN User" (0x1115)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 15
  "BNEP" (0x000f)
    Version: 0x0100
    SEQ8: 0 6 dd
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "PAN User" (0x1115)
    Version: 0x0100

Service Name: Group Ad-hoc Network Service
Service Description: Personal Group Ad-hoc Network Service
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10005
Service Class ID List:
  "PAN Group Network" (0x1117)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 15
  "BNEP" (0x000f)
    Version: 0x0100
    SEQ8: 0 6 dd
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "PAN Group Network" (0x1117)
    Version: 0x0100

Service Name: Phonebook access PSE
Service Provider: Symbian Software Ltd
Service RecHandle: 0x10010
Service Class ID List:
  "Phonebook Access - PSE" (0x112f)
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:
  "Phonebook Access" (0x1130)
    Version: 0x0100

Service Name: Audio Streaming Source
Service Description: Symbian OS,UIQ phone
Service Provider: Sony Ericsson
Service RecHandle: 0x1001b
Service Class ID List:
  "Audio Source" (0x110a)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 25
  "AVDTP" (0x0019)
    uint16: 0x100
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Advanced Audio" (0x110d)
    Version: 0x0100

Service Name: SEMC HLA
Service RecHandle: 0x1001c
Service Class ID List:
  "" (0x8e771301)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 61689
  "" (0x8e770300)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "" (0x8e771303)
    Version: 0x0100

Service Name: Dial-up Networking
Service Description: Symbian OS,UIQ phone
Service Provider: Sony Ericsson
Service RecHandle: 0x1001d
Service Class ID List:
  "Dialup Networking" (0x1103)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 7
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Dialup Networking" (0x1103)
    Version: 0x0100

Service Name: Headset Audio Gateway
Service Description: Symbian OS,UIQ phone
Service Provider: Sony Ericsson
Service RecHandle: 0x1001f
Service Class ID List:
  "Headset Audio Gateway" (0x1112)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 8
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Headset" (0x1108)
    Version: 0x0100

Service Name: Hands-free Audio Gateway
Service Description: Symbian OS,UIQ phone
Service Provider: Sony Ericsson
Service RecHandle: 0x10020
Service Class ID List:
  "Handsfree Audio Gateway" (0x111f)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 9
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Handsfree" (0x111e)
    Version: 0x0105

Service Name: Object Push
Service RecHandle: 0x10021
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 3
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

Service Name: File transfer
Service RecHandle: 0x10022
Service Class ID List:
  "OBEX File Transfer" (0x1106)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX File Transfer" (0x1106)
    Version: 0x0100

-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Daniel G. <dg...@su...> - 2008-12-15 10:58:22

On Monday 15 December 2008 11:26:43 Robin Atwood wrote:
> On Sunday 14 Dec 2008, Daniel Gollub wrote:
> > Could you provide the output of "sdptool browse $MAC"?

If you run "sdptool search SYNCML", make sure the MAC is matching your mobile.  
Very likely the result on channel 3 was the result of your neighbor's mobile. 
You can also run: sdptool --bdaddr=$MAC SYNCML to just search for a certain 
Service on a certain device. Without parameter it's checking all devices.

I saw traces of m-Router SDP records ...
You don't have to waste time with trying SyncML via OBEX. You need to 
establish an IP connection and then fire-up SyncML http over this IP 
connection.

Good luck...

best regards,
Daniel

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Robin A. <ro...@bi...> - 2008-12-15 11:16:48

On Monday 15 Dec 2008, Daniel Gollub wrote:
> On Monday 15 December 2008 11:26:43 Robin Atwood wrote:
> > On Sunday 14 Dec 2008, Daniel Gollub wrote:
> > > Could you provide the output of "sdptool browse $MAC"?
>
> If you run "sdptool search SYNCML", make sure the MAC is matching your
> mobile. Very likely the result on channel 3 was the result of your
> neighbor's mobile. You can also run: sdptool --bdaddr=$MAC SYNCML to just
> search for a certain Service on a certain device. Without parameter it's
> checking all devices.

 # sdptool search --bdaddr=00:1C:A4:5A:73:D8 SYNCML
Searching for SYNCML on 00:1C:A4:5A:73:D8 ...
Service Name: SyncMLClient
Service Description: SyncML BT client
Service RecHandle: 0x1002c
Service Class ID List:
  UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 6
  "OBEX" (0x0008)

It's my phone alright!

> I saw traces of m-Router SDP records ...
> You don't have to waste time with trying SyncML via OBEX. You need to
> establish an IP connection and then fire-up SyncML http over this IP
> connection.

Thanks, I will give it a try.

-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Daniel G. <dg...@su...> - 2008-12-15 12:28:27

On Monday 15 December 2008 12:16:30 Robin Atwood wrote:
> On Monday 15 Dec 2008, Daniel Gollub wrote:
> > On Monday 15 December 2008 11:26:43 Robin Atwood wrote:
> > > On Sunday 14 Dec 2008, Daniel Gollub wrote:
> > > > Could you provide the output of "sdptool browse $MAC"?
> >
> > If you run "sdptool search SYNCML", make sure the MAC is matching your
> > mobile. Very likely the result on channel 3 was the result of your
> > neighbor's mobile. You can also run: sdptool --bdaddr=$MAC SYNCML to just
> > search for a certain Service on a certain device. Without parameter it's
> > checking all devices.
>
>  # sdptool search --bdaddr=00:1C:A4:5A:73:D8 SYNCML
> Searching for SYNCML on 00:1C:A4:5A:73:D8 ...
> Service Name: SyncMLClient
> Service Description: SyncML BT client
> Service RecHandle: 0x1002c
> Service Class ID List:
>   UUID 128: 00000002-0000-1000-8000-0002ee000002
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 6
>   "OBEX" (0x0008)
>
> It's my phone alright!


Uuuuuuuuuh... that's interesting...

>
> > I saw traces of m-Router SDP records ...
> > You don't have to waste time with trying SyncML via OBEX. You need to
> > establish an IP connection and then fire-up SyncML http over this IP
> > connection.
>
> Thanks, I will give it a try.

Stop. There is OBEX....

The SYNCML SDP record doesn't seem to be "visible" when doing regular 
(broadcast) SDP query. Could you try latest syncml-ds-tool with "obex" 
transport on channel 6 via Bluetooth..

Please forget about the IP/m-Router stuff for a second...

best regards,
Daniel

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Robin A. <ro...@bi...> - 2008-12-15 13:55:01

On Monday 15 Dec 2008, Daniel Gollub wrote:

> Stop. There is OBEX....
>
> The SYNCML SDP record doesn't seem to be "visible" when doing regular
> (broadcast) SDP query. Could you try latest syncml-ds-tool with "obex"
> transport on channel 6 via Bluetooth..

In which package do I find that? It's not on my Gentoo system.

-Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Habib S. <hab...@ya...> - 2008-12-15 19:13:12

Dear Danial,


> The SYNCML SDP record doesn't seem to be "visible" when doing regular 
> (broadcast) SDP query. Could you try latest syncml-ds-tool with "obex" 
> transport on channel 6 via Bluetooth..

Like Robin, I don't have any package which contains "syncml-ds-tool". My linux box is Ubuntu 8.10. After searching in the opensync.org site, I found that this program has been included in syncml after the 0.5 version. Is it true?

So, I got the latest version of syncml and wanted to compile it from its source. The INSTALL file suggested to run:

mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=$prefix /path/to/libsyncml/source/
make
make test
make install

I had no rpoblem until make command, it issued the following errors:

[  2%] Building C object libsyncml/CMakeFiles/syncml.dir/transports/obex_client_samsung.o
In file included from /home/habib/ttt/libsyncml/transports/obex_client_samsung.c:25:
/home/habib/ttt/libsyncml/transports/obex_client_internals.h:26:27: error: openobex/obex.h: No such file or directory
In file included from /home/habib/ttt/libsyncml/transports/obex_client_samsung.c:25:
/home/habib/ttt/libsyncml/transports/obex_client_internals.h:49: error: expected specifier-qualifier-list before ‘obex_t’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c: In function ‘smlTransportObexVendorSamsungInit’:
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:29: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:29: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:44: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:45: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:48: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:49: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:50: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:51: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:52: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:53: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:54: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:55: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:56: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:57: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:58: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:59: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:60: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:61: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:62: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:63: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:64: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:65: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:66: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:67: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:68: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:83: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:83: error: ‘SmlTransportObexClientEnv’ has no member named ‘datastores’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:85: error: ‘SmlTransportObexClientEnv’ has no member named ‘datastores’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:87: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:89: error: ‘SmlTransportObexClientEnv’ has no member named ‘datastores’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:93: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:96: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:99: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:102: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:113: error: ‘SmlTransportObexClientEnv’ has no member named ‘model’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:118: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:119: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:120: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:123: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
/home/habib/ttt/libsyncml/transports/obex_client_samsung.c:123: error: ‘SmlTransportObexClientEnv’ has no member named ‘at_command’
make[2]: *** [libsyncml/CMakeFiles/syncml.dir/transports/obex_client_samsung.o] Error 1
make[1]: *** [libsyncml/CMakeFiles/syncml.dir/all] Error 2
make: *** [all] Error 2


Do you have any suggestion for compiling syncml?
Anyway, is it right to test the latest version of syncml?

Sincerely,
Habib Seifzadeh

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Daniel G. <dg...@su...> - 2008-12-15 19:28:58

On Monday 15 December 2008 20:12:59 Habib Seifzadeh wrote:
> Dear Danial,

Interesting, so far only my last-name got written wrong ;)

>
> > The SYNCML SDP record doesn't seem to be "visible" when doing regular
> > (broadcast) SDP query. Could you try latest syncml-ds-tool with "obex"
> > transport on channel 6 via Bluetooth..
>
> Like Robin, I don't have any package which contains "syncml-ds-tool". My
> linux box is Ubuntu 8.10. After searching in the opensync.org site, I found
> that this program has been included in syncml after the 0.5 version. Is it
> true?

Right syncml-ds-tool get introduced by libsyncml 0.5.0

>
> So, I got the latest version of syncml and wanted to compile it from its
> source. The INSTALL file suggested to run:
>
> mkdir build
> cd build
> cmake -DCMAKE_INSTALL_PREFIX=$prefix /path/to/libsyncml/source/
> make
> make test
> make install
>
> I had no rpoblem until make command, it issued the following errors:
>
> [  2%] Building C object
> libsyncml/CMakeFiles/syncml.dir/transports/obex_client_samsung.o In file
> included from
> /home/habib/ttt/libsyncml/transports/obex_client_samsung.c:25:
> /home/habib/ttt/libsyncml/transports/obex_client_internals.h:26:27: error:
> openobex/obex.h: No such file or directory

Looks like our cmake build-env checks for OpenOBEX are weak. Do you have 
openobex devel packages installed?

best regards,
Daniel

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Habib S. <hab...@ya...> - 2008-12-15 20:34:23

> On Monday 15 December 2008 20:12:59 Habib Seifzadeh wrote:
> > Dear Danial,
> 
> Interesting, so far only my last-name got written wrong ;)

So sorry.... :-(

> > [  2%] Building C object
> > libsyncml/CMakeFiles/syncml.dir/transports/obex_client_samsung.o In file
> > included from
> > /home/habib/ttt/libsyncml/transports/obex_client_samsung.c:25:
> > /home/habib/ttt/libsyncml/transports/obex_client_internals.h:26:27: error:
> > openobex/obex.h: No such file or directory
> 
> Looks like our cmake build-env checks for OpenOBEX are weak. Do you have 
> openobex devel packages installed?

You're right....
I installed OpenOBEX devel packages and the syncml-ds-tool installed successfully,
But how can I use it? When I type "syncml-ds-tool", it says:

ERROR: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request.
OBEX Transport not enabled in this build

It sounds this program hasn't any --help parameter or man page. Or may be I haven't installed it correctly.

Cheers,
Habib

Re: [Opensync-users] Connecting to Mobile over USB Cable

From: Daniel G. <dg...@su...> - 2008-12-15 20:44:35

On Monday 15 December 2008 21:34:15 Habib Seifzadeh wrote:
> > On Monday 15 December 2008 20:12:59 Habib Seifzadeh wrote:
> > > Dear Danial,
> >
> > Interesting, so far only my last-name got written wrong ;)
>
> So sorry.... :-(
>
> > > [  2%] Building C object
> > > libsyncml/CMakeFiles/syncml.dir/transports/obex_client_samsung.o In
> > > file included from
> > > /home/habib/ttt/libsyncml/transports/obex_client_samsung.c:25:
> > > /home/habib/ttt/libsyncml/transports/obex_client_internals.h:26:27:
> > > error: openobex/obex.h: No such file or directory
> >
> > Looks like our cmake build-env checks for OpenOBEX are weak. Do you have
> > openobex devel packages installed?
>
> You're right....
> I installed OpenOBEX devel packages and the syncml-ds-tool installed
> successfully, But how can I use it? When I type "syncml-ds-tool", it says:
>
> ERROR: Command failed. The recipient encountered an unexpected condition
> which prevented it from fulfilling the request. OBEX Transport not enabled
> in this build

That's bad - could you "flush" the cmake cache by deleting the build directory 
and re-rerun cmake from scratch? I guess on the first run when openobex-devel 
wasn't installed the obex built kept being disabled. The obex-error is just 
about an missing OBEX conditional i guess...

>
> It sounds this program hasn't any --help parameter or man page. Or may be I
> haven't installed it correctly.