[T-Mobile Galaxy Note 4 Android Development] gekkehenkie11:
So I thought, why not check it out right now :) The problems that existed on CM11/i9500 are not present. In fact, everything looks really normal from the log:

12-23 13:44:45.500 I/PowerManagerService( 784): Waking up from dozing (uid 1000)...

12-23 13:44:45.505 D/PowerHAL_TR_Ext( 784): cm_power_set_interactive_ext: enabling input devices

12-23 13:44:45.507 V/KeyguardServiceDelegate( 784): onScreenTurnedOn(showListener = com.android.internal.policy.impl.PhoneWindowManager$2@88c0c7a)

12-23 13:44:45.588 I/Sensors ( 784): Acc old sensor_state 0, new sensor_state : 1 en : 1

12-23 13:44:45.589 I/DisplayPowerController( 784): Blocking screen on until initial contents have been drawn.

12-23 13:44:45.590 V/KeyguardServiceDelegate( 784): **** SHOWN CALLED ****

12-23 13:44:45.601 D/audio_hw_primary( 336): adev_set_parameters: enter: screen_state=on

12-23 13:44:45.601 E/audio_a2dp_hw( 336): adev_set_parameters: ERROR: set param called even when stream out is null

12-23 13:44:45.616 E/native ( 784): do suspend false

12-23 13:44:45.636 E/Sensors ( 784): Sensor : Meta event

12-23 13:44:45.787 E/WifiStateMachine( 784): WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=e8:40:f2:21:f2:12 RSSI=-68

12-23 13:44:45.806 I/wpa_supplicant( 1116): wlan0: CTRL-EVENT-SCAN-STARTED

12-23 13:44:45.874 E/PowerHAL_TR_Ext( 784): Error opening /sys/class/input/event20/device/enabled: Permission denied

12-23 13:44:45.879 I/QCOM PowerHAL( 784): Got set_interactive hint

12-23 13:44:45.880 D/PowerManagerService-JNI( 784): Excessive delay in setInteractive(true) while turning screen on: 375ms

12-23 13:44:45.881 W/art ( 784): Long monitor contention event with owner method=void com.android.server.power.PowerManagerService.wakeUpInternal(long, int) from PowerManagerService.java:1144 waiters=0 for 271ms

12-23 13:44:45.892 W/art ( 784): Long monitor contention event with owner method=void com.android.server.power.PowerManagerService.wakeUpInternal(long, int) from PowerManagerService.java:1144 waiters=1 for 277ms

12-23 13:44:45.898 D/SurfaceFlinger( 307): Set power mode=2, type=0 flinger=0xb6a62000

12-23 13:44:45.898 D/qdhwcomposer( 307): hwc_blank: Unblanking display: 0

12-23 13:44:45.909 I/DisplayManagerService( 784): Display device changed: DisplayDeviceInfo{"Built-in Screen": 1440 x 2560, 60.0 fps, supportedRefreshRates [60.0], density 640, 508.0 x 516.063 dpi, appVsyncOff 0, presDeadline 17666667, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT}

12-23 13:44:45.912 W/art ( 784): Long monitor contention event with owner method=void com.android.server.wm.WindowManagerService$H.handleMessage(android.os.Message) from WindowManagerService.java:7606 waiters=0 for 204ms

12-23 13:44:45.917 V/ActivityManager( 784): Display changed displayId=0

12-23 13:44:45.952 I/DisplayPowerController( 784): Unblocked screen on after 362 ms

12-23 13:44:46.197 I/qdhwcomposer( 307): handle_blank_event: dpy:0 panel power state: 1

12-23 13:44:46.199 E/qdexternal( 307): writeHPDOption: file write failed '/sys/devices/virtual/graphics/fb1/hpd'

12-23 13:44:46.199 D/qdhwcomposer( 307): hwc_blank: Done unblanking display: 0

12-23 13:44:46.202 D/SurfaceControl( 784): Excessive delay in setPowerMode(): 306ms

12-23 13:44:46.208 I/DreamManagerService( 784): Gently waking up from dream.

12-23 13:44:46.212 I/DreamManagerService( 784): Leaving dreamland.

12-23 13:44:46.214 I/DreamController( 784): Stopping dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0

Taking from the log, it has the display unblanked 700 ms after pressing the power key. It seems slightly slower though, in my experience it's like 1 second, not sure why that is.. Anyway changing this would mean changing default AOSP code (the powermanagerservice) I dont think this is a good idea. When Samsung releases Lollipop, I'll check out if they changed something and if their wakeup is faster, I'll try to mimick it. However this is not bugging me much. On CM11/i9500 it would take almost 2 seconds, that's quite long, but 700ms-1000ms I can live with.