Firstly, the app and phone will need access to location services at all times.
Secondly, you will need a mobile data plan, and active access to mobile data during the trip and at the time of the collision detection in order to send a real time collision alert.
Collision Alerting won’t work in very remote regions with no mobile network. Although the collision will be detected because (as it doesn’t depend on network access), the data will not be sent to your monitoring team in real time.
While you are stationary, the Zendrive SDK efficiently monitors your location and speed while your app is ‘in the background’. When it detects your speed being greater than about 7 mph for more 50 to 100m, Drive Mode is activated. i.e. Detection of a sustained period of motion in time and space is required for Drive Mode to be activated. When your phone comes to rest for a sustained period of time again, Drive Mode automatically ends, switching off Collision Detection.
You can verify when Drive Mode is active by opening Smart24: you will see a banner on the home screen with ‘Drive in Progress’. As always, caution should be used when looking at your phone screen while actually driving.
Detection of a trip might be delayed if you do not have an active mobile network connection, for instance if you are in a tunnel or underground. This is because a mobile network connection is typically required to achieve high location accuracy required by Zendrive.
Occasionally Drive Mode is activated when you have a less accurate location or have a weak mobile network connection. We currently remove trips that are less than 60m in length from the Trip Details page.
What happens if there is no network coverage at the time of a collision?
This is important. If there is no network connection at the time of a collision then the Collision Alert will not be sent: the automated alert relies on access to mobile data. This means that the Collision Alert feature is only appropriate for regions of the world where there is mobile network coverage, typically cities and motorways. The information about the trip and collision is still ‘buffered’ and stored on the phone, and would be sent when the network is available again.
How much battery power will Collision Response use?
Zendrive Trip detection, Trip monitoring and Collision Detection have each been highly optimised by Zendrive’s team of expert iOS and Android engineers to use as little battery power as possible on both operating systems. There will be slightly increased battery consumption during Drive Mode only, when Zendrive monitors and analyses sensor outputs more frequently.
In the near future we will provide quantitative benchmarks on the increased battery consumption during Drive Mode. Depending on your phone, the consumption is approximately in the range 0.5-1% per hour of driving.
How much mobile data will Collision Response use?
The only feature that is ‘real time’, and therefore requires access to mobile data, is the Collision Alert, which is a small packet of data. So overall, the additional mobile data footprint is minimal. There may be some indirect increase in mobile data consumption at the phone’s ‘system level’ as the phone makes use of location services during Drive Mode.
In the near future we will provide quantitative benchmarks. At this time we recommend to allow an additional 1 to 10 MB per day of active driving, depending on the amount of time you drive while using our Collision Response feature.