How the Offline Emergency Toolkit Signals for Help
AnyTool Offline Emergency Toolkit drives a phone’s own hardware from the browser to produce signalling aids, entirely client-side. The SOS strobe and morse signaller build a list of on/off steps from the international morse pattern — · · · — — — · · · for SOS, or any word you type — and run it on a looping timer at a 220-millisecond dit (a dash is three units), flashing a full-viewport white overlay and, where supported, pulsing the rear-camera torch in time. The torch is controlled with MediaStreamTrack.applyConstraints({ advanced: [{ torch: true }] }) after getUserMedia opens the environment-facing camera and getCapabilities confirms a torch exists. The loud siren and whistle are synthesised live with the Web Audio API (an oscillator plus gain node), the compass reads DeviceOrientationEvent, and the location panel reads the Geolocation API. A Screen Wake Lock keeps the display on during signalling, and the overlay opens via the Fullscreen API.
- SOS / morse built as on/off step lists at a 220 ms dit, dash = 3 units, looped
- Camera torch via MediaStreamTrack.applyConstraints torch constraint where exposed
- Siren and ~3 kHz whistle synthesised with Web Audio oscillator + gain
- Compass from DeviceOrientationEvent; location from the Geolocation API
- Fullscreen overlay + Screen Wake Lock keep the signal bright and the screen awake
