Difference between revisions of "Android"
From The Battle for Wesnoth Wiki
(→Playing controls: add attack info) |
(→Logs and debugging steps: add info on how to enable taps (link to external)) |
||
| Line 17: | Line 17: | ||
(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.) | (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.) | ||
| + | |||
| + | === Enabling taps === | ||
| + | It is useful for debugging purposes, especially if you're sharing a screen recording of your bug, to show where you're tapping on the screen in the screen recording. See [https://discussio.zendesk.com/hc/en-gb/articles/4625151970065-How-to-Show-Taps-for-Mobile-Screen-Sharing-on-Android here] for how to enable that. | ||
=== Turning off Developer Mode === | === Turning off Developer Mode === | ||
Go to System > Developer Options and turn off the '''Use developer options''' toggle. | Go to System > Developer Options and turn off the '''Use developer options''' toggle. | ||
Revision as of 15:13, 30 September 2025
This pages contains some specific information about the Battle for Wesnoth new Android port (1.19+)
Contents
Playing controls
- Tap a unit to select/deselect 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.
- Drag from attacker unit towards attacked unit to attack.
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 logcator 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), thenadb logcat > log.txt(oradb logcatand copy from terminal). Run Wesnoth on phone. Reproduce the crash. - stop
adb logcaton PC, and attach thelog.txtto 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.)
Enabling taps
It is useful for debugging purposes, especially if you're sharing a screen recording of your bug, to show where you're tapping on the screen in the screen recording. See here for how to enable that.
Turning off Developer Mode
Go to System > Developer Options and turn off the Use developer options toggle.