This version is the last one to support API level 17 (Jelly Bean).
It also gets rid of all remnants from the old binutils/GCC toolchain.
This also migrates from LLVM 9 to LLVM 12.
- Use a SVG asset to allow for better scalability
- Make the controller visible when touching the screen
- Allow for oblique moving by placing finger between two directions
- Add more buttons on the center area of the screen (GUIDE, START, LEFT
STICK, RIGHT STICK) and simplify right area (only four buttons)
- Don't track all fingers, only the ones needed
- Cleanup now unused code
This was previously removed in commit 5cb87c1eca
We removed it when nearing the (then) upcoming 2.7.1 release, Play Store blocked the apk publishing because of this category's inclusion.
At the time, Play Store's error message was:
The app is published as an apk that supports TV. In other words, it contains <category android:name="android.intent.category.LEANBACK_LAUNCHER"/>
under one of the intent-filter of the main activity . It must be published as an app bundle instead.
Which was due to "Following June 30, 2023, Google Play will no longer support TV app updates in APK. All TV app updates must be published with Android App Bundles (AAB)."
Since 2.8.0 we publish to the Play Store in app bundle format, so it should be ok to restore the category. However, this does not necessarily mean
that the app will work on Android / Google TVs without issues. More testing and user feedback might be required.
Some bluetooth keyboards also need "navigation" supported as configuration change
Tested with a new Lamtech bluetooth (BLE5) keyboard and also this is suggested here as well:
https://stackoverflow.com/a/27238892
Since June 30, 2023 Play Store requires TV apps that use this category to use the app bundle distribution model
Since we currently build separate APKs this removal is a temporary measure for the upcoming release of 2.7.1.
However, we should re-instate the tag when we switch to the App Bundle distribution module and perhaps investigate, test
and resolve any other issues related to running the ScummVM Android app for TVs.
- Add a python script (generate-android-i18n-strings.py)
that generates the translated android strings.xml as per:
https://developer.android.com/guide/topics/resources/providing-resources#AlternativeResources
It considers the dists/android/res/values/strings.xml file as
a base template to generate those translated strings.xml files.
- The python script also generates a fake cpp with strings from
dists/android/res/values/strings.xml. These strings will be picked
up by gettext to make it translatable. If there is any change in the
original strings.xml file, we won't have to worry about the changes
in cpp file.
- Add documentation for the generate-android-i18n-strings.py script
Le Philousophe
Eugene Sandulenko
antoniou79
CadiH
Ankush Dutt
Lothar Serra Mari
Cameron Cawley