All geek questions in one place

Android emulator is terribly slow on Windows 7

This is not a saying, nor is it a duplicate forever "why such an Android emulator is so slow." So, until a few weeks (maybe months) ago, emulating Android devices on my 64-bit Win7 system was at least acceptable (x86 emulation was fast enough to be usable). However, an attempt to create any ("fast" "new" "2.0") emulator instances using the latest SDK, platform tools, etc. It is only a source of frustration and pain for several days. I'm trying to figure out if this could be a problem on my side, or can people actually use the latest version of the Android emulator included in the latest version of the SDK in Windows 7.

My PC config: Win7 x64 / Intel Core 2 Quad @ 3.8 GHz / 6 GB RAM / large hard drive space / dedicated GPU

What happens when you try to run the emulator with any API level with x86 or x86_64:

  • version 1) the emulator starts, the Android logo appears, it glows a bit and that it is. It never reaches the Home screen. There are absolutely no errors in the emulator log. Try connecting with adb freezes Android Studio until I kill the emulator process.

  • version 2) The same as version 1, but in this case I can’t even kill the qemu-system-i386 process (yes, even with full administrator rights). I have to restart Windows. The process remains a zombie using 1 GB of RAM.

  • version 3) If I'm lucky, sometimes it comes to the Home screen, but it becomes completely unusable. Sometimes I can click on things (maybe 2-3 clicks), and then it becomes completely immune. Sometimes random messages “Launcher stopped” / “System stopped” appear on the main screen of the emulator ...

I installed the latest Intel HAXM 6.0.3 (downloaded by the Android SDK manager). Virtualization is included in the BIOS.

I tried all kinds of emulator options (more or less RAM, GPU hardware and software, x86 / x86_64). Almost the same result every time.

I completely uninstalled and reinstalled the entire Android SDK and Android Studio.

The CPU is not a problem - it is not under load during the start of the emulator.

Free RAM is not a problem - it is not fully used during the start of the emulator,

- , .

, : - , Windows 7, , , Marshmallow x86 , ? ", " - , , , ? , , , , HAXM. , , . , VirtualBox . GenyMotion, , . , Android , ?

+4
2

, : , , . api 24 xxxhdpi - i7 8 .

, : , , . , . , ...

. i5 6 RAM . geforce gpu . , , , win7? : uninstalled ( 30) (! ..., , ++, Microsoft , - ripp'em! ++ - , ). , "", , , . Microsoft...

: Android ( ), , , .

-: "" apis, , android 4 5 . , 5 pol. 720 (), . , _x86 64.

. , . , : " gpu" . gpu.

, .

90% ( Android 5, 4.0 4.1 - 480x800), , dpi android 5, 6 N). , .

(?) , , . , . "" , , , , , .

, : i7, 8ram, gpu , : SSD ( 10 ), .:) .

EDIT: AVD- API- latests, Android Studio RAM , , , -. : . : Gb , . : , , . : 1 - avd, ram ; 2 - avd, , . OR/AND 3 - , .

+3

, ? nox android 4 daulcore processuer, , , Android-, sdk, , hi - haxm , sdk, , 8gb min i5 processuer min, , nox, android .... luk:)

0

Source: https://habr.com/ru/post/1648067/

More articles:


All Articles