> Attention!

New threads need to be created only inroot partition! In the future, they will be processed by moderators.

If you posted a new version of the program, please notify the moderator by clicking the "Complaint" button on your message.

Catalog of Android programs



BetterBatteryStats | battery monitoring



Rep: (1189)
BetterBatteryStats
version: 2.5

Last update of the program in the header:23.01.2020

Attached Image

screenshots
Attached Image

Attached Image

Attached Image

Short description:
Utility to monitor battery discharge when the phone is idle.
Description:
Fast battery discharge is often a problem for those who use their device to the maximum.
With this application, you can analyze which applications consume battery power when the phone is idle, as well as view detailed information about energy consumers.
Developer: Sven Knispel ( chamonix )
Homepage: http://blog.asksven.org/
Google Play Web: https://play.google.com/store/apps/details?...terbatterystats
XDA Forum: http://forum.xda-developers.com/showthread.php?t=1179809
Russian interface: there is, starting with 2.0.0.0B5
Current version: stable - 2.5 , 2.4 , 2.3 / beta 2.5-341

More screenshots (caution, traffic!)
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
About the program
ESSENCE OF THE PROGRAM: find out what prevents the phone from sleeping when it should sleep, and not the battery consumption during operation.

Main functions:
- General overview of "other statistics": wakefulness percentage, deep sleep, screen on, phone on, Wifi on, Wifi used
- Core kernels
- Partial wavelets
- Signals / Awakenings
- CPU statistics
- Network statistics
- Process statistics with system and user time

BetterBatteryStats accesses the "batteryinfo" service (battery information) of Android, retrieving already existing data without including additional resources.
BetterBatteryStats is focused and tested on Froyo, Gingerbread, Honeycomb, ICS on various firmware and kernels.

What are wavelets and why should you take them into account?
When it comes to Android, the most discussed and commented topic is battery consumption / life expectancy. If it is allowed that the battery is consumed when using the phone, then its slow consumption during “doing nothing” is disturbing.

Wavelets, or more precisely, partial wavelets, are a configuration (or class) that helps developers be sure that important parts of their code will not be interrupted.
Basically, the phone has three states (simply, do not be offended, the developers of the cores):
1. Waking when the screen is on
2. Wakefulness
3. Sleep (the most preferred state of your phone)


Transitions are carried out from wakefulness with the screen on to just wakefulness and, finally, from wakefulness to sleep. While you are using your phone, it is in the (1) state and does not allow you to log out of it while you are interacting with the device in an interactive mode. If you stop using it, the phone tends to go to (3) as quickly as possible.
And here the wavelets act: since our phones are smartphones, the processing of the processes takes place in the background. Some of these processes are important, such as a phone call, listening to music, or synchronizing contacts.
Since the phone tries to go from (2) to (3) and, on the other hand, you don’t want to hang up while talking, the application holds the wakelock to prevent the transition. When you hang up, a partial wavelet is released and everything ends (the phone goes into sleep).

Thus, partial wavelets are a tool, and not something that we should discourage for some reason. But there are cases when the design of the application is not tested in real life conditions (for example, a bad signal or lack of coverage) and wavelets produce a negative effect, as they are retained unnecessarily or for too long.
BetterBatteryStats determines these wavelets and, using your knowledge or knowledge of our users, you can understand what is happening and find a strategy for change for the better.

If you need help
Always post full information when asking for help. In most cases, you need a dump file, and sometimes screenshots that demonstrate your observations can also help.
Dump preparation
To analyze the battery consumption, you need a BBS dump duringinactionphone !!!!!
(I repeat, THE ESSENCE OF THE PROGRAM: find out what prevents the phone from sleeping when it should sleep, and not the battery consumption during operation.)

Note for ownersXiaomiand other devices onMIUI: to create a correct dump, please readthis post.

1.Make sure that the battery_stats and dump permissions are granted (with root they are automatically provided during installation, without root - see the second paragraph F.A.Q.)
2. Charge the battery if the charge is not enough (better if the charge is not 100%, but, say, 60-70, in this case the dump will be more real).
3. Close all programs, including BBS, turn off WiFi.
4. Clear the recent window (in Xiaomi and on Android 7, do thisnot necessary).
5. Connect / disconnect the charger.
6. Leave the phone idle for 4 hours or more, preferably overnight.
7. Open the BBS, make sure that the labels are: from - disabled (unplugged), to - current (current).
8. Save the dump:
Attached Image
Attached Image
Attached Image
Since version 2.3, files are saved to the folder at android / data / com.asksven.betterbatterystats_xdaedition / files / download
9. Open the dump, check that all items are displayed correctly. If not, try again. It makes no sense to lay out an incorrect dump, in which, for example, there is no information about the waking time, the item "Alarms" or "Kernel wakelocks". Nobody can decipher such a dump to you, so please, do not forget to view your dump before publishing.
10. Publish the dump as an attachment to the post.

ATTENTION!
According to the rulessavagemessiahzine.com, pictures hiding under the spoiler!
How to do this, read the topic in the header "FAQ on the forumsavagemessiahzine.com" under spoiler number 22:
Attached Image

If you place an image from your phone, read how to hide the image under the spoiler,here.
In the end, you can do it all manually.
- attach file (select file-upload);
- put the cursor in the message on the right place, in the menu "management of current files" click on the green plus sign next to your attached image - it will be inserted into the message in the form
[attachment = 5931454633.PNG]
- before this hands type
[SPOILER]
thereafter
[/ SPOILER]
- in the message after this, the line should look like this:
[SPOILER] [attachment = 5931454633.PNG] [/ SPOILER]
- everything, your picture under a spoiler.

It is preferable to attach the dump as a supplement to its contents are not indexed in the search topic. If you decided to insert into the message dump (not recommended), please,remove it under spoiler! And yet, cut off everything that comes after the line. "human readable part end here" , it lists the technical information JSON, which in its normal form is already in the first part of the dump.

Note: To insert a dump into the message, do not open it with a notepad, it will turn out like this, and no one can disassemble it:
Attached Image
Open through AkelPad, WordPad, Word or via a browser, for example, Chrome. To prevent Russian characters from being displayed as krakozabrami, choose Unicode (in chrome, you must install the extensionSet Character Encoding).
Attached Image

Attached Image

Attached Image

Attached Image

Attached Image

Attached Image

Attached Image

Messages with pictures or texts of dumps without a spoiler will be silently deleted without considering the essence. It is assumed that you have read these instructions before placing the dump. So no offense.
Stillherebriefly chew various options for preparing the dump.

It is best to ask for help directly in the developer topic onXDA. But for this it is necessary to make a dump in the original, untranslated version of the program, otherwise no one will understand anything there. Before publishing the dump, please make sure that the labels for the core wavelets and signals are processed correctly. Reading the dump takes a few minutes and it will be great if you do not waste the time of the one who will study it to help you. The developer will not respond to posts with incomplete dumps.
Well, if it’s not very good with English, then this topic was actually created for this ...

Video instructions for creating a dump using a custom label.

If you want, you can deal with the dump yourself. Examplehere.

Other questions about the program and work in it, wakelock guide, frequently asked questions, knowledge base (including an alphabetical index to the problems discussed in the topic) and tips on energy saving can be found by clicking on the links below (BBS and waveform reference , FAQ)
Reference materials on the BBS and wavelets
Frequently asked Questions

Q: Why must a dump be made while the phone is idle?
A: There is no separation in the dump, what happened during the operation of the phone, and what happened during inactivity. Each section lists the processes that occurred over the entire period of the dump. Accordingly, if you used the phone before removing the dump (and you do not need to convince anyone that you did not use it, because the graphScreen on it reflects perfectly), the dump will be present everything services related to your work with the telephone, wavelets, receivers, etc., that is, that should not wake the device and what must be present while using the device. And it is impossible to separate the processes that were launched during the active mode from what was happening during inactivity! Therefore, an analysis suggesting that it is necessary to limit or deactivate is not possible.

Q: How to install the BBS system application in Kitkat / Lollipop?
Рћ: From the version2.2.0.0B4 installation of the system is not required, everything works fine without root (without root - see the next question).
But it happens on some phones that no permissions are granted, therefore, just in case, the installation archive of the system recovery:Attached fileBetterBatteryStats_SystemApp_xdaedition_CWM_1.3.0.0.zip(212.59 KB)
and archive of removal of this system from the same recovery:Attached fileREMOVE_BetterBatteryStats_SystemApp_CWM_1.3.0.0.zip(140.69 KB)


Q: If there is no root, does it make sense to put this program?
A: Without root, there is no statistics of partial wavelets, signals and network, that is, it will be simply impossible to understand anything from the non-ruled phone dump, so if you do not have root on your phone, the program will only show statistics when you grant permissions to the program via adb:
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS

ForAmazon FireHD8users recommend more
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.PACKAGE_USAGE_STATS

If you have a version from the market, instead of com.asksven.betterbatterystats_xdaedition, write simply com.asksven.betterbatterystats. Detail process is paintedhere.
P.S. on some devices, after attempting to grant permission to the DUMP, the ADB system writes that the application did not request this permission. Then calmly skip this command and provide BATTERY_STATS.
And do not forget that in the path to the folder with ADB on your computere should be Russian letters.
To solve problems with providing access to MeД±zu, seehere.
If all this does not help, then, alas, it makes no sense to install the program. UsersreportThat without root on some phones with Kitkat there are no statistics at all, in particular, on S4.

Q: I have a significant wlan_rx wavelock. What is it and how to deal with it?
A: The reason for this wake kernel is waking your Wifi device. To avoid this, you should turn off Wifi if you are not using it, use your Wifi control program or try to find and remove the cause. Another reason may be incorrect configuration of the router. Borodovich conducted a big analysis of this issue, search his posts for the word wlan or router, for example,here.

Q: Google Maps causes a lot of battery consumption. Do I need to freeze them?
About: No, Karpfenhai made upstep by step instructionson setting up autorun and location service to fix this problem.

Q: Do you know about a bug in a BBS when SuperUser asks for permission again and again?
A: As you noticed, this SuperUser asks again and again, this is not a BBS bug, the BBS only makes a request for superuser rights. Read morehere.

Q: BBS shows "no ref since unplugged" (no tags from disabled)
A: Starting from version 1.9, it is necessary to connect / disconnect the device to the charger after booting in order to create the label "since unplugged" (disconnected). Starting from 1.10, there is a new label "since boot" (from boot) and in the settings there is a reset point to this label, if no other one is found.

Q: Why can't I just skip deleting tags when loading?
A: If the author could do this, he would do it. In short: BBS is a passive monitoring tool; This means that it does not process continuously, but simply compares the data. The disadvantage of this, therefore, is that there is no point in comparing the counters between two labels (for example, "since unplugged" and "current"), if the counters were reset during this period. In fact, this will potentially lead to negative values, in any case incorrect.

Q: What do the colors of widgets / graphics mean?
A: For a large widget: the colors correspond to the values ​​"From" - from (blue), "Deep sleep" - deep sleep (green), "Awake" - waking (yellow), "Screen on" - screen on (white), " Kernel wakelocks "- core wavelets (purple)," Partial wakelocks "- partial wavelets (blue). 100% is the maximum of these values.
For a small widget:
Attached Image

Q: What do the colors and abbreviations on the tab processes and core kernels mean?
A: In the details of the processes:
Red- system time,blue- user time.
UID- user ID of the Linux application. Each application runs under a specific user (and can be part of numerous groups), which allows you to control which applications have access to folders and files. This, however, is not particularly important.
Sys- the amount of time during which the application consumed CPU, using the kernel code (in the interests of the application). These are things like I / O, maybe graphics visualization, and other rubbish occurring in the kernel.
Us- the amount of time during which the application consumed the CPU using the "normal" code, i.e., the code of the application itself. Calculations, for example. The sum of user and system time gives the total amount of time a CPU application consumes.
Starts- the number of times that the application was launched (restarted) during this period. It can show 0 if the application has already been launched, when the countdown from the initial label started, 1 - if it was launched once. or, for example, 29-only times the application was opened and closed during the specified period.
In kernel kernels:
C- count, the number of times the given core wavek was activated
WC- wake count, the number of wake-ups - the number of times that the waveclock was first activated after the device went out of deep sleep (it may mean that it is somehow related to the cause of the awakening, but it may not have a relation to it. such as the wave monitor battery monitor on SGS2)
EC- expired count, the number of elapsed. Veykloki nucleus can be activated countless times (to be released completely) or for a specified time period. If they are activated for a time period and are not released during this period, they are released automatically and the counter is incremented by 1. For example, veykloki SMD_ * can release themselves after some time after activation (~ 440ms per SMD_DATA5, for example). So programmed driver. As for PowerManagerService, it never ends, because Service, which controls the veykloki openly requests the use / release of veykloka.


Q: Where is the dump file and logkat / how are the files called?
A: From version 2.3, files are saved to the folder at android / data / com.asksven.betterbatterystats_xdaedition / files / download, they are called BetterBatteryStats-<time>.txt and logcat-<time>.txt, where the time is specified in the format "yyyy-MM-dd_HHmmssSSS".
Prior to this version, the default files were saved to the root / sdcard, the folder specified above could be selected in the advanced settings.
On Android 7 with any version of the program, the file cando not persistto SD-card root, check the options in the settings save to the above folder and look for a dumpthere.

Q: Did you know that BBS does not work properly for additional users (Android 4.2)?
A: BBS works fine for additional users until you turn on the root feature. The reason is not in the BBS, but in the absence of support for the multiuser mode in the superuser / supersu version you are using.

Q: What is * overflow *?
* overflow * (brute force) is the notation that the statistics counter has exceeded the limits. This can happen if you did not restart the phone for a long time, or some kind of wake-up / wake-call process happened too often. The only way to find out what lies behind * overflow * is to reload and collect fresh data.

Q: Why isn't the 'screen off' label being created?
A: To create this label, it is necessary to turn on the standby mode.

Q: Even after connecting / disconnecting from the charger, no tags are displayed on the device, except for 'boot (from boot)'
A: Something is preventing the registration of a shutdown event from the memory in the BBS. Check for tools such as greenify or stamina mode to mask such events and make sure the BBS is on the white list.

Q: What is standby and how does it work?
A: Standby mode - a feature that helps you to analyze what happens when the screen is off. When the standby mode is turned on, the screen turns off to create a tag 'off screen'. In the configuration mode, you can also create a label 'On screen' when the screen is activated (unlocked). Optionally, the standby mode will notify you when the screen is turned on and the ratio of awakenings more than the threshold of awakening. To avoid unnecessary treatment, the duration of the threshold can be set to turn off standby mode in a short period of the screen is turned off.

Q: My log file is empty, it says "Unable to open log device '/ dev / log / main': No such file or directory".
A: Check if you have a custom kernel that disables logging. If not, some file permissions may be missing: use the permissions fix function in recovery.

Q: The core wavelets display does not work.
A: Your firmware / kernel does not allow you to read system files (or the necessary files are not created by the system). Check the presence of the file / sys / kernel / debug / wakeup_sources and if there is any information in it. If not, then logging is disabled, as an option, you can try itturn on. There are andanother variantorhere. The latter solution, such as correcting the absence of core wavelets and sensor statistics, including on Android Nougat,here. You can still lookhere.

Q: Why is my dump showing sparks?
A: To open a dump containing Russian letters, you need toUnicode Encoding (UTF-8).

Q: How to get rid of GSF / GMS wake calls of Google search?
A: GSF (google service framework) can not be avoided and in no case can not be frozen(opinion of the author of the program). HereThere are some settings that will help reduce it (for exampleSystem tuner). Also in the topic on xda recommend settings fromKarpfenhai. Hereit also gives updated and updated settings.
Alternatively, you can downloadthis archiveand unzip to computer. Connect the phone to the computer and run DISABLE - to disable the components, ENABLE- to turn on. In this case, you do not need to install any System Tuners on the phone, etc., the only thing is that adb drivers must be installed on the computer.
Settings from Karpfenhai
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image

Attached Image
Attached Image
Attached Image
Attached Image

Attached Image

Attached Image
Attached Image

Attached Image

Attached Image

Attached Image
Attached Image

An example of a fundamental deliverance from Google is described.here. If complete deliverance is not included in your plans, you can partially remove these wavelets. So, Google search, constantly waking up at night, can be pacified by disabling Google Now.
An example of My Android Tools settings for disabling Google’s push can be viewed.here.
An example of a phone without Google -here.

B: Other statistics are incorrect. It shows "No data connection" and "No or unknown signal (no or unknown signal)" when Wifi was turned on all the time.
A: "No data connection" and "No or unknown signal" refer to a mobile data network (2G / 3G). Since Wifi was turned on for a while, the mobile transmission was turned off, respectively, indicated in the statistics: this is provided by the application

Q: I have a lot of NLP wavelets. Can I do something about this?
ABOUT:Heregives a good overview on NLP and what it affects (thanks @ Perseus71)
Translation Post Perseus71
Network Location Provisioning is essentially a software equivalent of a GPS receiver chip in a phone. And by itself, the process is harmless. He coordinates the location when the task is to do it. This is done by reading the chip sensors. This creates an internal partial wavelock that keeps the phone awake until the end of the chip reading.

However, if some applications continue to trigger this process to ensure accurate location every second, the waveclock will begin to swell. Now let's talk about the other side of the coin.

Google tried to integrate Google Now as closely as possible with the Android system to reduce the size / performance of the Google Search application. In order to do this, they integrated the NLP receivers into the Google Play Service. (Just like GCM receivers for Google Cloud Messenger). Thus, the Google Play Service becomes a common basis for all applications, unifying the place for them.

Now the Play Service has grown and healed with its own life. Even if you don’t have Google Search on your phone, the Play Service will hold the NLP polling process. He will also periodically continue to contact the database (I mean the Google server) on this issue. It is used to send targeted ads to your phone, depending on where you are. This whole thing drains the battery to the remainder.

In addition to this, there is the recently appeared catastrophic and super-faulty "Scan always" option in the advanced Wifi settings, adding even more stress on this issue.

There are only two ways to effectively tame this unbridled behavior.

1. Turn off the location service. This silences the NLP process, cutting it off from the source. Radically, in its own way.
2. Turn off Google location reports. This is in the Google Settings app. This turns off what I mentioned above.


B: In firmware based on CM12, the launcher crashes when trying to place a widget. When will this be fixed?
A: The author did not find an error in the BBS code - the failure occurs in the launcher, and not in the BBS. After spending some time researching the problem, the developer concludes that CM12 is to blame (other firmware on Lollipop does not have this problem)

Р’: On Android 7 constantlypops up a windowreporting an application problem.
A: Dependence on the presence of the widget. If the widget is not installed, there is no problem.

Q: On Xiaomi, statistics are collected incorrectly. What can be done?
A: Lookhere. In general, a competent alignment on energy savingexactly on Xiaomi. In order for statistics on MIUI to be collected correctly,Murrrzaffka published more than detailed instruction .

B: What does the Greenify program do when putting applications to sleep?
A: Author BBSwriteson this occasion:
In battery consumption, there are concepts of wavelets - these are symptoms and signals (of awakening) - causes.
Greenify helps to correct errors in the structure of the application at the level of the cause, while many applications are trying (unsuccessfully) to deal with the symptoms.
Greenify seems to use the innovative method of “aligning” signals in such a way that when you wake up the phone, as many applications as possible use this slot, instead of creating multiple wavelets one by one.

Q: How to track in detail the Internet traffic of the phone?
ABOUT:tester99makes specific recommendations on this issuehere. Programsthat you will need, see the review fromborodovich .

Q: How do I know which services consume energy in the background?
A: If you have Android 4.4 and higher, go to the options for developers-process statistics. Read morehere.

Q: What can I do to make tags work on Xiaomi and on 7 Android?
O: BBS application needset to autoload. And in these conditionsnot necessaryclear in ram bbs.

Q: Is it possible to disable wavelets and background activity altogether?
ABOUT:Can, but it is worth seriously considering whether it is necessary and what consequences it will bring.

Q: The program does not start even when granting permissions via ADB, what can I do?
A: You can tryput other versions of the application.

Q: Why is full Russification stopped?
ABOUT:I recommend everyone to use the original version of the program.The application is officially translated by me from version 2.0.0.B5. Terms that are not translated are tags and statistics items, which are explained in the reference post. The results of the survey and the conclusion of the termination of the complete Russification -here.

Q: Why is my question no one answers / my post is deleted?
A: Make sure that you have posted a dump made according to the rules indicated in the header. You should not convince people that the dump is made in inactivity when there is significant activity in the "screen on" line. See if there is an answer to your question in the alphabetical directory or frequently asked questions. Do not be lazy and use the search on the topic.
Alphabetical guide to wavelets, signals and processes covered in the topic
Here are the terms discussed in the topic. Before asking a question, look here, maybe a similar problem had previously been raised by someone and the answer is already there.
The terms relating to Linux kernel drivers, respectively, are also found in the names of kernel wake cores, you can seehere.
ab8500-gpadc and below
ACTION_CHECK_NETSTAT
ACTION_CHECK_QUEUE
ActivityManager (wakelock guide)
adsp
Alarmmanager (knowledge base)
alarm_rtc (wakelock guide)
Alarmtimer
Alsps_wakelock
Analytics , still and here
android.appwidget.action.appwidget_update , here still and here
Android.intent.action.Time_tick , here still
android.process.media
ApmAudio, ApmOutput, AudioOutLock
AppMeasurementService
AppOps
AudioOut_1 (knowledge base, wakelock manual)
AudioOut_3 and AudioOut_2 and wakelock guide ( reference post )
audio_pcm and audpp
backup (Android system) , still and still
bam_dmux , here still
baseband_xmm_power
BatteryServiceUpdateStats
battery wakelock
batt_work wake lock
bbd_wake_lock
BBS_WAKELOCK_WHILE_SAVING_REF
bcm4773_wake_lock
bcm_sdhc.3
bln_kernel_wake_lock
bluesleep
CallerInfoCache
ccci
ccci_fs.h
CCCI1_NET_V2
ccmni wake lock
cc_wake_lock
cdc_acm
charger wake lock and here (same as battery wakelock)
ChargeRTC
Chekin service (wakelock guide), here decision
chimera , still
com.android.internal.telephony.gprs-data-stall
com.google.android.gms
com.jamworks.bxactions
com.kavsdk here Pictures
com.mapswithme.maps.pro.MAPS.ME
com.sec.epdg
com.UCMobile.intl
com.xiaomi.hm.health.Mi Fit
ConnectivityService (knowledge base, wakelock manual), still
CONTEXT_MANAGER_ALARM_WAKEUP
ContextManagerWakeLock
copresGcore_EventLoop
decon_fb (xxxx.decon_fb)
deleted_wake_locks (knowledge base, wakelock manual)
DeviceIdleController
dmagent_wakelock and here
DocumentService WakeLock
dofstrim
Doze Interactive Time
DPRAM , still
dwc3
ehci_pm, ehci_rwu and below
Eint , here version , still and still and interesting observation . AND here information.
epol
event0, event1, event2, etc.
eventx-xxxx , here is the instruction read more here
Event log service , here still , here decision
f995e000.uart
fiid-sync
Firebase
fast dormancy
fuelgauged
Gbmoddisplay
GCM_RECONNECT
Google
Google Cloud Messaging (GCM)
Google Play Market , still
gpio_kp
GsmCellBroadcastHandler , still from here and further
GsmInboundSmsHandler , decision , still
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (knowledge base, wakelock manual)
heartbeat
hold wake buttom
hsi wakelock
HVDCPD_WL
IPA_WS
ipc
IPCRTR_lpass_rx
isp_lock_wakelock
kworker , here
l2_hsic
LightsService.action.UPDATE_SVC_LED
lli_cp_wlock
location
mali_wakelock , here still
mbroadcastwakelock
MCS_HEARTBEAT
md1_cldma_peer
mdm_hsic_pm0
Measure
MediaScannerService (wakelock guide)
mhl_wake_lock
Mifit
migration / 0
mipi_link (knowledge base)
MIUI
mmc0_detect, mmc1_detect, mmc2_detect (wakelock guide), here
mmc_delayed_work
msm
msm8x16_wcd_codec-1
msm_hsic_host
msm_otg and here
msm_serial_hs_rx
multidpd
multipdp
musb_autosuspend_wake_lock (wakelock guide), here
net_scheduler and here
NETLINK and here and option
netmgr_wl
network-location (knowledge base)
NetworkLocationLocator, NetworkLocationCallbackRunner (wakelock guide)
Networkstats
NlpWakeLock, NlpCollector
nsrm_wakelock
null.DISCONNECTION_ALARM , null.CONNECTION_ALARM
Offloadtrack
otg_default
Phenotype
PhoneWindowManager.mBroadcastWakeLock and here
pil-wcnss
PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Play market , still
pm8921-charger-heartbeat
pm8xxx_adc
Powermanagerservice (knowledge base, wakelock manual)
PowerManagerService.Display , further down and still
ProximitySensor
Pseudonymous , still
Google's push
qbt_wake_source
qcom_rx_wakelock , here and below
qpnp_fg_cap_learning
qpnp_fq_memaccess
qpnp_fg_update_sram
qfp-service
qpnp-smbcharger
qpnp-vadc-ebcf0c00
qpnp-vm-bms , still
radio-interface , still here and below
ril-fd
Rilj , still , here , here muddy but probably too option , SIM card replacement
ril-rk29-dataonly
rmnet1
rpcrotuer_smd_xprt
rx_wake
SCREEN_FROZEN and wakelock guide ( reference post ), still opinion
sdio_al, sdio_dmux, etc (wakelock guide)
sec_battery
secril_fd-interface , here still
semc_power
sensor_ind , here and further
[b] Sensors / b]
show keygard , still here and wakelock guide ( reference post )
sia , here
Significant motion detector
sipc-smsg
smdcntl0
sns_async_ev_wakelock
spa_batt, adc
ssp_sensorhub_wake_lock and ssp_wake_lock , still , still , still , autoturn off
ssusb
STEP_IDLE_STATE
surfaceflinger
suspend_backoff (knowledge base, wakelock manual), here and below (on the next page)
svnet, svnet dormancy (knowledge base)
Sync, SyncLoopWakeLock (knowledge base, wakelock manual)
SystemUpdateService , here
TARGETED_INTENT
tasha-slim-pgd
TimedEventQueue
ti_usb_wake_lock
ttyC0 here still
ttyC2
ug31xx
umts_ipc0
usb_bus_active
usbpd0
usb suspend lock
UserPresenceService (com.google.android.gms / .auth.be.proximity.authorization.userpresence.UserPresenceService)
vbms_cv_wake and further still
vbus_wake_lock, vbus_present and knowledge base, wakelock manual ( reference post )
vbus_tuna_otg (wakelock guide)
WCNSS
WiFi running , turn off WiFi scan
WiredAccessoryManager
WLAN AHB ISR, WLAN TX THREAD
wlan_rx, wlan_rx_wake, wlan_wake (knowledge base, wakelock manual), here and here
Xiaomi
xmm_power
zygote

router setup , here and other posts borodovich
General energy saving tips
All the actions described below require certain skills, please do not proceed to it in any case without a full backup in order to avoid the loss of the performance of the phone and its data.

1. Root access.
If you do not have a root, there is nothing to even begin to struggle with the charge consumption. Without root, the phone is not controlled by you, but by Google, Samsung, LG, Sony and others.

2. Google
Google is the main reason for the deterioration of power consumption, so aggressive Google apps should be changed to analogues whenever possible, and it is better to completely disable the google.service framework receivers and Google Play services.HereI describe my actions in this direction. In short - installXposed FrameworkpaidGreenifyand put to sleep the Google Service Framework and Google Play services, and inAutorun managerorMy Android Toolsdisable all receivers of these applications. You can disable it in the same My Android Toolsa number of servicesthe above applications.
Google Now also recommend not to include, just use the usual search. From Google, you must leave the PLay Store - it works great when disabling the above services or receivers.

3. Autorun
A bunch of applications trying to start immediately with the inclusion of the phone, although you do not need it. There are simple programs likeStartup managerin which you can exclude and add applications that run at boot. There are more advanced applications likeAutorun manager, there you can disable various functions related to the launch and operation of applications, or even remove or freeze various applications, including system ones. You can also put to sleep applications with programs such asGreenify. There are programs likeAppOpsthere you can disable autoloading, you can do it inSD Maid.

4. Media
Media scanner can cause very serious damage to the battery.
First, it is worth putting the applicationRescan Media Rootand launch it after loading the phone (for convenience, you can use the above Startup Manager by placing the program in autoload and forgetting about manual launch). The application, however, has not been updated for a long time and its effectiveness is debatable, but it becomes a little calmer at heart.
Secondly, empty .nomedia files placed in the folder with media files do not allow the media scanner to rummage in this place. But it works only if you use players that have a built-in scanner (Poweramp, Dice player). If things likeGoogle music, they will not be able to see the media in the folder in which there is a .nomedia file, and, accordingly, play something.
When using Poweramp, it is also necessary to observe some conventions to reduce power consumption - disable automatic scanning, put music into one folder that you specify in the settings and scan manually (of course, with the above-mentioned .nomedia file). In addition, in the settings of the headset, turn off playback and pause when connecting / disconnecting headphones. By the way, such parameters in some firmware are also available in the system settings.
Yes, some help the procedure "settings" - "applications" - "media storage" - "clear the cache / delete data."

5. Synchronization and updates
There is no need to keep these parameters on all the time, where possible, you need to set longer intervals, or update and synchronize manually. Some applications send data to Google Analytics, it also needs to be disabled. Programs that do not have the settings to disable or adjust the time of updates can completely block access to the Internet. There are a bunch of firewalls, for example, I use the moduleXprivacyfor xposed. Tests have shown that only he can COMPLETELY block the program access to the network.

6. Location
Turn off both GPS and network detection, turn it on if necessary. Disable sending of location data in Google settings (you can see screenshots of settingshere). You can generally remove / freeze networklocation.apk.

7. Wifi, Bluetooth
Include as needed. For WiFi, for example, I useBetter Wifi on / off, including it together with the unlock screen and disconnecting after 30 seconds of inactivity. In addition, if you notice an increased charge consumption when using WiFi, you should check the settings of the router, at least to see if something changes with other settings / another router. Another source of increased consumption when WiFi is turned on can be defective.memory card.

8. Mobile network.
It is often better to use the option “only 2G network” or “only 3G”, so the device will stop the constant search and jump in conditions of an unstable signal. In addition, it is necessary to limit the background activity of applications using the network.

9. Sounds
Disable key sounds, vibration when touching the screen, loading, and so on.

10. Screen brightness
Brightness is better to set to a minimum, but for me, let's say it does not fit, I always use the phone both on the street and in the room, so I have to use auto brightness.
Wallpapers and themes are better to use dark, white text on black, sort of like, less disastrous to charge than black on white.

11. Programs
As I have already described above, you should not use Google’s programs, but there are others that consume a charge - Facebook, various kinds of widgets with HD graphics, watches with seconds, live wallpapers, apps that use push notifications, sensors, and more. For example, in Chrome, in the settings for developers, it is not necessary to tick "tilt through" - the sensor is activated and goodbye, charge.
And what would you not say that Android itself completes unused programs, it is better to exit them through the "exit" button (where available), or "back", or close them yourself by clearing the window of recent applications.

12. Battery
Often, the reason for the Jora is a trite battery failure. You can check it bywayrecommended by tester99 in topic"Power consumption (autonomy) Samsung Galaxy S IV".
In addition to software solutions to problems with savings, it is important to consider the properties of the battery itself. Detailed instructions for extending battery life givescode.masterunder the spoiler below (however,many people believeThat such recommendations were relevant for Ni-Cd batteries and for Li-Ion, full discharge (up to 0) is the main evil and a factor that greatly affects the reduction in battery life. But, for example, on the contrary, this instruction has always helped to increase the battery life on different phones with Li-Д°on batteries, so decide for yourself:
"I use the phone until it is completely discharged, so that it turns itself off when it reaches a critical level. But then I don’t turn on the charging, and even more I discharge the battery. How do I do it?

In two ways - without removing the battery from the phone (not the most efficient way, but more convenient and safer) and the second way - pull the battery out of the phone, put it in the charger "frog" so that the contacts of the frog are connected to the battery's plus-minus, and To the contacts of the frog, connect a small bulb, at 12 volts. Or 6 volts, but 12 is better, because the slower the battery discharge process is, the better, for example, a 3.5 volt light bulb will quickly land the battery.

IMPORTANT POINT! Different manufacturers have different approaches to the management of the battery charge-discharge. Most modern designs battery manufacturers so that it simply ceases to apply a voltage to the contacts as if nothing inside the battery during the critical discharge. With this approach, if you connect a light bulb to a battery, you discharge it just to the point that you have to - to complete a valid discharge. After that, you disconnect the wires and the light bulb and put "Zhabko" with the battery in the socket - all charge went.
Just remember, some frogs are able to determine the polarity automatically, others are not able, so before you start discharging the battery with a light bulb - set the polarity. A green or red light should be lit on the frog when properly connected - see the instructions for the frog. If the frog does not know how to automatically determine the polarity and you mix it up, then when connected to the outlet, either a further discharge of the battery or something bad that will kill the battery will go, be careful.
In general, if the polarity is set correctly and the light went out - just put on the charge and let the battery is fully charged, all night and can Zhabko it takes. Then I recommend removing the battery from the Zhabko not immediately put it in the phone, and give her to lie down, at least for an hour - unless of course there is such a possibility. If not - you can immediately put into the phone. If the battery will lie down - electrochemical processes it ustakanilos, and it will keep longer. And if you took off the charging, put it directly into the phone, then the effect will be such that the battery is a little warm on the charge, and immediately start using it for her worse, she needs a little rest.
The second case is that the battery controller cannot automatically disconnect the battery from the source of load during a critical charge, in this case it is possible to kill the battery with a light bulb, if you allow it to discharge below the threshold level.
How to determine that the battery itself does not turn off? By connecting a light bulb, you will see that it eventually dims and dims lights up, but does not go out dramatically - this is the case when the controller can not automatically turn off, which is typical for many Chinese batteries. What can I recommend in this case? If there is a tester, you can discharge the battery to the level of 2.7 Volts - it will be safe, I will discharge even to the level of 2.4 volts, but you do not take risks.

Or a second method, which I wrote at the beginning (without pulling the battery out of the phone). This method is simple. When there is very little longer battery life, but the phone still works (eg in less than 5%), switch off your phone, then go to rekaveri mode. Or even go to somewhere, even in FlashMode, though in BootLoader or FastBoot mode, the phone has testified that he included - for example, will be ready to sign a flashing or will be launched rekaveri mode. And yet - then leave the phone turned on, it will lie and to work as long as the battery will reach to a critical value, and extinguished itself, or goes off the phone. After this, pull out the battery and charge Zhabko (do not forget about the polarity), or connect the phone to a charger, but do not include it, even charged off - so it will be charged longer, but safer. And in this way make a few charge-discharge cycles - for example, do this 5-7 times. After these procedures, you will feel how much longer the battery will hold a charge that will surpass any battle with veyklokami.

IMPORTANT! When charging the battery, even with a toad, even telephone charging, you do not need to try to disconnect from charging and connect it immediately again, such as for a stronger charge, because lithium batteries do not like the recharge mode, they will really hold the charge after this, but far less.
Besides all this, I took another conclusion that the Android system is somehow measures the discharge levels and battery charge, and if, for example, frequently recharge a phone that is not fully discharged, and for example, only up to 20%, then eventually the phone start confused and inconsistent readings show charge and discharge, and the battery controller itself may encounter a "memory effect". In electrical memory effect is called the effect, when you discharge the battery to approximately 20%, and then connect to the charging, charging to 100%, and then like she should be discharged to 0, but the battery as it thinks it has initially been charged with 0 instead to 20%, therefore, reached the level of 20%, it will be considered that have fully discharged (so the way can be considered, and the Android system), which is why it is so important to do this entire calibration process, about which I wrote above.
This helps me to extend the battery charge, and very well. In fact, the memory effect was valid for nickel-cadmium batteries, or nickel-magnesium batteries, while the lithium-ion batteries do not have this effect, but in reality this is not the case. The memory effect is also present on these batteries, although not as pronounced. "


13. I recommend
-In the intricacies of dealing with the battery consumption will help another programGSAM Battery Monitor.
Attached ImageAttached Image
In a slightly different way, she analyzes the reasons for Jora, but there are a bunch of options that are not available in the BBS.
Attached ImageAttached Image
Somewhere it may repeat the BBS data (the number of awakenings, for example, is equivalent to the signals in the BBS, the core wavelets can also be output separately), but somewhere it will give a more understandable explanation. For example, you can display all wakefulness on a separate screen, rather than scouring the BBS dump and highlighting the reasons.
Attached ImageAttached Image
Each application can be viewed separately and see which processes it has activated.
Attached ImageAttached Image
In general, if there is a desire to understand, then this program in no way interferes with BBS, but only complements and helps. Especially since I officially translate it and I don’t need knowledge of English to use this application.

- Absolutely necessary program -My Android Tools- it is possible to turn off both receivers, freeze services and applications.
- Of the great variety of programs that clean the system of garbage, I recommendSD Maid, silently fulfills its purpose, without awakening and not consuming the charge of the phone in other cases. Naturally, be careful not to remove anything you need (everything is configured), my translation of the program’s helphere.
- Trickster MOD- A program for fine-tuning the kernel will help reduce power consumption by changing parameters even on the drain (even if you slightly lower the upper frequency range, there will already be savings). I translate at the current stage again.
- AppOps- if the firmware does not have operations in the applications, you can use this program (ormodule for xposed) to disable permissions.
- A lot of useful information on energy saving can be learned fromtester99, in particular,here.
- Actually, the basic basics can lookhere.
- Who is interested in the new tool in Android 4.4 - process statistics,hereYou can meet him.
- Descriptionan integrated approach to the problem of energy savingon the example of one phone.
- The cardinal solution to all problems -example.
Download
version 2.5-344 (98) with a convenience store (10/27/19)
version 2.4 (beta) and 2.5 (beta): BetterBatteryStats (Post gaich # 71896585) , version 2.5-325 (beta) from the market : BetterBatteryStats (Post Alex0047 # 85338449)
version 2.3: BetterBatteryStats (Post gaich # 70722088) , 2.4 - last stable
Version: 2.3 Mod BetterBatteryStats (Post Fint01 # 71982049)
full Russification, which continues on the basis of my translationBlue cat : BetterBatteryStats (Post Blue cat # 40200896) (current and previous versions)
A patched version working correctly for Samsung with Lollipop
version 2.3 (beta): BetterBatteryStats
version 2.2.2.0: BetterBatteryStats (Post by gaich # 56898087)
version 2.2.1.0: BetterBatteryStats (Post by gaich # 56632232)
version 2.2.0.0 (release): BetterBatteryStats (Post Alex0047 # 56127929)
version 2.2.0.0RC3: BetterBatteryStats (Post by gaich # 52891703)
version 2.2.0.0RC2: BetterBatteryStats (Post by gaich # 52827318)
version 2.2.0.0RC1: BetterBatteryStats (Post by gaich # 52018561)
version 2.2.0.0B6: BetterBatteryStats (Post by gaich # 47840218)
version 2.2.0.0B5: BetterBatteryStats (Post by gaich # 46040364)
version 2.2.0.0B4: BetterBatteryStats (Post by gaich # 45838216)
version 2.2.0.0B3: BetterBatteryStats (Post by gaich # 45827485)
version 2.2.0.0B2: BetterBatteryStats (Post by gaich # 45794243)
version 2.2.0.0B1: BetterBatteryStats (Post by gaich # 45794243)
version 2.1.0.0: BetterBatteryStats (Post by gaich # 43571019)
Version 2.1.0.0_RC6: BetterBatteryStats (Post by gaich # 43520918)
Version 2.1.0.0_RC5: BetterBatteryStats (Post by gaich # 43520918)
Version 2.1.0.0_RC4: BetterBatteryStats (Post by gaich # 43471179)
Version 2.1.0.0_RC3: BetterBatteryStats (Post Alex0047 # 43443871)
Version 2.1.0.0_RC2: BetterBatteryStats (Post by gaich # 43269089)
Version 2.1.0.0_RC1: BetterBatteryStats (Post by gaich # 43098487)
Version 2.1.0.0_B5: BetterBatteryStats (Post by gaich # 40977407)
Version 2.1.0.0_B4: BetterBatteryStats (Post by gaich # 40383902)
Version 2.1.0.0_B3: BetterBatteryStats (Post by gaich # 39883210)
Version 2.1.0.0_B2: BetterBatteryStats (Post Alex-814 # 39577832)
Version 2.1.0.0_B1: BetterBatteryStats (Post by gaich # 39387083)
version 2.0.0.0 (release): BetterBatteryStats (Post # 37201286)
Version 2.0.0.0_RC6: BetterBatteryStats (Post # 37100603)
Version 2.0.0.0_RC5: BetterBatteryStats (Post # 36880385)
Version 2.0.0.0_RC4: BetterBatteryStats (Post # 36659302)
Version 2.0.0.0_RC2: BetterBatteryStats (Post # 36228395)
Version 2.0.0.0_RC1: BetterBatteryStats (Post # 36145116)
Version 2.0.0.0_B7: BetterBatteryStats (Post # 35983381)
Version 2.0.0.0_B6: BetterBatteryStats (Post # 35955987)
Version 2.0.0.0_B5: BetterBatteryStats (Post # 35899512)
Version 2.0.0.0_B4: BetterBatteryStats (Post # 35824736)
Version 2.0.0.0_B3: BetterBatteryStats (Post # 35632122)
Version 2.0.0.0_B2: BetterBatteryStats (Post # 35461306)
version 2.0.0.0_B1: BetterBatteryStats (Post # 35041107)
Version 1.16.1.0_B2: BetterBatteryStats (Post # 33322552)
Version 1.16.1.0_B1: BetterBatteryStats (Post # 33297470)
version 1.16.0.0: BetterBatteryStats (Post # 32638399)
version 1.16.0.0_RC6: BetterBatteryStats (Post # 32615524)
version 1.16.0.0_RC5: BetterBatteryStats (Post # 32576520)
version 1.16.0.0_RC4: BetterBatteryStats (Post # 32511377)
version 1.16.0.0_RC3: BetterBatteryStats (Post # 32494818)
version 1.16.0.0_RC2: BetterBatteryStats (Post # 32473538)
version 1.16.0.0_RC1: BetterBatteryStats (Post # 32311931)
version 1.16.0.0_B7: BetterBatteryStats (Post # 32166672)
version 1.16.0.0_B6: BetterBatteryStats (Post # 32166672)
version 1.16.0.0_B5: BetterBatteryStats (Post # 32057413)
version 1.16.0.0_B4: BetterBatteryStats (Post # 32034515)
version 1.16.0.0_B3: BetterBatteryStats (Post # 30250385)
version 1.16.0.0_B2: BetterBatteryStats (Post # 29981603)
version 1.16.0.0_B1: BetterBatteryStats (Post # 29937063)
version 1.15.0.0: BetterBatteryStats (Post # 26951605)

We kindly request!
Please read the header before posting. Put the dump in inactivity, otherwise the post will be deleted so that the topic is not filled with unnecessary information that cannot be analyzed in any way. Details under the spoiler "Preparing dump".


Post has been editedgaich - 23.01.20, 13:49
Reason for editing: 344



Rep: (1189)
slas @ 28.03.2013, 16:02*
Odd is not working these links - all open the same page with a table of contents.

I happens in chrome jambs with html - you open a page, then another page, it opens in the background. That is, do you see the first again, and look up - right tab has appeared ...



Rep: (14)
Superstar @ 28/03/2013, 17:17*
What is known about the work of this program on Chinese plates?
The topic did not find it.
You can advise the other?

Recommend gsam battery monitor, produces less of information, but not eating battery.
And the subject, and GSAM, both showed that the latter draws 4 times less than%
How long have not tested, I may be wrong.



Rep: (1189)
POLYAKdim @ 29.03.2013, 06:43*
Recommend gsam battery monitor, produces less of information, but not eating battery.
And the subject, and GSAM, both showed, h

Confirm, gsam monitor this thing!
(My translation, again ...: happy:)



Rep: (7327)
Attached ImageBetterBatteryStats v1.13.0 Beta4

What's new:
-Added some logging to debug percentage problem: adb logcat | grep StatsAdapter
-refactored KB handling
-refactored "raw" stats
-Stats row shows interactive areas (glow)

Download: Attached fileBetterBatteryStats v1.13.0 Beta4.apk (2.11 MB)



Rep: (72)
Listen, there is somewhere a detailed analysis of the program interface in Russian? For example I can not understand that for the red and blue stripes on each other in the information about Eaters



Rep: (1189)
Reference materials on the BBS and wavelets

The first three items ( "Help", "How to ...", "The opinion of the author of the program to revoke permissions ...") - represent data transfers directly tobranches author of the program at xdaBy clicking on the header, you can see the original, spoilers, respectively, translating (well, maybe with a few of my editorial changes). "Knowledge Base" is also created by the author of the program, but supplement it all those who can contribute. "On veyklokam Guide" - sinceother forum, The original source can also be found by clicking on the headline. My only concern there changes to add information about the unaffected matters with other forums.
Letters a lot, but you need to read this! Without this knowledge, your fighting veyklokami not be complete and effective!

Help
Help
BetterBatteryStats

Here you will find details about the organization screens and BetterBatteryStatistics options. Other information about the use of BetterBatteryStats see How.

Tags
BetterBatteryStats does not collect data in the background, but uses tags stored at specific times (in certain events):

Loading (Boot): Saved when the phone is loaded, delete all the other labels
Disabled (Unplugged): Saved, when you unplug the phone from the charging
Charged (Charged): Saved when the phone is charged up to 100%
Screen Off (Screen off): Saved when your phone screen is turned off (when the standby mode is activated)
On the screen (Screen on): Retained when your phone screen is switched on (when activated standby mode)
The user (Custom): Saved when you select the menu option to save custom label
Current (Current): Current data
Please remember that time period data is deleted upon reboot. To use "From = Disabled" after reboot, you must connect / disconnect your phone.

If these events do not occur, or after a reboot, the BBS will report the missing link. This is not a bug, as provided by the BBS

Screens
There are the following types of statistics:

Other statistics (Other Usage, or Summary): Shows the sleep wake up, turn on the screen and other important time
Veykloki core (Kernel Wakelock): Shows the total time and number of core veyklokov
Partial veykloki (Partial Wakelocks): Displays the total time and number of partial veyklokov
Signals (Alarms): Shows the awakening caused by applications or services
Network (Network): Shows the network statistics
CPU statistics (CPU States): Displays CPU statistics and deep sleep
The processes (Process): Displays the CPU time (user and system), the process of consumption
Sensors (Sensors): Statistics using sensors
Package information (operation in applications): Shows the resolution and specific service package (application): This screen can be opened by clicking the icon in any of the screens
And these are possible time points for displaying statistics (the choice "from" and "to" any of these points)

Other statistics
A group of different indicators of battery consumption. This statistic should always be checked first, as it gives a good idea of ​​the expense.

A normal profile will show a low ratio of "Screen on" to "Wakefulness", meaning that partial wake blocks are responsible for the battery consumption, not allowing the phone to go into a deep sleep.

Deep sleep (Deep Sleep): Total sleep time phone
Wakefulness to Off. screen (Awake (Screen Off)): Total time when the phone is not in a deep sleep when the phone screen is off
On the screen (Screen On): Total time awake phone with the included display
Phone on (Phone On): Total time when the phone is in call mode
On Wifi (Wifi on): The total time included Wifi
Wifi used (Wifi Running): Total time when the Wifi was connected to SSID
Inc. Bluetooth (Bluetooth On): Total time, when it was included Bluetooth

Partial wavelets
The list shows the total time of partial veyklokov caused by the application or service during the time interval, the number veyklokov and their percentage. Value is calculated as a percentage of the total operating time, wakefulness or arousal - time included in the screen depending on the settings. Typically, the value calculated from the waking hours, which is more significant, since it shows the potential of reducing the time of waking time. The graphs show the percentage depending on the settings (see. Above).

Even if the total time is insignificant, it is important to check the number of veyklokov. A large number of short periods of awakenings can have a big impact on the waking hours, as the phone uses the time to wake up and sometimes again at the transition into sleep. It does not show these statistics. For example, assume that the phone is awakening and re-enter the sleep took 2.1 seconds. For 10 seconds veykloka result waking time is 11 seconds. For 10 veyklokov 0.1 second total time veyklokov be less than 1 second, but the waking time is 11 seconds.

Core wavelock
As in partial wavelets, both long and frequent wavelets (with a large number of times) are taken into account.

Signals
Signals are events created by applications that can cause awakenings.

Network
Transmitted bytes are shown by application and network interface.

CPU statistics
Shows the time spent on each processor state (frequency), including the time of deep sleep.

Processes
The list shows the processes and their CPU consumption during the time period. CPU consumption is expressed in the use of the processor by the user and the use of the CPU by the system, both times are shown in a general graph and in a diagram in different colors.

Sensors
Usage statistics applications of sensors.

Standby mode
Standby mode - a feature that helps you to analyze what happens when the screen is off. When the standby mode is turned on, the screen turns off to create a tag 'off screen'. In the configuration mode, you can also create a label 'On screen' when the screen is activated (unlocked). Optionally, the standby mode will notify you when the screen is turned on and the ratio of awakenings more than the threshold of awakening. To avoid unnecessary treatment, the duration of the threshold can be set to turn off standby mode in a short period of the screen is turned off.

Menu
Settings
Refresh
Still
Dump file records the statistics /sdcard/BetterBatteryStats.txt
Set custom label: set custom starting point for statistics
History: shows various graphs, such as battery use or wake-ups (starting with Android 2.3)
Unprocessed signals: shows signals from loading
Unprocessed Core Wavelets: Shows Wavelets from Download
Raw network statistics: network statistics from download
Raw CPU statistics: CPU statistics from the download
Help: Access to the help section and the section How

How...
How to work in BetterBatteryStats

The document gives a general idea of ​​how to use BetterBatteryStats to reduce battery consumption in a systemic way.
First you have to select a label (usually, the relation "Disabled (Unplug)" to "Current (Current)" is the best option to start with.

Check the time for deep sleep, wakefulness and the on screen
The ratio of deep sleep to total time shows how much time the phone has spent in the most economical mode: ideally, deep sleep should almost be equal to the total time.

The ratio of the included screen to wake time shows how long the phone has been used by the waking time. Ideally, the on screen time should be equal to the wake time, meaning that the phone was in wake mode only during use.

Note: The 1x1 widget shows both ratios and gives a better overview of the optimality of the phone.

Check kernel wavelets
The list shows which wavelets worked: the symbol on the right means that an article about this particular wavelock is in the knowledge base. First of all, we check the time (minutes or more), if there are no hot spots, we look at the number of times.

Wavelock PowerManagerService
This wavelock is shown in a number of partial wavelets on many phones. If this wavelock is # 1, go to Partial Wavelets for more information.

Waveclip multipdp / svnet-dormancy
This wavelock indicates intensive network usage. If this is wavekk # 1, go to Network Statistics for more information.

If PowerManagerService is not the most active wavelock, check the online knowledge base or use the search for more information about wavelock and its potential causes.

Check partial wavelets
The list shows which partial wavelets worked, and for most of them, which applications caused them. See “What's Next” for additional details and information on how to reduce them.

Wailek AlarmManager
A large time or number of wakelock AlarmManager shows that many of the awakenings were caused by signals or by the fact that applications intensively added / changed signals. A detailed review can be found in [Signals].

Network statistics
Here you will find which applications / packages were used for the most data transfer.

What's next?
Some, but not all wavelets can be called by a specific application. In this case, the following options are available:

Check / change settings
Sometimes we really need applications / functionality that cause wavelets, and there is good news - there is hope. The settings of many applications can determine their behavior, so you can check:

frequency: giving Twitter a message to check new messages every 2 minutes is not particularly compatible with a good battery life. Knowing the price of such functionality, it is better to set the use on demand, rather than letting the application work in the background
quantity: check additional services, such as cloud backup, full synchronization, etc., and ask yourself if you need all of this
Remove or freeze
If the cause of partial wavelets has been identified, ask yourself if you are using this application. If not, disable / delete / freeze it. Go back to the beginning and do a new check to confirm the effect of the actions performed.

In some cases, it is not possible to relate wavelets to a specific application. Use the knowledge base and search for more information on potential causes.

General remarks
The following notes will help you eliminate some of the reasons for waking up:
Turn off GPS when it is not needed so that applications do not abuse location sources.
when you have finished working with the application, close it with the "back" button. This will complete it and prevent it from working in the background.
Do not use auto-killers. If there are applications that you do not want to run or cache, freeze them or, accordingly, configure their autorun
also do not use energy-saving utilities such as Juice Defender or Green Power: most applications behave inadequately when data transfer is not possible and will increase the expense due to the additional volume of attempts
if you are not using Wifi, turn it off: in some cases, Wifi can cause wake-ups and additional load, for example, to location services
Enjoy your successes
The basic rule of work optimization is to check the results of each action and this applies to the following:

do not make too many changes at once: if the cause is eliminated, the picture may change completely. Therefore, working on two or more processes at a time can be a waste of time.
replacing the kernel, firmware or modem during the optimization process may distort your statistics, do not conduct tests at this time, so as not to get incorrect results
consider external factors, in case of unexpected BBS statistics, run tests again to confirm the results: our phones are not closed systems and conditions, such as network coverage, can affect the results. If in doubt, confirm the results by repeated testing in different conditions to correctly diagnose the problem.
Do not overdo it: you want to use the phone, so do not hunt for wake up until the last second. Enjoy the results and periodically check the statistics again if you feel that the battery consumption is increasing

The opinion of the author of the program revocation of permits and prevents retention applications veyklokov
Some thoughts on veyklokah and revivals
________________________________________
Recently, much has been written to revoke the permissions granted to applications on hold and veyklokov about getting rid of them, so it seems, the time has come to understand.

Firstly, you must understand that if you think that these details too much, you do not understand what was going on, or not interested in, to rise to this level of detail, you do not need to use any means to change access rights or any influence on veykloki or signals: no clue what you are doing or understanding of the consequences will hurt your phone could potentially make it unstable and is likely to increase the battery consumption, instead of any savings.

Let's start with the basics and then move on to a description of how these mechanisms interact, and finally, what can happen when you change any of these behaviors.

Basic terms

Signals
Signals are application mechanisms for asynchronous calling at a certain point in time. There are various types of signals that either work when the phone is already awake, or are the cause of the awakening. In addition, there are varying degrees of accuracy, depending on whether you need high accuracy or you allow the Android system to make a time decision, so that it can potentially collect several signal triggers in one wake-up.

Awakenings
Awakening is caused by a signal of type RTC_WAKEUP. A sign of a poorly designed application will be the use of the wrong type of signal (wake-up) to perform operations that are performed only when the screen is on (for example, updating the widget).

Wavelock
There are two types of wavelets: kernel wavelets and partial wavelets. Partial wavelets are specific to Android, while kernel wavelets are not specific to this system and are part of any linux kernel. Partial wavelets are internally involved in holding the core wakelock.
In Android, partial wavelets are needed when there is a code segment (block, chain) that should not be interrupted when the phone goes into sleep. An example of a sequence that should not be interrupted are both blocks that are used in such a way as to guarantee continuity during the passage, as well as blocks that use redundant resources, such as data, that you want to complete.

How they interact

Examples of partial wavelets
Let's start with the BBS example (yes, the BBS holds wavelets). With certain events (download, disconnecting the charger, screen off / on), the BBS retains the so-called labels: the label is a complete description of the corresponding full state of your phone at a point in time. Labels can then be compared to get a complete picture of what happened between the two labels.
In order for the label to maintain integrity, it is important that the preservation process is not interrupted. When using the phone, it doesn’t matter (since the screen is on and the wave is still held when using it), but think about what happens when the screen is off and you unplug the charger: the phone can go to sleep until the critical sequence is complete, breaking integrity: when you need a wavelock.

Another example would be the situation when you download something (for example, from google play) and your screen turns off. If the download started when you used the phone, you want to finish it before the phone goes to sleep. The absence of a wakelock during the download may cause the download to be interrupted, the file may remain underloaded and it turns out that you have wasted the battery and you need to start over.

Examples of awakenings
When an application needs to do something at a particular time (e.g., a request) it will use to run RTC_WAKEUP sequence which may, for example, to open a connection and to receive the data. Since waking up can be started when the phone is asleep and the screen remains off, the phone does not need a lot of time to go back to sleep, perhaps to the connection and the request will be completed. To avoid this, you must hold veykloka as long as the connection and subsequent actions will not be executed.

What can happen
Recalling permissions to hold wavelets or hindering an application from performing this operation is the worst thing you can do: as a result, you will get even more expense due to the connections being made and starting data transfer before the phone returns to sleep and cancels the result.
Worse: imagine the following sequence, which will occur upon awakening:
1. Phone wakes up (RTC_WAKEUP)
2. Hold Wakelock
3. Connection
4. Data Transfer
5. The next program signal
6. Liberation of Wakelock

Think about what happens if you prevent the application from holding the wakelock and the sequence is interrupted during the transfer process?

Are we at a dead end?
Not. Identifying wavelets (especially long and often occurring), as well as frequent awakenings, is an indication that something is going wrong. Knowing this means different things we can do:
• Decide to remove the application, because the cost of using it is too high compared with the benefits
• Try to change the symptoms by adjusting the application settings.
• Use tools to prevent certain wake-ups if there is no need to receive updates when the phone is turned off (Facebook is one example)
• Contact the developer and help him solve the problem with unwanted effects.
And what you should never do is try to suppress the symptoms instead of removing the cause (this is what you do when you prevent the application from holding the wavelets, and this is a very, very bad idea).

Knowledge base
Alarmmanager
AlarmManager provides access to services to wake the system. These services allow you to schedule the launch of applications. When the wake-up signal is triggered, the related goal processed by the system, automatically launching the application you want, if it is not already running. Recorded signals are retained until the device is asleep (optional and may awaken the device will work if at this time), but will be cleared at shutdown and reboots the phone. Alarm Manager keeps the CPU until veyklok performed method onReceive () signal receiver. This ensures that the phone will not sleep until you've completed the transfer process. After returning onReceive (), Alarm Manager lets the veyklok. This means that the phone in some cases, go to sleep right away, as soon as the execution of the method onReceive ().
Notable steps:AlarmManager launches not partial veykloki and applications (the target) that have been set to start when the alarm goes off. The alarm list can be seen in the "Alarms" menu.
Instructions for signal analysis:
to define these targets, run dumpsys alarm.
(How to do this can be found, for example,hereor a little more,here.)
This will save dump all signal events, and you can see what is AlarmManager as veykloka. Here you can see the items with a large number of awakenings. In some cases, you can not do anything about it (Android System), but in others, you can uninstall the application or turn off notifications. We hope it will help in solving the problems with AlarmManager.
Look at the "Alarm Stats" at the bottom, it will look something 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 this case, services, causes AlarmManager, seems to have been BeautifulWidgets (updated every time you change the clock minutes - 1583 signals: act = com.levelup.beautifulwidgets.ACTION_UPDATECLOC K flg = 0x4).
Battery Monitor Widget (obviously receiving information about the battery voltage) - 130743ms work, 1585 awakenings.
You can also reduce the amount of AlarmManager events, simply by disabling location, leaving the account, Google Talk, and disabling notifications or updates to applications that you do not particularly use.
AlarmManager - is a universal process that applications use a lot for time updates, notifications, etc. In most cases, it is a necessity, in other cases, you need to really make a check and disable / remove applications that are all too often this process is called.
References:
http://forum.xda-developers.com/showpost.p...p;postcount=861
http://developer.android.com/reference/and...armManager.html

AudioOut_1
AudioOut used to play notifications and system sounds.
Notable steps:from the settings menu ... ->sounds ->remove the check mark from the "clicking sound", "Lock Sound".
Certain conditions will occur:Each time you press or screen lock.

ConnectivityService
The service responsible for data transmission / access points, establishing and maintaining connections. Veyklok retained when switching between data transmission methods.
Notable steps:can be eliminated by using another radio / modem, in a better network coverage or using only 2G.
References:http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.0.3_r1/com/android/server/ConnectivityService.java#ConnectivityService

deleted_wake_locks
The software interface available drivers Android, prescribed to carry out commando wake_lock_destroy before freeing memory veyklokov structure they have created. For the most part this is happening on a trip but also, in some situations, when the driver is unloaded from the kernel dynamically. Whenever it happened, remote veykloki disappear from the list, but their statistics is added to the pseudo-veyklok deleted_wake_locks. This allows you to see that a number of old veyklokov has a combined set of statistics that demonstrates this item. Statistics of this paragraph does not increase as the additional operating, veykloki with nonzero statistics are removed.
Notable steps:since it is a simple point, including all team activity veyklokov kernel, which no longer exist, to do anything directly, in order to reduce the veyklok not necessary. The best course of action would be to identify veyklokov generating activity, before they will be deleted, and will appear in this paragraph.
Certain conditions will occur:Wifi Driver - one of the known sources veyklokov core are destroyed when the driver is unloaded (when the Wifi disconnected manually or under programmed off). Veykloki such as wlan_rx_wake and wlan_wake, when the driver is unloaded, is no longer displayed in the list and their stats are added to the existing values ​​deleted_wake_lock.
References: http://forum.xda-developers.com/showpost.p...;postcount=5644 http://forum.xda-developers.com/showpost.p...;postcount=6671 http://www.netmite.com/android/mydroid/cup...ower_Management

GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint
Veyklok irreproducible detected under certain conditions, showing a large number veyklokov and, in some cases, a great time. Because the causes are uncertain, there is no guarantee that will not happen veyklok other yet unknown reasons.
Notable steps:in one case (see ref.) This veyklok was successfully removed by changing the proxy / create a new access point with a blank proxy. "Guilty" is pre-installed proxy provider Orange, but it is possible that the proxies of other providers may have the same effect.
Related veykloki:other GTALK_ASYNC_CONN partial wakelocks
References:http://forum.xda-developers.com/showpost.p...;postcount=3416

mipi_link
Some people think that veyklok somehow connected with cameras, but confirmation of this. AllianceMIPIis a firm engaged in the mobile device interface development. Perhaps veyklok it held some produced by this alliance chip (on the site, for example, referred to someapplication processor), Which communicates with some other device (a wireless modem, for example) by means of some connection (link).
Notable steps:the only way to get rid of him - a flight mode.
Certain conditions will occur:veykoloka counter is incremented regardless, included wifi, or disabled, enabled mobile network data transmission, or disabled, enabled synchronization or not, 3g or just 2g, there is a SIM card in the phone or not. Gtalk, Gmail, Facebook, Skype, Gallery is not affected, all these applications can be frozen or deinstalirovanny, no matter veyklok remains.
References: http://forum.xda-developers.com/showpost.p...postcount=15099

network-location
network location service Service is responsible for providing information about the relative location to the requesting its application.
Update frequency (and veyklokov) depends on the accuracy of the data requested by the application (the maximum time between updates, the accuracy in meters).
Examples of applications requesting the relative location: Weather widgets cards, most of the social tools, google +.
To minimize veyklokov:
• Find the guilty app: view all veykloki network-location and mark and all applications in the second line of the list
• Check the application settings for the possibility of the accuracy change
• Use advantages Wifi base position (stable position which minimizes the frequency of updates)
• Look for alternative applications with more acceptable settings
Certain conditions will occur:incorrect applications with high accuracy requirements to run the service Network Location.
Unstable network conditions (frequent obmendannymi between the towers) can trigger a location update.
In some cases, updating radio / modem affects the network location: the location of the tower is based on information supplied by RIL.
Related veykloki: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/and...ionManager.html

Powermanagerservice
Veyklok active core is the label for all partial veyklokov custom field.
Notable steps:Use the "Partial Wakelocks" for computing applications / services causing veykloki.
Known causes of:Some devices show veykloki custom field generally at Tagged PowerManagerService.

suspend_backoff
suspend_backoff triggered by rapid transitions sleep-wake-sleep in short periods of time (10 times for x ms IIRC). When this happens, the veyklok makes sure that the device is constantly waking up for a while, instead of for a long time to change the state. Counter veyklokov core can provide information about the source of constant revivals, but a precise answer can not be found due to the lack of time show their distribution.
References:In connection with Chrome:http://forum.xda-developers.com/showpost.p...mp;postcount=24
In connection with the on / off Wifi on / screen is off
http://forum.xda-developers.com/showpost.p...;postcount=6603

svnet
Basic control radio module (specific for Galaxy S / S II).
Notable steps:no known direct action can be eliminated by replacing radio / modem.

svnet dormancy
svnet-dormancy is veyklokom core associated with cellular data - it is fast or not, always work 6 tisekundny veyklok every time the radio is transmitting data.
Notable steps:change the duration veykloka (use at your own risk). Decrease veyklok by reducing the volume / quantity data transfer requests.
Cause- data transfer.

Sync
sync service is responsible for synchronizing all the accounts in the "Settings" - "Accounts & Sync". Veyklok held until synchronization processes work.
The more points the more synchronized and synchronization, the more veyklok.
Potentially, veykloka time tends to increase as a bad connection.
Examples of accounts: twitter, google +, linkedin, google mail
To minimize veyklokov:
• Remove unnecessary accounts
• Check the settings and remove unnecessary options (eg., Contact synchronization)
• Check the timing mode and make sure that you really need in these settings
Certain conditions will occur:under bad communication conditions, the presence of synchronization providers misconfigured
References:known bug with gmail:http://code.google.com/p/android/issues/detail?id=9307

SyncLoopWakeLock
SyncLoopWakeLock - it veyklok used Android SyncManager (android.content.SyncManager) and it works, starting with Android 4.01. Synchronization Service is responsible for all the accounts in the "Settings" - "Accounts & Sync". Veyklok kept until the synchronization process is running.
The more points the more synchronized and synchronization, the more veyklok.
Potentially, veykloka time tends to increase as a bad connection.
Examples of accounts: twitter, google +, linkedin, google mail
To minimize veyklokov:
• Remove unnecessary accounts
• Check the settings and remove unnecessary options (eg., Contact synchronization)
• Check the timing mode and make sure that you really need in these settings
Certain conditions will occur:veyklok SyncManager retained when processing a synchronization action (handle () method). Earlier this veyklok was known as sync.
In case of poor communication conditions with the presence of correctly configured synchronization providers active veyklok retained longer.
Related veykloki:sync
References: https://github.com/asksven/BetterBatterySta...-Base/wiki/sync
Sources:new veyklok:http://grepcode.com/file/repository.grepco...ava#SyncManager
Old veyklok (* sync *):http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/2.3.7_r1/android/content/SyncManager.java#SyncManager.0SYNC_WAKE_LOCK

vbus_present
vbus_present is veyklokom nucleus, held at a connected memory.
Notable steps:there is no need to do something.
Certain conditions will occur:when connected to a charger / USB port to charge.

wlan_rx
Wifi chip receives from a package - on the Galaxy S II, a lot of data veyklokov combined with the fact that the device needs 650 ms to resume operation after the idle state and 150 to switch back to sleep, mean that the resulting packages wifi sharply increase Android OS consumption. As an extreme example, drive in Linux the following command at the wifi off policy "never" and see the ratio of your deep sleep, battery consumption and operating consumption: ping -i 5<wifi IP address of phone>
Notable steps:Use a packet sniffer to determine the causes of traffic.
Related veykloki:wlan_wake

wlan_wake
Wifi awakened processor chip (typically a start or leads to veykloku wlan_rx).
Notable steps:Use a packet sniffer to determine the causes of traffic.
Related veykloki:wlan_rx



Guide veyklokam
Full (but not in any way final) guidance on veyklokam


Veykloki evil. If you are trying to increase the life of your battery, it is known to you. Some veykloki - a happy, good creatures, but many - this silent leeches, sucking the life of your batteries, as long as you are blissfully unaware of what was going on. The purpose of this manual is to explain the most common veyklokov with whom you meet, and measures for their expulsion from the system. If you come across any not listed in this guide, please let me know the author, and it will add them to the list. By the way, the use of by the author phone can be characterized by short to moderate. Before deveyklokizatsii time per charge is 24 hours. After - to 36. Then the author has acquired an enhanced battery for the Galaxy Nexus and the third cycle, the operating time on a single charge has reached two and a half days. Impressive, right?

First, it is necessary to understand the difference between the kernel veyklokami (Kernel Wakelocks-KWL) and partial veyklokami (Partial Wakelocks-PWL). KWL - veykloki, the cause of which lies in the kernel or in hardware. Some of them are useful and some vampires. The only way to deal with them - this is to change the behavior of the phone. Examples will be given below.

PWL - veykloki caused by the application. The fight against them, more than ever, will be to freeze (or, in the case of Google apps, uninstall) aggressive applications. Before you do this, and this is critical, go to Settings ->Application force quit an application, clear its cache and data. If you do not, you will surely add yourself the headache was somewhere 30 seconds after removal of the application.

Second, you need to know what tools are involved in the hunt for veykloki. The first - a Better Battery Stats. Look in Google "better battery stats XDA" and find a developer forum; the application is distributed free of charge to participants XDA. However, if the BBS helps you, provide some appreciation developer and buy the paid version. It is only $ 2.89, and the developer will earn more than this to the time you finish the expulsion of its veyklokov. Other tools that you need, this guide are (presumably) and, of course, the Internet search engine of your choice. The author simply can not cover everything, just as he had not seen.

The last two notes to the management: do not start hunting for veyklokami immediately after installing the new firmware or a clean reinstall of the current. New firmware make some phone time to act unpredictably until things ustakanilos and some background processes will not be brought to fruition. Wait one full cycle of the battery (100% to 0%, you may still pass for calibration after a clean install of the firmware) before you start, or you will reduce yourself crazy. Also, remember that a victory over one veyklokom often leads to another, especially in the early stages of the process. This is normal and expected. God does not hate you, you chose not flashing any crap, your phone is not dead, but a clean install at a time when your firmware is more configurable, to make it worse.

So how do you keep track of these veykloki via BBS? This is a rather complicated procedure, so carefully follow the instructions of the author. To get started, open a BBS. Then, look at the drop-down menu at the top, which may now written "Other (Other)"? Click on it and you'll see below "Kernel Wakelocks (Veykloki core)" and "Partial Wakelocks (Partial veykloki)." Obscenely difficult, right?

Something about the BBS you need to know: it seems the program has a strange bug "count." When checking the firmware using the BBS, the author finally wondered why during his PWL significantly exceeds the actual time veykloka. "The actual time veykloka," to put it simply, this time bodrstvovaniya- waking time with the included screen. If your phone is awake for 45 minutes, and the screen was turned on only 40, you have 5 minutes of real time veykloka.

So why BBS claims that PWL time was 90 minutes, when the actual time veykloka equals 45 minutes? The author has two theories on this subject. First, BBS counts veykloki independently, even if they occurred in the same time. For example, if AlarmManager awakens your phone for two minutes and 30 seconds AudioOut_1 in one time period, BBS register PWL length of 2 minutes 30 seconds, even if the device was in the wake mode, only 2 minutes. Throw in 30 wlan_rx_wake (KWL), and BBS registers 3 minutes veyklokov, although there were only two. Taking into account that you have at this time the screen was turned on 30 seconds, you suddenly see a 3 min veyklokov when in deledeystvitelnoe veykloka time was only 90 seconds. BBS effectively doubled the time veykloka, denying your statistics. Thus, given the many dozens of mini-veyklokov occurring simultaneously with the display on, you can easily see, for example, 6 hours PWL for 24 h cycle, even if the actual time veykloka was only 45 minutes. It seems that Android Battery information screen of the reports in the same way, therefore, the author suggests using real time veykloka when stripping and assaulting KWL and unruly applications. Some PWL (AlarmManager) will always be significant.

The second theory - is that a minimum time signal displayed in the report of a specific number; eg., five seconds for each signal exhibiting its effect. Now, let's say you have a Facebook, Twitter, Google+, LinkedIn, Gmail, Email, News & Weather, and BBC News, all set to sync every 30 minutes. Each of them triggers a signal in the same time, and suddenly your reporting five seconds turn into 40 seconds every half hour. Let's say you had 35 triggered signal every half an hour (do not limit opportunities with Google Services Framework). 35 x 5 = 175 seconds waking hours (at the rate of five seconds, a signal), which will be 350 seconds per hour reporting veyklokov, even if the actual time veykloka equal to only 10 seconds. So that's something to keep in mind when dealing with PWL.

One more remark concerning the BBS and processing them KWL:There is no such thing as a 0-KWL cycle, no matter what the screen says the report BBS. If the BBS shows 0 KWL, press the menu button, then "More (More)", then "Raw Kernel Wakelocks (Rough statistics nucleus veyklokov)" to see it. KWL needed to load the phone. In fact, the only phone with 0 KWL phone will be from the last charge, which after this charge is not included.

There are a couple of other features BBS, we actively use later, but for now you need to know only one. Click on the BBS menu. Click "More (More)". You see the box that says "Set Custom Ref. (Set polz.metku)"? You need it - very necessary.
In addition, as soon as there is new information about any veykloke veyklokov or family, it is added here. If it helped you, please visit the post with this information and thank publish it. Links to each post are given twice, first in the description veykloka, then the bottom cap, so sorry about the inability to find the post will not be accepted!

Last in a row, but, definitely, not the least of value: a modification of your system in any way, including the removal or modification of processes necessary for veyklokov can lead to unpredictable results. Be careful and make backups of your data and applications, as well as nandroid-backups as often as possible in a period of searching for and get rid of veyklokov. All modifications that you do, you do at your own risk, and the author does not assume any responsibility for any damage that you may cause to your phone in the fight against veyklokami.

You can now KWLs, because they are the most malopoddayuschiesya destruction. Use the guide below to identify veykloka, its causes and ways to get rid of it.

VEYKLOKI NUCLEUS

wlan_rx, wlan_rx_wake, wlan_wake: veyklok is caused by network traffic. The simplest solution is Wifi off, but be careful with this! When an application starts the synchronization and sees that Wifi off, it will search the link for mobile data transmission (which is the reason veykloka ConnectivityService). If it can not locate a mobile network, it will have to wait and look again at the next synchronization interval and / or avtomaicheski synchronize with calls. This veyklok may also, conversely, be called Wifi network itself, when it updates the compound or IP-address.
To eliminate: that little crafty sucker is not easy to stop, because its operation has so many reasons. Flight mode is safe, synchronized applications seem to "respect" flight mode, but if only the Wifi is off, they just try to find a workaround. But in this case, of course, you lose the ability to talk on the phone. If you're particularly unlucky, your Wifi network itself can be a problem. For example, the author and his wife were in the home network of four computers, Ipad, Android three, two game consoles, and TV with Wifi. "Background noise" caused it all, constantly aroused phone. Decision? Wifi additional router has been set, is set to other than the main channel, and this network used the two-three smartphone. This is not an easy elimination of the problem, but wlan_rx_wake almost completely disappeared (now about 4 min 45 sec 12 min 27 h after charging).

PowerManagerService: it may, your # 1 or # 2 veyklok kernel, and you probably want to get rid of him at any cost, right? I would not like to say it, but there's nothing you can do. PowerManagerService - this KWL, which serves as a "repository" of all your PWL. This label, no more, no less. Do not spend a lot of time to care about him.
To Remedy: reduce the PWL. Read below.

deleted_wake_locks: remember that the author wrote above about the forced stop the application and removal of the cache and data before uninstalling? This veyklok gives an answer why. It PowerManagerService for remote applications. Once the app is gone, veykloki that it's called, suddenly become unknown to the system, so they're going here. Their number can be increased, but not dramatically, because the system is "looking" remote applications, and / or finding new veykloki associated with it.
For Solution: Make sure that you are forced to shut down the application, cleared their cache and data before deleting it. Restart must completely remove veyklok. If it still appears, clear the cache and cache Delvik phone.

sdio_al, sdio_dmux, etc .: veyklok is unfortunate, because there are two potential causes for it. One simple, and the other not. Simple - this is what you have become a victim of veykloka memory. The easiest way to prove it will download Jrockttu's Skyrocket Charger Test App . If your charger is shown as AC Regular Charge, your problem here. If AC Fast Charge or USB Normal Charge, the veyklok may be caused by an SD card. This can be annoying, but veykloka version of the SD card is usually quite insignificant and not worth the attention. Also, thank you so much for opening kishke third reason veyklokov family SDIO: data. It seems that veykloki sdio family and are part of the family wlan in the data equivalent of the cellular network And can be caused by applications, the leading search data.
To Remedy: Check charger and adjust if necessary. For testing over a cellular data network capabilities, note the time veykloka SDIO, then disconnect the transmission of data over the mobile network and Wifi and leave for an hour. After this check, and if sdio minimal or absent, then it was this. Try other radios for a better connection or disable the transmission of data over the mobile network and only use Wifi. If this is the SD card, then perhaps this is not so strong veyklok to fix it, but if you remove it zotite, format the SD card. If reformatting does not work, format again, then make a wipe cache and cache Delvik.

alarm_rtc: this controller internal signals your phone sets up calls for synchronization, and a push-notification al. Closely related to AlarmManager PWL.
To Remedy: check your application and make sure that they are configured to sync only when you want it, rather than continuously or at short intervals.

mmc0_detect, mmc1_detect, mmc2_detect: to be honest, no idea what is causing this. Fortunately, these veykloki miinimalny, there is no point in wasting time on them. User polarbearno , However, it has a lot of experience regarding this veykloka and call the cause of his excessive activity bad SD card.
To Remedy: Remove and put back the SD card, reboot. Perhaps, for the best results it is worth clearing your cache and Delvik. If the problem is due to poor external SD card, this procedure should help. If the cause of the problem was not a bad external SD, back to the original solution, sound like "good question ..."

vbus_present: This veyklok there until your phone is connected to the charger. It also appears when you use the charging of Apple, which is registered as a "slow USB (slow charging by USB)" and leads to veykloku, which is held after the disconnection from the charger.
To Remedy: Check the phone. whether it is connected to a cord? If so, whether it leads to a power source? If so, disconnect the phone (after full charge, of course). Veyklok still present? Connect your phone to the charger for a few minutes, then remove to kill veyklok, then think about where to bury the fruit, you are charging the phone. It is recommended to use the original charger Samsung, since they are designed for the phone (and do not cause permanent veyklokov). Jrockttu developed a great application for the memory test in the cap there is a reference to his outstanding theme "save the life of the batteries."

suspend_backoff: toughie. Very strong. Reducing long history in two words, this veyklok occurs when your phone wants to sleep, but the running process does not allow him to do so. A typical example is the Wifi. Make sure your Wifi is configured to operate when the phone is a dream. Otherwise, there is a risk that the Wifi will run amok, to prevent falling asleep phone. It is also, unfortunately, can be caused by applications that complicates this taming veykloka.
To Remedy: perform the operation with Wifi, reboot into rekaveri and wipes are sdelayti cache. If it persists then you have no choice but to look at the dmesg, to try to deal with it. Open a terminal and type the following commands, one per line:

su
dmesg>/mnt/sdcard/dmesg.txt

Then, transfer the file.txt to your computer and open it in WordPad or similar program automatically truncate (not Notepad). Hammer in search of the document "event". You'll find a bunch of lines that look like this:
eventX-XXXX
Where X-s - it figures. You see these four digits after the hyphen? You have to see them repeated over and over again. Rewrite them, then go back to the terminal. They - it's your process ID (PID). In the terminal, type:

ps

This will show all the processes that were started after booting. If you look at the second column on the left, you will see a sequence of four numbers. They are listed from smallest to largest to the bottom of the page. Keep looking until you find a sequence coinciding with the recorded figures. The line below the four characters is the name of the process that causes veyklok. If we see immediately that this application, remove the application, and see what happens. If this is something out of the hardware, which can be easily removed, for example, Wifi, change its settings. If this com.android.process.acore, should soon make a wipe. If you do not know what kind of process, it is not necessary to climb. With the help of the terminal, you can turn the phone into a brick. Instead, copy it, and drive in to Google. Surely, someone has already said what this process is and what it does. If there is something you can easily be fixed in advance. If it's any deep systemic process, just do a full wipe and a clean installation.

Remember, terminal emulators can turn your phone into a brick if you're not careful. If during use happens something bad or you will damage your phone, trying to eliminate one or the other veyklok, this is your problem.

Added from another forum:
musb_autosuspend_wake_lock: This method of core power management to turn off the power micro usb port and hold the connected devices in the power mode support. Perhaps the most veyklok needed to support USB OTG on a given port.
vbus_tuna_otg: sounds like a virtual bus for ustroustv with USB OTG. In the opinion of Franco, this veyklok occurs when "the device is connected to the USB." Hence vyvod- if your GNex connected to a computer via USB, you will see the veyklok.

mipi_link: It stands for Mobile Industry Processor Interface (mobile industry processor interface) but it is unclear what exactly is responsible. Google responds that it can be associated with cameras. Perhaps this type of the current device's camera report.
A source
Alliance Mobile Industry Processor Interface (MIPIВ®) is an organization with open membership, including the mobile industry's leading companies, obediennyh tselbyuopredeli and promote open interface specifications within mobile terminals.
Created in July 2003, ARM, Intel, Nokia, Samsung, STMicroelectronics and Texas Instruments, MIPI aims to reduce complexity and costs while increasing flexibility for cell phones and chips.


PARTIAL VEYKLOKI

PWL - it's a different beast. They are almost always caused by the application (for a couple of important exceptions). For this reason, we will not dig deeply into them, because the decision will usually cause the removal of their applications. Only some of them are significant and deserve attention.

AudioOut_1, AudioOut_2: vicious leech of the genus veyklokov that suck everything down to the bottom, if you give her will. Being a bone in the throat, this veyklok surprisingly easy to eliminate. It is created whenever the phone's speaker plays the sound. Regarding 99% of sounds, it passes almost instantly. With the sounds of the keyboard, but it does not go away so quickly and will sit there, emptying the battery until it has been noticed.
To Remedy: open the settings, select a sound. Disable keyboard sounds, touch sounds and vibrations lock screen with touch. A matter of habit, but the extra battery life you get only solving this ridiculously simple problem, more than worth it.
From the post DoctorQMM: AudioOut_1 through trial and error led to PowerAmp. Even when PowerAmp has not been started, the mark (in Settings ... Headset) to "Pause when disconnected" and "Play when connecting" ... prevented a deep sleep. After removing ticks, PowerAmp AudioOut_1 PWL disappeared ... a deep sleep to recover.
In addition, every time you open PlayStore, AudioOut_1 PWL increases every time some games (even when turned off the sound in the game settings), AudioOut_1 PWL increases. However, this does not affect the deep sleep .. those PWLs only increase if the screen is on!

ConnectivityService: It appears when the phone tries to connect to the mobile network. Veykloki unnecessary in this case indicate that telfon spends a lot of time to search for a sustainable network and more big pile out to stay in it.
To Remedy: Test different radios and find the best for your area.

AlarmManager: it is, in fact, not veyklok and compiling applications signals and the time during which they held device awake mode. View only this veykloka little you give, but here need those features BBS, which we discussed above.
To Remedy: Open the BBS. Tap the menu, then "More (More)" and "Raw Alarms (raw signals)". This will show which applications have prompted your phone, and how often they do it. Google will cause a ton of revivals, but they are mostly harmless. We will discuss some of the problems associated with Google, later. In e-mail clients will also heap signals. If something does not look right, however, first check the application settings on how often it is updated. If the application is set to update every hour, but launched the 400 signals in the last 30 minutes, get rid of this parasite and write to the developer. You can not remove this veyklok, and it can always be # 1, the PWL, but you can minimize it.
A special point about this veykloka: with it you will get all kinds of mad numbers. It can take up to 20 minutes in the hour and a half period of the battery life. You want to kill this veyklok, and kill it with fire. No, stop! Compare the time of its deep sleep and waking time with the included screen. Yes, there are doubts, a value somewhat lower than the 20 minutes which shows veyklok. Your wakefulness when the screen is 3 min. What is the reason for this difference? Well, we know that there veykloki, especially the PWL, which will keep your device awake, even if it has already been awakened: that is, the PWL recorded when the screen is on. Signals, specifically, are the veyklokami because they are designed to wake the device, and it will be the first thing they try to do and will do. There are suspicions that the difference in the testimony lies in the method of reporting program BBS. Each signal is calculated separately, so if the two signals come at you at one and the same time, and they last for 2 minutes each, BBS register veykloka 4 minutes, when in fact the duration of waking time was 2 minutes. It makes sense? Perhaps it does not exist, but it's the best explanation available, and the numbers seem to confirm this.

MediaScannerService: veyklok is generated by the system, scan your device for music, movies, pictures, etc. From time to time, he would periodically turn on and keep the phone at 384 MHz for a while ... well ... as long as you do not notice and do something about it will not do. As AudioOut_1, it greatly affects the battery veyklok. Fortunately, as AudioOut_1, it is almost easy to eliminate. Note on this veykloka: it is periodic, but a serious problem in the firmware Jellybean. While fully knowing why and how to get rid of him forever. By the way, haloeight managed on your phone to get him to surrender.
To eliminate Reloaded. In ninety-nine or so times out of a hundred, it solves the problem. If the problem persists, go to Settings ->Applications ->Working, then click on the "Show cached processes". Find the Media process and stop it by hand to kill veyklok. This is a short-term solution, though, permanent veyklok this process, for the most part may indicate the presence somewhere in the phone-or corrupt media file that you have a lot of sounds, movies, or images. This is one of the few veyklokov that, if they are a regular problem, justify a complete wipe and a clean installation. This is not due to the fact that the phone is applied to some harm, because more than that sift through each media file on your phone to find the culprit, not very practical solution. If you have a fasting person veyklokna firmware JB, try haloeight method.
haloeight method:
1. Search all .nomedia files using ES File Explorer & SD Maid and when connected to a PC -Various techniques can find different files. Removing found. Also remove any .db files in the data / data / com.android.providers.media / databases
2. Remove the empty directories from remote applications using SD Maid or similar programs, if left of them something that is causing the problem.
3. Settings ->Applications ->Everything ->Delete data for the following
Download Manager
Downloads
DRM Protected Content Storage
Media Storage
Gallery
Google Services Framework
Other media related to the application
4. Freeze in TiBu:
Android Live Wallpaper
Clock
Face unlock
Gallery
Live Wallpaper
Messaging
News & Weather
NFC Service
Tags
Talkback
Unicorn Porn
Xperia s
Xperia home
Xperia home preferences
Xperia keyboard
5. Reboot in rekaveri, clear your cache and cache Delvik.
6. Reboot, wait 20 minutes, until all the Media Scanner rescans. Charge your phone to 100 - Media Scanner is no longer rude, but after the restart noted that initially it was still more active on JB, than ICS.

SyncLoopWakeLock: this is how it sounds; Your phone is kept awake mode until the sync application. For him, there are two possible reasons: Sync application and poor communication.
To Remedy: Open the BBS. Tap the menu, then "More (More)" and "Raw Network Stats (untreated network statistics)." This will show which applications are mainly used the network, and will help to identify possible culprits. By doing this, check the settings of these applications and make sure they are not constantly sending push notifications, updated every five minutes or more doing some such nonsense. If they are correctly configured and still keep the timing is too long, try to download Speed ​​Test app from the Play Store and check the connection of your phone. If the connection is slow, it is possible that applications are fighting for the synchronization of the poor quality of the data connection. Try to flash the other radio modules and see if that fixes the problem. If the problem applications behave the same way, and after you have found the best radio is better to remove or freeze them.

ActivityManager family: a safe veyklok. A common cause is a partial exit from applications before the screen turns off.
To Remedy: Do not worry about it much. If it is for you is important, make sure that you fully exit the application (ie, use the back button to exit or forced termination in Task Manager) before the screen turns off. thanksXDA Wikiveyklok for this, he is one of those the PWL, which the author could not describe PROMT because hardly notice it, using the output of the application's back button.

GTALK_ASYNC_CONN family: Despite its name, it is unlikely that this veyklok directly connected with Google Talk. How do we know? The author did not have Google Talk on the phone about a month, but this veyklok from time to time still climbs. Veyklok seems to be related with a poor connection, wifi, so watch out for that, too. These may be absolute veykloki battery destroyers, if given a chance, and unfortunately for them, there is no apparent reason and there is no reliable way to get rid of them.
To eliminate: the veykloki often disappear in about a minute after they occur. If any of them is shown continuously, check the wifi / data transfer and make sure they are OK. If this does not work, reboot into rekaveri and make the wipes are Delvik cache and cache. It solves the problem temporarily, but it will return. Thank you, Google.

NetworkLocationLocator: what a beautiful name for such a pretty veykloka. However, nothing special about this veykloke not. If he appears, it means you are in an area with poor network coverage and lack of support Google Maps Wifi networks.
To eliminate: why on earth are you keep positioning enabled all the time?

NetworkLocationCallbackRunner : thank clankfu and mw86 for pointing this veyklok, and thank you so much promiseofcake for the decision. This is the first veyklok published here is not specific to Skyrocket; S3 is a problem. Hooray, we have moved to a global level! NetworkLocationCallbackRunner - is another veyklok caused the most wonderful application, Google Maps. If you are still using it, but seriously, why?
To Remedy: switch on your phone, open Google kaoty or something else, ispolzueschee Google's location data. Or, you know what, you can simply remove Google Maps so use an alternative program ... details below.

show keyguard: This new veyklok. No, it has always existed, but by changing the firmware, it suddenly became vylazit out. Not huge amounts, but enough to start scratching your head. It has become obvious that the installation of the lock screen does not display user information, weather, or a calendar significantly reduce it. You can try to add to this information one by one, add sliders to lokskrin - harm from it will not. The more people try it, the more accurate will be the concept of veykloka.
To Remedy: Test different possibilities, but it is best to work off display user information, calendar and weather. It seems that it makes the phone prompts for updates, which creates veyklok. Based on recent research, it can be the cause of a large leak.

Chekin Service: thank epapsiou for the discovery and confirmation of the author's speculation. This veyklok being Google services process seems to be caused by Facebook. This confirms the theory that Facebook "borrows" Google services.
For elimination: remove Facebook and use an alternative application, or go to Facebook via your mobile browser.

SCREEN_FROZEN: oh, damn.
To eliminate if it appeared in the list, you have a problem worse than veyklok.

AGGRESSIVE applications that call PWL

Below is a list of applications is causing serious the PWL, and what to do with them.

Note about deleting embedded Google applications: Built-in Google applications - is often a system packages, and their removal can lead to unpredictable results. It is recommended to freeze them in Titanium Backup for a few days to see how the phone works without them, then you can delete. Removing the system processes is particularly dangerous, take responsibility for your decisions.

Facebook: any social networking application wants to sync as often as possible, but you can control it by setting the refresh interval. But the point is what, Facebook does not respect these intervals, and awakens the device to communicate almost constantly (even if the news updated every hour or when you want it). This app is not better than the disease, and to treat it should be the same.
Alternative applications: Friendcaster and Fast is a great alternative, allowing to determine how often they will wake up, but you can just go to m.facebook.com through your phone's browser.

Gmail: the whole essence of this theme is that if there is a Google release the equivalent of an application, you may want to kill Google and download this equivalent. Gmail - is one signal and one of the main culprits the problem with excessive SyncLoopWakeLock.
Alternative applications: as there are e-mail client? Works great stock Email, good alternatives are the K-9, Kaiten, MailDroid, even Enhanced Email and Touchdown for advanced users. The taste and color ...

Whatever email client you are not used: e-mail clients will always be at the top of a list of signals, that is their nature. Keep an eye on the raw statistics of the network, how long are their connections, not be afraid to experiment. The author tried to K-9, Kaiten and MailDroid before set Email stock, provide the best balance between battery life and the features you need.
Alternative application: Download and try a variety of customers until you find one that is right for you. Easily and not catch fish, right?

Google Latitude: a navigation service. As such, it follows you. In addition to this ugly aspect of it at the same time quite often it keeps your phone awake mode. Kill her. Kill it with fire.
Alternative applications: the author is not particularly delved into this topic, but I heard that Glympse works well.

Google Maps: enormous damage to memory and battery. You can fix it. Important note on Google Maps: This app will wake the device, even ate it freeze Titanium Backup. It is not known why this happens, but it's true. For a complete solution of problems with Google Maps signals, there is no other choice but to remove them. Do this at your own risk.
Alternative applications: yes Waze to navigate and MapQuest interface close to Google Maps. OSMAnd is also a good alternative, but it uses a ton of memory because of its off-line life.

Google Play Music & Movies: constantly renew themselves and create veykloki. If they freeze, they still somehow inform you that an update is available. This zombie Google.
Alternative applications: there are literally 100+ music players and movies on the side. You can find what you need. The author is a fan RocketPlayer for music and video player uses the stock.

JuiceDefender: what can I say? JD is a ton of signals and keeps awake longer than it is worth discussing in more because of its installations. In general, the more harm than good.
Alternative applications: the main task of JuiceDefender, in fact, is to minimize the waking hours of your device. Well, if you've already been through it, to get rid of veyklokov, if you need another veyklochnoe application to do again what you just finished?

Skype: Sometimes, after the call, a Skype keeps veyklok. It is not envisaged by the program, and it is more glitch ANNEXES than forced synchronization. Helps forced stop and clearing application cache, if veykloki happen.
Alternative application: no idea. Replacement seems not.

World Weather Clock Widget: you have it on your phone? Get rid. The author has established it as an alternative to the widget SiMi Clock, and, with all its lovely form, it ignores the setting "Update every 3 hours" and tries to be updated 275 times for the 3-hour period. This resulted AlarmManager, GSYNC_ACONN, and NetworkStats in wild horror, and at 82% 6% deep sleep spent battery for 3 hr. Kill him. Kill the glowing nuclear explosion.
Alternative applications: SiMi Clock is a good app, but now there are hundreds of different time widgets.

This is the result of research by the author veyklokov cleaning. Remember that he had previously said, the search engine browser tool is the third? Just the fact that the author did not install all applications on the planet, respectively, and did not see all of the existing PWL. His phone's settings do not allow him to know that there KWL, which he also had never seen and will not see. If you have found a cunning veyklok that does not go away and causes a significant flow battery, Google (or the Bing, or the Ask.com, or something else) help you. Good luck, good hunting, and enjoy an extra battery life you get after spending a couple of hours to several days, tracking and destroying veykloki.

Also go toJrockttu's forum to increase battery life, There is a lot of necessary information.

Additional references in the text. If any of these posts helped you, please. Click the link below and thank the author.
DoctorQMMdeals with the problem com.google.android.apps.maps, alternative solution for AudioOut_1 and using CPU Spy to track veyklokov.
kishkemonitors alternative causes veyklokov family sdio family (ivklyuchaya sdio_al) and puts them to us.
polarbearnoHe shares his experience of working with the family mmc_detect.
haloeightIt gives us good advice on getting rid of veykloka MediaScannerService on firmware based on AOKP.
promiseofcakeIt solves a specific problem for S3 NetworkLocationCallbackRunner PWL.
Note:
Very interesting topic, perhaps it affects more specifics Galaxy SII. than other phones, but it is useful, in fact, to all users of Android. Unfortunately, all 37 pages to translate, I can not, I'm with it something utterly udelali. This is only a cap. Just a couple of veyklokov I added from another forum and descriptions from Wikipedia. Alas, for example, mipi_link I is a leading consumer, but nothing to do with it, I can not. Me and the kernel and firmware, remove the application, even out of the Googley account. And the information on the network, as you can see, is scanty. I hope other veyklokam information handy.


Post has been editedgaich - 06.01.17, 06:27
Reason for editing: Information update



Rep: (1189)
Decided a little more work, the benefit of his leg broke and have time something to do instead of work :-).

Attached fileBetterBatteryStats_xdaedition_1.13.0.0RC1_RUS.apk(2.13 MB)

Cheyndzhlogi last exp. versions:
v1.13.0.0RC1 2013-04-01

Processed storage control marks (mark is removed when first run)
Added "Share" for the dump file, and logkata dmesg
Reworked saving options (dump, dmesg, logkat). Saving these files are now included in the section "Share"
v1.13.0.0B4 2013-03-24

Processed appeal to BR
Neobrab redesigned. statistics
Response in a number of statistics
Added logging for the value / percent
Added timestamps in logkat
v1.13.0.0B3 2013-03-24

Masking account information (personal information)
Fixed a statistics reset to Dashclock widget
v1.13.0.0B2 2013-03-24

Fixed icon disappearing for packages in the processes
Fixed missing icon BR
v1.13.0.0B1 2013-03-19

Added widget dashclock (only Android 4.2.2+)
Saving the dump in JSON format

Names of Labels and other statistics are not transferred - actually help these items are mostly explained, I put brackets English terms. But now the dump in English - if you want you can upload it into the thread on the XDA, experts explained to emerging issues, and no one would swear that everything is in Russian as happened withDelCaos . :-) :-) :-)

Post has been editedgaich - 03.04.13, 09:25



Rep: (29)
Moved with BetterBatteryStats_xdaedition_1.12.4.0.apk versions BetterBatteryStats_xdaedition_1.13.0.0RC1_RUS.apk, stopped working widgets: 2x2 displays only the names of the items - does not update the data, what reference point to display the statistics it is not specified; 1x1 even the title does not show. Also, do not change font and font size to 2x2 (one with graphics), 1x1 never seen - the only place where it should be, so about his text has nothing to say.
By the way, to go to the English version (xdaedition) on Russian, English had to completely remove - at installation has been written, that the application is not signed by that signature.

Post has been editedslas - 03.04.13, 07:46



Rep: (1189)
slas @ 03.04.2013, 14:26*
was written during the installation, the application is not signed by the signature of the

On the contrary, that the same signature, and therefore conflict. And for widgets, I wrote -I have only worked when connected standby, and so I do not use them. try to putenglish version- if you do not work, try the super-digging is, any permission flies ...



Rep: (29)
The English version of widgets running. Russian set to read helpovnik in Russian, asfrom hereopen and did not work either one browser.



Rep: (1189)
slas @ 03.04.2013, 16:06*
The English version of widgets running. Russian set to read helpovnik in Russian, as here open and did not work either one browser.

I tried to tinker more, removed, in particular translation of a tag widgets More on the little things, like now shown infa on them.
Attached Image

Filled updated versionsame wayYou can try again to download and install.
And about, so I help out todaythis postmadea smallreference page, and to help put and operating principles, F.A.Q to heap translated - enjoy! : Yes2:

Post has been editedgaich - 04.04.13, 07:10
Reason for editing: even big get!



Rep: (2)
People help. I set this prog, and it showed that the phone does not give you sleep AudioOut_4. What the app can do it? I have a htc one x + with viperX 1.0.4.



Rep: (6)
I was the same, only Audio_Out 2. Empirically found out that it was the headphones, which I left in the quick-disconnect couplings



Rep: (1189)
Ufff ... Added to yourfastMore knowledge base veyklokam. Naturally, there are not all listed, but it is that there is ...



Rep: (29)
gaich
And you never came across information about the process of "kworker"? In-HETE of information in relation to the android is almost there, and that is - complaints that eats off the battery. Mainly discuss it linuksoidov, chew that kworker loads the kernel. But what to do - is unclear.
Personally, I am on this process began to pay attention only after the analysis of statistics from GSam Battery Monitor. There are those within the application kvokerov "The core (Android OS") - a nontransferable, with all shows in the section included processes.
What is this process, why it so much - is unclear. In this case the battery for 7-8 hours of inactivity dies at 3 percent somewhere - not so bad, when Failure to disconnect mobile data (GSM only).



Rep: (1189)
slas @ 05.04.2013, 13:33*
And you never came across information about the process of "kworker"

itworkflow kernel makes a lot of cases, particularly in terms of what concerns interrupts, timers, I / O (in fact, stands for kernel worker). So here only to understand and forgive. : Rofl:



Rep: (65)
gaich @ 05.04.2013, 10:50*
This workflow is the core, makes a lot of cases
Cool link you suggested! Spasibochki! : Thank_you: Here Toko with an English ... not friends: sveta: Can prompt a similar theme to the great and mighty? (- =



Rep: (1189)
TOL-IK @ 05.04.2013, 17:18*
a great and mighty?

Attached Image

I found the above link by Google. So if you dig, dig can be, but, I believe, will be disappointed - get rid of the core of the process is impossible. : Yes2:

Post has been editedgaich - 05.04.13, 11:49



Rep: (1189)
Completed another work, added to itsreference post. A lot of letters (and imagine they were English!), But oh, I highly recommend reading, a lot of useful information for those who are trying to understand what veykloki, what they eat, and how to deal with onymi. : Yes2:

Yes, and the citizenchamonix also I was not idle all this time - went 1.13.0.0RC2:
# 384: Account name disappears before hashing
Fixed the lack of statistics in the combo boxes for some users after updating labels

Attached fileBetterBatteryStats_xdaedition_1.13.0.0RC2_RUS.apk(2.14 MB)


Post has been editedgaich - 06.04.13, 06:49



Rep: (101)
Prompt, AMP-ta, why "More tab>Untreated network statistics ", as well as if you choose the" Network "in the box on the main screen - nothing is displayed (blank screen) Maybe something off in the settings?


Full version    

Help     rules

Time is now: 02/04/20, 14:39