Forum Discussion
Jepplen
4 years agoExpert Protege
SystemInfo.batteryStatus is bugged.
Hello,
OVRManager.batteryStatus is obsolete and we should use SystemInfo.batteryStatus.
But this is not working properly.
When the Oculus Quest 2 headset is plugged with the original charger, the SystemInfo.batteryStatus returns NotCharging.
According to the documentation: NotCharging means it's plugged in, but it is not charging.
It works when playing the game on the PC (Unity) with Play, but not in the actual headset.
It seems this is bugged.
Can anyone confirm this?
6 Replies
- JepplenExpert Protege
By the way I am using Oculus integration 37.0.0.
- MetaStoreHelpCommunity Manager
Hey there! It sounds like you're having some headset charging issues, is that correct? If so, we'd highly recommend trying alternative cables and outlets to see if the issue stops or still persists.
If you have already tried that (or it didn't work after trying), then please reach out to us here at https://metaque.st/Support and we'll be more than happy to get this issue sorted out as quickly and smoothly as possible!
- JepplenExpert Protege
Hi, I'm confused. I'm not having chargin issues with the headset.
I'm having issue with the SystemInfo.batteryStatus not returning Charging when the device is plugged in and charging (Yes it is actually charging so nothing is wrong there). It only return NotChargin, which according to the docs mean that it is plugged in, but not charging.
So to clarify, it does charge, but the method is not returning the correct response.
It works as expected in my test environment on the PC (Unity - play scene), but when i build and test it on the Quest 2 it doesn't return the correct response. That's a real build and APK installation, not using the Link cable.
Is this a known bug?
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 12 days ago
- 1 year ago
- 15 days ago