[Android Apps and Games] Ashray_Vk:
Hey [MENTION=5427507]ssrij[/MENTION]

This is one more log I took where the dozing got inverted even after I updated to the latest version , please let me know if this helps you.

05-17 11:10:36.536 W/ActivityManager(2756): Unable to start service Intent { cmp=com.oasisfeng.greenify/.DozeService } U=0: not found

05-17 11:10:38.257 I/ActivityManager(2756): Start proc 9911:com.suyashsrijan.forcedoze/u0a242 for broadcast com.suyashsrijan.forcedoze/.BootCompleteReceiver

05-17 11:10:53.442 I/ActivityManager(2756): Waited long enough for: ServiceRecord{e949957 u0 com.suyashsrijan.forcedoze/.ForceDozeService}

05-17 11:42:21.392 V/P~DozeTrackerService(9741): Still alive

05-17 11:42:21.392 V/P~DozeTrackerService(9741): Schedule revival

05-17 11:45:43.529 D/DozeTracker(9741): Interactive now

05-17 11:45:43.552 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:45:43.555 I/ForceDozeService(9911): Screen ON received

05-17 11:45:43.559 I/ForceDozeService(9911): Cancelling enterDoze() because user turned on screen and 5000ms has not passed or disableWhenCharging=true

05-17 11:45:43.780 D/DozeTracker(9741): Inactive now

05-17 11:45:43.782 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:45:43.783 I/ForceDozeService(9911): Screen OFF received

05-17 11:45:43.791 I/ForceDozeService(9911): Waiting for 5000ms and then entering Doze

05-17 11:46:05.524 I/ForceDozeService(9911): Entering Doze

05-17 11:46:05.910 I/ForceDozeService(9911): Now forced in to idle mode

05-17 11:46:22.147 I/ForceDozeService(9911): Disabling motion sensors

05-17 11:46:22.387 D/DozeTracker(9741): Enter doze mode

05-17 11:46:23.248 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:46:23.249 I/ForceDozeService(9911): Screen ON received

05-17 11:46:23.249 I/ForceDozeService(9911): Exiting Doze

05-17 11:46:23.303 I/ForceDozeService(9911): Stepped to: ACTIVE

05-17 11:46:23.462 D/DozeTracker(9741): Become active or start idle maintenance

05-17 11:46:24.272 I/ForceDozeService(9911): Re-enabling motion sensors

05-17 11:46:33.994 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:46:33.994 I/ForceDozeService(9911): Screen OFF received

05-17 11:46:33.995 I/ForceDozeService(9911): Waiting for 5000ms and then entering Doze

05-17 11:46:39.266 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:46:39.266 I/ForceDozeService(9911): Screen ON received

05-17 11:46:39.267 I/ForceDozeService(9911): Cancelling enterDoze() because user turned on screen and 5000ms has not passed or disableWhenCharging=true

05-17 11:46:43.091 I/ForceDozeService(9911): Screen is on, skip entering Doze

05-17 11:48:13.487 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:48:13.488 I/ForceDozeService(9911): Screen OFF received

05-17 11:48:13.488 I/ForceDozeService(9911): Waiting for 5000ms and then entering Doze

05-17 11:48:24.632 I/ForceDozeService(9911): Entering Doze

05-17 11:48:24.785 I/ForceDozeService(9911): Now forced in to idle mode

05-17 11:48:27.166 D/DozeTracker(9741): Enter doze mode

05-17 11:48:27.608 I/ForceDozeService(9911): Disabling motion sensors

05-17 11:48:29.370 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:48:29.370 I/ForceDozeService(9911): Screen ON received

05-17 11:48:29.370 I/ForceDozeService(9911): Exiting Doze

05-17 11:48:29.468 I/ForceDozeService(9911): Stepped to: ACTIVE

05-17 11:48:29.559 D/DozeTracker(9741): Become active or start idle maintenance

05-17 11:48:30.374 I/ForceDozeService(9911): Re-enabling motion sensors

05-17 11:48:31.128 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:48:31.128 I/ForceDozeService(9911): Screen OFF received

05-17 11:48:31.129 I/ForceDozeService(9911): Waiting for 5000ms and then entering Doze

05-17 11:48:31.421 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:48:31.421 I/ForceDozeService(9911): Screen ON received

05-17 11:48:31.421 I/ForceDozeService(9911): Cancelling enterDoze() because user turned on screen and 5000ms has not passed or disableWhenCharging=true

05-17 11:48:36.134 I/ForceDozeService(9911): Screen is on, skip entering Doze

05-17 11:48:39.651 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:48:39.651 I/ForceDozeService(9911): Screen OFF received

05-17 11:48:39.652 I/ForceDozeService(9911): Waiting for 5000ms and then entering Doze

05-17 11:48:45.156 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:48:45.157 I/ForceDozeService(9911): Screen ON received

05-17 11:48:45.157 I/ForceDozeService(9911): Cancelling enterDoze() because user turned on screen and 5000ms has not passed or disableWhenCharging=true

05-17 11:48:48.041 I/ForceDozeService(9911): Screen is on, skip entering Doze

05-17 11:48:59.154 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:48:59.154 I/ForceDozeService(9911): Screen OFF received

05-17 11:48:59.159 I/ForceDozeService(9911): Waiting for 5000ms and then entering Doze

05-17 11:49:02.083 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:49:02.083 I/ForceDozeService(9911): Screen ON received

05-17 11:49:02.084 I/ForceDozeService(9911): Cancelling enterDoze() because user turned on screen and 5000ms has not passed or disableWhenCharging=true

05-17 11:49:05.621 I/ForceDozeService(9911): Screen is on, skip entering Doze

05-17 11:49:08.375 I/Timeline(4679): Timeline: Activity_launch_request id:com.suyashsrijan.forcedoze time:2352312

05-17 11:49:08.376 I/ActivityManager(2756): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.suyashsrijan.forcedoze/.MainActivity bnds=[644,1407][851,1701]} from uid 10113 on display 0

05-17 11:49:08.540 I/ForceDoze(9911): android.permission.DUMP already granted, skipping SU check

05-17 11:49:08.544 I/ForceDoze(9911): Service already running

05-17 11:49:08.701 I/ActivityManager(2756): Displayed com.suyashsrijan.forcedoze/.MainActivity: +287ms

05-17 11:49:08.701 I/Timeline(2756): Timeline: Activity_windows_visible id: ActivityRecord{3765834 u0 com.suyashsrijan.forcedoze/.MainActivity t112} time:2352638

05-17 11:49:16.327 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:49:16.327 I/ForceDozeService(9911): Screen OFF received

05-17 11:49:16.328 I/ForceDozeService(9911): Waiting for 5000ms and then entering Doze

05-17 11:49:19.771 I/ForceDozeService(9911): Doze delay: 0ms

05-17 11:49:19.771 I/ForceDozeService(9911): Screen ON received

05-17 11:49:19.771 I/ForceDozeService(9911): Cancelling enterDoze() because user turned on screen and 5000ms has not passed or disableWhenCharging=true

05-17 11:49:22.341 I/ForceDozeService(9911): Screen is on, skip entering Doze

Edit : I think I put a doze filter here. Sorry :/ let me know if you want me to send you a log the next time it happens