Related
Android Studio produces the following error:
The ADB binary at
C:\Users\username\AppData\Local\Android\Sdk\platform-tools\adb.exe is
obsolete and has serious performance problems with the Android
Emulator. Please update to a newer version to get significantly faster
app / file transfer
I tried to check at: SDK Manager -> SDK Tools -> Android SDK Build-Tools (link to that answer). But the last update has been installed already.
P.S. I know, such a question already exists (link to that question), but there I can't write a solution that helped me, because I don't have enough reputation points. So, I'll write here the solution, maybe it will help someone...
The Android Studio should recheck SDK (it should help, at least it helped me)
Go to:
SDK Manager -> Android SDK Location: (Edit) -> Next -> Next -> Finish
SDK Location doesn't have to be changed.
Open SDK Manager
Click on --> SDK Tools.
Check--> Show Package Details. (Look at the bottom right corner)
Under--> SDK Build-Tools, scroll to the bottom and check the last item. (when I checked it was 19.1.0)
Click on--> Apply.
A dialog box appears just click OK.
It begins to install.
After installation gets completed just click--> Finish.
in short, I also have that problem. I accidentally solved by switching the graphic card from Integrated to Dedicated Graphics Card on my laptop setting. That is it, no more error pop up.
in long, I was trying to the get the emulator run faster and less lag. I am using Android Studio 4 with Win 10 on lenovo notebook with Intel and AMD Graphics Card. I accidentally found this switching GPU method and it's work for me. I don't know why or how it is related to adb.exe. I tried to switch back and forth GPU several time to confirm it already.
Give it a try and kindly let me and other knows
Thank you
Fiddling with the SDK manager did not work for me.
Changing the emulator device Graphics from Automatic to Hardware fixed this issue for me.
This solved the issue for me
Using Android studio 4.2+
For Windows
go to File->Settings->Tools->Emulator->Tick 'Launch in a tool window' (option)
Apply
For Mac OS
Preferences->Tools->Emulator->Tick 'Launch in a tool window' (option)
Apply
Check Image
after I update Android Studio from 2.3 to 3.0 version. I can not find AVD Manager in Tools/Android/AVD Manager.
I just did a fresh install and had the same issue. Solved by:
Click "Install missing platforms(s)..." in the highlighted error:
Then after the download/install, click "Intall Build Tools...":
Then after the download/install, you will see Android under Tools menu
If you have never used Android Studio Before, and do not have a Project
..Opening the AVD Manager is even trickier!!
For example, if you are installing it to use an emulator for a create-react-native-app project., but aren't otherwise using Android Studio to write or manage your app.
Here is how you can gain access to the AVD Manager.
AVD Manager is required to set-up your emulators.
Android Studio Documentation does NOT tell you how to gain access to AVD Manager. It starts at Open the AVD Manager!
I Just Need the emulator (and manager).
But I did not even have the window the OP refers to.
Nothing in the Configure menu, not Preferences (even Preferences -> Tools) gave me access to AVD Manager.
So in my case it was even more confusing to have No Direct Access AVD Manager !
Nor did I have an android folder in my create-react-native-app app, so hamdi's answer above did not work for me.
All I had was a new folder/git repo from:
create-react-native-app
My Solution
On the Android Studio Startup Screen, I choose:
Import Android Code Sample
Then choose any sample. (I choose the first example listed).
Then (after a bunch of downloading/building..), then brought up the window the OP refers to.
I then had to update gradle, as mentioned by user1449542's post above.
At that point, Muhammad Hannan's answer above was helpful !!!
I clicked the icon from the bottom image in his post -- vioa!
( Alternatively from the menu bar choose: Tools -> AVD Manager )
Better Solution:
I have since realized that the Startup Screen Option:
Start a new Android Studio Project
also works and is even quicker (less to download/build), and might not even need gradle file updates (mentioned by another post) that I had to do when I downloaded a sample project.
Just use the default settings to create a dummy project in the default location, and choose
Add No Activity.
Android Studio will "build" this dummy project, and set it up, then open the Window you need to access said icon, and/or menu bar.
In the future, this dummy project will appear on the left of Android Studio's Startup Screen.
Just click on that dummy project to re-open the window you need to access AVD Manager.
Then, as before, click that icon (or from the menu bar choose: Tools -> AVD Manager) to create/edit AVD emulators.
If you're using React Native (create react native app), you can start an emulator from the command line, once you have created an AVD emulator, and probably won't need to open Android Studio itself. (see notes below).
Be sure to start the emulator before choosing a (from the terminal window that's running your app via yarn start).
Additional Notes for reference:
To start the emulator from the command line:
emulator -avd <avd_emulator_name>
To list what emulators have been configured:
emulator -list-avds
AVD_Nexus_6P_API_23
AVD_Pixel_2_XL_API_27
AVD_Pixel_XL_API_25
So, for example, I can do this:
emulator -avd AVD_Pixel_2_XL_API_27
Additional Information
I also had to add the following lines to my .bash_profile
export JAVA_HOME=`/usr/libexec/java_home -v 10`
Note: the value between the back-ticks is what the JAVA install from my terminal replied. If you type that part into terminal by itself, it spits out the location Java was installed. If you have an different version of Java installed, just replace 10 with your version.
I then got the following path from:
- Android Studio Startup Screen -> Configure -> SDK ManagerPreferences
- Appearance & Behavior -> System Settings -> Android SDK
- Android SDK Location: /Users/sherylhohman/Library/Android/sdk
and used it as the value for adding the following line
export ANDROID_HOME=/Users/sherylhohman/Library/Android/sdk
Though I chose to write it as the following instead:
export ANDROID_HOME=$HOME/Library/Android/sdk
Finally I added:
PATH=$PATH:$ANDROID_HOME/emulator
PATH=$PATH:$ANDROID_HOME/tools
PATH=$PATH:$ANDROID_HOME/platform-tools
PATH=$PATH:$ANDROID_HOME/tools/bin
PATH=$PATH:$ANDROID_HOME/platform-tools/adb
export PATH
I may not have needed the ...adb or 1 or more of the last PATH entries.
This was a cumulation of many internet searches, many conflicting solutions. The major missing key was accessing AVD Manager (OP's question), which finally solved the problem. This just happens to be the items I had already added to my .batch_profile along the way trying to get the android emulator working inside my create-react-native-app App!.
I found this just under the toolbar in Android Studio (v3.2):
Go to the "Event Log" tab in the bottom right corner.
There will probably be some error messages. It will provide information and links to resolve the problem. Then the buttons will not be greyed out anymore.
I'm using Android Studio 3.0 on Ubuntu I have AVD under Tools > Android > AVD . And also on the right upper corner of the screen.
EDIT :
Go to Settings and search for AVD.
If you encountered the problem when using React Native, you are probably trying to include the whole project in Android Studio. You only have to include the android folder from the React Native project. After this process, Gradle will be synchronized and AVD Manager will come back.
I had the same problem.
If you get this message: "Frameworks detected: Android framework is detected in the project" then click on it and add Android.
After that, the icons should be enabled now.
you can find SDK manager,AVD manager TOP right side on android studio version more than 3.2.0.
and if you want to run via commmand promat you can go to
cd Library/Android/sdk/tools/bin
./avdmanager list
I had the same issue in Windows 10 and saw this solution in another post ... It worked for me.
Set-up the System Environmental Variables ANDROID_HOME and ANDROID_SDK_ROOT
To do this ...
Click the windows key and start typing System.
Select it when it pops up in the menu.
Click advanced system settings
Select the advanced tab
Click Environmental Variables at the bottom
Under system variables, click new
Enter the variable name
For value, enter the the path to the Android SDK, which will most likely be: C:\Users[username]\AppData\Local\Android\Sdk
Use the same path for both variables
In Andriod Studio 3.5 its here
Following the event log to install resolves the issue
Hit ctrl+shift+a and search avd and click on it
I was not able to find AVD manager in android studio easily for Android studio version 3.1.2.In order to launch AVD manager, i had to create a sample project and then launch it from there.
I have documented all my steps here, in case any one wants to get benifitted.
How to launch AVD manager on Android Studio 3.1.2
I'm very new to Android development and have never used Android Studio before. I set it up, got my app working on my phone and left it alone for a few weeks. Upon returning, I could not find the Android Studio executable on my computer, so I reinstalled it and restarted on the same project.
Not sure if this has to do with the AVD Manager button being grayed out. Things I have tried:
Making sure my SDK path is correct
Running Android Studio as administrator
Launching the AVD Manager executable from windows. I can create a virtual device but doesn't affect disabled AVD Manager button when restarting Android Studio.
Installing Intel X86 Atom System Image and Google APIs in SDK Manager, under API 24.Everything under API 25 is installed.
Any help is appreciated. Thank you!
This generally happens when Android Studio is not able identify the android sdk installation in the machine. This could happen if Android Studio is launched in non-Administrator mode.
Just close and relaunch Android Studio in administrator mode. You will see a saying "android framework is identified" Click on the configure link on that notification. The AndroidStudio will start configuring the android sdk. After some time the buttons would be visible and enabled.
If you tried running the Android Studio in administrator mode and it still do not work for you try the following way.
Delete the .idea folder in the project
Re open the project from going to File->Open Recent->
Then you will be asked to convert the project
Click convert
For anyone seeing this problem following the React Native tutorial make sure to click the "Configure" button in the Event Log next to the log text that reads "Frameworks detected: Android framework is detected in the project"
This action seems to be what configures the project to be an Android project.
I'v solved this issue by updating gradle.
It is simple
The only thing that worked for me was that I clicked in Androidstudio in the top right on SDK Managar.
And there under android sdk it was so that there was no path entered. and it was also so that NO Check box was checked below.
So I had to first click in the top right on Edit thereby was written to me the path pure.
After that I had to select a chack box below it no matter whiche and sometimes it must then just install something. When it has finished installing click OK. It may be that you then have to close and open android studio again.
I was having this issue on a new machine running MacOS High Sierra.
After installing Android Studio and the most recent SDK/
SDK Tools, I was unable to create any AVD from Android Studio (button greyed out, no option under Tools) or run the AVD Manager any other way.
I tried the same things the OP had done, then noticed I was getting the following error: Gradle sync failed: Failed to find Build Tools revision 26.0.2
From the Event Log I followed a link to download the Build tools and now it works!
If you are working on Flutter, Follow the steps:
Open Settings in Android Studio (CTRLALTS)
Search Flutter
Check may path of Flutter SDK is not available.
Set the path and press OK.
Done! Thank you
I tried the answers here, but the only solution for me was to restart my machine and it fixed itself. It happened after upgrading AS (from 4.0.2 to 4.2.2)
in android studio or intellij program:
goto tools > android > SDK manager
click on Edit (android SDK location)
click next and next
close dialog
its ok.
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
I am installing the Android SDK along with Eclipse in mac os. Whenever I try to start a new project development I get an error location of the android sdk has not been setup in the preferences
How do I resolve this problem?
Hi try this in eclipse: Window - Preferences - Android - SDK Location and setup SDK path.
I got this message after updating eclipse platform-tools and tools from the SDK Manager and then it was impossible to update the SDK path because I had an old version of ADT plugin.
Whenever you get this error message in a prompt right after eclipse loaded, you should do the following:
Go to Help - Install new software
Click on Available software sites
Delete the link http://dl-ssl.google.com/android/eclipse/
Reboot eclipse
Go to Help - Install new software
In the box "Work with" add http://dl-ssl.google.com/android/eclipse/ again
Install ADT and accept whatever that prompts.
This is how my problem with this message got solved.
I saw this error after updating the Android SDK to r17. The solution was to go to Help -> Update and get the latest version of the Android SDK to match.
I experienced this problem and fixed it by updating to the latest Android SDK Tools which in my case was 20.0.3
I am running Mac OSX Lion 10.7.4
If ever you encounter errors while updating the SDK Tools try deleting
http://dl-ssl.google.com/android/eclipse/
from the "Available Software Sites" in Eclipse, and adding it again.
If you have not installed plugin for eclipse, install it first.
If the plugin is installed, setup preferences: "Eclipse">"Preferences...", in left column choose "Android"(do not expand list, just choose root element), and first preference will be "SDK Location".
I've had the same problem on Eclipse Juno.
No "Welcome page" appeared, I could not create a project, compilation didn't work and "Graphical layout" didn't work.
I have fixed it:
Window > Preferences > General > Startup and shutdown:
Check "Android development toolkit"
Reestart Eclipse.
Of course you have to be configured this:
Window - Preferences - Android - SDK Location and setup SDK path.
Simply create this folder:
C:\Users\xxxxx\android-sdk\tools
and then from Window -> Preferences -> Android, put this path:
C:\Users\xxxxx\android-sdk
I had the same problem when I was trying to upgrade from ADT 20.0.x to ADT 23.0.x on Eclipse Indigo.
To fix the issue, I had to uninstall the ADT plugin (remove feature) from Eclipse, then reinstall the newer versions.
This maybe done by going to Help->Install New Software. Then at the bottom of the page, click What is already installed?
All what is left now is to install the newer versions as usual from help->Install New Software.
there are many things which can cause this error. For example, I
imported google api from the android SDK Manager and that is when I
got this same error. Eclipse broke down on me. I could not even create
a new android project.
To fix this, I went to help - Install New Software... - from the "work with"
drop-down box I selected http://dl-ssl.google.com/android/eclipse/ -
I then check marked "Developer Tools" and hit the Next button.
I then followed the prompts and it basically did a re-install. It took less
than 5 minutes. That resolved the error.
Now Im back up and running, and I got the lastest version of Eclipse.
i tried everything/....but only this thing worked for me:
To fix this, I went to help - Install New Software... - from the "work with" drop-down box I selected http://dl-ssl.google.com/android/eclipse/ - I then check marked "Developer Tools" and hit the Next button. I then followed the prompts and it basically did a re-install. It took less than 5 minutes. That resolved the error.
Now Im back up and running, and I got the lastest version of Eclipse.
Thanks a lot Nadir
Hope this helps:
Step 1.) Go to https://www.eclipse.org/downloads/index-developer.php?release=kepler and download appropriate Eclipse version.
Step 2.) Extract downloaded zip file in appropriate location. In this tutorial, I have downloaded and installed it under program files.
Step 3.) Right click on eclipse.exe file and send shortcut to desktop.
Step 4.) Double click on eclipse shortcut from desktop and select appropriate location to create your workspace.
Step 5.) Navigate to Window > Preferences. This should open Preferences window.
Step 6.) On the left hand side page expend “Java” and click on “Installed JREs”
Step 7.) Click Add. It will open “Add JRE” dialog. Select “Standard VM” and click Next.
Step 8.) For “JRE home” select “Direcotry…”. This will open “Browse for folder” dialog. Select the location where your JDK is installed. NOTE: MAKE SURE THAT ITS x64 AS WELL, AS WE ARE USING 64-BIT VERSION OF ECLIPSE.
Step 9.) If you have selected proper location, it will show JDK version in JRE name and it will display “JRE system libraries”.
Step 10.) Click finish. Now your JDK is properly pointed as “Installed JREs”.
Step 11.) Select checkbox unchecked before name of your JDK name.
Click ok and you’re done. You are now using JDK as “Installed JREs”
Read complete procedure at below location.
https://softwaretestingboard.com/qna/4/how-do-i-map-android-sdk-after-eclipse-plugin-is-installed#axzz4wM3UEZtq
You can find the Android SDK path by running the SDK Manager. Once the window comes up the path is displayed at the top. For me it was hiding in AddData (Windows). You can then set the path in Eclipse by going Window > Preferences > Android > and set SDK Location.
If you already installed in your eclipse you can solve this problem below,
Go to Windows -> Install New Software and find your android plugin address
Check all lists and re-install your android plugin for eclipse
I solved it like this
It is very irritating problem... i found one simple solution...that is
eclipse->help->Install new software
now u see "work with"field...below this fields u observe on link called
"available software sites"...click on this link..then open one window...here u find out some location address..... delete wrong locations and then add perfect location to install/update location. then click on ok button... then ur problem is solved....
This problem seems to arise from new versions of android sdk the solution that worked fine for me was to go to help->check for updates and let that finish once all software in eclipse updated it all seems to work fine. I was using juno and the latest sdk, which I upgraded outside eclipse.
i was facing the same problem.
the solution is...Copy the link http://dl-ssl.google.com/android/eclipse/
then in eclipse go to
Help > Install New Software > Add(work with) > past the link on locations > ok > select all > next
this will solve your problem.
If you already setup location in preferences, but see that error, try to create folder "add-ons" in your sdk folder
had the same problem in windows, the reason is always displayed at the top of the window(where you browse for the location)
Here is, how I've handled this issue (Mac OS X 10.8.4):
1) Because I previously have installed Android Studio the sdk located here:
Applications/Android Studio.app/sdk
You can dig into Android Studio.app folder by hitting "Show package contents" in context menu
2) Simply copy the "sdk" folder to another location and write it down to Eclipse preferences.
Because I couldn't find how to properly add adress like "/Android Studio.app/sdk" (folder with .app extension) to Eclipse preferences.
I know that this solution is not smooth and best, but it works (at least for me). And I've tried all advices in this theme, and installed the ADT from http://dl-ssl.google.com/android/eclipse/ before, but the error window have kept appearing every time.
I had the same problem: when click on the "Opens the Android SDK Manager", a pop out error message says “Location of the Android SDK has not been setup in the preference”.
The delete and add again update address in "install new software" doesn't work for me.
I went to the ../android/android-sdk-windows and click the SDK Manager.exe. This works for me.
So I think after I updated the SDK, the eclipse cannot trigger the SDK Manager currently. But it can run by itself outside of eclipse.