[delphin]

I agree that it's a pain that you can't just have the reader continue to display your last page, then seamlessly pick up the device and return to reading where you left off.

Sadly, it doesn't look like this can be done by hacking the PRS-T1 software, because it would appear that the present generation of hardware can't wakeup on any button press except the power button.

But it's not just Sony . . . ALL the manufactures of eInk devices seem to have totally missed the boat in the way that 'sleep' mode works.

For readers like the Sony and Nook that have physical page turn buttons, a better solution would have been to design the hardware to allow the reader to wake from sleep whenever a page turn button is pressed, and then transparently process the page turn.

In Android, waking from sleep is fast enough, and eInk page turns are slow enough, so the slight added delay would go virtually unnoticed, and 'sleep' would be totally hidden from the user most of the time.

Using this arrangement, the reader would enter and exit sleep transparently without the user even knowing (unless the user specifically WANTS a 'screensaver' type image, and selects one under settings.)

To make this work, the eReader device would need to be designed so that its Power Saving Circuitry can wake the CPU from Sleep and pass it the proper button-press interrupt after ANY button press (including HOME, BACK and Page-Turn buttons)

This approach would take full advantage of eInks zero power page retention along with Androids super quick fractional-second wakeup times, to make the eInk reading experence more like a real book, because the reader would stay on the last page almost indefinitely, while allowing the user to seamlessly return to reading where they left off (unless the battery is so low that a full shut down is necessary).

To avoid accedental button presses (when the reader is slipped into a bag for example) the user would 'lock' the device by simply pressing the power button to manually enter 'sleep-lock' mode. In this mode the screen would freeze on the present page with a small lock icon in the status area (or go to screen-saver image if configured under settings).

This would give the best of both worlds - protection from accedental button presses when needed, but seamless reading without be forced to deal with sleep mode at other times.

This seems so obvious that one wonders how Sony, Amazon and B&N missed it? Duhhh!

Oh well, at least Sony got rid of the totally STUPID 'swipe to wakeup' garbage that most Android devices use, electing instead to just slightly recess the power button to prevent accidental activation. The Nook Color, for example does force the user to deal with this silly Android 'swipe-to-wake' crap (which an eReader needs like a fish needs a bicycle).

This pretty much sums up my frustration with Android (and Linux/POSix type O.S.'s in general) where standardization IS needed there is NONE, and when they DO 'standardize' something it's something STUPID.