I can explain your result. The issue is specifically a race condition with the lock screen triggering after the suspend sequence starts. The driver change that helps it flushes content during the suspend sequence to ensure engines are not running when suspend starts.
By using pm utils you don't trigger the lock screen. The proper solution is the patch linked in the bug I referenced.
I can explain your result. The issue is specifically a race condition with the lock screen triggering after the suspend sequence starts. The driver change that helps it flushes content during the suspend sequence to ensure engines are not running when suspend starts.
By using pm utils you don't trigger the lock screen. The proper solution is the patch linked in the bug I referenced.