The documentation for Vocera Collaboration Suite version 3.2.0 for Android is available online:

• Vocera Collaboration Suite Android User Guide

From this online help location, you can download the PDF version of the VCS 3.2.0 documentation.

This release includes the following new features and functionality.

Features marked with an asterisk * require Vocera Messaging Platform version 5.2.2.

Features marked with two asterisks ** require Vocera Messaging Platform version 5.2.2 and Vocera Voice Server 5.2.2.

• Background thread removed and new push mechanism introduced. **

  This version of Vocera Collaboration Suite now no longer uses a background thread to stay active and now provides support for a new push mechanism. This provides the following capabilities:

  • Reduced battery consumption both on and off campus.
  • The app can now be woken up if it has been terminated or when new calls and messages arrive.
  • Podcasts and other audio are no longer interrupted.

• Contact information now viewable from list of Escalation Distribution List members.

  If you are in the Contacts screen, and you tap on an Escalation Distribution List to view its members, you can now tap on any member of the displayed list to view contact information for that member.

• On-call status now displayed when viewing On-Call Distribution List contact details.

  If you are in the Contacts screen, and you tap on an On-Call Distribution List, the contact details screen for that list now includes the current on-call status of the list's members.

• Contact status now displayed for Distribution List members.

  When you are viewing the list of members of a Distribution List, contact status information is now provided for each member. In previous releases of Vocera Collaboration Suite, contact status information was provided for group members, but not for Distribution List members.

• Sender and start of VMI message can now be displayed on lock screen. *

  If your system is integrated with a patient monitor, nurse call system, or other system that sends messages using the Vocera Messaging Interface (VMI), the lock screen now displays the sender and the first few characters of any message sent through VMI (all characters that can fit on one screen line) if this capability has been enabled in the VMP Administrator. This enables you to quickly triage and respond to urgent messages.

• The VMP Administrator can now obtain client logs from a device running VCS. *

  This makes it easier for administrators to troubleshoot problems if they occur. When this log retrieval is performed, the VCS user is not notified.

• Messages sent using templates can be set to expire and can be delivered to on-campus users only. *

  If the Vocera administrator has set up message templates, and you create a notification using a template, you can specify that the notification is to expire after a specified period of time. You can also specify that the notification is to be delivered to on-campus users only. This ensures that emergency messages are sent only to people that are available, and that out-of-date emergency messages are not waiting for users when they start a later shift.

If you are using the TC51-HC, you will need to update your firmware before you can use Vocera Collaboration Suite.

Two firmware packages are available:

• GMS, to support obtaining and deploying Vocera Collaboration Suite from the Google Play Store
• Non-GMS, to support the use of Android Mobile Device Management (MDM) to deploy Vocera Collaboration Suite

The release notes for these firmware packages can be downloaded here:

• GMS: TC51 Operating System For GMS Devices
• Non-GMS: TC51 Operating System for Non-GMS Devices

Make sure that you update your TC51-HC with the proper firmware. You must be on firmware version 19.01.4 before you apply the firmware Update 005 shown above.

The firmware update makes the following assumptions:

• ADB is installed on your PC (the adb drivers and platform-tools)
• Your TC51-HC has Developer options enabled
• USB debugging is On

Contact Vocera technical support for instructions and driver download information.

This release includes the following known issues and limitations for versions of the Vocera Collaboration Suite running on Android operating systems.

• VCS-3607 - Accessing a conversation with a large number of messages may cause the app to restart.

  When you access a conversation that contains a large number of messages, your VCS app may restart as it is downloading the conversation's message history. When you access the conversation again, all messages are loaded and accessible.

• VCS-3632 - On some devices, VCS is not launched after device is rebooted until the screen is unlocked (Android 7.x or later).

  If your device is running Android version 7.x or later, and you reboot your device, VCS may not be restarted until you unlock your screen. This means that, depending on your device model and operating system version, messages or calls sent to you immediately after rebooting may not be received if the device is locked.

• VCS-3651 - On MC40-HC devices, you must log into VCS again if you upgrade your firmware.

  If you are using an MC40-HC device, and you upgrade your firmware from version 4.4 to version 5, you will need to log into VCS again.

• VCS-3717 - Keyboard dismissed after supplying response option for message (Android 7.0+ Samsung devices only).

  On some Samsung devices running Android version 7.0 or later, if you are creating a message that requires a response and you type in a response option for the message, the keyboard is dismissed and the cursor does not move to a new response option.

• VCS-3919 - Line is Busy icon does not appear when talking in instant conference that was started while the app was in background.

  If you have placed the VCS app in the background, you are invited to join an instant conference, and you press Push To Talk to become active in the conference, the Push To Talk button is not updated to display the Line is Busy icon.

• VCS-12576 - Calls received while on another call do not appear in the call log.

  If you are in a call and you receive another call, the second call does not appear in the call log. This will be fixed in a future release of VCS.

• VCS-14231 - Calls may be dropped when "Use VCG for VCS client connection management" option activated on VMP Server in environment containing multiple Vocera Client Gateway servers.

  If your environment uses connections to multiple Vocera Client Gateway servers, and you activate the "Use VCG for VCS client connection management" option on your VMP Server, existing calls may be dropped. For this reason, we do not recommend the use of this option at this time. This problem will be fixed in version 3.3 of VCS.