Skip to main content
New Participant
September 15, 2026
Question

[Bug v2.7] Power controller stuck in protection mode after PC-VR Link

  • September 15, 2026
  • 3 replies
  • 153 views

Hello Horizon OS Dev Team,

 

I want to report a specific, reproducible software calibration bug regarding the battery controller logic in Horizon OS 2.7 Beta (PTC). This issue originally started in v2.6.

 

Previous Behavior (On Older Firmware)

Previously, on all older software versions, the headset performed flawlessly. During PC-VR gameplay via an active Link cable, the battery charge was constantly maintained at 100%. If the headset was connected to the PC with a lower battery percentage, it would immediately start charging during the game, regardless of the high graphical and processing load.

 

Current Bug Description (On Firmware v2.6 and v2.7)

1. Now, during long PC-VR Link sessions via the active cable, the system forces the Battery Care protection mode, safely discharging the battery from 100% and freezing it at exactly 80%.

2. When the session is finished and I select Power Off via the software menu, the OS correctly triggers the standard post-shutdown cooling loop where the internal fan continues to spin on low RPMs to blow out residual heat.

3. The Issue: Once the fan stops and the headset cools down completely, the power controller firmware gets stuck in Protection Mode. If I plug the cold headset into the official 18W wall charger, it completely refuses to take power, staying at 0.0W on a hardware wattmeter.

4. LED Indicator Behavior: When the headset is in Standby or Sleep mode, the red LED flashes continuously, and no charging happens. When the headset is completely turned off (Power Off), the red LED stays solid red without flashing, but the charging current still remains at 0.0W.

5. How the bug is cleared:

- Thermal Timeout: I have to leave the headset idle for exactly 30 minutes. Only after this strict software timeout does the firmware finally clear the internal Overheat Flag, automatically resuming normal charging at 8.0W up to 100%.

- Manual Reset: If I physically unplug and replug the wall adapter about 15 times, it forces the USB Power Delivery handshake to reset, bypassing the stuck flag.

- Standalone Reset: If I drain the battery below 50% in standalone mode (unplugged from PC), the protection flag drops immediately, and it charges from 0% to 100% continuously in 2 hours 10 minutes without a single drop.

 

Hardware Health Proof (Flawless Hardware)

- ADB dumpsys battery report: Status: 5 (Full), Health: 2 (Good), Charge counter: 5033 mAh (0% degradation after 2.5 years of use because it was always powered via an active link buffer).

- Total Energy Intake: A hardware wattmeter recorded exactly 0.020 kWh for a full 0-100% charge, aligning perfectly with a healthy 19.44 Wh factory battery.

 

Conclusion

This is strictly an OS-level firmware bug. The power manager fails to properly release the hardware thermal protection flag immediately after the post-shutdown cooling sequence ends. A Factory Reset does not resolve this.

 

Please investigate this power delivery logic sequence and include a patch in the upcoming stable release.

 

Thank you.

3 replies

Honored Contributor
September 15, 2026

Hi there Megre​

This is a user only forum. There are no Meta community managers, no Meta moderators here, or any Meta staff. So don't expect a reply from them here. 

You should post this in the developer forum. Here is the link. Good luck! 

Developer Forum | Meta Community Forums

 

steve40
Honored Contributor
September 15, 2026

This is the correct forum for reporting Link issues Maccyb123​ . Meta sometimes does silently monitor this Link forum. This one, and the Creator forum, are the only ones I think are still partly monitored.

steve40
Honored Contributor
September 15, 2026

You should also report this in the headset and also through the Link PC app:

HEADSET>QUICK SETTINGS>REPORT A PROBLEM

HORIZON LINK>HELP CENTRE>PROVIDE FEEDBACK

Do not report it in the Dev forum, that is not for Quest hardware/firmware issues.