[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AndroidSlave:
AlarmManager

Author(s): sven, credits to andy2na [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

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".

Here is a comprehensive guide to analyse Alarms: In order to find those Intents run the command dumpsys alarm.

This will dump all the alarm events so you can see what is invoking AlarmManager as a wakelock. From there you can find the culprits that have a lot of wakeups. In some instances, you cant do anything about it (Android System), but in others, you can uninstall or disable notifications. Hope this helps in solving your excessive AlarmManager problems.

Scroll to the " Alarm Stats" near the bottom, it should look like this:

com.levelup.beautifulwidgets

246776ms running, 10 wakeups

10 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATEWEATHER flg=0x4

1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4

com.motorola.blur.datamanager.app

22ms running, 0 wakeups

1 alarms: act=com.motorola.blur.datamanager.app.checkin.timeout flg=0x4 cmp=com.motorola.blur.datamanager.app/.DataManagerCheckinService

ccc71.bmw

130743ms running, 1585 wakeups

1585 alarms: flg=0x4

com.motorola.kpilogger

2156ms running, 0 wakeups

13 alarms: act=com.motorola.kpilogger.START_LOG flg=0x4

com.gau.go.launcherex

528ms running, 10 wakeups

6 alarms: act=com.jiubang.intent.action.AUTO_CHECK_UPDATE flg=0x4

4 alarms: act=com.jiubang.intent.action.SCAN_APPS flg=0x4

As you can see, in my case, the services that have invoked AlarmManager seem to be BeautifulWidgets (to update the clock everytime the minute changes - 1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOC K flg=0x4)

Battery Monitor Widget (obviously to pull the mW of the battery) - 130743ms running, 1585 wakeups

You could also reduce the amount of AlarmManager events by simply turning off Wireless location, Signing out of Google Talk, and turning off notifications or updates in apps you dont really use.

TLDR: 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.

Known conditions of occurence:

Related wakelocks:

References:

http://xdaforums.com/showpost.php?p=17207454&postcount=861

http://developer.android.com/reference/android/app/AlarmManager.html

AudioOut_1

Author(s): xda

Ranking: n/a

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.

AudioOut_3

User's experience

ConnectivityService

Author(s): sven

Ranking: n/a

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.

Known conditions of occurence:

Related wakelocks:

References:http://grepcode.com/file/repository.../ConnectivityService.java#ConnectivityService

deleted_wake_locks

Author(s): sven, credits to Tritonio_GR [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

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.

Related wakelocks:

References: http://xdaforums.com/showpost.php?p=27227201&postcount=5644 http://xdaforums.com/showpost.php?p=28915936&postcount=6671 http://www.netmite.com/android/mydr...k.chttp://elinux.org/Android_Power_Management

GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint

Author(s): credits to lmihaila [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

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

Related wakelocks: Other GTALK_ASYNC_CONN partial wakelocks

References: http://xdaforums.com/showpost.php?p=22786143&postcount=3416

network-location

Author(s): sven

Ranking: n/a

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

References:

http://developer.android.com/guide/topics/location/obtaining-user-location.html

http://developer.android.com/reference/android/location/LocationManager.html

PowerManagerService

Author(s): sven, credits to Entropy512 [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

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

Author(s): sven, credits to Tungstwenty [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

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.

Know actions:

Known conditions of occurence:

In relation with Chrome: http://xdaforums.com/showpost.php?p=28676218&postcount=24 In relation with Wifi turning on/off when the screen goes on/off

Related wakelocks:

References:

http://xdaforums.com/showpost.php?p=28836538&postcount=6603

svnet

Author(s): sven, credits to Entropy512 [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

Speaking Name: svnet

Rationale: basic radio management (Galaxy S/S II specific)

Know actions: No direct actions known, may be conditioned by using a different radio/modem

svnet dormancy

Author(s): sven, credits to Entropy512 [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

Speaking Name: svnet-dormancy / multipdp (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

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

Author(s): sven

Ranking: n/a

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: http://code.google.com/p/android/issues/detail?id=9307

SyncLoopWakeLock

Author(s): sven

Ranking: n/a

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

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

Sources: New implementation:http://grepcode.com/file/repository...droid/content/SyncManager.java#SyncManagerOld implementation (sync):http://grepcode.com/file/repository.../SyncManager.java#SyncManager.0SYNC_WAKE_LOCK

vbus_present

Author(s): sven, credits to Entropy512 [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

Speaking Name: vbus_present

Rationale: vbus_present is a kernel wakelock that is held when the charger is connected.

Know actions: No action required.

Known conditions of occurence:

When plugged in to charger / charging USB port

wlan_rx

Author(s): sven, credits to Entropy512 [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

Speaking Name: wlan_rx

Rationale: Wifi chip received a packet from somewhere - On a Galaxy S II, lots of these combined with the fact that the device takes 650 msec to resume from suspend and 150 to go back to sleep means that occasional wifi packets coming in will skyrocket Android OS usage. As an extreme example, run the following from a Linux box when wifi sleep policy is "never" and watch your deep sleep percentages plummet, your battery drain, and Android OS skyrocket: ping -i 5 <wifi IP address of phone>

Know actions: Use a sniffer to determine the cause of the traffic.

Known conditions of occurence:

Related wakelocks: wlan_wake References:

wlan_wake

Author(s): sven, credits to Entropy512 [MENTION=4906580]xda-dev[/MENTION]

Ranking: n/a

Speaking Name: wlan_wake

Rationale: wifi chip woke the CPU (Usually this fires and leads to a wlan_rx wakelock).

Know actions: Use a sniffer to determine the cause of the traffic.

Known conditions of occurence:

Related wakelocks: wlan_rx References:

***NEW***L2_HSIC:

HISC is the interface that connected the main Soc processor ( Also called Applciation Processor AP) to the modem ( 3G or 4G if there are two modems separately )

HSIC is uses the standard USB core library. And it is standard given by usb.org. The HSIC by itself consumes very less power and is one of the very power efficient and space efficient ways of interconnecting chips. Currently common to Qualcomm and Sammy Exynos architectures.

The reason seeing too many HSIC wake lock and other wake ups is due to the fact that the HSIC interface is waken up by modem (resulting modem scenarios are also so many) .

Also one important reason is EFS sync.

A concept : that the new modem architectures doesn't support a flash storage.(Saves lot of cost to manufacturer) .So every time modem needs to store something , it wakes up hisc interface and ask the AP (Main processor) to store it for him in his flash.

So this CP storing via AP is a fairy frequent activity even during suspend/deep sleep mode. Remember modem is periodically awake to do "Cell Update message" all the time.

I see the concern over this L2_hsic wake lock. I can say at this point that it is quite natural activity. and a necessary evil for smooth working of your modem( network 2g,3g,4g ) subsystem.

Every company including Sammy have some kind of power optimization done in the HSIC. So they taking care of this we considering fairy high battery drainer issue. .

If it is too high, modem/network can be blamed , if too many frequent network ( too many cell re-selection activity due to low RF reception) changes force the modem to do more activity, thus waking AP to do the work of storing its data over HSIC.