@Mike,
Sounds like you expended a lot of effort and did your homework here. Thanks for that. Did you fill out the survey I offered a few pages back? I want to make sure that we capture your successful experience with the 1613 machine in the numbers of users
represented here, because the point of the survey is to hopefully uncover a trend. It seems as if, with your attention to detail and scientific analysis, proof of newer tradeins working should emerge in the survey.
I think we have to be careful, because there have been multiple issues around sleep, hibernate, lack of sleep, and then there were the graphics issues with the detachable screen on the Surface Book. Panos talked about a lot of things, and I don't know that
he said the sleep problem (the one being described in this thread, for the most part) is fixed.
At any rate, let's all keep it civil and work through the problem towards a solution. The minute we start ranting and lobbing insults, the whole group loses credibility
-e
I mostly agree with Mike. I think you lose a little bit of credibility here Chief.
Read the blog post again, it wasn't hard to find. I think it's quite fair to assume that "power management" includes waking from sleep. It's ridiculous to try and give Panos an out there.
They are well aware of the issue and knew exactly what he was trying to address with the blog post. The next day the media is reporting that the issues had been fixed solely on what Panos said. Mission accomplished for them.
MS has failed consumers on this, period. They sold us on their quick wake architecture (watch the video above). Someone mentioned 10's of seconds for Windows Hello, unacceptable. I have a working unit that works as advertised. Wake from sleep, Hello, to
desktop takes seconds total. Something is certainly wrong with a lot of units, I lean towards hardware or maybe fatal flawed updates process that hosed a bunch of machines.