quirks missing (Samsung SGH-X680)

2008-08-16
2013-05-01
  • Hi,

    I wonder if there's an automatic quirks setup function somewhere in the library (if that's even possible)?

    I ask because "obexfs-0.10" needs quirks for my Samsung SGH-X680 in order to work:
    1) channel is 9.
    2) cli->quirks |= OBEXFTP_LEADING_SLASH | OBEXFTP_TRAILING_SLASH | OBEXFTP_SPLIT_SETPATH.
    (for now, I hardcoded the change in "obexfs.c" to test whether it would work -> it does)

    -----------
    obexftp -b 00:18:AF:B4:8B:37 -Y
    Browsing 00:18:AF:B4:8B:37 ...
    Channel: 9

    === Probing with FBS uuid.
    Connecting...done
    getting null object without type
    response code 20
    getting empty object without type
    Receiving ""... failed:
    response code 44
    getting null object with x-obex/folder-listing type
    Receiving "(null)"... done
    response code 20
    getting empty object with x-obex/folder-listing type
    Receiving ""... done
    response code 20
    getting null object with x-obex/capability type
    Receiving "(null)"... failed: (null)
    response code 44
    getting empty object with x-obex/capability type
    Receiving ""... failed:
    response code 44
    getting null object with x-obex/object-profile type
    Receiving "(null)"... failed: (null)
    response code 44
    getting empty object with x-obex/object-profile type
    Receiving ""... failed:
    response code 44
    getting telecom/devinfo.txt object
    Receiving "telecom/devinfo.txt"... failed: telecom/devinfo.txt
    response code 44
    getting telecom/devinfo.txt object with setpath
    Receiving "telecom/devinfo.txt"... Sending ""... done
    failed: telecom/devinfo.txt
    response code 44
    === response codes === 20 44 20 20 44 44 44 44 44 44
    Disconnecting...done

    === Probing with S45 uuid.
    Connecting...failed: FBS UUID
    Still trying to connect
    Connecting...failed: FBS UUID
    Still trying to connect
    Connecting...failed: FBS UUID
    Still trying to connect
    couldn't connect.

    === Probing without uuid.
    Connecting...failed: connect
    Still trying to connect
    Connecting...failed: connect
    Still trying to connect
    Connecting...failed: connect
    Still trying to connect
    couldn't connect.

    End of probe.
    -----------

    (I post here because the GMane group "gmane.network.protocols.obex.openobex.user" seems to be read-only)

    cheers,
       Danny

     
    • Thanks for debugging this! I'll look into adding this to ObexFTP or ObexFS (looks like detecting that phone could be trouble).

      The gmane group is just a mirror of the sf mailing list archive I guess.

       
    • Hi,

      the cell phone also supports the AT GSM command set - so to find out the model, one could do "ATI" on the rfcomm channel:

      -----------------
      ATI                                                                           
      Samsung SGH-X680                                                              
      OK
      -----------------

      As for autodetecting the split_setpath, how about trying to supply an invalid path for the listdir message and see whether it fails? (it wouldn't fail if it ignored the "path" parameter for the listdir message and in that case, we'd have found out that it's in fact ignoring the parameter :))

      Evil workarounds but...

      And about the "channel = 9", I noticed that OBEXFTP gets it right without patch. How come?

      cheers,
         Danny

       
      • AT-style communication is only available on the TTY transport. And TTY is kind of a last resort these days. Ah, well IrDA might be even more exotic now ;)

        There is plan (and some testing patches) to do some initial probing on a device. But testing is limited since I don't own any quirky devices...

        The API to browse for the bt channel wasn't finished. But the current release, ObexFS 0.11 has this.