Comment 5 for bug 1552371

For case 1 I always back out of emergency calls or wherever it got to and manually turn it off.
For case 2 yes it dims and turns off.

My hypothesis was that case 1 is caused by some variant of case 2 since it seems to be a relatively new phenomenon and I can't think of anything else that can cause a known wakeup event. However I have no proof of that other than I had debug logging on and saw a lot of BT and pulse activity when the MX4 woke up yesterday. I had moved out of range of my connected headset.

Fix 1: I think the policy for screen management is simple, never turn the display on if proximity is detected, it should not be specific to SMS or calls.
Fix 2: We are waking up on a headset connection not a HID. Connecting this IMO should never turn on the display. Only HID profile devices should turn on the display.
Fix 3: I suspect other BT events are also taking the phone out of suspend and may need to be filtered