One UI 7.0 charging issue

[coxs06]

After updating my S24 Ultra on Friday April 11th 2025 to the One UI 7.0 version, it no longer recognizes my Samsung superfast charging blocks. I did all the routine checks in settings. I checked the cable and blocks and still nothing. Prior to the update the phone was charging great using my Samsung charging blocks. After the update it no longer recognizes the charging blocks. However my buds pro 3, bose open ear and galaxy watch ultra, all recognize the Samsung superfast charging blocks. Does this One UI 7.0 version has issues? Is anyone else getting this problem?

[PrinceP]

Same issue here, S23 ultra

[Jswante]

I have the same issue after upgrading, super slow charging my S24+and my car charger simply does not do anything, this is ridiculous that after all this time and all the delays they would release something like this?  Hopefully they did not ruin Samsung phones, I have been using them forever!!

[Members_f8rgPCs]

Same here, charging stops and reconnects randomly, and also it never charges over 65%. After a night's charging it still says 65%. All this happend after latest update.

[PrinceP]

After recommendations, I have now reset the phone and cleared battery cache and the problem persists. The only other solution I was offered is to take the phone to a store. I think it's pathetic and laughable that an update can wreck a phone this bad without it being intentional?

[svga2000]

i have the same issue here , did any one fine a solution using Samsung original 45W charger with Samsung cable , it shows super fast charging for a second then stops charging. 

[T-Jo]

I have the same issue since updating to One UI 7, 3 days ago. Fast charge not working. Hopefully enough comments on this forum will get Samsungs attention.

[Dwatts]

I am also having a similar problem, the blue charging icon is just constantly popping up and the phone keeps vibrating.

[Marius1978]

I got the same problem on mye tab s8. No superfast charge. REALLY annoying.

[mehdick22]

My phone is a35 and I had the same problem after updating to one ui 7 and then I was able to fix it by clearing the cache.

[Maxmelon]

I agree, same issues for me after updating to one UI7