Related
Hello everyone,
So I've installed ACER's adb drivers, but when I connect the tablet to my computer it shows up as an MTP device. I've tried updating the driver and manually browsing to the driver's location, but windows says that driver is not compatible with my device? BTW: I am running a fresh install of Windows 7 64-bit.
Any tips would be appreciated.
Thanks!
I'm having the same issue. It seems like everyone else's Iconia "just worked" with adb.
I've tried installing the acer drivers. It puts a folder in my Program Files directory...but I don't see what I'm supposed to do there. There's "EUUDriverInstaller" but when I click on it nothing (seems to) happens.
When I plug the device in it uses some generic Microsoft driver to show the device contents but composite adb doesn't show up at all like it does for my Droid.
I've reboot several times on both device and laptop. I've uninstalled / reinstalled the application that made that driver directory.
I opened an application in the driver directory under the x64 folder and it opened up the windows driver installer and installed some drivers...but still no composite adb when I plug it in.
It was called "dpinst" and installed:
Linux Developer Community Net
Acer, Inc (androidusb) USB
Google, Inc (WindUSB) USB
then a couple others about a modem and ports
It is on usb debugging and I've toggled it on and off.
It's running 3.1 stock and I'm on x64 Windows 7
Both command prompt adb devices is empty under "List of devices attached" and Eclipse devices is empty.
My sdk is fully updated.
Curiously it appears Acer hides the driver if you specify Honeycomb 3.1
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
apapousek said:
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
Click to expand...
Click to collapse
I appreciate the suggestion, but I'd rather not install another partition just to adb connect this tablet.
Some additional differences I've noticed.
It seems like the tablet is going straight to mounting if that means anything. Connecting my Droid doesn't bring up the Autoplay menu while connecting the tablet automatically asks me how I want to access the data in the autoplay menu. It does *say* usb debugging is on, but no "ACER composite ADB interface" appears in my device manager.
Edit:
It seems like my situation is comparable to this guy in regards to the device just being treated like a flash drive. forum.xda-developers.com/showthread.php?t=734139 He says the rom was the problem...but I can't see why this stock rom should have an issue.
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
I'm too on Windows 7 64bits and for the drivers I go to http://support.acer.com/us/en/product/default.aspx
If you want I have re-upload the drivers on my 4shared
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
bpivk said:
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
Click to expand...
Click to collapse
I don't seem to have another icon. I have this one referring to the Iconia Tab, but when I right click on it it just treats it like a flash drive.
I can't link the picture yet (need to have 8 posts), but there is on "Acer Iconia Tab" in Devices and Printers, but there's no yellow exclaimation mark and when I right click it it just has the option to browse files, it treats it like a flash drive.
It's under "Unspecified"
EVEALEX62 said:
I'm too on Windows 7 64bits and for the drivers I go to
EDIT : [Had to remove URLS to quote]
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
Click to expand...
Click to collapse
I've downloaded those drivers, unzipping them, and ran the setup several times =/.
EDIT:
I feel like a tool, someone at stack overflow suggested I switch to a different port (not just unplugging / re-plugging it into the same one), I guess that finally told windows to reanalyze it. Should have figured it would have been something silly for such a basic problem, shame on me for keeping all my other ports full.
Thanks for the help everyone!
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
EVEALEX62 said:
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
Click to expand...
Click to collapse
That worked! Thanks.
Figured it out
Hey guys,
Thanks for all of your suggestions, but none of them worked. I ended up having to disable automatic driver installation, then went into Windows\System32\DriverStore\FileRepository and deleted the folders corresponding to the drivers that windows kept on insisting I wanted. After that everything worked great!
Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq
It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.
I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was
I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq
Drivers from acer website.
I have adb installed should this not be enough?
You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.
I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq
I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq
don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.
If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App
gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.
Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
kjy2010 said:
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
Click to expand...
Click to collapse
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
looking335 said:
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
Click to expand...
Click to collapse
And please my op... of course I tried the drivers from acer's site, both of them. And my sdk kit works, just like I said. But thanks!
officetally said:
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
Click to expand...
Click to collapse
Glad it was something simple!
Sometimes we always overlook the simple things.
But I would not have told on myself.to many other things could blame it on.giggles
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.
Hi all,
Of late i have been facing this issue of transferring media files from PC to my nexus 10. On connection, MyComputer just crawls and whenever it connects the file transfer bar shows virtually no progress. Even if the file is just a few MB. I also have 2 users on this tablet and on the other user the same thing happens. I have to do multiple restarts to fix this and multiple file transfers is not possible as the whole PC hangs and Windows Explorer crashes.
Any help will be appriciated.
PS. Windows 7 OS and stock N10 with 4.4.2
Hi,
While I can't help you with the Windows issue I can offer you a temporary solution! Which is using adb push.
To do as such please go to the Manta Help Thread and check how to set up adb and enable USB Debugging. From there you will now open a terminal in the folder you want to copy the files and type:
Code:
adb push *filename* /sdcard/
Now the file is in your Nexus 10, if you want to push many files, I suggest creating one folder with the files and pushing the folder itself.
Code:
adb push *foldername*/ /sdcard/
Hope this helps a little . I use it a lot since my Fedora can't recognise MTP hahaha .
~Lord
"All I ever needed was a little piece of hope" - World of Fantasy (Helloween)
Sent from my Xperia Z1
Have you looked at the wifi file transfer apps? - I've never tried them because I'm rooted and use Sambadroid.
Re the transfer speed problem I've a vague recollection that a USB 1 device, like a keyboard will pull other usb 2 devices on the same hub down to usb1 speeds. Have you tried other usb sockets? Other things you can try are disabling USB Legacy Support and enabling AHCI in your BIOS.
If you decide to pursue the USB problem then you may find these progs helpful
There's a microsoft program usbview.exe that you can get from MS here http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx It's also here http://www.ftdichip.com/Support/Utilities/usbview.zip . My copy is copyright 1996-98 and it runs under W8.1
http://www.nirsoft.net/utils/usb_devices_view.html
XxLordxX said:
Hi,
While I can't help you with the Windows issue I can offer you a temporary solution! Which is using adb push.
To do as such please go to the Manta Help Thread and check how to set up adb and enable USB Debugging. From there you will now open a terminal in the folder you want to copy the files and type:
Code:
adb push *filename* /sdcard/
Now the file is in your Nexus 10, if you want to push many files, I suggest creating one folder with the files and pushing the folder itself.
Code:
adb push *foldername*/ /sdcard/
Hope this helps a little . I use it a lot since my Fedora can't recognise MTP hahaha .
~Lord
"All I ever needed was a little piece of hope" - World of Fantasy (Helloween)
Sent from my Xperia Z1
Click to expand...
Click to collapse
Will try.
peterk-1 said:
Have you looked at the wifi file transfer apps? - I've never tried them because I'm rooted and use Sambadroid.
Re the transfer speed problem I've a vague recollection that a USB 1 device, like a keyboard will pull other usb 2 devices on the same hub down to usb1 speeds. Have you tried other usb sockets? Other things you can try are disabling USB Legacy Support and enabling AHCI in your BIOS.
If you decide to pursue the USB problem then you may find these progs helpful
There's a microsoft program usbview.exe that you can get from MS here http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx It's also here http://www.ftdichip.com/Support/Utilities/usbview.zip . My copy is copyright 1996-98 and it runs under W8.1
http://www.nirsoft.net/utils/usb_devices_view.html
Click to expand...
Click to collapse
Thanks
You've had a few tangential suggestions, the ADB push being the fastest with the hardware and software you have currently.
I don't actually store files on my "PC" really as my source, I store them on a NAS and then pull them either to my PC or my other devices. This makes all my devices "stateless" as I find individual devices I'm moving around with ultimately break more often so I prefer the NAS route. My NAS is a Raspberry Pi running Rasbian with a 1TB USB hardd drive and a 64GB OTG flashdrive.
You can add to the other ideas:
Airdroid which runs a small web server on your Android device and you access the Android device from browser on PC and push files, at Wifi speeds.
run web server on your "PC" and then in Android just get them in a download app. My "PC" is Linux and its running Apache and I either SSH from the PC to the Android and then wget the file or use of the file download methods inside Android.
USB OTG stick which also serves to augment capacity, I get about 22MB/s from USB to inside N10
One other indirect thing, is when you do a full Android flash wipe it seems to reformat and speed up the filesystem better than if you've done an upgrade, although I never benchmarked it to know, just an impression.