The documentation for Vocera Collaboration Suite version 3.0.1 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.0.1 documentation.

For the MC40, the following are supported:

• MC40-HC Rev C with Android 4.4.4
• MC40-HC Rev C FIPS with Android 4.4.4

For other Android devices, Vocera Collaboration Suite version 3.0.1 provides support for Android OS 4.1 and later.

If you are using Android OS 6.0 or later, Vocera recommends that you add Vocera Collaboration Suite to the list of apps that is whitelisted from battery optimization doze mode.

VCS 3.0.1 clients require VMP Server 5.1.0 for full functionality. When a VCS 3.0.1 client is connected to VMP Server version 4.9.2 to version 4.9.4, the client uses version 2.0.2 backward compatibility mode to interact with the server.

Vocera Voice Server 4.4.1 or later is required. If your organization is using Vocera Voice Server departments and synchronizing them with VMP groups, Vocera Voice Server 5.1 or later must be installed.

VMP Server 5.1 does not support message templates in which one or more recipients are Escalation Distribution Lists and other recipients are regular users. Only one Escalation Distribution List can be listed as a recipient, and it must be the only recipient.

To install Vocera Collaboration Suite 3.0.1 for Android:

1. On your Android device, open the email sent to you from the Vocera administrator.

2. Tap the first link in the email to go to the Google Play Store to download and install the Vocera Collaboration Suite app.

3. If you are prompted to complete the action using either the Internet or Play Store, tap Play Store.

   Important: If you tap Internet instead, the link to the Google Play Store won't work.

4. When you see the Google Play Store page for Vocera, tap Install.

5. After the app is installed, open the email again, and tap the second link to configure the app to connect to your organization's server.

This release includes the following fixes:

• Android version 6.0 now supported. Version 6.0 of the Android operating system (Marshmallow) is now supported.

• Message status now displayed if right to see in contacts directory not granted. If a recipient is added to a conversation that a participant does not have rights to normally see in their contacts directory, and the participant sends a message to the group, he or she now sees status updates for this recipient. (DE7589)

• Message tone and vibration settings now consistent on device platforms. If you log into an Apple iOS device and set your notification tone and vibration options, these settings are now preserved if you log into an Android device. Similarly, settings created on an Android device are now preserved if you log into an Apple iOS device. (DE7742)

• When Call not answered, message no longer indicates that recipient is not on network. If you make a Call to someone who is on the network but does not answer, you no longer receive a message that your recipient is not on the network. (DE7818)

• Can now enter PIN after receiving notification. On some Android devices, you could not enter your PIN when you received a notification and pressed the in-app banner or system notification banner while in the PIN entry screen. This problem has now been fixed. (DE8955)

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

1. PIN screen displayed on some devices when receiving a Call. On some Android devices, if PIN security is enabled, if you start Vocera Collaboration Suite and then put the application in the background when the screen requesting the PIN appears, the PIN screen appears instead of the "call connected" screen when a call is placed to your device and automatically answered. (DE8287)

2. Device switches back to handset mode after completing second Call. If you make a Call, set the audio to use the speaker, and then make and end a second Call, the device switches back to handset mode after the second Call is completed, instead of continuing to use the speaker for the still-active first Call. (DE8298)

3. Audio mode reverts to default when VCS relaunched. If you make or receive any type of call, change the audio mode, back out with the device's Back button, and then tap the VCS icon to relaunch it, the audio mode is reset to its default instead of remaining in the mode that you have specified. (DE8335)

4. Audio mode icons not reset properly when wired headset unplugged during Call. If you unplug your wired headset during a Call, a highlighted handset icon replaces the headset icon, but then an un-highlighted headset icon replaces the handset icon. If you switch to speaker mode after this, you cannot switch back to handset mode. (DE8450)

5. Cannot switch back to speaker mode when wired headset plugged in during Call. If you are in speaker mode during a Call, and plug in a wired headset, the Call is successfully redirected to your headset, but the displayed audio mode does not change, and you cannot switch back to speaker mode. (DE8452)

6. Can update personal photo when system option disabled. If you have updated your personal photo in the past, you can continue to do so even if the VMP Server is configured to disable uploading of personal photos. (DE9266)