Skip to content
FixingBook
Verifiedintermediateest. 15 minutes

Stop Severe Idle Battery Drain on Android

Battery depletes rapidly even when the screen is off. Identify rogue background apps, location services, and network searching issues.

Confirmed working on: Android 12 · Android 13 · Android 14 · Android 15

Before you begin

Match the environmentUse this guide only for Android 12, Android 13, Android 14, Android 15 or a clearly compatible setup.
Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.
Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

Problem overview

Your Android device loses a significant percentage of battery life while not in use. You wake up to find the battery severely depleted despite the screen remaining off all night.

Common causes

  • Rogue applications constantly waking the device (wakelocks)
  • Poor cellular signal causing the modem to work harder
  • High-drain features left active, like Always-On Display
  • Unrestricted background data usage

Solution 1: Identify battery-draining apps

  1. Open Settings on your Android device.
  2. Tap on Battery, then select Battery usage.
  3. Scroll through the list to identify apps consuming high percentages of battery in the background.
  4. Tap a suspect app and select Restricted under battery usage.
Expert Tip

Install a third-party monitor like AccuBattery to view detailed wakelock statistics and identify exactly what prevents your phone from sleeping.

Solution 2: Restrict location permissions

  1. Go to Settings and tap Location.
  2. Tap App location permissions.
  3. Review apps listed under Allowed all the time.
  4. Change unnecessary apps to Allowed only while in use or Don’t allow.

Solution 3: Disable Always-On Display

  1. Open Settings and navigate to Display or Lock screen.
  2. Find the Always-on display toggle.
  3. Turn the feature off, or set it to activate only when you tap the screen.

Confirm the result

  1. Repeat the exact action that originally triggered the problem.
  2. Confirm the original error or symptom is gone and no new warning has appeared.
  3. If the guide changed a driver, service, package, or system setting, restart once and test again.
  4. If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.

Did this fix work for you?

Weighted Consensus Protocol

Consensus0%
Required100% (Weight 3)
Contributors0
Verified By YouNo
Your Weight--

Did this solution resolve your issue?

Confirming if this works strengthens verification statistics on the registry.

Sign In to VerifySign in required to verify

FixingTeam10,000 rep

Official Project Maintainers

The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.

Spotted something outdated? Suggest an edit. Maintainers review submissions within 48 hours.
Share:XReddit

Discussion (0)

No comments yet. Share your experience or verify if this fixed your issue!

Join the Discussion