Maybe you should turn on ndroid.app.background_running in your
AndroidManifest.xml
<!-- Background running -->
<!-- Warning: changing this value to true may cause unexpected
crashes if the
application still try to draw after
"applicationStateChanged(Qt::ApplicationSuspended)"
signal is sent! -->
<meta-data android:name="android.app.background_running"
android:value="true"/>
<!-- Background running -->
On Thu, Mar 3, 2016 at 3:56 AM, Jason H <jh...@gmx.com> wrote:
> So there seems to be some conflicting information out there about how to
> do this in Qt.
> It seems that in 5.3, because the Qt thread as not the UI thread,
> everything worked. then in 5.4, that stopped working? This was supposed to
> be fixed in 5.5? Anyhow, I'm working with 5.6 now. I have enough of a
> platform shim in place that I
>
> I wrote a bunch of code that assumed that I'd be running any time. I've
> successfully locked the CPU awake and detected foreground/background
> switches, but it seems that once I get to
> Qt::ApplicationState(ApplicationSuspended) my app is unable to do anything.
>
> Any help?
>
> _______________________________________________
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
