[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
@fmo: Bug #903422 is not a duplicate of this one. This bug here deals with Samsung related problems which are exisiting on pre-ICS versions. Bug #903422 deals with ICS (Android 4) on all kinds of devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
I believe this is the same problem as Bug #815055 and #903422. This bug seems to have been fixed in the newly released libmtp 1.1.3 see here http://sourceforge.net/projects/libmtp/files/libmtp/1.1.3/ I think it would probably also be a good idea to upgrade mtpfs to 1.1 http://www.adebenham.com/mtpfs/ (current version is 0.9-3) Not sure where to go from here but I hope it helps. ** Changed in: libmtp (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
The MTP stack found in these Samsungs seems to be the Microsoft one, with a lot of quirks to the USB level of things. I need to work hands-on with a device to progress on this... Else I rely 100% on users to hack with libmtp to get it working :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
** Changed in: banshee Status: Confirmed = Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
I also have a Samsung Galaxy S / GT-I9000 And like above it's miss detected on my Kubuntu 11.10 jonas@tor:~$ sudo mtp-detect libmtp version: 1.1.0 Listing raw device(s) Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959. Found 1 device(s): Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 1, dev 8 Attempting to connect device(s) LIBMTP PANIC: Unable to find interface endpoints of device Unable to open raw device 0 OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
Looking at the Galaxy Tab bug report: http://sourceforge.net/tracker/?func=detailaid=3372454group_id=158745atid=809061 It looks like the issue is Samsung implements Microsoft DRM, and there is no easy fix to get around this. ** Bug watch added: SourceForge.net Tracker #3372454 http://sourceforge.net/support/tracker.php?aid=3372454 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
Still not working: timothy@timothy-1005P:/usr/bin$ mtp-detect libmtp version: 1.1.0 Listing raw device(s) Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000. Found 1 device(s): Samsung: Galaxy S GT-I9000 (04e8:6877) @ bus 1, dev 5 Attempting to connect device(s) 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 Unable to open raw device 0 OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
It seems if I plug my device into usb then quickly run mtp-detect it will detect my device. However if I wait even a few seconds then it will fail this would point to some sort of locking issue I would have thought. What other applications might be interfering with libmtp??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
Running device-drivers gives me: T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#= 34 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04e8 ProdID=6877 Rev=04.00 S: Manufacturer=SAMSUNG S: Product=SAMSUNG_Android S: SerialNumber=1000b4332e7e C: #Ifs= 3 Cfg#= 4 Atr=c0 MxPwr=96mA I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 2 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=(none) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
My wifes Samsung Nexus S works with banshee, nautilus etc but comes up as: T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#= 42 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=18d1 ProdID=4e21 Rev=02.27 S: Manufacturer=Samsung S: Product=Nexus S S: SerialNumber=XX C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
Hmmm, ok if I turn on USB development in my phones settings and then enable USB mass storage drumroll.it works!! Banshee etc connect and detect the phone. And a storage device is added to the usb devices: T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#= 44 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04e8 ProdID=681c Rev=04.00 S: Manufacturer=SAMSUNG S: Product=SAMSUNG_Android S: SerialNumber=XXX C: #Ifs= 4 Cfg#= 3 Atr=c0 MxPwr=96mA I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none) I guess now someone smarter than me has to work out how to get access to the usb-storage without having to enable usb debugging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
Please ignore my last comment wtp does not work when you do that. The storage device just become accessible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
bigbrovar can you test this, I am currently stuck on OS X till such a time as correct installation of Linux on an EFI powered Mac Mini 2011 is possible (timeframe for this should be ca. F16 Beta, or roughly 2 months). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
Please give a try with libmtp 1.1.0 now available in Oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/696301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
I am having same issue with my Galaxy S I9000. when I run mtp-detect I get the following error libmtp version: 1.0.6 Listing raw device(s) Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959. Found 1 device(s): Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 2, dev 16 Attempting to connect device(s) LIBMTP PANIC: Unable to find interface endpoints of device Unable to open raw device 0 OK. I was trying to figure out why neither amarok nor banshee is able to sync with the galaxy S. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
On Ocelot (same libmtp): Banshee: [1 Warn 00:40:56.444] Failed to load media-player-info file for 1 [1 Warn 00:40:56.469] Failed to load media-player-info file for 1 [1 Debug 00:40:56.919] U1MS: Url Loaded: - http://stores.7digital.com/default.aspx?shop=436partner=983 Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959. [1 Warn 00:40:58.695] Failed to load media-player-info file for 1 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 [12 Debug 00:41:17.463] Failed to connect to mtp device. Trying 4 more times... 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 [12 Debug 00:41:39.524] Failed to connect to mtp device. Trying 3 more times... 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 [12 Debug 00:42:01.583] Failed to connect to mtp device. Trying 2 more times... 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 [12 Debug 00:42:23.644] Failed to connect to mtp device. Trying 1 more times... 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 [12 Debug 00:42:45.703] Failed to connect to mtp device. Trying 0 more times... [1 Warn 00:42:47.706] Failed to load media-player-info file for 1 mtp-detect: david@sagan:~$ mtp-detect libmtp version: 1.0.6 Listing raw device(s) Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959. Found 1 device(s): Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 1, dev 10 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface inep: usb_get_endpoint_status(): Device or resource busy outep: usb_get_endpoint_status(): Device or resource busy usb_clear_halt() on IN endpoint: Device or resource busy usb_clear_halt() on OUT endpoint: Device or resource busy usb_clear_halt() on INTERRUPT endpoint: Device or resource busy LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. The device is also still wrongly detected as a Vibrant, this is a Galaxy S i9000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
Please, could you try to reproduce this with the latest release of libmtp on Natty? ** Changed in: libmtp (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
** Bug watch added: GNOME Bug Tracker #639598 https://bugzilla.gnome.org/show_bug.cgi?id=639598 ** Also affects: banshee via https://bugzilla.gnome.org/show_bug.cgi?id=639598 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
same problem with the builds in Natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
It seems I can't add a second libmtp upstream bug to the list: http://sourceforge.net/tracker/?func=detailaid=3159038group_id=158745atid=809061 ** Bug watch added: SourceForge.net Tracker #3159038 http://sourceforge.net/support/tracker.php?aid=3159038 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
** Changed in: banshee Status: Unknown = Confirmed ** Changed in: banshee Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
One of those bugs should be marked a duplicate of the other, I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
It seems like this would be fixed with an update to the just released libmtp 1.0.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
I compiled the latest libmtp from git and now the device shows up in Nautilus but mtp-detect still gives errors. david@sagan:~/Projekter/libmtp$ mtp-detect libmtp version: 1.0.4 Listing raw device(s) Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959. Found 1 device(s): Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 1, dev 8 Attempting to connect device(s) 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 Unable to open raw device 0 OK. The device should be a Samsung Galaxy S GT-I9000 but now it is detected as a different model.. odd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696301] Re: Samsung Galaxy S detected but cannot be connected to
** Bug watch added: SourceForge.net Tracker #3026337 http://sourceforge.net/support/tracker.php?aid=3026337 ** Also affects: libmtp via http://sourceforge.net/support/tracker.php?aid=3026337 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696301 Title: Samsung Galaxy S detected but cannot be connected to -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
