site_archiver(a)lists.apple.com
Delivered-To: bluetooth-dev(a)lists.apple.com
The operation could not be completed.
An unexpected error occurred (error code -10810).
Any help getting PacketLogger running would be much appreciated...
Thanks
-Tico
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.…
I'm having a strange problem where my bluetooth connection between my
Nokia mobile phone and my Mac seems to successfully connect (as
indicated by both the Mac and the Phone) but then the connection seems
to hang. I'm running 10.3.9 and I've downloaded the latest Bluetooth
SDK (v1.5.3). The problem is when I try to run PacketLogger to debug
the connection, I get the following error:
This email sent to site_archiver(a)lists.apple.com
site_archiver(a)lists.apple.com
Delivered-To: bluetooth-dev(a)lists.apple.com
User-agent: Microsoft-Entourage/9.0.5.4011
> when I try to GET a file, such as foo.jpg, the phone comes back with
> 0XC4 (file not found). The OBEX GET request packet includes the connection id
> header, together with the name header with value foo.jpg encoded as Unicode.
OBEX specification 1.3 > chapter 3.3.6: SetPath
If you get the directories content, you have not switched the context to the
folder automatically. Although the newer OBEX 1.3 says nothing about
absolute or relative setPath navigation, the Bluetooth Folder Browsing
profile says to use setPath always and not absolute path.
Siemens OBEX is very tricky because some models do not allow absolute
navigation and only setPath. Some do not allow parent, most do not allow
absolute with /path only path/path/ and some very rare models do not allow
paths in the name header at all.
Conclusion:
For each directory change always use setPath and begin at the root always
(for super-directories; not for subdirectories). This trick works for me,
Siemens, Ericsson and my OBEX stack. Never played with the Apple Mac OS X
one. Do not know about the Samsung D500, Nokia or Motorola but I think they
work quite the same (and have their own bugs).
> I appreciate this question is somewhat specific to my phone, which is
> manufacturer specific,
I do not think so, it was a generic problem.
> it's driving me round the bend!
It is very difficult not only because the implementations are buggy but
because even the specifications are not clear (absolute vs. relative).
If that did not help, give use your complete OBEX header in hex (if
possible).
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.…
This email sent to site_archiver(a)lists.apple.com
site_archiver(a)lists.apple.com
Delivered-To: bluetooth-dev(a)lists.apple.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.…
This email sent to site_archiver(a)lists.apple.com
x-obex/folder-listing.