High CPU usage with Android emulator (qemu-system-i386.exe) - windows

The emulator qemu-system-i386.exe cpu usage almost constantly running between 7~9
Android studio 2.1
Android SDK Tools: 25.1.3
Host Operating System: Windows 7 - i7 2630QM - 8GB Ram
Intel x86 Atom System Image installed
No matter what setting i change in the emulator like: emulated performance, multi-core CPU, x86-64 image, always the same thing
It is really annoying fan always on
Anyone had a fix for this issue?

The cause of the constant CPU usage could be the sound. If you do not need sound in your emulator you can disable it by editing the AVD's config file.
Change/add those two lines
hw.audioInput=no
hw.audioOutput=no
Update: As buncis commented you can also try to disable GPS if not needed:
hw.GPS = no
On Linux/Mac the file is located at ~/.android/avd/<AVD_Name>.avd/config.ini
On Windows the file is located at C:\Users\<username>\.android\avd\<AVD_Name>.avd\config.ini

On Mac I noticed that the emulator was using over 100% CPU after my laptop went to sleep. Turning the audio off as Benjamin suggested didn't fix that problem.
Restarting the simulated device by long-pressing the power button on the emulator works for me.

Using the x86_64 (Or the 64 bit) emulator solved it for me. They recommend the x86 version, but it was acting up for me.

To find out what on the virtual device is using the most CPU:
adb shell
$ top
This will show you a list of processes with the highest CPU usage atop.
This will help you determine whether it's a process (such as your app) inside the emulator, another process inside the emulator, or just the emulation itself using a lot of CPU.
In the latter case, try optimizing the emulator by installing HAX (Native intel instructions) or perhaps enable hardware acceleration using the AVD profile editor.

I had that problem on the start of November 2018.
Virtual device was contently trying to connect to the mobile network data, so I turned it off inside of the device itself.
Work great now.

The same problem with qemu on Win7, HAXM 7.2.0. I've tried switch off audio, it didn't help, qemu consumes about 20% of CPU anytime, Android works very slow on both x86 and x64 images.
I've found solutions in HAXM's Release Notes file:
On Windows, Avast Antivirus may interfere with HAXM and cause Android Emulator or QEMU to run very slowly. A workaround is to uncheck "Use nested virtualization where available" in Avast Settings > Troubleshooting.
I have Avast Pro Antivirus 18.5. I've unchecked this param, rebooted PC and now qemu consumes 0% in idle, Android works fine.
UPDATE: if QEMU started consume CPU again, first check Avast's update status. After background update Avast may start to interfere to HAXM again. Just reboot Windows to solve it.

In my case using hardware graphic solved my problem.

my case, coz I choose software for graphics rendering in adv. so after a change to the hardware reduce CPU usage from 60 to 10, and CPU temp from 70 to 40.

I am on macOS Catalina(Version 10.15.2) with Intel Core i9 and 16 GB RAM and Radeon Pro 560X 4GB Graphics.
I solved high CPU usage by qemu by restarting the emulated device using the emulated power button.
Also, while creating the AVD, I chose Hardware Graphics Renderer instead of Auto.

Using kind of old Android version I used Lollipop Galaxy Nexus API 22 dropped CPU usage from 220% to around 30% ! ...
I also switched: Emulated Performance > Graphics > Hardware
Using Android Api 25 ... Hardware for graphics and turning off AVD audio and GPS didn't work for me...
Platform: MacOS

I reduced the CPU usage of my emulator by setting the framerate of the monitor to 60hz. It was on 144hz and my CPU was running at 60% - 70%. By only changing the framerate of the monitor, it's now sitting at 3% usage.

I wasn't able to shut the audio off with the config.ini file, but only with the -noaudio cmd line argument to qemu. However, with Android Studio 3.2, you can't add custom arguments to the emulator, so I made this:
In the emulator dir of the Android SDK, in my case ~/Android/Sdk/emulator/
mv emulator emulator.orig
Make a bash script called emulator with the content:
#!/bin/bash
DIR=`dirname "$0"`
$DIR/emulator.orig -noaudio $*
Then:
chmod +x emulator
Now, the argument -noaudio will be added to all invocations of emulator from Android Studio and will save you a lot of CPU cycles.

I solved it by cancelling "Auto-save current state to Quickboot"
Snapshots -> Settings -> Auto-save current state to Quickboot - NO

I had the same issue recently on Windows 10 (18363): the AVD used all of the host's 16 Threads at 100%, it seems the android.hardware.graphics.composer#2.1-service process on the AVD was to blame.
What helped in my case: going to AVD settings - Advanced - change the OpenGL ES renderer to Desktop native OpenGL and restart the AVD. Now it uses like 2-3% of my CPU resources. Hope this helps someone.

Update:
I have installed Genymotion plugin at genymotion.com/plugins, and it has an amazing performance

In my case, I only encountered this issue when running multiple instances of the emulator.
Re-run the Intel Hardware Accelerated Execution Manager (HAXM) installer provided in the Android SDK (<Android SDK path>\extras\intel\Hardware_Accelerated_Execution_Manager\intelhaxm-android.exe), select Change, and see how much memory is allocated to HAXM. If it's 2 GB or less, you probably want to raise it to at least 4 GB. Then restart your emulator and see if the CPU usage drops.

Disable location in settings and also disable touch sounds.

In my case it was the fast boot that was causing the problem, to force into normal boot open the text file in C:\Users\<username>\.android\avd\<AVD name>\config.ini and change at least one of the values.
for example change the line
hw.battery=yes
to
hw.battery=no

In my case it was Airplane mode, when turned ON the CPU usage jumped to 99%:
adb shell
$ top
The issue was noticed on Android 10.0 x86.
If you turn Airplane Mode OFF then the CPU usage should return to normal.

Changing the resolution worked form me. I was using 1440 x 2560 560 dpi Oreo 8.1. Now im using M-DPI Oreo 8.1

For me I turned WIFI off and I dropped from 112% usage to 10%. I would recommend doing this

Just do
$adb shell
$top
Look the PID which high CPU
$kill -9 <PID>

on api31&32: do EDIT each AVD config with Show Advanced Settings and be sure to:
Multi-Core CPU > max (<=> hw.cpu.ncore=8,
4/cores is not enough and may overheat cpu strongly)
Graphics > Hardware (GLES 2.0)
No-SDCard (<=> hw.sdCard=no)

Related

Android Studio and Emulator not responding

I have an Acer Aspire E5-573 laptop with 4Gb RAM, Windows-10 64 bit operating system. Whenever I start my Android Studio, my laptop stops responding, and I am my program does not run on the emulator. What do you think would be the problem?
You have to increase your RAM atleast 8gb,
alternative way:
Use lower version of android studio because version 4.0 and up has many features like animations etc. don't use AVD Android Virtual Device instead try to use Physical phone as emulator
Its mainly happen when your computers memory (RAM) run out, when there is no sufficient memory(RAM) space left to run your program than your laptop is not responding.
Possible solution
Increase your RAM (memory) to minimum 8 GB and
Include a SSD storage in your laptop

Is there a min amount of ram to run create react app?

I find when I run create react app on my laptop then begin to code in VSCODE my laptop heats up a lot more than usual to the point its burning to the touch.
I have a macbook pro 2018 macos mojave fully upto date i5 8gb ram.
Is the reason for this low ram of 8gb?
Any information would be amazing.
Thanks
Nav
Not sure what to try?
npx create-react-app
Not expecting laptop to get unusually hot. Only happens when running create react app. also sometimes happens when running Atom IDE but does anyone even use that anymore?
No, the amount of ram you have should be more than sufficient to to VSCode and a create-react-app. Ram also has little impact on heat so I don't think that is causing the issue.
What you could try is to open the activity monitor to check if any processes are using more CPU than they should. Also check under the Energy-tab, that could give you a good guidance to what is causing your heating problem. As an example, I've had problems before where some of my VSCode plugins have had a bug that causes them to run at 100% CPU constantly.

Android Emulator is very slow only if Android Studio is opened

Actually in this case all system is quite slow but the emulator is extremely slow.
Hardware acceleration is enabled, emulator works just fine if I close Android Studio.
The OS is Ubuntu 18.04
Any ideas how to fix this?
P.S. I did read all recommendations regarding emulator performance and it works fine until I start Android Studio.
Go to Tools > AVD Manager > Edit a specific Device > show Advanced Settings >
1. reduce RAM
2. Make sure your using Quick Boot
3. Enable Multi-Core CPU
For me it was completely different I was getting some data from a node server which I forgot to start. The php was delivering the date so could not see the problem on UI. Just started the node server and it was fixed.
Check all server side starts.
In my case (Ubuntu 20.04, Nvidia GPU) it was hardware rendering not being auto-enabled, so I had to manually enable. After that the emulator was very smooth.
Device Manager > find your device > Edit > Emulated Performance / Graphics > Hardware - GLES 2.0

Got Android Studio installation error

I am kinda new to Android Studio & stuff. So today, I was installing the Android Studio with the SDK Manager. All was going smooth until an error came up which says:
Unable to install Intel HAXM
Your CPU does not support required features (VT-x or SVM).
Unfortunately, your computer does not support hardware accelerated virtualization.
Here are some of your options:
Use a physical device for testing
Develop on a Windows/OSX computer with an Intel processor that
supports VT-x and NX
Develop on a Linux computer that supports VT-x or SVM
Use an Android Virtual Device based on an ARM system image (This
is 10x slower than hardware accelerated virtualization)
I've attached a pic of my system specs. Can someone please throw some light on this issue?
Thanks
It is because you had not intialize virtual technology in your device.You Need to go in BOOT Option before starting WINDOWS OS and enable VT-x from there>
The option of enabling Virtual technology is putted in different option depends on device manufacturer
Edit: Android Studio emulator won't run on Windows with an AMD processor. The error message is kind of misleading, as it suggests the problem is with your CPU. But it is within the troubleshoot message: "Windows/OSX computer with an Intel processor". Basicallly, that means it is not going to work properly in your current setup. Either try installing Linux and running Android Studio on that (which might come with its own issues), using a physical device for testing or use the slow ARM images.
You are using an AMD processor. SVM is AMD technology and VT-x is Intel technology. So you won't be able to get VT-x to run, but SVM might be possible.
As another poster had suggested, virtualization may have been disabled in the BIOS. There may be an option to enable virtualization. It does however seem to happen that virtualization is activated in the BIOS and Android-Studio does not recognize that. I have not figured out how to fix that either.
You could use the emulator with an ARM image, which will be very slow. Alternatively, you could use another emulator that is not integrated into Android-Studio.

Android Emulator tried with RAM Sizes

Please help me.
I have installed Andoird in my 16GB Ram, I5 Processor laptop.
Everything went well but Emulator is never starting.
I tried with different RAM sizes like 1536,950,512,700,600,800,1100,450,1450.
None worked.I am using CPU/ABI in X86_64, a shown below. Can you please suggest me something.
AVD setup
Thanks
"I have installed Andoird", sounds like you want to use emulator for some other use than for development, if so than Android Emulator isn't that good as it is. If you're using it for development usage, then try to update the system images for API level 23
- the emulator may take upto 10 (or more) minutes to start
-confirm that emulator is running in Task manager,
also , API level 23 is quite new so It may contain bugs that are not known.

Resources