My K3 is often used for work related stuff, and I need to have te same page active for longer than the 10 minutes or so before the kindle goes into sleep mode.

For the K3 you can temporarily disable the screensaver / sleep mode with the ;debugOn, ~disableScreensaver command.

Does anyone know if this works for the Paperwhite as well?
Or even better, can you change the settings for sleep mode or disable it altogether in het regular menu's? Changing the time out period from 10 to 30 minutes would solve my problem.

My K3 is often used for work related stuff, and I need to have te same page active for longer than the 10 minutes or so before the kindle goes into sleep mode.

For the K3 you can temporarily disable the screensaver / sleep mode with the ;debugOn, ~disableScreensaver command.

Does anyone know if this works for the Paperwhite as well?
Or even better, can you change the settings for sleep mode or disable it altogether in het regular menu's? Changing the time out period from 10 to 30 minutes would solve my problem.

Thank you for your answers!

There's no regular menu access, but you can use the "~ds" command on the Paperwhite to disable the screen saver.

Where do you type this "~ds" command and do you need to somehow turn debug on and then off and if so, then how?

You simply put that in the search bar. See Searchbar Shortcuts for instructions and other shortcuts. For PW you need scroll down to section 7.1.1, but it is better explained in the KT section.

Update: Possible undesired sideeffect is that you cannot put the PW to sleep by closing the cover. If you close the cover, it simply turns the light off. If you push the power button shortly, nothing happens. To put PW to sleep, you must push the power button for several seconds to enter the white screen sleep mode. To restore normal behavior, a restart is required. If I get some time in the morning, I will add that to the Wiki.

Does this work for Paperwhites with ads enabled? Also, when you turn it on, will it go straight to your book or will you still have to swipe to remove the ad?

Yes this works on SO-PW. Seeing the ad depends on how you wake up. When you wake up with the button, I believe you never see the ad (if it works like on the KT). I don't have a SO-PW model to check, so I could not tell you if the white screen sleepmode will show an ad or not if you wake up by opening the cover. See post #5 (mine) in the update part for limitations of the ~ds mode.

Does the Kindle have a default sleep timeout, or does the ~ds command kill sleep altogether? I'd like to permanently keep the screensaver off with my paperwhite, but I'm not sure I want it badly enough to come at the expense of battery life.

You simply put that in the search bar. See Searchbar Shortcuts for instructions and other shortcuts. For PW you need scroll down to section 7.1.1, but it is better explained in the KT section.

Update: Possible undesired sideeffect is that you cannot put the PW to sleep by closing the cover. If you close the cover, it simply turns the light off. If you push the power button shortly, nothing happens. To put PW to sleep, you must push the power button for several seconds to enter the white screen sleep mode. To restore normal behavior, a restart is required. If I get some time in the morning, I will add that to the Wiki.

Hi, thanks for this tip, I confirm that it works, you only have to type in the search bar of Paperwhite "~ds" to remove the screensaver

It shouldn't drain the battery quicker, as it only takes power to change the screen. To NOT change the screen would not take any power.

Of course even in sleep mode, "behind the scenes" activities such as indexing continue, but *additional* battery drain that occurs in ~ds mode that does not occur in sleep mode is the power required to operate the touch screen. The screen is non-responsive in sleep mode while it continues to detect taps in ~ds mode.

There is measurable additional battery drain when the device uses infrared touch detection. I'm not sure if the capacitive sensing method used on the older Kindles uses enough power to be an issue, but it has to use *some* power.