Controlling the Global User Directory: Difference between revisions

Jump to navigation Jump to search
→‎Windows: a bit late, but updated the guide to reflect the new default folder on Windows
(Added information about Android and scoped storage)
(→‎Windows: a bit late, but updated the guide to reflect the new default folder on Windows)
 
(6 intermediate revisions by one other user not shown)
Line 2: Line 2:


== Windows ==
== Windows ==
Versions of Dolphin before {{revision|3.5-2381}} always used a local user directory, stored in the same folder as Dolphin.exe and named User. In {{revision|3.5-2381}}, the global user directory system was introduced on Windows. By default, the user directory is now a folder in Documents named Dolphin Emulator, but it's possible to configure Dolphin to use the old local user directory or a custom location.
Dolphin {{revision|3.5-2368}} and earlier always used a local user directory, stored in the same folder as <tt>Dolphin.exe</tt> and named <tt>User</tt>. Starting with {{revision|3.5-2381}}, the global user directory system was introduced on Windows and the default user directory changed to a subfolder inside the <tt>Documents</tt> folder, named <tt>Dolphin Emulator</tt>.
 
The default folder changed again on {{revision|5.0-18242}}, which now defaults to <tt>%AppData%\Dolphin Emulator</tt>, however, for backwards compatibility, the previous location will remain in use if it exists when launching Dolphin {{revision|5.0-18242}} or newer for the first time. Additionally, it's possible to configure Dolphin to still use a local user directory or another custom location, as explained below.


=== Disable the Global User Directory for a Specific Build with "portable.txt" ===
=== Disable the Global User Directory for a Specific Build with "portable.txt" ===
Line 45: Line 47:


Dolphin will use the regular user directory path again the next time you launch Dolphin, unless you use <tt>-u</tt> again.
Dolphin will use the regular user directory path again the next time you launch Dolphin, unless you use <tt>-u</tt> again.
=== Environment Variable ===
If you set the <tt>DOLPHIN_EMU_USERPATH</tt> environment variable, Dolphin will use its value as the path to the user directory.


== macOS ==
== macOS ==
Line 56: Line 62:


Dolphin will use the regular user directory path again the next time you launch Dolphin, unless you use <tt>-u</tt> again.
Dolphin will use the regular user directory path again the next time you launch Dolphin, unless you use <tt>-u</tt> again.
=== Environment Variable ===
If you set the <tt>DOLPHIN_EMU_USERPATH</tt> environment variable, Dolphin will use its value as the path to the user directory.


== Android ==
== Android ==
Line 65: Line 75:
* <tt>Android/data/org.dolphinemu.dolphinemu/files</tt> does not exist or is empty
* <tt>Android/data/org.dolphinemu.dolphinemu/files</tt> does not exist or is empty
* <tt>dolphin-emu</tt> exists
* <tt>dolphin-emu</tt> exists
* You give Dolphin permission to access your files when asked
* When Dolphin requests permission to access your files, you press Allow


Scoped storage is disabled if <b>at least one</b> of the following applies:
Scoped storage is disabled if <b>at least one</b> of the following applies:
* You were using Android 10 or older when you installed Dolphin, and you haven't uninstalled Dolphin since then
* You are using Android 10 or older <!-- TODO: What exactly happens when updating from Android 10 with Dolphin installed? Is scoped storage intended to stay disabled? Does the preserveLegacyExternalStorage bug affect it? -->
* You were using Dolphin {{revision|5.0-15341}} or older when you installed Dolphin, and you haven't uninstalled Dolphin since then
* You were using Dolphin {{revision|5.0-15341}} or older when you installed Dolphin, and you haven't uninstalled Dolphin since then, and you haven't triggered the preserveLegacyExternalStorage bug since then
* You have manually disabled scoped storage for Dolphin using the following command (only possible if you have a rooted device or a debug version of Dolphin): <pre>adb shell cmd appops set org.dolphinemu.dolphinemu android:legacy_storage allow && adb shell am force-stop org.dolphinemu.dolphinemu</pre>
* You have manually disabled scoped storage for Dolphin using the following command (only possible if you have a rooted device or a debug version of Dolphin), and you haven't triggered the preserveLegacyExternalStorage bug since then: <pre>cmd appops set org.dolphinemu.dolphinemu android:legacy_storage allow && am force-stop org.dolphinemu.dolphinemu</pre>
 
[https://cs.android.com/android/_/android/platform/frameworks/base/+/c57e3455ff29b0a15a8781a34c19c6ded196f69e The preserveLegacyExternalStorage bug] is triggered when <b>all</b> of the following applies at the same time:
* You are using Android 11 (not Android 12 or newer)
* The installed version of Dolphin is {{revision|5.0-15348}} or newer
* You restart your device


[[Category:Tutorials]]
[[Category:Tutorials]]

Navigation menu