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 sourceAlliance 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. thanks
XDA 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 to
Jrockttu'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.