diff --git a/src/android/app/src/main/java/io/github/lime3ds/android/features/settings/ui/SettingsFragmentPresenter.kt b/src/android/app/src/main/java/io/github/lime3ds/android/features/settings/ui/SettingsFragmentPresenter.kt
index bf07d1d14..d35e1a2c6 100644
--- a/src/android/app/src/main/java/io/github/lime3ds/android/features/settings/ui/SettingsFragmentPresenter.kt
+++ b/src/android/app/src/main/java/io/github/lime3ds/android/features/settings/ui/SettingsFragmentPresenter.kt
@@ -650,14 +650,12 @@ class SettingsFragmentPresenter(private val fragmentView: SettingsFragmentView)
add(InputBindingSetting(button, Settings.axisTitles[i]))
}
- // TODO: Improve the integration of the two dpad types to be
- // less user-facingly hacky
- add(HeaderSetting(R.string.controller_dpad_axis))
+ add(HeaderSetting(R.string.controller_dpad_axis,R.string.controller_dpad_axis_description))
Settings.dPadAxisKeys.forEachIndexed { i: Int, key: String ->
val button = getInputObject(key)
add(InputBindingSetting(button, Settings.axisTitles[i]))
}
- add(HeaderSetting(R.string.controller_dpad_button))
+ add(HeaderSetting(R.string.controller_dpad_button,R.string.controller_dpad_button_description))
Settings.dPadButtonKeys.forEachIndexed { i: Int, key: String ->
val button = getInputObject(key)
add(InputBindingSetting(button, Settings.dpadTitles[i]))
diff --git a/src/android/app/src/main/res/values/strings.xml b/src/android/app/src/main/res/values/strings.xml
index 946df3ce5..ddb874645 100644
--- a/src/android/app/src/main/res/values/strings.xml
+++ b/src/android/app/src/main/res/values/strings.xml
@@ -112,7 +112,9 @@
Trigger
D-Pad
D-Pad (Axis)
+ Some controllers may not be able to map their D-pad as an axis. If that\'s the case, use the D-Pad (buttons) section.
D-Pad (Button)
+ Only map the D-pad to these if you\'re facing issues with the D-Pad (Axis) button mappings.
Up/Down Axis
Left/Right Axis
Up