View Single Post
Old 08-16-2021, 09:54 PM   #49
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 3,939
Karma: 17500001
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Quote:
Originally Posted by Hyphen-ated View Post
It's sidestepping some important elements of what I care about testing, though.
Well, the command from hardware button, finger tap, finger swipe, console command to key injector, USB key or Bluetooth key really only takes a few milliseconds, which is small compared to what we're looking for.
The ADB input command is slow and not worthy of our consideration because it spins up a Java for the trivial task of injecting an input.
I have wired up stick-on foil and a diode pair and driver to simulate a capacitive finger touch before also. (I even still found it on my desk.)

Most (all?) ereader apps load/compose/whatever the next page while you are reading the current page.
That is a reason why repetitive page flipping could run into limits and actually be slower.
For a modern device to "wake up" by goosing the CPU governor doesn't take any time.

The next time I have to pop open my Poke3 I'll take some measurements like the Glow3, 4 above.
Renate is offline   Reply With Quote