I just started to install Android Studio, but I am finding it difficult. Now I'm stuck trying to enable an AVD at the emulator.
As you can see at the image below, variables are set and SDK tools and environment are updated. I'm using Windows 10 with AMD (HyperV virtualization enabled). What more can I do?
Well, it's solved. The issue comes because of Windows 10 Spanish version sets as default username Tú. Creating a folder at C:\Users\Tú
The accent breaks the AVD giving the error at the picture. We should change our username, rename the folder and swap all the windows registry entries referencing to the folder.
If you have this issue, maybe this video would help: https://www.youtube.com/watch?time_continue=35&v=J_rTOA4gXJI&feature=emb_title
Related
I tried to install flutter (including android studio and emulator) on Windows OS (also tried Linux dist. (Ubuntu)). I keep getting the same error when I try running the emulator: "Unable to locate adb". However, I checked and the adb file is located in platform-tools and the path is referenced correctly (to my knowledge). Also, even though the error pops up, the emulator still loads. I've even tried running the test code (despite the error), it gets stuck on the following line: "Running Gradle task 'assembleDebug'...". I have checked environment variable path/made sure paths are set correctly. I have tried reinstalling the software and the platform-tools folder, as well as any other suggestion I've seen online. I can provide more info if needed. Any help would be greatly appreciated!
Software Version Info:
Windows 10 Home,
Ubuntu 20.04,
Flutter 1.17.4,
Dart 2.8.4,
Android Studio 4.0
Android Studio - launch emulator AVD - "unable to locate adb"
I have answered to your question already, kindly visit the above link to read more.
Solution:
Click on the project folder, tap the dropdown icon just beside it.
Now Navigate to the path below.
android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
Now Click on the file GeneratedPluginRegistrant.java to open it.
Once it is open, At the Top you will notice a bar that says 'Module SDK is not defined',
Now right against it, you will also see a hyper-text named 'Setup SDK', Just Click on it.
That will open a Pop-up Box with the title 'Select project SDK'.
Now select the Android Platform API and then click OK. After that being done Restart your IDE.
Your Problem will be Solved. And you will also notice that Emulator Opens up way faster than before.
NOTE:
The Above Steps has to be performed with every new flutter project.
I just recently experienced this issue myself. I'm on Ubuntu 18.04.5 LTS.
This was happening because there wasn't enough space in my pc.
The solution was to make space in my home directory by deleting old stuff.
First post--be gentle. Can't find any posts on Android Studio 4.0, so I hope this isn't a repeat. I updated Android Studio from 3.6.3 to 4.0 on Windows 10 (1909). Had created a couple of virtual devices in 3.6.3 (a Pixel 2 running API 28 and a Pixel 3 running API 29)--both worked great in AS-3.6.3 and I could develop apps, compile, load, and run them with no problem.
After the update to AS-4.0, the virtual devices no longer appear in the devices box at the top of the GUI--it just says "No Devices". When I open the AVD Manager, I can see them, and I can start them (although when I start them I get a pop-up saying "AVD Manager: Unable to locate adb"), but I can't get any code to download and execute on it. On the Pixel 3 emulator, I also get another pop-up saying "Detected ADB: Could not automatically detect an ADB binary.", and it gives instructions to resolve it, which don't make any difference (jump into extended controls and toggle "Use detected ADB location").
When I try to open a past project and run it, I get the same behavior--no devices found.
I've also tried making new emulators, hoping the new setup would recognize them, but to no avail. Tried starting and restarting AS, as well as the computer, also to no avail. I have Android SDK Build-Tools 30-rc4, the latest Android SDK Command-line Tools, Android Emulator 30.0.12 Android SDK Platform-Tools 30.0.1, and the Intel x86 Emulator Accelerator all installed.
I've Googled and spoken words of fierce power over this for several days now. Any suggestions for how to get AS-4.0 to recognize the emulators? I've resisted uninstalling everything and starting over--was hoping it was just a configuration thing.
Thanks in advance,
Uber
After some more Googling, I found the answer here (I think my constraint of wanting an answer for AS-4.0 specifically kept me from finding it):
Could not automatically detect an ADB binary - Android Studio
I had to redownload the SDK platform-tools zip file and reinstall it. I don't know why the old one got messed up with the migration from AS-3.6.3 to 4.0, but there you go--such is life with complicated software.
As soon as I replaced the old platform-tools directory with the new one, all my old emulators showed up and I was back in business.
Thanks anyway!
Uber
I've just downloaded and installed Android Studio but there is no Android submenu in Tools menu and no AVD Manager icon on the instrument panel. When I start SDK Manager, there is an error message:
Please specify a Android SDK location
SDK Manager screenshot: "Please specify a Android SDK location"
If I click on Edit link next to Android SDK Location field, there is another error message:
Your SDK location contains non-ASCII characters
SDK Components Setup screenshot: "Your SDK location contains non-ASCII characters"
I studied these somewhat similar questions, but non of them helped me:
Your project path contains non-ASCII characters android studio
Unable to install SDK tools component while installing Android Studio
unable to install or locate android sdk in android studio
NO Android option in "tool" menu, and no avd manager
I see that the path really contains non-ASCII characters, but is there any workaround other than uninstall Android Studio and then install it from scratch to some other directory like С:\Android\SDK?
UPD:
it seems there is no such workaround at this time
As a matter of fact at the moment there is no other way than to re-install Android Studio to some other directory with no non-ASCII characters and blank spaces, like С:\Android\SDK
I guess you've solved this by now but I ran into the same problem today and after a little research and some annoying tries I solved it. What I found out is this:
Using mklink function you can create a junction to a location but it will not boter if you are creating a it to a non existing location(that's the "file not found" you were getting). And you are creating a junction to a non existing location in this case due to C:\Users\username\AppData\Local\Android\Sdk should(not sure about this) be created by the Android Studio Setup Wizard during installation. In order to solve that, you should create \Android\Sdk in C:\Users\username\AppData\Local and it's done.
The installer does not show junctions to non existing locations in the Sdk install location so if you don't create the folders you can't select the link.
Finally but not less important, the installer does not allow the Sdk to be installed in a folder in the root directory C:\, so you have to create the junction in any other directory but the root one or move it if it's already there(that's what I did).
As I was writting this the installer was running and when it was done I came across the exact same problem with the location to store Android Proyects, and so the same solution to the installer must be aplied to the Save location in the New proyect step.
This is exactly what I did:
1) Create \Android\Sdk in C:\Users\username\AppData\Local\
2) Open cmd as admin and enter the following command:
mklink /J "C:\..\android-sdk" "C:\Users\username\AppData\Local\Android\Sdk"
It will return this:
C:\WINDOWS\system32>Junction created for C:\..\android-sdk <<===>> C:\Users\username\AppData\Local\Android\Sdk
Note: android-sdk is the name the junction will have, you can name it as you like and \..\ reffers to the folder where you want to put the it in, make sure there are no non-ASCII characters in the folder's name anyways.
3) In the Sdk install location, select C:\..\android-sdk and the installation will be ready to go.
4) Repeat the process for the Save location for new proyects, just instead of C:\Users\username\AppData\Local\Android\Sdk use the location you want the proyects to be stored in.
Didn't try moving the junctions files but I suggest you don't, I guess that could get the paths lost and mess up the installation.
Hope this is usefull and good luck with your proyects!
If you don’t want to reinstall the Android SDK in another location you can also create a junction point which is a link to the actual location. You can use the junction tool to do this.
For example, you can create the directory C:\Android and then create the junction SDK and claim the SDK lives there with
Junction C:\Android\SDK C:\Users\Whatever\actual\location
The operating system will show the same contents under both paths and applications will not know the difference.
Hey I had the same problem here but I was able to fix it by just changing the directory to a new folder directly on the hard drive.
Hope this can help.
In my case since I have a Windows 10 operating system, and my sdk was located in Program Files. Having spaces in the directory caused some sort of error, to solve this I used mklink to create a junction called android-sdk in the C drive that pointed at the directory where my sdk was located.
If you can't find the sdk in
C:\Users\username\AppData\Local\Android\Sdk
I suggest looking at
C:\Program Files (x86)\Android\android-sdk
then trying
mklink /J "C:\android-sdk" "C:\Program Files (x86)\Android\android-sdk"
Afterwards open Android Studio go to Project Defaults > Project Structure > Android SDK, click on the "..." button to browse for your sdk and select the junction you just created. Or if you still haven't setup android studio because of this issue, open the application as administrator select the theme settings and all that, and when you reach the setup sdk section, click on the "..." button to browse for your sdk and select the junction you just created.
Important to run Android Studio setup as administrator otherwise you may experience issues downloading components, if you still have issues it might be your antivirus blocking the setup.
When I first start the emulator in Android Studio I get an information message,
guest hasn't come online in 7 seconds retrying
I am curious as to how to stop this because while it is on my screen for about 40 seconds I cannot do anything in the emulator.
Actually 'Cold Boot Now' may work in this situation
I had the same problem. Selecting Cold Boot Now in AVD manager solves the problem.
But I have to open AVD manager each time when I want to launch Emulator and I just want to click on Run app button and select device, without opening AVD manager.
To solve this: open AVD manager -> Edit device -> Show Advanced Settings -> Boot option -> select Cold Boot instead of Quick boot.
tools->Android->AVD Manager
Choose the device then Cold Boot Now
maybe it's bug from intel haxm 6.2.1, because after i update i got same problem.
I solved by recreate emulator and testing again
I managed to solve this issue by updating the .ini file manually. (I was not able to find a corresponding setting in the GUI.)
The location of the .ini file, relative to your home directory, is:
~/.android/avd/MyDevice.avd/config.ini
where MyDevice refers to the configured device name.
Depending on your operating system, you may find your home directory according https://en.wikipedia.org/wiki/Home_directory.
Change the entry within config.ini from no to yes:
fastboot.forceColdBoot=yes
I specified AVD memory 2048 Mbyte instead of 1536 Mbyte. Things
started to work again. (I'm developing on macbook.)
I tried "Kuldeep Chandel" solution which is to duplicate AVD and my app runs again too. Because of that I specified RAM again as 1536
Mbyte. Guess what... It worked...
I think AVD confuses to handle things and we need to duplicate the current AVD, and use it instead of the problematic one.
In "Your Virual Device" - Click on Duplicate OR Duplicate your Device. It will work like Charm.
I faced this issue on using Android API 28 emulator with Android Studio 3.0.1. Android API 28 requires Studio 3.1 and above. Once I updated Studio to 3.1.4 and Android Emulator to the latest version, it worked.
Seting default settings for problem device from Android Device Manager resolved issue for me.
I'm trying to install Visual Studio 2012 Express for Windows Desktop and every time I run the installer I get this error:
"Windows Program Compatibility mode is on. Turn it off and then try setup again."
I checked the file properties and compatibility mode was off. Googling found that changing the name to "vs_premium.exe" or "vs_ultimate.exe" or changing the registry keys might help, but the name changes had no effect, and there were no registry keys to delete. I have restarted my machine several times to no avail.
Changing to Visual Studio 2013 is not an option for me, as my work computer has Visual Studio 2012 on it which they will not update to 2013, and I need to work on my project on both computers.
The computer I am using has a Windows 8.1 HP Pavilion g6. I have installed Visual Studio 2013 for Windows Desktop, Web, and Windows, as well as the 30-day trial for Professional (which has recently expired). I have also installed Visual Studio 2012 for Windows Phone but I have not used it yet.
Previous posts are correct in that compatibility mode appears to be based entirely on file names. There is a simple method for determining precisely which name Windows expects:
Right-click the file, select Properties and navigate to the Details tab. There should be an entry labelled "Original filename". Simply rename the file accordingly and it should run happily.
Screenshot:
If you downloaded Visual Studio 2012 and Visual Studio 2013 at the same time and one was renamed with a "(0)" suffix (just as I did) then change the installer to the original name will probably fix it, because "somehow compatibility checking is based on file naming"
I just have to Rename the setup name. I rename the setup file to vs_ultimate and it worked.
In case you mounted it, first extract the content before you install. it worked for me.
Had the same issue installing vs_ultimate on Windows 10, It tells me to turn compatibility mode off which I didn't know to do. After reading all the solutions above without success, I was able to solve it on my own.
I mounted the .iso before installing which was giving me problem, but later as I extracted it into a desktop folder, it installed fine.
I couldn't find a solution, but I could find a workaround. I downloaded the offline installer (ISO) and ran that instead. It's not a solution, but it should work in this situation.
I ran into this problem and the solution for me was to rename the file back to its original name. I had downloaded it as "vs2012sdk_full.exe" but the original name was "vssdk_full.exe". When I ran it as "vs2012sdk_full.exe" I got the compatibility mode error. Once I renamed it back to the original "vssdk_full.exe" it worked.
Open The Run (Win+R) And type Services.msc.
Found Program Compatibility Assistant Service Then Disable Service and Stop it.
Open the Run (Win+R) And Type Gpedit.msc.
User configuration-->Administrative Templates-->Windows Components-->Application Compatibility
And check Enable button then restart system.
Run as administrator. And for my 2013 installer I renamed it to be
vs_professional.exe
And it worked.
In a round about way I discovered the problem on my system. Check the properties of the installer. Mine was blocked because it was downloaded from another system. Click unblock. Voila! If you can't find the location of the installer, run it again. When it fails, leave it running. Open task manager, right click the installer, then open file location. This will take you to the folder containing your installer.
mount the ISO file and run the setup as a from the disk.
I had the same issue, my solution was to run it in administrator mode and it seemed to work just fine.
Run as Administrator worked for me.
I had the same problem. I had run the installer from an ISO, reading from the DVD image.
The solution was to simply take the ISO and uncompress it as a .RAR into some folder, and everything worked.
Well, filename varies from versions to versions. Fix:
Right Click on file
Select Properties
Select "Details" tab
Rename that file to value of "Original Filename"
This is the solution:
Right Click on Visual Studio Setup Icon
Select Properties
Open Compatibility Tab
Check Run This Program In Compatibility Mode
Select Your Windows Version (ex:Windows 8)
Finally Click OK And Install Your Program Again