Repeating (default long-press) should occur immediately after the time out, so insert first repeat immediately. The first timeout should be shorter than hook_viewConfigTimeouts too.
repeatCount() is not needed in the check
No functionality change, wrapping some calls, actually using mRepeatCount in preparation for long-long press
Allow combi events only using last (secondary) key (as is now) or fully repeated
So event mapped to Power-Home double click can be invoked
primary-down,sec-down, up*2, prim-down, sec-down, up*2
  is same as
primary-down,sec-down, sec up, sec-down

Similar as the following for 3.3: https://github.com/gerhardol/xposed-additions/commit/322cfa667c838f9fe7f21cd115727bef927d890b
http://robobunny.com/wp/2013/08/24/android-seekbar-preference-v2/
Comment 12, 15

to avoid printouts like

W/View    ( 4916): requestLayout() improperly called by android.widget.LinearLayout{52861f50 V.E..... ......ID 11,18-166,41 #7f0b0009 app:id/seekBarPrefBarContainer} during layout: running second layout pass
For tap/long-press timeouts: Set max to 50 ms over current val if that is lower than hardcoded (set in xml).
This allows increasing the max value. More than 50 can be set by exit/enter several times. (inconvenient, but most users seem to want lower val.)
(This could be done by just adding 25% or so to current)
Similar could be done for min.

For some devices, 200ms for the double click is too little.
Merge branch '3.4.x.timeout_remap' into 3.4.x.g

* 3.4.x.timeout_remap:
  For tap/long-press timeouts: Set max to 50 ms over current val if that is lower than hardcoded (set in xml). This allows increasing the max value. More than 50 can be set by exit/enter several times. (inconvenient, but most users seem to want lower val.) (This could be done by just adding 25% or so to current) Similar could be done for min.
  http://robobunny.com/wp/2013/08/24/android-seekbar-preference-v2/ Comment 12, 15