
Some Pixel 10 Pro owners say their phone loses battery on a wireless charger after the November update — the screen says “Charging”, and the percentage falls anyway. Google has not acknowledged the reports, and wired charging still works, so this looks like a software fault in the November build rather than a broken battery. The evidence so far is a small set of owner reports; nothing yet shows the problem is widespread.
Featured image: the Google Pixel 10 series — Image: Google
What owners report
The first reports appeared on 12 November, a week after Google released the November update. Owners describe the same pattern: place the phone on a wireless charger, the lock screen shows “Charging”, and the battery keeps falling. Some see “Connected, not charging” instead. The drains are small but steady — the phone cools less, holds a charge less, and in some cases the owner wakes to less battery than the night before. The one detail that shows up again and again: wired charging works normally on the same phone, same battery, same day.
The reports are spread across Google’s own support forums and Reddit, with Android Authority and Android Police picking the story up after the first posts. Both outlets asked Google for comment and reported no reply. Android Authority noted it has no concrete evidence tying the drain to the update beyond the timing, and that matters: these reports are unconfirmed, and the timing alone is not proof.
Why this one is different
Wireless charging has tripped Pixels up before. Pixel owners have reported slow charging, chargers that stop and start, and “Connected, not charging” messages for years, and Google fixed some of those with software updates. The difference this time is the direction of the charge: the battery drains while the phone says it is charging. That points to the phone drawing more power than the charger supplies — or to the charger stopping while the phone still reports it as connected.
The November update is a natural suspect because it touched the charging stack. It brought the Pixel Drop features — full battery charge limits, the charging optimisation that learns a routine and holds the battery at 80% until just before the owner wakes — and it changed how the phone manages a charge. A bug in that logic could leave the phone charging at a trickle while the screen, radios and background work draw more than the charger delivers. That is a theory, not a finding: no one has reproduced the fault on demand, and Google has said nothing.
What is confirmed and what is not
What to do if it happens to you
What to Watch Next
The next monthly update is the test. If Google fixes a charging fault in it, the November build was the cause; if the reports keep coming, the fault is deeper. Until then, the honest picture is a small number of reports, a clear pattern, and no official word. This post will be updated if Google acknowledges the issue or a fix arrives.






