30-01-2022 03:59 AM - last edited 30-01-2022 06:12 PM
The super fast charging feature on my Note 10 Plus suddenly stopped working 2 days ago. Normally when I plug it in it says "super fast charging" and it will charge from 0% to 100% in an hour. But now when I plug it in it says "cable charging" and it's taking 2.5 - 3.5 hours to fully charge. I checked the setting and the "fast charging" option is turned on. I am using the Samsung adapter and cord that came with the phone and it is not damaged in any way. I even tried using my husband's Samsung adapter/cord (he has a Note 10 Plus as well) but it still said "cable charging". The phone charging port is clean. I have already tried to solve the problem by clearing the cache partition and I reset the settings...neither one worked. I then turned it off and restarted it in safe mode, but that didn't work either. I've read countless articles online and none of the DIY solutions worked. Can anyone give me any insight into what the problem is?
I ran a diagnostic test on it through the Samsung members app and I've attached pics of the results. It appears as if super fast charging is no longer a feature of my phone even though I've always had it up until 2 days ago and it's still an option in my phone settings. Idk but I feel like there is a software issue Samsung is not telling us about...
30-01-2022 11:19 AM in
Always if a phone takes more than 2.5 hours to charge, charger or cable are damaged. Look for a new charger official by Samsung. If my comment is helpful, please accept it as solution✔️😀
30-01-2022 03:31 PM in
Hi, the charger and cable are not damaged so that's not the issue. Plus my husband has the same phone so I tried 2 different chargers/cables and my phone still wouldn't super fast charge. However, when my husband tried them on his phone both chargers work and his phone will super fast charge.
21-02-2022 02:55 AM in
Exactly same issue here, after updating to latest update Android 12 One UI 4. Not a faulty charger or cable. Issues started appearing just after the update. @MonK17 , have you been able to solve the issue since?