Menu

Could not send object info

Help
2006-10-31
2012-09-13
  • Robert Kratky

    Robert Kratky - 2006-10-31

    Hi,

    I'm having trouble sending data to an iRiver T10 (1GB) MTP player. The device is autodetected correctly (libmtp 0.0.21), I can read the directory structure with 'mtp-folders' and create new folders but when I try to send tracks/data, I get this:


    mtp-sendfile -t MP3 -f "folder" file.mp3
    Sending file:
    Autodetected device "iRiver T10" (VID=4102,PID=1117) is known.
    PTP: Opening session
    Connected to MTP device.
    parent_id = 327680
    Sending file...
    LIBMTP_Send_File_From_File_Descriptor: Could not send object info
    Return code: 0xa806 (look this up in ptp.h for an explanation).

    PTP: Closing session
    OK.


    Same thing happens with 'mtp-sendtr'.

    Return code 0xa806 is (according to ptp.h and Microsoft):

    Invalid_Dataset: Indicates that the dataset sent in the data phase of this operation is invalid. This indicates an internal error in MTP stack.

    Thanks for your advice.

     
    • Rob Reardon

      Rob Reardon - 2006-11-17

      Hi,

      It is now possible to upload MP3 files using the latest CVS version of libmtp, and mtp-sendtr.

      Thanks
      Rob

       
      • Robert Kratky

        Robert Kratky - 2006-11-17

        Thanks. I tried today's CVS version but still get the same error. Is there any other info I could provide that would help to track this down?

         
    • Rob Reardon

      Rob Reardon - 2006-11-20

      Did you get the same error message as last time?

      --
      LIBMTP_Send_File_From_File_Descriptor: Could not send object info
      Return code: 0xa806 (look this up in ptp.h for an explanation).
      --

      or was it a different one? I would expect to see a different error message if it is using
      the new MTP Enhanced code.

       
      • Robert Kratky

        Robert Kratky - 2006-11-20

        Yep, exactly the same error message. I checked out today's version to try again but still get the same thing:

        =====================
        $ mtp-connect --sendfile 16-Aurora.mp3,327680
        Autodetected device "iRiver T10" (VID=4102,PID=1117) is known.
        PTP: Opening session
        Connected to MTP device.
        Send file 16-Aurora.mp3,327680
        Sending 16-Aurora.mp3 to 327680
        type:mp3,1
        Sending file...
        LIBMTP_Send_File_From_File_Descriptor: Could not send object info
        Return code: 0xa806 (look this up in ptp.h for an explanation).

        PTP: Closing session

        Robert

         
    • Rob Reardon

      Rob Reardon - 2006-11-20

      Could you run the detect program and post the output? It sounds like something odd is happening.

       
      • Robert Kratky

        Robert Kratky - 2006-11-20

        $ mtp-detect
        Autodetected device "iRiver T10" (VID=4102,PID=1117) is known.
        PTP: Opening session
        Connected to MTP device.
        USB low-level info:
        Using kernel interface "usbfs"
        bcdUSB: 512
        bDeviceClass: 0
        bDeviceSubClass: 0
        bDeviceProtocol: 0
        idVendor: 4102
        idProduct: 1117
        IN endpoint maxpacket: 512 bytes
        OUT endpoint maxpacket: 512 bytes
        Device flags: 0x00000000
        Device info:
        Manufacturer: iriver
        Model: iriver T10
        Device version: MTP 1.03P
        Serial number: (null)
        Vendor extension ID: 0x00000006
        Vendor extension description: microsoft.com/WMDRMPD: 10.1
        Supported operations:
        1001: get device info
        1002: Open session
        1003: Close session
        1004: Get storage IDs
        1005: Get storage info
        1006: Get number of objects
        1007: Get object handles
        1008: Get object info
        1009: Get object
        100b: Delete object
        100c: Send object info
        100d: Send object
        100f: Format storage
        1014: Get device property description
        1015: Get device property value
        9801: Get object properties supported
        9802: Get object property description
        9803: Get object property value
        9804: Set object property value
        9805: Get object property list
        9810: Get object references
        9811: Set object references
        9101: Get secure time challenge
        9102: Get secure time response
        9103: Set license response
        9104: Get sync list
        9105: Send meter challenge query
        9106: Get meter challenge
        9107: Get meter response
        9108: Clean data store
        9109: Get license state
        910a: Unknown(910a)
        910b: Unknown(910b)
        Events supported:
        None.
        Device Properties Supported:
        0x5001: Battery Level
        0xd401: Synchronization Partner
        0xd402: Device Friendly Name
        0xd101: Secure Time
        0xd102: Device Certificate
        Playable File (Object) Types and Object Properties Supported:
        3001: Association/Directory
        dc01: StorageID
        dc02: ObjectFormat
        dc04: ObjectSize
        dc07: ObjectFileName
        dc0b: ParentObject
        dc41: PersistantUniqueObjectIdentifier
        dc4f: NonConsumable
        3009: MP3
        dc01: StorageID
        dc02: ObjectFormat
        dc04: ObjectSize
        dc07: ObjectFileName
        dc0b: ParentObject
        dc41: PersistantUniqueObjectIdentifier
        dc4f: NonConsumable
        dc44: Name
        dc46: Artist
        de93: SampleRate
        de94: NumberOfChannels
        de99: AudioWAVECodec
        de9a: AudioBitRate
        b901: WMA
        dc01: StorageID
        dc02: ObjectFormat
        dc04: ObjectSize
        dc07: ObjectFileName
        dc0b: ParentObject
        dc41: PersistantUniqueObjectIdentifier
        dc4f: NonConsumable
        dc44: Name
        dc46: Artist
        de93: SampleRate
        de94: NumberOfChannels
        de99: AudioWAVECodec
        de9a: AudioBitRate
        b902: OGG
        dc01: StorageID
        dc02: ObjectFormat
        dc04: ObjectSize
        dc07: ObjectFileName
        dc0b: ParentObject
        dc41: PersistantUniqueObjectIdentifier
        dc4f: NonConsumable
        ba05: Abstract Audio Video Playlist
        dc01: StorageID
        dc02: ObjectFormat
        dc04: ObjectSize
        dc07: ObjectFileName
        dc0b: ParentObject
        dc41: PersistantUniqueObjectIdentifier
        dc4f: NonConsumable
        Special directories:
        Default music folder: 0x00020000
        Default playlist folder: 0x00000000
        Default picture folder: 0x00000000
        Default video folder: 0x00000000
        Default organizer folder: 0x00000000
        Default zencast folder: 0x00000000
        Default album folder: 0x00000000
        MTP-specific device properties:
        Friendly name: iriver T10
        Synchronization partner: WMP 10; Napster;
        Total bytes on device: 1045135360 (996 MB)
        Free bytes on device: 1044889600 (996 MB)
        Storage description: "FAT16 System"
        Volume label: "chlbjnpaaaaaaanpcdadadfdadidcdcd"
        Battery level 4 of 4 (100%)
        libmtp supported (playable) filetypes:
        ISO MPEG Audio Layer 3
        Microsoft Windows Media Audio
        Ogg container format

        Secure Time:
        <DRMCLOCK type="status"><VALUE>#20050417 19:34:57Z#</VALUE><FLAG>DRM_CLK_NEEDS_REFRESH</FLAG></DRMCLOCK>
        PTP: Closing session
        OK.

        ================

        However, every time after connecting the device, the first run of 'mtp-detect' says this at the very end of the output:

        ...
        LIBMTP panic: Found a bad handle, trying to ignore it.
        PTP: Closing session
        OK.
        ================

        When I run 'mtp-detect' again, it is without the 'LIBMTP panic' (until reconnecting the device).

        Robert

         
        • Rob Reardon

          Rob Reardon - 2006-11-20

          What version of firmware does the device report? That list seems to indicate 1.03, which is old. The
          latest firmware for the T10 is 1.70: http://www.iriveramerica.com/support/ultra/t10_new.aspx

           
          • Robert Kratky

            Robert Kratky - 2006-11-20

            Didn't think about that... Well, I will have to find a way to upgrade the firmware. Right now I don't have access to any Windows box (and I can't upload anything from Linux) so this will have to wait.

            Thanks for the comments. I will report back when I get the firmware upgraded.

             
            • Rob Reardon

              Rob Reardon - 2006-11-20

              Ok. Hopefully the new firmware will resolve the problem. You might get a faster reply if you
              drop an e-mail to the mailing list, as the forums aren't visted very regularly.

              Thanks!
              Rob

               
              • Robert Kratky

                Robert Kratky - 2007-01-27

                Just wanted to report success with the new firmware (1.70). By the time I got to upgrade the device libmtp 0.1.3 was out and Amarok needed a patch to compile (http://bugs.kde.org/show_bug.cgi?id=139489) -- other than that, everything worked fine. Thanks for your efforts.

                 

Log in to post a comment.

Auth0 Logo