Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Why do we default to `-gpu swiftshader_indirect` if HAXM is supported by MacOS Latest?

See original GitHub issue

According to the readme, it seems the default GPU flag uses -gpu swiftshader_indirect, but this is the software acceleration which the Android Docs here say to try to use if Hardware Acceleration is not available. But, MacOS-Latest allegedly does support HAXM and Hardware Acceleration.

Is this really the default that the ReactiveCircus/Android-Emulator-Runner uses?
Or is this only used an example in the readme? The wording is confusing, because it says the default emulator options are Default emulator-options: -no-window -gpu swiftshader_indirect -no-snapshot -noaudio -no-boot-anim

I recommend not defaulting to this, or adding clarification in the readme.

Issue Analytics

State:
Created a year ago
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

mrk-hancommented, Oct 6, 2022

@ychescale9 Funny thing is I helped update that readme before they open-sourced it from the internal repo. But I haven’t checked it out much since. I really would prefer to run in Docker so things could be more portable. Thanks for the suggestion.

It’d be a real shame if Hardware Acceleration couldn’t be taken advantage of on the Github Actions/Azure runners.

Will do more investigating…

0reactions

mrk-hancommented, Oct 19, 2022

Closing as HAXM is not pre-installed by macOS-11 or macOS-12.

See: https://github.com/actions/runner-images/issues/6388