13-04-2025
10:11 PM
- last edited
05-05-2025
04:00 PM
by
ChrisB_
Hello has anyone else experience faster battery drainage after updating one UI 7 on your S24 ultra and if you have experience the same thing has anyone been able to sort out the issue and if yes what have you done
05-07-2025 05:37 AM
So been trying to find the source of the problem, one possibility is that the problem may be in the problematic "Digital wellbeing" app which cannot be uninstalled or kicked out.
The app gives itself unrestricted access to data,and this data usage spikes whenever the phone is overheating.
This leads me to believe this is 100% spyware.
05-07-2025 06:33 AM - last edited 05-07-2025 06:34 AM
We're almost 3 months after the first reports regarding this MAJOR battery/heat issue linked to ONE UI 7 upgrade and yet, Samsung said nothing so they cleary don't care at all about their (too) many customers affected by this issue and are patiently waiting that we said nothing anymore...
It's so crazy & ridiculous to think that we will just accept that our phone will not work properly anymore and be OK with it!
Samsung you took months to build, test & deploy this upgrade and despite that, it's a complete nightmare!! Shame on you for that and doing nothing to help your customers.
On my side, i'm waiting to see if ONE UI 8 will finally fix this issue and if not, despite the fact i was suppose to keep my S24 for many years, i will get rid of it and NEVER buy a Samsung phone again.
07-07-2025 07:41 AM
Is there any fix to this issue. I was getting 5-6 hours of screen on time of 80% charge (my battery limiter). Now I am getting around 3-4 hours after the update.
11-07-2025 09:02 AM
11-07-2025 09:03 AM
11-07-2025 10:14 PM
624 messages is a ***** lot, anyway not 100% how it got fixed for me, but I turned off power saving and battery protect and then (accidently) let it drain to 0, i then let my phone charge to 100 (and more possibly), presumably completely filling it up and it seems to have recalibrated itself. Now my battery is quite literally excellent.
14-08-2025 08:36 AM
4 months later still the same problem : UI7 draining battery.
we've made various tests and had been able to identify the exact version of One UI that caused battery drain. It did not begin with one UI7 but with the two previous update.
For comparison, with february 2024 update, a S24 ultra is able to stay on for 22 hours with a heavy and diversified use.
We now have a lot of data, from various phones with various software version.
It seems problem is a spyware introduced through the digital behaviour app from Samsung. This spyware is using a lot of power.
For now, the only solution is to downgrade your one UI version to an earlier version.
Public Action will be taken and data will be exposed.
Grats Samsung you wanted to spy and you lost a bunch of customers.
14-08-2025 07:11 PM
Yes definitely my case also. I am seriously considering if I should keep on buying samsung phones after this. Pushing customers to buy the latest phone to get good battery autonomy through software updates is not a great strategy. I've Been buying samsung phones since forever and now I am questioning that choice!
Better hear an explanation from customer service and problem solving or am done!
05-09-2025 07:52 AM
I thought there are less people affected by us. But now I know we are alot and Samsung should take this matter seriously. Their product is not working properly and needs to be fixed if they want their customers to be retained.
a month ago
Update: I have been able to fix this, though I'm trying to recall how. It was a while back.
I found some advice about clearing something. Sorry if this is cryptic, hopefully not on this thread. Clearing a kind of low-level cache file which holds statistics about battery history, so the phone is forced to rebuild it. I'm not convinced that step was 100% necessary, but following that my Galaxy S24+ did re-learn how to charge the battery and started lasting longer again. Also stopped overheating. I may have done something else too, akin to fully discharging it a few times. But it was basically a miscalibration.
If I could recall exactly, then I'd say more. But since I previously contributed to this thread, my purpose here is just to update and say that it's user fixable.