I am new to Android Studio (2.2.3) and after installation it. I am getting this error of NDK Not Configured.
Although it does say to get it done via SDK Manager however when I go to SDK Manager the SDK Tools tab does not respond or operate.
Can anyone help me on it?
SDK manager
There shouldn't a space in the android sdk location, I had the same problem, a space in the pc name as I had a space in "usama" and "azam".
Be sure that you don't have a space in it.
Related
This question already has answers here:
Error:Unable to locate adb within SDK in Android Studio
(31 answers)
Closed 4 years ago.
I have been trying to test my app on real device. I keep receiving error message that "unable to locate adb". I have the USB driver for my phone installed. Thank you for the help. The snap shot is shown below.
on your android studio at the top right corner beside the search icon you can find the SDK Manager.
view android SDK location (this will show you your sdk path)
navigate to file explorer on your system, and locate the file path, this should be found something like
Windows=> c://Users/johndoe/AppData/local/android (you can now see the sdk.)
Mac=>/Users/johndoe/Library/Android/sdk
check the platform tools folder and see if you would see anything like adb.exe (it should be missing probably because it was corrupted and your antivirus or windows defender has quarantined it)
close Android Studio, open the Task Manager and finish the ADB.exe process if it's running and then delete the platform tools folder
go back to android studio and from where you left off navigate to sdk tools (this should be right under android sdk location)
uncheck android sdk platform-tools and select ok. (this will uninstall the platform tools from your ide) wait till it is done and then your gradle will sync.
after sync is complete, go back and check the box of android sdk platform-tools (this will install a fresh one with new adb.exe) wait till it is done and sync project and then you are good to go.
If you are still having problems, you may need to set the Project SDK.
I hope this saves someone some hours of pain.
if using avast go for virus chest,will find adb,restore it by clicking right button..thats all,perfectly works
open Studio settings-->System settings --> Android SDK --> select SDK tool tab -->> select "Android SDK platform tool" and install
(I am using Android Studio 3.0.1)
I downloaded "SDK Platform-Tools" from
https://developer.android.com/studio/releases/platform-tools
Copied 'adb.exe' to C:\Users\user\AppData\Local\Android\Sdk\platform-tools.
Then I got no errors when running the app.
I also added C:\Users\user\AppData\Local\Android\Sdk\platform-tools\adb.exe to the exception list of my anti-virus tool
I use android studio in Windows 7 and i have AVG for antivirus. The first time you launch adb, AVG prompts you to add avg.exe in antivirus vault. If you accept, then you android studio dont have access to run adb.exe. So open
avg >> options >> Virus Vault >> Restore (select the adb file)
In Android Studio, Click on 'Tools' on the top tab bar of android studio
Tools >> Android >> SDK Manager >> Launch Standalone Sdk manager
there you can clearly see which platform tool is missing , then just install that and your adb will start working properly.In Image You Can see every thing
Due to some problem my adb.exe, was lost. My space of work suffered an electrical energy interruption, after that, I could not run or compile android programs.
Adb.exe is a file which should be located in your [android directory]/sdk/platform-tools. In my case, the file dissapeared, however the platform-tools was ther. My solution was as follows:
I changed the name directory of [android directory]/sdk/platform-tools towards platform-tools_OLD, in order to hide it for android studio without erase it.
In [android directory]/sdk there is a file SDK Manager.exe, ... I launched it.
A window of "Android SDK Manager" is shown, then, in the Tools folder I chose "Android SDK Platform Tools" and then, Install packages.
Enter to Android Studio
This was well for me
Else this will helps you
The ADB is now located in the Android SDK platform-tools.
Check your [sdk directory]/platform-tools directory and if it does not exist, then open the SDK manager in the Android Studio (a button somewhere in the top menu, android logo with a down arrow), switch to SDK tools tab and and select/install the Android SDK Platform-tools.
Alternatively, you can try the standalone SDK Manager: Open the SDK manager and you should see a "Launch Standalone SDK manager" link somewhere at the bottom of the settings window. Click and open the standalone SDK manager, then install/update the
"Tools > Android SDK platform tools".
If the above does not solve the problem, try reinstalling the tools: open the "Standalone SDK manager" and uninstall the Android SDK platform-tools, delete the [your sdk directory]/platform-tools directory completely and install it again using the SDK manager.
Hope this helps!
I had the same problem, and I solved it by doing:
(You should be connected to the internet)
click the logo of the SDK Manager
click Launch StandAlone SDK Manager (wait a moment)
if the dialog of the SDK manager shows, you click cexbox [Tools] and Install all packages
if the download is finished, you restart android studio and boot again..
After that, it should work.
Got it to work go to the local.properties file under your build.gradle files to find out the PATH to your SDK, from the SDK location go into the platform-tools folder and look and see if you have adb.exe. If not go to http://adbshell.com/downloads and download ADB KITS. Copy the zip folder's contents into the platform-tools folder and re-make your project.
I didn't need to update the PATH in the Extended Controls Settings section on the emulator, I left Use detected ADB location settings on. Hope this makes this faster for you !
I fixed this issue by deleting and inserting new platform-tools folder inside android sdk folder.
But it is caused by my Avast anti virus software. Where I can found my adb.exe in Avast chest. You can also solve by restoring it from Avast chest.
If you are using Anti-Virus, you can first check virus chest and restore from there. Otherwise, just go to your SDK Manager and install Android SDK Tools.
Check your [sdk directory]/platform-tools directory and if it does not exist, then open the SDK manager in the Android Studio (a button somewhere in the top menu, android logo with a down arrow), switch to SDK tools tab and and select/install the Android SDK Platform-tools.
Alternatively, you can try the standalone SDK Manager: Open the SDK manager and you should see a "Launch Standalone SDK manager" link somewhere at the bottom of the settings window. Click and open the standalone SDK manager, then install/update the
"Tools > Android SDK platform tools".
If the above does not solve the problem, try reinstalling the tools: open the "Standalone SDK manager" and uninstall the Android SDK platform-tools, delete the [your sdk directory]/platform-tools directory completely and install it again using the SDK manager.
Hope this helps!
A young friend of mine would like to push a game created using www.buildbox.com to his Samsung Android Tablet. He is using Windows 10 and Android Studio 3.6.1.
But the Device Drop Down is greyed out and for some reason the AVD Manager, the SDK Manager and the Connection Assistant are missing from this tools menu.
On my Android Studio 3.4 I can still see the Connection Assistant
I checked the Release notes but could not find anything.
https://developer.android.com/studio/releases
I checked that Windows can see the tablet as a USB device and the friend told me that developer mode is enabled.
Any ideas what is going on ?
So I got a chance to look further into the problem.
It turned out, that the problem seems to be with Buildbox not generating a proper Android project. In particular the generated project is missing a proper module and a proper app configuration. Once I added those the missing connection tool reappeared.
However I still got an error.
A few hours ago, my Android studio was working very fine. I could write, build and run on my test device (TECNO K7).
I decided to update my Android Studio to 3.5. The whole process went well except that I cannot find my device among the list of devices any longer. I have also tried with multiple devices, I got the same outcome. When I click on the run-button, the app runs on the Pixel 2 emulator. However, I want it to run on my device.
Here's a screenshot of what my menu looks like. Note that the device (TECNO K7) is currently connected:
Is there something I am doing wrong?
UPDATE:
I tried restarting my ADB server and I go the following error:
Unable to locate ADB.
I have also tried re-installing the following tools multiple times, still the same outcome:
Android SDK tools
Android SDK Build-Tools
Android SDK Platform-Tools
PS: For reference, I use Mac OS and it is also important to remember that my Android studio was working perfectly fine before the update.
Solution:
Drivers not installed: If the Android Physical device is not a Google/Nexus product than you have to download the OEM drivers of the particular model.
HAXM not installed properly : Hardware Accelerated Execution Manager must have not installed properly on your computer. Try reinstalling it directly from the options available in your SDK.
No proper Path : Sometimes though the files are available in the local system, The Android Studio is not guided with the accurate path name to reach the file.
Hope this will be useful to you.
After spending hours on this I found that the Studio update had un-assigned an SDK for my project.
Selecting File -> Project Structure, then selecting an SDK under 'Project SDK' immediately displayed the 'allow debug on this device' dialog on my phone, then within a few seconds after accepting it, the device showed up in the device list.
Go to:
File > Invalidate caches/Restart > Invalidate and Restart
That should work.
Before going to bellow steps make sure
Your "Google USB Driver" package is installed ("Tools" -> "SDK Manager" -> Check "Google USB Driver" -> "Apply" -> "Ok").
If you are trying to access with emulator then check "Intel x86 Emulator Accelarator(HAXM installer)" is instaled. ("Tools" -> "SDK Manager" -> Check "Intel x86 Emulator Accelarator(HAXM installer)"" -> "Apply" -> "Ok")
Go to Tools.
Then go to SDK Manager.
Open SDK tools.
Uncheck "Android SDK Platform-Tools" (On my case it was checked).
press apply then ok.
Again goto Tools.
Then goto SDK Manager.
Open SDK tools.
check "Android SDK Platform-Tools"
Restart Android Studio :)
Hope this will help somebody like me.
This option is definitely not the most optimal. I eventually deduced that the problem was with my HAXM and simply re-installing this would have solved the problem. If you face, this exact problem, simple re-install the HAXM in your SDK.
I hope this helps someone out there.
I have recently updated Android Studio from 2.2.3 to 2.3. Now can't see the option "Launch Standalone SDK Manager", which is useful to check for updates, google play services, etc.
It is a deprecated feature: https://code.google.com/p/android/issues/detail?id=235625 There is an option in Android Studio to "Show Package Details".
For manual SDK and AVD management, please use Android Studio.
For command-line tools, use tools/bin/sdkmanager and tools/bin/avdmanager
See also: https://www.reddit.com/r/androiddev/comments/5x6adh/android_studio_23_is_now_available_in_the_stable/deg48lj/
Even I had this issue when I updated to Android Studio 2.3
Click on Configure on the bottom left side
Select the Check Box to Show Package Details on the bottom left side
Move between the different tabs as per your requirements.
Can't working on Android Studio 2.3.3
On Mac :
/Users/YourAccount/Library/Android/sdk/tools
click android, you'll see standalone SDK manager
On Windows :
C:\Productivity\android-sdks\tools
double click on android.bat, standalone SDK Manger will be launched (see image below).
As the standalone sdk manager has been deprecated in favor of studio builtin sdk manager, there's a workaround to get back the standalone sdk manager.
Step1.
Download command line sdk tools for your platform:
http://dl.google.com/android/installer_r24-windows.exe
http://dl.google.com/android/android-sdk_r24-windows.zip
the links refer to an old distribution intentionally (see note below).
Step2.
Copy the SDK Manager.exe, tools/android.bat and tools/lib/archquery.jar into your existing sdk to which android studio is currently being pointed.
Step3.
Run SDK Manager or tools/android.bat and you will get back your beloved standalone sdk manager while having latest android studio > 2.3
Note
if you download latest command line tools for sdk, you wont be able to find the archquery.jar which is required to run the standalone sdk utility.
In this latest version (2.3.1 and 2.3.1+), after some digging, I found a faster way to open AVD and SDK: In the welcome interface of Android Studio, after pressing CTRL+SHIFT+A, a search box will jump out, then you can input "AVD", the AVD manager will come out. To open SDK is the same way.
However, AVD does not work in the welcome interface but SDK works. If you want to use CTRL+SHIFT+A to quickly open AVD you must create a new project and open AVD in the project interface.
If you are a Xamarin user, you can install the Xamarin Android SDK Manager, available on the Visual Studio Marketplace which will give you an interface like this:
NOTE: The Xamarin SDK manager has to be accessed from visual studio, but it will (should) work on both windows and mac
You can open it from your SDK path which in my case is
C:\Users\Akshay\AppData\Local\Android\sdk
Double click on SDK Manager.exe and it will open standalone SDK manager, refer attached Screenshot.
SDK tools is not opening in SDK manager in android studio. I tried to click on SDK tools and SDK update sites and even show package details but nothing is opening.
A few things to check :
Is Android SDK Location correctly set ? (Typical value on a Linux host is /home/USERNAME/Android/Sdk)
Have you full access to this directory (both read/write) ?
Check if you have an error message in the Android Studio log file (Typically located under /home/USERNAME/.AndroidStudio2.2/system/log/idea.log
You can also try to Launch Standalone SDK Manager (link at the bottom of the window) and see what happens.