Skip to content

Update Readme & Provide current context on Hardware Acceleration on Github #279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ychescale9 merged 8 commits into from
Oct 26, 2022
Merged

Update Readme & Provide current context on Hardware Acceleration on Github #279

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
94b88e6
Clarify README with mid-2022 updates, and add info for spellchecker t…
Oct 19, 2022
f04a05b
Remove redundant paragraph in Usage section, and add relevant links t…
Oct 19, 2022
e860dce
Add HAXM installation example and remove linux emphasis
Oct 20, 2022
592f866
Remove gist which contained manual emulator creation/startup
Oct 21, 2022
6722abd
Add clarity to GPU vs VM acceleration in README
Oct 25, 2022
8f64fa8
Fix reversal of examples in README
Oct 25, 2022
b9bd3bb
Add support for commenting run tests on PRs to rerun checks if they fail
Oct 26, 2022
646d92b
Add better conditional logic to determine if comment is issue or PR
Oct 26, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix reversal of examples in README
  • Loading branch information
mrk-han committed Oct 25, 2022
commit 8f64fa84e8f73f19655731df6555e5b7ce2cd0c7
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

A GitHub Action for installing, configuring and running hardware-accelerated Android Emulators on macOS virtual machines.

The old ARM-based emulators were slow and are no longer supported by Google. The modern Intel Atom (x86 and x86_64) emulators can be fast, but rely on two forms of hardware acceleration to reach their peak potential: [Graphics Acceleration](https://developer.android.com/studio/run/emulator-acceleration#accel-graphics), e.g. `emulator -accel on` and [Virtual Machine(VM) Acceleration](https://developer.android.com/studio/run/emulator-acceleration#accel-vm), e.g. `emulator -gpu host`. Note: GPU and VM Acceleration are two different and non-mutually exclusive forms of Hardware Acceleration.
The old ARM-based emulators were slow and are no longer supported by Google. The modern Intel Atom (x86 and x86_64) emulators can be fast, but rely on two forms of hardware acceleration to reach their peak potential: [Graphics Acceleration](https://developer.android.com/studio/run/emulator-acceleration#accel-graphics), e.g. `emulator -gpu host` and [Virtual Machine(VM) Acceleration](https://developer.android.com/studio/run/emulator-acceleration#accel-vm), e.g. `emulator -accel on`. **Note:** GPU and VM Acceleration are two different and non-mutually exclusive forms of Hardware Acceleration.

This presents a challenge when running emulators on CI especially when running emulators within a docker container, because **Nested Virtualization** must be supported by the host VM which isn't the case for most cloud-based CI providers due to infrastructural limits. If you want to learn more about Emulators on CI, here's an article [Yang](https://github.com/ychescale9) wrote: [Running Android Instrumented Tests on CI](https://dev.to/ychescale9/running-android-emulators-on-ci-from-bitrise-io-to-github-actions-3j76).

Expand Down