S25 battery drains whilst wireless charging and time to full charge

[Gp261]

Every night I put my s25 on wireless charge, usually remaining battery is around 15% or so.  I get the usual text saying fast wireless charging and time to full charge. Battery protection of 80% is set.

Actual time to full charge (80%) is 4 or 5 hours rather than the 1 or 2 hours stated on the phone, times are dependent on the starting battery level.

Worse still is on a number of occasssions phone starts charging but then the battery drains whilst still charging. The phone position on charger does not get disturbed. Below is a couple of screen shots that show the battery level fall whilst charging.

Any ideas, suggestions or has anyone else had this happen.

 

[willcranston]

Is it a 3rd Party Charger?

[sarasphotobox]

Everyone is having issues battery drain whether it's plus base models or ultra

[Piper123]

Hey there and welcome to the Samsung UK and EU Community Customer to Customer Forum

Wireless charging is set to a maximum 15w whereas on a superfast charger you can reach up to 45w.

Charging from 15 to 80% on a superfast 45w charger takes about 45 to 60 minutes. On a 15w expect 3 to 4 x that so 3 to 4 hours.

[TomPulfrey]

And on s24 ultra, ever since I started one ui7 beta, my battery has never lasted me more than 1 day, where before it would last 2. Same setting and usage.. no even on stable one ui7, I'm lucky to get 1 full day.

[sarasphotobox]

Blimey no way so its definitely the software that's a bummer I went from one ui 6.1 s23 base model upgraded to s25 base model and updated it to one ui7

[TomPulfrey]

All through the BETA I reported bugs on battery drain along with many other users, so definitely seems like it's the software, and despite numerous reports,.the developers haven't managed to fix.

[sarasphotobox]

Yes you are right shame samsung ant sort it out for s25 and s25 series

[keith30]

Wireless charging takes longer than it would if you charge with a normal cable and charging brick.

[Gp261]

The time isn't a major issue but why doesn't the firmware state a realistic time? I don't expect you to answer that by the way.