Hi Johan, Thanks again. I installed obc and got the following results: ~ $ obc OBEX Bluetooth client Getting rfcomm device from btcond via D-BUS btcond returned error: com.nokia.btcond.error.invalid_svc Using device: /dev/rfcomm0 OBEX setup failed: Connecting failed (err: 260) Type "help" to see available commands disconnected > scan Searching... 2 devices found. Resolving names...done. #1 : 00:17:4B:66:FF:3A Carel's Nokia 6280 #2 : [...] disconnected > connect 00:17:4B:66:FF:3A Getting rfcomm device from btcond via D-BUS btcond returned error: com.nokia.btcond.error.invalid_svc Using device: /dev/rfcomm0 OBEX setup failed: Connecting failed (err: 260) disconnected > exit Exiting. ~ $ The 260 error is indeed GW_OBEX_ERROR_CONNECT_FAILED . The invalid_svc error. is "No such profile on device" I still have no clue, -- Carel Johan Hedberg wrote: > Hi Carel, > > On Thu, Apr 20, 2006, Carel Bast wrote: > >> ~ $ gnomevfs-ls obex://[00:17:4B:66:FF:3A]/ >> Error opening: Service not available >> ~ $ >> > > That maps to the GW_OBEX_ERROR_CONNECT_FAILED error from libgwobex which > can be caused by several different things, however since your phone > asks to accept the connection my guess would be that the OBEX CONNECT > command is for some strange reason failing. > > >> Does this mean that my new Nokia 6280 does not support the BT obex protocol? >> Do you know of an alternative way to communicate from the 770 to the >> 6280 (via BT)? >> > > It *should* support OBEX just fine. I just ordered one for testing, but > it could take a few weeks before I get it. Meanwhile, you could try the > other two steps I mentioned to get some more info. It's also not > uncommon that flashing the phone with a newer firmware can solve this > kind of problems. > > Johan > > >
