I am just starting to learn on Android development. I use Ubuntu 11.10 and Eclipse. I have installed the needed plugins from android development, and I have also write yet some examples that compiles and run fine on the emulator.
But somethings as multitouch cannot be tested on the emulator, so I want to test them on my real Samsung Galaxy S2 device. The problem is that I have tried everything I have found on the web on this, but still have not been able to use it.
When I run ./adb devices, it does show none, although the device IS attached.
$ lsusb
...
Bus 001 Device 012: ID 04e8:6860 Samsung Electronics Co., Ltd
$ ./adb devices
List of devices attached
I have modified /etc/udev/rules.d/51-android.rules many times in different ways following instructions on the web, but none of them make a difference. Currently I have this line in it:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}="6860", MODE="0666", GROUP="plugdev"
Of course I tried restarting udev and adb services, even rebooting the whole system, but it did not work neither.
Any hint?
Thanks a lot in advance,
If you have plugged in your Samsung Galaxy phone and you are facing usb debugging not accessible problem, disconnect the phone and plug it back in. 2. Select "PTM/MTP" as the USB connection mode After you connect the phone to PC through a USB cable, choose default mode as an Internet connection.
Running the Android Debug Monitor tool (monitor.bat) has been known to kickstart Eclipse into recognizing a new device. Connect your device, locate monitor.bat (android-sdks/tools/monitor.bat) and double-click to open. This will open the Android Debug Monitor, a stand-alone debugging tool that lists connected devices.
After you fix the problem of cant enable usb debugging broken screen, you can recover deleted or lost files on your Samsung Galaxy or any other android phone with Android Data Recovery software. Select file types to scan, type of recovery and scan.
Some phones have a ‘charge only’ mode that can prevent Eclipse from recognizing the device. 3. Make sure you don’t have an Android Virtual Device running in the background. 4. Could there be a problem with the USB cable? If you have a spare cable to hand, plug it in to rule out a fault with the cable itself. 5.
Enable USB Debugging on the device from the Settings -> Applications -> Development
Try Samsung kies, it delivers suitable ADB driver: http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
With the right adb driver (from kies or elsewhere) it should work flawlessly
EDIT: on linux: http://developer.android.com/tools/device.html
If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux: Log in as root and create this file: /etc/udev/rules.d/51-android.rules. Use this format to add each vendor to the file: SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node. Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules. Now execute: chmod a+r /etc/udev/rules.d/51-android.rules
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With