This bug is not in powerd itself, it's usually caused by the amount of events that are either on hold before suspending, or that are triggered after resuming back (which makes the device to take a while to fully resume back).
We landed quite a few changes as part of OTA3 that reduced such events (battery, console, etc), which improved quite a bit. I still saw this happening once, but then wasn't really able to reproduce it anymore.
This bug is not in powerd itself, it's usually caused by the amount of events that are either on hold before suspending, or that are triggered after resuming back (which makes the device to take a while to fully resume back).
We landed quite a few changes as part of OTA3 that reduced such events (battery, console, etc), which improved quite a bit. I still saw this happening once, but then wasn't really able to reproduce it anymore.