#12798 NORM 13.2.0-: Screenshot does not take every time

[Zarro Boogs per Child]

#12798: Screenshot does not take every time
-----------------------------------+----------------------------------------
           Reporter:  tonyforster  |       Owner:  suyouxin                         
               Type:  defect       |      Status:  new                              
           Priority:  normal       |   Milestone:  13.2.0-android                   
          Component:  android      |     Version:  Development build as of this date
         Resolution:               |    Keywords:                                   
        Next_action:  design       |    Verified:  0                                
Deployment_affected:               |   Blockedby:                                   
           Blocking:               |  
-----------------------------------+----------------------------------------

Comment(by Quozl):

 i've experimented further with an arduino driving the keys, and verified
 the thresholds for correct response as described by ben;
  * the x key must be pressed no more than 60ms before the power key,
 otherwise the volume dialog occurs,
  * the power key must be pressed no more than 240ms before the x key,
 otherwise the volume dialog occurs,
  * if struck together, both keys must remain down with no release for at
 least 660ms,
  * if power is struck before x key by 90ms (the difference in firmware
 debounce timers), both keys must remain down for 580ms.

 even if we messed with the power key debounce, or increased the game key
 debounce, this would only move the boundaries from -60ms:240ms to
 -150ms:150ms.  this is a remarkably narrow window, and is obviously
 designed for hardware that has nearly identical physical structure for
 both buttons, such that a finger can cover both.

 reviewed the source PhoneWindowManager.java.  there does not seem to be a
 good reason why both keys have to be down for 580ms.  it depends on
 whatever getGlobalActionKeyTimeout returns.

 i suggest next time the code is edited, that we try:
  * increasing the 150ms boundary by 90ms, so it will be -150ms:330ms,
  * decrease getGlobalActionKeyTimeout significantly.

-- 
Ticket URL: <http://dev.laptop.org/ticket/12798#comment:19>
One Laptop per Child <http://laptop.org/>
One Laptop per Child bug tracking system