Dolphin, the GameCube and Wii emulator - Forums

Making this thread myself so I don't have to wait for anyone else to ask this question.

Android O confirmed as Android Oreo has been said to run 2x the speed of its predecessor for boot speed and general app performance so that may also equate to better speeds in Dolphin Emu since the CPU usage is likely reduced especially with background processes being dealt with more strictly.

Of course when Android TV gets its upgrade,we hope it will allow configuration for "battery" consumption so that it can be set to use more electricity to keep performance way up.

Instability may be expected with major Android OS updates,so results will vary on the outcome of your updates.

In case I can't get a poll to work via the thread setting,how does it run for you?

1. Dolphin runs near identical to previous Android. 

2. Dolphin runs better than on previous Android. 

3. Dolphin runs worse than on previous Android. 

4. Dolphin runs way better than it did on previous Android. 

5. Dolphin fails to run at all. 

Don't expect too much. I'm going to be pleasantly surprised if Dolphin becomes any faster at all.

Google updates the java virtual machine, so we might be very lucky and get twice the performance in the UI. And maybe they've reduced the background tasks from 1% to 0.5% - on the spare CPU core.

In the end, maybe there was a GPU driver update on the new firmware, maybe not. Everything else, include the emulation performance, can't change because of an update of the OS.

Android Oreo clocked my phone to 42069 ghz and now Dolphin runs at 316.5% on Rogue Squadron 2 and my phone doesn't get hot at all

best update ever

(08-23-2017, 07:23 AM)Helios Wrote: [ -> ]Android Oreo clocked my phone to 42069 ghz and now Dolphin runs at 300% on Rogue Squadron 2 and my phone doesn't get hot at all

Replace ghz with MHz, and the number might be correct. At least because the arm jit doesn't support MMU and falls back to the interpreter *very* often for RS2.

I'm just waiting for a custom rom with GO_FASTER=1 enabled in the build.

I'm *still* surprised that's not the default....

Oreo was released yesterday, and unless it's a Pixel it's going to take months for it to turn up on phones. Why make a thread about this now, when practically no one has it yet?

Should just rename this thread to "how does it run on pixel's" since literally nobody else will have an answer.

Well darn,the confusion of those events led me to believe it was being rolled out on all devices on the day of the solar eclipse for their own convenience.

What about the other Nexus devices then? Its not just the Pixel that has the rollout.

My poll was set for 6 months and lasts until February 2018 so there is plenty of time for other brands to get the new OS upgrade.
I or someone else could bump the thread when Android Oreo gets a more substantial release within September or October.

(08-23-2017, 09:19 AM)JonnyH Wrote: [ -> ]I'm just waiting for a custom rom with GO_FASTER=1 enabled in the build.

I'm *still* surprised that's not the default....

explain pls? Is there some sort of performance tweaks available?