I would argue that this method isn't actually as long as it seems: 50 lines if you exclude comments[1]. I could see a case for extracting the screen/CPU lock logic[2], which would reduce it to 35 lines. But factoring out 4-5 methods would be more difficult to read, because then in order to understand the code, you must (a) understand the flow of method calls, (b) ensure those other methods are only used in the expected place, and (c) be aware of how state can change if those methods are called at unexpected times.

I respect Uncle Bob's quip, but having a bunch of small methods is not always better than having a single larger method (especially when the task at hand is something like this constructor: setting up one thing at a time). In this case, DRY is my guiding light. 

[1]: https://gist.github.com/mcav/11269865
[2]: https://gist.github.com/mcav/11269934