Does anyone know why my phone does this?

[Cheddarssssss]

I recently purchased an S25 and have been enjoying it, except for one issue. When the phone's battery is depleted and I attempt to charge it using a wired connection, a voltage symbol appears, followed by vibrations and an alert to remove the charger after about 30 seconds. However, wireless charging works without issue, and subsequent wired charging attempts function normally. I rarely use my phone near water, so I'm quite puzzled and would appreciate any assistance. Also yes i did rewrite this using Galaxy AI lol ヽ(●´ε｀●)ノ

[Tourbillon De La Vie]

What's the exact error? Battery depleted to what level? Does wired charge works if battery is less depleted like maybe 30%

Did you try different cables/charges? Samsung or 3rd party charger 

[arianwen27]

That's very much not supposed to happen. Are you using an official samsung charger with an official cable?

Have to say never experienced a phone screaming to be unplugged so this is a new one.

Just from what you've said, my personal thoughts is your charger is sending your phone the wrong voltage, then on trying again, it gets the correct voltage. Total guess so don't quote me on that

[Cheddarssssss]

Yes I think so. Lol it wasn't actually screaming😄

[Cheddarssssss]

I use the charger from the box. I meant to say when it fully dies and powers off. Also its the same problem with other cables.

[Cheddarssssss]

It's something similar to this and it just vibrates very loudly.

[arianwen27]

But you have no water icon right? Just a voltage symbol and an unplug message

[Cheddarssssss]

No, there is one.

[Tourbillon De La Vie]

Is that photo of your s25 with error message? 

[arianwen27]

Ah, then that leads me to think the phone is detecting moisture/debris in the usb port. The port has a lot of pins, lets say 4 to be simple. If any of them make contact with the others either by water, dust or something else, you get that warning.

So either something is up with the port or cable.
Or there's a bug and the message is showing when it shouldn't. And there have been reports of that, but not as extreme as you're getting