[Android Apps and Games] ianmacd:
I've been running ForceDoze for 24 hours now. I used the first day with the app to wade through the 44 pages of this thread, so that I could understand the path of its development to date, and ensure that I wouldn't pose any questions that had already been asked and answered.

As promised, here are my findings.

In general, the app has performed very well in its first day. There have been a couple of times that my phone failed to enter Doze, but most of the time it has worked as intended.

I found that the standard behaviour of immediately dozing on screen off was a little too aggressive for my needs. I often remember something that I have to do just as the screen turns off, so I found that I was getting a lot of dozes < 60 seconds, which I'm guessing might deplete my battery more than simply waiting 60 seconds before dozing, so I have now configured a 1 minute doze delay and that seems to be working well. I gather that this does use a partial wakelock to maintain the delay, but I don't think a few of those in any given 24 hour period is going to hurt me.

This morning, FD's persistent notification had some odd data to show me:

Last screen off: Unknown
Time spent dozing: 24419976 mins

Obviously, something's not quite right there. Every other time I have checked the notification, it has appeared to be accurate.

Speaking of notifications, I have left Greenify's turned on, because it displays not just the most recent, but multiple recent doze sessions. I find this very useful in ascertaining that the system is working as expected. FD's notification could be made more useful in this regard, but it's no problem to leave Greenify's turned on. Obviously, I have Greenify's Aggressive Doze itself turned off.

When I went to bed last night, I plugged my phone into the wall and noticed this morning that this had not caused it to exit Doze, even though Turn off while charging is enabled. Does this option only work if the phone is plugged in before it starts to doze? My device was already dozing before I plugged it in. If this is by design, I can easily achieve my desired behaviour with a Tasker profile.

Ignore lockscreen timeout is working as intended, which is very nice.

I use Smart Lock with my home as a trusted location and the BT connection to my Android Wear watch as a trusted connection. ForceDoze seems to negotiate these correctly.

I'm running Xposed, so I turned on Disable motion sensing for Doze. It's not clear that there are any benefits to doing so with my device, since I'm using an S7E and don't experience the auto-brightness and auto-rotation issues that others have seen, but perhaps there is some benefit to allowing other parts of the system to continue to access the sensors during Doze. In any case, I have read that further Xposed-dependent features are in development.

I was confused about the relationship between FD's app whitelist and the system's battery optimisation whitelist, but this has been dealt with in a separate exchange.

Last but not least, the debug log: It would do wonders for legibility if individual log lines could be terminated with a carriage-return. It's a bit of a jumble at the moment.

Finally, I'd like to compliment the developer on the rapid development cycle of his app, and his great responsiveness in this thread, which he manages without ever sounding impatient or frustrated.

When I first encountered this app just over a day ago, I wondered how it could be that I hadn't previously heard of it, but I see now that the app is actually very new. In spite of that, its XDA thread has run to 44 pages in just 3 weeks, which shows just how involved both community and developer are. That's great, because both apps and XDA are at their best when this kind of perfect symbiosis is attained.

Keep up the great work!