This will mean a lot of extra manual work for us but unfortunately on Android this seems to be the only way we can fix this issue. Later on, there is going to be a way to report the refresh rate that you have found to work well on your device by e-mail so that we can add a ‘hack’ to RetroArch so that it will automatically use a ‘sane’ refreshrate instead of the one the device reports (erroneously). Keep doing this until you finally find that video/audio are perfect. If it audio crackes again, lower the value even more. If it still audio crackles with that value, lower the value by 0.01. Start with 59.95 (which should be the default). Press ‘Forced refreshrate (Hz)’ and set up a manual refresh rate.Go to RetroArch Settings, go to Video Settings.

Even though these devices report a nonsense refreshrate, there is something that can be done about it. However, like the input autodetection, this is something that the users can help us out with. Unfortunately there is little we can do about this - some devicesreport nonsense refresh rates to the Android OS (such as the Xperia Play, or the Samsung Galaxy S3). If you find that speed is not what it should be or that the audio is popping/crackling, chances are that the refresh rate of the screen is getting reported incorrectly.

YOU CAN FIND OUT THE SYSTEM REQUIREMENTS FOR EACH CORE IN THE RETROARCH ANDROID CORES MANUAL. NOTE - BEFORE TRYING THIS - PLEASE CONFIRM THAT THE CORE YOU ARE RUNNING SHOULD BE RUNNING AT FULLSPEED ON YOUR DEVICE.

Resident evil 2 n64 rom audio bug