[maemo-developers] gwobex problem
From: Christian Kuersteiner ckuerste at gmx.chDate: Wed Oct 7 05:31:13 EEST 2009
- Previous message: gwobex problem
- Next message: gwobex problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Johan Hedberg wrote: > > gw-obex doesn't really care which OBEX profile it's connected to. The > different functions will always try to do the same operations (but they > are of course likely to fail if you connected to OPP but try to use FTP > operations such as folder listing or SetPath). > > Johan > Well, directory listing works quite well :-) Even directory listing of one subdirectory (but I can't get any further cause as you mentioned gw_obex_chdir can't handle the absolute path). Just SetPath seems to fail. Anyway I finally checked the error code (I should have done this right from the beginning...) and I get a 65 which would be OBEX_RSP_UNAUTHORIZED and explaines the failure. On the other hand I used hcidump as you suggested. Here is the dump from the SetPath command: < ACL data: handle 45 flags 0x02 dlen 42 L2CAP(d): cid 0x01cc len 38 [psm 3] RFCOMM(d): UIH: cr 1 dlci 12 pf 0 ilen 34 fcs 0x4f OBEX: SetPath cmd(f): len 34 flags 2 constants 0 Name (0x01) = Unicode length 26 0000: 00 50 00 68 00 6f 00 6e 00 65 00 20 00 6d 00 65 .P.h.o.n.e. .m.e 0010: 00 6d 00 6f 00 72 00 79 00 00 .m.o.r.y.. > HCI Event: Number of Completed Packets (0x13) plen 5 handle 45 packets 1 > ACL data: handle 45 flags 0x02 dlen 13 L2CAP(d): cid 0x0041 len 9 [psm 3] RFCOMM(d): UIH: cr 0 dlci 12 pf 1 ilen 3 fcs 0x89 credits 1 OBEX: SetPath rsp(f): status 401 len 3 Can I somehow match the status 401 to the final error code? Or is it rather the cid 0x0041 which would match my error code? Finally I guess I need another (older) phone to check my implementation... Thank you for your help! Christian
- Previous message: gwobex problem
- Next message: gwobex problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]