Proposal: Document ARM Translation (Native Bridge/libhoudini) for x86 Emulators

[Galaxy-sc]

Hi MASTG Team,

0x05b-Android-Security-Testing.md explains the limitations of x86 emulators when running applications containing ARM native libraries, but it doesn't currently discuss the available approaches for overcoming these limitations in x86-based testing environments.

I would like to propose adding a short subsection covering the available ARM-to-x86 translation approaches:

1. Android Emulator ARM Translation: Documenting Google's ARM binary translation support available for compatible Android Emulator system images.
2. Custom VMs & Native Bridge: For researchers relying on custom VMs like Genymotion (which lack this built-in support), explaining the underlying Native Bridge mechanism (libhoudini/libndk_translation).
3. Security Considerations: Highlighting the limitations, compatibility issues, and security implications of using unofficial translation scripts for custom VMs.

The goal is to provide a complete picture—highlighting the official AVD capabilities while explaining the underlying OS mechanics for analysts who need to configure manual burner VMs.

I'd be happy to prepare a PR if you think this would be a valuable addition.

References:

• Google's Official Announcement: https://android-developers.googleblog.com/2020/03/run-arm-apps-on-android-emulator.html
• Custom VM Workaround Example (Android 11): https://github.com/niizam/Genymotion_A11_libhoudini
• Legacy Custom VM Workaround (Android 9 and below): https://github.com/m9rco/Genymotion_ARM_Translation