From: David Haslam <dhaslam@nt...> - 2004-11-18 22:09:56
I've been playing with obexftp, getting it work with my SE K500i. I've
made some small
fixes to version 0.10.5 which make it work. I've uploaded a small patch
file to sourceforge.
Out of the box, obexftp appears to establish a connection, but any
attempt to get
a folder listing fails, with response 44. It turns out that the K500i is
fussy about the null terminator on the end of the type header. So in
obexftp/object.c around line 55 in the function obexftp_build_get_type I
added one to the string length. This meant I could get folder listings.
The next problem was that the setpath command was failing. It seems that
in the same file, function obexftp_build_setpath, there's some confusion
over the two extra bytes inserted into the header. The existing code is
erroneously setting the second reserved byte, and the k500i doesn't like it.
These now allow me to get files from my phone. I'm still looking at
sending files. There's also some problems with setting up the initial
connection that fails sometimes. I'll look into that too.
Of course, I've no idea if these changes break anything for other phones.
From: Christian W. Zuckschwerdt <Christian@Zuckschwerdt.org> - 2004-11-18 22:45:25
David Haslam wrote:
> I've been playing with obexftp, getting it work with my SE K500i. I've
> made some small
> fixes to version 0.10.5 which make it work.
Your contributions are much appreciated .
> It turns out that the K500i is fussy about the null terminator on the
> end of the type header.
I couldn't find anything about the type-header format in the specs.
Perhaps someone can dig up authoriative info on that.
> The existing code is erroneously setting the second reserved byte,
Plain to see, yes. Regarding flags we are talking about bits no bytes ;)
> Of course, I've no idea if these changes break anything for other phones.
Works for my Siemens S65.
0.10.6 will be out soon for people to test-drive the enhancements.