f9f39cc4a8
is going idle. The inputs to DeviceIdleController (alarm manager, sensors) hold wake locks while they call it. But then the real work happens in a handler which is outside of the wakelock, so listeners don't get a chance to run right away, which in the case of NetworkPolicyManager means the device is in a higher power state than it should be. It's not clear that this will 100% fix the bug, because NetworkPolicyManagerService also has its own internal Handler, and isn't holding its own wakelock for this, but this change allows NPMS to be fixed if it really needed to be. Bug: 31900521 Change-Id: I706045aa189147824c9214c57abc13993aee9a5b