Qt launcher for Android

[kambala-decapitator]

• Qt launcher now builds for Android
• old launcher and most Java code removed
• gradle project adjustments to satisfy androiddeployqt assumptions
• SDL for Android updated to 2.26.5
• added launcher option to ignore SSL errors when downloading mods list - disabled by default, useful on old OSs that no longer update system certificates
• launcher's icons and translations are now packaged inside the binary (using Qt resource system) for all platforms
• Android additionally packages config and Mods dirs inside the binary and unpacks that at launcher start: this replaces packing them in a zip and unpacking with Java code
• Qt code to copy oh3 files from existing directory doesn't work on Android, so it was taken from the old Java implementation

[kambala-decapitator]

dev docs to be updated

[nullkiller]

Abort message: 'terminating with uncaught exception of type std::runtime_error: Resource with name CONFIG/FILESYSTEM and type JSON wasn't found.' samsung

[kambala-decapitator]

Abort message: 'terminating with uncaught exception of type std::runtime_error: Resource with name CONFIG/FILESYSTEM and type JSON wasn't found.' samsung

next build should solve it

[Laserlicht]

Also add the possibility to add scrolling to the elements: Laserlicht/vcmi@0c236da...2ac85d9

After that the only remaining issue is that after changing the language in setup it's not possible to proceed (error with resizing). And some long texts.

[kambala-decapitator]

Also add the possibility to add scrolling to the elements: Laserlicht/vcmi@0c236da...2ac85d9

Nice trick! Will definitely add both changes.

[IvanSavenko]

Is this test change or permanent one?
Github offers more Linux CI runners than macOS runners. Having a lot of macOS runners might slow down CI queue

[kambala-decapitator]

If you could provide Qt host tools (all the stuff in bin folder, plus androiddeployqt) for Linux, then we can use Linux builder again.

[nullkiller]

Was not able to pass initial wizard. First of all language selector is quite laggy. But main problem is file storage. Was not able to upload files there using standard controls. Says can not detect HOMM3 files when I select a folder which previous launcher was able to accept. Maybe copying them manually may work.

[nullkiller]

After manually moving files was able to start random map but not campaign. Was not able to use Install GOG Files

[nullkiller]

Was not able to start a regular map as well. 2024-04-24 21:20:46.730 25602-25722/? E/libc++abi: terminating with uncaught exception of type std::runtime_error: Failed to find object of type randomResource::object

[nullkiller]

#6 pc 0000000000e531a0 /data/app/~~geG1DA1WdRGmf9Cv0LgjYw==/is.xyz.vcmi.daily-2av4AcFJ8wkIA7hvKitSCg==/lib/arm64/libvcmiclient_arm64-v8a.so (VCMI::CObjectClassesHandler::getHandlerFor(std::__ndk1::basic_string<char, std::__ndk1::char_traits, std::__ndk1::allocator > const&, std::__ndk1::basic_string<char, std::__ndk1::char_traits, std::__ndk1::allocator<char

[nullkiller]

Daily build from develop works fine.

[kambala-decapitator]

applied all suggestions

@nullkiller that was upstream issue

[kambala-decapitator]

still need to update dev docs and rename apk to include commit hash / branch name

[IvanSavenko]

Not sure if you've tested it, but there is also bundle_release job that generates .aab for Google Play. Not sure if it will work as it or if it needs adjustments

[kambala-decapitator]

Not sure if you've tested it, but there is also bundle_release job that generates .aab for Google Play. Not sure if it will work as it or if it needs adjustments

only signing fails locally because I don't have the key. I've made adjustments to CI, should work I believe. In the worst case let's fix it after upload attempt fails.

[IvanSavenko]

Was not able to pass initial wizard. First of all language selector is quite laggy. But main problem is file storage. Was not able to upload files there using standard controls. Says can not detect HOMM3 files when I select a folder which previous launcher was able to accept. Maybe copying them manually may work.

I also have this problem right now.
Selecting directory with data / maps / mp3 directories from H3 results in "data not found" message. (exact message: "Failed to detect valid Heroes III data in chosen directory. Please select directory with installed Heroes III data.")
And gog.com installer files are not selectable if I try to pick innoextract option.
Latest beta build on PC works, so does not looks like an upstream regression.

Manual copy still works.
I have not tried data import with previous build, so might not be a new problem.

===

However if files are copied manually, everything seems to be working as intended! Yeah, some things are not very suitable for touchscreens, and I would tone down that "overshot" effect when you try to scrolling too far, especially on mod list.

But these things are quite minor and certainly something we can live with.

[kambala-decapitator]

the gog fix made it to the beta branch, should I retarget PR?

[IvanSavenko]

Sure. Don't see any problems with targeting beta, it is not like we have to merge it in 1.5.0 if you do so.

But probably won't fix not working "copy existing data" option.

[kambala-decapitator]

targetSdkVersion is the reason most probably, thanks!

[dydzio0614]

googling shows this: testOnly="true" means the APK can only be installed via adb (which Android Studio uses)

[kambala-decapitator]

let's see if it's fixed, then will remove the temp commit

[IvanSavenko]

Apk installs, but translations are broken? Changing language does nothing.

Everything else seems to be working so far

[kambala-decapitator]

Apk installs, but translations are broken? Changing language does nothing.

Everything else seems to be working so far

yeah, sorry, copied fix blindly from #4091 and didn't test it. Reverted it and removed the temp commit.

[IvanSavenko]

Seems to be working.

Issues that I've noticed:

• using "Import existing files" leads to UI freeze, with no indication of progress
• Checkboxes are extremely tiny and almost impossible to hit
• Some popup windows (mod screenshots, updates check) look weird due to no window borders
• Buttons to open directories in "Help" tab do nothing -> Fixes to help tab in Launcher #4099
• It is no longer possible to configure "relative cursor mode" since Launcher has no entry in settings for it -> Launcher settings update #4098
• Mod list lags a lot when dragged -> Fix lag on dragging mod list in Launcher on Android #4100

Any way to fix/alleviate 1st issue? Progress bar would be great, but even simple "copying data, please wait" message would be better than UI freeze.

In any case don't see anything critical. Will try to look into these issues after merge. Perhaps post on Discord and if nothing critical is found - merge tomorrow?

[kambala-decapitator]

• using "Import existing files" leads to UI freeze, with no indication of progress

yes, I already mentioned it above

Buttons to open directories in "Help" tab do nothing
Mod list lags a lot when dragged

same on iOS

Any way to fix/alleviate 1st issue? Progress bar would be great, but even simple "copying data, please wait" message would be better than UI freeze.

it's doable, but would need more Java code (and possibly notifying Qt app to show the progress bar / message if we want to display it from Qt)

[IvanSavenko]

it's doable, but would need more Java code (and possibly notifying Qt app to show the progress bar / message if we want to display it from Qt)

Would be great to fix that for 1.5.3. Progress bar would be amazing, but even simple "Copying data, please wait" message will do, whether via Java or via Qt.
This is going to be one of the first things new player is going to see after all.

Can look into rest of issues I've mentioned myself, but probably not this one unfortunately.

[kambala-decapitator]

ok, will try to implement that

[IvanSavenko]

Perhaps merge as it and fix UI freeze in separate PR? What do you think?

If yes - can you rebase PR to fix that merge conflict?

[kambala-decapitator]

Perhaps merge as it and fix UI freeze in separate PR? What do you think?

If yes - can you rebase PR to fix that merge conflict?

Fine for me. Will rebase in the evening.