[DO NOT MERGE] Android: try to make my Pixel 6 run at full speed

[landfillbaby]

Just guessing at what will make my Pixel 6 run Mario Sunshine at full speed, other than when I'm actively causing UI updates.
Specifically, I can trigger this speedup tapping or dragging my finger on the system notification bar, left side menu, controller overlay, etc. Holding my finger in place doesn't do anything. Pressing volume or power buttons also works since it brings up the volume overlay or fades the screen out.
Seems to be CPU based, since raising the internal resolution makes no difference (another good idea would be to have separate CPU and GPU usage stats in the overlay instead of just guessing based on the maximum speed estimate).
Making it a PR for ease of getting builds.

#10206 (comment)

[landfillbaby]

this is just random guesses at what will fix my issue since i have no way of knowing exactly how sched_pixel or whatever works.

decided to try setpriority(PRIO_PROCESS, 0, -20); in Core::CPUThread first since it's the simplest of the ideas* i have.
if it works i'll set it to a lower value. maybe -10 (THREAD_PRIORITY_VIDEO).

*the ideas in question are:
thread priority (testing failed)
thread affinity to fast cores (only cpu thread: testing failed) (more threads pinned ?)
something to do with the newish Android Dynamic Performance Framework (either GameState or PerformanceHint)

[JMC47]

@dolphin-emu-bot rebuild

[JMC47]

I myself can't give you auto-build privileges, but I can at least make it build

[landfillbaby]

thanks :)

[landfillbaby]

ok so that didn't work. i'll try another way later today hopefully.

[landfillbaby]

ok can i have another build please? nasty wip of thread pinning

[landfillbaby]

oh oops

[landfillbaby]

try again please?

[landfillbaby]

... that somehow made the performance even worse ????

[landfillbaby]

backed up the broken wip of thread pinning at https://github.com/landfillbaby/dolphin/tree/threadpinningwip
maybe i just did it wrong

for now i think i'll try android.app.GameState stuff

[landfillbaby]

oh no. i was wrong before. it is gpu throttling due to system ui stuff.

and i think maybe the only way to fix it is to have a new activity that doesn't have any android java system ui elements or fragments or whatever, only the emulation and a custom controller overlay. not the current one but one that runs in native code. maybe will have to be implemented separately for each renderer???

that's why only dolphin is affected and not ppsspp or duckstation or nethersx2 or melonds-android or retroarch or ...

really wish stenzek hadn't made duckstation's android branch closed-source ...

i'll still try this GameState and PerformanceHint stuff though maybe ...

[landfillbaby]

it does happen for melonds-android too btw

[landfillbaby]

ohno it is . everything

[landfillbaby]

ok actually i would like to see what performance mode does

[landfillbaby]

i give up