I want to test against Android 1.3 platform instead of latest 2.2.
Here is how my Android SDK and AVD Manager look likes.
However, I was expecting (screen from http://developer.android.com/sdk/installing.html#components), so that I can select old platform.
Is there anything I had missed out?
Run Help > Check for Updates first, to update your Eclipse plug-in, then you can access the repository. Why would you want to test against 1.3? If anything is still on that old a version of Android (was there even a 1.3? It's not listed here), it's an insignificant portion of the market. The earliest you should even worry about is 1.5.
Also - on the bottom of the first screen between "Delete Add-on Site..." and "Refresh" uncheck the "Display updates only" check box.
Related
I am trying to add Android Q using AVD manager but it says: "Package "Android Emulator" with revision at least 28.1.9 not available." Has anyone tried this before? what should I do now to resolve this.
Thanks to #JulianC I also set the emulator. I tried to download it standalone from the official site, but couldn't. Then switched to Canary Channel. I pressed Tools > SDK Manager, then Updates label and changed channel. Also pressed Check Now button and dismissed a dialog (Remind Me Later).
Then switch to Android SDK and updated needed emulators.
Then reverted back to Stable Channel.
After several days of work I faced some visual bugs in the emulator. Sometimes I have to restart virtual devices from AVD Manager with Cold Boot Now:
Sometimes I recreate virtual devices in AVD Manager.
Based on https://developer.android.com/preview/release-notes:
Note: If you try to download the Android Q Beta 2 emulator system images from within the emulator, you will be prompted to download the latest version of the emulator. If you are on the stable channel of Android Studio releases, then you might need to switch to the canary channel to be able to download this latest version of the emulator. You do not need to download all of Android Studio from the canary channel—you can download only the emulator from the canary channel from within the SDK Manager.
You have to use the Android Studio Canary build to get an updated emulator. This worked for me
As stated in the other answers, installing the update from the canary channel solves this problem. However, if you don't want to install Android Studio from canary channel, you can just use the sdkmanager tool. Just run this in the terminal:
sdkmanager --update --channel=3
************ EDIT ****************
Today I found version 29.0.6 available in stable channel.
Just click "Check for Updates..."
I found kind of solution.
Go to Preferences -> Updates
Select "Canary Cannel" and click "Check Now"
Dismiss the updates "Remind me Later"
Go to Preferences -> Android SDK -> SDK Tools
Click 3 times on "Android Emulator" checkbox (The state on the checkbox will be the same like in the beginning)
Go again to Preferences -> Updates
Select "Stable Channel" and click "Check Now"
Install recommended updates (android emulator to 29.0.3)
Also you have to download Android Q Preview from Preferences -> Android SDK -> SDK Platforms
It works for me.
Hope to help you :)
For a more recent answer:
Those installing from snap:
The reason is listed here:
This happens because Android Q is still in beta and therefore it’s only be available
through the Canary and Development channels.
The solution is to download Android 3.6 from here.
For anyone who bumps into this issue whilst using Android's Command Line tools, --channel=3, at least on Windows, will not actually net you the latest version of the Android emulator, and thusly as it is dependent on that Emulator version, the latest Android images (particularly google_apis_playstore;x86 v8)
As a workaround, I was able to manually install the package by fishing around in the repositories here:
https://dl.google.com/android/repository/repository2-1.xml
I was sufficiently annoyed about having a broken tool that I made a lightweight Python tool to do the steps below for most any package, which is what I link below under automated version.
This will also work for the Android Studio versions in theory, but I haven't tested those personally. Your mileage may vary.
AUTOMATED VERSION
Clone or otherwise download this repo: https://github.com/FailSpy/android-sdk-alternative
With Python 3.6+ installed, go into the folder you cloned it to with your commandline, and run python downloadtools.py emulator (or any package name if you're looking for other packages)
That will then download and unzip the latest package for you in the location of your SDK (using env. variables ANDROID_SDK_ROOT or ANDROID_SDK_HOME)
MANUAL VERSION
To make this easiest, you'll need an existing install of the emulator
To find the latest version download URL:
Find on that XML file a <remotepackage> tag with path="emulator" featuring inside it the <channelRef> tag with 'channel-3' -- which signals latest version, locate the 'url' tag for the latest version for your platform (currently, emulator-windows-6549980.zip) and add that to the end of the previous URL -- replacing 'repository-2-1.xml'
e.g. https://dl.google.com/android/repository/emulator-windows-6549980.zip (if you're not too far from the future, you can just use this link rather than digging -- just replace 'windows' with 'darwin' for MacOS or 'linux' for Linux)
Take note also of the major, minor, and micro tags in the archive as well. We'll need this in a moment. In this case: 30, 0, and 16 respectively to make version 30.0.16
At that point, find your SDK install location
Find your currently installed emulator package in there under folder emulator, and edit your package.xml. Replace the major, minor, and micro with the version you found in the repo (or lazily with the version you know you need, though I don't recommend this)
Finally, delete the existing install (making sure to keep your edited package.xml!) and unzip your downloaded file into there, replacing your install.
Your SDK Manager should now recognize the emulator install as the version you set, and allow you to install the latest images.
I've never struggled with anything in programming as much as this Xamarin installation, unbelievably flakey. I've got my environment (VS 2015 Enterprise) to a point whereby I can spin up a new Blank App (Android) but the designer requires a newer version of the Android SDK (apparently):
I've only just installed the latest Android Studio, so I can confirm (in Xamarin settings) I'm pointing to the correct path for the SDK (in AppData/Local etc.)
On opening the SDK manager I can see the latest SDK tools is installed.
Please note: I've also tried running the SDK manager independently of VS (and as admin).
Never had this much trouble trying to get something installed and configured. Any help MASSIVELY appreciated.
Whoever helps me crack this gets a massive bounty.
EDIT:
Found this in the logs, fairly certain this is the issue:
Xamarin.VisualStudio.Android.MonoAndroidDesignerPane Error: 0 : [2016-09-22 16:36:54.2716] System.AggregateException: One or more errors occurred. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Xamarin.VisualStudio.Android.Designer.MonoAndroidDesignerDocumentCache.Push(String filePath, AndroidDesignerDocumentCacheItem value) in C:\data\lanes\3513\c4382f51\source\xamarinvs\src\Core\VisualStudio.Android\Designer\MonoAndroidDesignerDocumentCache.cs:line 25
at Xamarin.VisualStudio.Android.MonoAndroidDesignerPane.OpenViewCode() in C:\data\lanes\3513\c4382f51\source\xamarinvs\src\Core\VisualStudio.Android\Designer\MonoAndroidDesignerPane.cs:line 619
at Xamarin.VisualStudio.Android.MonoAndroidDesignerPane.b__66_0() in C:\data\lanes\3513\c4382f51\source\xamarinvs\src\Core\VisualStudio.Android\Designer\MonoAndroidDesignerPane.cs:line 612
EDIT
Bounty is for Jon when it allows me to award it. This issue has already been resolved.
Try to delete your obj/bin folders as it seems you might have an AndroidSdksCache holding the old version. Specifically look for a file here obj\Debug\sdks.cache.
The second note is that you have build-tools 23.0.0 installed. Please uninstall that version and any other old version and install 24.0.2.
It shows the current directory as being C:\sdk1\ when the referenced SDK version is different in your screenshot. You will need to update C:\sdk1\ to the latest Android SDK Tools.
I think that can be many things.
1) some time your user name in your PC if have character specials like accents or spaces. Make problems with the VS.
2) you need check if you install Visual studio Emulator android. After donwload a device and check the api that have that device.
Windows 8 or windows 10 pro.
https://www.visualstudio.com/en-us/features/msft-android-emulator-vs.aspx
Don´t use the generic emulator. If you dont know how configure.
3)Make sure that you have install Xamarin correctly in your VS.
Tool -> options -> Xamarin
you need watch all the green check.
if the android dont have the green check. Search the route when you have install the sdk. For example watch the image. My root for example
Let me know if this solve your problem. Regards.
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 just updated my Android SDK Tools to version 21.1. Unfortunately this is causing an error when I load the Android Developer Toolkit:
The Android SDK requires Android Developer Toolkit version 21.1.0 or above.
Current version is 21.0.1.2012-12-6-2-58.
Please update ADT to the latest version.
When I upgraded the SDK I was warned that I might need to upgrade ADT. I tried to do so by going to Help > Check for Updates. Unfortunately this returns a message that "No updates were found."
In case I've missed something here's a screenshot of my Android SDK Manager:
Am I missing an install package? Do I need to go about updating ADT (Eclipse) another way? Should I just download a new copy of ADT?
For some reason ADT (Eclipse) won't pick up on the fact that it does in fact need to be updated. Since the built in tools for updating are failing you you'll have to work around them. On the Help menu instead of selecting Check for Updates instead pick Install New Software (so Help > Install New Software).
On the Available Software screen in the Work With dropdown provide:https://dl-ssl.google.com/android/eclipse/ if it's not already available. You should see a list of options including Developer Tools. Check everything that you want to update. In the list of checkboxes below uncheck "Contact all update sites during install to find required software."
Click Next and follow the remaining onscreen prompts. You may be warned that instead of an install an update will be performed. This is okay. Once the operation is complete you will no longer receive the "The Android SDK requires Android Developer Toolkit verxion 21.1.0 or above" error when you load ADT.
I'm working at the moment at a simple app in eclipse for android. Just receiving and sending data, and using the camera API.
I've set the minSDKversion to 8, because I think that has the widest user base. But at the beginning of the project eclipse was asking me which target SDK version I would use, and because I had just one installed (the latest 4.0.3) I've took this.
Now I'm asking me if it wouldn't be wiser to install a lower SDK, like Android 2.2, because it would be not that big (compared to the 4.0.3) and my app would not have included all the fancy new features, which are not used in any way?! Or is this complete nonsense I'm talking here, and just should take my 4.0.3 SDK? When not, how can I install a lower version? Help -> SDK Manager is not showing old SDKs...
Here is a very helpful link that will probably answer your question: http://developer.android.com/sdk/installing/adding-packages.html
Basically, open up the Android SDK manager and it should give you a list of packages that you can install! From there you can choose old SDKs!
hey i faced the same issue as yours
usually while updating due to this error , it is unable to fetch the older SDKs
Failed to fetch URL https://dl-ssl.google.com/android/repository/addons_list.xml, reason: File not found
This is how you can fix it :
1) Go to Window > AndroidSDK Manager
2) select tools> options
3) set the proxy (if u r sitting behind proxy)
4) in checkboxes check Obsolete option (in Android SDK Manager)
5) go to Packages > reload (in Android SDK Manager)
This worked for me
In case you are using windows7 .
Go to Android SDK Manager location > right click > Run as Administrator
Best Regards,
Ashwani kumar
I was having a problem with this also. I tried all of the things listed in the other answers here and nothing worked. I went into Tools/Options (in the Android SDK Manager) and checked "Force https:// sources to be fetched using http://" and reloaded and the older APIs magically appeared.
if u want minSDKversion from its maxSDKversion
1.select maxSDKversion and delete all old pakages .
2. after doing it sdk manager will show all its older versions .
3. select required version and install all packages again.
:) :)
it worked for me .. just try .