If your tablet seems laggy delete the corrupted .jpg images that are created by the default camera 'Camera Awesome'. The corrupt jpg image sends the media scanner into an endless loop that taxes the CPU nonstop. The folder location is Android/data/com.smugmug.android.cameraawesome. I would delete any subfolders also.
Battery drain from Android OS is caused by Blake_wakelock wakelock which is created by the Shield Wireless Controller which is connected your Wi-Fi continually and keeps the tablet from going into a deep sleep. Download the 'Disable Service' app from the Google play store and once it is installed scroll over to the system apps and long click the 'SHIELD Wireless Controller Service'. From there you can disable the 'BlakeManagerService'. You can always turn it back on if and when you need to use it but that will stop your wakelocks.
Related
1.Battery drain
Numerous users have reported problems with the battery life of their devices. One of the easiest ways to prolong your smartphone's battery is to change your locations and brightness settings.Enter the settings menu, click on Location, and select battery saving mode. As for brightness, you should avoid using auto-brightness and instead turn your screen down somewhere below halfway, or to a level that is acceptable for your eyes.
2.Frozen and slow user interface
Phones typically begin to slow down as their internal storage fills up. Try deleting unused apps and photos, or moving them to the cloud or a microSD card. In addition, you should close open apps that you are no longer using, delete app cache, and limit the use of live wallpapers.An app's cached data can be deleted be going to Settings, clicking on Apps, selecting a certain app, and choosing the "Clear cache" option. Programs such as App Cache Cleaner and Clean Master, both of which are available for free from the Google Play store, can also be used to automate the process of clearing cache.
3.Connectivity issues
If you have are having a problem connecting to Bluetooth, Wi-Fi, or your cellular network, enable Airplane mode for 30 seconds, toggle it off, and try connecting again. Sometimes simply toggling the specific connection can also solve the problem.Still having issues? Try repairing or setting up your Bluetooth device or Wi-Fi network again.
4.Stalled text messages
Ensure you are connected to the Internet either through Wi-Fi or cellular, click on the unsent message, and click the "resend" option.If the problem continues, try restarting your device or even installing a third-party messaging app.
5.Syncing error
There are numerous steps you can take to address problems with syncing. First, ensure that you are connected to the Internet, and that the service you are trying to sync with, such as Google or Dropbox, isn't down. Double check that your password is correct and try syncing again.
6.App crashes
Apps can crash for all sorts of reasons. Is there an update available for either the app or your phone? If so, install it.If not, force close the app by swiping it away in the multitask menu (pictured above) and then reopen it.
7.Unresponsive screen
You may want to throw your phone against the wall when it begins to malfunction, but there isn't a need to panic. Most problems are fixed with a simple restart. Although if you physically damaged your phone or dropped it in water, you may have bigger problems on your hands.Press the power button and let the phone turn off, but wait a minute or two before powering it back on.
Hope these advice can help you,thank you!
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.
I've been having severe issues with battery drain both before and after a factory reset, using a completely stock setup. The system app consistently waking the device was NlpCollectorWakeLock - no real news there. However, I managed to fix it with a slightly strange change.
I don't want to disable location services, but I've no interest in location history (which is disabled). However, when I went into the setting (Settings: Location >> Google Location History) there was a message at the top saying "Could not detect current setting" - although the box was unchecked. Checking and unchecking the box both removed this message and has stopped my Note 3's battery drain.
Presumably, because this setting is stored on Google's servers, this would explain how the issue could survive a factory reset. I'm also assuming that whatever this error was was causing constant wakeups.
Though I would share on the off chance it could help somebody else with this issue.
Try amplify (exposed) it limits the Wakelocks... And you don't need to disable features
Hello all. Sometimes (very often actually) the battery starts going down very fast. Taking a look at the frequency states of the CPU I saw it's because it doesn't go in deep sleep state. The guilty is the media scanner process, a sub-process of the download manager app it seems. I tried to Greenify the app, I even disabled the media scanner process completely, nothing. If I go in the Apps section in settings and I find media process in the cached processes the phone doesn't sleep (even if the service is disabled!). How do I prevent it to keep the phone in a permanent wakelock state?
My typical use case of Android TV box (Mi Box S, Android 9) is to watch serials from SMB source in Kodi app. The problem is that Android TV kills Kodi while sleeping, i.e. at the next day I have to start from the initial screen and launch Kodi, then navigate to SMB source, find appropriate folder in the long list, etc.
So is it possible to prevent aps from killing somehow?
@setupio, if you leave your box switched on day and night regardless then you should be able to go into the settings and find power optimisation (aka battery optimisation on phones) and select Kodi to not be optimised. if you do turn the box off this won't help.