Package Details: android-emulator 31.3.13-1

Git Clone URL: (read-only, click to copy)
Package Base: android-emulator
Description: Google Android Emulator
Upstream URL:
Keywords: android development
Licenses: custom
Submitter: dreamingincode
Maintainer: dreamingincode
Last Packager: dreamingincode
Votes: 51
Popularity: 0.104866
First Submitted: 2017-04-19 07:06 (UTC)
Last Updated: 2022-10-31 20:18 (UTC)

Latest Comments

1 2 3 Next › Last »

arturbruno17 commented on 2022-06-17 12:43 (UTC)

I don't know if this is just me, but when I access the Android Emulator's 'Extended controls', the map doesn't show up for me. In the place where the map should be to select the location of the fake gps, there is nothing.

ulidtko commented on 2021-12-23 12:09 (UTC)

Ah, nevermind... Upgrading android-sdk-platform-tools 30.0.1-131.0.3-1 fixed it.

ulidtko commented on 2021-12-10 16:30 (UTC)

Hi @dreamingincode... Hope you're well. I pulled an update here recently, and it started failing to run like this:

$ emulator -avd myimg
[140373027645248]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '/home/ulidtko/../emulator/qemu/linux-x86_64/qemu-system-x86_64': No such file or directory

However, this works:

$ ( cd /opt/android-sdk/emulator/; ./emulator -avd myimg; )

Can this be helped? I can try to whip up some wrapper launcher script and send it as a patch, if that's OK with you.

Additionally, I somehow have 2 different emulator binaries:

$ ls -lh /opt/android-sdk/{tools,emulator}/emulator
Permissions Size User Date Modified Name
.rwxr-xr-x   12M root  7 Dec  1:02  /opt/android-sdk/emulator/emulator
.rwxrwxr-x@ 625k root 24 Jun  2019  /opt/android-sdk/tools/emulator

— very different in size, but seem to function equivalently (even the CWD-dependence bug is the same). Is this expected? I've got android-sdk installed (from your AUR) too. Which one is best to use in a wrapper script? I want to be able to launch the emulator from any CWD.

dreamingincode commented on 2021-06-18 21:42 (UTC)

Re aquatic7: makepkg worked fine for me locally and I checked the checksums in PKGBUILD v.s. manually running sha1sum, both are correct. Maybe you did have a bad download?

aquatic7 commented on 2021-06-18 18:28 (UTC)

Building android-emulator... ==> Making package: android-emulator 30.6.5-1 (fre 18 jun 2021 20:26:33 CEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found -> Found -> Found android-emulator.csh -> Found package.xml ==> Validating source files with sha1sums... ... Passed ... FAILED android-emulator.csh ... Passed package.xml ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build android-emulator

mynacol commented on 2021-04-19 18:36 (UTC) (edited on 2021-04-19 18:36 (UTC) by mynacol)

Hi @Erz3,

Please follow the instructions on the Arch Wiki. As this is not an instructions or support channel I won't help you here. Please ask your questions on more suitable platforms.

Erz3 commented on 2021-04-18 23:26 (UTC)

Hi everyone.

I am not developer and I am not an exeperienced Linux user, so forgive me if my question is stupid.

I was looking for an Android emulator to run mobile games, but I have installed "android-emulator" and I don't know how to work with it.

Thanks in advance.

dreamingincode commented on 2021-03-31 04:31 (UTC)

emulator 30.6.1 is still in another channel (channel-3, seems to be canary chacnnel) as of writing. See . Please only flag this package out of date when there's an update on channel-0 (the stable channel).

thotypous commented on 2021-02-14 04:19 (UTC) (edited on 2021-02-14 04:20 (UTC) by thotypous)

android-emulator 30.3.5 crashes with SIGSEGV for me due to sysconf(_SC_LEVEL1_ICACHE_LINESIZE) returning -1, whereas qemu expects it to return 0 in case of failure. This is actually fixed in latest qemu, but android-emulator 30.3.5 comes with outdated qemu.

To fix the issue, one needs to patch the /opt/android-sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64 binary and modify bytes starting at offset 0x4e5641 to bb 40 00 00 00 89 d8 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90.

This is equivalent to inserting the following instructions (followed by a bunch of nops) in place of the calls to sysconf.

8e5641     mov         ebx, 40h
8e5646     mov         eax, ebx