@Lucas Malor I did, rather extensively, back in 2014 to get the H2O to suspend reliably. If you get a log without interruptions it means that the device failed to suspend, for example because a particular module is still loaded. In order to suspend successfully, you must do it with a script. Wifi or USB will block it. If you don't wait at least 4 seconds after unloading all necessary modules then the H2O will almost certainly not suspend. If there's a full screen update you have to wait up to 8 seconds to suspend reliably. NB The H2O is an outlier.
The log I posted before shows
exactly the same thing as the one below. I literally "tried it" half a dozen times this afternoon in order to get the result where the log was interrupted.
Code:
2011-02-01T19:09:37+0100
2011-02-01T19:09:40+0100
2011-02-01T19:09:43+0100
2011-02-01T19:09:46+0100
2011-02-01T19:09:49+0100
2011-02-01T19:09:52+0100
2011-02-01T19:09:55+0100
2011-02-01T19:09:58+0100
2011-02-01T19:10:01+0100
2011-02-01T19:11:53+0100
2011-02-01T19:11:56+0100
2011-02-01T19:11:59+0100
2011-02-01T19:12:02+0100
2011-02-01T19:12:05+0100
2011-02-01T19:12:09+0100