Project

General

Profile

Actions

Emulator Issues #12849

open

Advice to add an option to disable automatic savestate when putting the emulator from active to background

Added by Cissnei about 2 years ago. Updated about 2 months ago.

Status:
Questionable
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
Android
Issue type:
Feature request
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Any game

What's the problem? Describe what went wrong.

Advice to add an option to disable automatic savestate when putting the emulator from active to background
As savestates are big (may write as much as 30-50MB of data to phone flash memory on each active to suspend transition) and the phone flash memory's lifespan to write data is limited, this feature may write too much data and reduce the useful lifespan of someone's phone whom is subjected to a lot of interruption during NGC/Wii gaming.
So maybe we can add an option to let the user to do the tradeoff between avoid the possibility of losing the progress on resume, and avoid the excessive flash write

What steps will reproduce the problem?
-begin a game in the Dolphin emulator
-push home button when the game is running to go back to the phone launcher/desktop
-normally a savestate is saved in case that system kills the dolphin process
-but there are no options to disable this feature

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
yes, any currently available version have this logic. as for now 5.0-16083

Is the issue present in the latest stable version?
yes, any currently available version have this logic. as for now 5.0-15993

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

What are your PC specifications? (CPU, GPU, Operating System, more)
Android 11

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Actions #1

Updated by JMC4789 about 2 years ago

  • Status changed from New to Questionable

It's against the Android guidelines to not support suspending, and honestly I'm highly doubtful that any of Dolphin's behaviors could make a significant impact on a device's health under normal usage. I've been testing Dolphin on Android for ~3 years now on a Pixel 3a, and I haven't noticed any kind of memory problems despite having to copy ISOs in and out of my limited memory, sometimes 50+ GB in a day when testing different games. I know every manufacturer is different and sometimes hardware fails, but is this really a problem.

Actions #2

Updated by Billiard26 about 2 months ago

  • Operating system Android added
  • Operating system deleted (N/A)
Actions #3

Updated by Billiard26 about 2 months ago

  • Issue type changed from Bug to Feature request
Actions

Also available in: Atom PDF