![]() The “lp” in the file name stands for Lollypop, the code name for Android 5.ĭrag the gapps package and drop it on your Android VM. I downloaded one named gapps-lp-20150314.zip. The file sets available from TeamAndroid should install without any problems. They all reported an invalid folder error message. None of their packages would install into my VMs. I was hoping to to use the packages on the Open Gapps project. There are a few places where you can download a package from, but not all of them may work. Since we have Android 5.1, we need a GApps package for Android 5.1. Multiple web sites have a copy of this file. If it didn’t reboot the VM, reboot it to be safe. Dialog that appears after drag and drop the ARM Translator package onto the Android VM zip on to a running Android VM and follow the prompts. The ARM translator lets ARM code run on an x86 image. The Google Play Services are usually packed up already compiled for ARM. The VS Android Emulator gets its speed by running an x86 version of Android. While we are checking stuff with ADB, the following command will return the SDK version adb shell getprop ro. Results from the ADB commandsįirst up is the installation of an ARM translator. If you were working with VM and were not sure of the version, you can check via the Android Settings app or from the command line with the adb command. SInce we created the VM, we know it’s Android 5.1. adb shell getprop ro.Īlso see the documentation for the Build class. Thanks to a tip from the nutty people at Intel, you can execute an ADB command to see what is on board. If you are using an existing VM, you’ll need to know which CPU architecture or ABI that the VM is running under. I tried this with Android 6 and it did not work with the GApps packages that I was able to obtain. For this example, we’ll create an Android 5.1 VM. If you run it from VS, you may not be able to install firmware packages. Run the Visual Studio Emulator for Android from the Start Menu. They are commonly packaged under the name “GApps”. Enough developers have put together versions of the package so that it’s a fairly easy process to install. Google does not allow Microsoft/Genymotion/Xamarin to include the Google Play Services with their builds from the AOSP. On top of that, the OEMs add any customizations that they do to Android. Device OEMS (Samsung, Huawei, LG, etc) then license the Google Play Services from Google. The typical Android device starts with a base Android stack that comes from the Android Open Source Project (AOSP). And the Google Play Services are not included in the virtual machine (VM) images that the Visual Studio Android Emulator uses. The reason for this is that GCM is part of the Google Play Services. Out of the box, the Visual Studio Android Emulator (and the Genymotion emulator, and the Xamarin Android Player) does not support Google Cloud Messaging (GCM) push notifications. Adding Google Play Services to Visual Studio Android Emulator ![]()
0 Comments
Leave a Reply. |