-
Notifications
You must be signed in to change notification settings - Fork 176
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.
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
FEATURE: bypass emulator detection #198
Comments
Try this script. It works in some cases. For example, for konosuba. |
I would try it but suddenly my waydroid is not working anymore also on the HayDay part |
Doesn't work after running the script? You can always manually delete the lines added by the script in waydroid.cfg and restart the upgrade command. If it didn't work before running the script, you can do a full reset |
I finally got my waydroid back working |
I have access to this code from apk relevant to emulator detection: private void checkEmulator() {
this.emulatorDetectorThread = EmulatorDetector.with(this).setCheckTelephony(false).setDebug(false).detect(new f());
} and also public void run() {
boolean detect = EmulatorDetector.this.detect();
EmulatorDetector emulatorDetector = EmulatorDetector.this;
StringBuilder sb = new StringBuilder();
char[] cArr = {(char) (cArr[4] ^ 't'), (char) (cArr[6] ^ 17), (char) (cArr[13] ^ 26), (char) (cArr[4] ^ 'S'), (char) (cArr[16] ^ 'M'), (char) (cArr[3] ^ ' '), (char) (cArr[15] ^ Typography.less), (char) (cArr[11] ^ 'S'), (char) (cArr[13] ^ 7), (char) (cArr[4] ^ 'E'), (char) (cArr[5] ^ Typography.greater), (char) (cArr[8] ^ 'T'), (char) (cArr[13] ^ 26), (char) (cArr[15] ^ '6'), (char) (cArr[4] ^ 0), (char) ((-29490) ^ (-29557)), (char) (cArr[12] ^ 4), (char) (cArr[23] ^ 'O'), (char) (cArr[21] ^ 3), (char) (cArr[2] ^ '\b'), (char) (cArr[4] ^ 'T'), (char) (cArr[12] ^ 6), (char) (cArr[15] ^ '7'), (char) (cArr[15] ^ 127), (char) (cArr[10] ^ 'M')};
sb.append(new String(cArr).intern());
sb.append(detect);
emulatorDetector.log(sb.toString());
OnEmulatorDetectorListener onEmulatorDetectorListener = this.f12052a;
if (onEmulatorDetectorListener != null) {
onEmulatorDetectorListener.onResult(detect);
}
} and much much other obfuscated data so I guess no easy way to spoof this one |
I also found these in logcat |
there are some games that do not allow being played on emulators.
I'm mostly concerned about Hayday a Supercell game.
There are some reddit threads that previously had mentioned changing some data such as manufacturer, brand and device model had solved the issue and they were able to play it fine for a short amount of time.
https://www.reddit.com/r/HayDay/comments/12yy6hq/is_anyone_playing_hay_day_on_bluestacks_and/
https://www.reddit.com/r/BlueStacks/comments/12ycpvr/hay_day_is_broken_in_the_new_update_for_me_on/
https://www.reddit.com/r/HayDay/comments/z7kqz3/hayday_wont_open_on_emulator_after_update/
These are pretty old so none work but there is some idea into how these detections work
Getting back to the main point:
Are there any ways to make An android emulator indistinguishable from a normal day to day device ?
The text was updated successfully, but these errors were encountered: