The table listed on the Wakeup page describes the functioning of each of the wake causes depending upon how the terminal fell asleep. You'll notice the first column of the table lists all the potential wake causes.  The subsequent columns describe the reasons the terminal would have suspended.  Either the power key or an API or a timeout.  (in WM, the system can't distinguish between API or timeout so they're lumped together as "other") So, if we take an example.  Look for USB Connect as a wake source.  Then follow that row over to the PwrKey column.  There's a "YES" in that box.  This means that if the terminal fell asleep because the user pressed the power key, then a USB connect event will wake the terminal. As another example, look further down the table for the Trigger wake cause.  Follow the row to the right and you'll see "NO" under the Power Key and if you keep going across, you'll see "YES" under the API.  This means that if the terminal falls asleep because the user presses the power key, then the trigger will NOT wake the terminal.  But, if the terminal falls asleep because an application called the API to suspend the terminal then the trigger WILL wake the terminal.