22-05-2025 01:57 AM
22-05-2025 02:20 AM
22-05-2025 02:32 AM - last edited 22-05-2025 02:35 AM
22-05-2025 04:13 AM
Hi @fadi00,
A drop in battery life after an update is often normal: the operating system changes and interacts differently with services, temporarily affecting power consumption.
A major update can also cause temporary instability because the system, having to process a large amount of new information quickly, keeps the CPU and internal resources constantly active. This leads to a temporary increase in consumption, but once the new instructions are “learned,” everything tends to stabilize.
To help speed up this stabilization, we recommend performing a wipe cache partition. This procedure is safe, does not delete photos, videos, apps, or messages, and helps remove outdated temporary data that may affect performance. It is also useful in case of slowdowns, crashes, or other abnormal behaviors after an update.
1. Completely turn off the smartphone.
2. Connect the device to a computer using a USB cable.
3. Press and hold the Power and Volume Up buttons simultaneously.
4. When the "Samsung" logo appears on the screen, release only the Power button, keeping Volume Up pressed.
5. Wait for a blue screen with the Android symbol or a warning message, then release the Volume Up button as well.
6. The recovery mode menu will appear: use the Volume Up and Volume Down buttons to scroll through the available options.
7. Select "Wipe cache partition" by highlighting it with the volume buttons.
8. Press the Power button to confirm the selection.
9. On the next screen, move to "Yes" using the volume buttons.
10. Press the Power button again to confirm the cache deletion.
11. When the process is complete, the recovery menu will appear again. Select "Reboot system now".
12. Press the Power button to restart the device normally.
22-05-2025 07:14 AM
Hi Everyone,
I had similar issues back on One UI 6, but after updating to One UI 7, everything was fine — the background activity and battery drain were gone. However, after about a month of using the new firmware, the same problems have come back again.
Honestly, either I find a solution to this soon, or I’ll give up on Samsung for good. This level of background drain and sensor activity is just unacceptable on a flagship device.
Please, check the data from gsam bat. I think it`s not OK. Also I receive -8% of battery by sleeping time today.
🔋 Battery Drain Analysis – Samsung Device (May 21, 2025)
Sharing some GSam Battery Monitor data for community insights. If anyone has suggestions to optimize background performance or reduce drain, feel free to jump in.
📊 Key Usage Stats:
CPU total usage: 3h 36m
CPU background: 3h 32m (!)
Awake time: 1h 17m
Wake locks: 7153
Wakeups: 436
Mobile data used: 23.22 MB up / 28.38 MB down
Audio on: 1h 27m
GPS: 4m
📍 Top Sensors Active:
STK33F11 Light Sensor: 3h 5m
Pressure Sensor (lps22df): 3h 30m
Step Counter: 13h 31m
Magnetometer: 1h 47m
Auto-rotate sensor: 1h 41m
⏱️ Top Wake Locks:
AudioIn & AudioMix: ~33m each
ImsService: 3.7m across 199 triggers
AssistantDelay & SystemJobs: multiple small but frequent activations
📦 Enabled System Packages & Services:
Over 100 system-level packages are active, including:
DiagMonAgent, ImsService, Device Health Manager, SmartFPSAdjuster, BrightnessBNR, and Bixby Wakeup.
Several sensor-related and diagnostic services are persistently running.
🧠 Processes of Interest:
com.samsung.android.lool and DiagMonAgent among top background players.
SmartSwitch, StickerCenter, Bixby Wakeup, and multiple system daemons active.
⚠️ Observation:
Very high background CPU use and persistent sensor activity.
Wake locks triggered by system jobs, assistant-related tasks, and diagnostic agents suggest heavy background processing.
📌 Looking for advice:
Has anyone found success disabling or optimizing background services like DiagMonAgent, Bixby Wakeup, or SmartFPSAdjuster without impacting core functions?
26-05-2025 05:28 PM
Funny how the mods only reply to say, if you don't have documentation we can help you, you are just overreacting, or no one else is having problems. (I too am seeing the battery drain issue a few weeks in now). But when you do provide the documentation, not a peep. SMH