The reqTime/recvTime fields of the no-valid-mapx-fb-rmd value. On the
Android 448 fresh capture the app writes two fixed numbers there that it never
computes: they do not match the /rmd request/response times or the capture
clock, appear nowhere else, and decode as little-endian ASCII fragments of
uninitialized memory (1869771886 → ntro, 1701999731 → stre). Because
they are not derivable, they are carried as an application constant and the
conformance harness compares them literally; a future capture with other values
therefore turns conformance red instead of being normalized away. Keeping them as
strings keeps the constant opaque (they are not usable timestamps).
The
reqTime/recvTimefields of theno-valid-mapx-fb-rmdvalue. On the Android 448 fresh capture the app writes two fixed numbers there that it never computes: they do not match the/rmdrequest/response times or the capture clock, appear nowhere else, and decode as little-endian ASCII fragments of uninitialized memory (1869771886→ntro,1701999731→stre). Because they are not derivable, they are carried as an application constant and the conformance harness compares them literally; a future capture with other values therefore turns conformance red instead of being normalized away. Keeping them as strings keeps the constant opaque (they are not usable timestamps).