Title says it all. I'm trying to use adb with my tablet, but I can never seem to get it. I followed this tutorial, but all I get is this:
I don't understand. I tried native LG drivers, followed the aforementioned tutorial, and even just using the device vanilla. Nothing is working, and I don't know why. I manually added my vendor ID to the adb_usb.ini if anyone is curious. (LG's VID is 1004).
I solved my own question after 2 days of working with it. Hopefully this helps anyone in the future.
Procedure:
Enable developer options on the tablet
Enable USB Debugging under Settings > Developer Options
Go to Settings > PC Connection > Select USB connection method and select Internet connection > Ethernet
Go here and download the USB drivers for whatever OS you need (Windows Mirror)
Install the drivers and connect your device
Start adb and check if the device is connected
If for some reason the link in Step 4 ever dies, search for LG G Pad VK810 USB drivers from LG. If you have a different model from a VK810, make sure you use your model.
NOTE:
As mharr pointed out, you may not be able to find the setting in Step 3 on all devices, but if you have this setting, it is imperative that you set it, otherwise I discovered on my VK810 that adb will not work any other way.
Came across the same problem with LG V522 tablet.
Only choose the third or fourth option solved the problem.
(photo transfer, or as MIDI devices)
Unplug you tablet from the USB Connection
Go to Settings -> Developer Options
Check the USB Debugging
Plug the USB Cable
Related
I am getting started with Android development. I have an older Samsung Galaxy S2. But Android Studio doesn't recognize the device. I've tried going to the USB utilities but I can't seem to find them. Is my device too old?
You will have to enable the "USB debugging" option in your phone:you will get this after enable the "developer mode" on your phone(aka "developer options" on some devices).
Check this guide to enable this mode.
In addition - if you want to test your apps on a real device you will need to have a data USB cable(if you can upload stuff from your phone to your computer than you have the correct type of cable )
In some devices after enabling developer mode and connecting a cable you should scroll from the top side of the screen (Like in the photo) and click on USB for file transfer, and select Transfer files.
In addition to enable the Developer mode, if yet doesn't work, take a look at this page https://developer.android.com/studio/run/oem-usb, maybe with this driver you will have your problem solved: http://www.samsung.com/us/support/downloads
You can also check at your adb to make sure your device is connected:
cd cd c:\Users\Linda\AppData\Local\Android\sdk\platform-tools\
run: adb devices
It must shows your device's ID.
Hope it helps.
I was not using the correct cable. I assumed since the phone was charging I was using the correct usb cable to connect to my pc. Found a different cable, I believe the same cable that came with the phone. Now my device is found and working.
I am trying to connect my android device on mac to test application I developed.
First I installed USB driver, then I activated in my phone the developer option by tapping on Build Number and then tick USB debugging option.
Once I did all those steps when I connect my android mobile, my Mac still not recognize my device.
Any idea to solve it?
Maybe it's your USB cable, try another one.
There are two types of USB cables:
for supplying power only
for supplying power and data
I after few research and testing of existing solutions, I found mine, my issue was released while I have installed Android file Transfer for Mac
I experienced the same problem with a Moto X and my Macbook Pro. I tried many of the suggestions (installed Android File Transfer, tried different usb ports on my computer, Settings => Storage => USB computer connection => toggled between MTP and PTP, etc.). None of these other recommendations helped.
It finally worked when I tried a different micro-usb cable.
Bizarre. You definitely want to first enable Developer Options first by going to Settings => About Phone => tapping Build number 7 times to display Developer Options. From there, you want to enable USB debugging.
I found this solution to be helpful to resolve this problem
Connect your Android to your Mac via USB.
Unlock your Android's screen. ...
Swipe down to open the Android Notification Panel.
Tap the USB option in the Notification Panel.
Tap "File transfer" or "MTP."
Click the Go menu and select "Applications."
Double-click "Android File Transfer."
https://discussions.apple.com/thread/250023078
I had this problem. The only solution was to reboot my computer. Then it started working again.
Just to add my experience here. I had a similar problem with my mac book pro and my Google Pixel 1 device. For me when running adb devices locally, I was no longer showing my device on the list. I would see any emulators I had running, but not my physical device.
My solution and steps:
Go to the "Settings App"
Go to "Developer Options"
Revoke USB debugging Authorizations
Toggle Developer Options off / on
My device then prompted me to allow debugging from my computer and everything continued to work as expected. adb devices resulted in showing my connected device.
Hopefully, this will help someone else if the above does not.
Make sure to have debugging by usb enable on your device.
It is an option inside "Developer options"
I've recently (2018) started to have this issue, and have found the only way to get my device connected is to use a USB hub. I have not been able to track down a root cause but will edit this answer if I can find a solution rather than a workaround.
I connected my Android deceive with my mac:
1) If you use Android studio, you may update to latest version of 1.0.2 or 1.1 preview, because lower version have some problem with ADB connection.
2) You may restart your IDE once again.
3) You may go to settings -- storage -- three docs on the right up corner -- USB computer connection -- enable MTP
I have an HTC U11 and a MacBook Pro (2017). It used to work most of the time, but I experienced issues with it once or twice. Then a restart of the Mac solved the problem.
Recently I was not able to USB debug. adb devices gave nothing, even though my phone said I'm USB debugging (even asked if I wanted to).
After trying many things the solution was to connect my phone and run HTC Sync Manager (I also had to update it). Then it magically started to woek.
I hope it helps somebody.
check your android sdk tools, install your sdk-plateform-tools package.then it is ok
For me what fixed the problem is
i clicked on the notification "USB for file transfer" in the
notification panel on the phone
Clicked on "Transferring images"
Than I clicked on "Transferring files / Android Auto" and it was fixed.
I think I have done everything right but I cannot get Eclipse to recognize my plugged in running Samsung Tab-2. Below is what I have done. What have I done wrong?
1) I have instelled USB drivers and can move files from the tablet to the Windows XP computer.
2) I have enabled USB debugging on the phone
3) I have been debugging on a virtual device then sending the apd files over email to my tablet and phone. That works fine. Obviously, I have enabled that on the phone.
4) I set up Eclipse to always ask what device to debug on.
5) I plugged the tablet into the USB slot and it is recognized by Windows.
6) I read the instructions Here
7) I click debug and am faced with a blank list of devices under "Choosing a running Android Device". My tablet does not show up.
8) I find myself at wit's end (adventure reference).
9) I ask for help on Stackoverflow.
I think you should take a look at this answer. An identical issue was accepted at that post.
Hope it works to you!
Try a different MicroUSB cable, I have seen this affect the device showing up in Eclipse, even if the cable is working fine for everything else (even transferring files to/from that specific device).
If nothing works you can use adb over wifi by calling : adb connect "your ip adress". I am assuming the Tab runns Android ICS. You can enable Adb over wifi right under the USB debugging- menu point.
How many times have I called tech support and had them tell me to reboot windows? Well, the solution was to reboot windows. Nowhere in any of the installation instructions did I skip a step of rebooting but just thought I should try that.
I am trying to enable USB Debugging on Android so that I don't need to use the emulator.
I did what all the posts all around the web say to do: I went to settings -> applications -> Developer -> USB debugging
It still does not turn on the notification sign that USB Debugging is enabled, and Eclipse does not recognize it, and uses the regular emulator.
Does anyone have any idea what is wrong?
You haven't specified what device you are using or what operating system you are using, so that could be helpful.
A few things to keep in mind:
1 Don't mount as USB storage.
2 You also need to make sure to install the drivers for your phone so that the Android Debug Bridge (ADB) can properly communicate. After these are installed, try the command "adb devices" and you should see an item in your list of devices.
Update based on your comment: You can download Kies from Samsung, which include the drivers (as well as other things): http://www.samsung.com/us/kies/
Or you can find unofficial driver-only packages, such as: http://forum.xda-developers.com/showthread.php?t=961956
I think you'll need the OEM USB dirvers.
Read this:
OEM USB Drivers
My experience with windows has been that you might need to un-install the USB drivers under device manager. Then disconnect the device (restart might be required). After plugging the device back in make sure you use the manufactures drivers if available
you have installed your device driver rite?then right click on your app name->run as->run configurations->target->select manual->apply.after that click on debug button then it will ask you to select the device.
If everything else is tested, try with another USB cable.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
Fruthermore on some devices you will be asked to accept an RSA key, which allows debugging through your computer. This ensures that other adb commands cannot be executed unless you're able to unlock your device.
Detailed information can be found here:
http://developer.android.com/tools/help/adb.html It is the overview about adb commands (which is used to send data to your device) and it starts with the steps how to bring your phone to debug-mode.
I wish to add to Danation's answer with the following.
If you have installed KIES, and you've tried following instructions a couple of times (for the android SDK package) without success, here's what worked for me:
As a precaution, disconnect the device, and press 'Revoke USB Debugging authorizations'.
Now, go to kies, and reinstall the device driver as seen on the image below.
Connect the device.
For me, it was a routine, it usually works when installing kies, but I was stuck on this today for a little while, and I hope i can help others with my solution as well..
I've connected my Samsung Galaxy Tab device to my Mac. Yes, I've turned on debugging. When I go to run my application to test on the device the device is not listed on the Android Device Chooser menu. Running the ./adb devices shows no results.
NOTE: Posting this question for others to find. When looking for the solution earlier all I was able to locate were answers to broken links to device driver downloads for Windows.
Make sure you uncheck
Settings > Applications > Unknown Sources (Allow installation of non-Market applications)
Turn on USB Debugging inside Settings > Applications > Developers Settings
If you're trying to connect to a Mac, I had this issue with a Samsung Galaxy Tab 10.1 running Android 4.3. To enable developer options, open the Settings app, tap on "About device" under the "General" tab and then tap on the "Build number" repeatedly (it's grayed out but you can tap on it anyway). A small pop-up will appear showing the amount of additional taps you need to do to turn on these options.
Once enabled, just turn on USB Debugging and it'll show up in Eclipse just fine.
I had this problem on my Mac and after 30 minutes tried switching USB ports and it finally started working on the second port.
I fixed it by reboot the device (Samsung Galaxy Tab2 7.0)
Update your driver for samsung. It can be found here: http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Connecting your phone after development mode is on, and USB debugging is on.
At connecting to the PC the phone asks to trust this location. Finally.
This fixed my problem while all other tips were incomplete.
It does not answer your question of how to get ADB to see the device - I could not get that working. But what I did to install an APK I needed to test was to put it in Dropbox on my computer, then install it from there on the device.
Connect your device via USB hub instead of directly connecting to one of the usb ports on MAC. It worked that way for me. Please give a try.
There's also a pop-up that comes up at times requesting the currently connected computer to have access to your device(not to be confused with the Linux not supported pop-up; it lies ; ] ). I continued to receive Target:Unknown in Eclipse until I managed to catch it and accept. This is on a Samsung Note 8", which I believe is registered as a Tab 10.1 in my Arch Linux udev rules.
It may also happen that USB debugging is not checked on your device. Please go to developper options in your device and check it is enabled.
By the way, for devices with android Jelly Beam (4.2) and later versions, you will find out that this option is hidden. To activate it, click 7 times on the compilation number, and the option will be activated.
Tried everything, nothing helped. Including
USB debugging enabled
MTP/PTP
ADB restarted
Device/PC restarted
Tried Samsung's USB driver
By tricking/modifying driver installer, installed Google OEM Usb drivers for Galaxy Tab.
All software up-to-date
The only thing that helped is installing Kies3 + setting PTP on device, instantly authorization pops out in device. Everything OK now.
Kies3 download here: http://www.samsung.com/uk/support/usefulsoftware/KIES/
Enable USB Debugging mode solve the problem!
For those who don't know how to enable it (it's very hidden on Android 4.3 onward), see this.
In my case, this solved the problem:
unchecked the Settings->Security->Unknown Sources,
clicked on the upper left corner and changed USB mode from MTP to PTP,
unplugged/plugged the device, and
clicked OK on the USB debugging prompt.
Had this problem last year, never solved it. Again, after googling high and low, I could not find a cure for the USB debugging flakiness. Now for the good news:
1) Root your device. 2) Install adbWireless widget from Play (I am in no way associated with the author).
You are now good to go. After starting adbWireless and following its directions, you can now debug through adb wirelessly to your device, in my case, the original 7" Galaxy Tab.