1.7.0 OS Release Notes

Build B3E.240418.09-R.060

This release builds upon the previous 1.6.0 release.

caution

The 1.7.0 OS update disables USB Debugging and Developer Mode by default. After updating, please manually turn on Developer Mode using this guide.

AR Cloud Localization and Mapping Services

• Version update of the localization and mapping services to version 2.1.2.
• Changes included in version 2.1.2:
  • Improved map accuracy through enhanced detection capabilities of revisited locations in the map.
• AR Cloud version 1.48.21 (or higher):
  • Updated map viewer inside the enterprise web console. Includes improved usability, updated user experience and new tool menu.

‘Battery Saver’ Setting Enhanced and Renamed ‘Battery Mode’

• The Battery Saver setting allowed the end user to toggle between a power saving mode and maximum compute performance.
• The Battery Mode setting now allows the end user to choose between three modes of operation:
  • Maximum Performance:  Maximum system performance with no battery life optimization, resulting in shorter battery life.
  • Optimized Performance:  Balances system performance and battery life optimization.
  • Enhanced Performance (preview):  Prioritizes battery life optimization; includes preview battery life optimization features.
  • Optimized Performance is the default for ‘clean’ (erase userdata) flashing of the latest software build and for factory reset use case. For upgrade use cases (e.g., upgrading from a prior software release without erasing user data), the former Battery Saver setting will be mapped to the new Battery Mode setting as follows:
    • Battery Saver disabled will be mapped to Maximum Performance.
    • Battery Saver enabled will be mapped to Optimized Performance.
  • CAUTION:  For some use cases, the selection of the Enhanced Performance option may significantly increase device performance. In some cases, application instability or performance degradation may be noted.  Please experiment with the Enhanced Performance option and share your observations with the Magic Leap team.
    • Likely Performance Enhancement: Remote rendering and high-resolution camera RGB capture.
    • Likely Performance Degradation:  Hand tracking.

Audio Capture

• Mixed capture mixing levels have been updated.  Relative levels of voice, world, and virtual capture streams in mixed capture are no longer adjusted based on the current master volume level, but are now fixed for a more consistent user experience.  Virtual content in mixed capture streams (including for Video Capture) is attenuated by 3 dB, while the dedicated virtual capture stream continues to present this material with no attenuation.
• Added clipping protection on input capture streams.

Voice Service

• Italian system intents and app intents are supported.
• In-app system intents are supported for all enabled languages; new for Modern Standard Arabic, EU Spanish, and EU French.
• Voice Intent Development ToolKit (VIDTK):
  1. Supports all platform-supported languages.
  2. Introduces language detection feature to avoid using the language characters other than the target language.
  3. Improves spell checking capabilities for Japanese to avoid misspelling.

Developer Option - USB Debugging

• In order to ensure that the ML2 device is as secure as possible for our customers, the USB Debugging feature is disabled by default for 'clean' (erase userdata) flashing of the latest software build and for factory reset use case. With this default, developers or users who want to connect the ML2 device to a PC will have to manually enable USB Debugging from within the headset. This will also disable Developer Mode until manually enabled by user.

Renderdoc Improvements

• We updated the Renderdoc version from 1.26 to 1.29 to include the latest updates and bug fixes available. A workaround was also added to address some older Unity apps causing GPU hangs.

Object Occlusion

• We added object occlusion as part of the XR_ML_physical_world_occlusion extension. This allows world occlusion on objects like the controller inside the application and on in application objects with appropriate depth.

Improved video captures using secondary views

• Previously, we relied on the application developers specifying a set focus distance within their application to facilitate accurate video captures on the Magic Leap 2. This can be tricky as often the user needs to focus on objects at different distances and can cause video captures to have offsets between real world and virtual object alignment. We have added support for client apps to provide a dedicated pass via the Secondary Views extension to eliminate this issue. Application developers should now be able to procure high quality video captures with accurate physical and virtual world alignment on their Magic Leap 2 device. The XR_MSFT_secondary_view_configuration and XR_MSFT_first_person_observer extensions are required to enable this feature. Some examples of how to use the extension can be found here.

Improved dimmer alignment

• We have improved the dimmer alignment algorithm for remote rendering. We have added segmented dimmer usage for quad composition layers as well.

LED Changes

No changes in this release

UX Changes

No changes in this release

Known Issues

Don’t forget: Some Magic Leap hardware and software features are in a pre-release state and might not be available, might contain bugs or defects, and might experience delays or failures. Read this document for guidance on the current state of Magic Leap hardware and software. This guidance helps developers make the best possible use of the Magic Leap platform.

• Voice Service

  • System intents “open” and “close” cannot correctly recognize some app names for non-English languages.
  • EU Spanish recognition performance needs more improvement.

• Vulkan Validation error fix

  • Fixed Vulkan Validation layer errors shown when using XR_KHR_vulkan_enable1

• OpenXR Runtime layer fix

  • Fixed issues with xrEndFrame returning with an error timeout for some applications when valid color data was not available.

• Virtual keyboard jitter and snapping

  • We have improved virtual keyboard animation smoothness and user experience to avoid it snapping into position when being opened.

• Magnetometer and Accelerometer data fix

  • An issue with the orientation transforms for magnetometer and accelerometer sensors was corrected
  • Both sensors now stream corrected values through to the Android sensor layer and are adjusted to the following (see diagram) coordinate space to conform with the default Android Sensor coordinate space.

• Device Sleep

  • Device may reset when forced to enter sleep or waking up from sleep
  • Device may freeze or reset if left in sleep state for long periods (more than 30 mins)

• Using external power brick

  • Menu may display incorrect state-of-charge for the external battery

Flashing Instructions​

Before flashing make sure to power cycle your device without the cable plugged in. Hold down the power button for 20 seconds to do so.

When flashing, you MUST flash in a linear sequence based on the build order in the table below which can be found on our Customer Care site under Magic Leap OS Update Path.

We recommend you to use ML Hub flashing capability to flash the OS. Contact your Magic Leap customer care representative for any additional support with regards to flashing your device.

Device Reset (Hardware Recovery)​

When device (wearable and/or compute pack appear frozen or unresponsive), use the following sequence to restart:

1. Remove USB-C cable from the device
2. Press and Hold the power button for at least 20 seconds
3. Release the power button
4. Wait a few seconds, then restart the device by tapping/releasing power button again.