Ok, I was ok with the far-less-than-par speeds when pushing files to the phone from the computer connected via USB (2.0 in my computer). When it reached an all new low, this is what you get:
Mind you, the file I pushed is 1.8MB!!!!!!
Code:
$ adb push Dorimanx_2.0.zip /sdcard/ROMS/
3 KB/s (1778643 bytes in 435.309s)
Its not my laptop, I know that for a fact, as I can connect my Galaxy Nexus the same way, and push the same size file, in less than half a second, and I can repeat that over and over again, any time I want.
Anybody else have any insight as to WHY its so damn slow to do ANYTHING on the G2?
Im running stock VS98012B, rooted, debloated, Xposed framework (with 3 running modules), and nothing else special done to the system.
Maybe the USB cord is having compatibility problems with the G2?
Im using the cord that came with the phone.
Same problem here, mate. Very slow and also the transfer often freezes. Most of the time when I want to transfer a file I must disconnect and then reconnect the phone for the transfer to start. Really annoying... I have this problem on both stock and AOSP roms...
Sent from my LG-D802 using Tapatalk
Related
when trying to transfer files from my mac onto my N4 using android file transfer (im on a mac) at first the device will load and then maybe after 5 seconds or less it will disconnect and reconnect for about 1 second on and off. it makes it really annoying to put roms onto the devices storage because i am able to start the transfer then after the 5 seconds it disconnects and the transfer fails. i know the usb works and everything because adb works fine. this happens on every rom/kernel i have tried. any ideas?
Hey guys anyone encounter when transferring files to the N10 via mtp that it transfer, but after a couple of minutes it will hang and pop up an error saying it lost communication with the device? The computer recognizes the N10 in mtp but after trying to transfer a file it would hang and that error will show. I mean this is not a huge problem for me since I just transfer my stuff wirelessly now which is a lot better, but I just wanted to see if anyone else has this problem and if there is a fix or is it on my end.
MTP switch off
vel0city said:
Hey guys anyone encounter when transferring files to the N10 via mtp that it transfer, but after a couple of minutes it will hang and pop up an error saying it lost communication with the device? The computer recognizes the N10 in mtp but after trying to transfer a file it would hang and that error will show. I mean this is not a huge problem for me since I just transfer my stuff wirelessly now which is a lot better, but I just wanted to see if anyone else has this problem and if there is a fix or is it on my end.
Click to expand...
Click to collapse
I only got my N10 today and while transferring music over from my laptop via mTP, I got the same problem you spoke of. I reconnected the cable, and copied the files over again without a hitch. Hope this isn't a persistent problem.
JB4.2.2
stock ROM and Kernel
marc4eva said:
I only got my N10 today and while transferring music over from my laptop via mTP, I got the same problem you spoke of. I reconnected the cable, and copied the files over again without a hitch. Hope this isn't a persistent problem.
JB4.2.2
stock ROM and Kernel
Click to expand...
Click to collapse
Yeah I got my Nexus about a week ago and noticed this problem. I wonder if it has to do with the adb drivers. My Nexus 4 though transfer files like a champ through MTP so idk whats wrong with the N10. But like I stated using the wifi transfer is actually better for me anyways.
3 things can cause the errors. 1. Not using the supplies USB cable 2. Not using Nexus 10 driver on the PC. (Or having multiple USB drivers for different devices) 3. Using a USB 3.0 port.
Fixes:
Use the provided USB cable.
Grab the Universal USB/ADB drivers which can be found in this forum.
Don't use USB 3.0 ports.
These issues are not Nexus 10 specific. As far as USB 3 ports go backwards compatibility is hit and miss.
The cable might not be functioning properly or the file downloaded is corrupted. Try to redl the file. Sometimes rebooting the device helps too
brees75 said:
3 things can cause the errors. 1. Not using the supplies USB cable 2. Not using Nexus 10 driver on the PC. (Or having multiple USB drivers for different devices) 3. Using a USB 3.0 port.
Fixes:
Use the provided USB cable.
Grab the Universal USB/ADB drivers which can be found in this forum.
Don't use USB 3.0 ports.
These issues are not Nexus 10 specific. As far as USB 3 ports go backwards compatibility is hit and miss.
Click to expand...
Click to collapse
I think its the usb/adb driver because I have like so many different devices that I installed through AIO toolkits from the past
Hi,
Not sure if others have had this issue yet, but its been driving me nuts for three days now.
Basically, I done a fresh flash to latest JB 4.3.1. now I having issues with transfering files via wifi or USB.
Its like its not mounting correctly or updating folders correctly.
If I try and transfer via usb, it will transfer one or two files then give error saying device is not present or some other stupid error.
If I try the same via wifi, it gives IO errors.
If I do anything on the tablet itself, it works fine. I can download games and stuff from store and it all works perfect.
This is why I didn't notice it until I spent 6 hours resetting it up and came to installing my emulator files.
I have tried different drivers, but nothing helps. This happens on complete stock or custom kernel.
Never had these issues with 4.2.2.
The current version is 4.3. The latest small update of about 2Mb keeps the version also at 4.3, but the Build number changes to JWR66Y. I had previously updated to 4.3 and recently took the small update to JWR66Y and my usb connection still works fine. If I use the original usb cable and use a rear usb port on my desktop, I have no problems with transferring files. Using a 3rd party cable or front usb port can result in the kinds of errors you're getting. I don't know why the wifi transfers are not working though.
Groid said:
The current version is 4.3. The latest small update of about 2Mb keeps the version also at 4.3, but the Build number changes to JWR66Y. I had previously updated to 4.3 and recently took the small update to JWR66Y and my usb connection still works fine. If I use the original usb cable and use a rear usb port on my desktop, I have no problems with transferring files. Using a 3rd party cable or front usb port can result in the kinds of errors you're getting. I don't know why the wifi transfers are not working though.
Click to expand...
Click to collapse
Yep, JWR66Y is the version.
Been using the same ports and cables before update all was fine. USB transfer has never been great, but to play up this bad is crazy.
I disconnected usb and rebooted, then used WiFi and it seems to be working ok.
So it has to be something to do with it mounting when USB is connected. If usb is connected and I do WiFi, then I get all types of odd errors.
In recovery, ADB pull works perfect. I can pull and push as much data as I want through USB.
Everytime I connect via usb, it tries to install drivers but fails. I am unable to transfer files like music, pics and was wondering if anyone had suggestions.
Have you tried downloading and installing LG's PCSuite?
Try to change different connection mode on the phone, like storage mode to copies files or PC Suite to sync files like iTunes.
sunnymiu said:
Try to change different connection mode on the phone, like storage mode to copies files or PC Suite to sync files like iTunes.
Click to expand...
Click to collapse
it might be the usb cord that is defective..
I've tried different cords and also different connect methods. I dont have the suit though, I'll download that and see how that goes. Its weird though because it was working prior to the kit kat update and tbh Im beginning to think its my computer that is having the issues and not my phone. But dont really know what to do about it.
You can also download the drivers from LG website on your phone models page.
Uninstall previous, install the new ones. Reboot computer.
Plug in phone and ignore the promotion phone to install. Choose appropriate mode for connecting and victory.
If not check in explorer on computer if phone is listed
That should do it
if you are talking about that little error in the bottom right of your computer screen that says something like usb failed to recognize with a yellow triangle, try rebooting that usually works for me if not
uninstall the lg driver
reboot then reinstall the lg driver and you should be good to go..
Hmm...idk but I think something wasn't right with my root. I checked on rootchecker and it was verified then I checked again it night and it wouldn't detect it. So I rerooted my phone and the connection seems to be working now. I hope this also takes care of all the other issues I've been having
Sent from my VS980 4G using XDA Free mobile app
Is your device manager blank?
Sent from my LG-LS980 using XDA Free mobile app
< Mod edit: thread closed at OP's request >
Hello,
I am currently using a Zuk Z1 running Cyanogen 12.1, based on Android 5.1.1.
For a while, I have been facing problems with the USB connection between my phone and computer.
Here is what I could observe:
When connecting my phone to my computer using MTP, I usually get an error such as
Code:
Could not enter folder /ZUK Z1.
.
Sometimes, I am able to access some files and move, create and delete some of them, but usually in less than 30 seconds, I get a similar error.
This problem happens with both Windows and Linux, on at least two distinct computers, and with at least two cables that worked fine with another phone.
I am able to connect a USB-C storage media to my phone and transfer files between them without errors, and the connection remains almost always "stable".
I am able to move large folders between my phone and computer using
Code:
$adb pull
and
Code:
$adb push
without any error or file corruption.
I would guess this is a software problem on the phone side.
I must add that the three buttons on the bottom of the screen do not work anymore, and I had to enable the on-screen navigation bar to use my phone.
Here is what I cannot figure out:
Is there a way to fix this problem while keeping the original ROM?
Could installing a custom ROM solve this issue? I would like to install a custom ROM ideally anyway.
Does installing a custom ROM present more risks in this situation? The few tutorials I read seem to indicate that if
Code:
adb
works, everything can be done, but I am a bit worried that the USB connection might die mid-flashing, or that some operations might require the broken buttons to work...
If the risk is increased, what tests could I perform to assess the risk more accurately before flashing?
Bonus: Any chance the broken buttons are also software-related and fixable?
Thank you all in advance for your help!