HMT Release 11.1

1. Release Overview

This Release Notes document is for the RealWear HMT-1 firmware release 11.1, a security patch release with additional feature updates.
The release is only applicable to the HMT-1 standard model. Any HMT-1 ever sold by RealWear may update to this release (although earlier updates may need to be installed before 11.0.0 can be installed.). Full product brief authored by our product manager is here.

1.1 Deliverables

2. Release Notes

Release notes are only a summary of what’s new in this release. For more detailed information on using the features, consult the comprehensive documentation in RealWear’s Knowledge Center linked below in each section of the release notes.

2.1 Enhanced File Management and Cloud Integration

2.1.1 My Files
RealWear’s My Files application has always been great for viewing files hands-free with access to My Media, My Documents and My Photos. With Release 11.1 users will now have the ability to browse:

• Microsoft OneDrive files within My Files
• Hardware mounted storage drives like SD cards and USB drives
• The local file system of a RealWear device within My Files.

Relevant Knowledge Center Pages:

• Browse OneDrive documentation page
• My Files documentation page

2.1.2 Photo Tagging

Photos that are captured in RealWear’s My Camera application can now quickly and easily be tagged with one or multiple tags. Photo tagging is particularly useful in inspection or audit use cases where organizing and extracting value from many photos and videos is challenging.

Relevant Knowledge Center Pages:

• Photo Tagging documentation page
• My Camera documentation page

2.1.4 Web Apps
A new application that enables users to access a shortlist of Web Pages and applications such as predefined bookmarks or web based applications purpose built for the RealWear platform.

Relevant Knowledge Center Pages:

• Web Apps documentation page
• Web Apps Bookmark Configuration documentation page

2.2 Developer Enablement

2.2.1 My Files

RealWear’s My Files now implements the Android standard Storage Access Framework. In the linked Google documentation, under “Writing a client app” you’ll see that by invoking standard intents, you’ll be able to access RealWear’s My Files for required actions programatically.

2.2.2 Document Viewer & Media Player:

RealWear’s Document Viewer and Media Player now support remote URI’s via their existing intents without any additional work required by the application developer.

2.2.3 Photo Tagging
Using the RealWear My Camera intent and tagging service, tags are kept as meta data in the EXIF, meaning they are persistent with files and images.

2.2.4 Web Page Viewer
Behind the scenes of RealWear’s Web Apps application is the Web Page Viewer called via intent.

• RealWear’s Web Page Viewer supports the Android standard intent for URL’s
• For more details, consult Android’s documentation under the “Web Browser” section

2.2.5 Audio Recorder
RealWear’s Audio Recorder can be called programmatically by other applications.

Relevant Knowledge Center Pages:

• Audio Recorder documentation page

2.2.6 File Annotation
A new application that enables a user to annotate a picture with arrows, boxes and circles that can be white or red from a RealWear device. This is particularly useful for providing a simple annotation experience from a RealWear device.

In Release 11.1, this application can only be launched by a 3rd party application via an intent.

• Developers can call the File Annotation intent and pass it a file for annotation
• Developers can programmatically define if they want to create a new file or override an existing file
• Developers can programmatically define where they want the file to live in the file system after it’s been annotated

2.2.7 Web Kit
Applications that use the WebView component can now install and update Google’s version of WebView. This gives developers and users the ability to continually upgrade the version of WebView & WebKit without needing a RealWear firmware update.

2.2.8 WearML Indicators
One of the most powerful features of RealWear’s software platform is the ability to place any Android application onto a RealWear device and have that application be voice enabled with no effort required by automatically mapping speech bubbles, known as WearML indicators, over items on a RealWear screen to indicate that the item is clickable. These WearML indicators can be triggered either by saying that voice command or by saying “select item x” for example “select item 4”. This no code approach to voice enabling apps has been taken to the next level in Release 11.1. Now in My Controls, users can control how long WearML Indicators appear on the screen before they fade away.

Options available are:

• Fade after 3/5/10 seconds
• Fade never

This functionality for a specific app can also be controlled programmatically by developers.

2.3 New Applications and Ease of Use

2.3.1 Head-Tracking mouse
RealWear’s head tracking mouse, available as an option from My Controls, has been significantly improved.  This improved mouse can be used system wide and is leveraged in the Web Apps application and any other time the RealWear Web Page Viewer is used.

Relevant Knowledge Center Pages:

• Web Apps documentation page
• My Controls documentation page

2.3.2 Keyboard
Replaced close keyboard voice command with navigate back

Relevant Knowledge Center Pages:

• Speech Keyboard documentation page

2.3.3 Audio Recorder Application
RealWear’s Audio Recorder application enables users to record audio using the microphones of their RealWear device.

Relevant Knowledge Center Pages:

• Audio Recorder documentation page

2.4 Additional Language Support

2.4.1 Full language support for Indonesian

Relevant Knowledge Center Pages:

• Selecting Language documentation page

2.4.2 Cloud dictation support for the Great Britain, Australia and India dialects of English language

Relevant Knowledge Center Pages:

• Selecting Language documentation page

2.5 Security Changes

2.5.1 Android Security Updates
Security updates released through the end of February 2020 are incorporated into this release. See the full list of updates in the appendix of these release notes.

2.6 MDM/EMM/UEM

2.6.1 “android.software.managed_users Declaration” 

• MDM/EMM/UEM enrolment behavior in which device would attempt to enroll via Android Enterprise (work profile enrolment) instead of device administrator when Intune enrollment restrictions allow both
• android.software.managed_users declaration removed based on the dependency for Google Mobile Services and creation of Google account required to support Android Enterprise (work profile enrolment) RealWear HMT-1 and HMT-1Z1 hardware model run Android AOSP and does not run Google Mobile Services
• The device will now always enroll via the Device Administrator management if management model is supported within MDM/EMM/UEM

2.8 Bug Fixes

• Improvement in Camera Auto Focus
• Integrated Strings and language from RealWear

2.9  Known Issues 

19 issues  

NOTE – Noise Capture Feature for 3rd Party Apps are for demo only and below issues are known on MR3.1 

3 Software Update Method

• To get over the air update user has to be on 11.0.0-19-C.HMT-1.G
• The upgrade process for Release 11.1 is a simple one step upgrade process that retains your data which takes about five minutes.
• For specific details on how to upgrade, visit the Wireless update page in RealWear’s Knowledge Center.

Appendix 1: Software version format

• There is change in versioning format for future Maintenance releases
• Only the minor value will be incremented
• Build information represents the value for every incremental releases during the development cycle

Major.Minor.Patch MAJOR – increments when we make incompatible BSP changes,
MINOR – Increment for every Maintenance Release
PATCH – 0 for HMT1 , 1 for HMT-1Z1 & 2 for Picard

For Every Maintenance release – we just increment the Minor number and keep the Patch constant for the product

• Minor should be 1 for MR3.1 (for all products) and it would be 2 for MR3.2
• Patch should be 0 for Kirk, 1 for Kirk IS and 2 for Picard

Product MR3 MR3.1 MR3.2 MR3.X
HMT1 11.0.0 11.1.0 11,2.0 11.X.0
HMT-1Z1 11.1.0 11.1.1 11.2.1 11.X.1
HMT1 (Picard) 11.2.0 11.X.2
XX – Build Information will start will 01 for the first internal release from SIMT and would be incremented as per the build sequence

NOTE – If there is no change between Generic device and IS – Build Information should remain same

Appendix 2: Security Patch List

Android Security Bulletin — October 2019

• = not publicly available

Framework

Media Framework

System

Kernel Components

Qualcomm Components

Qualcomm closed-source components

 Android Security Bulletin — November 2019

• = not publicly available

Framework

Library

Media Framework

System

Framework

 System

Kernel Components

Qualcomm Components

Qualcomm closed-source components

Android Security Bulletin — December 2019

• = not publicly available

Framework

Media Framework

System

Kernel Components

Qualcomm Components

Qualcomm closed-source components

Android Security Bulletin — January 2020

• = not publicly available

Framework

Media Framework

System

Kernel Components

Qualcomm Components

Qualcomm closed-source components

Android Security Bulletin — Feb 2020

• = not publicly available

Framework

Media Framework

System

Kernel Components

Qualcomm Components

Qualcomm closed-source components