Computer doesn't recognise phone

English Hardware
#1

Opensuse 13.2/KDE desktop/i586 standard installation.
To copy files (e.g. photos) from out phone we use the USB cable and the phone showed up at the notifications similar to a USB flash drive. Although USB sticks still show the phone does not show anymore and we cannot connect. The dmesg command showed the following:

[10753.733775] usb 1-2: new high-speed USB device number 14 using ehci-pci
[10753.850037] usb 1-2: New USB device found, idVendor=12d1, idProduct=1037
[10753.850050] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10753.850057] usb 1-2: Product: Android Adapter
[10753.850064] usb 1-2: Manufacturer: Huawei Incorporated
[10753.850069] usb 1-2: SerialNumber: 20F3A3DF7D9C
[10753.852846] usb-storage 1-2:1.0: USB Mass Storage device detected
[10753.853208] scsi11 : usb-storage 1-2:1.0

Why is the mounting not working any more - apart from regular updates we haven’t changed anything? How can I access the phone?
Any help is very much appreciated.
Cheers
Uli

#2

No answer so far. I tried to research a bit more. I have mtpfs-1.1-16.1.i586 installed because of a newer tablet, however the phone is still old android 2.3 which used to connect straight to the USB. Can it be that the computer now tries a MTP transfer when the phone is a pre MTP device? The computer still recognises the phone and lsusb -vv results with this:

Bus 001 Device 016: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x12d1 Huawei Technologies Co., Ltd.
  idProduct          0x1037 Ideos
  bcdDevice            2.26
  iManufacturer           1 Huawei Incorporated
  iProduct                2 Android Adapter
  iSerial                 3 20F3A3DF7D9C
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              8 Mass Storage
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

Is there anyone around with a bit more knowledge than me?
Cheers
Uli

#3

As you have discovered the phone is showing up as a storage device. Is there a phone setting that needs to be configured to make it appear as a modem. FWIW, it may be that ‘usb-modeswitch’ is needed to expose the modem interface.

#4

Hm, I am not quite sure,but thus the OP mean that connecting the phone earlier did show a popup n the desktoop,where you could then click Dolphin,etc. and that such is no more the case now?

That reminds me of other threads where it also seemed that some USB storage devices work as intended (show up on the desktop, will then be mounted by the desktop) and others will not. That is they can be mounted using a mount statement, nut will not show a popup from the desktop.

In the case I mentioned, it was not a phone, but a nrand new USB stick (that worked onother systems):

  • dmesg still shows it as “mass-storage” like here, thus that is not a problem;
  • the device files are created, The OP could check that;
  • mounting using the device file is possible;
  • only problem being that the desktop does not offer the possibilities as normal.

That case is still unsolved. The problem is also in 13.2 and if I am correct, 13.1 did work as intended. Thus it seems to be a 13.2 problem. And as the OP indicates, it seems to be introduced after some update. I have no idea about Tumbleweed.

#5

Yes, I think you’re correct Henk. This is about mass storage vs MTP behaviour. (I jumped too quickly thinking that they wanted to connect to the phone as a modem.)

#6

On 2015-09-04 03:06, fuerstu wrote:
>
> Opensuse 13.2/KDE desktop/i586 standard installation.
> To copy files (e.g. photos) from out phone we use the USB cable and the
> phone showed up at the notifications similar to a USB flash drive.
> Although USB sticks still show the phone does not show anymore and we
> cannot connect. The dmesg command showed the following:
>
> Code:
> --------------------
> [10753.733775] usb 1-2: new high-speed USB device number 14 using ehci-pci
> [10753.850037] usb 1-2: New USB device found, idVendor=12d1, idProduct=1037
> [10753.850050] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [10753.850057] usb 1-2: Product: Android Adapter
> [10753.850064] usb 1-2: Manufacturer: Huawei Incorporated
> [10753.850069] usb 1-2: SerialNumber: 20F3A3DF7D9C
> [10753.852846] usb-storage 1-2:1.0: USB Mass Storage device detected
> [10753.853208] scsi11 : usb-storage 1-2:1.0
> --------------------

This is what shows up when I connect my Samsung phone, with Android 2 something:


<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.605081] usb 1-4: new high-speed USB device number 3 using ehci-pci
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.720291] usb 1-4: New USB device found, idVendor=04e8, idProduct=689e
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.720299] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.720304] usb 1-4: Product: Samsung Android USB Device
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.720308] usb 1-4: Manufacturer: SAMSUNG Electronics Co., Ltd.
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.720312] usb 1-4: SerialNumber: ......
<0.3> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.722168] cdc_acm 1-4:1.0: This device cannot do calls on its own. It is not a modem.
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.722308] cdc_acm 1-4:1.0: ttyACM0: USB ACM device
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.723757] usb-storage 1-4:1.3: USB Mass Storage device detected
<0.6> 2015-09-09 13:16:40 minas-tirith kernel - - - [12090.723901] scsi7 : usb-storage 1-4:1.3
<1.6> 2015-09-09 13:16:41 minas-tirith mtp-probe - - -  checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4"
<1.6> 2015-09-09 13:16:41 minas-tirith mtp-probe - - -  bus: 1, device: 3 was not an MTP device

<0.5> 2015-09-09 13:16:41 minas-tirith kernel - - - [12091.725822] scsi 7:0:0:0: Direct-Access     SAMSUNG  GT-S6500D        0100 PQ: 0 ANSI: 2
<0.5> 2015-09-09 13:16:41 minas-tirith kernel - - - [12091.726720] sd 7:0:0:0: Attached scsi generic sg2 type 0
<0.5> 2015-09-09 13:16:41 minas-tirith kernel - - - [12091.730925] scsi 7:0:0:1: Direct-Access     SAMSUNG  GT-S6500D Card   0100 PQ: 0 ANSI: 2
<0.5> 2015-09-09 13:16:41 minas-tirith kernel - - - [12091.731976] sd 7:0:0:1: Attached scsi generic sg3 type 0
<0.5> 2015-09-09 13:16:41 minas-tirith kernel - - - [12091.735659] sd 7:0:0:0: [sdb] Attached SCSI removable disk
<0.5> 2015-09-09 13:16:41 minas-tirith kernel - - - [12091.736906] sd 7:0:0:1: [sdc] Attached SCSI removable disk
<3.6> 2015-09-09 13:16:44 minas-tirith ModemManager 1386 - -  <info>  Creating modem with plugin 'Generic' and '1' ports
<3.6> 2015-09-09 13:16:44 minas-tirith ModemManager 1386 - -  <info>  Modem for device at '/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4' successfully created
<3.6> 2015-09-09 13:16:45 minas-tirith ModemManager 1386 - -  <info>  Modem: state changed (unknown -> disabled)

At this point, it works neither as modem nor as storage device, it is simply ready and waiting.
To connect to Internet using it, I have to use an option in the phone to tell it to share the connection via USB (in settings, WiFi zone and USB modem).
To access the storage, I have to instead access settings, USB utils (or slide down message area), then press the big “connect usb storage” button.
When I do, I get these further messages in the computer:


<0.5> 2015-09-09 13:23:58 minas-tirith kernel - - - [12528.613386] sd 7:0:0:1: [sdc] 62325760 512-byte logical blocks: (31.9 GB/29.7 GiB)
<0.5> 2015-09-09 13:23:58 minas-tirith kernel - - - [12528.614642] sd 7:0:0:0: [sdb] 3849068 512-byte logical blocks: (1.97 GB/1.83 GiB)
<0.5> 2015-09-09 13:23:58 minas-tirith kernel - - - [12528.614997] sd 7:0:0:1: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2015-09-09 13:23:58 minas-tirith kernel - - - [12528.616249] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.6> 2015-09-09 13:23:58 minas-tirith kernel - - - [12528.628865]  sdc:
<0.6> 2015-09-09 13:23:58 minas-tirith kernel - - - [12528.637042]  sdb:

Where as can be seen, two disks appeared, without partitions (sdb and sdc), and I can mount them by clicking on the disk icons that appear on my XFCE desktop.

But in your case, the disks do not appear on your machine.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#7

Thank you, all for replying to my thread.
I tried to mount the phone manually with mount sdb1 /mnt but - as dmesg showed - the computer did not recognise the phone as sdb1, I tried scsi11 instead but this too did not work. I could connect the phone to a different computer and I could download the images there or on this computer via Bluetooth. So this was the work around. May be I try to upgrade the phone…
Cheers
Uli

#8

On 2015-09-10 01:36, fuerstu wrote:
…
> and I could download the images there or on this
> computer via Bluetooth. So this was the work around. May be I try to
> upgrade the phone…

On my Samsung, I can transfer files via WiFi, somehow. I only tried
once. I don’t remember how O:-)

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#9

On Thu 10 Sep 2015 12:04:06 AM CDT, Carlos E. R. wrote:

On 2015-09-10 01:36, fuerstu wrote:
…
> and I could download the images there or on this
> computer via Bluetooth. So this was the work around. May be I try to
> upgrade the phone…

On my Samsung, I can transfer files via WiFi, somehow. I only tried
once. I don’t remember how O:-)

Hi
I use ssh/sftp, there are numerous clients available.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel
3.12.44-52.10-default If you find this post helpful and are logged into
the web interface, please show your appreciation and click on the star
below… Thanks!

#10

Perhaps a comparison to my own similar situation might trigger a helpful response.

My PC runs 13.2-64 & KDE, and my phone is a Nexus 6 running the very latest Android. l note that my complaint is similar to the OP despite the fact that my phone is much newer, and I further note that my problem also came about recently. Those things lead me to conclude that the issue might be with a recent change in my openSUSE. That conclusion is somewhat confirmed by the fact that, like the OP, I run zypper patch every weekend.

Prior to the patches installed on the weekend of Sept 1 I could download photos by simply plugging in the usb cable and opening any one of several photo programs to import the pictures. Shotwell for example is great as it automatically arranges photos in folders and subfolders according to year, month and date of exposure (vital for “progress pictures” used to verify contract compliance).

Since the Sept 1 updates I can no longer use any photo software to transfer my work. They are all unable to access the phone, though the error messages are varied. I can however use Dolphin (mtp) to access and read write to the phone by simply plugging it in and clicking on the entry for the phone that pops up auto-magically. (horribly inconvenient however as I now have to manually create daily folders and sort the files to the correct folders.)

There have been no updates to my phone for over a month, so I conclude that the issue is with an openSUSE patch created sometime in the week prior to Sept. Those patches include a kernel update, so I have tried booting with an older kernel but that didn’t change the behavior,.

I hope something above is helpful.