The following tables describe the differences between a real target device and the Emulator. For more detailed information, see the differences in:
Category | Subject | Physical target | Emulator |
---|---|---|---|
Development environment | Target | Buy a target device or reference board (by model) | Download the SDK (multi-model support) |
Network | Need Wi-Fi or 3G/4G | 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 | |
Portability | Screen resolution | Fixed | Configurable (WVGA/HD) |
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, not accessible from an external machine) | |
Sensor | Fully supported | Partially supported (using the Event Injector view) | |
PnP, external connection | Fully supported | Partially supported (using the Event Injector view) | |
Camera | Fully supported | Partially supported (preview/capture/recording/contrast/brightness, not effect/control) | |
Vibration, haptic | Fully supported | Not supported | |
Bluetooth, radio | Fully supported | Not supported | |
Performance | CPU performance | Mobile CPU | Desktop CPU (with hardware virtualization) |
GPU performance | Real GPU | Emulated 3D (relatively slow) | |
I/O performance | Real HW I/O | Emulated I/O (relatively slow) |
Category | Physical target | Emulator |
---|---|---|
Device type | Touchscreen | Virtio Touchscreen |
Device driver | AT42QT602240 | Maru touchscreen |
Category | Physical target | Emulator |
---|---|---|
Framebuffer device | Display controller in the processor | Virtual VGA card |
Backlight control | LDI (LCD Driver IC) command | Additional virtual device and driver |
Overlay control | Display controller in the processor | Additional virtual device and driver |
Category | Physical target | Emulator | |
---|---|---|---|
Sensor | Acceleration | Receives the actual acceleration value of the device. | Receives the virtual acceleration value through the Event Injector view.
If the Emulator orientation is portrait, the acceleration values are approximately 0, -9.81, and 0 degrees. |
Gyro | Receives the actual gyroscope value of the device. | Receives the virtual gyroscope value through the Event Injector view. | |
Geomagnetic | Receives the actual geomagnetic value of the device. | Receives the virtual geomagnetic value through the Event Injector view.
If the Emulator orientation is portrait, the y axis points to true north and the magnetic tesla values are 1, 0, and -10 degrees. |
|
Proximity | Receives the actual proximity value of the device. | Receives the virtual proximity value through the Event Injector view.
You can register an event handler for the proximity sensor and test it with the Event Injector view. However, the screen does not power off during the event because the Emulator does not have the power manager. |
|
Light | Receives the actual ambient light value of the device. | Receives the virtual ambient light value through the Event Injector view.
You can register an event handler for the light sensor and test it with the Event Injector view. However, the screen brightness does not change during the event because the Emulator does not have the power manager. |
|
Motion | Receives the actual motion event of the device. | Receives a partial motion event through the Event Injector view.
Double tap, shake, and snap are supported, while panning and face-down are not. |
|
Device | Battery | Receives the actual battery value of the device. | Receives the virtual battery value through the Event Injector view.
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 Event Injector view.
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 Event Injector view. | |
RSSI | Receives the actual RSSI value of the device. | Receives the virtual RSSI value through the Event Injector view. | |
Location | Log | Supported by lbsFW. | Receives the virtual GPS log file through the Event Injector view.
You can use a log file of the NMEA format. |
Manual | Not supported. | Receives the virtual longitude and latitude values through the Event Injector view. | |
Map | Not supported. | Receives the virtual longitude and latitude values through the Event Injector view map. | |
Auto | Receives the actual GPS coordinates of the device. | Not supported. |
Category | Physical target | Emulator | |
---|---|---|---|
Telephony | Call | Calls and video calls are supported. | Call waiting, outgoing call barring, and voice calls with the Event Injector view 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 Event Injector view is supported.
Sending Emulator-to-Emulator SMS messages is not supported. |
Category | Physical target | Emulator |
---|---|---|
LCD on/off | Display controller in the processor | Internal emulation |
Power off | Power management in the processor | ACPI (Advanced Configuration and Power Interface) |
Category | Physical target | Emulator | |
---|---|---|---|
Decoder | AAC+ | Supported | Not supported |
Enhanced AAC+ | Supported | Not supported | |
FLAC | Supported | Not supported | |
Encoder | H.264 | Supported | Not supported |