- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Because no one cares about this at Microsoft for years and years to address this, and it is a major issue for laptops, I ask if Intel could address this in their drivers, or be so nice, to ask someone at MS to address this maybe finally, to make laptops maybe once and for the first time in history, be usable with Windows 10.
The issue is as simple as it is dangerous: To this day, you CANT define for a modern standby device in Windows 10 what devices are allowed to wake up the device. This may not be an issue for tablets but it is for laptops. And that all laptops these days just come with modern standby support and no S3 sleep anymore.
Issue: Even with lid closed, a simple movement of a connected bluetooth mouth or keyboard wakes the laptop from modern standby and the laptop could easily burn to death with random high performance operations happening.
A normal user would assume, that if the lid is closed of a laptop, it stays sleeping, until the lid is opened again. This is NOT the case with a laptop and Windows 10 and modern standby. It is not acceptable to turn of your BT mice and keyboards before closing a laptop lid.
How to reproduce:
- use a bluetooth mouse
- ping the laptops' WIFI via a 2nd device in LAN
- put the modern standby enabled laptop to sleep via lid closing
- ping stops, modern standby starts
- move the bluetooth mouse
- ping starts again, laptop is fully awake even with lid closed
- even waiting for minutes now, the laptop wont enter modern standby anymore, ping is working forever, until the manual sleep timer kicks in. Though the display off timer should trigger it at lock screen after 15 seconds or so, which it doesn't (another bug)!
It is not wanted by design, that a bluetooth device could wake up a laptop, with its lid closed.
Intel needs to address this in the driver, because MS is not interested in looking into this, even it is a dangerous issue, burning laptops to death with lids closed in the bag.
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Only guess I've is that the OS (HID stack specifically) is not getting LID closed event from the BIOS. The systems go through hardware certification (or WHQL) for modern standby before release. So it is not BT issue or processor/chipset issue. 2 other dells systems do not have this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great! Those registry keys were preventing lid notification to the hid stack. These keys were supposed to be OEM customized.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »