Skip to main content
Version: 14 May 2024

1.6.0 OS Release Notes

This release builds upon the previous 1.5.0 release.

New Features and Enhancements

  • 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.
  • WiFi / BT disable
    • Magic Leap now provides customers with a public preview ability to disable Wi-Fi and Bluetooth wireless network capabilities for operations in high-security environments.
  • Sleep Mode
    • Sleep is now ON by 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), user's existing Sleep setting will be retained.

GFX Changes

Remote Rendering With MLCapture

In order to provide the highest level of quality capture to our remote rendering customers, we implemented a mechanism that while offering good capture quality, trades off fidelity on the left eye viewport. This can cause artifacts, especially when content is transparent or thin, but only when the user is recording a capture.

Reduced jitter for heavy OpenGL apps in the browser

Earlier, if we ran GPU heavy apps on the browser on device we would encounter significant jitter and see issues with the rendering. We have addressed this issue to greatly reduce the jitter seen in these cases by optimizing the OpenGL backend.

LED Changes

No changes this release

UX Changes

Capture: OS Nav Support and Text Tooltips

  • The Capture app now supports better hand interaction so that users do not have to disrupt tasks to capture images and videos. We also added in-app tool tips to reduce ramp up time to successfully taking captures on the ML2.

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.

  • Iris ID will infrequently fail to unlock after sleep when auto-unlock is enabled.
    • While performing Iris ID auto-unlock, if the target is continuously pulsing and the device does not unlock from Standby or Sleep, remove the device from your head for a few seconds and then wear the device again. This should enable the device to be successfully unlocked.
  • There will a waiting time of around 1 minute in order for the Arabic speech model to be fully loaded and functional under these scenarios:
    • Voice Input is enabled when system language is Arabic.
    • Language is changed to Arabic when Voice Input is enabled.
    • User switches between apps or app intent JSON files when Voice Input is enabled and system language is Arabic.
  • Sleep Mode
    • Device may reboot on attempt to resume from Sleep Mode
    • After in sleep for an extended period of time, device may become unresponsive to the wake up process (tapping power button). To recover from this, press/hold power button for at least 10 seconds; then proceed to power up normally.
  • Marker Tracking
    • When maintaining 20 or more markers (marker poses) or using 4x4 markers, rendered content may no longer be visible. If this occurs, the app will need to be restarted.

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.

Easier Bug Reporting with Three-Button Press

Developers can now generate bug reports with a three-button press. This streamlined process simplifies bug reporting for developers and accelerates our team's ability to identify and address bugs promptly. If an individual encounters a bug hold down the ‘Volume Up’, ‘Volume Down’, and ‘Power’ buttons for two seconds to trigger a report, retrievable through the Hub. Ensure Developer Mode is enabled. For more information on this release, refer to the Bug Report page.

Starting Bug Report

Timestamp Change

Starting with OS version 1.6.0, the timestamps returned by vendor tag ML_CONTROL_CAMERA_MLTIME_TIMESTAMPS will be returned in nanoseconds instead of microseconds. This change is to better align with the Android platform standards. Developers who are currently using the Android Camera NDK and obtaining the Camera Pose using the exposure timestamp will need to update their applications to accommodate this change.

Developers can utilize the ML_API MLPlatformGetAPILevel() API to query the Platform Level supported on the OS. This value can then be used to determine if the timestamp conversion needs to be performed manually.