I have implemented an android application with Google Map, using v2 Version . i tested the app on a real device . it is working fine , but i want to test it on genymotion also . How can i do that ?
You need to follow the directions posted in this forum: http://forum.xda-developers.com/showthread.php?t=2528952%5d
Long Story Short
Genymotion emulators are missing a set of libraries that real devices have. For example to many features nowadays (such as google maps api related features) you need to have the google-play libraries. Same rule applies for all other third party apis e.g. Facebook SDK.
Some people in the forum (link above) have created such libraries that you install on your Genymotion emulator simply by drag&drop.
Hope it helps.
you have to download gapps from below link and drag and drop in emulator.
https://basketbuild.com/gapps
As others have noted, you need to download the google apps and drag and drop the downloaded zip onto your emulator. Perhaps, the best place to download from is the from the opengapps.org project. Plenty of options there too.
Genymotion emulators are missing a set of libraries that real devices have. For example to many features nowadays (such as google maps api related features) you need to have the google-play libraries. Same rule applies for all other third party apis e.g. Facebook SDK. Some people in the forum (link above) have created such libraries that you install on your Genymotion emulator simply by drag&drop.
Related
The top answer to this question (ADK and Eclipse woes - com.android.future and USBAccessory?) solved my issue (in a specific case), but I wondered why I needed to use the Google API and not the default Android API for implementing a IOIO board via USB. Why does this feature exist in the Google API 2.3.3 and not Android API 2.3.3 (since the android operating system is capable of supporting it... did the Android API developers just not add some additional functionality that makes the IOIO plugin tick?), and why is it not required to use the Google API for 4.2? Is this likely specific to the IOIO interface code I am using (https://github.com/ytai/ioio/wiki/Downloads#client-software-and-ioio-application-firmware-images)?
I would like to further understand the reason behind this so that I can better predict if I encounter a similar issue in the future with other libraries.
I do not have an idea about the USB issue you've mentioned. I just want to clarify why you need to use Google APIs instead of normal Android API in some cases.
Android code is open-source which means anyone can have access to it and can compile the code to make their own android enabled devices. Most of the device manufacturer choose Google's proprietary licensed version of Android which includes some of the Google services inbuilt which are closed source and are not included in the android source code.
These services include Google Play Store, Google Maps, Gmail, Admob etc. So if you want to use any of the Google services/features(which are not included in the usual Android features), you have to use Google APIs, which have support for these features.
An actual device running on Android OS may or may not support these features, depending upon the availability of Google Services in the installed ROM (These can be installed later if you have root access). For example Nokia X series won't support any Play Store, Google map or Google gaming services feature.
I suppose this is true in your case too.
PS: The above info is from my own experience and is not supported by any of the articles mentioned anywhere. Feel free to add references in the comments if you know any article supporting the facts.
I wonder if anyone has documentation on how to implement Google Maps v2 on Android Studio, the official documentation does not explain this.
Thanks in advance.
Well these steps worked good to me
First, update the version of your android studio to version 0.5.4 or later
Second, make the project as you want only recommend you to create at least 17 API for Google Maps V2 run with no problem and select Google Maps Activity
Third, the good thing about this update is that Android Studio in Manifest.xml and Activity are already configured to do the test directly
Fourth, do not forget to configure and enter your own api_key
Fifth: I recommend to you use Genymotion to test your apps with maps, the emulator is much easier to manage, faster and easier to install Google Play Services
http://www.genymotion.com/
http://www.youtube.com/watch?v=iCRNqCXGNK0
This question may seems very stupid but I'm really stuck. To run the map on my app on my emulator I need to run with Google Api library and on emulator), but for textview and rest of the stuff I run with Android 4.2.. How can I run the whole app?
When you choose "Google APIs" as your SDK target, that includes the full Android API for that level as well.
Thus, if you choose "Google APIs (level 17)", that will include Android 4.2.
Note that in addition to the setting the appropriate API level, you may need additional libraries to support particular Google services. For example, see https://developers.google.com/maps/documentation/android/start for details on adding the maps library, or http://developer.android.com/google/gcm/gs.html#libs for details on adding the helper libraries for Google Cloud Messaging.
I'm new to Android Development and Eclipse and I'm going through the various tutorials.
When setting up Eclipse I installed Android 2.3.3 SDK Platform along with Google APIs for that platform.
When I create new projects for most all of the tutorial programs I select Android 2.3.3 as my target.
However, when going through the Google Map Views tutorial I am told to select Google APIs instead of Android 2.3.3 when creating the project. I did this and the map view program works just fine.
But this seems like a binary OR decision; I'm allowed to select one or the other. Does the Google APIs include all that's in the Android 2.3.3 platform? In other words could I just always select Google APIs target for the platform level that I want and it would work?
Thanks,
Dean
Yes, it would always work because the Google APIs is a superset of the Android SDK.
Google APIs Add-On is an extension to the Android SDK development environment that lets you develop applications for devices that include Google's set of custom applications, libraries, and services. A central feature of the add-on is the Maps external library, which lets you add powerful mapping capabilities to your Android application.
You shouldn't make use of it unless you need to. This will save the system the extra work required to load these unnecessary features at runtime.
Right now the Google API SDK is mostly used for the proprietary Google Maps API in it.
You only want to select this as your target when you require specific API's inside of it. If you don't use Maps in your app, you can usually leave it off. It does include everything that is in its accompanying Android SDK.
When you select this as your target, it makes it so only devices that are running a ROM with the Google API SDK can see your app on the market.
I'm porting my android app to playbook and keep getting an error related to not supporting Google Maps, however I don't use that anywhere in my project. It's also not mentioned anywhere in my manifest.
I'm at a loss here, not sure what to do next. Any ideas?
Just to update on this: I was able to compile and run the app on the emulator w/ that warning present so - lets see if it gets past approval process, will update.
The Google Maps API for Android is unsupported on the Blackberry Playbook. See https://bdsc.webapps.blackberry.com/android/apisupport/ for a list of what can and cannot be ported.
For now, there is no way around this. If you want to create a Google Maps application for the Playbook, you will need to use the AIR SDK with the Google Maps Flash API