What and Where is Android Debug Bridge (ADB)?Īndroid Debug Bridge (ADB) is a very powerful command-line utility you can use to communicate with Android-enabled devices or emulators. Topics include what ADB is, where to find it, how to use it to interact with connected devices and emulators, and point out the Android Studio integration.

We will cover the most commonly used options in this tutorial and touch on some advanced examples. If you have not started using it, please check out the introductory tutorial, “ Using Android Studio.” Like others, ADB is also integrated into Google’s Android Studio IDE. ** (If your vendor isn't Google Inc., also replace the vendor id with the one before the colon in lsusb).As we are doing Android development with a variety of tools, Android Debug Bridge, or ADB, is a command-line utility among the most important ones. This can be solved by creating a new udev rule - I used /etc/udev/rules.d/les- to add the device to the group plugdev, which adb already assumes you to be a member of (you shoukd be, check using id) SUBSYSTEM='usb', ATTR='4ee7' with your own product id that you found out in step one. This which means that the device file will be owned by the user root and the group root, which is why adb can access it as root but not as your standard user. Likely you will see something like crw-rw-r- 1 root root 189, 5 Sep 8 21:47 /dev/bus/usb/001/006 Point of interest in this case: Bus 001 Device 006: ID 18d1:4ee7 Google Inc.Ĭheck out the corresponding device file $ ls -l /dev/bus/usb/001/006 I too had this problem & came across a relatively simple solution.īus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 8087:0a2b Intel Corp.īus 001 Device 002: ID 05c8:03a2 Cheng Uei Precision Industry Co., Ltd (Foxlink)īus 001 Device 006: ID 18d1:4ee7 Google Inc.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Very likely udev is incorrectly adding your device.

Android studio adb not working