BetterBatteryStats -savagemessiahzine.com

> savagemessiahzine.com >Android >Android - Programs >System utilities

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

688 pages
« < 82 83 84 85 86 87 > »

BetterBatteryStats | battery monitoring

18.03.12, 08:20 | #1661
●
Topics Curator
Curators
Rep: (1203)

BetterBatteryStats
version: 2.5

Last update of the program in the header:23.01.2020

Attached Image

screenshots

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!)}

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:

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:

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:

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

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

Reference Post
Online help in Russian

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:BetterBatteryStats_SystemApp_xdaedition_CWM_1.3.0.0.zip(212.59 KB)
and archive of removal of this system from the same recovery:REMOVE_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:

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

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

General energy saving tips

I spend more time on the site than in the subject, so the most current edition of Energy Saving Tipshere.

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.
On new android is setting in "Battery" - autorun, or launch applications. There you can disable unnecessary, so as not to run itself and not hanging in the background.

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.
In the most recent versions of Android, you can find the item "network applications" in the network settings, where you can disable particular insolent Internet access.

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.
In other locations, the settings is the "Use a WiFi network to determine the location." So, with this setting, search for WiFi networks will be involved, even if WiFi is turned off itself, which itself will increase the accuracy of determination hardly, but, of course, impact on battery consumption.

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.

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.

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.

Each application can be viewed separately and see which processes it has activated.

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. Without root, although it does not work in full force and slow. I recommend to hand over the file manager to get into the folder, for example, instant messengers and clean it the old media.
- 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

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 - 13.06.20, 16:10

Reason for editing: Add-ons

03.08.14, 12:27 | #1662
●
Friendssavagemessiahzine.com
Rep: (260)

gaich
If I put the latest version of BBS through CWM, then it will be possible to later remove it from zipom FAQ REMOVE_BetterBatteryStats_SystemApp_CWM_1.1.0.0.zip? Well, or any system files involves the installation of spare parts? I ask because for subsequent OTA firmware update is necessary that the system partition was not touched.

03.08.14, 12:52 | #1663
●
Topics Curator
Curators
Rep: (1203)

Imp_GL @ 03.08.2014, 18:41

Again, I repeat the question. Where is this little application to take?

again the answer

gaich @ 03.08.2014, 00:36

zip, unzip, get there this apk

kbm113 @ 03.08.2014, 19:27

If I put the latest version of BBS through CWM, then it will be possible to later remove it from zipom FAQ REMOVE_BetterBatteryStats_SystemApp_CWM_1.1.0.0.zip?

Yes of course.

kbm113 @ 03.08.2014, 19:27

which involves the installation system files zip?

No. He inserts a Russified version

gaich @ 03.08.2014, 12:49

Russified version: BetterBatteryStats_xdaedition_1.16.1.0B1_RUS.apk

by the address

gaich @ 02.08.2014, 13:44

system / priv-apps

And it looks like this: spoilerthis message.

Post has been editedgaich - 03.08.14, 13:01

04.08.14, 10:52 | #1664
●
Friendssavagemessiahzine.com
Rep: (6)

Hello.
Need help, can someone faced a similar problem: Phone huawei p6, cost custom Omni RE, 0 Android 4.4.4. The very problem is that when the mobile phone Internet, per night eats about 3% of the battery, and if you turn wifi - eats up 17% and the process of wifi is always active.
What to do: Startup cleaned, selected its mobile network (auto-disable), select "only 2G", geolocation is turned off, the synchronization is disabled. The wifi settings should "do not turn off wifi in sleep mode" and optimization wifi during sleep time.
When working at the drain was observed initially high energy consumption, so the left immediately on custom bikes, of which many have tried, the best of speed and appearance seemed to me the Omni in principle satisfied with everything except consumption for wifi ...

Statistics with wifi and free bbs

BetterBatteryStats-2014-07-31_072208750 [1] .txt(18.1 KB)

BetterBatteryStats-2014-08-01_073213668 [1] .txt(17.92 KB)

On screens with wifi

On screens with mobile internet

04.08.14, 11:27 | #1665
●
Friendssavagemessiahzine.com
Rep: (70532)

v.1.16.1.0B2 (04.08.2014)

- correction cboya operation standby

Russified version: Attached file

BetterBatteryStats_xdaedition_1.16.1.0B2_RUS.apk(4.21 MB)

Zip for CWM / TWRP on KitKat: Attached file

BBS_FULL_RUS_CWM_1.16.1.0B2.zip(4.1 MB)

Post has been editedgaich - 09.08.14, 09:37

Reason for editing: Formatting

05.08.14, 06:07 | #1666
●
Friendssavagemessiahzine.com
Rep: (3)

When you try to install the new version as the system application climbs the message "Failed"

05.08.14, 17:58 | #1667
●
Topics Curator
Curators
Rep: (1203)

hoodan83, check the router to start, look for tips in the cap.

pavel.korolev86, also take a look at the cap, there are other installation options.

Post has been editedgaich - 05.08.14, 18:02

05.08.14, 18:37 | #1668
●
Friendssavagemessiahzine.com
Rep: (552)

gaich I certify on 2 firmware when installed as a system - error. As a user + companion - works.

06.08.14, 01:51 | #1669
●
Topics Curator
Curators
Rep: (1203)

J_Livingston, I no longer set by the application, and in many the same picture, so I applied for rekaveri zips.

06.08.14, 06:21 | #1670
●
Friendssavagemessiahzine.com
Rep: (260)

gaich
Version with xda put through the application 4.4.4.

06.08.14, 06:24 | #1671
●
Friendssavagemessiahzine.com
Rep: (955)

kbm113,
Similarly

06.08.14, 09:21 | #1672
●
Topics Curator
Curators
Rep: (1203)

kbm113,

denon480
FAQ, paragraph 1:
"I have repeatedly written, the Russian version translated informally and, quite possibly, from the translation could suffer and the system files)"

06.08.14, 19:15 | #1673
●
Friendssavagemessiahzine.com
Rep: (1)

Dear please tell me what it means to the current status: Okay Signal - 100%? Network mode GSM only worth, and the signal strength is good. If you put only mode WCDMA writes: good signal - 0%, and the level of the signal just 20-50%. It turns out that BetterBatteryStats believes that in GSM mode sucks and catches a load of as much 100% chtoli? :-(

06.08.14, 21:13 | #1674
●
Friendssavagemessiahzine.com
Rep: (1184)

hoodan83 @ 04.08.2014, 11:52

Optimization wifi during sleep time.

What kind of beast is it?

"Xmm_power" (): 2 h 13 m 56 s (8036 s) Cnt: (c / wc / ec) 2771/0/0 27,0%

You have a case like this:
http: //forum.xda-devel...owthread.php t = 2033765?

let'straffic from your smartphonewe'll see.

Ran on issues xmm_power - veyklok many people associate with a modem, it happens on chips tegra, it seems, can be cured by replacing the kernel, or to try to set the search operator "manually".

Post has been editedgaich - 08.08.14, 16:21

07.08.14, 09:47 | #1675
●
Users
Rep: (0)

People please help. Phone MI3 TD. I sew from version 4.7.25 to 4.8.1 with both miui.su. site Bottom line: he was to eat the battery in sleep mode. 4.7.25 version of the situation is established again the same ... to clear the cache, and wipe all data, again, put the firmware 4.7.25 situation is the same ....
Section Battery consumption shows that the main flow makes "OC Android"

BBS has established dump for 5.5 hours in sleep mode consumes 44% of the charge.

Help who can decipher the dumps. Prior to that he held the charge of the day 3. ready to provide compensation. Dump attached.

Attached file

BetterBatteryStats-2014-08-07_052621515.txt(18.43 KB)

07.08.14, 09:54 | #1676
●
Friendssavagemessiahzine.com
Rep: (6)

tester99, Shark for Root for this business go? what period of time should be zasnifit, sleep, or you can just turn on Wi fi and zasnifit hour phone?

08.08.14, 07:41 | #1677
●
Friendssavagemessiahzine.com
Rep: (45)

guys tell zygote is that? and how to calm down?

08.08.14, 09:50 | #1678
●
Users
Rep: (0)

What kind of trouble eats the Akuma? a week trying to figure out

===================
General information
===================

BetterBatteryStats version: 1.15.0.0

Creation Date: 2014-08-07 05:26:20

Statistic Type: Unplugged to Current
Since 7 h 16 m 54 s

VERSION.RELEASE: 4.4.2

BRAND: Xiaomi

DEVICE: pisces

MANUFACTURER: Xiaomi

MODEL: MI 3
OS.
VERSION: 3.4.35-g0662c74

BOOTLOADER: unknown

HARDWARE: pisces

FINGERPRINT: Xiaomi / pisces / pisces: 4.4.2 / KOT49H / 4.7.25: user / release-keys
ID:
KOT49H
TAGS: release-keys

USER: builder
PRODUCT: pisces

RADIO: DM_BASE_13A_8803G_W13.44 | 20140120092332

Rooted: true

============
Battery info
============

Level lost [%]: Bat .: -44% (100% to 56%) [6,0% / h]

Voltage lost [mV]: (4365-3840) [72,1% / h]

===========
Other usage
===========

Screen On (): 11 s (11 s) Ratio: 0,0%

Deep Sleep (): 1 h 46 m 16 s (6376 s) Ratio: 24,3%
Awake (): 5 h 30 m 38 s (19838 s) Ratio: 75,7%

=========
Wakelocks
=========

AlarmManager (0): 24 s (24 s) Count: 467 85.7%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 2 s (2 s) Count: 1 7.1%
CallerInfoCache (0) 1 s (1 s) Count: 1 3.6%

NfcService: mRoutingWakeLock (0) 1 s (1 s) Count: 3 3.6%

================
Kernel Wakelocks !!! wakeup_sources !!!
================

alarmtimer (): 1 m 4 s (64 s) Cnt: (c / wc / ec) 32/32/32 0,2%

alarm (): 38 s (38 s) Cnt: (c / wc / ec) 471/220/0 0,1%

PowerManagerService. WakeLocks (): 26 s (26 s) Cnt: (c / wc / ec) 483/44/0 0,1%

sc8800g_wake_lock (): 26 s (26 s) Cnt: (c / wc / ec) 37/8/38 0,1%

max170xx_battery (): 1 s (1 s) Cnt: (c / wc / ec) 332/179/0 0,0%

vbus-tegra-otg (): 1 s (1 s) Cnt: (c / wc / ec) 1/0/2 0,0%

KeyEvents (): 1 s (1 s) Cnt: (c / wc / ec) 76940/665/0 0,0%

nfcwakelock (): (0 s) Cnt: (c / wc / ec) 8/0/0 0,0%

event0-903 (): (0 s) Cnt: (c / wc / ec) 4/1/0 0,0%

=========
Processes
=========

kworker / u: 0 (0): Uid: 0 Sys: 37 m 35 s (2255 s) Us: (0 s) Starts: 0

kworker / u: 1 (0): Uid: 0 Sys: 13 m 49 s (829 s) Us: (0 s) Starts: 0

kworker / u: 3 (0): Uid: 0 Sys: 6 m 6 s (366 s) Us: (0 s) Starts: 0

kworker / u: 2 (0): Uid: 0 Sys: 4 m 44 s (284 s) Us: (0 s) Starts: 0

system_server (Android System): Uid: 1000 Sys: 3 m 22 s (202 s) Us: 1 m 4 s (64 s) Starts: 0
/ Init (0): Uid: 0 Sys: 3 m 26 s (206 s) Us: 45 s (45 s) Starts: 0

kworker / u: 4 (0): Uid: 0 Sys: 3 m 19 s (199 s) Us: (0 s) Starts: 0

com.android.systemui (Android System): Uid: 1000 Sys: 1 m 23 s (83 s) Us: 16 s (16 s) Starts: 0

com.android.phone (Phone): Uid: 1001 Sys: 1 m 16 s (76 s) Us: 6 s (6 s) Starts: 0

kworker / 0: 3 (0): Uid: 0 Sys: 1 m 10 s (70 s) Us: (0 s) Starts: 0

android.process.acore (): Uid: -1 Sys: 57 s (57 s) Us: 6 s (6 s) Starts: 0

com.miui.securitycenter (Android System): Uid: 1000 Sys: 56 s (56 s) Us: 5 s (5 s) Starts: 0

kworker / 0 0 (0): Uid: 0 Sys: 57 s (57 s) Us: (0 s) Starts: 0

com.google.android.inputmethod.latin (com.google.android.inputmethod.latin.Klaviatura Google): Uid: 10070 Sys: 53 s (53 s) Us: 3 s (3 s) Starts: 0

com.miui.home (com.miui.home.Rabochy MIUI table): Uid: 10009 Sys: 47 s (47 s) Us: 8 s (8 s) Starts: 0

kworker / 0: 1 (0): Uid: 0 Sys: 53 s (53 s) Us: (0 s) Starts: 0

com.android.nfc (com.android.nfc.NFC): Uid: 1027 Sys: 49 s (49 s) Us: 2 s (2 s) Starts: 0

com.android.settings (Android System): Uid: 1000 Sys: 49 s (49 s) Us: 2 s (2 s) Starts: 0

com.xiaomi.xmsf (com.xiaomi.xmsf.Sistemnye service Mi Cloud): Uid: 10066 Sys: 43 s (43 s) Us: 7 s (7 s) Starts: 0

kworker / u: 5 (0): Uid: 0 Sys: 50 s (50 s) Us: (0 s) Starts: 0

com.miui.networkassistant (Android System): Uid: 1000 Sys: 41 s (41 s) Us: 3 s (3 s) Starts: 0

kworker / 0 2 (0): Uid: 0 Sys: 44 s (44 s) Us: (0 s) Starts: 0

com.trafficctr.miui (com.trafficctr.miui.TrafficControl): Uid: 10062 Sys: 34 s (34 s) Us: 3 s (3 s) Starts: 0

com.lbe.security.miui: service (com.lbe.security.miui.Razresheniya): Uid: 10041 Sys: 32 s (32 s) Us: 2 s (2 s) Starts: 0

com.miui.backup (com.miui.backup.Bekap): Uid: 9800 Sys: 28 s (28 s) Us: 6 s (6 s) Starts: 0
cfinteractive (0): Uid: 0 Sys: 34 s (34 s) Us: (0 s) Starts: 0

lbesec.loader (0): Uid: 0 Sys: 29 s (29 s) Us: 2 s (2 s) Starts: 0

surfaceflinger (Android System): Uid: 1000 Sys: 24 s (24 s) Us: 6 s (6 s) Starts: 0

com.svox.pico (com.svox.pico.Pico TTS): Uid: 10058 Sys: 26 s (26 s) Us: 2 s (2 s) Starts: 0

com.android.deskclock (com.android.deskclock.Chasy): Uid: 10030 Sys: 26 s (26 s) Us: 2 s (2 s) Starts: 0

rild (Phone): Uid: 1001 Sys: 28 s (28 s) Us: (0 s) Starts: 0

com.miui.providers.weather (com.miui.providers.weather.Postavschik weather): Uid: 10065 Sys: 25 s (25 s) Us: 2 s (2 s) Starts: 0

com.android.defcontainer (com.android.defcontainer.Package Access Helper): Uid: 10004 Sys: 25 s (25 s) Us: 2 s (2 s) Starts: 0

com.amap.android.location (com.amap.android.location.Opredelenie locations): Uid: 10021 Sys: 19 s (19 s) Us: 7 s (7 s) Starts: 0

com.android.settings: remote (Android System): Uid: 1000 Sys: 22 s (22 s) Us: 2 s (2 s) Starts: 0

com.lbe.security.miui (com.lbe.security.miui.Razresheniya): Uid: 10041 Sys: 21 s (21 s) Us: 1 s (1 s) Starts: 0

netd (0): Uid: 0 Sys: 16 s (16 s) Us: 6 s (6 s) Starts: 0

adbd (com.android.shell.Obolochka): Uid: 2000 Sys: 19 s (19 s) Us: (0 s) Starts: 0

com.google.android.gsf.login (Google Play Services): Uid: 10007 Sys: 16 s (16 s) Us: (0 s) Starts: 1

com.miui.gallery (com.miui.gallery.Galereya): Uid: 10008 Sys: 14 s (14 s) Us: (0 s) Starts: 0

mediaserver (1013): Uid: 1013 Sys: 14 s (14 s) Us: (0 s) Starts: 0

com.android.providers.calendar (com.android.providers.calendar.Pamyat calendar): Uid: 10026 Sys: 13 s (13 s) Us: (0 s) Starts: 1

com.android.calendar (com.android.calendar.Kalendar): Uid: 10001 Sys: 13 s (13 s) Us: (0 s) Starts: 1
vold (0): Uid: 0 Sys: 12 s (12 s) Us: (0 s) Starts: 0

mdbd (0): Uid: 0 Sys: 12 s (12 s) Us: (0 s) Starts: 0

shelld (Android System): Uid: 1000 Sys: 10 s (10 s) Us: (0 s) Starts: 0

zygote (0): Uid: 0 Sys: 7 s (7 s) Us: 3 s (3 s) Starts: 0

flush-179 0 (0): Uid: 0 Sys: 10 s (10 s) Us: (0 s) Starts: 0

com.miui.providers.datahub (com.miui.providers.datahub.DataHub Provider): Uid: 10029 Sys: 9 s (9 s) Us: (0 s) Starts: 1

glgps_nvidiaTegra2android (1021): Uid: 1021 Sys: 9 s (9 s) Us: (0 s) Starts: 0

powerservice (Android System): Uid: 1000 Sys: 8 s (8 s) Us: (0 s) Starts: 0

servicemanager (Android System): Uid: 1000 Sys: 7 s (7 s) Us: 1 s (1 s) Starts: 0

ueventd (0): Uid: 0 Sys: 4 s (4 s) Us: 3 s (3 s) Starts: 0

kthreadd (0): Uid: 0 Sys: 7 s (7 s) Us: (0 s) Starts: 0

debuggerd (0): Uid: 0 Sys: 5 s (5 s) Us: 1 s (1 s) Starts: 0

com.android.updater (com.android.updater.Obnovlenie): Uid: 9802 Sys: 6 s (6 s) Us: (0 s) Starts: 1

healthd (0): Uid: 0 Sys: 6 s (6 s) Us: (0 s) Starts: 0

rm_ts_server (Android System): Uid: 1000 Sys: 6 s (6 s) Us: (0 s) Starts: 0

irq / 77-tegra_ac (0): Uid: 0 Sys: 6 s (6 s) Us: (0 s) Starts: 0

sdcard (1023): Uid: 1023 Sys: 5 s (5 s) Us: (0 s) Starts: 0

fild (0): Uid: 0 Sys: 5 s (5 s) Us: (0 s) Starts: 0

wlbwservice (Android System): Uid: 1000 Sys: 5 s (5 s) Us: (0 s) Starts: 0

drmserver (1019): Uid: 1019 Sys: 5 s (5 s) Us: (0 s) Starts: 0

com.android.fileexplorer: remote (): Uid: -1 Sys: 5 s (5 s) Us: (0 s) Starts: 1

kworker / 0: 4 (0): Uid: 0 Sys: 5 s (5 s) Us: (0 s) Starts: 0

immvibed (Android System): Uid: 1000 Sys: 4 s (4 s) Us: (0 s) Starts: 0

nvsyncd (0): Uid: 0 Sys: 4 s (4 s) Us: (0 s) Starts: 0

akmd8963 (Android System): Uid: 1000 Sys: 4 s (4 s) Us: (0 s) Starts: 0

su (0): Uid: 0 Sys: 3 s (3 s) Us: (0 s) Starts: 0

flush-0: 19 (0): Uid: 0 Sys: 3 s (3 s) Us: (0 s) Starts: 0

keystore (1017): Uid: 1017 Sys: 2 s (2 s) Us: (0 s) Starts: 0

tunman (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0

installd (1012): Uid: 1012 Sys: 2 s (2 s) Us: (0 s) Starts: 0

bdi-default (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0

irq / 83-soctherm (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

mmcqd / 0 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

kswapd0 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

jbd2 / mmcblk0p24 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

jbd2 / mmcblk0p27 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

jbd2 / mmcblk0p26 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

khubd (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

jbd2 / mmcblk0p28 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

jbd2 / mmcblk0p23 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0

irq / 77-tegra_mo (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

ksoftirqd / 0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

file-storage (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

android.process.media (): Uid: -1 Sys: (0 s) Us: (0 s) Starts: 2

com.xiaomi.market (com.xiaomi.market.Mi Store): Uid: 10061 Sys: (0 s) Us: (0 s) Starts: 1

mmcqd / 0boot1 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

mmcqd / 0boot0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / u: 0H (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 0: 1H (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 1 0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

watchdog / 0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 1: 0H (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 2: 2 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 2: 0H (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 3 0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 3: 0H (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

irq / 266-max7766 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

sync_supers (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

irq / 91-tegra_sp (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

irq / 311-inv_irq (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

irq / 105-tegradc (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

irq / 274-atmel_m (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

migration / 0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

kworker / 1: 1H (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0

======================
Alarms (requires root)
======================

android (): Wakeups: 33

Alarms: 0, Intent: android.intent.action.TIME_TICK

Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL

Alarms: 32, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED

Alarms: 0, Intent: miui.intent.action.CHECK_TIME_UP

Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL

Alarms: 1, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE

Alarms: 0, Intent: android.content.syncmanager.SYNC_ALARM

com.trafficctr.miui (): Wakeups: 1

Alarms: 1, Intent: {com.trafficctr.miui / com.opera.max.web.DataUsageMaintenanceScheduler}

======================
Network (requires root)
=================

=====
==========
CPU States
==========

51 MHz (): 1 m 25 s 0,3%

102 MHz (): 1 s 0,0%

204 MHz (): 0,0%

306 MHz (): 45 s 0,2%
324 MHz (): 0,0%

396 MHz (): 1 s 0,0%

510 MHz (): 9 m 45 s 2,2%

612 MHz (): 1 m 13 s 0,3%

768 MHz (): 8 s 0,0%

816 MHz (): 5 h 17 m 3 s 72,6%

918 MHz (): 1 s 0,0%
1,02 GHz (): 1 s 0,0%

1,12 GHz (): 0,0%
1,22 GHz (): 1 s 0,0%

1,33 GHz (): 0,0%

1,43 GHz (): 5 s 0,0%

Deep Sleep (): 1 h 46 m 16 s 24,3%

========
Services
========

Active since the moment when it was made.
Last activity:
Seehttp: //developer.andro...unningServiceInfo.html
com.android.mms (com.android.mms.transaction.SmsReportService)
Active since: 50 s
Last activity: 10 h 10 m 55 s
Crash count: 0
com.xiaomi.xmsf (com.xiaomi.xmsf.account.ActivateService)
Active since: 30 s
Last activity: 10 h 10 m 51 s
Crash count: 0
com.android.settings (com.android.settings.wifi.MiuiWifiService)
Active since: 15 m 51 s
Last activity: 15 m 11 s
Crash count: 0
com.miui.securitycenter (com.miui.powercenter.provider.PowerSaveService)
Active since: 51 s
Last activity: 51 s
Crash count: 0
com.android.settings (com.android.settings.analytics.ObserverService)
Active since: 51 s
Last activity: 51 s
Crash count: 0
com.android.phone (com.android.phone.BluetoothPhoneService)
Active since: 23 s
Last activity: 23 s
Crash count: 0
com.miui.backup (com.miui.backup.cloud.CloudAppService)
Active since: 47 s
Last activity: 47 s
Crash count: 0
com.android.phone (com.android.providers.telephony.MakeMmsPreviewService)
Active since: 33 s
Last activity: 10 h 10 m 55 s
Crash count: 0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 21 s
Last activity: 21 s
Crash count: 0
com.google.android.inputmethod.latin (com.android.inputmethod.latin.spellcheck.AndroidSpellCheckerService)
Active since: 25 s
Last activity: 25 s
Crash count: 0
com.nvwfd.server.internal.protocols (com.nvwfd.server.internal.protocols.ProtocolsPackService)
Active since: 53 s
Last activity: 53 s
Crash count: 0
com.amap.android.location (com.amap.android.location.NetworkLocationService)
Active since: 22 s
Last activity: 22 s
Crash count: 0
com.android.fileexplorer: remote (cn.kuaipan.android.service.KscService)
Active since: 9 h 50 m 28 s
Last activity: 8 h 22 m 52 s
Crash count: 0
android.process.acore (com.android.providers.contacts.GuardService)
Active since: 22 s
Last activity: 22 s
Crash count: 0
com.android.systemui (com.android.keyguard.KeyguardService)
Active since: 20 s
Last activity: 20 s
Crash count: 0
com.miui.home (com.miui.home.launcher.ForegroundPlaceholderService)
Active since: 24 s
Last activity: 24 s
Crash count: 0
com.nvidia.NvCPLSvc (com.nvidia.NvCPLSvc.NvCPLService)
Active since: 23 s
Last activity: 10 h 10 m 54 s
Crash count: 0
com.trafficctr.miui (com.opera.max.sdk.saving.SavingService)
Active since: 11 m 32 s
Last activity: 9 m 37 s
Crash count: 0
com.android.updater (com.android.updater.UpdaterBackgroundService)
Active since: 57 s
Last activity: 4 h 49 m 39 s
Crash count: 0
com.trafficctr.miui (com.opera.max.sdk.traffic.TrafficService)
Active since: 11 m 32 s
Last activity: 9 m 37 s
Crash count: 0
com.nvidia.NvWFDSvc (com.nvidia.NvWFDSvc.NvwfdService)
Active since: 34 s
Last activity: 34 s
Crash count: 0
com.android.bluetooth (com.android.bluetooth.a2dp.A2dpService)
Active since: 34 s
Last activity: 34 s
Crash count: 0
com.miui.networkassistant (com.miui.networkassistant.service.FirewallService)
Active since: 33 s
Last activity: 9 m 37 s
Crash count: 0
com.miui.networkassistant (com.miui.networkassistant.service.tm.TrafficManageService)
Active since: 33 s
Last activity: 9 m 37 s
Crash count: 0
com.miui.securitycenter (com.miui.securitycenter.SecurityCenterService)
Active since: 23 s
Last activity: 2 m 18 s
Crash count: 0
com.xiaomi.xmsf (com.xiaomi.xmsf.account.AlertSyncService)
Active since: 55 s
Last activity: 55 s
Crash count: 0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 20 s
Last activity: 20 s
Crash count: 0
com.xiaomi.xmsf (com.xiaomi.push.service.XMPushService)
Active since: 21 s
Last activity: 10 h 10 m 55 s
Crash count: 0
system (android.hardware.location.GeofenceHardwareService)
Active since: 21 s
Last activity: 21 s
Crash count: 0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkServiceProxy)
Active since: 16 m
Last activity: 15 m 11 s
Crash count: 0
com.xiaomi.xmsf (com.xiaomi.xmsf.account.MiCloudTaskService)
Active since: 16 m 41 s
Last activity: 14 m 46 s
Crash count: 0
com.miui.guardprovider (com.miui.guardprovider.SecureService)
Active since: 1 m 16 s
Last activity: 6 m 14 s
Crash count: 0
com.svox.pico (com.svox.pico.PicoService)
Active since: 4 m 10 s
Last activity: 10 h 10 m 55 s
Crash count: 0
com.android.phone (com.android.stk.StkAppService)
Active since: 54 s
Last activity: 59 s
Crash count: 0
com.google.android.inputmethod.latin (com.android.inputmethod.latin.LatinIME)
Active since: 21 s
Last activity: 9 m 56 s
Crash count: 0
com.xiaomi.xmsf (com.xiaomi.xmsf.account.MiCloudStatusService)
Active since: 55 s
Last activity: 14 m 46 s
Crash count: 0
com.android.settings: remote (com.miui.securitycenter.services.MemoryCheckService)
Active since: 2 m 18 s
Last activity: 2 m 18 s
Crash count: 0
com.android.bluetooth (com.android.bluetooth.hfp.HeadsetService)
Active since: 25 s
Last activity: 25 s
Crash count: 0
system (com.android.internal.backup.LocalTransportService)
Active since: 20 s
Last activity: 20 s
Crash count: 0
com.amap.android.location (com.amap.android.location.GeocodeService)
Active since: 1 5 m s
Last activity: 1 m 5 s
Crash count: 0
com.amap.android.location (com.amap.android.location.internal.server.NetworkLocationService)
Active since: 22 s
Last activity: 22 s
Crash count: 0
com.android.defcontainer (com.android.defcontainer.DefaultContainerService)
Active since: 20 s
Last activity: 26 s
Crash count: 0
com.android.phone (com.android.phone.TelephonyDebugService)
Active since: 23 s
Last activity: 23 s
Crash count: 0
com.lbe.security.miui: service (com.lbe.security.service.SecurityService)
Active since: 23 s
Last activity: 4 h 40 m 42 s
Crash count: 0
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 20 s
Last activity: 20 s
Crash count: 0

==================
Reference overview
==================

ref_unplugged: Reference ref_unplugged created 4 h 58 m 26 s (Wl: 0 elements; KWl: 14elements; NetS: 12 elements; Alrm: 8 elements; Proc: 0 elements; Oth: 3 elements; CPU: 21 elements)
ref_charged: Reference ref_charged created 4 h 58 m 27 s (Wl: 1 elements; KWl: 14elements; NetS: 12 elements; Alrm: 8 elements; Proc: 0 elements; Oth: 3 elements; CPU: 21 elements)
ref_current: Reference ref_current created 12 h 15 m 20 s (Wl: 4 elements; KWl: 13elements; NetS: 12 elements; Alrm: 7 elements; Proc: 107 elements; Oth: 3 elements; CPU: 21 elements)

Post has been edited2012swoboda - 08.08.14, 10:32

08.08.14, 09:54 | #1679
●
Friendssavagemessiahzine.com
Rep: (955)

2012swoboda,
Message design

08.08.14, 15:50 | #1680
●
Topics Curator
Curators
Rep: (1203)

DAMIR-777 @ 08/07/2014, 2:15

BetterBatteryStats believes that in the GSM mode sucks catches

BBS reads data from the phone. How phone equipment evaluates the signal, so it will be displayed in the program.

2012swoboda @ 07.08.2014, 16:47

Help who can decipher the dumps.

No information why the phone does not sleep 5 h 30 m 38 s to dump there. Try it, maybe the latest version of the BBS?

TAVarish @ 08.08.2014, 14:41

guys tell zygote is that?

ProcessResponsible for launching applications. I think that will get rid of it only if you do not run the application.

hoodan83,
Finally gained access to the computer, just rummaged on the Internet, supplementedthis post.

P.S. Russified version version 1.16.1.0_B2addedIn addition, just over the first item in detail painted F.A.Q., regarding the work of BBS on Android 4.4 and the latest clarifying questions of translation.

Post has been editedgaich - 09.08.14, 17:25

09.08.14, 06:05 | #1681
●
Friendssavagemessiahzine.com
Rep: (45)

gaich @ 08.08.2014, 18:50

I think that will get rid of it only if you do not run the application.

he calmed down ... last sazhral charging the batteries a little less than the screen

688 pages
« < 82 83 84 85 86 87 > »

Full version

Help rules

Time is now: 08/05/20, 10:26

©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com^®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement

Forum IP.Board © 2020 IPS, Inc .