Auto Secure LoginSecurity
SignalLab stops treating an invalid capture as a clean result
The Android correction distinguishes unusable input from a valid capture with no findings and clears results when the input changes.
Work covered: September 25–October 8, 2026
An empty result needs valid evidence
Blank, unrecognized, empty and partially malformed capture input is now rejected instead of producing a misleading zero-findings result. The distinction matters: “nothing was found” should not stand in for “the input could not be analyzed.” The issue was reproduced in the earlier public release before correction.
Do not carry findings into a different capture
Editing the input immediately clears the previous findings. Phone checks covered the corrected feedback and accessible layouts so users can see why a capture was rejected and which data the current result refers to. This is an input-handling improvement, not a new claim about hardware coverage or detection performance.
Recorded release status
SignalLab 1.0.5 was submitted to production review on September 28. The dated record reports review in progress, not confirmed public approval. Its authorized, contained testing scope remains unchanged; the update does not permit testing systems or radio environments without the necessary authorization.
Explore the product
Prepared from dated development and release records. Status is stated for the recorded milestone; internal tests and review submissions do not establish public availability. Sensitive operational details and customer information are excluded.