View Single Post
Old 12-05-2009, 12:40 PM   #95
ekaser
Opinion Artiste
ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.
 
ekaser's Avatar
 
Posts: 301
Karma: 61464
Join Date: Mar 2009
Location: Albany, OR
Device: Nexus 5, Nexus 7, Kindle Touch, Kindle Fire
Quote:
Originally Posted by jusmee View Post
Well, the original software that was on my PP was bad too.There were many criticisms of the way the device can completely miss button presses. I found that slow definite presses were required, as quick clicks were often missed.
I'm quite sure (from much experience with low-power devices that go into 'sleep' modes) that what's happening is that:
1) The unit is asleep (VERY minimal power).
2) You quickly press and release a button.
3) The pressed button starts to wake the unit up, but before it completes its wakeup and scans the buttons to see which one was pressed, you've already released the button, so it doesn't see any button down, and doesn't do anything, and goes back to sleep.

The only way to fix this is if the unit has HARDWARE to 'latch' which button was pressed to wake up the unit. If the unit doesn't have that 'latch' hardware, then the only hope of improvement is to add a "button scan" VERY shortly after the wakeup starts. But usually in these situations, there's a certain amount of "wakeup processing" that HAS to be done before anything else can be done. So, of course, only Jinke can say whether or not this can be improved, and they don't talk...
ekaser is offline   Reply With Quote