I've created simulator for S4 as described in https://stackoverflow.com/a/16646536/206809.
My PC configuration is Core i5 2.5 GHz and 8GB RAM 64Bit Windows 8 still I'm unable to load the emulator. Are you able to run the same ? Please suggest if I'll require higher config. Attached my Emulator Config for reference
When I'm running same it stuck in this screen for a long and then time out.
tick "Use Host GPU" and try. Some times it may work.
Not sure.
Try this one:
I have opened successfully s4 emulator and it's working fine. I think you should reduce size of RAM, Internal storage, and sdcard of emulator according to your computer RAM example I have 4 GB ram in my pc and I have changed according to it like :
RAM : 512,
Internal Storage : 128,
Sdcard : 256.
and
also reduce screen size of your emulator(in my case I have used 5) should be 5 to 7. More Screen size of emulator takes more time to open.
so according to my knowledge size should be your issue.
hope it will help you.
Emulators have been driving me crazy for long time because they are so slow. I had no problems
using emulators on android 2.3, 2.2 etc. It takes for ever to load an emulator for android 4.0 and above and most for the time it won't even load. The high resolution you try to you use, the less chance for emulator to start.
I run my emulators on windows 7. Anyway, after a long search, i came a cross this link. http://developer.android.com/tools/devices/emulator.html.
Thanks to intel VM Acceleration for windows. Emulators runs on my laptop in seconds. Its not perfect yet but it does the job. I thought i'd share this, because i wished i knew about it long time ago.
Note: CPU must support one of the following virtualization extensions technologies:
Intel Virtualization Technology (VT, VT-x, vmx) extensions
AMD Virtualization (AMD-V, SVM) extensions (only supported for Linux)
and if it does support VT, remember to enable VT .
Related
When I run Genymotion and want to start a relatively new device it freezes with a strange screen but with older devices like android 5 or 7 I don't have such problem.
I updated Genymotion version, edited my devices to lower memory size and processor core number but it made no change. It doesn't stuck in booting like so many others that have problem and its status is "On".
I use:
-windows 10, Genymotion V3.1.1.
-GPU nvidia geforce GT550M 2GB
-CPU intel core i5
-display driver is updated
This is what I see in this device:
These files are genymotion log: Download Link
This is typically an issue with the GPU and/or display driver. Does your GPU meet Genymotion requirements? Is your display driver up to date?
Also, if you use a laptop with dual GPUs, make sure to read this article: https://support.genymotion.com/hc/en-us/articles/360002732678-Virtual-device-display-is-black-Genymotion-Desktop-
UPDATE:
I can see the following in the logs: Running on a Intel(R) HD Graphics 3000 from Intel It means that Genymotion is not using your discrete NVidia GPU but your low-end Intel iGP which is too low to support Android 8 and above rendering. You need to force Genymotion player (player.exe) to use your NVidia GPU instead.
See https://gpu.userbenchmark.com/Faq/How-to-force-Optimus-or-Switchable-discrete-GPUs/97
At the moment I'm developing an application with Android wear support but I have no smartwatch. Now I want to test my application on an emulator but that is the problem. The emulator need up to 1.5 hours to start. I created one with following settings:
<!-- language: lang-none -->
Target Google APIs (Google Inc.) API lev 22
CPU/ABI Google APIs Intel Atom (x86)
Device 5.1" WVGA (480x800: mdpi)
Skin No Skin
RAM 512 //also tried with 768
VM Heap 32
Internal Storage 200
Use Host GPU true //also tried with false
I installed HAXM, enabled it in the BIOS settings and if run
sc query intelhaxm
I get the status 4 like it is written here. I set the HAXM memmory to 2GB so it should be enought. I also do not run any other VM software and I have even reinstalled my Windows. The only interesting information from the LogCat is that there are many lines (up to 70%) of Suspending all threads
My computer has the following Hardware:
<!-- language: lang-none -->
Windows 7 x64
Intel Core 2 Quad Q6600
8GB RAM
Do you have any ideas why my emulator is so slow?
EDIT: Here I posted the target for a smartphone device but it's also so slow for wearable devices so Genymotion is no real alternative because it has no images for them.
Well dont know for sure but all the native emulator in android are very slow.
I suggest that you use the Genymotion which is very faster emulators for android than native.
It will give you user experience almost as of devices though it does have the same limitation of android native emulators.
Toggle your ScreenSize and Monitor dpi to get a lower scale - it will increase your speed of loading and usage.. SnapShot can also be Handy
There are several options:
One option is the Visual Studio Emulator for Android--it's fast, Hyper-V, x86, and free when you install Visual Studio 2015 (currently in Preview; free download).
Reference: Source
Run Android Image in VirtualBox.
http://www.android-x86.org/download
You can use the Intel x86 System images, I'm not sure but they might be faster
Note: I read somewhere that Anti Virus Softwares scan the Image of Emulator which make it slow. I need to confirm it.
One thing i figured out about a slow AndroidX86 in a VirtualBox...maybe it help you.
I have an older system. A Board with a P45Express chipset and only a dual core [E8400].
I have two 1 Gig LAN Ports on my Asus P5Q Deluxe Board [iam connected cia cable to my router]. One is working through the Northbrigde, the othe one works over a PCIe Lane. Since i use the PCIe Port, my AndroidX86 runs alot faster.
Before, when i used the NB supported port, it took me minutes to get a stable connection to the www. It looks like that the VM slows down hard, if the www connection is not supported by a good mainboard connection.
I dont use 3D accleration,i use VBoxSVGA and only PAE/NX and "Nested Paging".
Maybe that can help you abit.
Sorry for my bad english :/
1.Make sure you are using 64-bit operating system.
2.Use host GPU while starting Emulator.
3.Update you graphic drivers if u have graphic card
If you want to make the Android emulator faster and more responsive, you can configure it to take advantage of hardware acceleration. View this link for more details.
Configuring Graphics Acceleration
Try this configuration:
CPU/ABI: Intel Atom (x86);
Device: Nexus 5;
Keyboard: Hardware Keyborard present;
Skin: Skin with dynamic hardware controls;
Ram: 2048;
VM Heap: 64;
Internal storage: 200 MB;
SD Card: 500 MB;
Emulation Options: Use Host GPU;
You have not described which IDE you are using for development. I use Eclipse and with this configuration the emulator go up very fast. Maybe if this won't fix your problem try to use Android studio and the relative emulator which should be better (with the same configuration.
I was experiencing the same issue and almost give up on learning android until I found Genymotion. It is highly recommended.
One cause can be old HAXM driver:
Update here:
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
Mine was very slow with 6.0.1 but fast with 6.1.1
Because the emulator was really slow I installed the intel x86 emulator. I changed the settings in my emulator (ARM to intel atom). Now when I run a project it takes me to the emulator selection screen and when I select it, the project starts running, but the emulator doesn't pop up.
I tried switching the cpu back to ARM, but it still doesn't work.
When I close Android studio it asks me if I want to disconnect from the project so I'm sure it is running.
I came across a few posts that said to give the device 768 ram, but that didn't work.
Anyone knows a solution?
I was facing the exact same issue, but for me reducing the device RAM to 768 did fix it. Therefore I'd suggest continuing to decrease the RAM values and trying to launch it.
How about to use Rock speed Emulator - Genymotion?
I know it sometimes take time to launch emulator and launch app in emulator too. But it depends on your configuration of your PC and settings you have done in Eclipse or Android Studio.
For example: You may have kept "Build Automatically" ON and it sometimes slow down running time.
My current rep is not high enough yet to comment on another answer, so I am adding a new "answer" to +1 Paresh Mayani's answer to use Genymotion. I only recently discovered it and found it to be much much faster than the emulator. Instead of emulation it runs an Android rom in a VM using VirtualBox. I've found that it runs full speed on my machine and is just as fast in debug mode as normal mode, which is impressive since even my Nexus 5 struggles when connected to a debugger.
In my case also x86 was creating problem, I installed Android 5.0.1 armeabi-v7a and have set 768MB as RAM size and it worked.
Try to check and run the emulator ie. store a snapshot for faster startup...
I have tried that by checking the button and works fine.
If you're using an AMD machine try using the "ARM EABI v7 system image". For an intel chip use the "APIs Intelx86 Atom system image". Also, try a different tablet from the Android Studio settings e.g(Nexus 6), as the API level might not be supported from in the Nexus5 VM. You will also have a little wait time for the android emulator, mine takes about 7mins
I've successfully installed the Intel AVM for Jelly Bean v4.1, and I can create and start an Intel x86 AVM. However it's just as slow as the ARM ones. Having wasted a lot of time on this, as far as I can see the Intel emulation is no faster at all than the ARM images.
I do have HAXM installed, and on starting the emulator a message appears suggesting it's running in "fast" mode, but it's certainly not fast!
Is this because my PC (Windows 7, Intel) is not compatible, or did I miss something? How do I check compatibility?
Quoting the documentation:
The software requires an Intel CPU with Virtualization Technology (VT) support
However, this is not necessarily enabled by default on every machine with a VT-capable CPU. Once again, quoting the documentation:
Virtualization extensions are typically enabled through your computer's BIOS and are frequently turned off by default. Check the documentation for your system's motherboard to find out how to enable virtualization extensions.
So, for example, on a Dell Latitude E6400 sitting to my right, there is a BIOS option for "Enable Intel Virtualization Technology" that you have to check.
Checking the 'use host GPU' option in AVD properties seems to make it a bit faster for me (still slow but usable).
In Eclipse: Window > android Virtual Device Manager > Choose your device > Edit > 'use host GPU' checkbox at bottom.
NOTE: If you are using laptop with nvidia hybrid graphics (GeForce G210M in my case) make sure you have it on high performance before running the emulator. Otherwise Virtual device wont find the graphic card and will crash.
Also apart of "Virtualization Technology" I enabled something called "VTd support" in BIOS. I have no idea what it is or what it does (no description in my BIOS) but either of the above mentioned actions fixed the issue for me
I have the same issue. After making sure everything is properly configured:
(VT enabled in BIOS), Intel HAXM driver installed successfully, AVD details are as they should be.The emulator runs even slower than the ARM one.
If you still face the same problem as well. Star the issue here
Go into the AVD Manager (one of the little Android icons in the toolbar, hover to see which one) and on your AVD change the Memory Options: RAM to 768 MB. Hardware acceleration seems to fail if it's bigger.
(Also make sure "Use Host GPU" is ticked!)
(And also note the messages just below that. You might have to go into the SDK Manager and install an image.)
It still boots up slow, but once it's been running for a minute or two it should be faster. But it's still not as fast as a clean, native device, attached via USB.
In my case, I created and started several x86 emulators on an Linux server(cent os 7), and they all running slowly as hell.
The reason is, by default the emulators are set to have 2 cores, which is far less than the modern cell phones. So I changed the config.ini file in each emulator's directory, add one line hw.cpu.ncore=6(Depends on your major hardware, other properties may affect are hw.ramSize, vm.heapSize and so on. You can see all properties from hardware-qemu.ini in same directory.), and restart the emulators.
The emulators are running much more faster, not too much slower than real phones.
Hope my poor English expresses this clearly.
In my case i have a SSD Samsung 850 pro with software Samsung magician with rapid mode on that was the problem I put it off and android emulator run as a fash again.
I do not know what to do. I purchased a new laptop, hp pavillion i5 6GB RAM, started Android 3.2 emulator and it is still as slow as unusable!!!
It's not that it is slow, it's that I cannot do anything.
I set 1GB of RAM, disabled camera on emulator and run it. When I click on Applications, they first load for 30s and then I am not able to start any app, not mine, not default ones. All I can do is return to desktop and open Applications menu.
I see people complain that the emulator is slow and I am not even able to make it run. What is worse, my laptop eats games like a sandwich, but it chokes with Android emulator 3.2. The same is with Android 3.0 emulator!
Can anyone help me set up the emulator so that I can run it on my machine?
PS. if you want, I will record a video and post it to visually see what I am talking about.
I do not know what to do. I purchased a new laptop, hp pavillion i5 6GB RAM, started Android 3.2 emulator and it is still as slow as unusable!!!
The Android emulator uses a single core. If you had gone with a Core i7 with Turbo Boost, that would have helped. Your Core i5 is not an especially powerful CPU on a per-core basis.
The Android 3.x emulators also do all graphics purely in software (no hardware graphics acceleration) and convert ARM instructions to x86 on the fly.
Can anyone help me set up the emulator so that I can run it on my machine?
Start by using the Android 4.0 emulator, with the latest Android development tools. This uses your desktop's GPU for graphics rendering, and it helps performance a bit.
If that proves insufficient, you can start switching to x86 emulator images if you are not doing NDK development (where you will tend to want to test on ARM). At the moment, the only official x86 image is for 2.3.3, but there is an unofficial one for 4.0.3 built from the AOSP that runs exceptionally fast (at least on Linux, haven't tried it on Windows).
My only suggestion to you would be to change the "ADB Connection Timeout (ms)" in Eclipse under Window->Preferences->Android->DDMS. I am using a HP Pavillion 486 laptop, and was really struggling with the emulators. I changed the default timeout value from 5000 ms (5 sec) to 60000 ms (1 minute). This didn't solve all of my problems, but it did help in the startup of both the emulator and my applications.