Android 5.1 Issues

[SamGrant]

When running my app on Android 5.1... if I push the app to the background, then bring it back to the foreground, the UI does not show.

This does not happen on Android 4.x.

Using QT 5.5.

[kolegs]

Are you debugging application? I've noticed that this happens only on debug (android 4.x, dont have device with 5.x), but when I only run application there is no problem

[SamGrant]

Nope. Running the app on-device. Debug and Release mode both exhibit the same thing....once the app is backgrounded and then foregrounded, the UI does not return...

[SamGrant]

Actually, this seems to be a QT 5.5 issue... recompiling with QT 5.4 works.

[SGaist]

Hi,

Sounds like a regression. You should check the bug report system to see if it's something known.

[SamGrant]

Update:
Actually, still getting the same result with 5.4....

Testing on Droid Turbo with Android 5.1....looks like it may be an Android 5.1 issue. Anyone else seen this?

[SamGrant]

Update 2:

using this code seems to help on Android 5.1:
Connections {
target: Qt.application
onStateChanged: {
console.debug("applicationStateChanged: " + Qt.application.state)
if (Qt.application.state === Qt.ApplicationActive) {
applicationWindow.show()
//we're back from idle
}
else {
applicationWindow.hide()
//going to background
}
}
}

[SamGrant]

BUT>>>>>>

That causes Android 4.4.4 to exhibit the behavior.

[SGaist]

You should check and fill a bug report about it. You can also talk about it on the #necessitas IRC channel

[SamGrant]

Actually... Tried it on another Android 4 device (a newer one)...and it works as expected, with the Connections code. Going to try this on other Android 4+ devices before filing a bug report.

The other device was running a 4.4.4 version of Cyanogenmod...so...