Is there a central place where I can find the specs for the majority of the Android phones available on the market? I want to create avds for each of them.
Android SDK v6 tools brings sdk addons to the emulator via avd manager instead of the old way..expected release with android Os 2.2 sdk sometime within the next 4 to 6 weeks..
Suppose to simplify the way to integrate those emulator addons with items like google maps etc..
That is why is some OEMS have been waiting instead of issuing emulator addons..
Related
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.
According to an article in the Android Developers Blog, regarding the release of Android Studio 2.0:
Android Emulator - The new emulator runs ~3x faster than Android’s previous emulator, and with ADB enhancements you can now push apps and data 10x faster to the emulator than to a physical device. Like a physical device, the official Android emulator also includes Google Play Services built-in, so you can test out more API functionality. Finally, the new emulator has rich new features to manage calls, battery, network, GPS, and more.
Great! That's exactly what we need. Later on the article they explain how we can get Google Play Services in our emulators.
Trying out the new emulator is as easy as updating your SDK Tools to 25.1.1 or higher, create a fresh Android Virtual Device using one of the recommended x86 system images and you are ready to go. Learn more about the Android Emulator by checking out the documentation.
I have SDK Tools 25.1.1 installed. I have a fresh Android Virtual Device running x86 system image.
No Google play services :-(
What am I missing?
When you create your virtual device, be sure to choose the one "with Google APIs". If that isn't an option, you will have to use the Android SDK manager to download the Google APIs for each API level you want to work with.
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.
This question has many parts.
Some info about my system:
64-bit Ubuntu Linux
I am wondering what the stock emulator is that comes with Android Studio (A.Studio) (if indeed it has a name).
A helpful answer would include comparing this emulator with other emulators. A list of pros and cons of using each different emulator would also be helpful.
Perhaps there is a more fundamental ~thing~ about using different emulators; information on that is welcome if anything comes to mind.
Finally, i have never used an emulator besides the one that has come with Eclipse or A.Studio. What do I need to know in order to plug any emulator into any IDE? I have had issues with IDEs being "fragile" and breaking frequently, FYI.
You can use genymotion, for fast speed the quality, both for the eclipse and Android studio, get it here.
Also you can set up the Google play service for using Google Maps and downloading apps from Google play store.
Get the package and how it use it , please refer to here.
The emulator used by Android Studio is the exact same one used with Eclipse. It is in fact included with the Android SDK (which is in turn included in Android Studio) and used by various development environments.
The way it works depends on what kind of system image you use it with. For most recent Android versions, there are 2-4 different system images - arm, arm 64-bit, x86, and x86 64-bit (the 64-bit ones are Lollipop only, and fairly experimental at this stage of the game [early 2015]).
There are also Google API versions of these images (they include various Google apps such as Google Play Services) which can be used if these components are needed by your app.
For development purposes, the x86 system images are your best bet as performance is vastly improved by the emulator not having to emulate the ARM architecture - you need to use HAXM (by intel, also available in the Android SDK) to get any real speed benefits with x86 images though. The emulator also provides GPU acceleration (it must be manually enabled for each emulator device) which allows it to use your physical GPU for rendering instead of emulating these operations in software.
The way the development environment (Android Studio) connects to the emulator is via ADB (Android Debug Bridge). This means that it can work with virtually any emulator (such as Genymotion, which runs via VirtualBox). However, there is native support for using the Android Emulator from within Android Studio (this is configured by selecting emulator in the Run/Debug configuration)...when using another emulator (such as Genymotion) you should select USB device (in Run/Debug configuration) and make sure that the ADB instance is connected to your emulator via TCP (Genymotion does this for you automatically at startup).
This should give you enough information and I will not re-post all the various instructions on how to do any of the above as they have been posted as answers to various questions here on SO.
I was taking a look at the nook developer site on barnesandnoble.com and noticed that their claim is:
The NOOK Tablet SDK contains the following components:
Android Virtual Device (AVD) Emulator
Android Debug Bridge (ADB)
configuration settings
I was wondering if that means that everything else is exactly the same as the android sdk except the emulator plugin and the adb settings?
Thanks
You are correct - it is similar to the LG, Sony, Motorola SDK add-ons that are loaded as part of the official Android SDK.
The current links are below (but note that these seem to change quite often and are correct as of Jan 2012 - register and check with NOOK regularly).
[NOOK Tablet, API 10] http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
[NOOK Color, API 8] http://su.barnesandnoble.com/nook/sdk/addon.xml
Once installed via android sdk manager (use Tools >> Manage Add-on Sites ), it should automagically update ADB drivers on Linux/Mac Osx and have emulators available via AVD.
You can run "android update adb" in order to get ADB functioning. I havent tested in Windows but this should be similar.
Do you mean the emulator or the device itself? The emulator is an approximation of the real hardware, but I don't think it includes all of the real software and configuration.
The emulator operates closely to a normal AVD, but with a different skin and different setup for Nook-specifics (e.g. /media is available to write). However, some operations will appear to work in the emulator but cause a failure on a real device (or at least the QA testing). Some of the Nook-specific workarounds won't work on the emulator (e.g. calling the Nook intent for wallpaper manager or the Nook store).