Step 1 - Run the sdkmanager commands KITKAT (4.4) API 19 You can then manually run automation against various APIs for added device coverage during regression. If you run this locally, you can use the -read-only parameter to run multiple devices at the same time.

Instead of using emulator NAME} to run devices, you can use the aliases if they are added.Or add these parameters to your build steps in TeamCity. Add aliases to run the emulators with parameters more easily.See: Google Documentation on Start the emulator from the command line for more info Steps We create two sets of emulators here, one set with pixel hardware emulation and one set with default oem emulation.Note: X86 is the fastest architecture for emulators, though x86_64 would probably be better to test against because most phones are 64 bit now.These can be run locally or on the base build agent.The goal of this gist is to quickly pre-install a range of system images to provide our project teams the ability to run emulators on a range of API levels, from API 19 to API 28.If you cannot do this, you can still pass -skin 1080x1920 as an argument when starting the emulator.

Hw.keyboard=yes # enables keys from your laptop to be sent to the emulator Skin.name=1080x1920 # proper screen size for emulator List All System Images Available for Download: sdkmanager -list | grep system-imagesĭownload Image: sdkmanager -install 'system-images android-29 default x86'Ĭreate Emulator: echo 'no' | avdmanager -verbose create avd -force -name 'generic_10' -package 'system-images android-29 default x86' -tag 'default' -abi 'x86' I recommend adding these lines to: ~/.android/avd/generic_10.avd/config.ini Install and Create Emulators using AVDMANAGER and SDKMANAGER TL DRįor generic skin emulator with default apis (without google apis):

Android nougat emulator mac