The Tizen Emulator is a tool that reduces the inconvenience of testing the application on a real device, by providing an environment similar to a real device. In other words, if you do not have the real device, you can test on a virtual device with similar features.
Using the Emulator Manager, you can create a variety of environments (different device types) and you can preview the problems during the development process. The emulator provides the actual hardware similar to real device controls, and you can check the application features, such as data processing and user scenarios.
The emulator is based on the open source QEMU project and consists of a virtual CPU, memory, and various peripherals. Currently, Tizen Studio only supports the x86 machine architecture for guest.
The emulator provides the following main features:
For more information, see Supported Features.
To use the emulator, you need the Emulator Manager. If you do not have the Emulator Manager, install it through the Tizen Studio Package Manager.
To start the emulator and run an application:
Open the Emulator Manager.
If you do not have an applicable emulator instance, create one.
Select the emulator instance and click Launch.
Test your application in the emulator. You can launch your application in 2 ways:
To close the emulator, right-click the emulator and select Close, or click and hold the Power key.
The emulator device stores the installed application so you can run it again, if needed. To remove the application, you must uninstall it. If you run the project again on the same emulator, the emulator replaces the application with the new version.
In the Emulator Manager, in addition to creating new emulator instances according to the environments you need, you can also modify and delete emulator instances.
If the CPU VT is disabled in the Emulator Configuration view on the Emulator Manager, check the following prerequisites and install KVM or HAX:
Prerequisites for using HW virtualization:
To use KVM, you need a processor that supports HW virtualization. Both Intel and AMD have developed those extensions for their processors (Intel VT-x/AMD-V). Check whether the CPU supports HW virtualization with the following command:
$egrep -c '(vmx|svm)' /proc/cpuinfo
If the output of the command is 0, the CPU does not support HW virtualization. Otherwise, it does.
The HW virtualization feature can also be disabled on the BIOS setting. Check the setting and enable it if you need the feature.
To use HAX, you need an Intel VT-x-supported CPU, and you must enable the NX-related setting in the PC BIOS.
To use HAX, install EFI-related updates on your Intel-based Mac computer.
For more information, see EFI and SMC firmware updates for Intel-based Mac computers.
Installing KVM or HAX:
No installation is required for KVM.
In Windows® and macOS:
The HAXM driver is installed during the Tizen Studio installation. For more information on installing HAXM, see Hardware Accelerated Execution Manager.
If the installation fails with a VT-related message, check the CPU feature and BIOS settings. If the installation fails with an NX-related message, enable NX (or PAE and DEP) -related item in the BIOS. In addition, make sure that the operating system supports the NX feature (for more information, see MSDN).
No configuration is required for KVM or HAX.
To run the emulator with the HW virtualization support in the Emulator Manager, set the CPU VT field to ON. The field is disabled if your system cannot support HW virtualization.
You can also run the emulator with the HW virtualization support from the command line, by including the
-enable-kvm (in Ubuntu) or
-enable-hax (in Windows® and macOS) option in the start-up command.
The emulator provides various virtual HW, media formats, codecs, and OpenGL® ES acceleration. For better performance of the OpenGL® ES support, the Tizen Emulator exploits the latest feature of the graphic driver, so always install the latest vendor-provided graphic driver. The emulator, however, has some limitations and differences compared to physical target devices.
The following table lists the basic features supported in the emulator.
Table: Supported emulator features
|Skin||Skins are fitted to the screen resolution:
4 orientation modes are supported:
Portrait (default), landscape, reverse portrait, and reverse landscape
|Supported||2 skin layout types are supported:
|Touch||Maru touchscreen device||Supported||Multi-touch is supported.|
|Key||HW keys, host keyboard, and SW keypad||Supported||The host keyboard is not supported for the wearable emulator.|
|Rotary||360 levels of clockwise or counter-clockwise rotation||Supported||-|
|Display||VGA card with 100 levels of brightness control||Supported||-|
|OpenGL® ES||Compatible with OpenGL® ES 1.1 and 2.0
OpenGL® ES API pass-through through PCI
|Supported||The OpenGL® ES 1.1 functionality is not guaranteed on the emulator, unless the graphics hardware of your computer supports OpenGL® 1.5.
The OpenGL® ES 2.0 functionality is not guaranteed on the emulator, unless the graphics hardware of your computer supports OpenGL® 2.1.
The host machine must support OpenGL® 1.4.
|Sound||AC97 device||Supported||Audio in:
Make sure that the input volume of the microphone is enough to record your voice or songs on the host machine.
On Windows® 7, inject the microphone into the host machine before starting the emulator.
On Windows® 7, enable at least 1 audio out device before starting the emulator. Make sure that the volume icon in the tray is not disabled.
While the emulator is running, do not disable the audio out device, as it can lock the audio system of the guest platform.
|Network connection||Virtio||Supported||Raw socket protocol, such as ICMP, is not supported.|
|Emulator Control Panel||The Emulator Control Panel (ECP) supports different features depending on the device profile:
|Supported||The ECP is a standalone tool, which replaces the Event Injector. It helps to control and monitor the emulator features, and can be launched from the emulator context menu.|
|Camera||Virtual camera device connecting a host machine's Webcam:
||Supported||While recording a video using the emulator, an audio-video synchronization error can occur depending on your computer hardware and performance.|
|Wi-Fi Direct®||-||Not supported||-|
For the emulator to support OpenGL® ES acceleration, you need:
The emulator supports only ES 1.1, ES 2.0, and EGL™ 1.4 versions.
The following tables describe the differences between a real target device and the emulator. For more information, see the detailed differences in:
Table: Comparison summary
|Development environment||Target||Buy a target device or reference board (by model)||Download Tizen Studio (multi-profile and multi-model support)|
|Network||Need Bluetooth||Only the network environment|
|Target connection||USB||IPC (TCP/UDP)|
|Source and package management||Source and package for target||Source and package for the emulator|
|Host Directory Sharing||Not supported||Supported|
|RAM, storage size||Fixed||Configurable|
|2D and 3D acceleration API||GPU-dependent||GPU-independent (common set)|
|CP, telephony||Fully supported||Partially supported (only SMS and voice call)|
|Wi-Fi||Fully supported||Partially supported (using Ethernet)|
|Sensor||Fully supported||Partially supported (using the Emulator Control Panel)|
|PnP, external connection||Fully supported||Partially supported (using the Emulator Control Panel)|
|Camera||Fully supported||Partially supported (preview, capture, recording, contrast, and brightness)|
|Vibration, haptic||Fully supported||Not supported|
|Bluetooth||Fully supported||Not supported|
|Performance||CPU performance||Mobile CPU||Desktop CPU (with hardware virtualization)|
|GPU performance||Real GPU||Desktop GPU (relatively slow)|
|I/O performance||Real HW I/O||Emulated I/O (relatively slow)|
Table: Input differences
|Touch screen panel||Real device and driver||Virtual (VirtIO) device and driver|
|Host keyboard and hardware key||Real device and driver||Virtual (VirtIO) device and driver|
Table: Graphics and display differences
|Framebuffer device||Display controller in the processor||Virtual VGA card|
|Backlight control||LDI (LCD Driver IC) command||Additional virtual device and driver|
Table: Virtual sensor differences
|Sensor||Acceleration||Receives the actual acceleration value of the device.||Receives the virtual acceleration value through the Emulator Control Panel.
When the emulated device is stationary and vertical in portrait orientation, the acceleration values are 0, 1, and 0 g.
|Gyro||Receives the actual gyroscope value of the device.||Receives the virtual gyroscope value through the Emulator Control Panel.|
|Geomagnetic||Receives the actual geomagnetic value of the device.||Receives the virtual geomagnetic value through the Emulator Control Panel.
When the emulated device is stationary and vertical in portrait orientation, the Y axis is at true north and the magnetic field strength values are 1, 0, and -10 µT.
|Proximity||Receives the actual proximity value of the device.||Receives the virtual proximity value through the Emulator Control Panel.
You can register an event handler for the proximity sensor and test it with the Emulator Control Panel. However, the screen does not power off during the event because the emulator does not connect to the power manager.
|Light||Receives the actual ambient light value of the device.||Receives the virtual ambient light value through the Emulator Control Panel.
You can register an event handler for the light sensor and test it with the Emulator Control Panel. However, in order to test the screen brightness change, the brightness setting must be automatic in the setting application.
|Pressure||Receives the actual pressure value of the device.||Receives the virtual actual pressure value through the Emulator Control Panel.|
|Ultraviolet||Receives the actual ultraviolet value of the device.||Receives the virtual actual ultraviolet value through the Emulator Control Panel.|
|Heart Rate Monitor||Receives the actual heart rate and peak-to-peak values of the device.||Receives the virtual actual heart rate and peak-to-peak values through the Emulator Control Panel.|
|Device||Battery||Receives the actual battery value of the device.||Receives the virtual battery value through the Emulator Control Panel.
You can change the battery level and the charger connection status.
|Earjack||Receives the actual earjack connection event of the device.||Receives the earjack connection event through the Emulator Control Panel.
You can select a 3-wire or 4-wire connection, or set the earjack as disconnected.
|USB||Receives the actual USB connection event of the device.||Receives the USB connection event through the Emulator Control Panel.|
|RSSI||Receives the actual RSSI value of the device.||Receives the virtual RSSI value through the Emulator Control Panel.|
|Location||Log||Supported by lbsFW.||Receives the virtual GPS log file through the Emulator Control Panel.
You can use a log file of the NMEA format.
|Manual||Not supported.||Receives the virtual longitude and latitude values through the Emulator Control Panel.|
|Map||Not supported.||Receives the virtual longitude, latitude, altitude, and horizontal accuracy values through the Emulator Control Panel map.|
|Auto||Receives the actual GPS coordinates of the device.||Not supported.|
Table: Telephony differences
|Call||Calls and video calls are supported.||Call waiting, outgoing call barring, and voice calls with the Emulator Control Panel are supported.
Video calls, call forwarding, incoming call barring, and emulator-to-emulator calls are not supported.
|SMS||SMS messaging is supported.||SMS messaging with the Emulator Control Panel is supported.
Sending emulator-to-emulator SMS messages is not supported.
Table: Power management differences
|Display on/off||Display controller in the processor||Internal emulation|
|Power off||Power management in the processor||ACPI (Advanced Configuration and Power Interface)|
Table: Media format and codec differences