Quest 3 not charging - forever problem
Well I'm now a topic starter after replying on a two year old post. So - I have a few minutes this morning and will start a fresher discussion on this topic. OH - and in case you didn't see a post...
Forum Discussion
A loose USB‑C port can cause exactly the "charges for 30 seconds then drops to zero" behaviour you're seeing. If one headset's port already feels looser than the other, that's a strong sign the connection is intermittent rather than anything to do with battery temperature.
Waiting a few hours before charging might help only because it avoids plugging in right after use, when the battery management system is still stabilising. It's a workaround, but it doesn't necessarily point to the real cause. The headset shell can feel cool while the battery itself is still warm - most of the heat you notice during use comes from the CPU/GPU, not the battery.
Glad it's working again for now - just keep an eye on that loose port in case the issue returns.
Wow - I was able to erase this one.
But I can't touch the original forum topic.Just to clear this up before the narrative gets any further away from reality: I'm not a Meta employee. The forum-assigned tag just means I've spent a lot of time helping people here. That's it.
And since you brought up the Feb 23 update - I've actually read the release notes. There were no battery‑related changes in that rollout at all except for a new battery level indicator next to the clock in Navigator. It was UI updates, Navigator changes, media‑sharing controls, and on‑device dictation. Nothing touching charging behaviour or battery management.
For what it's worth, my own Quest 3 is fully updated to v2.1 (27 Feb) and charges normally. So whatever's happening isn't a universal firmware issue.
I'm responding to the symptoms you described because a charge that starts for a few seconds and then drops is a textbook sign of an intermittent connection. The fact that one port already feels looser is relevant whether it fits the conclusion you prefer or not. That isn't "latching onto one sentence"; that's how troubleshooting works.
If waiting before charging works for you, great - genuinely. But a workaround isn't proof of the cause, and correlation alone doesn't turn a theory into fact. My goal here is simply to keep the thread grounded in what the symptoms actually point to, not in assumptions about an update that didn't even touch the battery system.
steve_40 This guy is a troll Steve. Ignore him. He seems to think he's entitled to an answer from volunteers who are just trying to help. By the tone of his post, he seems to be under the mistaken impression that you're a Meta consultant, being paid by Meta. 🃏
Not even close. I'm not a Troll. I just am irritated by people who have expert in their title, and don't read or think before they respond.
You know there was an update that rolled out on February 23rd, or at least I would think that an expert consultant would know that.
I know that you're not paid, and that I could probably earn the "Expert" designation if I answered enough questions.[deleted]
I'm quite certain that the rollout is the reason that both of my headsets had the same issue within days of each other, and so far, the exhausting hours I've spent trying to resolve this reading between the lines, and catching fragments of information, I'm 90% sure that I've found the workaround.
Even though I've been putting my Quest's on charge immediately for years, I've found out that delaying the reset a few hours is allowing the charge to proceed to completion.
[deleted]
