I've been experiencing a unique issue with my Magic Leap 2 where the device shuts down when it reaches high temperatures. This problem specifically occurs while using a feature I've developed for 1v1 WebRTC calling. I built this feature utilizing the WebRTC examples provided in MagicLeap_Examples.
During the first one to two minutes of the call, the local stream freezes and, after a few seconds, the remote video also gets stuck. The device then overheats and requires cooling before it can be used again.
The current resolution when this issue happens is 1080p.
Here are the details of my setup:
Unity Editor version: 2022-2.0f1
ML2 OS version: Version 1.3.0-dev1, Build B3E.230427.10-R.023, Android API Level 29
MLSDK version: 1.7.0
Host OS: Windows 11
The error message that shows up when the device shuts down is: "High Temperature - The device may shut down at high temperatures. Please allow the compute pack to cool."
The device may shut down at high temperatures. Please allow compute pack to cool.
I'm curious if anyone else has faced similar issues with WebRTC on Magic Leap 2, and if there are any solutions or workarounds that you could suggest.
I have attached the log file; PFA
High-temperature-WebRTC-ML2.txt (138.8 KB)
Kindly assist me in this matter as this is a pressing matter for us.
Thank you for reaching out to us regarding this issue. Would you mind running the profiler and showing the values for memory usage and CPU load at two different points in time?
I have performed a long testing of Calling feature using our application:
- Initiated a test using Expert call which lasted for 13 minutes.
- In the last minute of the test, the call was automatically disconnected.
- Simultaneously, both local and remote rendering views were automatically terminated.
- Notably, at the time of disconnection, the CPU usage exceeded 100%.
- Before starting the test, the device's battery level was at 47%.
- By the end of the test, the battery status had decreased to 38%.
Application didn't crashed or something, but call gets disconnected automatically.
I have attached the profiler video link for your reference, Please see last 2 minutes of the attached video to get better understanding:
Does the same thing occur when using the boilerplate MLExamples project?
@etucker I haven't tested MagicLeap_Examples that much extensively.
Here are some more observations.
A series of more than 10 comprehensive tests were conducted on a ML2 device.
II. Test Specifications:
Last two tests were long duration tests.
The final test was executed for a total duration of 1 hour.
III. Test Conditions:
- The device was completely charged at the beginning of the test, showing a 100% battery status.
- After the 30 minutes of test performed, Battery status was turned to 97%.
- I put the application to background and open settings. Frame become inactive, then I again open Application using controller. Frame again resumed.
IV. User Interactions:
- An interesting aspect of the test was that the scene on the device would pause if the user wasn't wearing glasses.
- Once the device was picked up again by the user, the scene would reactivate and resume.
V. Test Observations:
- Intermittent video latency * was experienced during the test.
- These latency periods lasted between 10 to 20 seconds each.
- After each latency period, the video frames would recover automatically without any user intervention.
The tests provided valuable insights into the device's performance under specific conditions, which will help in further refining its performance and user experience.