Libra 2 Buttons execute page turns faster than screen taps

bob.f · Yesterday, 05:53 AM

Hi,

I noticed recently on my Libra 2 that page turns via a screen tap are noticeably slower than when using the physical buttons. It seems that the difference is more marked when using KOReader, but I think the same behaviour is noticeable with stock.

Anyone else encounter this?

pickyaxe · Yesterday, 07:24 AM

going to take a guess here, but when touching the screen it needs to determine if you're doing a tap-and-hold or just a tap, which adds artificial delay.

John F · Yesterday, 07:32 AM

I just tried this on a Forma. I do notice a difference in page turn speed when using buttons vs tapping.

Quoth · Yesterday, 08:25 AM

A button can wake the CPU directly (the ereader sort of sleeps till you turn a page). The capacitive touch is a subsystem that is probably powered up and polled periodically by the CPU, then the CPU SW has to interpret the information to decide if it goes to menu mode, or changes screen brightness or highlights, or opens dictionary or turns page.

The two buttons probably connect direct to the CPU and likely cause an interrupt. Thus the page turn routine is directly run. Then the CPU goes "sleepy" again.

You'll save power by having smaller margins and font, thus less page turns per book.

It would be surprising if the swipe or tap on screen to page turn (swipe only setting might be faster than swipe or tap?) was as fast or faster than the buttons.

However I've only found the Libra H2O totally reliable on the buttons. The Libra 2 is less reliable and the Sage is worst, sometimes skipping a page. So for reading epub and recording Audio Narration I can only use the original Libra (Libra H2O). Swiping or tapping is more awkward and too slow. I have to remember the last few words on the page as I turn to keep reading smoothly.

I've used an auto scrolling screen (horrible on eink) and autocue, but that really needs an assistant to adjust the speed. There is no perfect scrolling speed for out-loud narration.

bob.f · Yesterday, 08:34 AM

Quote:

Originally Posted by pickyaxe

going to take a guess here, but when touching the screen it needs to determine if you're doing a tap-and-hold or just a tap, which adds artificial delay.

Nice catch. Disabling double taps in KOReader does indeed improve matters.

Yesterday, 05:53 AM	#1
bob.f Connoisseur Posts: 78 Karma: 99068 Join Date: Nov 2017 Device: N/A	Buttons execute page turns faster than screen taps Hi, I noticed recently on my Libra 2 that page turns via a screen tap are noticeably slower than when using the physical buttons. It seems that the difference is more marked when using KOReader, but I think the same behaviour is noticeable with stock. Anyone else encounter this?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
KOReader previous/next page taps for any hand	mod2n	KOReader	5	05-10-2025 05:06 PM
tts page autoturn only works if built-in page number turns off for 1 page txt file	CrazyGriferman	PocketBook	0	10-22-2024 02:50 PM
landscape set to show 2 pages but page turns still at 1 page at a time	badbob001	Server	3	07-22-2020 03:01 PM
PRS-T1 Can you make page-numbers correspond to page-turns?	bibahbuzemann	Sony Reader	13	01-01-2012 12:03 AM
Amazon says having their own format permits faster page turns	RockdaMan	General Discussions	57	01-05-2011 11:43 AM

Yesterday, 07:24 AM	#2
pickyaxe Addict Posts: 289 Karma: 3762916 Join Date: Nov 2011 Device: none	going to take a guess here, but when touching the screen it needs to determine if you're doing a tap-and-hold or just a tap, which adds artificial delay.

Yesterday, 07:32 AM	#3
John F Grand Sorcerer Posts: 7,921 Karma: 70186655 Join Date: Feb 2009 Device: Kobo Clara 2E	I just tried this on a Forma. I do notice a difference in page turn speed when using buttons vs tapping.

Yesterday, 08:25 AM	#4
Quoth Still reading Posts: 13,948 Karma: 103895653 Join Date: Jun 2017 Location: Ireland Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper	A button can wake the CPU directly (the ereader sort of sleeps till you turn a page). The capacitive touch is a subsystem that is probably powered up and polled periodically by the CPU, then the CPU SW has to interpret the information to decide if it goes to menu mode, or changes screen brightness or highlights, or opens dictionary or turns page. The two buttons probably connect direct to the CPU and likely cause an interrupt. Thus the page turn routine is directly run. Then the CPU goes "sleepy" again. You'll save power by having smaller margins and font, thus less page turns per book. It would be surprising if the swipe or tap on screen to page turn (swipe only setting might be faster than swipe or tap?) was as fast or faster than the buttons. However I've only found the Libra H2O totally reliable on the buttons. The Libra 2 is less reliable and the Sage is worst, sometimes skipping a page. So for reading epub and recording Audio Narration I can only use the original Libra (Libra H2O). Swiping or tapping is more awkward and too slow. I have to remember the last few words on the page as I turn to keep reading smoothly. I've used an auto scrolling screen (horrible on eink) and autocue, but that really needs an assistant to adjust the speed. There is no perfect scrolling speed for out-loud narration.

Advert

Advert