Custom port of Qt can't return from Sleep mode
-
I have the following scenario:
-
we have Qt 4.8 ported (by a vendor) to a custom Linux/Android device;
-
the device also has some proprietary APIs for entering low-power modes;
-
the application creates a number of Qt threads for doing various things;
-
when the application calls our sleep function, it goes to low power mode;
-
when the application returns from low power modes, the screen seems to freeze but we know that the application is still running because we see logs from it in the serial port;
Now the question is: what is the proper way to handle this scenario in Qt? Is there some sort of event I can handle before/after entering the low power mode? I'm not sure what are Qt's best practices for dealing with this problem. Can someone point me the direction?
Thank you.
-
-
I have the following scenario:
-
we have Qt 4.8 ported (by a vendor) to a custom Linux/Android device;
-
the device also has some proprietary APIs for entering low-power modes;
-
the application creates a number of Qt threads for doing various things;
-
when the application calls our sleep function, it goes to low power mode;
-
when the application returns from low power modes, the screen seems to freeze but we know that the application is still running because we see logs from it in the serial port;
Now the question is: what is the proper way to handle this scenario in Qt? Is there some sort of event I can handle before/after entering the low power mode? I'm not sure what are Qt's best practices for dealing with this problem. Can someone point me the direction?
Thank you.
@Daniel-Rosa-Franzini
Qt 4.8 is quite an outdated version. It's not guaranteed that it works with modern operating system versions.
Without seeing any code, it's impossible to say why the UI thread hangs.
Amongst many possible reasons, it could be blocking code in the port or in the application. Could also be OS incompatibility. -