Announcement

Collapse
No announcement yet.

Lenovo A6000 dropping connection

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Lenovo A6000 dropping connection

    I am not sure if this is a software or some hardware issue. but the connection between PC and phone is dropped/lost while doing the file transfer (pictures). it doens't have anything to do with phones power management (we tried to keep using it when it got lost again).

    Here are the system log messages (there is a whole bunch of them, so just an excerpt):

    Code:
    07/10/16 05:03:10 PM	tatie-desktop	kernel	[ 6323.025979] usb 1-2: usbfs: process 9338 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:10 PM	tatie-desktop	kernel	[ 6323.134910] usb 1-2: usbfs: process 9341 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:10 PM	tatie-desktop	kernel	[ 6323.248030] usb 1-2: reset high-speed USB device number 9 using ehci-pci
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.381618] usb 1-2: usbfs: process 9341 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.381863] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.381881] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.381893] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.381971] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.381985] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.381997] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.382009] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.382021] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.382033] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.382045] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.382057] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    
    
    ...
    
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.415527] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.415588] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	tatie-desktop	kernel	[ 6323.420208] usb 1-2: usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:14 PM	tatie-desktop	kernel	[ 6327.022303] usb 1-2: usbfs: process 9160 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:22 PM	tatie-desktop	kernel	[ 6335.337681] usb 1-2: usbfs: process 9354 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:23 PM	tatie-desktop	kernel	[ 6335.452027] usb 1-2: reset high-speed USB device number 9 using ehci-pci
    07/10/16 05:03:23 PM	tatie-desktop	kernel	[ 6335.585006] usb 1-2: usbfs: process 9354 (kio_mtp) did not claim interface 0 before use
    these are the kernel log messages (also plenty of them, so just an excerpt):

    Code:
    07/10/16 05:03:11 PM	usb 1-2	usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	usb 1-2	usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:11 PM	usb 1-2	usbfs: process 9317 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:14 PM	usb 1-2	usbfs: process 9160 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:23 PM	usb 1-2	usbfs: process 9354 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:03:23 PM	usb 1-2	reset high-speed USB device number 9 using ehci-pci
    07/10/16 05:03:23 PM	usb 1-2	usbfs: process 9354 (kio_mtp) did not claim interface 0 before use
    07/10/16 05:13:15 PM	usb 1-2	USB disconnect, device number 9
    last one is when device was then disconected. So any ideas what is going on? seems that it worked fine before, but not lately. Works well on windows on another PC. So i ended up downloading there and transfering to Linux PC over SAMBA-

    #2
    The connection is using a protocol called MTP which was invented by Microsoft, and often gives trouble; on some phones it doesn't work at all or is flaky. If you have a network that your computer is on and the phone connects to wirelessly, it's far simpler, easier, and more functional to use the network.

    On 14.04 you haven't got KDE connect, now part of KDE for just this purpose. So if your phone is android I recommend using AirDroid, a free app that turns your phone into a web server that your browser can access. I really like being able to type text messages using a real keyboard, for the phone to send.
    Regards, John Little

    Comment


      #3
      yes, phone has wireless LAN option available. what are alternative network protocols i can use? sFTP?

      Airdroid seems to require some payments, while the free option look limited. Also i am not sure i want transmitting anything from this phone. surelly there is a better option to do only the file transfer?

      Comment


        #4
        used a workarround by using USB mode for file transfer, but after certain update in October or maybe already in September it started crashing Dolphin. when files are moved it is showing them being moved until suddenly everything freezes. desktop and all. nothing helps but a hard reset.

        still on 14.04 LTS...

        any ideas how to solve this? is there something i could upgrade?

        the fear i have is that 16.04 will not be working as good as 14.04 is.

        Comment


          #5
          Originally posted by mastablasta View Post
          .... is there something i could upgrade?

          the fear i have is that 16.04 will not be working as good as 14.04 is.
          14.04 and 16.04 have the same EOL date, in April of 2019.

          Upgrade to either 16.04.x (where x is the latest release version) OR to KDE Neon User Edition.

          I chose the Neon User Edition. I've been using Linux since May of 1998 and Neon is the BEST "distro" I have ever run, bar none.

          I
          "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
          – John F. Kennedy, February 26, 1962.

          Comment


            #6
            PC is relatively old celeron E3300 with 2 Gb ram and with a strange motherboard (has DDR and DDR, AGP and PCIe 1.0). i tried to upgrade the GPU to a PCIe one but it could only run it with noveau drivers (with the AMD one it didn't even boot), so i gave up and went back to the old ATI AGP card which only has 256 Mb ram. we use the PC for a few games that actually work and don't freeze the desktop and some website editing and web surfing.

            due ot the motherboard sound is an often an issue where the chip is set as dummy and not always recognised at boot. but i have a working workarround for that. anyway at the moment the PC is setup so that it kind of works. and while 16.04 works really well in live session i have no idea what thing will stop working if i install it. printer, sound, games, you tube videos, DVDs...

            so if possible i would just upgrade what i need to, to get this working as it should. if there is no other way i guess i need to clone the OS and perform an upgrade. i have a free external drive and owuld be able to do that.

            Comment

            Working...
            X