Related
#1: Keep Your Drive Half Filled
Whenever you use most apps, they will feel sluggish and suffer from “stutter”. Avoid filling the drive beyond 50% capacity (you can get away with 25% free space).
#2: Uninstall Crappy Software
Keeping a minimal number of installed software and media remains one of the cornerstones of a fast device. Fewer apps also means fewer demands on data and a longer battery life. Keep the drive clean of unneeded files.
#3: Leave the Device Idle While Plugged In For 24 Hours
Charging your battery for extended periods of time will cause some battery wear. However, provided you don’t charge overnight on a regular basis, you shouldn’t cause any battery issues. Let the device sit idle for 24 hours. If you’re lucky, this should activate its internal optimization feature.
Credits - Kannon Yamada
It is also important not to use a lot of custom software meant to replace built-in software.
You may have several games installed without slowing down your phone (but be wary of those that automatically connect to the internet in order to bombard you with ads ). However, if you install a launcher, a custom keyboard and a custom lock screen, for example, you will feel quite some serious lag.
So, remember it also matters WHAT you install and WHAT you use
if your phone is rooted, you can use apps like greenify and seeder to reduce lag and to improve your device's performance.
yup
riteish08 said:
#1: Keep Your Drive Half Filled
Whenever you use most apps, they will feel sluggish and suffer from “stutter”. Avoid filling the drive beyond 50% capacity (you can get away with 25% free space).
#2: Uninstall Crappy Software
Keeping a minimal number of installed software and media remains one of the cornerstones of a fast device. Fewer apps also means fewer demands on data and a longer battery life. Keep the drive clean of unneeded files.
#3: Leave the Device Idle While Plugged In For 24 Hours
Charging your battery for extended periods of time will cause some battery wear. However, provided you don’t charge overnight on a regular basis, you shouldn’t cause any battery issues. Let the device sit idle for 24 hours. If you’re lucky, this should activate its internal optimization feature.
Credits - Kannon Yamada
Click to expand...
Click to collapse
Simple things make a big difference. Totally agree with this. :good:
Gringster said:
It is also important not to use a lot of custom software meant to replace built-in software.
You may have several games installed without slowing down your phone (but be wary of those that automatically connect to the internet in order to bombard you with ads ). However, if you install a launcher, a custom keyboard and a custom lock screen, for example, you will feel quite some serious lag.
So, remember it also matters WHAT you install and WHAT you use
Click to expand...
Click to collapse
Yeah , Well said.... :good:
aarish1 said:
if your phone is rooted, you can use apps like greenify and seeder to reduce lag and to improve your device's performance.
Click to expand...
Click to collapse
I use that too!
oh, I restart my Nexus 4 about once a week.
Restarting is useful!
I've just recently started using Greenify and I think I like it, though i'm not sure if the improvement is just in my head. Will have to check out seeder.
Also will agree that reboots are nice. I'd even go so far as to suggest a full power-down/battery pull leaving the battery out for a minute, maybe once a week? But a nightly/daily reboot helps.
Keep the device clean by removing unwanted software and files in the System/app which are waste and don't use it
--------------------Signature--------------------
http://hmpshah.com/signature/
Thanks for sharing
iMewo said:
Thanks for sharing
Click to expand...
Click to collapse
Looks u are new.
Never post a Thanks post this will increase XDA Database Size
So just press Thanks button.
Whixh saves your times and xda Bandwidth
--------------------Signature--------------------
http://hmpshah.com/signature/
There is also app called LagFix (fstrim) for rooted users with 4.2.2 and under. This uses Linux command fstrim to TRIM block no longer required in SSD, more info at http://forum.xda-developers.com/showthread.php?t=1971852. This may not work with all phone. worth a try. Android 4.3 and later already runs this command automatically when your phone is charging and ideal.
Install and remove?
About keeping the device clean.
Is it ok to install apps and then remove them? (so the device doesnt get saturated).
Or will the device eventually slow down just like Windows does?
Is just that I like to test apps and if I like them I keep them, but that involves a lot of testing and installing and removing.
Thanks in advance.
Removing the software I don't need.
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 have a stock tmobile s7. It's running the latest OTA no root. Using cpuz, I identified that my CPU has been running at 90-100 percent non stop. It's making my phone warm all the time, killing my 7300 mha zerolemon battery in less then 2 hours because of how much energy it's using. I don't have the issue in safe mode. I know the phone gets super cold when running in safe mode. I haven't been able to find what process is causing this issue. Most cpu task managers no longer currently work in Nougat according to what i've seen due to a bug that prevents apps from seeing other app's usage. If I don't have another option. I'll just factory reset tomorrow and start from scratch completely. I started removing a ton of apps but still no luck. I've attached a screenshot of cpuz.
There's a "Show CPU usage" option under the monitoring section of the developer options.
CurtisMJ said:
There's a "Show CPU usage" option under the monitoring section of the developer options.
Click to expand...
Click to collapse
That option is also broken by the 7.0 bug. It only shows the system process which is low cpu usage but won't show all running apps. (https://code.google.com/p/android/issues/detail?id=213571) According to google, they have already fixed the bug internally and it's pending a public release. That feature would have definitely helped me pin point the cpu heavy process.
GOVATENT said:
I have a stock tmobile s7. It's running the latest OTA no root. Using cpuz, I identified that my CPU has been running at 90-100 percent non stop. It's making my phone warm all the time, killing my 7300 mha zerolemon battery in less then 2 hours because of how much energy it's using. I don't have the issue in safe mode. I know the phone gets super cold when running in safe mode. I haven't been able to find what process is causing this issue. Most cpu task managers no longer currently work in Nougat according to what i've seen due to a bug that prevents apps from seeing other app's usage. If I don't have another option. I'll just factory reset tomorrow and start from scratch completely. I started removing a ton of apps but still no luck. I've attached a screenshot of cpuz.
Click to expand...
Click to collapse
Search xda for better battery stats, without root you need to give it a permission via adb
So, Sense has always been this way for a while (the HTC EVO 4G LTE was the worst of them all), and I see that the U11 with *almost stock* software and 4GB of RAM is not enough for it to keep a few more apps in the background.
This is bothersome when trying to play games that start over every time that I switch to another app! Even XDA just restarted and I lost half of this post that I was writing. I don't actually see it as a bug or faulty software...just very aggressive RAM management.
Is there any solution to this? Do custom ROMS even solve this issue?
+1, I'd also like to see how to make the RAM management less aggressive. Right now when I play a game, then switch to Chrome, Facebook, or even just public transport timetables app and then go back, game usually starts over. I thought 4 GB of RAM would be enough to have two games loaded, apparently not
LuH said:
+1, I'd also like to see how to make the RAM management less aggressive. Right now when I play a game, then switch to Chrome, Facebook, or even just public transport timetables app and then go back, game usually starts over. I thought 4 GB of RAM would be enough to have two games loaded, apparently not
Click to expand...
Click to collapse
I don't think that the 4GB of RAM is to blame. There is no justification for closing a game to send a TEXT! I think that they just try to keep as much RAM available at all times, at the cost of convenience.
Boost+ enabled,?
Yeah I think it's the boost+ app. Uninstall it and check. I don't use it and I just launched 25apps and none of them reloads.
Update: hmmm actually they started reloading after 3 mins. Not all of them but half. Wierd. I don't mind though as long as the battery stays like this.
In boost+ I don't allow the background optimizer to kick in in less than 3 days on apps I want to run in background, so that's probably not it.
LuH said:
In boost+ I don't allow the background optimizer to kick in in less than 3 days on apps I want to run in background, so that's probably not it.
Click to expand...
Click to collapse
Neither do I. Even coming from a fresh install and rejecting Boost+, the Task Killer is still aggressive.
I think that it depends on the OOM settings (I think that is the correct acronym...haven't dealt with those for a WHILE....).
I was getting frustrated with a lot of my apps pretty much closing every time I backed out of them causing me to have a huge delay in getting notifications as a best case scenario, and sometimes not getting any at all unless I actually opened the app again, Facebook/Messenger being the biggest culprits, but many others too.
Looking in Settings/Power/Battery Optimization I found that nearly all my apps say they are being optimized. I've never used Boost+ so it seems they have defaulted to this. After toggling a few apps to Not Optimized I've found that these apps no longer close and need to reload when I back out, and notifications come through in a timely manner. Battery life seems unaffected, I still easily get through a day and have at least 50% remaining at bed time. Might be worth looking at
liberator72 said:
I was getting frustrated with a lot of my apps pretty much closing every time I backed out of them causing me to have a huge delay in getting notifications as a best case scenario, and sometimes not getting any at all unless I actually opened the app again, Facebook/Messenger being the biggest culprits, but many others too.
Looking in Settings/Power/Battery Optimization I found that nearly all my apps say they are being optimized. I've never used Boost+ so it seems they have defaulted to this. After toggling a few apps to Not Optimized I've found that these apps no longer close and need to reload when I back out, and notifications come through in a timely manner. Battery life seems unaffected, I still easily get through a day and have at least 50% remaining at bed time. Might be worth looking at
Click to expand...
Click to collapse
Bro....thank...you! This definitely made a difference so far.... I'll pay attention to see if it makes a big difference in the long run...
Testing as well, thanks! It doesn't seem connected to Boost+ and appears all my apps are optimized by default - even those I never ran on this phone.
Yeah it had me stumped at first but I noticed it last week and changed it then and have had no problems since. Hopefully it sorts it for you too
liberator72 said:
Yeah it had me stumped at first but I noticed it last week and changed it then and have had no problems since. Hopefully it sorts it for you too
Click to expand...
Click to collapse
Still restarting apps quicker than I prefer, but much better. Thanks!
The problem is android and how it handles apps. If you want to switch apps then use the recents list to use the multi app function (splitscreen).
Beamed in by telepathy.
Got weird observation - curious, if it's only in my case or it's typical.
1. I restrict background usage of the app (doesn't matter which one - google apps as well as 3rd party) with adaptive battery on.
2. After a while (let's say few hours) this app goes back to optimized by itself.
It happens with most of my apps. I can restrict 30 apps and after short period of time only 5-6 stay in restricted mode.
Has anyone got the same problem and/or can share a solution?
Same for me, just wanted to search if iam the only one. Although I think it takes days or weeks for me. Maybe it's a setting we Activate which deletes it (maybe Using adaptive battery?)
I have adaptive battery on and restricted apps, and they stay restricted.
I don't open these apps though, perhaps if you open'restricted' apps they become optimised, which makes sense.
piotrkruczek said:
Got weird observation - curious, if it's only in my case or it's typical.
1. I restrict background usage of the app (doesn't matter which one - google apps as well as 3rd party) with adaptive battery on.
2. After a while (let's say few hours) this app goes back to optimized by itself.
It happens with most of my apps. I can restrict 30 apps and after short period of time only 5-6 stay in restricted mode.
Has anyone got the same problem and/or can share a solution?
Click to expand...
Click to collapse
Thats weird, all my restricted app stay restricted with adaptive battery on
I've the same problem, restricted app goes back to optimized
I have the same problem as well, but I thought they reverted back to optimized following a phone restart - I thought that was the trigger. Anyone else confirm?
Psychlone said:
I have the same problem as well, but I thought they reverted back to optimized following a phone restart - I thought that was the trigger. Anyone else confirm?
Click to expand...
Click to collapse
that should not be the trigger, i restart my phone often and I don't think it ever reverted back because of this.
Hi, I have the same problem with or without adaptative battery. Any solution?
It's annoying because I have Youtube Vanced with MicroG and sometimes MicroG consume a lot of battery. And if I choose restrictive battery, this come back to optimized
PD: I'm not root
EDIT: Not only bring it back to optimized, Garmin connect app backs to unrestrictived (it's default for Garmin app).