Sonic Colors Crashing Help

[TheGamerPro]

While booting up Sonic Colors on Dolphin Emulator, it kept freezing at startup when displaying the controls. I figured out why and it was because I was using JIT ARM64 Recompiler. However, when I used Interpreter or Cached Interpreter it booted up normally but ran super slow.
Is there any way to fix this bug so I can play of JIT ARM64 Recompiler because Interpreter is very slow. I'm running this on android and it has a decent CPU to run games and if it can run Sonic Colors on Interpreter, then I'm sure it can run on JIT ARM64 RecompileR higher frame rate. Am I doing something wrong?
(Running on build 4.0-9170 and using a Samsung Galaxy S6 to run.)

[YellowDart]

The interpreter is a CPU core that is designed to have maximum accuracy, at the cost of running extremely, extremely slowly.

Think if you were visiting a foreign country: if you didn't know that country's language, but you had a dictionary for it, you could still talk to people; it would just take you literally 30 seconds for every word.

If you just knew the language, you could speak at a regular speed. If you even *kind* of knew it, you could speak at something close to a regular speed, but you'd get some words wrong sometimes.

Dolphin for ARM64 processors doesn't currently know enough Wii-ese to play Sonic Colors, and when it gets a word wrong, the result is a crash.

[Nintonito]

If you happen to be running android 6.0 on the Galaxy S6, this is a known device specific issue with dolphin on that particular android build.  My advice would be to either attempt a downgrade to 5.1.1 using ODIN,  or just keep your device as up to date as possible and hope the issue is resolved soon.

[YellowDart]

Oh, yeah. I didn't see that they said they were running a Galaxy S6. Yeah, that phone on 6.0 is having trouble launching any games at all.

[brujo5]

(03-27-2016, 11:24 AM)YellowDart Wrote: Oh, yeah. I didn't see that they said they were running a Galaxy S6. Yeah, that phone on 6.0 is having trouble launching any games at all.

nope.

galaxy s6 in android 6.0 broke rendering for dolphin

galaxy s7 exynos in android 6.0 crash at launch any game

[brujo5]

(03-27-2016, 07:13 AM)TheGamerPro Wrote: While booting up Sonic Colors on Dolphin Emulator, it kept freezing at startup when displaying the controls. I figured out why and it was because I was using JIT ARM64 Recompiler. However, when I used Interpreter or Cached Interpreter it booted up normally but ran super slow.
Is there any way to fix this bug so I can play of JIT ARM64 Recompiler because Interpreter is very slow. I'm running this on android and it has a decent CPU to run games and if it can run Sonic Colors on Interpreter, then I'm sure it can run on JIT ARM64 RecompileR higher frame rate. Am I doing something wrong?
(Running on build 4.0-9170 and using a Samsung Galaxy S6 to run.)

try to run the game using the cpu cache interpreter until you reach the menu then make a save state, close the game and change cache interprete for armjit64, run the the game and load the save state as fast you can.

maybe work

[TheGamerPro]

I am currently on 5.1.1 as a SM-G920V doesn't support 6.0 (yet). For some reason it's only happening with this game but every other wii game works just fine.
Any options?

[TheGamerPro]

(03-27-2016, 11:59 AM)brujo5 Wrote: try to run the game using the cpu cache interpreter until you reach the menu then make a save state, close the game and change cache interprete for armjit64, run the the game and load the save state as fast you can.

maybe work

I've actually tried that before I made this thread. It worked one time but then crashed as soon as I loaded the quick save. But it won't work neither do I want to have to go through a 2 second gap loading screen each time I try and crash whenever I enter the game. :/

[TheGamerPro]

Ok so when using JIT, thwe game crashes on the wii instruction screen.
But runs just fine on Cached Interpreter...
This game works on the pc version of dolphin just fine, I'm so confused now...
What seems to be the problem?  

[Helios]

bad drivers and broken mobile OSes, on top of little maintenance right now on the Android version of Dolphin.