Am Samstag 16 Februar 2008 schrieb Josip Rodin:
> On Fri, Feb 15, 2008 at 01:44:33PM +0100, Hendrik Sattler wrote:
> > > I want to be able to get to the phonebook.
> > >
> > > > > A search on the web, and in this mailing list's archive mostly
> > > > > found me nothing concrete, so I'm wondering if this is a genuine
> > > > > problem with the device, or if there is some setting that can be
> > > > > tuned to make it talk OBEX.
> > > >
> > > > Try obexftp with the /dev/ttyACM0. Maybe obex-over-serial is
> > > > implemented.
> > >
> > > It doesn't work, it just times out three times, and I don't see a way
> > > to debug that.
> >
> > try using
> > strace -x -s 128 -o m600i.log obexftp -t /dev/ttyACM0 -l
>
> Oh, it doesn't seem to say much, although you may make some sense of it.
> The device sends over some binary data and doesn't respond to AT commands,
> even though I have seen FMA talk to it in Windows like that.

You said that it create 3 ttyACM devices. Did you try the other two? One of 
them is going to accept AT command, I am pretty sure.
In the worst case: get a cheap bluetooth dongle. 99% of the phones support 
obex, there.

> I searched some more in the meantime, and a couple of forum posts on a
> MacOSX-related web site seem to say that the device really doesn't support
> OBEX, intentionally...?

Funny since MacOS X only supports Obex-over-RFcomm (aka bluetooth).

HS

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users

Reply via email to