Unity-Technologies / Unity-Technologies/com.unity.webrtc

[BUG]: High temperature and battery consumption on Android AR glasses

Open
#1,034 2 comments 0 reactions 1 assignee View on GitHub

@karasusan is already working on this.

Since May 22, 2024.

bug
Dominant language
Assembly
Stars
852
Forks
238
PR merge metrics
No merged PRs in 30d

Description

Package version

3.0.0-pre.7

Environment
* OS: Android
* Unity version:
2022.3.27
Steps To Reproduce

Use WebRTC unity plugin to stream video within Unity application with Snapdragon Spaces SDK on Android device.

Current Behavior

Hello Unity WebRTC Team,

We have noticed that our Unity application, which utilizes the SnapdragonSpaces SDK along with your com.unity.webrtc library, is causing rapid battery drain and device overheating. Our device is the Argo by Digilens, based on Android.

We’ve attached a screenshot from our profiler showing how the application’s CPU cores are constantly active. The silver cores run at 787MHz (more efficient), while the gold cores operate at 1.2GHz (high performance but less efficient). As a result, the internal temperature of the SoC reaches up to 74°C.

Our questions are:

Is there any way to reduce the temperature during WebRTC usage (and battery consumption)?
Is it expected behavior for the WebRTC library to cause such significant core load, as shown in the screenshot?
We appreciate your guidance on mitigating these performance issues.

Expected Behavior

Reduce device temperature when using webRTC plugin - during video call device is up to 52 C degrees.

Anything else?

image

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.