I've installed eclipse (JUNO version), SDK, ADT (20.0.3) and configured them through the Developer.android.com. After that I made a virtual device on eclipse (Android 4.1 API level 16) as well, but when I run the "Hello World" application in eclipse, the emulator is running with out error but the app is not running on the emulator.
There is also the problem with real device. I use Windows 7/64 bit and HTC incredible S phone. When I connect the device to my pc, windows detect it, but eclipse does not detect it. (The USB Debugging is enable on device and USB driver is updated on windows).
I tried different solutions like reinstalling eclpise, SDK and ADT, removing ADV and creating the new one,... but the problem did not solve.
Did u located your android sdk? If not,locate the sdk as follows:
open Eclipse->Windows->preferences->Android->Select your android sdk folder.
then please try to run you program. Tell me the status after that.
Related
I'm trying to develop an Android app using the Eclipse IDE and I want to debug using my physical Moto X (2nd gen, Android version 4.4.4). I thought it was as easy as turning on USB debugging on the phone, plugging it into my macbook (OS X Yosemite 10.10.1), running my Android application from eclipse, and selecting my device.
However when the device chooser dialogue comes up, it doesn't show my moto x in there. It shows all the Android Virtual Devices I have set up, but nothing under running Android device. What's particularly mind-blowing about this to me is that I can clearly see my device in the eclipse device view as online. I can also see it by going into the sdk folder and running adb devices. The only time to doesn't show up is when I try to run the application and select what to run it on.
Has anyone ever encountered this problem before? Is there something here I'm missing? I have the latest Android SDK all up to date, as well as my Eclipse (I'm running Juno if that matters). My Min SDK version is 11, and the Target is 21, so my device should be in that range. I have also tried restarting the device, eclipse, and even my macbook with no luck.
If you are on Yosemite, try to drag corner of one of the column headers in the device chooser box and it will show the device. This is a hilariously stupid bug on eclipse for Mac. Check this answer.
There might be something wrong with eclipse. Sometimes the only solution to fix eclipse is to redownload a fresh copy of ADT from website.
You say that you can see your device when you run adb devices.
In this case use eclipse to build your project then use adb to install the apk on the phone:
adb install /path/to/projectRoot/bin/myBuild.apk
Better yet I would take this as a sign to forget Eclipse and move to Android Studio. Version 1.0 was released today (no more beta).
I am having trouble running an app I am developing in Android Studio on my Nexus 7. I have successfully gotten this to work before using the same tablet and computer (running Windows 8), but since having my laptop repaired and everything wiped I'm convinced something with my dev environment is messed up.
When I go to run the project, there are no available devices, so it is not recognizing my Nexus 7 anymore.
Things I have tried
making sure my computer recognizes the device and that I have the Nexus 7 driver installed from ASUS
going to the SDK manager and ensuring I have the Google USB driver installed
closing Android Studio and re opening it, restarting my computer, restarting my Nexus 7
killing adb.exe from the task manager
ensuring I have USB debugging enabled and toggling that on and off
switching from MTP to PTP and back again (currently connected as MTP, not sure if that is correct)
Any help would be greatly appreciated. This is very frustrating and I would like to just get back to developing again.
Update- I just noticed that when I go to developer options, "Wait for debugger" (near where you toggle USB Debugging) is grayed out. I think this has something to do with it but I'm not sure how to enable it.
I got it!
This was at least the issue in my case, I hope maybe this will help someone someday, apparently I had not installed the adb driver properly:
Search for Device Manager from the search bar on the start screen
Open Device manager, click on your Android device
Select"Update Driver Software"
BOOM. Now Android Studio recognizes the device.
I know this may not be the solution for everyone, but its worth a shot if you are having trouble testing apps on your device.
Between upgrading my second-gen Nexus 7 to Android 5.0.x and Android Studio leaving beta I lost the ability to debug on my tablet.
To get this working again I used a combination of the above advice.
I grabbed a copy of the USB Driver from Asus, but updating the Device in Device Manager and pointing to the unzipped files wasn't enough.
The next step was to point Device Manager to the Android Studio sdk directory (on a 64-bit Windows 8 install that was C:\Program Files (x86)\Android\sdk - beta versions of Android Studio - or %localappdata%\Android\sdk - switched to in 1.x) and then things worked just fine again.
Another possible reason that you may not be able to connect is:
Don't forget to enable debugging mode in Android setting.
I have had the same problem, although just getting started with my Nexus 5 and windows 7. I installed google usb driver package using SDK manager first, computer recognized phone but studio could not find it. Went in to manually update driver for phone but update driver couldnt find it, downloaded driver separately and pointed it to directory path, driver installed then studio found it and ran fine.
My android device is a cutePad TX-A7108, with Android OS 4.2.2.
I have enabled USB Debugging on it, but when I plug it to my laptop via a USB cable, and then run my Android project on Eclipse, the Device Window doesn't show it on the Device List.
I have a Samsung Galaxy running Android 2.3. When I plug it to my laptop and run the same Android project, it works as it normally should.
I am developing Android apps on Windows 8 OS. My android SDK has been setup with most of the used APIs(10, 16, 18, 19), tools and supported libraries.
Please help me out with this issue.
Right Click on "My Computer" choose "properties".
Go into Device Manager there you can find your device(cutePad) right click on that and choose update device drive let windows search online if windows could find the updates try to locate on your own
Hope it Helps..!!
you should install device drivers for that tab, then try running project directly from the eclipse.
Recently I got my first Android smartphone - ZTE Blade III and want to start learning it. I've downloaded Android Studio for Windows, created basic "Hello World" app, tried to run it on the phone and here I encountered a problem - Adroid Studio doesn't see my device.
http://i.imgur.com/mpSciXz.jpg
I followed this guide. I installed ZTE USB driver, enabled USB debugging on my phone and set targetSdkVersion to match Android version of device (I have Android 4.0.4, so I set it to 15), but Android Studio still doesn't see the device.
Any suggestions?
Have you opened up the: /path/to/android/sdk/tools/android Android SDK download tool and installed "Google USB Driver" under the "Extras" folder? (Required for Windows. Screenshot from Linux computer)
I found the solution.
I had to enable Windows Update and set Windows auto driver download function to always on, like in this guide: http://zteblade3.com/zte-blade-3-install-a-custom-jelly-bean-rom-ics-rom-from-scratch/install-the-usb-drivers/
I have a Sony Ericsson Xperia Mini device which I use to test android app development. Earlier it is working fine if I run any project from Eclipse as Android App. I can select the device and run the program in that device. But after formatting I reinstall all the systems(e.g. eclipse, ADT plug in, driver of the device), but when I try to run the program, it is telling 'No compatible targets found', although I have connected the device properly. Actually the eclipse-ADT plug in system not all getting the device. What may cause this problem?
Try to re-install your mobile's drivers..
It is due to setting in the device...non-market app and USB debugging should be allowed.