More arrows please
Lifetime Premium Member
- Jan 27, 2019
- Reaction score
- Seattle area, WA
I'm happy to announce that I've published v2.3.1 to the beta channel. I'm planning to keep this update in beta mode for several weeks while observing stability and tuning the performance; later, I'll make it public. To become a beta tester, you need to enroll in Play Market on the app's page.
Here are the main improvements in v2.3.1
- Update of aircraft severity computation
No more continually appearing and disappearing planes if they fly precisely at the vertical boundary. In the new update, the app defines a "kill zone" - a set of all possible aircraft positions from where your car is visible. The severity is determined based on how long it would take for an aircraft to reach that area (considering both h- and v-speeds). E.g., five dots, if already in it, four dots if up to 30 seconds is needed to get there, three dots for up to a minute, and so on. The exact numbers depend on the sensitivity preference value.
- Options for non-linear severity computation for police alerts
In previous versions, the severity was determined based on the ratio of the distance to the report to the maximum alerting distance. A linear law was used. E.g., if the max alerting distance is 2.5 miles, you have one dot on the 2-2.5mi range, two dots on the 1.5-2mi range, three dots on 1-1.5mi range and so on. In the new version, you may choose these distances. For example, you may prefer the exponential law when severity increases after you pass half of the distance remaining. You may set up arbitrary rules for determining the number of dots. All you need is to set the proportion from the max alerting distance for each severity value.
- Option for the mute button to mute only one alert for each tap
It is often preferable not to mute all alerts with the mute button. v2.3.1 adds an option to configure the mute button to mute only the first alert.
- Heading (direction) indicators
Now all alerts have direction indicators showing where an officer/aircraft/hazard is pointing to. Especially useful for understanding aircraft moving direction.
- Option to start other application together with service start
I know a lot of people prefer using HwR with another app (e.g., GMaps or Waze). Now HwR provides an option to start another application once the service is started. There are four possible ways of starting another application
- Preload - start the external app and return to HwR, leaving the external application in the background. Useful for Waze as it starts much faster being preloaded when you want to submit a report.
- Split-screen - start the external app side-by-side with HwR.
- Foreground (HwR in PIP) - start the external application leaving HwR in PIP mode. PIP must be enabled for this.
- Foreground (no PIP) - start the external application leaving HwR completely in the background.
- Option to control displaying of aircraft outside of alerting area
For example, known enforcement aircraft can be displayed even if way too far away for an audible alert.
- Option to alert on airplanes or helicopters only
Some states use only one type of aircraft for speed enforcement. Filtering out others may help with reducing the number of false alerts. Aircraft with unknown type will always be displayed.
- An updated 25-score risk score
Now it is a bit harder to interpret but much smoother, and the scores themselves make much more sense. The 10-score model is untouched.
- Updated heat map to give more weight to recent reports
For a quicker painting of new trap spots
- Enlarged reset zoom button in map mode
- Fixed weird overlay of mute and Waze buttons on small screens and in split-screen mode when dark buttons enabled
So, stay healthy and have fun! And special thanks to those 104 people switched to the beta update channel!