@Christian-Ehrlicher It took me a whole day, but I finally understood that you were referring to the fact that exit()/quit() can't be used in the same vein as requestInterruption()/isInterruptionRequested() or terminate(). I first learned about basic QThread semantics so long ago (more than a decade I think), that the fact that it's possible to not understand that got completely lost on me.

@SGaist That seems to be the solution, haha! Thanks.

@Bonnie said in QThread does not quit, why?: The solution is QObject::connect(myControl, &Control::finished, myThread, &QThread::quit, Qt::DirectConnection); And where does it say that this slot is thread-safe? @robro Just quit the thread before you exit the application. QObject::connect(&app, &QApplication::aboutToQuit, myCtrl, &Control::deleteLater); QObject::connect(myCtrl, &Control::finished, &myThread, &QThread::quit); QObject::connect(&myThread, &QThread::finished, myCtrl, &Control::deleteLater); //< This is needed Which translates simply to: qDebug() << "Started Waiting:"; myThread.quit(); myThread.wait(); // Wait for thread to quit qDebug() << "Quit";

Ok, thanks, I think I have all information I need now.

@vlada said: I tried to catch all possible signals but I didn't get any of them. I think it is because of the way Qt applications are run on Android. Because on Android is run a Java application which runs my app as a library. Assuming this is true, then indeed, you'll need to write a bit of java and only if the Java runtime allows interception of the signals. I don't know if it's worth it, but it shouldn't be too hard.

@Chris-Kawa, i see what you did there! :d thanks, didn't even think about that approach before! very useful!