From: Sciamano <sci...@gm...> - 2008-02-11 14:51:37
|
Hi everybody, I'm the owner of a SanDisk Sansa View player, which needs the MTP protocol to work (MSC is only available as a workaround, and anyway I'd like it to work with libmtp). I thought the developers of libmtp might be interested in the anomalous behavior that happens when I try to connect to the device. When I connect the View to the USB cable, its display shows "Connected", but it really is not so. In fact if I try to connect with any MTP-compatible software, like Qlix or Amarok, they fail. If I send the mtp-detect command, the View will reboot, and the terminal will show the following info: -------------------- libmtp version: 0.2.5 Attempting to connect device(s) usb_claim_interface(): No such device LIBMTP PANIC: Unable to initialize device 1 LIBMTP PANIC: configure_usb_devices() error code: 7 on line 1561 Detect: There has been an error connecting. Exiting ------------------- As I said, while this shows up in the terminal, the device reboots. During reboot, the View shows a splash screen with SanDisk's logo and such, then there is a super-short moment (maybe half a second long) when the View's GUI shows up. Immediately after that, the black screen with the "connected" sign shows up again. If I send the mtp-detect command now, it reboots again, and again, and again... you get the point. To make things work, I have to send the mpt-detect command during that short moment in which the View's GUI is shown, otherwise I will not be able to connect with any program that uses the mtp protocol. I hope this helps improve libmtp's compatibility. If you need any more information, or need me to try something, just ask. Thanks for reading (and for working on libmtp). Luca |