FAQ/Troubleshooting Guide - Solo Mobile

A: The following conditions can adversely affect collision detection:

• Poor GPS coverage
• Poor cellular coverage
• Poor internet speed
• Air-plane mode
• Wi-Fi disabled
• Location services disabled or location permission denied
• Battery saver mode enabled (Android only)
• Background restrictions enabled (Android only)
• Wi-Fi scanning disabled (Android only)
• "Always Allow" Location permission not available (iPhone only)

Note: Collision detection will only be triggered if the vehicle involved is moving at a minimum 32 kph (20 mph). Therefore a collision will NOT be detected if the vehicle involved is stationary and is hit by another vehicle, even if that vehicle is travelling at 32 kph (20 mph) or greater at the time of the collision.

A: To use Solo, you will need a smartphone running either of the following Operating Systems:

• Android 5.0 or later.
• iOS (Apple) 8.0 or later.

Note: 
When using the SoloDrive feature, certain custom Android Operating Systems [such as OnePlus' Oxygen or Hydrogen OS] will have compatibility issues.

A: Two-Factor authentication is required to provide added security for customer data and customer identity.

A: For a 12-hour session per day, set up with hourly check-ins and 5 min GPS interval tracking, we estimate ~125KB per 12-hour session so ~2.5MB per month just for session data per device.
If the session is set up with 1 min GPS intervals, we would estimate 100MB per device per month.

Note: That Maps, messages, & other apps are not included in this estimate.

A: The 'Nearby' feature will only display those workers assigned to the same team(s) as you. Additionally, your Organisation may also choose to disable this feature entirely for your team. This assignment is managed  by Solo Platform Users with a Solo Role of Admin or Operations Manager.

A: If you are indoors, the position may jump around. This is related to something called the 'Urban Canyon Effect', where the signal is impacted by materials such as concrete and steel and may result in your position being inaccurately reported. Indoor accuracy can be improved with the use of iBeacon technology. Please contact your Account Manager for further information.

A: If you have been in an Active Wearable session when you start a Mobile session, the New Mobile session will override the Old Wearable one. The Wearable session will keep running on your device but check-ins and raised alerts etc will NO LONGER be received by Solo Platform. It is therefore recommended that you End the Old Wearable session to prevent any confusion or incorrect usage.

A:

• The Mobile devices session will continue to run and any pre-set check-ins will still be requested as per the Profile you have selected.
• The check-in and GPS data will be stored by the Solo app until a network connection is re-established, at this point the stored data will be sent to the Platform. 
• The Solo Platform session will show a connection lost icon  but will still continue to "tick" over however no data will be received.
• A "missed check-in" alert will be triggered in the Platform if the device does not re-enter a network coverage area before the next scheduled check-in.

• If you try to raise an alert while there is no connectivity to the Solo service, the Mobile App will continue to retry to raise the alert at the following intervals:
  try 3 times in the first instance

  wait 1 minute, then try 3 times

  wait 10 minutes, then try 3 times

  wait 30 minutes, then try 3 times

  try once every 15 minutes until it goes through (or the alert is cancelled)

A:

• The Mobile device's session will continue to run and all pre-set check-ins will still be requested, however the location recording will show as 'Off'.
• Check-ins and Alerts will still be actioned as normal.
• GPS location data will not be available to the Solo service for any session activities or events that took place during the GPS coverage outage.

A: The Solo session will pause in the mobile device BUT will continue to "tick" over within the Solo Platform. It will also trigger a "missed check-in" alert in the Platform if the device does not power back up before the next check-in. Once the device is powered back up, the session will continue as per normal and the Solo Platform timeline will update with 'GPS Lost' & 'GPS Found' activities.

A: ONLY if the device is paired with an iPhone, this will allow the call to connect to a mobile network. Otherwise no, the iPad is not enabled for calling.

A: No, currently an alert can ONLY be managed via the Solo Platform.

A: Data usage for upload is 50kB per hour of continuous driving.
For cumulative trips less than one hour, data upload will be less than 50kB.
Data usage for download is approximately 10kB per 6 hours.
In short, this is an insignificant amount of data  and therefore should not cause concern from a data usage stand point.

A: Android - 4% per hour of driving (incremental battery drain, above that of the host app).
iOS - 3% per hour of driving (incremental battery drain, above that of the host app)
IMPORTANT: Battery drain numbers displayed to users are relative battery drain numbers and therefore depend on the battery drain of other apps running concurrently.

A: SoloDrive measures driver safety using smartphone sensors: the accelerometer, gyroscope, and GPS. This is done by measuring a wide variety of driving behaviours including speeding, hard braking, sharp accelerations, driver phone use, and more.

Phone Use: Whilst driving detection will require GPS, and Gyroscope sensors.
*Registered only if the phone is handled for a period greater than 3 seconds whilst the vehicle is
  travelling at least 17 km/h.

Hard Turn detection: Will require GPS, Gyroscope, Magneto and Gravity sensors.
*Registered when the vehicle turns more than 30 degrees at a speed of 17 km/h or more where the
  lateral speed is more than 13 km/h in 1 second.

Hard Brake detection: Will require GPS, Accelerometer sensors.
*Registered only when speed is reduced by 11 km/h or more in one second.

Aggressive Acceleration detection: Will require GPS sensors.
*Registered when the vehicle increases its speed by 11 km/h or more in one second.

Speeding detection: Will require GPS sensors.
*Registered when the vehicle exceeds the posted speed limit by:
         8 km/h while travelling less than 48 km/h for a minimum of 10 seconds; or
         16 km/h while travelling more than 48 km/h for a minimum of 10 seconds.

Collision detection: Will require Accelerometer, Gyroscope and GPS sensors.

Notes:
If your device does not have some of the above sensors SoloDrive will still work. However it will work optimally if these sensors are available.
Certain custom Android Operating Systems [such as OnePlus' Oxygen or Hydrogen OS] will have compatibility issues.

A: For each detected drive, Solo considers the length of the drive and the riskiness of any detected behaviours to determine an overall score on the scale of 0 -100, where 100 is a flawless drive. A shorter drive with more risk taken attracts a lower score. For example, a 100km drive with two hard-acceleration events is considered less risky and would therefore result in a higher score than a 1km drive with two hard-accelerations.

A: Yes, SoloDrive detects smartphone / tablet handling as follows: 
All calls and screen interactions when the vehicle is traveling >18 Kph [11Mph]. 
Unless the smartphone / tablet is docked. When docked and travelling >18 Kph [11Mph], actions such as hands free calling and screen interactions < 3 seconds will NOT be detected.

A: If your Organisation has opted-in to the Leader board feature, you will be able to see your standing on the 'Leader board' tab of the SoloDrive page, under 'More'. Note that the Leader board is calculated and published once per calendar month, so if you are just getting started with Solo you may have a short wait before you can see where you're placed.

A:  This app is required if you intend to use Solo on a Samsung smart watch. It is the interface between your smartphone and the Samsung Galaxy Watch and is required in order to install the Solo Wearable App on your Galaxy Watch.

A:  This is an optional feature that allows video and audio to be recorded via your mobile device in the event that you manually raise alert or Solo detects a vehicle collision. Enabling this feature can provide crucial situational awareness to the first responders attending to your alert incident.

A:  This feature will only be available on your phone if both you and your Organisation permit it. First, your Organisation must opt-in to the Video Recording During Alerts feature. In addition, you (as a Solo Mobile User) must opt-in to the feature via the Settings menu in the Solo Mobile app in order for it to activate on your device. Click here for help with this.

A:  When this feature is correctly enabled for your Organisation and you have opted-in to using it, video and audio will be automatically recorded using the device’s front-facing camera and microphone whenever an alert is manually raised or a vehicle collision is detected, and will begin streaming available audio/video to the secure Solo cloud infrastructure. Click here for help with opting-in to this feature.

A:  Your Organisation will have defined a particular person, people, team or teams as an escalation-point that will be notified whenever you raise an alert or your device detects a vehicle collision. With this feature enabled, the notification will include a link to view the footage via a web browser. After 24 hours, the link will expire. Additionally, you may review and/or delete the footage via the ‘Session History’ section of the Solo Mobile app. Note that deleting a video from the app will delete it for all users. Click here for help with accessing your Session History.

A: You are able to stop recording via the on-screen controls at any time. Click here for help with managing alerts from your phone.

A: In order for video to be recorded, all of the below conditions must be met:

• The Video Recording During Alerts feature must be enabled for your Organisation
• You must have opted-in to using the feature and permitted the Solo Mobile App to access your camera and microphone
• The App must be open and in the foreground of your device
• No other App can be using the camera and/or microphone (e.g. Zoom, FaceTime, Microsoft Teams)
• A mobile data or WiFi internet connection must be in place at the time the (satellite connection is not supported for this feature)
• The device battery must not be critically low ("critically low" is normally set at 5%, however this is decided by your Organisation.)