Target on genymotion - android

How to set the target on genymotion emulator like this (Google APIs)?

There's no Google APIs equivalent images for Genymotion. If your app needs anything that is not in vanilla AOSP, then you need to install all the Google Apps (like Google Play Services etc) separately.

Related

android emulator with google play services at docker

I want to create a dockerfile that creates an android emulator with version 7-8 and google play services
Does anyone know how can i do it?
Thanks
Maybe you can use some android emulator(like a Genymotion) and set up a Google play services inside. But Genymotion doesn't provide Google apps and
you must set up it manually using a ARM Translation Installer.
If you want only run android apps on docker, you should look at this.

Android emulator with google play services

I created an android emulator to test google play services, with the google apis 4.2.2 or greater like this article said
https://developers.google.com/android/guides/setup, but only google maps services is available, and the game I am testing claims for google play services. I am missing something?
You can refer google play services in 4.2.2 emulator
And I will suggest you to use Genymotion instead of using android default emulator. It is like virtual phone and you can also add Gapps in it as well as download any app from Google Play, same as android device.
Genymotion and you can download google apps based on your virtual device version from this Genymotion Gapps link
You have to run an emulator with Target: Google APIĀ“s
Also be sure of compile this:
compile 'com.google.android.gms:play-services:8.3.0'
(Lastest version of google play services) If it doens't run, check for the verion of google play services on the emulator and change the version to compile.
Start SDK Manager. Check APIs in android version you create emulator and install it. Open SDK folder/system-images and delete the emulator image. Start Emulator Manager and dowload new image with api. Start new emulator and it fixed.

Android - What is the best android emulator to build maps app?

i have a problem to run Android on Android Emulator,i'm using Android Emulator but it too slow,i already try another emulator such Bluestack but it is same for me,too slow,then Genymotion but there is no Google Play Services on it now,any suggestion for me??
Install haxm you can download externally from HERE, see installation instruction here HERE
once your installed create google api based emulator with intel cpu
You can use Genymotion to run your application.Genymotion is an open source Android emulator for app testing and presentation. You can control simulated sensors like battery, GPS, accelerometer,camera etc. It is quick and powerful Android emulator.
You can download it from This LINK
i would recommend genymotion.You can install google play services and google apps in geny motion easily.You just have to install ARM Translation in genymotion.Here's link that will help you
http://forum.xda-developers.com/showthread.php?t=2528952
Genymotion is very good emulator for testing maps based applications. It supports OpenGL. You will find a lot of good features in it. It is very easy there to set the test location points.
To install Google Apps like Gmail, Google Play Service, Play Store, Map etc you have to install GApps.
http://wiki.rootzwiki.com/Google_Apps

Install Google Settings on HAXM x86 emulator (Google Maps SDK)

I've gotten a VM accelerated Android emulator (4.2.2, API 17) working using Intel HAXM (on a Mac). I installed the Google Maps SDK using these instructions, which is basically this answer to a previous SO question - Google maps SDK with new Intel Atom x86 emulator - but with pictures.
Therefore, the emulator has access to Google APIs. However, I need to enable location access for Google apps. This is usually done through the Google Settings app, but since the emulator was created targeted to API 17 (not Google APIs 17), Maps and Google Settings are not installed.
Where can I find the .apk for Google Settings in order to install it? It would be even better if there was a way to permanently keep it on the emulator (so that -wipe-data does not delete it).
(I know I need to enable location access because of a problem I was running into earlier. See my previous question here.)
There is now a new x86 system image available which has the Google APIs. Install it from the SDK manager - it's under API 19 and called "Google APIs (x86 System Image)". Using an emulator created from that image you should find you have all the Google APIs you could previously only get on ARM system images (I have only tested Maps v2 so far, but it worked).
As per Google Android Map Api v2 ypu can't run it on an Android Emulator; you need a real device to test your apps. To run a app which uses Google Maps v2 you need two applications already running on the device
1. Google Play Services (com.google.android.gms.apk)
2. Google Play Store (com.android.vending.apk)
Follow this guide here to download and install the latest version of these two apk's using adb commands.

Why would you choose Android API over Google APIs in the SDK on Eclipse?

When you create an android project in Eclipse, you have to choose which platform to compile with. You can choose API 17 (Android 4.2) or Google APIs (API 17).
From my understanding, Google APIs is API 17 (Android 4.2), but has the maps library support and usb open library. So if Google APIs is the same as Android, but with more features... why wouldn't you choose it everytime?
Is there a downside to Google APIs? Every tutorial online I see, they use API 17 (Non Google APIs). I'm always curious as to why they manually change it to that instead of just using the one that has more in it.
When you run with Google APIs, your app is built to run on a device which has the Google services installed on it already (Maps, USB etc). If you absolutely require these services, you should build against Google APIs, but then your app will not run on device which aren't certified by Google (that is, don't have Google Play installed).
If you do want to run on device without Google Play, and your app does not require any of the Google Services to be 100% present, then you should compile against the normal Android APIs.
See this document for a bit more on what Google expects from certified devices.
Some of the cheap android phones which aren't certified android phones (those that don't have Google Play) won't support apps compiled against the google api. So unless you need functionality provided by google api, just build against android api
Google APIs includes some extra things like Maps. It is optional, and some people don't want to download the extra stuff. The examples use the non-API version in case the person downloading the sample didnt download the Google APIs.

Categories

Resources