05-03-202401:56 AM - last edited on 07-24-202402:52 PM by LaserDisk
First of all, I have already factory reset my headset. I've tested Air Link with the original Link cable and charger to see if it's a cable issue. I've also tested just the headset by itself, plugging in the charger and waiting 10 minutes, and the issue still persisted.
It's not a PC issue; it's the headset. So let's get that out of the way. I have one of the first units, the Oculus Quest 64 GB version. Everything was working perfectly until recent firmware update.
The issue is that the headset is not reporting the correct battery percentage while charging after 10 minutes. It stays at 100%, preventing the low battery notifications at 20%, 15%, and 10% from appearing and stopping the headset from charging. Consequently, the headset dies on me while playing, which is frustrating with no way to tell when its gonna happen. I have tried everything, as you've seen, but it appears to be a bug with the firmware.
But the weird thing is, while the headset is off and charging, it will report the battery correctly. So I believe it's a simple fix. Currently, I am not financially able to upgrade my headset to Quest 3, and I would like to have my experience not be ruined by this issue.
In conclusion, after you plug in your charger while the headset is turned on, after 10 minutes, the headset will report that the battery is fully charged to 100%, no matter what, but it's actually not. Here are some logs of it happening:
I connected the charger around 01/05 21:05~ there is no log for that.
01/05 21:15:26.867 {INFO} [RemoteHeadset_V2] HMD battery level update: from 79 to 100
01/05 21:15:26.867 {INFO} [HardwareSDKRelay] HMD HeadsetSerialNumber got health event with error code 0:
01/05 21:15:26.881 {INFO} [LifeCycle] ActiveHardwareChanged::get(session).subscribe() End
I've contacted support; they were nice and fast to respond, but it doesn't seem they can do anything for me since I'm in the EU, and replacement is only available for US residents.
Ive looked and i'm not the only one with this case they are multiple.
So that's why i am posting here, I would like this to reach the Meta Quest development and bug team in hopes of this issue being fixed in a future firmware update.
@1os7, Thank you for providing us that information. Based on everything, we would like for you to send us a private message. To do so, please select our name to get to our profile page, or click here. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message. We hope to hear from you soon!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Hey @CCPam, thanks joining in on the conversation! For many users, submitting a bug report can be a quick fix for issues like this. There are also some great troubleshooting steps provided by other community members in this thread.
Of course, tech can be tricky, so we encourage our Quest users to get in touch with us over PM for more personalized support. To do this, select our name to get to our profile page, or click here: https://metaque.st/CommunitySupport. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
No there is no solution on this from Meta... If you read the thread to re-calibrate the battery you have to click the power button and wait at least 10 seconds then click it again the battery should re-calibrate...
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
