Skip to content
  • There are no suggestions because the search field is empty.

April 2024 version 3.20

Full version: 3.20.24101.96

Simplified logoff

This version of Strivr Player includes an update to the Log Off flow to expedite the process of uploading telemetry (training results and data). In previous versions of Player, upload would not begin until the user went through a series of button selections (log off, confirm, fill out and submit survey if enabled, select Done).

In version 3.20, the logoff confirmation and survey steps have been removed. Telemetry is now sent to Strivr after the user selects Log Off in the headset.

The Log Off command in the Strivr Home environment

Course ordering

In the main training menu in headsets, courses are now shown in alphabetical order by course name. Previously, there was no defined order.

The main training menu in Strivr Home, showing courses

Telemetry status updates

In the Telemetry Status field on the Device Details page in the Strivr Portal, newly provisioned headsets (on which no training has yet occurred) will now report their telemetry status as Synced. Previously, these headsets displayed Pending, which was confusing because no telemetry files were pending.

The telemetry status field in Device Details

When telemetry status is Pending, meaning that there are files on the device waiting to be uploaded, the following information will be passed to Strivr Portal:

  1. How many files are pending

  2. Of the pending files, the timestamp of the oldest telemetry file

  3. Of the pending files, the timestamp of the newest telemetry file

  4. The timestamp of the last time a telemetry file upload completed successfully

Learn about checking for pending telemetry files in the headset in About the Facilitator user type.

End of support update

New versions of Strivr Player now have a support lifespan of 210 days. Previously, the lifespan was 180 days. To learn more about Strivr Player version support, see the release notes for Strivr Player 3.19.

Bug fix: Content update timestamp

When content was updated on a given headset, Strivr was not correctly reporting to the portal the timestamp when this occurred. This has been resolved and we now correctly report the timestamp of a successful content update.

Bug fix: Already registered headsets

If a user tried to register a headset that had already been registered, Strivr Player could become corrupted. This issue has been resolved.

Learn more about registering headsets