I am moving from Windows over to Ubuntu 14.04 for my Android application development. By biggest worry was to figure out how to make Android devices work with adb on Ubuntu. Various articles on the Internet talk about creating /etc/udev/rules.d/51-android.rules file and adding specific information for each Android device.
However, I didn't do any of that. I just plugged in my Android phone to the USB port and typed "adb devices." There was a question on my phone about trusting the attached computer. After I said yes, adb listed that device as usable.
I tried plugging in another phone. Once again, adb just recognized the device.
I don't see any rules for USB under /etc/udev/rules.d directory and I certainly didn't create one. I am just curious on how adb automatically recognized my devices.
I have two Android phones
Alcatel One Touch 4030D, Android version 4.1.1, kernel version 3.4.0
Highscreen Spark, Android version 4.0.4, kernel version 3.0.21-perf.
adb devices detects the Alcatel phone, but not the Highscreen phone.
I tried to run adb kill-server; adb start-server, but it didn't help. Switching between different connection modes (Media device (MTP), USB storage) didn't help either. USB debugging is enabled.
Here are the screenshots of the Developer options settings:
How can I make adb recognize the Highscreen device?
Update 1 (03.08.2013 19:00 MSK): Adding the line 0454 to adb_usb.ini didn't help.
Update 2 (03.08.2013 19:59 MSK): My attempt to follow the official Google recommendations failed because I couldn't find the drivers for the Highscreen Spark device.
If you could setup an ADT on Linux or Mac, it will work out of the box.
We were able to connect all sorts of devices to adb easily with ADT on Linux/Mac.
If you haven't managed to connect it through usb, you can try the network connection.
Add your device to the same network, then type in the command prompt:
adb connect your_device_ip_address
Hey try to dig for drivers at Official website.
May be search other sites for USB drivers, that may help you to come out of your problem.
I had the same problem .Try it again by activating the usb mass storage.
Without adb driver for device (in your case Highscreen Spark) it is almost impossible to create a bridge(connection) between your program and device, as adb (Android Debug bridge) makes a connection between your PC/laptop to your android device And without Adb in windows Pc/Laptops its not easily possible to debug.
Because of this, Companies like samsung, lg, htc are providing adb drivers to users for easy debugging, if you dont have a adb driver for Your Device you have only one choice left , Change your operating System into linux and then see the magic.
I had this same problem. Turns out, the issue was the USB Port I plugged in to. The port directly on my laptop does not allow for ADB to see the device. The port on the back of my docking station does allow ADB to see the device. I believe it has to do with USB 3.0 vs. 2.0. I believe 3.0 blocks the protocol ADB needs to use.
You will actually require the device drivers to connect it, so try insatalling Highscreen Spark's PC Suite.
If that dosen't work or you don't find the PC Suite you can download Moborobo from here which is a universal PC Suite for smart phones and connect the device with it and then try connecting the device from abd
It may be a problem with your adb.exe. I had the same problem earlier for connecting HCL G1 tablet. I also added lines in android_winusb.ini, but could not connect yet. Then I found out this link. I got solution by changing the adb.exe file. Try this link : http://www.slatedroid.com/topic/37692-adb-drivers-problem/ Or just download the adb.exe from following link and replace it with you adb.exe file. http://sdrv.ms/NepKED It is also suggested run this command to make adb_usb.ini effective for respective adb after modifying. echo 0x2207 >> %USERPROFILE%.android\adb_usb.ini
Try these drivers
x86
x64
It works for me.
After head banging for more than a day - a small thing saved my life on my RK3066 based device:
after you update the adb_usb.ini and everything else,
and after you do a
adb kill-server
do a
adb usb
and only then do a
adb devices
saved my life
By the way
Adding the line 0454 to adb_usb.ini didn't help.
you should be adding 0x454
I was having issues with my android phone showing up when I typed adb devices but found out that it was the usb cable which caused the issue, members in my family have two different android phones each with their own charging cable. I was using one phone with the other phones usb cable just because it was the nearest and I didn't think it would make a difference but it did.
Try a different usb cable and that might help.
I have the same issue in the past but i don't found the driver on my computer today, so :
You can go on http://www.alcatelonetouch.com and find the call center for your land.
Call them , and explain the issue , they have to send you a driver to connect your phone to the computer. This drivers is very easy to install.
I have make that and i can use it for debbuging
I whish you good luck... Sorry for my English
I would like to control one android device with another. I have a Samsung Galaxy S III with the USB Host adapter, and would like to control another android phone via ADB. I've looked into this SO post:
build android adb for arm processor
but this isn't necessarily for and Android Host.
Does anyone know how one would go about building ADB for Android? Has it already been done?
Also, would it be "easier" to build ADB against a Linux distro running on the device under emulation? Would control of the device USB port by an emulation app be possible?
Any feedback is much appreciated!
I found a project with this purpose:
p2p-adb.
It has an on-the-device adb executable, so one can 'debug'/control other phones with a phone.
everyone, I would like to connect my galaxy nexus to the eclipse, which allows me to use the real device for debugging my program, however, my galaxy nexus does not appear even I have clicked on the usb debugging option in the developer mode. Can anyone give a hand to me, thank you!
Which operating system are you using?
If on Windows:
Have you installed the ADB and FastBoot? Does your device show up if you do adb devices?
If not, follow the instructions here or here.
Reconnection your device, open a console window and type: adb devices. If your device is listed in the output, Eclipse will also pick it up.
For Samsung provided firmware and drivers, check here.
If on Linux:
Follow this tutorial. You don't necessarily have to unlock the bootloader. As long as your device shows up in adb devices after adding the device identification lines in udev, followed by a udev restart with sudo service udev restart, all should be good.
Here is another tutorial that claims to install ADB automatically on both Windows, Linux and Mac. I haven't tried it myself. So it might be a good idea to peep inside the Knives-&-Forks scripts before executing them.
Make sure the USB driver is installed. Instructions can be found here.
You need to install the Galaxy Nexus driver from Samsung
Galaxy Nexus USB Driver
I have tried downloading the Samsung specific drivers. It installs the modem, not sure if the adb bridge got installed. I don't see it in the device manager. I have installed kies 2.0, I have tried connecting USB via MASS storage, via Kies, and under no circumstances so far will ADB detect the device when running adb devices command. I got lots of suggestions to use Kies, I tried this. Don't see any real relationship between Kies and ADB which is a debug bridge. I simply have no clue what ADB is doing when I type adb devices. How does it look for devices, where does it check, where can i register my device with ADB?
Apparently sometimes you need to uninstall and reinstall the driver multiple times before it works (http://androidforums.com/captivate-all-things-root/136373-adb-shell-error-device-not-found.html). Also, make sure that USB debugging is turned in your application settings.
make sure you are using the correct drivers (32 bit or 64 bit). when you connect your phone in debug mode check device manager. I would bet you have an error in there. Try and delete the error and rescan for changes.