Android emulators: Difference between revisions
Ilyagredasov (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
Ilyagredasov (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
||
| Line 341: | Line 341: | ||
|- | |- | ||
| [[Shaders_and_filters|Filters]] | | [[Shaders_and_filters|Filters]] | ||
| {{~}}<ref group=N3> | | {{~}}<ref group=N3>Similarly to Android Studio, it has device skin capability for better immersion but it's exclusive to users with license registration.</ref> | ||
| {{Na}} | | {{Na}} | ||
| {{Na}} | | {{Na}} | ||
| Line 347: | Line 347: | ||
| {{Na}} | | {{Na}} | ||
| {{Dunno}} | | {{Dunno}} | ||
| {{~}}<ref group=N3>Android Studio emulator [https://developer.android.com/studio/run/managing-avds#skins supports lots of device frame and custom skin] ( | | {{~}}<ref group=N3>Android Studio emulator [https://developer.android.com/studio/run/managing-avds#skins supports lots of device frame and custom skin] (similarly to libretro overlay/bezels). You can get additional skins from various sources (e.g. [https://github.com/mingchen/android-emulator-skins mingchen's Android Emulator Skins], [https://sourceforge.net/projects/android-emulator-skins/files/ CREAL's AVD skins]), also you can use buttons on these device frames.</ref> | ||
|- | |- | ||
|[[High_dynamic_range#Inverse_tone_mapping|Inverse tone mapping compatible]] | |[[High_dynamic_range#Inverse_tone_mapping|Inverse tone mapping compatible]] | ||
| Line 422: | Line 422: | ||
| {{Dunno}} | | {{Dunno}} | ||
|- | |- | ||
| [[Hypervisors|Built-in, self-contained or integrated virtualization engine]]<br /><small>Emulators that employ a self-contained hypervisor are a distinct class of virtualization solutions that integrate their own layer directly into the application package | | [[Hypervisors|Built-in, self-contained or integrated virtualization engine]]<br /><small>Emulators that employ a self-contained hypervisor are a distinct class of virtualization solutions that integrate their own layer directly into the application package similarly to [[Computer_specifications#Recommended_Specifications|static linking]]. Unlike emulators that rely on third-party or host operating system (OS) features (Microsoft Hyper-V/WHPX, KVM or Intel's HAXM), these solutions are designed to be functionally independent of the host OS's virtualization stack. On Windows, this is typically achieved for Android emulation by installing a proprietary, kernel-level driver that acts as a hypervisor to manage the virtual machine, bypassing the need for pre-existing host OS'es virtualization stack/feature. This shouldn't be confused with hardware-assisted virtualization (VT-x/AMD-V).</small> | ||
| {{Na}}<ref group="N3">It has built-in QEMU version which asks for Hyper-V (on Windows)[https://docs.genymotion.com/desktop/Get_started/011_Windows_install/#hypervisor] (it's currently in beta), otherwise you need to use "with VirtualBox" builds.</ref> | | {{Na}}<ref group="N3">It has built-in QEMU version which asks for Hyper-V (on Windows)[https://docs.genymotion.com/desktop/Get_started/011_Windows_install/#hypervisor] (it's currently in beta), otherwise you need to use "with VirtualBox" builds.</ref> | ||
| {{Na}}<br/><small>''Hyper-V-dependent''</small> | | {{Na}}<br/><small>''Hyper-V-dependent''</small> | ||
| Line 652: | Line 652: | ||
|{{Ya}} | |{{Ya}} | ||
|- | |- | ||
| colspan="2" | Disk I/O<br /><small> | | colspan="2" | Disk I/O<br /><small>Similarly to [[PC_emulator_comparisons#Storage|disk storage emulation on IBM-PC emulators]], this allows you to emulate devices with slow internal storage.</small> | ||
|{{Ya}}[https://docs.genymotion.com/desktop/04_Emulating_sensors_and_features/#disk-io] | |{{Ya}}[https://docs.genymotion.com/desktop/04_Emulating_sensors_and_features/#disk-io] | ||
|{{Dunno}} | |{{Dunno}} | ||