Using Hardware Devices

When building a mobile application, it's important that you always test your application on a real device before releasing it to users. This page describes how to set up your development environment and Android-powered device for testing and debugging on the device. You can use any Android-powered device as an environment for running, debugging, and testing your applications. If you want a SIM-unlocked phone, then you might consider a Nexus phone. Note: When developing on a device, keep in mind that you should still use the Android emulator to test your application on configurations that are not equivalent to those of your real device. Setting up a Device for Development With an Android-powered device, you can develop and debug your Android applications just as you would on the emulator. Note: When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. USB Vendor IDs

Ubuntu No devices permission Quote: Welcome to Linux! Actually, the more you use it, you'll find that you'll pickup these bits along the way, just like this. The files are processed in order of their name so 51-xxx is mid-way through, 99-xx is at the tail end of the processing order. Also, after posting the wrong info to you earlier, I deleted the entry I posted. So, I put both lines in one file today and all is well again. I.e: SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666" SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666" and I changed my filename to 99-android.rules then ran: sudo restart udev and now I can access the phone as a non root user again, either from adb or fastboot-linux. -Rotohammer T879 Note on T-Mobile Do not quote my entire first post in a reply!

android - Detecting device for debugging (ADB) does not work