Package Details: android-emulator 30.6.5-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: 49
Popularity: 0.80
First Submitted: 2017-04-19 07:06
Last Updated: 2021-05-15 20:13

Latest Comments

1 2 Next › Last »

mynacol commented on 2021-04-19 18:36

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

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

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

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

galaxy0419 commented on 2020-09-04 14:57

Upgrading to 30.0.26 still showing the version is 30.0.12

dreamingincode commented on 2020-05-09 20:15

I personally didn't see those warnings, and if this is not related to AUR packaging you might want to ask it somewhere else.

Regarding "-bin", I didn't see any official guideline/requirement saying that packages not built from source code must have that suffix. (See ), and currently none of all the Android SDK packages have that suffix. If people actually use Android SDK built from source, we might be able to move all the Android SDK packages into official repo. I'll be happy to rename this package for disambiguation in that case.

greyltc commented on 2020-05-09 14:58

When I run a virtual device with the emulator, it makes a bunch of complaints about Vulkan, for example Emulator: VK_VERSION_1_1 check failed: vkCmdSetDeviceMask not found

Is this missing some configuration to work with Arch's MESA/vulkan libs or something?

Also, shouldn't this package be changed to have a -bin suffix? Either that or it should be compiled here it seams.

mynacol commented on 2019-10-27 12:29

The file is "generated" or "placed there" by sdk-manager. If I install a fresh android-sdk with the sdk-manager, every component/package gets a package.xml and I simply copied it.

A strange effect: every other package (platform, platform-tools, build-tools etc.) has also a package.xml similar to the one for android-emulator, but those packages get noticed by android-studio without the package.xml file. The android-emulator is the only one (I know of) that requires the package.xml file to be noticed by android-studio.

To support android-studio, we have to include a package.xml file and keep it updated - the simplest way would be to download android-emulator with sdk-manager to get the newest package.xml and by the way the link to the android-emulator package. Changes to the given dependencies in a newer package.xml could be reflected by fittng "depends" clauses in the PKGBUILD.

dreamingincode commented on 2019-10-26 17:52

I replied to your email but your email server responded "The certificate is not valid according to the STS policy".

The file seems to include version and dependencies of the package, so simply including it won't work when the package is updated. Do you know where the file is from/generated?

mynacol commented on 2019-10-26 12:41

I created a patch which includes the missing package.xml and mailed it to the maintainer. I hope he sees the email after noticing this comment.