Home / ubuntu / Questions / 1034919
In Process
Manfred Steiner
Asked: 2018-05-12 05:28:15 +0800 CST

Ubuntu 18.04 does not connect to Android smartphone

  • 772

Neither Bluetooth connection nor USB connection is able to transfer files from Android smartphone to Ubuntu 18.04. Same devices with Ubuntu 16.04 did not show any problems. When starting Nautilus, it shows the android device, but when opening it, it stays busy and does not show any results.

Ubuntu 18.04 kernel: 4.15.0-20-generic
Android Smartphone Samsung A3, Android 7.0

kernel.log messages when connecting the phone via USB seems to be OK:

May 12 05:39:53 len kernel: [69577.277832] usb 2-1: new high-speed USB device    number 28 using xhci_hcd
May 12 05:39:53 len kernel: [69577.427116] usb 2-1: New USB device found, idVendor=04e8, idProduct=6860
May 12 05:39:53 len kernel: [69577.427122] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 12 05:39:53 len kernel: [69577.427127] usb 2-1: Product: SAMSUNG_Android
May 12 05:39:53 len kernel: [69577.427130] usb 2-1: Manufacturer: SAMSUNG
May 12 05:39:53 len kernel: [69577.427134] usb 2-1: SerialNumber: 5203f8dd51fc142b

When starting Nautilus from shell and opening Android folder, I get the following message:

Nautilus-Share-Message: 05:41:13.818: Called "net usershare info" but it failed:  
Childprocess »net« could not be executed (No such file or directory)

My workarround at the moment: installing SSHHelper on Android and using scp to copy files via SSH.

android usb bluetooth

4 Answers

  1. I have the same problem with ubuntu 18.04 lts and a samsung s6 edge. When I connect the phone to my pc and open Nautilus it shows no files or folders. But I stumbled on a work around: close all instances of Nautilus, dismount the phone and turn it off without disconecting it. Then turn it on and sometimes Nautilus can see it. Hope it works for you

    • 3

  2. On the phone, you have to click on the notification that says "use this USB for charging" and change it to file transfer.

    • 1

  3. I had a similar problem, I tried this and worked, check:

    Ubuntu Linux: There are two things that need to be set up correctly: each user that wants to use adb needs to be in the plugdev group, and the system needs to have udev rules installed that cover the device.

    plugdev group: If you see an error message that says you're not in the plugdev group, you'll need to add yourself to the plugdev group:

    sudo usermod -aG plugdev $LOGNAME

    Note that groups only get updated on login, so you'll need to log out for this change to take effect. When you log back in, you can use id to check that you're now in the plugdev group.

    udev rules: The android-sdk-platform-tools-common package contains a community-maintained default set of udev rules for Android devices. To install:

    apt-get install android-sdk-platform-tools-common

    https://developer.android.com/studio/run/device

    • 1

  4. My experience shows me that the main culprit is often the cable or the usb port, which cause a faulty or dropping connection. When I happen to have these problems, often a new cable or the original one resolve the issue.

    • 1