[Android] Strange Performance Issue after 4.1 update

RetroArch Android devices
#1

on my HTC One X (AT&T), after downloading the update to Android 4.1, the performance of PSX and GBA cores has changed drastically. the PSX core runs slightly better overall (not complaining) but when sound is disabled in the audio settings menu, the core runs way faster than it should; like it’s stuck in fast forward. The GBA core runs significantly worse. prior to the update, GBA games ran smooth either with or without sound enabled. post update, most roms crawl. with sound disabled, some run smooth, however some are still moving at a crawl and are almost unplayable.

is this actually an issue, or am i just missing an obvious settings fix?

#2

Regarding PSX going into ‘fast forward’ when audio is disabled - we do blocking on audio perhaps in that emu core - so when you disable audio the ‘block’ will be gone and it will be running at maximum speed. I’d advise just dimming/muting the volume instead and leaving audio enabled for the meantime.

Regarding GBA - unfortunately I can’t guarantee any kind of performance level when you do OS upgrades. There are thousands of phones out there all with different specs (and different vendor hacks). As for Android, Android is badly written from a performance perspective, it’s bloated and generally I’d advise against doing OS upgrades beyond the one the device came with since system requirements are constantly increasing for each new Android OS update.

Besides, VBA Next is quite a slow core for Android purposes - you need at least a phone/tablet that has the same runtime performance on the CPU side as a Wii. If it can’t even muster that, you won’t even get 60fps on a lo-frills game like Super Street Fighter II Turbo Revival or Super Mario Advance 1.

Anyway, no word yet on when notaz will decide to do the gpSP port to libretro - that could be one solution to the quite demanding GBA core right now - you’re unlikely to be getting full speed on most games unless you have an Android phone/tablet that has the same runtime performance as a PS3 CPU-wise - that should automatically rule out anything besides perhaps a Cortex A15.

#3

i figured that was the case. thanks for the prompt response.