My USB Mass Storage telephone is not being mounted properly under 13.1 and I haven’t found any answer as to why or what can be done. I have a Samsung Galaxy S I device and want to transfer files between phone and PC. Anyone?
Some gneral advice.
Directly after connecting the device, look at the last lines of
dmesg
You may post them here (between CODE tags, the # button in the tool bar of the post editor) for advice,
Also, when it is an USB device, you can list all USB devices (when connected) with
lsusb
On 2013-12-17 16:46, chuckenheimer wrote:
>
> My USB Mass Storage telephone is not being mounted properly under 13.1
> and I haven’t found any answer as to why or what can be done. I have a
> Samsung Galaxy S I device and want to transfer files between phone and
> PC. Anyone?
Define properly. Does it mount somehow, not at all, shows file names,
fails to copy files, what?
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[26524.202702] type=1400 audit(1387303130.599:2690): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm="nmbd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[26534.213044] type=1400 audit(1387303140.609:2691): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm="nmbd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[26544.223230] type=1400 audit(1387303150.620:2692): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm="nmbd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[26554.233414] type=1400 audit(1387303160.630:2693): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm="nmbd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[26564.243601] type=1400 audit(1387303170.640:2694): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm="nmbd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[26574.253787] type=1400 audit(1387303180.650:2695): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm="nmbd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[26580.736044] usb 3-2: new high-speed USB device number 12 using ehci-pci
[26580.861634] usb 3-2: New USB device found, idVendor=04e8, idProduct=681c
[26580.861641] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[26580.861644] usb 3-2: Product: SAMSUNG_Android
[26580.861648] usb 3-2: Manufacturer: SAMSUNG
[26580.861650] usb 3-2: SerialNumber: 3730779EFD6200EC
[26580.883219] cdc_acm 3-2:1.0: This device cannot do calls on its own. It is not a modem.
[26580.883579] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[26580.885806] usb-storage 3-2:1.2: USB Mass Storage device detected
[26580.885969] scsi14 : usb-storage 3-2:1.2
[26581.893018] scsi 14:0:0:0: Direct-Access SAMSUNG SPH-D700 Card PQ: 0 ANSI: 2
[26581.895453] sd 14:0:0:0: Attached scsi generic sg2 type 0
[26581.899493] sd 14:0:0:0: [sdb] Attached SCSI removable disk
[26584.255662] type=1400 audit(1387303190.652:2696): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm="nmbd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
charles@linux-uc1g:~>
charles@linux-uc1g:~> lsusb
Bus 003 Device 012: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica/S
Bus 004 Device 002: ID 046d:c30a Logitech, Inc. iTouch Composite
Bus 004 Device 003: ID 0461:4d0f Primax Electronics, Ltd HP Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
charles@linux-uc1g:~>
Here we are.
Not at all. Fails to “notify” a device has connected. Fails to show up in Dolphin file manager as a device.
On 2013-12-17 19:06, chuckenheimer wrote:
> Code:
> --------------------
> [26524.202702] type=1400 audit(1387303130.599:2690): apparmor=“DENIED” operation=“mkdir” parent=1 profile="/usr/sbin/nmbd" name="/var/cache/samba/" pid=641 comm=“nmbd” requested_mask=“c” denied_mask=“c” fsuid=0 ouid=0
This is unrelated, but you have to adjust the apparmor “nmbd” profile,
else you will have problems with samba shares.
> [26580.736044] usb 3-2: new high-speed USB device number 12 using ehci-pci
> [26580.861634] usb 3-2: New USB device found, idVendor=04e8, idProduct=681c
> [26580.861641] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [26580.861644] usb 3-2: Product: SAMSUNG_Android
> [26580.861648] usb 3-2: Manufacturer: SAMSUNG
> [26580.861650] usb 3-2: SerialNumber: 3730779EFD6200EC
> [26580.883219] cdc_acm 3-2:1.0: This device cannot do calls on its own. It is not a modem.
> [26580.883579] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
> [26580.885806] usb-storage 3-2:1.2: USB Mass Storage device detected
> [26580.885969] scsi14 : usb-storage 3-2:1.2
> [26581.893018] scsi 14:0:0:0: Direct-Access SAMSUNG SPH-D700 Card PQ: 0 ANSI: 2
> [26581.895453] sd 14:0:0:0: Attached scsi generic sg2 type 0
> [26581.899493] sd 14:0:0:0: [sdb] Attached SCSI removable disk
> charles@linux-uc1g:~>
I get the same, but to really connect, I have to select an option in the
Android drop down notification bar.
>
> --------------------
> <1.6> 2013-12-17 19:18:28 Telcontar mtp-probe - - - checking bus 1, device 18: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6"
> <1.6> 2013-12-17 19:18:28 Telcontar mtp-probe - - - bus: 1, device: 18 was not an MTP device
> <0.5> 2013-12-17 19:18:29 Telcontar kernel - - - [565648.016538] scsi 21:0:0:0: Direct-Access SAMSUNG GT-S6500D 0100 PQ: 0 ANSI: 2
> <0.5> 2013-12-17 19:18:29 Telcontar kernel - - - [565648.016801] sd 21:0:0:0: Attached scsi generic sg5 type 0
> <0.5> 2013-12-17 19:18:29 Telcontar kernel - - - [565648.018165] scsi 21:0:0:1: Direct-Access SAMSUNG GT-S6500D Card 0100 PQ: 0 ANSI: 2
> <0.5> 2013-12-17 19:18:29 Telcontar kernel - - - [565648.018414] sd 21:0:0:1: Attached scsi generic sg6 type 0
> <0.5> 2013-12-17 19:18:29 Telcontar kernel - - - [565648.022408] sd 21:0:0:0: [sde] Attached SCSI removable disk
> <0.5> 2013-12-17 19:18:29 Telcontar kernel - - - [565648.023199] sd 21:0:0:1: [sdf] Attached SCSI removable disk
The above is before pressing the button in the Android device.
Below appears just after.
> <0.5> 2013-12-17 19:20:18 Telcontar kernel - - - [565756.902352] sd 21:0:0:1: [sdf] 62325760 512-byte logical blocks: (31.9 GB/29.7 GiB)
> <0.5> 2013-12-17 19:20:18 Telcontar kernel - - - [565756.903095] sd 21:0:0:1: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.6> 2013-12-17 19:20:18 Telcontar kernel - - - [565756.910355] sdf:
> <0.5> 2013-12-17 19:20:20 Telcontar kernel - - - [565758.947769] sd 21:0:0:0: [sde] 3849068 512-byte logical blocks: (1.97 GB/1.83 GiB)
> <0.5> 2013-12-17 19:20:20 Telcontar kernel - - - [565758.948514] sd 21:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.6> 2013-12-17 19:20:20 Telcontar kernel - - - [565758.959021] sde:
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Yes, yes, yes! I had upgraded my device to the newest of The People’s ROM v 2.22 and it similarly incremented the firmware version to 2.3.6 which now allows me to activate the USB Mass Storage function to connect properly. Here again, another hurdle with OpenSUSE 13.1 has been negotiated and I am once more a very happy camper. Thanks to you all for your continued hand holding of this newbie and know that my job is made easier with help of this magnitude.
This is unrelated, but you have to adjust the apparmor “nmbd” profile,
else you will have problems with samba shares.
I will approach this task in a timely manner but don’t know what it is exactly that I need to do. I will post again another message with this as the topic header and go from there. Thank you for the advisory.
Good catch Carlos. So, the Android (mass storage connectivity) must be initialized at the Android end by pressing that button. I assume it is some kind of notification. Do you know what the dialogue is called?
On 2013-12-17 19:56, deano ferrari wrote:
> initialized at the Android end by pressing that button. I assume it is
> some kind of notification. Do you know what the dialogue is called?
I get it in Spanish and it is very prominent to see. At the top of the
display there is an horizontal bar with very notifications icons. If you
touch it and slide the finger down, they expand. One of them is about
the USB storage, press it, and a full screen dialog appears, with a
prominent button that says press to transfer files.
Mine is the original firmware, with Android 2.3.6, a galaxy mini 2 model.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
I have to do the same with my ancient ZTE mobile before it will appear in KDE.
Thanks for clarifying Carlos. 
FWIW, I have an iPhone 4S which has been upgraded to iOS 7. It uses MTP connectivity, but I get a pop-up request with ‘Trust/Don’t Trust’, before I can view files. (There is some strange issue with the USB communication whereby, the KDE notifier pops up again, and the request dialogue shows again, over and over, but I ignore both once I have acknowledged the first time, and proceed with navigating the files via Dolphin.)
On 2013-12-18 05:56, deano ferrari wrote:
> Thanks for clarifying Carlos.
>
> FWIW, I have an iPhone 4S which has been upgraded to iOS 7. It uses MTP
> connectivity, but I get a pop-up request with ‘Trust/Don’t Trust’,
> before I can view files.
Well, MTP is a different beast altogether. I assume it allows you access
to the files without disconnecting the entire storage from the phone; I
mean, in my case, the storage is connected solely to the computer or to
the phone.
I assume with MTP there is no such restriction, the phone remains in
control while the computer has access. I don’t have any such device to
verify.
> (There is some strange issue with the USB
> communication whereby, the KDE notifier pops up again, and the request
> dialogue shows again, over and over, but I ignore both once I have
> acknowledged the first time, and proceed with navigating the files via
> Dolphin.)
Well, at lest it works for you.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Yes, that is true. That is supposed to be one of the advantages of MTP communication, but unfortunately, for many Linux users it doesn’t work quite as well as it should.