Fedora Linux Support Community & Resources Center
  #1  
Old 8th May 2012, 12:48 PM
Tieum Offline
Registered User
 
Join Date: Nov 2009
Posts: 58
linuxfirefox
Issues with Samsung I9100P

Hello,

I have several issues with my Samsung I9100P.



1) When plugin the phon in MTP mode I can see the root files and root directories but all directories are shown empy. I cannot see their content

2) When I unplug the phone, swith to USB debugging and replug the phone the USB port has an issue: the phone gets power but lsusb does not show the usb port anymore. If I plug in a different port everything is fine and I can use the USB mode.

ANy help to address those issues would be appreciated.
Reply With Quote
  #2  
Old 10th May 2012, 09:30 AM
george_toolan Offline
Registered User
 
Join Date: Dec 2006
Posts: 2,077
linuxfirefox
Re: Issues with Samsung I9100P

Code:
tail -f /var/log/messages
But it is working in usb mass storage mode now?
Reply With Quote
  #3  
Old 11th May 2012, 12:33 PM
Tieum Offline
Registered User
 
Join Date: Nov 2009
Posts: 58
linuxfirefox
Re: Issues with Samsung I9100P

After I change USB port or reboot the computer yes it works.

This is the log when I plus the phone in and the USB port disappears:

May 11 13:28:53 puitepee kernel: [15319.758113] usb 1-6: new high-speed USB device number 8 using ehci_hcd
May 11 13:28:53 puitepee kernel: [15319.873285] usb 1-6: New USB device found, idVendor=04e8, idProduct=685e
May 11 13:28:53 puitepee kernel: [15319.873294] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 11 13:28:53 puitepee kernel: [15319.873302] usb 1-6: Product: SAMSUNG_Android
May 11 13:28:53 puitepee kernel: [15319.873307] usb 1-6: Manufacturer: SAMSUNG
May 11 13:28:53 puitepee kernel: [15319.873311] usb 1-6: SerialNumber: 304D19446E71231F
May 11 13:28:53 puitepee kernel: [15319.875329] scsi8 : usb-storage 1-6:1.0
May 11 13:28:53 puitepee kernel: [15319.875882] cdc_acm 1-6:1.1: This device cannot do calls on its own. It is not a modem.
May 11 13:28:53 puitepee kernel: [15319.876085] cdc_acm 1-6:1.1: ttyACM0: USB ACM device
May 11 13:28:53 puitepee mtp-probe: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-6"
May 11 13:28:53 puitepee mtp-probe: bus: 1, device: 8 was not an MTP device
May 11 13:28:53 puitepee modem-manager[1313]: <info> (ttyACM0) opening serial port...
May 11 13:28:53 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (ttyACM0) opening serial port...
May 11 13:28:54 puitepee kernel: [15320.878339] scsi 8:0:0:0: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
May 11 13:28:54 puitepee kernel: [15320.878908] scsi 8:0:0:1: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
May 11 13:28:54 puitepee kernel: [15320.880947] sd 8:0:0:0: Attached scsi generic sg6 type 0
May 11 13:28:54 puitepee kernel: [15320.883113] sd 8:0:0:1: Attached scsi generic sg7 type 0
May 11 13:28:54 puitepee kernel: [15320.886310] sd 8:0:0:0: [sde] Attached SCSI removable disk
May 11 13:28:54 puitepee kernel: [15320.887526] sd 8:0:0:1: [sdf] Attached SCSI removable disk
May 11 13:29:00 puitepee modem-manager[1313]: <info> (ttyACM0) closing serial port...
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (ttyACM0) closing serial port...
May 11 13:29:00 puitepee modem-manager[1313]: <info> (ttyACM0) serial port closed
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (ttyACM0) serial port closed
May 11 13:29:00 puitepee modem-manager[1313]: <info> (ttyACM0) opening serial port...
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (ttyACM0) opening serial port...
May 11 13:29:00 puitepee modem-manager[1313]: <info> (Generic): GSM modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-6 claimed port ttyACM0
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (Generic): GSM modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-6 claimed port ttyACM0
May 11 13:29:00 puitepee kernel: [15326.549008] ehci_hcd 0000:00:12.2: force halt; handshake ffffc90000c20024 00004000 00000000 -> -110
May 11 13:29:00 puitepee kernel: [15326.549008] ehci_hcd 0000:00:12.2: HC died; cleaning up
May 11 13:29:00 puitepee kernel: [15326.552038] usb 1-1: USB disconnect, device number 2
May 11 13:29:00 puitepee kernel: [15326.552048] cdc_acm 1-6:1.1: acm_port_activate - usb_submit_urb(ctrl irq) failed
May 11 13:29:00 puitepee kernel: [15326.552618] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552659] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552677] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552693] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552709] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552724] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552740] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552755] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552773] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552790] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552806] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552852] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552889] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552923] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee kernel: [15326.552958] cdc_acm 1-6:1.2: acm_start_wb - usb_submit_urb(write bulk) failed: -19
May 11 13:29:00 puitepee NetworkManager[1210]: <info> radio killswitch /sys/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/ieee80211/phy0/rfkill0 disappeared
May 11 13:29:00 puitepee kernel: [15326.568779] usb 1-1: ath9k_htc: USB layer deinitialized
May 11 13:29:00 puitepee kernel: [15326.568962] usb 1-3: USB disconnect, device number 4
May 11 13:29:00 puitepee kernel: [15326.571092] usb 1-6: USB disconnect, device number 8
May 11 13:29:00 puitepee modem-manager[1313]: <info> (ttyACM0) closing serial port...
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (ttyACM0) closing serial port...
May 11 13:29:00 puitepee modem-manager[1313]: <info> (ttyACM0) serial port closed
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (ttyACM0) serial port closed
May 11 13:29:00 puitepee modem-manager[1313]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-6
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-6
May 11 13:29:00 puitepee modem-manager[1313]: failed to marshal parameter 1 for signal DeviceRemoved
May 11 13:29:00 puitepee dbus-daemon[1284]: modem-manager[1313]: failed to marshal parameter 1 for signal DeviceRemoved
May 11 13:29:00 puitepee NetworkManager[1210]: <info> (wlan0): now unmanaged
May 11 13:29:00 puitepee NetworkManager[1210]: <info> (wlan0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
May 11 13:29:00 puitepee NetworkManager[1210]: <warn> (4) failed to find interface name for index
May 11 13:29:00 puitepee NetworkManager[1210]: (nm-system.c:685):nm_system_iface_get_flags: runtime check failed: (iface != NULL)
May 11 13:29:00 puitepee NetworkManager[1210]: <error> [1336735740.591548] [nm-system.c:687] nm_system_iface_get_flags(): (unknown): failed to get interface link object
May 11 13:29:00 puitepee avahi-daemon[1237]: Withdrawing workstation service for wlan0.
Reply With Quote
  #4  
Old 13th May 2012, 08:52 PM
Tieum Offline
Registered User
 
Join Date: Nov 2009
Posts: 58
linuxfirefox
Re: Issues with Samsung I9100P

Now I update the phone to Ice Cream Sandwixh and it is even worse.

The phone as two modes: MTP and PTP. In both modes the folders show up empty in any mode including USB debugging and they have weird names:

00000001
00000002
...

In MTP mode: ID 04e8:6860 Samsung Electronics Co., Ltd
In PTP mode: ID 04e8:6865 Samsung Electronics Co., Ltd
In PTP mode with USB debugging: ID 04e8:6866 Samsung Electronics Co., Ltd

---------- Post added at 03:52 PM ---------- Previous post was at 03:14 PM ----------

After googling a little bit more I found mtpfs package but unfortunately it will not help:

# yum --enablerepo=updates-testing install mtpfs
...
# mtpfs mnt
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 1, dev 18
Attempting to connect device
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
Reply With Quote
  #5  
Old 1st June 2012, 12:35 AM
Fred Zyphal Offline
Registered User
 
Join Date: Nov 2011
Posts: 34
linuxfirefox
Re: Issues with Samsung I9100P

MTP has been broken in Linux for some time now, unless you use some app. like Rhythmbox that supports it ... the good news is ... it seems to be working quite well with everything I've tried, including Nautilus, in my brand new F17 installation.
Reply With Quote
  #6  
Old 5th June 2012, 09:00 PM
Tieum Offline
Registered User
 
Join Date: Nov 2009
Posts: 58
linuxfirefox
Re: Issues with Samsung I9100P

Thanks. I finally update to fedora 17 and can now copy files through the cable which is way faster than Wi-Fi!

---------- Post added at 04:00 PM ---------- Previous post was at 03:45 PM ----------

I was actually too optimistic. SOme files cannot be copied:

Error getting file: -6: Not Supported
Reply With Quote
  #7  
Old 10th December 2012, 05:05 AM
sashko Offline
Registered User
 
Join Date: Jun 2004
Posts: 25
linuxfirefox
Re: Issues with Samsung I9100P

Quote:
Originally Posted by Tieum View Post
[/COLOR]I was actually too optimistic. SOme files cannot be copied:

Error getting file: -6: Not Supported
same here. The worst thing is that among about a hundred .jpg files in one directory of my android device only about 10 latest ones give that error. Perhaps an android camera app is to blame?
__________________
F18 x86_64
Reply With Quote
  #8  
Old 10th December 2012, 07:56 PM
Tieum Offline
Registered User
 
Join Date: Nov 2009
Posts: 58
linuxfirefox
Re: Issues with Samsung I9100P

I am on ICS 4.0.4
Reply With Quote
  #9  
Old 8th March 2013, 04:37 PM
Tieum Offline
Registered User
 
Join Date: Nov 2009
Posts: 58
linuxfirefox
Re: Issues with Samsung I9100P

Upgrading to Jelly Bean and f18 and the issue is still there.

It is a pity I have to find a Windows box to transfer files to/from my phone :-(
Reply With Quote
Reply

Tags
i9100p, issues, samsung

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Samsung 2253bw / monitor issues (old video card problems?) Nevek Hardware & Laptops 0 21st July 2008 02:30 AM
samsung yp t7 rpgbilder Hardware & Laptops 1 19th August 2007 06:40 AM
Samsung CLP-300 andrewr Hardware & Laptops 3 6th April 2007 10:19 AM
FC3 Samsung DVD-ROM issues mndar Hardware & Laptops 3 16th March 2005 07:14 PM


Current GMT-time: 22:11 (Sunday, 21-09-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat