[HTC One X] Goku80:
Wakelocks Definition

AlarmManager:

Speaking Name: Alarm Manager

Rationale: AlarmManager provides access to the system alarm services. These allow you to schedule an application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted. The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast. Once onReceive() returns, the Alarm Manager releases this wake lock. This means that the phone will in some cases sleep as soon as your onReceive() method completes.

Know actions: AlarmManager itself is not generating partial wakelocks but the applications (intents) that were set to be called when an alarm goes off do. Alarms can be listed through the menu "Actions - Alarms".

AlarmManager is a universal process that MANY apps use to update time, push you notifications, etc. In most cases, it is a necessity; in other cases, you should really check it out and disable/uninstall things that have invoked it too much.

AudioOut_1

Speaking Name: AudioOut_1

Rationale: AudioOut is used to play notification and system sounds.

Know actions: From the home screen... Menu -> Sounds -> uncheck "Touch Sounds", uncheck "Screen lock Sounds"

Known conditions of occurence: Each time the screen is touched or locked.

Definition: "AudioOut_1" is a Wakelock that is basically a kernel process that funnels data from audio apps to the audio hardware. It's what processes audio from say, Pandora or Slacker Radio, and passes it to the phone's audio hardware.

AudioOut_3

User Experience

But for those of you that have lockscreen sounds on, touch screen sounds on and dialpad touch tones on then you will have massive wakelock. I had this same problem with my S2.

Only way to beat this. Settings - Sound - system and untick the first 3 options. Reboot and charge your phone and then check the difference. You will see that the wakelock is not as high as it use to be.

More info regarding this you can find here

ConnectivityService

Speaking Name: ConnectivityService

Rationale: Service responsible for tracking data connection / apn, establish and maintain connections. This wakelock is held during transition between data connections.

Know actions: May be conditioned by using a different radio/modem or bad coverage, may be reduced by forcing 2G.

deleted_wake_locks

Speaking Name: deleted_wake_locks

Rationale: In the API available to android drivers it is advised to call wake_lock_destroy before freeing the memory of the wakelock struct that they created. This is done above all on shutdown, but also in a few situations where a driver is unloaded dynamically from the kernel. Whenever it happens, the destroyed wakelocks disappear from the list but their stats are added up to this pseudo-wakelock to the deleted_wake_locks. This allows knowing that a set of old wakelocks had a combined set of stats that this entry shows. The stats of this entry do not increase unless additional real wakelocks that have non-zero stats are destroyed.

Know actions: Since this is merely an entry that combines the activity of all the kernel wake locks that no longer exist, there's nothing that can be directly done to reduce this entry. The best course of action is to identify the wake locks that generate activity and that are later deleted, before that happens and they end up showing in a combined way on this entry.

Known conditions of occurence:

The Wifi driver is one known source for kernel wakelocks that are destroyed whenever the driver is unloaded (when Wifi is disabled manually or as part of the turn-off policy). Wakelocks such as wlan_rx_wake and wlan_wake, when the driver is unloaded, will no longer show up in the list and their stats be added to the deleted_wake_lock previous values.

GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservi ce.AndroidEndpoint

Speaking Name: AndroidEndpoint

Rationale: This wakelock has been found to occur under certain non reproducible conditions, showing high wakelock counts and in certain cases high wake times. As the reasons are not exactly known there is no garanty that this wakelock does not occur for other yet unknown reasons.

Know actions: In one case (see ref) this wakelock was successfully removed by changing the proxy / re-creating an APN definition and leaving the proxy blank for that APN. The "faulty" proxy was predefined for the provider Orange but it is not excluded that proxies from other providers show the same effect.

Known conditions of occurence:

Conditions are unclear, to be confirmed

network-location

Speaking Name: Network Location

Rationale: The network location service is responsible for providing coarse grained location information to requesting applications.

The frequency of updates (and of wakelocks) is related to the precision requested by the application (max. time between updates, precision in meters).

Examples of app requesting coarse grained location: weather widgets, latitude, most social tools, google+

Know actions: Actions to reduce wakelocks:

•	Find the responsible app: look for all network-location wakelocks and check for the responsible apps on the second line of the list

•	Check the settings of the app to see if the precision can be changed

•	Use the benefits of Wifi based location (stable location minimizing the update frequencies)

•	Look for alternative apps with a better design

Known conditions of occurence: Poorly designed apps with too high requirements on precision will drive the Network Location Service up.

Unstable network conditions (frequent handovers between towers) may trigger location updates.

In some cases updating the radio/modem has effect on the network location: the location is based on the tower information delivered by the RIL.

Related wakelocks: LocationManagerService, NetworkLocationLocator, WifiService, GpsLocationProvider, network-location-cell-update

PowerManagerService

Speaking Name: PowerManagerService

Rationale: This kernel wakelock is a placeholder for all partial wakelocks being held in userland.

Know actions: Use "Partial Wakelocks" to drill down the applications / services causing wakelocks.

Known conditions of occurence: Some devices show userland wakelocks as a total named PowerManagerService

suspend_backoff

Speaking Name: suspend_backoff

Rationale: suspend_backoff is triggered whenever there's a rapid succession of sleep-wakeup-sleep transitions in a short period of time (10 occurrences within x ms IIRC). When that happens, SB makes sure the device is continuously awake for a bit instead of alternating a lot. The KWL count indicator could give a hint about the source of those continuous wakes, but not a definite answer because it doesn't show their time distribution.

Known conditions of occurence: Read here on how to tackle this wakelock and read here to

svnet

Speaking Name: svnet-dormancy / multipdp from the man himself(those are synonyms, depending on android version)

Rationale: svnet-dormancy is a kernel wakelock related to cell data transfers - Fast dormancy or not, you get a 6 second wakelock any time the radio transfers data..In other words, the phone stays awake for 6 seconds for every incoming data packet which effectively prevents it from sleeping.

Know actions: Change the duration of the wakelock (use at your own risk). Reduce the wakelock by reducing the amount / number of data traffic requests

Known conditions of occurence:

Caused by data traffic

Sync:

Speaking Name: Account Sync Service

Rationale: The sync service is responsible for syncing all the accounts from "Settings" - "accounts and sync". A wakelock is held while the sync process is running.

The more items are getting synced and the more often the sync occurs the higher the wakelock time will be.

Potentially the wakelock time is prone to raise in case of bad data connectivity.

Examples of accounts are: twitter, google+, linkedin, google mail

Know actions: Actions to reduce wakelocks:

•	Remove any unwanted accounts

•	Check the settings and remove any unwated options (contact sync)

•	Check the frequency of the sync and see if you really need it as defined

Known conditions of occurence: Under bad data connectivity conditions, with poorly designed Sync providers

Related wakelocks: none

References: A known bug related to gmail:Email app wakelock

SyncLoopWakeLock

Speaking Name: SyncLoopWakeLock (Account Sync)

Rationale: SyncLoopWakeLock is the wakelock used by the Android SyncManager (android.content.SyncManager) and was introduced starting in 4.01. The sync service is responsible for syncing all the accounts from "Settings" - "accounts and sync". A wakelock is held while the sync process is running.

The more items are getting synced and the more often the sync occurs the higher the wakelock time will be.

Potentially the wakelock time is prone to raise in case of bad data connectivity.

Examples of accounts are: twitter, google+, linkedin, google mail

Know actions: Actions to reduce wakelocks:

Remove any unwanted accounts

Check the settings and remove any unwated options (contact sync)

Check the frequency of the sync and see if you really need it as defined

Known conditions of occurence: This wakelock is held by the SyncManager while handling sync actions (method handle()). Previously this wakelock was known as sync. Under bad data connectivity conditions, with poorly designed Sync providers this wakelock is held longer.

Related wakelocks: sync https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/sync

Which stated as above both similar and can cause same drainage if not tackled properly.

com.android.phone(under alarms,BBS)

Way to beat it:

1. Choose SETTINGS - WIRELESS CONTROLS - MOBILE NETWORKS -

2. uncheck everything unnecesary ie. "Data Roaming" and "Enable always-on mobile" -

3. Change setting on "Use only 2G networks", wait 10 seconds, then change it back.

4. Now try NETWORK OPERATORS. Here you will get a network error (Not the "com.android.phone" error)

Just continue and you'll get your wanted network.

The reason for this behavior is that android uses a new type of network and supports old ones.

Some countries dosen't use this new network.

When your android phone makes a handshake in these countries it'll accept without error, but when it returns to the new type it won't connect.

This must be a bug and you can solve / workaround this by doing the above