ScummVM 2.1.0 unavailliable on google play store

Subforum for discussion and help with ScummVM's Android port

Moderator: ScummVM Team

Post Reply
User avatar
BoTToX
Posts: 3
Joined: Thu Jul 18, 2019 8:46 pm

ScummVM 2.1.0 unavailliable on google play store

Post by BoTToX » Sat Oct 12, 2019 11:23 pm

Only the old 2.0.0 (jan 1 2018) is availliable on google play. (samsung galaxy s8 ans Tab S3)
And .apk don't work (black screen)

Praetorian
ScummVM Developer
Posts: 85
Joined: Tue May 08, 2007 8:54 am

Re: ScummVM 2.1.0 unavailliable on google play store

Post by Praetorian » Sun Oct 13, 2019 3:08 am

BoTToX wrote:
Sat Oct 12, 2019 11:23 pm
Only the old 2.0.0 (jan 1 2018) is availliable on google play. (samsung galaxy s8 ans Tab S3)
And .apk don't work (black screen)
Hello,
The 2.1.0 version on the Google Play store has been recalled for the time being as we work out some outstanding issues that have been reported to us.

The new version changed quite a few things as to how the Android port works (mainly the non-SDL port is now adopted as the Google Play release package) and even though it has introduced quite a few improvements overall, there have been a few regressions too; namely tiny UI text in high resolutions and "loss" of existing game entries and save data made with the old version (fortunately this should not be permanent).

Please be patient for a few more days as we are resolving these issues.

TheHutt
Posts: 2
Joined: Sun Oct 13, 2019 8:21 pm

Re: ScummVM 2.1.0 unavailliable on google play store

Post by TheHutt » Mon Oct 14, 2019 5:46 am

Well... how about not reinventing the wheel every upgrade?

The 2.1 version was automatically installed on my tablet during the night, with the following result:
- All game data, all savegames ( :twisted: ) are lost.
- The GUI was illegible on FullHD resolution: too small buttons and texts.
- The mouse steering has been changed once again.

As you cannot downgrade with GooglePlay, the only way I could go back to 2.0 was uninstalling 2.1 and reinstalling 2.0, resulting in:
- All the game data, all savegames ( :twisted: ) are lost.

Larrynho
Posts: 6
Joined: Fri Aug 11, 2017 7:12 am

Re: ScummVM 2.1.0 unavailliable on google play store

Post by Larrynho » Mon Oct 14, 2019 11:11 am

Praetorian wrote:
Sun Oct 13, 2019 3:08 am
BoTToX wrote:
Sat Oct 12, 2019 11:23 pm
Only the old 2.0.0 (jan 1 2018) is availliable on google play. (samsung galaxy s8 ans Tab S3)
And .apk don't work (black screen)
Hello,
The 2.1.0 version on the Google Play store has been recalled for the time being as we work out some outstanding issues that have been reported to us.

The new version changed quite a few things as to how the Android port works (mainly the non-SDL port is now adopted as the Google Play release package) and even though it has introduced quite a few improvements overall, there have been a few regressions too; namely tiny UI text in high resolutions and "loss" of existing game entries and save data made with the old version (fortunately this should not be permanent).

Please be patient for a few more days as we are resolving these issues.
May I ask why the non SDL port is adopted as the release package? I found the SDL version more suitable for us Android users :/ Not that Im Complaining; Scummvm is great but SLD was more convenient.

Praetorian
ScummVM Developer
Posts: 85
Joined: Tue May 08, 2007 8:54 am

Re: ScummVM 2.1.0 unavailliable on google play store

Post by Praetorian » Mon Oct 14, 2019 3:18 pm

Larrynho wrote:
Mon Oct 14, 2019 11:11 am
May I ask why the non SDL port is adopted as the release package? I found the SDL version more suitable for us Android users :/ Not that Im Complaining; Scummvm is great but SLD was more convenient.
Ultimately, it was a team decision which I agree with.

Some of the benefits that I'm seeing for it are:
  1. The official ScummVM buildbot built daily development builds only for the non-SDL port (and always did). That to me means this has always been the version that most people were testing with. So, it should follow that this was the most tested version.
  2. The non-SDL version got more love from our developers the last few months. All Android port related patches were to improve this version.
  3. The non-SDL version currently supports older devices that the SDL port did not.
  4. The SDL port uses and depends on a few hacks and a difficult to maintain /update process for its build toolchain. Since I have a few Android devices and I wanted to set up the app to test Blade Runner on them, I had to set up building environments for both SDL and non-SDL ports. In fact, I had to update some of the scripts and re-write the instructions on how to build the SDL port based on my experience. Personally, even though I appreciate the extra functionality, I hated that process. Conversely, the non-SDL port has a much more straightforward way to set up its toolchains and we were able to cross-compile more 3rd party libraries for it and up-to-date versions of those already included (our wiki page for the build process is still outdated but we now have various easy to setup environments for this version including dockerised processes).
  5. Performance-wise I have noticed no differences, and all the recent code updates for the port helped a lot.
We knew that moving back to the plain port would result to some loss of existing functionality (while gaining other new functionalities at the same time), but in the end I do not regret the decision of the team.
I, along with other team people I have discussed with, do intend to keep improving the non-SDL port and building that functionality into it in the future.

Praetorian
ScummVM Developer
Posts: 85
Joined: Tue May 08, 2007 8:54 am

Re: ScummVM 2.1.0 unavailliable on google play store

Post by Praetorian » Mon Oct 14, 2019 3:39 pm

TheHutt wrote:
Mon Oct 14, 2019 5:46 am
...
I apologize for the inconvenience and I recognize that mistakes were made; this is why the Play Store version is currently put on hold, so that it won't affect more people in that way (loss of configuration and save files).

For those who did not uninstall the ScummVM app, someone on reddit posted a temporary workaround that may work for people, while our team is working on a proper solution integrated in our code:
https://www.reddit.com/r/ScummVM/commen ... e/f3ecj6v/
Well... how about not reinventing the wheel every upgrade?
I don't agree with this; we are not reinventing a wheel, and certainly not with "every upgrade".
So, here is what I know:
  • The ScummVM project is based on volunteers work and the Android port has not had dedicated developer(s) maintaining it for a long time (probably more than a year) as far as I know.
  • As mentioned above, the non-SDL port is the only Android port that is built by our buildbot daily. This was for all we know the version that people were testing with, during the test phases that were officially announced prior to release.
  • Consequently this version's outstanding bugs (crashes/ SD card paths etc) were the focus of any developers (including myself) that shifted time to the port in the days leading up to the release.
  • As far as I know there were no bug reports on our tracker about the issue of small text in high resolutions and, while I agree that it's a real issue which needs to be resolved immediately, my three android devices (phones) are not of such high resolution. So personally I never encountered this issue quite as hard as it hit people with tablets or more hi-def devices than mine.
  • The other bugs you are reporting are a result of the upgrade process between the SDL-port and the non-SDL port, because for whatever reason the SDL port version changed the way these important paths are set up, and we failed to catch this in time (...).
We're still working on the issues and hope to have a proper solution soon.

TheHutt
Posts: 2
Joined: Sun Oct 13, 2019 8:21 pm

Re: ScummVM 2.1.0 unavailliable on google play store

Post by TheHutt » Mon Oct 14, 2019 5:17 pm

I am apologizing for my rather harsh words.

Larrynho
Posts: 6
Joined: Fri Aug 11, 2017 7:12 am

Re: ScummVM 2.1.0 unavailliable on google play store

Post by Larrynho » Tue Oct 15, 2019 10:10 am

Praetorian wrote:
Mon Oct 14, 2019 3:18 pm
Larrynho wrote:
Mon Oct 14, 2019 11:11 am
May I ask why the non SDL port is adopted as the release package? I found the SDL version more suitable for us Android users :/ Not that Im Complaining; Scummvm is great but SLD was more convenient.
Ultimately, it was a team decision which I agree with.

Some of the benefits that I'm seeing for it are:
  1. The official ScummVM buildbot built daily development builds only for the non-SDL port (and always did). That to me means this has always been the version that most people were testing with. So, it should follow that this was the most tested version.
  2. The non-SDL version got more love from our developers the last few months. All Android port related patches were to improve this version.
  3. The non-SDL version currently supports older devices that the SDL port did not.
  4. The SDL port uses and depends on a few hacks and a difficult to maintain /update process for its build toolchain. Since I have a few Android devices and I wanted to set up the app to test Blade Runner on them, I had to set up building environments for both SDL and non-SDL ports. In fact, I had to update some of the scripts and re-write the instructions on how to build the SDL port based on my experience. Personally, even though I appreciate the extra functionality, I hated that process. Conversely, the non-SDL port has a much more straightforward way to set up its toolchains and we were able to cross-compile more 3rd party libraries for it and up-to-date versions of those already included (our wiki page for the build process is still outdated but we now have various easy to setup environments for this version including dockerised processes).
  5. Performance-wise I have noticed no differences, and all the recent code updates for the port helped a lot.
We knew that moving back to the plain port would result to some loss of existing functionality (while gaining other new functionalities at the same time), but in the end I do not regret the decision of the team.
I, along with other team people I have discussed with, do intend to keep improving the non-SDL port and building that functionality into it in the future.
That was a very concise answer, thank you :! :D

As a dev myself, I undestand very dearly the problem of maintaining a hacky version vs having a proper maintained app, even if you lose some of the benefits of the hacky one.

Post Reply