Difference between revisions of "Android"

Revision as of 07:22, 5 August 2025

This pages contains some specific information about the Battle for Wesnoth new Android port (1.19+)

Playing controls

Tap a unit to select it
Tap a unit, then tap the target hex to show defense stats of that unit and footsteps. (Similar to hover on PC)
Tap a unit, then double tap on the target hex to move it. Alternative, you can drag along the path to choose the exact path which the unit is supposed to move by.

The Settings menu (Splash screen)

Logs and debugging steps

Install adb (Android Debug Bridge) on your computer. Search internet for information about your OS. Install drivers for your phone/tablet if necessary.
Enable Developer Mode on your Android device (phone/tablet). Again, the internet is your friend. On newer devices, you need tap Settings > About Phone > Build Number 7 times until it says "You are now a developer", then go into the Setting > System > Developer Options (newly appeared), and find "USB Debugging" in the menu and turn that on.
Connect phone to PC. Do adb logcat or similar from a terminal/command prompt to see if your device appears on the list and is authorized. Tap ok on your phone if any permission request appears.
Run adb logcat -c (clears existing logs), then adb logcat > log.txt (or adb logcat and copy from terminal). Run Wesnoth on phone. Reproduce the crash.
stop adb logcat on PC, and attach the log.txt to your issue report on github along with detailed steps of the bug, and use the Android label.

(Note: adb can be ./adb.exe on Windows. Use internet for help on any of the steps if needed, this is supposed to be a preliminary guideline. Steps might slightly differ based on manufacturer or Android version.)

Turning off Developer Mode

Go to System > Developer Options > Turn off Use developer options toggle.

@@ Line 10: / Line 10: @@
 == Logs and debugging steps ==
 * Install adb (Android Debug Bridge) on your computer. Search internet for information about your OS. Install drivers for your phone/tablet if necessary.
-* Enable Developer Mode on your Android device (phone/tablet). Again, the internet is your friend. On newer devices, you need tap Build Number 7 times until it says "You are now a developer", then go into the Developer Options settings under System (newly appeared), and find "USB Debugging" and turn that on.
+* Enable Developer Mode on your Android device (phone/tablet). Again, the internet is your friend. On newer devices, you need tap Settings > About Phone > Build Number 7 times until it says "You are now a developer", then go into the Setting > System > Developer Options (newly appeared), and find "USB Debugging" in the menu and turn that on.
 * Connect phone to PC. Do <code>adb logcat</code> or similar from a terminal/command prompt to see if your device appears on the list and is authorized. Tap ok on your phone if any permission request appears.
 * Run <code>adb logcat -c</code> (clears existing logs), then <code>adb logcat > log.txt</code> (or <code>adb logcat</code> and copy from terminal). Run Wesnoth on phone. Reproduce the crash.
 * stop <code>adb logcat</code> on PC, and attach the <code>log.txt</code> to your issue report on github along with detailed steps of the bug, and use the Android label.
-(Note: adb can be <code>./adb.exe</code> on Windows. Use internet for help on any of the steps if needed, this is supposed to be a preliminary guideline.)
+(Note: adb can be <code>./adb.exe</code> on Windows. Use internet for help on any of the steps if needed, this is supposed to be a preliminary guideline. Steps might slightly differ based on manufacturer or Android version.)
+=== Turning off Developer Mode ===
+Go to System > Developer Options > Turn off <code>Use developer options</code> toggle.