[T-Mobile Samsung Galaxy S6] lizaSB:
Does your device consistently keep waking up when pulling it out of your pocket? I would think that our variants shouldn't be too different but apparently samsung just wants to screw with us.

I'm currently digging through some CM documentation and finding a few things.

In system UI does your bools.xml contain

<bool name="doze_pickup_performs_proximity_check">false</bool>

Also, in framework-res integers (mine is set to 1 already =/ ):

<!-- Control the behavior when the user short presses the power button.
0 - Nothing
1 - Go to sleep (doze)
2 - Really go to sleep (don't doze)
3 - Really go to sleep and go home (don't doze)
-->
<integer name="config_shortPressOnPowerBehavior">1</integer>

Some more documentation:

<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
device from the display on/off state.
When false, autosuspend_disable() will be called before the display is turned on
and autosuspend_enable() will be called after the display is turned off.
This mode provides best compatibility for devices using legacy power management
features such as early suspend / late resume.
When true, autosuspend_display() and autosuspend_enable() will be called
independently of whether the display is being turned on or off. This mode
enables the power manager to suspend the application processor while the
display is on.
This resource should be set to "true" when a doze component has been specified
to maximize power savings but not all devices support it.
Refer to autosuspend.h for details.
-->
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">false</bool>

<!-- Power Management: Specifies whether to decouple the interactive state of the
device from the display on/off state.
When false, setInteractive(..., true) will be called before the display is turned on
and setInteractive(..., false) will be called after the display is turned off.
This mode provides best compatibility for devices that expect the interactive
state to be tied to the display state.
When true, setInteractive(...) will be called independently of whether the display
is being turned on or off. This mode enables the power manager to reduce
clocks and disable the touch controller while the display is on.
This resource should be set to "true" when a doze component has been specified
to maximize power savings but not all devices support it.
Refer to power.h for details.
-->
<bool name="config_powerDecoupleInteractiveModeFromDisplay">false</bool>

I set powerDecoupleInteractiveModeFromDisplay to false and now I can interact with the notifications while dozing, which is the desired behavior. We want to wake our device without touching the power button

---------- Post added at 11:13 AM ---------- Previous post was at 11:06 AM ----------

It's almost working perfectly for me... My issue just seems to be keeping the doze service active. It works plenty fine if all you want it for is for incoming notifications

---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------

This is the line I added that doesn't seem to be anywhere in aosp documentation. I haven't tried removing it yet -- I'll give it a shot and see if shaking my device still wakes the screen