I've followed all the instructions found and I can mount my Galaxy Nexus using
mtpfs. I can read files willy-nilly, although performance is pretty bad.
However, I'm unable to copy files over. The output of my test "mtp-sendfile"
command is:
diego@diego:~$ mtp-sendfile ofbiz.sql ofbiz.sql
libmtp version: 1.0.6
Device 0 (VID=04e8 and PID=685c) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Sending ofbiz.sql to ofbiz.sql
type: sql, 43
Sending file...
Error sending file.
Error 2: PTP Layer error 02ff: send_file_object_info(): Could not send object
info.
Error 2: (Look this up in ptp.h for an explanation.)
ERROR: Could not close session!
After this, the device is unusable and must be unplugged and re-plugged in.
Here's the output of a subsequent mtp-sendtr -h command without replugging the
device:
diego@diego:~$ mtp-sendtr -h
libmtp version: 1.0.6
Device 0 (VID=04e8 and PID=685c) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_ERROR_IO: failed to open session, trying again after resetting USB
interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
No devices.
(Speaking of which, the "-h" variants of the commands should output the usage
syntax - since it's not documented anywhere else - without necessitating the
device to be connected...)
And now, the mtp-sendtr attempt after replugging the device:
Please report this VID/PID and the device model to the libmtp development team
usage: sendtr
-t
-a <artist> -A <Album artist> -w <writer or composer> <br>
-l <album> -c <codec> -g <genre> -n <track number> -y <year> <br>
-d <duration in seconds> -s <storage_id> <local path> <remote path> <br>
(-q means the program will not ask for missing information.)</p>
<ol>
<li>Owner Of A Lonely Heart.mp3,Music/lonely.mp3,(null),(null),(null),(null),(null),(null),00,0,0,0 <br>
Sending track 01. Owner Of A Lonely Heart.mp3 to Music/lonely.mp3</li>
</ol>
<p>type: mp3, 1</p>
<p>Title> Owner Of A Lonely Heart</p>
<p>Album> 90125</p>
<p>Album artist> Yes</p>
<p>Artist> Yes</p>
<p>Writer or Composer></p>
<p>Genre></p>
<p>Track number></p>
<p>Year></p>
<p>Length></p>
<p>Sending track:</p>
<p>Codec: ISO MPEG-1 Audio Layer 3</p>
<p>Title: Owner Of A Lonely Heart</p>
<p>Album: 90125</p>
<p>Album artist: Yes</p>
<p>Artist: Yes</p>
<p>Storage ID: 0</p>
<p>Sending track...</p>
<p>Error sending track.</p>
<p>Error 2: PTP Layer error 02ff: send_file_object_info(): Could not send object<br>
info.</p>
<p>Error 2: (Look this up in ptp.h for an explanation.)</p>
<p>Error 1: LIBMTP_Send_Track_From_File_Descriptor(): subcall to<br>
LIBMTP_Send_File_From_File_Descriptor failed.</p>
<p>Album doesn't exist: creating...</p>
<p>Unsupported abstract list type: ba03</p>
<p>Error creating or updating album.</p>
<p>(This could be due to that your device does not support albums.)</p>
<p>Error 2: PTP Layer error 02ff: get_storage_freespace(): could not get storage<br>
info.</p>
<p>Error 2: (Look this up in ptp.h for an explanation.)</p>
<p>Error 1: check_if_file_fits(): error checking free storage.</p>
<p>Error 6: get_writeable_storageid(): all device storage is full or corrupt.</p>
<p>Error 1: create_new_abstract_list(): player does not support this abstract<br>
type</p>
<p>ERROR: Could not close session!</p>
<p>Please let me know what other information I can gather for you to help you<br>
figure out what the issue might be. Evidently, this might be an issue with the<br>
phone's software stack but it's easier to try to work with you guys to find a<br>
solution than trying to convince Google to fix their damn broken code (if<br>
that's really the problem).</p>
<p>Cheers!</p>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-12-18
One peculiarity is that in my case, mtp-detect lists the Kernel interface as
"usbfs" instead of "dummy", as seen by the other people who've reported the
mtp-detect output for this phone. I'm afraid I don't know enough to determine
if this is a problem.
Furthermore, retrieval of files is working fine (using mtp-getfile, etc).
Finally, the previously-successful mtp-getfile test fails after a failed
attempt at sendtr, so this confirms that after the write attempt the device is
left in an unusable, unresettable state.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I've followed all the instructions found and I can mount my Galaxy Nexus using
mtpfs. I can read files willy-nilly, although performance is pretty bad.
However, I'm unable to copy files over. The output of my test "mtp-sendfile"
command is:
diego@diego:~$ mtp-sendfile ofbiz.sql ofbiz.sql
libmtp version: 1.0.6
Device 0 (VID=04e8 and PID=685c) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Sending ofbiz.sql to ofbiz.sql
type: sql, 43
Sending file...
Error sending file.
Error 2: PTP Layer error 02ff: send_file_object_info(): Could not send object
info.
Error 2: (Look this up in ptp.h for an explanation.)
ERROR: Could not close session!
After this, the device is unusable and must be unplugged and re-plugged in.
Here's the output of a subsequent mtp-sendtr -h command without replugging the
device:
diego@diego:~$ mtp-sendtr -h
libmtp version: 1.0.6
Device 0 (VID=04e8 and PID=685c) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_ERROR_IO: failed to open session, trying again after resetting USB
interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
No devices.
(Speaking of which, the "-h" variants of the commands should output the usage
syntax - since it's not documented anywhere else - without necessitating the
device to be connected...)
And now, the mtp-sendtr attempt after replugging the device:
diego@diego:~/Music/Collection/Yes/90125$ mtp-sendtr -D 10 01.\ Owner\ Of\ A\ Lonely\ Heart.mp3 Music/lonely.mp3
libmtp version: 1.0.6
Device 0 (VID=04e8 and PID=685c) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
usage: sendtr
-t
One peculiarity is that in my case, mtp-detect lists the Kernel interface as
"usbfs" instead of "dummy", as seen by the other people who've reported the
mtp-detect output for this phone. I'm afraid I don't know enough to determine
if this is a problem.
Furthermore, retrieval of files is working fine (using mtp-getfile, etc).
Finally, the previously-successful mtp-getfile test fails after a failed
attempt at sendtr, so this confirms that after the write attempt the device is
left in an unusable, unresettable state.
Okay so I found out that (in my case anyway), it was a problem of not having
the latest libmtp files on my system. So I fixed the problem and made this
writeup to help others: http://www.humans-enabled.com/2011/12/how-to-fix-
samsung-galaxy-nexus-mtp.html
Cheers! Shannon