Overview
This Release Notes document is for the RealWear firmware release 12.0, update to Android 10.0 with security patch release and additional feature updates. Any HMT-1 ever sold by RealWear may update to this release (although earlier updates may need to be installed before 12.0.0 can be installed.)
For more details on this release not included in this article, see Release 12 Product Brief.
Deliverables
Delivery Data | |
Company | RealWear Inc. |
Model Number | HMT-1 (T1100G) |
Firmware Version | 12.0 |
Build File Name | HMT-1: 12.0.0-12-C.HMT-1.G or 12.0.2-12-C.HMT-1.G |
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 Android 10
- As part of RealWear’s ongoing commitment to long product lifecycles, RealWear’s device firmware and native applications have been upgraded to Android 10.
2.2 Android Security Updates
- Security updates released through the end of January 2021 will be incorporated into this release. Full list will be updated before the final commercial release.
2.3 Image Stabilization
- Improvement in Video stabilization for video recording
- Support for both HAL1 and HAL3 version of camera
- Support for video stabilization during video streaming for 3rd party applications.
2.4 Improved cloud dictation
- Introduction of a new cloud dictation engine for RealWear’s speech keyboard that delivers more accurate, responsive and grammatically correct results.
- Note: cloud dictation for Indonesian language is not available with RealWear’s new cloud dictation engine.
- When trying to use cloud dictation in Indonesian, users will be given a toast message letting them know that Indonesian dictation isn’t available and asks them to use another speech input method available in RealWear’s speech keyboard.
- Apr 1, 2021 Cut over date
- RealWear devices running firmware versions older than Release 12 will not have access to cloud dictation starting on Apr 1, 2021 .
- To resolve this issue customers simply need to upgrade to Release 12.
2.5 Dutch language support
- Dutch becomes RealWear’s 15th supported language with full language translation and cloud dictation
2.6 RealWear Explorer Interoperability
- Release 12 users who are using RealWear Explorer v4.1.0 will encounter a known issue with screen casting and device adb connection.
- To fix the issue, download and install the new version of RealWear Explorer.
2.7 Summary of what’s changed in early access version six:
- Improved SD Card support
- Verified interoperability with multiple EMM providers
- Improved Image Stabilization with Dynamic Motion Blur Reduction
- Fixes/updates for Voice Commands not working
2.8 Bug Fixes, Known Issues & limitations
Bug fixes and improvements have been made for this release. Details on specific fixes are available upon request via RealWear support.
Software Availability and Update Method
- The upgrade process for Release 12.0 is a simple one step upgrade process that retains your data
- To receive the over the air update, HMT-1 users have to be on 11.2.0-07-C.HMT-1.G.
- For specific details on how to upgrade, visit the Wireless update page in RealWear’s Knowledge Center.
- Please consult RealWear’s Firmware Update and Support policy if you have not already.
Appendix 1 – Security Patch List
September 2020
Components | CVE | References | Status | Comments |
Framework | CVE-2020-0074 | A-146204120 [2] | Included | |
CVE-2020-0388 | A-156123285 | Included | ||
CVE-2020-0391 | A-158570769 | Included | ||
CVE-2020-0401 | A-150857253 | No | N/A to RealWear kernel version | |
CVE-2020-0382 | A-152944488 [2] | Included | ||
CVE-2020-0389 | A-156959408 | Included | ||
CVE-2020-0390 | A-157598026 | Included | ||
CVE-2020-0395 | A-154124307 [2] | Included | ||
CVE-2020-0397 | A-155092443 [2] | Included | ||
CVE-2020-0399 | A-153993591 [2] [3] | Included | ||
Media Framework | CVE-2020-0245 | A-152496149 | Included | |
CVE-2020-0392 | A-150226608 | No | N/A to RealWear kernel version | |
CVE-2020-0381 | A-150159669 | Included | ||
CVE-2020-0383 | A-150160279 | Included | ||
CVE-2020-0384 | A-150159906 | Included | ||
CVE-2020-0385 | A-150160041 | Included | ||
CVE-2020-0393 | A-154123412 | Included | ||
System | CVE-2020-0380 | A-146398979 | Included | |
CVE-2020-0396 | A-155094269 [2] [3] [4] [5] [6] [7] [8] [9] | No | N/A to RealWear kernel version | |
CVE-2020-0386 | A-155650356 | No | N/A to RealWear kernel version | |
CVE-2020-0394 | A-155648639 | No | N/A to RealWear kernel version | |
CVE-2020-0379 | A-150156492 | Included | ||
Kernel | CVE-2019-19769 | A-150693748 Upstream kernel [2] |
No | N/A to RealWear kernel version |
CVE-2020-0404 | A-111893654 Upstream kernel |
No | N/A to RealWear kernel version | |
CVE-2020-0407 | A-153450752* | No | N/A to RealWear kernel version | |
MediaTek components | CVE-2020-0123 | A-149871374 DTV02098055* |
No | N/A Qualcomm Baseline |
CVE-2020-0229 | A-156333725 ALPS05023182* |
No | N/A Qualcomm Baseline | |
CVE-2020-0278 | A-160812574 ALPS05132252 * |
No | N/A Qualcomm Baseline | |
CVE-2020-0342 | A-160812576 ALPS05132765* |
No | N/A Qualcomm Baseline | |
Qualcomm components | CVE-2019-10527 | A-147102899 QC-CR#2421611 QC-CR#2421602 [2] QC-CR#2419153* |
Included | |
CVE-2019-14117 | A-147104886 QC-CR#2525999 |
No | N/A Qualcomm Baseline | |
CVE-2020-3613 | A-148816706 QC-CR#2239987 |
No | N/A Qualcomm Baseline | |
CVE-2020-3656 | A-157905780 QC-CR#2580967 |
No | N/A Qualcomm Baseline | |
CVE-2020-11124 | A-157906588 QC-CR#2611487 |
No | N/A Qualcomm Baseline | |
Qualcomm closed-source components | CVE-2019-10628 | A-147102780* | Included | |
CVE-2019-10629 | A-147101658* | Included | ||
CVE-2019-13994 | A-147104051* | Included | ||
CVE-2020-3621 | A-148816726* | Included | ||
CVE-2020-3634 | A-150695049* | No | N/A to RealWear kernel version | |
CVE-2019-10596 | A-147104369* | Included | ||
CVE-2019-13992 | A-147102898* | Included | ||
CVE-2019-13995 | A-147104253* | Included | ||
CVE-2019-14074 | A-145546792* | Included | ||
CVE-2020-3617 | A-150697774* | No | N/A to RealWear kernel version | |
CVE-2020-3620 | A-148817068* | Included | ||
CVE-2020-3622 | A-148817285* | Included | ||
CVE-2020-3629 | A-148816991* | Included | ||
CVE-2020-3671 | A-148529608* | Included | ||
CVE-2020-11129 | A-157905420* | No | N/A to RealWear kernel version | |
CVE-2020-11133 | A-157905987* | Included | ||
CVE-2020-11135 | A-157906313* | No | N/A to RealWear kernel version |
October 2020
Components | CVE | References | Status | Comments |
Android runtime | CVE-2020-0408 | A-156999009 | Included | |
Framework | CVE-2020-0420 | A-162383705 | No | N/A for Android 10 |
CVE-2020-0421 | A-161894517 | Included | ||
CVE-2020-0246 | A-159062405 | Included | ||
CVE-2020-0412 | A-160390416 | Included | ||
CVE-2020-0419 | A-142125338 | Included | ||
Media Framework | CVE-2020-0213 | A-143464314 | Included | |
CVE-2020-0411 | A-142641801 | Included | ||
CVE-2020-0414 | A-157708122 | Included | ||
CVE-2019-2194 | A-137284057 | No | N/A for Android 10 | |
System | CVE-2020-0215 | A-140417248 [2] | Included | |
CVE-2020-0416 | A-155288585 [2] | No | N/A to RealWear kernel version | |
CVE-2020-0377 | A-158833854 | Included | ||
CVE-2020-0378 | A-157748906 | Included | ||
CVE-2020-0398 | A-154323381 | Included | ||
CVE-2020-0400 | A-153356561 | Included | ||
CVE-2020-0410 | A-156021269 | Included | ||
CVE-2020-0413 | A-158778659 | Included | ||
CVE-2020-0415 | A-156020795 | No | N/A to RealWear kernel version | |
CVE-2020-0422 | A-161718556 | Included | ||
Kernel | CVE-2020-0423 | A-161151868* | No | N/A to RealWear kernel version |
MediaTek components | CVE-2020-0283 | A-163008257 M-ALPS05229282* |
No | N/A to RealWear kernel version |
CVE-2020-0339 | A-162980705 M-ALPS05194445* |
No | N/A Qualcomm Baseline | |
CVE-2020-0367 | A-162980455 M-ALPS05194445* |
No | N/A Qualcomm Baseline | |
CVE-2020-0371 | A-163008256 M-ALPS05229226* |
No | N/A Qualcomm Baseline | |
CVE-2020-0376 | A-163003156 M-ALPS05194415* |
No | N/A Qualcomm Baseline | |
Qualcomm components | CVE-2020-11125 | A-160605820 QC-CR#2617422 QC-CR#2673763 |
No | N/A to RealWear kernel version |
CVE-2020-11162 | A-160605604 QC-CR#2677376 |
No | N/A to RealWear kernel version | |
CVE-2020-11173 | A-160605709 QC-CR#2646001 |
No | N/A to RealWear kernel version | |
CVE-2020-11174 | A-160605900 QC-CR#2636449 |
Included | ||
Qualcomm closed-source components | CVE-2020-3654 | A-153346045* | No | N/A to RealWear kernel version |
CVE-2020-3657 | A-153344684* | No | N/A to RealWear kernel version | |
CVE-2020-3673 | A-153345154* | No | N/A to RealWear kernel version | |
CVE-2020-3692 | A-153345116* | No | N/A to RealWear kernel version | |
CVE-2020-11154 | A-160605708* | No | N/A to RealWear kernel version | |
CVE-2020-11155 | A-160605404* | No | N/A to RealWear kernel version | |
CVE-2020-3638 | A-153346253* | No | N/A to RealWear kernel version | |
CVE-2020-3670 | A-153345118* | No | N/A to RealWear kernel version | |
CVE-2020-3678 | A-153345398* | No | N/A to RealWear kernel version | |
CVE-2020-3684 | A-153346047* | No | N/A to RealWear kernel version | |
CVE-2020-3690 | A-153344723* | No | N/A to RealWear kernel version | |
CVE-2020-3703 | A-160605749* | No | N/A to RealWear kernel version | |
CVE-2020-3704 | A-160605508* | No | N/A to RealWear kernel version | |
CVE-2020-11141 | A-160606016* | No | N/A to RealWear kernel version | |
CVE-2020-11156 | A-160605294* | No | N/A to RealWear kernel version | |
CVE-2020-11157 | A-160605864* | No | N/A to RealWear kernel version | |
CVE-2020-11164 | A-160605595* | No | N/A to RealWear kernel version | |
CVE-2020-11169 | A-160605405* | No | N/A to RealWear kernel version |
November 2020
Components | CVE | References | Status | Comments |
Android runtime | CVE-2020-0409 | A-156997193 | Included | |
Framework | CVE-2020-0441 | A-158304295 | Included | |
CVE-2020-0442 | A-147358092 | Included | ||
CVE-2020-0418 | A-153879813 | Included | ||
CVE-2020-0439 | A-140256621 [2] | No | N/A for Qualcomm Baseline | |
CVE-2020-0454 | A-161370134 [2] | No | N/A for Android 10 | |
CVE-2020-0443 | A-152410253 | Included | ||
Media Framework | CVE-2020-0451 | A-158762825 | Included | |
CVE-2020-0452 | A-159625731 | Included | ||
CVE-2020-0438 | A-161812320 | No | N/A for Qualcomm Baseline | |
System | CVE-2020-0449 | A-162497143 | Included | |
CVE-2020-12856 | A-157038281 [2] [3] [4] | No | N/A for Qualcomm Baseline | |
CVE-2020-0424 | A-161362564 | No | N/A for Qualcomm Baseline | |
CVE-2020-0448 | A-153995334 | Included | ||
CVE-2020-0450 | A-157650336 | Included | ||
CVE-2020-0453 | A-159060474 | No | N/A for Android 10 | |
CVE-2020-0437 | A-162741784 | No | N/A for Qualcomm Baseline | |
MediaTek | CVE-2020-0445 | A-168264527 M-ALPS05253566 * |
No | N/A for Qualcomm Baseline |
CVE-2020-0446 | A-168264528 M-ALPS05257259* M-ALPS05316810* |
No | N/A for Qualcomm Baseline | |
CVE-2020-0447 | A-168251617 M-ALPS05287879 * |
No | N/A for Qualcomm Baseline | |
Qualcomm closed-source components | CVE-2020-3639 | A-155653490 * | No | N/A to RealWear kernel version |
CVE-2020-3632 | A-155652696 * | No | N/A to RealWear kernel version | |
CVE-2020-11123 | A-155652382 * | No | N/A to RealWear kernel version | |
CVE-2020-11127 | A-155653795 * | No | N/A to RealWear kernel version | |
CVE-2020-11168 | A-162756122 * | No | N/A to RealWear kernel version | |
CVE-2020-11175 | A-162756020 * | No | N/A to RealWear kernel version | |
CVE-2020-11184 | A-162756352 * | No | N/A to RealWear kernel version | |
CVE-2020-11193 | A-162756585 * | No | N/A to RealWear kernel version | |
CVE-2020-11196 | A-162756960 * | No | N/A to RealWear kernel version | |
CVE-2020-11205 | A-162757240 * | No | N/A to RealWear kernel version |
December 2020
Components | CVE Number | References | Status | Comments |
Framework | CVE-2020-0099 | A-141745510 | Included | This part of the code already exists in Kirk |
CVE-2020-0294 | A-154915372 | Included | ||
Media Framework | CVE-2020-0440 | A-162627132 [2] | No | N/A to RealWear kernel version |
CVE-2020-0459 | A-159373687 [2] [3] [4] [5] | No | N/A to RealWear kernel version | |
CVE-2020-0464 | A-150371903 [2] | Included | ||
CVE-2020-0467 | A-168500792 | Included | ||
CVE-2020-0468 | A-158484422 | No | N/A to RealWear kernel version | |
CVE-2020-0469 | A-168692734 | No | N/A to RealWear kernel version | |
CVE-2020-0458 | A-160265164 [2] | Included | This part of the code already exists in Kirk | |
CVE-2020-0470 | A-166268541 | No | N/A to RealWear kernel version | |
System | CVE-2020-0460 | A-163413737 | No | N/A to RealWear kernel version |
CVE-2020-0463 | A-169342531 | Included | ||
CVE-2020-15802 | A-158854097 | Included | ||
Kernel components | CVE-2020-0444 | A-150693166 Upstream kernel |
No | N/A to RealWear kernel version |
CVE-2020-0465 | A-162844689 Upstream kernel [2] |
No | N/A to RealWear kernel version | |
CVE-2020-0466 | A-147802478 Upstream kernel [2] |
No | N/A to RealWear kernel version | |
Broadcom components | CVE-2020-0016 | A-171413483 * | No | N/A to RealWear kernel version |
CVE-2020-0019 | A-171413798 * | No | N/A to RealWear kernel version | |
MediaTek components | CVE-2020-0455 | A-170372514 M-ALPS05324771 * |
No | N/A to RealWear kernel version |
CVE-2020-0456 | A-170378843 M-ALPS05304125 * |
No | N/A to RealWear kernel version | |
CVE-2020-0457 | A-170367562 M-ALPS05304170 * |
No | N/A to RealWear kernel version | |
Qualcomm components | CVE-2020-11225 | A-168050601 QC-CR#2724407 |
No | N/A to RealWear kernel version |
CVE-2020-11146 | A-157906412 QC-CR#2648596 |
No | N/A to RealWear kernel version | |
CVE-2020-11167 | A-168049959 QC-CR#2434229 [2] |
Included | This part of the code already exists in Kirk | |
CVE-2020-11185 | A-168050580 QC-CR#2658462 |
No | N/A to RealWear kernel version | |
CVE-2020-11217 | A-168051734 QC-CR#2710036 |
No | N/A to RealWear kernel version | |
Qualcomm closed-source components | CVE-2020-3685 | A-157905813 * | No | N/A to RealWear kernel version |
CVE-2020-3686 | A-157906329 * | No | N/A to RealWear kernel version | |
CVE-2020-3691 | A-157906171 * | No | N/A to RealWear kernel version | |
CVE-2020-11136 | A-157905860 * | No | N/A to RealWear kernel version | |
CVE-2020-11137 | A-157905869 * | No | N/A to RealWear kernel version | |
CVE-2020-11138 | A-157905657 * | No | N/A to RealWear kernel version | |
CVE-2020-11140 | A-157906530 * | No | N/A to RealWear kernel version | |
CVE-2020-11143 | A-157905814 * | No | N/A to RealWear kernel version | |
CVE-2020-11119 | A-168051735 * | No | N/A to RealWear kernel version | |
CVE-2020-11139 | A-157905659 * | No | N/A to RealWear kernel version | |
CVE-2020-11144 | A-157906670 * | No | N/A to RealWear kernel version | |
CVE-2020-11145 | A-157905870 * | No | N/A to RealWear kernel version | |
CVE-2020-11179 | A-163548240 * | No | N/A to RealWear kernel version | |
CVE-2020-11197 | A-168050278 * | No | N/A to RealWear kernel version | |
CVE-2020-11200 | A-168049958 * | No | N/A to RealWear kernel version | |
CVE-2020-11212 | A-168050603 * | No | N/A to RealWear kernel version | |
CVE-2020-11213 | A-168050861 * | No | N/A to RealWear kernel version | |
CVE-2020-11214 | A-168049138 * | No | N/A to RealWear kernel version | |
CVE-2020-11215 | A-168049960 * | No | N/A to RealWear kernel version | |
CVE-2020-11216 | A-168050579 * | No | N/A to RealWear kernel version |
January 2021
Components | CVE Number | References | Status | Comments |
Framework | CVE-2021-0313 | A-170968514 | No | N/A to RealWear kernel version |
CVE-2021-0303 | A-170407229 | No | N/A to RealWear kernel version | |
CVE-2021-0306 | A-154505240 [2] | No | N/A to RealWear kernel version | |
CVE-2021-0307 | A-155648771 [2] | No | N/A to RealWear kernel version | |
CVE-2021-0310 | A-170212632 | No | N/A to RealWear kernel version | |
CVE-2021-0315 | A-169763814 | Included | ||
CVE-2021-0317 | A-168319670 | Included | ||
CVE-2021-0318 | A-168211968 | Included | ||
CVE-2021-0319 | A-167244818 | No | N/A to RealWear kernel version | |
CVE-2021-0304 | A-162738636 | Included | ||
CVE-2021-0309 | A-158480899 | Included | ||
CVE-2021-0321 | A-166667403 | No | N/A to RealWear kernel version | |
CVE-2021-0322 | A-159145361 [2] | Included | ||
CVE-2019-9376 | A-129287265 | No | N/A to RealWear kernel version | |
CVE-2020-15999 | A-171232105 | Included | ||
Media Framework | CVE-2016-6328 | A-162602132 | Included | |
CVE-2021-0311 | A-170240631 | Included | ||
CVE-2021-0312 | A-170583712 | Included | ||
System | CVE-2021-0316 | A-168802990 | Included | |
CVE-2020-0471 | A-169327567 | Included | ||
CVE-2021-0308 | A-158063095 | Included | ||
CVE-2021-0320 | A-169933423 | Included | ||
Google Play system updates | CVE-2021-0311, CVE-2021-0312 |
No | N/A to RealWear kernel version | |
Kernel components | CVE-2020-10732 | A-170658976 Upstream kernel |
No | N/A to RealWear kernel version |
CVE-2020-10766 | A-169505740 Upstream kernel |
No | N/A to RealWear kernel version | |
CVE-2020-10767 | A-156766097 Upstream kernel |
No | N/A to RealWear kernel version | |
MediaTek components | CVE-2021-0301 | A-172514667 M-ALPS05342361* |
No | N/A to RealWear kernel version |
Qualcomm components | CVE-2020-11233 | A-170138863 QC-CR#2257789 |
No | N/A to RealWear kernel version |
CVE-2020-11239 | A-168722551 QC-CR#2744826 |
No | N/A to RealWear kernel version | |
CVE-2020-11240 | A-170138526 QC-CR#2702760 [2] [3] |
No | N/A to RealWear kernel version | |
CVE-2020-11250 | A-170139097 QC-CR#2734543 |
No | N/A to RealWear kernel version | |
CVE-2020-11261 | A-161373974 QC-CR#2742124 |
No | N/A to RealWear kernel version | |
CVE-2020-11262 | A-170138789 QC-CR#2742711 |
No | N/A to RealWear kernel version | |
Qualcomm closed-source components | CVE-2020-11134 CR2617125 |
A-170138862* | No | N/A to RealWear kernel version |
CVE-2020-11182 CR2738672 |
A-168722721* | No | N/A to RealWear kernel version | |
CVE-2020-11126 CR2609168 |
A-170139227* | No | N/A to RealWear kernel version | |
CVE-2020-11159 CR2604636 |
A-170138666* | No | N/A to RealWear kernel version | |
CVE-2020-11181 CR2664505 |
A-168051034* | No | N/A to RealWear kernel version | |
CVE-2020-11235 CR2634794 CR2637648 CR2641024 |
A-170138866* | No | N/A to RealWear kernel version | |
CVE-2020-11238 CR2694355 |
A-170139099* | No | N/A to RealWear kernel version | |
CVE-2020-11241 CR2703058 |
A-170139229* | No | N/A to RealWear kernel version | |
CVE-2020-11260 CR2735335 |
A-168918332* | No | N/A to RealWear kernel version |
Bug Fixes
The specific bugs that have been fixed will be provided in the release notes when available. The fixes are not only to the operating system, but also to the RealWear native applications that are shipped with the operating system. Several have been incorporated directly, in response to issues discovered by the ISV partner community.
Firmware Availability and Dates
Item | Date – HMT-1 |
Firmware Notice | 19 Jan 2021 |
Firmware Beta Early Access Begins | 05 Jan 2021 |
Firmware General Availability | First half of March 2021 |
Note: Dates are approximate and subject to change
Participating in Early Access
This release was made available for Beta Early Access beginning 05 Jan 2021. To be added to the Allow List for Firmware Early Access (on no more than three devices), fill out the form here. After completing the form you will can upgrade via a Firmware Over the Air (FOTA) upgrade within one business day. If you do not receive access after than, email Support@RealWear.com.
IMPORTANT: Please ensure your RealWear device(s) have the below firmware versions installed and logging is activated.
RealWear Device | Firmware Version |
HMT-1 | 11.2.0-07-C.HMT-1.G |
If you experience an unexpected result during the upgrade process, the device’s log files will detail the status of the device software and actions needed to complete the install process. Here is a guide to ensure your success during the update process.
Follow the update documentation outlined.
Providing Feedback
As always, provide complete information when contacting support to expedite the resolution process. Initiate the feedback via email with “Support@RealWear.com” in the “To” and your dedicated RealWear contact(s) + James Gordey (James@RealWear.com) on “Cc”.
Items to include:
- Your contact information (Email & Phone Number)
- HMT device serial number
- ISV software & version
- Actual behavior
- Expected behavior
- Steps to reproduce the behavior
- Helpful images & device screenshots
- Short videos
- Log file(s) (You can capture this via RealWear Explorer, support.realwear.com/knowledge/realwear-explorer).
Note: For best results enter the below adb command which provides much better information to our support and Engineering team than simple logcat
adb bugreport E:ReportsMyBugReports
RealWear encourages all product feedback. Send non-bug-related product feedback to James Gordey (James@RealWear.com), RealWear’s Device Software Product Manager, or via our Product Ideas portal.
Upgrading at or after General Availability
By default, the firmware will be available to all devices upon General Availability. When ready, the Release general availability will be announced across all RealWear communication channels. For specific details on how to upgrade and RealWear’s Firmware Availability Policy visit the Knowledge Center.
Frequently Asked Questions
Q: According to RealWear’s Firmware update and support policy which releases will be supported once Release 12 is generally available?
As outlined in the firmware policy, effective 01 Jan 2021 RealWear’s firmware support is for “N-2” releases meaning that only Releases 11.2, 11.1 and 11.0 are supported. Once Release 12 is generally available, only Releases 12, 11.2 and 11.1 will be supported.
Links and Resources
- Prior to GA, all RealWear Solution Engineering and Support Teams globally will be versed on the technical details of Release 12. Contact your solutions engineer for support or reach out directly through the general support email, support@realwear.com.
- Upon product General Availability, User Guide updates and release notes are published to the RealWear Knowledge Center at https://www.realwear.com/knowledge-center/. The Release Notes will include step-by-step instructions on how to upgrade any device.
- When possible, the Marketing Team – supported by the Product Team – create videos for the most compelling aspects of any release, as well as other communications.
- As always, the Product Team can answer any questions not addressed by the above resources.