Android Studio Not Showing My Phone for Run Application:
I want to run my developed application directly on my phone but I'm unable to run this. Because It's not showing in android studio. It also not working on emulator also. I already ready Google Development Guidelines(https://developer.android.com/studio/run/oem-usb.html). But these are not working for my system.
Have you enabled Developer mode on your phone?
If you haven't done yet follow these steps:
Go to settings -> About phone.
Tap on Build number 7 times and the developer option will be on.
If you have already enabled it then:
Go to Settings and find Developer options.
Check whether it is enabled or not.
Swipe down and find USB debugging. This option should be enabled. (Also enable Wireless ADB debugging if you're running app wirelessly)
Sorry for the late answer
I am also facing this issue couple of month ago, I had checked that I had enabled the USB debugging in developer but there is an issue with the Redmi phones that along with the USB debugging you will need to do the following
Go To Settings > Additional Settings > Developer Options
Enable USB debugging
Enable Install via USB
Disable Turn on MIUI optimization
On Select USB configuration select MIDI or File transfer (this is
what solved the problem for me)
also, keep in mind to give an RSA permission
you also check the link https://developer.android.com/studio/run/device?hl=ro
I have solved my problem on my own. The problem was in Android SDK. I'm using 2 windows in my same pc so I just used android studio on my another window then it's was working perfectly so I thought i have to try with changes that windows Android/Sdk folder in other windows which one I had problem. So I just copy (C:\Users{MyUserName}\AppData\Local\Android\Sdk) in getting the problem window and try again the android studio & Wawu... It's starting working. I hope it's will be helpful for you also.
I am absolutly new in Android development (I am a Java EE developer) and this is the first time that I use Android Studio.
So I am finding some difficulties to run my HelloWorld application on my HTC One phone.
I have installed the driver of my phone on my Windows 8.1 system (it should be ok because I can correctly see my phone into the Windows Device Manager).
So I open my app into Android Studio and then click on the start button and then I can choose perform the application on my phone but then I obtain the following error message:
The selected device is incompatible
Here a screenshot of the problem:
Why? What is the problem? How is it possibile that my Htc One is incompatible with Android Studio? How can I fix this issue?
Another problem is that if I chose Launch Emulator instead my phisical phone I have not a virtual device. Is is something that have I to instal separatly or what?
Sometimes reasons may be your device is not recognized by Android Studio.
For this to happen do the following:
Settings -> Developer Options -> Revoke USB debugging authorizations.
Select OK and disconnect your phone. Reconnect it, run the app and you should get a popup on your phone asking for authorization with title "Allow this Device..." . Tick the checkbox for future prefrence. and Select Ok.
You have created the app with min SDK version 15 (as mentioned in the snapshot) but your device is working on a lower version of android. You can change the min SDK version from project properties or create a new application project with lower or equal version of android SDK than the android version installed on your device.
The version of SDK, you select, will work on any device having same or higher version of android OS installed.
Gingerbread (version 10) will work on ~90% of the devices.
It seems the minSdkVersion defined in the grade file of your project is higher than the api version of your phone. So you should change minSdkVersion.You can only start a virtual device, if you have previously downloaded a system image and configured the device with AVD Manager.
I was using my phone earlier today for testing apps. I plugged it in later today to test another and eclipse wouldn't recognize it. I looked everywhere. I'm not sure why it wont work. Im using a Samsung Galaxy S3 device. All of the drives properly installed and updated. And debuggin is on.
This is not a problem with eclipse, devices get detected by adb(Android Debug Bridge that comes with the SDK) and the underlying driver(Install Samsung Kies to get the correct driver for S3), Ensure you have the correct drivers installed. Then it will detect successfully. Ensure USB debugging connected in Settings -> Developer Options
I have only used my phone to test for one day. And all day i had my phone connected cause i was teathering. I turned my teather back on and viola, problem solved.
Install google usb driver throu android sdk manager
I am using LG-P500. When I try to select it in the 'Android device chooser', Eclipse recognizes the phone but not the target. It says target "unknown". Because of this problem, I can't choose the phone as the Android device.
How can I get Eclipse to recognize the target?
Had the same problem with an LG phone. Rebooting it (phone) worked for me
One solution I am aware of is to just turn off and on USB Debugging on your phone. It also happens to solve a bunch of other device-not-recognized kinds of problems.
Follow these steps, if your device is recognised but the eclipse is stating it as unknown:
->open cmd
->go to the your android sdk directory --> Go to platform-tools
->adb kill-server
->adb start-server
this will definitely solve your problem :)
If you already installed USB driver and still your device showing as unknown then follow this solution. I had same problem with my MOTO G and this solution works fine for me
Check your device that
USB connected
and
USB debugging connected
or Check the following
The solution was to create a udev rule for the device. See http://developer.android.com/guide/developing/device.html#setting-up for how to setup a udev rule for your specific vendor device.
With the rule in place. Eclipse was able to launch and debug.
One simple trick works fine for me.
Disconnect device from PC
Tap revoke USB debugging authorization in phone setting
Reconnect device to PC
Tap OK for RSA authorization
The reason that my SCH-I535 device was not being targeted... is because I had the device plugged into a USB 3.0 port.
Once I plugged it into a 2.0, everything began to work properly.
Also try this, On your phone:
Go to "USB computer connection"
Select Connect as "Media Device (MTP)"
I tried these suggestions, but unfortunately, nothing worked.
What worked for me was:
close Eclipse
end the adb.exe process (using Windows Task Manager)
restart Eclipse (the device was now recognized in Android Device Chooser)
Go to Settings -> Storage -> Click on Top right menu button -> USB computer connection-> Check Media device(MTP) is enable or not
Do you have a driver for your phone installed on your computer, eclipse doesn't automaticly come with drivers for phones.
My problem solved by changing the cable. Nothing else worked for me.
For this problem I had tried disconnecting/reconnecting the USB cable, toggling on/off the USB debugging and relaunching Eclipse with no effect. Trying a different android device showed exactly the same eclipse errors, with two entries marked 'offline' and after disconnecting the USB connection it still showed one entry while nothing was connected.
My problem was solved by rebooting my computer and starting again. Probably ending the adb.exe programme (answer 4) would have done it too in my case.
GALAXY S5
I know this has been answered heaps of times already but if you have a Galaxy S5 then the turn off and turn on of USB debugging works to resolve this problem
When the phone is plugged in and the Eclipse window shows the "Unknown" icon...on the phone turn off USB Debugging then on again, it will then ask to allow that computer to connect, and you can say to always let it do so. Then it comes up OK.
create a udev rule for your development device.
I had this same issue, and I found this post, which fixed it for me.
Just download
http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip
unzip it and replace your "C:\Program Files (x86)\Android\android-sdk\platform-tools" directory with that
Credit goes to hack_on
Here is his post that helped me:
https://stackoverflow.com/a/15000565/342497
Thanks! :-)
If you cannot select the ok button when choosing a device it probably means you cant do things like adb logcat either in my experience.
I usually kill adb from Task Manager and it starts working. I noticed adb kill-server only sometimes works, and that there are often multiple processes called adb running... not sure if this is a bug or by design.
step 1 : rigth click on the project => properties => android => select api level that your device suport.
step 2 : restart your phone
work for me ...
Had the exact same problem. Working fine for over two years then all of a sudden this error pops up. The fix for me was running the SDK Manager.exe located here on my machine: C:\Program Files (x86)\Android\android-sdk
Turns out I did not have the ability to run on the device with Android operating system 4.2.2, only 4.0.2. After the SDK updated recognition worked perfectly. Turns out my phones operating system was updated and I forgot to update the SDK.
Had the same problem. Turns out I had changed my USB connection mode from MTP to MSC. Changing it back to MTP solved the problem. Thanx.
I used to debug w/o problems in my HTC One X, I broke the screen and until they repair it I managed to get an HTC One (M7 I think it's called internally).
I was unable to debug with this same problem, what actually happened is that besides having to follow a weird procedure to make Debug options appear (press 7 times in the firmware version in "About" menu) the phone was showing a message asking me to verify that the computer trying to debug on it was authorized.
I had not seen this behavior before in any the the phones I have used, not sure if this is a new functionality or simply it was not enforced on the other ones.
It is because that you didn't allow your phone to be debug by this computer.
Lock your screen, unplug and plug it then unlock screen click allow in the dialog.
KITKAT 4.4.2+ users, TRY to switch from ART to DALVIK or from DALVIK to ART. :) solved mine.
I tried different drivers, turning USB debugging on/off, rebuilding program with lower level API, killing ABD and restarting. Then I saw post on here regarding cable swap. Changed USB cable to Samsung USB cable and worked immediately.
you need to authorize the device to that computer. I was connecting the phone to my centos VM and kept getting this. I had to kill the adb server and then run it as root user. then you will get the prompt on the phone to authorize machine.
For me it worked by disabling and enabling the USB-Debugging option while ADB is running. Thanks for all the suggestions.
I had the same problem, restarting the PC worked for me.
(Debugging was already on, USB cable plugged in, fresh restart)
SOLUTION:
Switched USB connection from Media Device (MTP) to Camera (PTP).
When I did this it the PC installed device drivers, then phone gave me my computer's fingerprint and had a dialog concerning allow device to use USB Debugging. Accept. Device shows up in eclipse. All good.
(On Samsung Note II API 19)
Note: it's good habit to always try toggling the USB mode. I don't think it's the act of designating Camera (PTP), but the dialogs that are generated when doing so. Also, I had my phone replaced: I remember seeing this dialog before but not on this phone. Maybe there's an option somewhere to enable it per device?
I had the same problem. Turns out my device was prompting a dialog asking me whether I should allow connecting to my laptop or not. After clicking yes this problem went away.
The problem for me turned out to be insufficient rights of adb server.
I run Android Studio through remote desktop (used laptop to connect to a local, more powerful computer). Apparently i didn't have all the privileges when running through remote desktop.
After stopping adb server and restarting it with root privileges solved the problem.
sudo ./adb kill-server
sudo ./adb root
Edit:
Turns out i had to do this just the first time. Since the first time i don't have to do this anymore.
I recently bought a Galaxy Nexus and flashed 4.0.4 onto it (I don't know if this affected the problem). My application used to, but no longer, is displayed in the Android Market on the device when searching for it or even when navigating to My Apps.
It does display in my launcher correctly once installed and runs perfectly, however it will not show up in the Android Market. I am very confused as to why this is (comes up on my Nexus One, Droid X, Galaxy S etc.) and my min SDK version is 7.
In my Manifest
uses-sdk android:minSdkVersion="7"
Any help would be greatly appreciated!
Turn off the copy write protection and it will show up in a few hours..It's better to implement you're own authentication system.
Does this happen only on your device or on other GNs as well? You can use the developer console to find out what devices the app won't show up on. Find the 'Supported devices' section, then click 'Show devices' and do a search for 'Samsung'. If it is filtered, it might be due to the permissions/features you are using in the manifest. Check those and and requried=false as necessary (if possible).