首先，让我们假设它锁定， doze 需要多少时间，用于保存电量？ 另一方面，如果智能锁定是作用（如通过地理位置），保持设备解锁几个小时（是六个限制，右？），这将如何影响"打瞌睡" 功能？< / p>
Consider a device that was left on a table, unplugged, and no movement. After sometime, the screen turns off, and the screen lock may (or may not) be auto activated, according to lock and smart lock settings.
Firstly, let's assume its locked, how much time is required for Doze, working to save power?
On the other hand, if the smart lock is acting (like by geographic location), keeping device unlocked for several hours (is six the limit, right?), how will this affect "Doze" functionality?
Idle time is not specified by Google and I guess this is implemented differently by OEMs
Quoting from Google documentation Optimising for Doze and stand by (emphasis added)
If a user leaves a device unplugged and stationary for a period of time, with the screen off, the device enters Doze mode. In Doze mode, the system attempts to conserve battery by restricting apps' access to network and CPU-intensive services. It also prevents apps from accessing the network and defers their jobs, syncs, and standard alarms.
Periodically, the system exits Doze for a brief time to let apps complete their deferred activities. During this maintenance window, the system runs all pending syncs, jobs, and alarms, and lets apps access the network.
Edit : This may answer from a user perspective as this is what developers are apparently planning 9 minute interval
Dianne Hackborn17 Nov 2015 +Petr Nalevka Sorry scheduling alarms so frequently is currently not supported in doze....For what it's worth, the minimum time between while idle alarms will be changing to 9 minutes at some point relatively soon (even on devices running the current Marshmallow builds).
It is difficult to answer this correctly as
As can be seen from the answer to first part of question, developers seem to be improving / modifying the behaviour of "Doze" functionality and only once it is matured and implemented, one can reach a conclusion.
As can be seen in this post https://stackoverflow.com/questions/33018306/doze-mode-and-foreground-service, thanks to Firelord for highlighting this , documentation by Google is lacking in details and developers/ OEM may implement varying behaviors, so nothing can be said at this point of time with certainty.