Thanks dkb1898 and again Mike1098 for your inputs.
Dkb1898, would you mind showing us your sleepstudy mW’s and “High, Moderate, Low” system levels in you sleep studies (of course not using Mike1098’s USB workaround). (as
a reminder, under cmd prompt, "powercfg /sleepstudy"). Also, if you can, would you mind testing a scenario where you fully charge to 100% and leave plugged in for an extended period (say overnight) then unplug,
then put to sleep under battery power and then wait 10 minutes before waking (if woke, wait another 10 minutes and wake again for a 2^nd^ test)?
Just so you know, this scenario consistently caused NoWake for a few days, either in the 1st wake attempt or 2nd, then it stopped happening.
It then only occasionally caused a NoWake in my SP4.
Sometimes, associated with that occasional NoWake, I had also changed wifi signals and in each case these NoWake scenarios had a 6+ hour full charge.
If I did a full charge in some short interval, say under 3 hours, I would not have any issues waking (but those scenarios used the same wifi signal).
I seem to have found a very specific NoWake scenario in my SP4 and it has something to do with miss information after a full charge and possibly combined with changing wifi signals while in sleep.
No doubt frustrating.
In the ‘test for wake after full charge’ scenario, I would typically use <20mW’s per hour (and often 0mW’s) as well as Green-Low System Activity.
These results and the fact that my NoWake only occurs when the sleep usage is likely low suggests to me that there is a link.
After a while, my sleep uses consistent energy per hour and it has yet to have a NoWake after the 4/19 update but only after I get passed the initial wakes from 100% battery.