This update makes my phone drain it's battery every minute every minute, before it used to last 1 or 2 days active use, now it doesn't even last an hour, the ui all of it sucks, Samsung really needs to re think there terrible design, they need to fire all people that created this horrid trashy ui
It's been 5 days since my update, first 3 days I did notice faster drain. Today, the drain is too slow. ๐ i don't know what's going on. Maybe it's because i used the App Booster module?
Half the time my phone stops charging at 65%! And the battery doesn't last as long as it did before. This only started after the last update!!! Please fix this!!!!!
@kvain Did you wipe the device cache partition after the update? I recommend that you do this after every device update. It wipes out incompatible or outdated cache information which might be incompatible after the update. It does not erase any user data nor applications.
To wipe the device cache partition:
1. Power off your device. 2. Power up while holding down the Volume up key and the Side key until the Samsung logo appears. 3. An Android recovery menu will appear. 4. Use the Volume down key to scroll down to Wipe cache partition. 5. Click the side key to select it. 6. Use the Volume down key to scroll down to Yes. 7. Click the side key to select it. The Cache will be wiped almost instantaneously. 8. Click the side key to select "Reboot system now"
Since installing the One UI 7 update, my phone's battery life has significantly deteriorated. I've taken every possible step to conserve powerโadjusting settings, limiting background activity, disabling unnecessary featuresโbut nothing has helped. Before the update, I only needed to charge my phone once a day, and it would easily last from morning to night. Now, I'm having to charge it twice, sometimes even three times a day, just to get through. This has been, without question, the most frustrating and detrimental update Iโve received from Samsung. Iโm incredibly disappointed, and I sincerely hope thereโs a fix in development to address this issue soon. Can you confirm whether a solution is currently being worked on?
