Peter L Jones

> 3. The value should increase for each build potentially for release to Google Play Store. If we presume this means a build performed by the Github build actions, then...

> That would then meet requirements 2, 4, 5 and 6. Actually, not 4. We'd still have no way to know if there were local changes without git. So we're...

I'm going to put this into Triage. It needs more thought. I don't know enough about Github automation or the Qt build process, really.

Can someone check with 3.10.0rc1 whether this is still an issue on iOS? This is what I see on my Moto G9 Power (Android 11, 720x1640 pixels):  (Could be...

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...

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

Looks like we need to catch changes to state: https://doc.qt.io/qt-5/qt.html#ApplicationState-enum https://doc.qt.io/qt-5/qguiapplication.html#applicationStateChanged (Same in 6.5: https://doc.qt.io/qt-6/qguiapplication.html#applicationStateChanged) Also this looks interesting - I guess we should honour the request: https://doc.qt.io/qt-5/qguiapplication.html#saveStateRequest https://doc.qt.io/qt-6/qguiapplication.html#saveStateRequest

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...

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...

| | | |--|--| | https://docs.gradle.org/current/userguide/compatibility.htmlhttps://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...