Sure. I've downloaded the latest stable libmtp and compiled from scratch, replacing the old one provided by the Ubuntu repos. After that, I compiled latest stable mtpfs and tested everything.
By the way, here goes the output of issuing mtp-detect:
libmtp version: 1.1.0
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1 (04e8:6860) @ bus 1, dev 6
Attempting to connect device(s)
But it never connects...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, now I went a little further and followed the instructions of the project's main page. I started trying different combinations of device flags in the music-players.h file. I did not know for sure which ones to try, so I tried BROKEN_BATTERY_LEVEL and FORCE_RESET_ON_CLOSE, and combinations of those with the ones previously stated (UNLOAD_DRIVER and LONG_TIMEOUT). I would modify the file, recompile the whole lib, install it and then unplug/plug the tablet, but the results would always be the same. Finally, I tried the flag DEVICE_FLAG_NONE, but it was the same as before.
I was not sure if I should reboot the computer or something like that so that the changes in the library make effect. If that is the case, please tell me, and I will test again.
Renaming the summary, I don't think this has anything to do with Honeycomb,
it does not appear to be using the Android MTP stack but the Samsung version
instead.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Testing with libmtp 1.1.3, Samsug Galaxy tab 10.1:
mtp-detect
libmtp version: 1.1.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 6
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
usb_open(): No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Testing with libmtp 1.1.3, Samsug Galaxy tab 10.1:
mtp-detect
libmtp version: 1.1.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung
GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note
(04e8:6860) @ bus 2, dev 6
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB
interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
usb_open(): No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same here. Archlinux 64bit, samsung galaxy tab2 7.0 (P3110).
The device says it is connected, but every operation fails.
Here is the output of mtp-detect -d
Listing raw device(s)
LIBMTP LIBMTP_Detect_Raw_Devices[663]: Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 3, dev 6
Attempting to connect device(s)
PTP: Opening session 0000: 1000 0000 0100 0210 0000 0000 0100 0000 ................
LIBMTP configure_usb_device[1993]: PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP configure_usb_device[1994]: LIBMTP libusb: Attempt to reset device
PTP: Opening session 0000: 1000 0000 0100 0210 0000 0000 0100 0000 ................
LIBMTP configure_usb_device[2005]: LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm testing out in the blind, the git contains a selection fix for the USB
interface, maybe you can test this. It's pretty tricky for me to debug
without the device :-(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2012-10-13
I've tested the git version, but it doesnt seems to works as I've expected.
I'm attaching the output of mtp-detect, I don't know if it's helpful.
Just for reference, mtp-connect --sendfiles output is:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.5
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Send file /home/simone/sogno.txt
Sending /home/simone/sogno.txt to SSH_AGENT_PID=827
type: txt, 44
Sending file...
Error sending file.
Error 1: Get Storage information failed.
Error 2: PTP Layer error 2006: send_file_object_info():Could not send object property list.
Error 2: Error 2006: PTP: Parameter Not Supported
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
This is the bug that I filed at Launchpad. https://bugs.launchpad.net/unity/+bug/803694
Last edit: Anonymous 2013-11-21
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
I am also affected by this bug. I will be glad to do any testing as well.
mtp-detect can detect the device, but when it tries to auto-connect it gets stuck, just freezes, and I have to kill the process. I used libmtp 1.1.0.
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
@paulocic: what do you mean it detects? When i run gMTP it says no raw device detected. Can I have the steps?
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Sure. I've downloaded the latest stable libmtp and compiled from scratch, replacing the old one provided by the Ubuntu repos. After that, I compiled latest stable mtpfs and tested everything.
By the way, here goes the output of issuing mtp-detect:
libmtp version: 1.1.0
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1 (04e8:6860) @ bus 1, dev 6
Attempting to connect device(s)
But it never connects...
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Okay, now I went a little further and followed the instructions of the project's main page. I started trying different combinations of device flags in the music-players.h file. I did not know for sure which ones to try, so I tried BROKEN_BATTERY_LEVEL and FORCE_RESET_ON_CLOSE, and combinations of those with the ones previously stated (UNLOAD_DRIVER and LONG_TIMEOUT). I would modify the file, recompile the whole lib, install it and then unplug/plug the tablet, but the results would always be the same. Finally, I tried the flag DEVICE_FLAG_NONE, but it was the same as before.
I was not sure if I should reboot the computer or something like that so that the changes in the library make effect. If that is the case, please tell me, and I will test again.
Anyway, I've put the output of lsusb -v in http://paulo.oc.eti.br/lsusb_gtab101.txt , so that if it can help, it is available.
Being discussed on the mailing list I think, report progress here pls.
Suspect this is about strong DRM measures implementing deviating Microsoft commands on the device.
This is a pretty interesting bug ticket so keeping it around.
Renaming the summary, I don't think this has anything to do with Honeycomb,
it does not appear to be using the Android MTP stack but the Samsung version
instead.
Please test this device with libmtp 1.1.3+
Testing with libmtp 1.1.3, Samsug Galaxy tab 10.1:
mtp-detect
libmtp version: 1.1.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 6
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
usb_open(): No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.
Date: 2012-06-28 15:45:29 PDT
Sender: nobody
Testing with libmtp 1.1.3, Samsug Galaxy tab 10.1:
mtp-detect
libmtp version: 1.1.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung
GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note
(04e8:6860) @ bus 2, dev 6
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB
interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
usb_open(): No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.
Are you trying this immediately after the device was plugged in?
This seems to be a factor in these devices.
Also make sure the screen is unlocked.
Yes: wake up device, unlock the screen, plug in, run mtp-detect. The tab itself says it is USB connected, but libmtp reports the error below
Same here. Archlinux 64bit, samsung galaxy tab2 7.0 (P3110).
The device says it is connected, but every operation fails.
Here is the output of mtp-detect -d
simone@orion:~$ mtp-detect -d
LIBMTP_Set_Debug: Setting debugging level to 9 (on)
libmtp version: 1.1.3
Listing raw device(s)
LIBMTP LIBMTP_Detect_Raw_Devices[663]: Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 3, dev 6
Attempting to connect device(s)
PTP: Opening session 0000: 1000 0000 0100 0210 0000 0000 0100 0000 ................
LIBMTP configure_usb_device[1993]: PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP configure_usb_device[1994]: LIBMTP libusb: Attempt to reset device
PTP: Opening session 0000: 1000 0000 0100 0210 0000 0000 0100 0000 ................
LIBMTP configure_usb_device[2005]: LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
It me again with archlinux and Galaxy Tab2 7.0.
I've tried to downgrade libmtp to 1.1.2 but with the very same results.
I'm testing out in the blind, the git contains a selection fix for the USB
interface, maybe you can test this. It's pretty tricky for me to debug
without the device :-(
I've tested the git version, but it doesnt seems to works as I've expected.
I'm attaching the output of mtp-detect, I don't know if it's helpful.
Just for reference, mtp-connect --sendfiles output is:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.5
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Send file /home/simone/sogno.txt
Sending /home/simone/sogno.txt to SSH_AGENT_PID=827
type: txt, 44
Sending file...
Error sending file.
Error 1: Get Storage information failed.
Error 2: PTP Layer error 2006: send_file_object_info():Could not send object property list.
Error 2: Error 2006: PTP: Parameter Not Supported
No response in ages, closing.