I have a nice PC Desktop that I run all my development applications, Visual Studio, SQL Server instance running, Eclipse, Spring Eclipse etc... everything is fairly fast.
But when I run a simple, little, empty android hello world app, it takes literally 3 or more minutes for the Android get started!!! I don't believe I am the only one experiencing that? I don't want to run in the device every single time... usually it is handy run in the emulator just like I do with XCode to IPhone simulator...
any experience with that? solution tips?
thanks
You can use android-x86 (helpful post). x86 port works faster than emulator, but I recommend use a real device to avoid emulator-specific problems.
The Android emulators, especially the older ones, are notoriously slow. This is because they not only have to run an OS in an OS, but they must also emulate an ARM processor Architecture, on a x86 or x64 processor. This makes them rather slow.
However, you do get Intel images for ICS, which are built for x86 and run faster. You could also try using the older emulators. They got progressively slower upto honeycomb. You could also try increasing the emulator RAM and get a minor speed boost.
Other than that, you could leave the emulator running once started, as then it's much faster to test your apps, since you don't need to start it up everytime.
However, I would personally recommend testing on a device, as you will never get the same quality and accuracy in debugging on an emulator.
There is an Android emulator called Bluestacks that you can use for apps as well. It is less for development and more for playing Android games on your PC, but if you don't mind testing your app in a non-standard launcher environment then it is super fast.
You can even use it for debugging and access DDMS from Eclipse as well by following these steps:
Open Bluestacks
In your 'platform-tools' folder in command prompt, type "adb connect 127.0.0.1"
Try to run your app or debug from Eclipse and you should see a new device listed for Bluestacks.
It doesn't have the same type of hardware/environment emulation that the normal emulator does, so it will not be appropriate for testing all apps, but I use it whenever I can because the normal emulator is such a headache.
So far, there is no solution for that...I have to buy a nexus to run my apps to make the development viable
Related
I've tried 3 virtual devices and when I run any of them a white screen is opened without anything inside .
and i think that the VirualBox problem is the reason
here are my computer properties
I've already answered similar issue: Ubuntu Linux 32bit - not a Genymotion virtual device
Genymotion already does not support 32-bit computers, so I suppose that you're running older version or you're trying to run 64-bit version on 32-bit.
With 2GB RAM and 32-bit machine I would have forgotten about any emulator - Genymotion, Android SDK emulator and others.
Look, building small sample application in Android Studio may freeze your computer as it takes more than 1GB RAM and you want to run also an emulator which takes also more then 1GB RAM and I suppose also web browser (Chrome) and other software.
If you really need to work on this pretty weak computer, I suggest you to buy a low-end Android devices and forget about emulator.
It would be good also changing Windows operational system, which seems to me a bit heavy to lite Linux operational system like Lubuntu or Elementary OS.
Hope it will help
Suppose I wanted to build a PC application but instead of that I'd make an Android app which does not access mobile only APIs. Can I run something like that on my PC? Do that by like running dalvik vm on a pc and then running the app in that?
Is there another way to run an app on PC apart from using an emulator?
No there is no direct way of doing that. The only ways of doing it are by using an emulator like for example the one included in the Android SDK (Android Studio) or Bluestacks.
EDIT: But there is no way to run android apps without an emulator unless you want to write the dalvik vm for every cpu architecture yourself!
EDIT2: Quoting #XavierFalempin from the comments section:
There was also ARC welder on chrome to run some android apps. developer.chrome.com/apps/getstarted_arc
On Linux yes: https://anbox.io/
I checked win,mac support - there is no support and there is not plans for that.
But running Ubuntu in VirtualBox is not a problem :)
In order to run android apps on pc without any emulator you will need to install any Android based OS on your PC which will remove the emulation part and just run the apps directly on the PC and as a result you will get better performance. I would suggest you to try Prime OS as the development for this OS is going pretty well and you can post your query on their forums in order to get your issues resolved asap. They have 3 separate variants for old, newer and newest chipsets which makes it compatible with most of the systems. You can download it from here : https://www.primeos.in/download
Is there anyway to run Android virtual devices through Eclipse while operating with AMD processor? I had Genymotion for a while and despite it worked, it was too much of a kerfuffle to dabble with it.
For AMD processor, create a new Virtual Device and while selecting the system Image select the ABI as armeabi instead of the default x86 one.
You don't need an Intel processor to run the emulator, it's just so much faster with the HAXM technology which obviously is not available to you. I recommend buying a cheap Android device for testing, as none of the emulations provided with the ADK are particularly fast.
With developer mode enabled on your Android device, you'll find the debugging and all other useful features that Eclipse provides work very well (but note that developer features are now quite hidden: http://www.theandroidsoul.com/android-4-2-developer-mode-is-a-tricky-thing-heres-how-its-done/ ).
Use Genymotion insted of default one. It is way faster than the default one. And yaa the emulator is compatible with both Intel and AMD. Genymotion just uses Virtualbox to run Android in VM.
Genymotion Home Page
I have this assignment to run a "hello world" Android app.
The problem is the Android app emulator is stuck on the Android loading screen.
I have searched this problem. They said that Android development needs a faster computer to execute apps neatly.
Is there a way to run it on a netbook?
For example, editing the RAM settings and/or SD card settings so that it can run faster?
Realistically I think your best bet is to try and find a used android phone. You can get them VERY cheaply on Amazon or at other retailers.
If you really can't you can try to muck around with the emulator, but even when it's at it's best the Emulator is a miserable way to do development. You can barely get it running as it is - imagine what happens if you do figure some hacky way to get it running and you try to do anything substantial. It will be a nightmare.
I would also look into upgrading your computer if you are really going to do dev work. A machine that can't run the emulator is a machine that probably can't do most of what you're going to be needing to do. Have you tried your schools computer lab?
Also - as a commentor has stated this question is likely off topic for stack overflow.
Edit: Per Chris Strattons Comment:
You might try disabling various things in your IDE (I'm assuming you're using eclipse) - for example Syntax checking. I would also recommened ensuring that you don't have a web browser, antivirus or other software running in the background which might eat up your computing power. If you're going to run the emulator I would strongly recommend making it the ONLY thing you run.
You may want to look into building and running the application from the command line to avoid the overhead of running and IDE at all:
Please see:
Building from the command line:
http://developer.android.com/tools/building/building-cmdline.html
Running the emulator from the command line:
How do I launch the Android emulator from the command line?
Additionally - is your netbook running Windows or Linux? Windows boxes tend to have higher overhead than Linux machines, so you might try installing a lightweight Linux distro (mint perhaps) and seeing if that helps.
If the problem is getting the emulator to start or your emulator is just too slow, you should look into HAXM:
http://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
Pretty much all of my emulators are running the x86 image with HAXM for acceleration, and my dev machine has 16GB of RAM. Using ARM images for your emulators is just too slow, especially for your netbook.
Yes, if you are serious about Android Dev (or any Dev really) you need to get something better than a netbook, but for now, see if a little hardware acceleration will do in a pinch.
So I downloaded the ADT bundle at the android website. I tried making a simple project, the one with HelloWord program. I already added an AVD and tried to run my application. At first, I got stuck at
"Waiting for HOME ('android :process:acore') to be launched"
but after searching the net, I learned that I must right click my project and click run as Android Application and then it was able to proceed with the next lnes in the console.
But after some lines, it gets stuck at the line in the console saying
"Starting activity.com.example.myfirstapp.MainActivity on device emulator:5554"
it's been an hour since that line and nothing has happened in the AVD. I tried using 2 ADT bundles, one for my 32-bit computer and one for my 64-bit computer. Both get stuck at the same line. How do I solve this? I've been working with this issue the whole day. Just when I thought it would be a simple installation.
Launch your emulator from Android Virtual Device(AVD) Manager and run your application
One thing that can really stick your program is a virtual device that is eating up too many resources. Try lowering the amount of RAM your virtual device has. Also be sure you have the latest JDK/JRE installed.
Just picked this book up:
http://www.amazon.com/Android-Development-From-Eclipse-ebook/dp/B00EEI5NHO/
Decently well written an very easy to follow. Walks through building an app in decent detail.
Actually the AVD works very slow on normal configuration systems, it requires a very high config PC to run smooth, you have to wait for sometime to continue with AVD, it will start don't worry. But I would recommend you to run and test your apps on a real android device using the USB debugging feature.