If you are lucky there is an existing module working out-of-the box, letting you run your app on an emulator. There are a some existing XPosed modules for hiding that a device is rooted or that it is running on an emulator. It allows to modify system calls the app uses for identifying that it is running on an emulator. Test results show an improved speed for the hardware architecture while sustaining reasonable enhancement benchmarks. On the way to achieve real-time hardware implementation, certain important computationally efficient approximations are deployed.
You can install the XPosed framework onto your emulator. A modified local normalization has been proposed along with its efficient hardware structure. However, it still may require some Java development. Therefore from my point of view only option 3 is realistic for you. Option 2 is even harder as it requires you to patch and recompile the Android emulator (which is available as source code). using apktool to decompile it to Smali code), identify the emulator checks, and then bypass app integrity checks that may exist. None of the ways are that simple however, the third way may be the easiest as there are some tools that can help you.īack to option 1 - it requires a lot of development skills to decompile the app (e.g. Modify the system calls the app does for detecting it is running on an emulator.Modify the emulator so that it pretends to be a real device.Modify the app and remove the emulator check.In general there are three ways to bypass an emulator check: