Subversion Repositories SmartDukaan

Last modification

• Rev 37433 2026-08-27 03:19:34
• Author: amit

• Log message:

  Oppo/Realme: split the slider tuning, and give Oppo its own failure verdict
  
  The two classes drive the same dingxiang widget and have been edited in lockstep,
  but they do not behave alike: measured over the last 11 hours as successes per
  completed drag, oppo runs 11-17% and realme 60%. A change proven on one is not
  evidence for the other, so the tuning constants are now documented as per-brand
  and must not be synced.
  
  Correcting the record while I am here: oppo has NOT regressed. Earlier "43%" and
  "48%" figures were successes over FAILURES, and a small widget-verdict sample --
  not successes over drags. On the consistent denominator oppo has been 12-15%
  throughout, across r37422, r37424 and r37432 alike.
  
  Oppo: ASSUMED_RATIO 1.7 -> 0.67.
  
  It only sizes the calibration probe: nudge ~= gap / (2 * ratio), intended to
  close half the gap. 1.7 came from one hand measurement. Production says
  otherwise -- 3,694 oppo calibrations average 0.67 (realme 0.70 over 1,683), so
  the probe has been closing about a fifth of the gap, not a half, and the ratio
  is then derived from that needlessly small and noisy sample. Mean gap is 120px
  for both, and 28% of oppo calibrations already overshoot.
  
  Oppo: log the captcha widget's verdict on the failure branch.
  
  Realme has carried this since r37428 and oppo never did, which is why realme's
  failures name POSITION_MISMATCH and oppo's 85% say nothing. Without it there is
  no way to tell a bad drag from a widget that never rendered.
  
  Realme: comment only, no behaviour change. Its ratio is wrong in the same way,
  but it is wrong while converting 60%, so oppo carries the corrected value first
  and realme follows only if it helps.