Skip to content

Instantly share code, notes, and snippets.

@pwicherski
Created March 17, 2020 20:06
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save pwicherski/4ca90188b8d65c2eb99bcc47f7cc1317 to your computer and use it in GitHub Desktop.
Save pwicherski/4ca90188b8d65c2eb99bcc47f7cc1317 to your computer and use it in GitHub Desktop.
Android Emulator custom hardware profile
PlayStore: Does the device supports Google Play?
PlayStore.enabled [no]:
avd home that was used during the construction of this hardware.ini: This can be used by post processing tools to migrate snapshots
android.avd.home []:
sdk root that was used during the construction of this hardware.ini: This can be used by post processing tools to migrate snapshots
android.sdk.root []:
ID of the AVD being run:
avd.id [<build>]:
Name of the AVD being run:
avd.name [<build>]:
Cache partition support: Whether we use a /cache partition on the device.
disk.cachePartition [yes]:
Cache partition: Cache partition to use on the device. Ignored if disk.cachePartition is not 'yes'.
disk.cachePartition.path []:
Cache partition size:
disk.cachePartition.size [66MB]:
Initial data partition: If not empty, its content will be copied to the disk.dataPartition.path file at boot-time.
disk.dataPartition.initPath []:
Path to data partition file: Path to data partition file. Cannot be empty. Special value <temp> means using a temporary file. If disk.dataPartition.initPath is not empty, its content will be copied to the disk.dataPartition.path file at boot-time.
disk.dataPartition.path [<temp>]:
Ideal size of data partition:
disk.dataPartition.size [0]:
Path to encryption key partition file: Path to encryption key partition file. Should be at least 16K bytes empty disk without any filesystem on it.
disk.encryptionKeyPartition.path []:
Path to the ramdisk image: Path to the ramdisk image.
disk.ramdisk.path []:
Path to snapshot storage: Path to a 'snapshot storage' file, where all snapshots are stored.
disk.snapStorage.path []:
Initial system partition image:
disk.systemPartition.initPath []:
Path to runtime system partition image:
disk.systemPartition.path []:
Ideal size of system partition:
disk.systemPartition.size [0]:
Initial vendor partition image:
disk.vendorPartition.initPath []:
Path to runtime vendor partition image:
disk.vendorPartition.path []:
Ideal size of vendor partition:
disk.vendorPartition.size [0]:
Always use cold boot: If set, AVD will always use the full cold boot instead of snapshot-based quick boot process
fastboot.forceColdBoot [no]:
Accelerometer: Whether there is an accelerometer in the device.
hw.accelerometer [yes]:
Chrome OS device (App Runtime for Chrome): The emulated device is a Chrome OS machine.
hw.arc [no]:
Auto login for Chrome OS devices: Used to enable auto login into Chrome OS devices
hw.arc.autologin [no]:
Audio recording support: Whether the device can record audio
hw.audioInput [yes]:
Audio playback support: Whether the device can play audio
hw.audioOutput [yes]:
Battery support: Whether the device can run on a battery.
hw.battery [yes]:
Configures camera facing back: Must be 'emulated' for a fake camera, 'webcam<N>' for a web camera, or 'none' if back camera is disabled.
hw.camera.back [emulated]:
Configures camera facing front: Must be 'emulated' for a fake camera, 'webcam<N>' for a web camera, or 'none' if front camera is disabled.
hw.camera.front [none]:
CPU Architecture: The CPU Architecture to emulator
hw.cpu.arch [arm]:
CPU model: The CPU model (QEMU-specific string)
hw.cpu.model []:
SMP CPU core count: Number of cores in a simulated SMP CPU.
hw.cpu.ncore [2]:
DPad support: Whether the device has DPad keys
hw.dPad [yes]:
Screen density of the second display:
hw.display1.density [0]:
the flag to use when the second display is initialized in the Android system.:
hw.display1.flag [0]:
Pixel height of the second display:
hw.display1.height [0]:
Pixel width of the second display:
hw.display1.width [0]:
the horizontal offset of the second display with respect to the host QT window.:
hw.display1.xOffset [-1]:
the veritcal offset of the second display with respect to the host QT window.:
hw.display1.yOffset [-1]:
Screen density of the third display:
hw.display2.density [0]:
the flag to use when the third display is initialized in the Android system.:
hw.display2.flag [0]:
Pixel height of the third display:
hw.display2.height [0]:
Pixel width of the third display:
hw.display2.width [0]:
the horizontal offset of the third display with respect to the host QT window.:
hw.display2.xOffset [-1]:
the veritcal offset of the third display with respect to the host QT window.:
hw.display2.yOffset [-1]:
Screen density of the fourth display:
hw.display3.density [0]:
the flag touse when the fourth display is initialized in the Android system.:
hw.display3.flag [0]:
Pixel height of the fourth display:
hw.display3.height [0]:
Pixel width of the fourth display:
hw.display3.width [0]:
the horizontal offset of the fourth display with respect to the host QT window.:
hw.display3.xOffset [-1]:
the veritcal offset of the fourth display with respect to the host QT window.:
hw.display3.yOffset [-1]:
Vertical size of the sub-region:
hw.displayRegion.0.1.height [0]:
Horizontal size of the sub-region:
hw.displayRegion.0.1.width [0]:
Horizontal offset of the sub-region:
hw.displayRegion.0.1.xOffset [-1]:
Vertical offset of the sub-region:
hw.displayRegion.0.1.yOffset [-1]:
Feature flags: A comma-separated list of feature flags to enable or disable, such as 'Enabled,-Disabled'.
hw.featureflags []:
Adjust display window to folded size:
hw.fold.adjust [no]:
Transport used to run graphics:
hw.gltransport [pipe]:
For address space graphics, the size of the ring used to transfer larger buffers.:
hw.gltransport.asg.dataRingSize [32768]:
For address space graphics, the total size of the write buffer the guest can write into:
hw.gltransport.asg.writeBufferSize [1048576]:
For address space graphics, the max size of each guest-to-host transaction.:
hw.gltransport.asg.writeStepSize [4096]:
Interval over which to flush draw calls (balance host gpu starve vs pipe notif overhead):
hw.gltransport.drawFlushInterval [800]:
GPS support: Whether there is a GPS in the device.
hw.gps [yes]:
GPU emulation: Enable/Disable emulated OpenGLES GPU
hw.gpu.enabled [no]:
GPU emulation mode: This value determines how GPU emulation is implemented.
hw.gpu.mode [auto]:
GSM modem support: Whether there is a GSM modem in the device.
hw.gsmModem [yes]:
Gyroscope: Whether there is a gyroscope in the device.
hw.gyroscope [yes]:
Initial screen orientation: Setup initial screen orientation, can be rotated later on.
hw.initialOrientation [portrait]:
Keyboard support: Whether the device has a QWERTY keyboard.
hw.keyboard [no]:
Keyboard charmap name: Name of the system keyboard charmap file.
hw.keyboard.charmap [qwerty2]:
Keyboard lid support: Whether the QWERTY keyboard can be opened/closed.
hw.keyboard.lid [yes]:
LCD backlight: Enable/Disable LCD backlight simulation,yes-enabled,no-disabled.
hw.lcd.backlight [yes]:
Abstracted LCD density: A value used to roughly describe the density of the LCD screen for automatic resource/asset selection.
hw.lcd.density [160]:
LCD color depth: Color bit depth of emulated framebuffer.
hw.lcd.depth [16]:
LCD pixel height:
hw.lcd.height [640]:
LCD VSYNC rate:
hw.lcd.vsync [60]:
LCD pixel width:
hw.lcd.width [320]:
Logcat Output File Path:
hw.logcatOutput.path []:
Hardware Back/Home keys: Whether there are hardware back/home keys on the device.
hw.mainKeys [yes]:
Device ram size: The amount of physical RAM on the device, in megabytes.
hw.ramSize [0]:
Rotary input support: Whether the device has rotary input
hw.rotaryInput [no]:
Touch screen type: Defines type of the screen.
hw.screen [multi-touch]:
SD Card support: Whether the device supports insertion/removal of virtual SD Cards.
hw.sdCard [yes]:
SD Card image path:
hw.sdCard.path []:
Uncalibrated gyroscope support: Provides uncalibrated gyroscope sensor values.
hw.sensors.gyroscope_uncalibrated [yes]:
Humidity support: Whether there is a relative humidity sensor in the device
hw.sensors.humidity [yes]:
Light support: Whether there is a light sensor in the device
hw.sensors.light [yes]:
Magnetic field support: Provides magnetic field sensor values.
hw.sensors.magnetic_field [yes]:
Uncalibrated magnetic field suport: Provides uncalibrated magnetic field sensor values.
hw.sensors.magnetic_field_uncalibrated [yes]:
Orientation support: Provides orientation sensor values.
hw.sensors.orientation [yes]:
Pressure support: Whether there is a pressure sensor in the device
hw.sensors.pressure [yes]:
Proximity support: Whether there is an proximity in the device.
hw.sensors.proximity [yes]:
Temperature support: Provides temperature sensor values.
hw.sensors.temperature [yes]:
Track-ball support: Whether there is a trackball on the device.
hw.trackBall [yes]:
Deprecated option. Ignored.: Used to specify the Ext4 partition image type. This is now autodetected.
hw.useext4 [yes]:
Does the kernel require a new device naming scheme?: Used to specify whether the kernel requires a new device naming scheme. Typically for Linux 3.10 and above.
kernel.newDeviceNaming [autodetect]:
kernel boot parameters string.:
kernel.parameters []:
Path to the kernel image: Path to the kernel image.
kernel.path []:
Does the kernel supports YAFFS2 partitions?: Used to specify whether the kernel supports YAFFS2 partition images. Typically before 3.10 only.
kernel.supportsYaffs2 [autodetect]:
Delay sending data to guest adb until guest completed booting:
test.delayAdbTillBootComplete [0]:
Monitor Adb messages between guest and host. Default: Disabled.:
test.monitorAdb [0]:
Quit emulator after guest boots completely, or after time out. Default: end of universe.:
test.quitAfterBootTimeOut [-1]:
Max VM application heap size: The maximum heap size a Dalvik application might allocate before being killed by the system. Value is in megabytes.
vm.heapSize [0]:
@RealYukiSan
Copy link

looking for a way to fix the button controls in emulator skins that don't work at all
image
image

C:\Android\emulator\lib\hardware-properties.ini

Either menu, back or home
Arghhhhhhhhhhhh

@RealYukiSan
Copy link

Hardware Back/Home keys: Whether there are hardware back/home keys on the device.
hw.mainKeys [yes]:

not work too

AaaaAaaaa

@RealYukiSan
Copy link

@RealYukiSan
Copy link

RealYukiSan commented Aug 25, 2023

C:\Users\Zero\.android\avd\my.avd\config.ini
Arrgghhh

@RealYukiSan
Copy link

Uwoghhhhh Solved my issue with the command below:
avdmanager create avd -d 22 -k "system-images;android-31;google_apis;x86_64" -n test -f

I add the -d argument for device pixel 4 (id 22) and now the screen have a control button:
image

Cheers!

@RealYukiSan
Copy link

but still wondering why this button still didn't work at all :"
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment