I would like to do development for a rooted Nook Simple Touch, which uses Eclair. I've downloaded the Android SDK and launched the Virtual Device Manager, but as it is now 2015, it doesn't offer any versions before Gingerbread. Is there a way I can get an Eclair virtual device? Alternatively, is there an older SDK package I can get?
Thank you,
Bob
it doesn't offer any versions before Gingerbread
The standalone SDK Manager does when you check the "Obsolete" checkbox. Note that the emulator images were in the "SDK Platform" options back in the old days, rather than having separate line items in the SDK Manager.
Related
I bought a course at Udemy, but the version that the instructor uses is older than mine. Thus, I couldn't finish my installation successfully. In the version that he used, there were 3 boxes to check on the first opening. Android Studio, SDK, and virtual device. He checked all of them. But mine doesn't have SDK box at all.
I am totally new to the Android studio and using windows 10. How should I install the sdk?
Install Android Studio, and if you want to configure SDK settings or whatever that is related to SDK, go to Tools -> SDK Manager
If you want to configure virtual devices go to Tools -> AVD Manager.
see the Android Studio intro, which explains how to use the SDK manager.
it's toolbar icon had been changed recently, which may lead to confusion.
use x86 emulator images for best performance, when HAXM is supported.
I work by eclipse and android studio to develop game and upload it in play store , but the problem is the sdk that take too much disk space more than 40GB , my question :is it necessery to install all SDK ? Because i test my app on particular device.
40GB seems very steep but yes it is necessary
If you're using a physical device for debugging and not the emulators, you can uninstall installed Android API versions by opening tools > android > sdk manager and unchecking the packages you don't need.
I have a physical Pixel device running 8.0 I use for debugging, so I do not have the Oreo package installed on my machine. I have a few emulators running lower versions of Android that I have installed through SDK manager. Hope this helps!
Above you can see I have almost every 7.1 system image installed, yet my only options for CPU in my AVD are for TV or the wearable... what am I doing wrong? I just want to emulate a regular old Android phone :(
You are using SDK Tools v25 which do not support the new avdmanager images. You will need to use SDK Tools v26 and the Xamarin Android Device Manager.
I'm just starting Jesse Liberty's new Pluralsight course, "Building Your First Mobile Application with Xamarin.Forms and Visual Studio 2017" and I'm running into a problem right out of the gate.
In the video, Jesse creates a new Xamarin.Forms project, modifies the XAML a bit, and runs it. Here is a screenshot of his list of emulators:
I've disabled Hyper-V, and installed the latest Intel HAXM.
I've followed along step-by-step, using the latest version of VS2017 (installed yesterday, no updates available), and I've used the Android SDK Manager to install the SDK Platforms APIs 23 - 27. More specifically, I've installed every available option for Android 6 (API 23), which is what shows in Jesse's list.
I have set the following Android project Properties:
Application :: Target Framework = Use Latest Platform (Android 8.0 Oreo)
Android Manifest :: Minimum Version = Android 6.0 (API 23 - Marshmallow)
Android Manifest :: Target Version = Android 8.0 (API 26 - Oreo)
When I open the dropdown, I don't even see the VisualStudio_android emulators at all, and I'd assume they come preinstalled with VS2017 when I install Xamarin, but no:
I have no idea where to get the Visual Studio emulators; but, as I understand it, they run much faster than others so figuring this out will probably be worth my time.
The Android Virtual Device (AVD) Manager doesn't list the VS emulators, so I can't add them from there. I know there is an Android emulator from Microsoft but it says it's Hyper-V compatible, and I've just disabled Hyper-V to use the other emulators. Is this a good choice? Are these the emulators I'm missing?
I'm out of ideas - what's my next step?
They have been renamed to streamline development. We only install a minimal amount of emulators. They used to be named visualstudio_ and now just android_ but you can create as many as you want.
I use intel haxm x86 emulators from google.
It turns out, the emulators weren't installed for some reason when I installed VS2017 and the Mobile Development Workflow.
I went into the "Individual Components" tab in the Visual Studio Installer, checked the emulator boxes, and all the emulators show up fine now.
Try uninstalling visual studio and then installing it again (save your projects first) and make sure that you install the Microsoft Visual Studio Emulator for Android. Check everywhere in the installation guide (Specifically under Cross platform mobile development). You might have missed it during your installation process.
I've just did fresh installs of the ADT bundle (20130522) and the Android Studio. (because my eclipse install got screwed up again, but that's another story.)
In either version, when I launch the SDK Manager, I don't have any system images for 2.2, only an x86 image for 2.3.3, and no images for 3.0, 3.1, and 3.2.
I couldn't find any official word as to why they've been removed. Is there now a better way to test on those platforms rather than by using the emulator images?
Check the "Obsolete" checkbox, towards the bottom of your SDK Manager window, and you should see them.
More specifically, up until Android 4.0 (or thereabouts), the ARM emulator image was not broken out into a separate download, and so you get that from the base "SDK Platform" download.
Why would people expect the ARM image to be part of the SDK platform for <4.0, when it is broken out separately for 4.0+
Well, for those of us graybeards who have been developing for Android for a while, it's second nature... :-)
More seriously, I suspect they did not want to attempt to repackage the older releases. Bear in mind that the only available platform for Android was ARM up until about 2.3, and so having a separate ARM image download would have seemed odd back in the beginning.