I'm building a sandbox for testing Android applications and I need to isolate the emulator from the sdk as I wish to reduce the size of the tool as much as possible. I've been searching around for a stand-alone version of the emulator which can be put pre-configured and run without sdk. The important part is that I need adb to work mandatorily.
Where can I find a stand-alone Android emulator (even better if headless) ? Is there any other solution to this ?
Related
I know that Android studio comes with an Emulator for testing apps. but this Emulator is too damn slow and never runs on my machine.
so i was checking for alternatives like if at all there is a standalone emulator which i can install on my system and upload my APKs and test. It is good if this emulator tool kit also shows the logs.
I just want something to test my Apps without the Emulator that comes with Android SDK.
While i was browsing SO i bumped into this here check for the comment that Paul Ratazzi has written, (second comment) this one is a paid solution so i did not dig into it much.
Genymotion is free for individuals. So you can use it unless its commercials and better than Emulators.
I recently built an android application that i need to run 24/24 7/7.
I thought about using web servers, so I bought KVM VPS WITH 2GB RAM AND 2 CPU CORES (Ubuntu). I tried to install Genymotion on it but it doesn't work, so I tried to use the androidx86 version on virtualbox and it works but it is very slow.
Now i am asking if there is a way to run an android application 24/24 on a server ?
In order to run an Android application on your computer and have it be fast, you'll need to use the x86_64 or x86 images. Using an ARM or MIPS based image requires overhead since native instructions can't be run on an x86 computer. Genymotion is good, but I find the new Android Emulator is really fast, and it's free.
I would check out the new Android Emulator and use an x86/x86_64 based image. You can customize your image to provide extra disk space and RAM allocation to the system image for better performance. I've had great luck getting it to run quickly and smoothly in recent builds.
Here is blog post and video from Google announcing the new and improved emulator at Android Dev Summit in December of 2015: http://android-developers.blogspot.com/2015/12/android-studio-20-preview-android.html
Note: Please make sure you have the most up to date Android SDK for best performance and to make sure you have the version they talk about in the link.
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 have a Red Hat Linux (RHL) system on which I'd like to run Android apps. How would I do this? Is there an open-source port of the Android Runtime for linux? Kind of like a VM?
If not, what steps will I need to follow to port the runtime to RHL (with the Dalvik VM etc) so that I can run the android apps built by all android developers?
I am new to android so I am trying to understand if there is an application virtualization support for it from anyone. Thanks in advance!
You need to use dex2jar to convert an APK file to a JAR and then you need IcedRobot to run the Android stack above OpenJDK. Maybe I will try to emulate AndroidGL with JOGL 2.0 (it supports both OpenGL and OpenGL-ES). Keep in mind that it is not trivial.
The emulator of Android SDK is quite slow but you just have to enter adb install my_file.apk to install your application.
You can run android-x86 in VirtualBox or Live Android from a Live CD as Dimitri suggested but I'm not sure it is what you want.
P.S: The most promising solution seemed to be AndroVM.
P.S 2: ARChon Runtime works very well on 64-bits systems. This tutorial is very helpful to make it work.
P.S 3: App Runtime for Chrome Welder is even more promising, it's currently in beta. The final version will support all Android APIs in Google Chrome under GNU Linux (including Chrome OS), Mac OS X and Windows.
I know there is a project for porting Android on x86 platform. You can find iso to download and you can install on LiveCD : http://code.google.com/p/live-android/. You can find more information here
You can't just run Android apps - you will need the entire underlying Android operating system. That goes beyond a simple JVM. EDIT: There is actually a project in the works that aims to do that, see Dimitri's link.
But you're in luck - the Android SDK comes with an emulator that should fulfill your needs (although it's a bit on the slow side - if you're developing Android apps, you definitely want to use a physical device instead). The SDK is available here.
Run Bluestacks on Windows on VMWare on Linux. Easy.
I know I could use my Desire Z as a test phone, but what if I want to develop for 3.0 Honeycomb? What's an alternative for the emulator since it's so slow?
http://www.bluestacks.com/
This site has been getting some press recently. It seems that they are going to launch a windows runnable version of android later this year. This will be another alternative to using devices or emulators for testing I would imagine.
A general solution to the slowness of processor-emulation based emulators is to run a build of the embedded environment compiled for the same processor and general architecture as the hosting machine, in virtual machine software which can run most of the code native, and only has to trap and emulate privileged/hardware-related actions.
In other words, you run the x86 build of android in VirtualBox, vmware, or whatever, and dispense with the overhead of emulating an arm processor.
In quick web searching I'm not getting a confident answer if there's a working build of Honeycomb for x86 yet, but presumably there will be a build of that or a later android version at some point.
The only alternative is to have a physical device with Android 3.0 imaged on it.
Try this one for a change it actually provides an eclipse plugin and it uses cloud i guess it is faster than the emulator comes with android by default http://www.genymotion.com/features/