So do you guys find it necessary to have a ram manager to free memory or no ?
No, ics have a good system to manage ram.
No. Creates more issues than it solves.
+1 for no. Watchdog has always been a must have for me, but it hasn't yet had to call out an app on my SGN.
No. Don't use automated tools to kill tasks and free up memory... in Android, free memory is wasted memory. You make your phone work harder when you interfere with its built-in memory management.
I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.
EP2008 said:
I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.
Click to expand...
Click to collapse
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Funniest thing I read all day and its true
adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Android does not operate like windows. Apps listed as "Running" are actually only loaded in ram and are not using cpu cycles or battery power. Android loads them in ram in order for them to start/be available more quickly to the user. If Android needs more ram for a task, it will remove any thing it needs to in order to free up more ram. You are wasting battery power and cpu cycles by "killing" those apps/service. If you think of ram as a memory stick you will realize that once something is loaded there, it doesn't take any power to keep it there.
Good luck
Good luck
jordanishere said:
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
System services should obviously not be messed with, but disabling autostarting services that you don't use is generally not a problem. It may take more power/time to start up apps that use those services (since they will have to be manually started), but if it's an app that you use infrequently it may be worth doing.
Intelligently tuning what services are allowed to autostart themselves is NOT the same as indiscriminately killing apps chasing after "free memory".
Personally, I wouldn't terminate services, but only modify which ones are allowed to automatically start up with the OS.
codesplice said:
if it's an app that you use infrequently it may be worth doing.
Click to expand...
Click to collapse
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
you basically proved what he said was true
I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.
jordanishere said:
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Eh, usually there's not much benefit to be had - but preventing a service from auto starting when you might not use its app for the entire time Android is booted won't cause any problems. You're essentially "freezing" the service while still allowing it to be used on demand .
WiredPirate said:
I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.
Click to expand...
Click to collapse
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN. Not necessarily a technical response, but just my experience.
Wow, the ignorance on XDA is staggering.
A RUNNING SERVICE is not the same as a cached app or background process.
Why the heck would anyone want 3 or 4 running services in the background when they don't need them running?
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk
EP2008 said:
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Less an Android flaw and more related to how developers wrote those apps. Otherwise I think we are in agreement though.
codesplice said:
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN.
Click to expand...
Click to collapse
why?
10char
Related
Love the phone but a few times the launcher has redrawn after exiting an app because of most likely memory issues. Anybody using this option? Assuming over time this would keep more memory free and reduce this issue. Any thoughts?
Sent from my Galaxy Nexus using xda premium
mobilehavoc said:
Love the phone but a few times the launcher has redrawn after exiting an app because of most likely memory issues. Anybody using this option? Assuming over time this would keep more memory free and reduce this issue. Any thoughts?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is one of the reasons why I don't like that Google included these developer options pre-installed on this phone. They're developer options for a reason, we can install them if we need to.
This feature is designed so that developers can test their app to be sure that data is properly saved when is no longer in the foreground. For example, if a user receives a phone call or jumps to another app, the app needs to do what is necessary to save it's data. At times, Android can kill a process in the background. If the user plans to go back (perhaps they finished the phone call), they want to see what it is they were working on last. The developer is supposed to handle this case by rebuilding everything as it was before (to provide that seamless experience for the user when switching between apps).
This debug feature helps us test that it works.
For the average user, all you're really more likely to do is slow down your apps. As they will have to rebuild themselves when you resume them, and you may even open yourself to more quirky bugs (for those apps that didn't properly test the above scenario).
So please don't enable it unless you're doing it for development purposes. My 2 cents.
*EDIT* Here's a page from the Android Dev Guide justifying my explanation:
http://developer.android.com/guide/developing/debugging/debugging-devtools.html
Immediately destroy activities
Tells the system to destroy an activity as soon as it is stopped (as if Android had to reclaim memory). This is very useful for testing the onSaveInstanceState(Bundle) / onCreate(android.os.Bundle) code path, which would otherwise be difficult to force. Choosing this option will probably reveal a number of problems in your application due to not saving state. For more information about saving an activity's state, see the Activities document.
Click to expand...
Click to collapse
(and yes, they used to call it "Immediately destroy activities")
Thanks. I turned it off. Did notice some bugs while on. I just wish with 1GB of RAM the launcher wouldnt have to reload. Hopefully things get better. Might just be my apps but it happens quite often when leaving the browser.
Sent from my Galaxy Nexus using xda premium
mobilehavoc said:
Thanks. I turned it off. Did notice some bugs while on. I just wish with 1GB of RAM the launcher wouldnt have to reload. Hopefully things get better. Might just be my apps but it happens quite often when leaving the browser.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
weird.. how many widgets do you have on your launcher? the more widgets you have, the slower the launcher is.
Have you tried another launcher? The stock launcher has never been known for being fast and efficient, although I haven't had any issues with it (whereas I'm a LauncherPro fan on my other devices).
kwazi said:
weird.. how many widgets do you have on your launcher? the more widgets you have, the slower the launcher is.
Have you tried another launcher? The stock launcher has never been known for being fast and efficient, although I haven't had any issues with it (whereas I'm a LauncherPro fan on my other devices).
Click to expand...
Click to collapse
I have quite a few Widgets but nothing too crazy I don't think. I use LauncherPro on my other devices as well but I love this new launcher so I'm going to stick it out. Like I said the most common task that causes the issue is when I'm using the web browser and then come out of it. Otherwise its been stable. I've noticed the same thing with Honeycomb on my Xoom so it might just be one of those things I have to put up with.
Sent from my Galaxy Nexus using xda premium
i'm also noticing some redraw and occasional lag when hitting the home button.
I'm hoping that CM9's custom launcher will have an option to lock it in memory- that may increase the performance by a lot.
also when replacement launchers like go launcher start optimizing more for ICS those might be good options.
Have you tried converting your launcher into a system app? You'll need to use Titanium Backup Pro or something similar to do it for you, or simple copy the APK into your system/app folder... Really sped up my launcher!
shawnshine said:
Have you tried converting your launcher into a system app? You'll need to use Titanium Backup Pro or something similar to do it for you, or simple copy the APK into your system/app folder... Really sped up my launcher!
Click to expand...
Click to collapse
Did you see the date on this thread, almost 8 months old
Sent from my Galaxy Nexus using xda premium
95Z28 said:
Did you see the date on this thread, almost 8 months old
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
... and yet people still continue to discover the thread and benefit from it.
Thanks for clarifying the meaning of "Don't keep activities"
my razr xt910 cannot be counted upon to run smoothly with all the apps simultaneously running and forcing itself to go into reboot. i then fancied an iPhone single styled system (as compared to Android multi-talks) cuz iPhone looks robust and responsive. all the killer that claimed to do the job looked more of a farce and then when i stumbled upon the destroy activity i was like OMG. srsly b4 using it I've only got just inner 100mb of ram, after using it i have a whooping 400mb ram. UI appears faster and all. regarding the relaunching of apps and battery life being used up. i think I'll start to worry about it on a later date. what say any body. ooh yes to add on, even after i deleted 40 apps on my phone it still hanged like fcuked. i guess i can reinstall them back again and not have to worry about it. btw i can't seem to root my xt910 for nuts so i can't custom ROM it along with all other fanciful mods that i hear about what others did to their phones.
I found some articles on net talking about harmful influences when using task killers apps.
I'm using SlimICS at the moment and I want to know if when I use the killing button that I've added on my navigation buttons harms my phone as the task killers do..
Sent from my Galaxy Nexus while relaxing..
Don't kill apps unless you have a misbehaving one that's adversely affecting your phone.
The OS can manage apps and memory so much better than you ever could.
martonikaj said:
Don't kill apps unless you have a misbehaving one that's adversely affecting your phone.
The OS can manage apps and memory so much better than you ever could.
Click to expand...
Click to collapse
Just to add: If you have a misbehaving app, don't bother killing it. Just uninstall it. It's not worth the trouble.
These task killers and memory optimizers are really good for lower end devices that have little memory. I used them on a phone that only had 356MB of RAM and only run at about 30-40MB free. A better way to address these issues is to run the V6 Supercharger script on a rooted device.
As for the GNex, why do you need to run task killers? You're not having memory performance issues, are you?
netbuzz said:
These task killers and memory optimizers are really good for lower end devices that have little memory. I used them on a phone that only had 356MB of RAM and only run at about 30-40MB free. A better way to address these issues is to run the V6 Supercharger script on a rooted device.
As for the GNex, why do you need to run task killers? You're not having memory performance issues, are you?
Click to expand...
Click to collapse
Yep. On my old ZTE Blade I really did feel a significant difference in smoothness after killing off some apps, so I don't entirely agree with the notion that you should never ever even consider doing it (which seems to be what some people advocate), but on the GNex there doesn't seem to be a need for it unless a specific app is misbehaving. I don't know if that's just because of the more powerful hardware or if it's also because of the much improved OS (I imagine it's both), but there you go.
JaiaV said:
Just to add: If you have a misbehaving app, don't bother killing it. Just uninstall it. It's not worth the trouble.
Click to expand...
Click to collapse
This. I use watchdog to monitor rogue apps. Engadget was s repeat offender so it had to go.
As mentioned the OS does a great job on its own.
Sent from my Galaxy Nexus using Tapatalk 2
You need nothing more than to swipe apps away when you're done with them in the multitasking window, which doubles as a task manager of sorts.
Sent from my Galaxy Nexus
MikeyMike01 said:
You need nothing more than to swipe apps away when you're done with them in the multitasking window, which doubles as a task manager of sorts.
Click to expand...
Click to collapse
Again, why even bother? The OS handles this just fine.
Although, that doesn't necessarily "kill" background apps. There is a box in "developer settings" that, if you check it, will kill any application after using it. I haven't tried it out but it may just work.
Sent from my GummyNex!
LocoTSX said:
Although, that doesn't necessarily "kill" background apps. There is a box in "developer settings" that, if you check it, will kill any application after using it. I haven't tried it out but it may just work.
Sent from my GummyNex!
Click to expand...
Click to collapse
I'm pretty sure that's as bad as using a task killer.
Sent from my Galaxy Nexus using Tapatalk 2
Ntavelis said:
I found some articles on net talking about harmful influences when using task killers apps.
I'm using SlimICS at the moment and I want to know if when I use the killing button that I've added on my navigation buttons harms my phone as the task killers do..
Sent from my Galaxy Nexus while relaxing..
Click to expand...
Click to collapse
even cyanogenmod has a kill app button, i dont think it does anything to your phone.
IMO the only useful reasons to kill a background app are if it's wasting your battery, bandwidth, or it's some kind of logger. In those cases you're better off just uninstalling it. Android is designed to keep things in memory to save start-up time and related battery drain, and so you have the benefit of the task-selector button. It knows when to clear enough memory to keep your foreground app and you happy. Task killers are holdovers from the days when they were useful.
galaxy nexus (gsm) / cm9 / trinity @ 1.4GHz
I learned a long time ago that in Android/Linux free RAM is wasted RAM.
Sent from my Galaxy Nexus using xda premium
Ics/jb does not need app killers if you press the recent app key and swype it left or right the app gets killed
Sent from my GT-N7000 using xda premium
martonikaj said:
Again, why even bother? The OS handles this just fine.
Click to expand...
Click to collapse
No, not really. And if it were "bad" they wouldn't put it into Android. You should swipe them away when you're done with them.
I Am Marino said:
I'm pretty sure that's as bad as using a task killer.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
There's nothing bad about closing apps you're done with.
What's bad is the auto task killers.
Sent from my Galaxy Nexus
MikeyMike01 said:
No, not really. And if it were "bad" they wouldn't put it into Android. You should swipe them away when you're done with them.
Click to expand...
Click to collapse
No it really does nothing positive to swipe apps away when you're done with them. As the poster a couple above me said, free RAM is wasted RAM. The OS will keep everything in order. You're unnecessarily micromanaging your apps when you swipe them away. Your phone just works harder and for longer re-opening apps over and over again when you kill them manually.
Your RAM is powered and draining battery whether its full of apps or not. It's in your best interest to let the OS fill up your RAM (all the way up to about 90% full) and let it kill things as necessary when you load an app that needs more than is available. The OS will handle it. I know everyone has it engrained in their minds from using Windows for so long to keep as much RAM free as possible, but its just not the case in Android anymore.
martonikaj said:
No it really does nothing positive to swipe apps away when you're done with them. As the poster a couple above me said, free RAM is wasted RAM. The OS will keep everything in order. You're unnecessarily micromanaging your apps when you swipe them away. Your phone just works harder and for longer re-opening apps over and over again when you kill them manually.
Your RAM is powered and draining battery whether its full of apps or not. It's in your best interest to let the OS fill up your RAM (all the way up to about 90% full) and let it kill things as necessary when you load an app that needs more than is available. The OS will handle it. I know everyone has it engrained in their minds from using Windows for so long to keep as much RAM free as possible, but its just not the case in Android anymore.
Click to expand...
Click to collapse
Whatever you want to believe. I'm not going to waste my time on convincing you.
Sent from my Galaxy Nexus
MikeyMike01 said:
Whatever you want to believe. I'm not going to waste my time on convincing you.
Click to expand...
Click to collapse
Hah alright.
Android is praised for having 'real' multitasking. But why does it have to 'suck' on a phone with 1GB memory?
Chrome starts to reload 3-4 tabs only if it's the only app 'opened' (of course there are other background services. but I don't have much running services, map, google messaging service, keyboard, )
I think it could also be problem with app. app not releasing memory resource when goes to background.
But it's really annoying to see that apps activity needs to be created again from scratch after opening a few apps.
Please discuss your opinion here.
Bayint Naung said:
Android is praised for having 'real' multitasking. But why does it have to 'suck' on a phone with 1GB memory?
Chrome starts to reload 3-4 tabs only if it's the only app 'opened' (of course there are other background services. but I don't have much running services, map, google messaging service, keyboard, )
I think it could also be problem with app. app not releasing memory resource when goes to background.
But it's really annoying to see that apps activity needs to be created again from scratch after opening a few apps.
Please discuss your opinion here.
Click to expand...
Click to collapse
No problems here..
try to avoid apps with high memory usage, one being the Facebook app
crixley said:
No problems here..
try to avoid apps with high memory usage, one being the Facebook app
Click to expand...
Click to collapse
I don't have facebook running as I've said earlier. I don't even have it installed.
But I"m still not convinced that it's the BEST android multitasking could have. it's too aggressively killing background activity..
Bayint Naung said:
I don't have facebook running as I've said earlier. I don't even have it installed.
But I"m still not convinced that it's the BEST android multitasking could have. it's too aggressively killing background activity..
Click to expand...
Click to collapse
Get autokiller from the market and adjust the settings then. You want lower numbers in the app to allow more applications to stay active. Note that some apps might just kill background memory use, there's nothing you can do about that one.
Doing this might make your phone more laggy. You need to decide for yourself what the best trade-off is for you.
When exactly does it do it? I have 5 tabs open and I'm good! Is it after a while of inactivity?
Sent from my iPad using Tapatalk HD
I have never noticed this issue.
Sent from my other android devive using Tapatalk 2
z06mike said:
When exactly does it do it? I have 5 tabs open and I'm good! Is it after a while of inactivity?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
It's not a refresh (like refresh web page), I think it's just re-rendered from the cache..
even though I'm android fan, I'm jealous how iOS manage to run pretty well for daily use with 512MB... probably dalvik JIT is culprit here?
I personally think this is a problem with chrome and this is the reason I don't like chrome because it runs a constant large service at 70+ mb at all times which takes away from general multitasking of the phone. My guess is this is related to your problem. Persistent services on android are rather powerful and when one is too large it has detrimental effects. Maybe others don't experience this with chrome, but I did, and that's why I stopped using it.
Yes, chrome is worse than stock browser.
Stock can maintain usually 4-5 tabs easily without reloading.
Hopefully Google could do something with both chrome and improve OS multitasking capability.
Hello everyone,
By reading your helpful posts, I have rooted my Xplay, removed all the bloatwares, installed Link2SD and Autostarts.
This way I've been able to save lots of ram and my Play starts really quickly and has improved its performances.
However,
however,
however...
This bloody facebook won't stop launching by itself: task killer cannot handle it, Autostarts cannot manage to prevent it from starting by itself. Went into the settings of the app to remove all notifications, but still, it's always there, in the running programms, taking between 20 and 50mb of precious RAM.
I suffer randomly from lags in demanding games and I suspect that's because of Facebook working in background...
Do you have another solution than simply removing it? Indeed, Xperia play is a great gaming device indeed, but it's also a great smartphone, and I want to enjoy it with its full potential. Facebook is part of it and the official app offers more possibility than the non-official ones, usually limited to some basic options.
I just want it to stay closed until I decide to launch it and use it by myself... And not in my back...
Thanks for your help!
Uninstall Facebook.
Use site on mobile or on pc.
May sound "stupid", but its the best way
Sent from my Xperia Play using xda app-developers app
To be honest the official facebook app for our phones is rubbish, Constant pointless updates what don't fix any bugs, eats up your phone memory plus ram,
Just remove it with X-plore if you have Root
Sent from my R800i
Or try autostarts it's an app that lets u disable apps...im testing it at the moment with facebook
Just download romtoolbox, go on autostart and disable it
Actually, I've disabled Facebook and its extensions with Autostarts, but still, it remains and continues launching automatically! So I've just frozen it with link2SD and installed Friendcaster instead. So annoying!
cippi21 said:
Or try autostarts it's an app that lets u disable apps...im testing it at the moment with facebook
Click to expand...
Click to collapse
Does this app work with non rooted phones?
Sent from my R800i using xda premium
Very freakin' simple. FREEZE IT.
I easily get near 200MB+ free RAM with FB frozen.
Use the mobile site via your browser instead. It's way better and faster anyway.
Growling Clover said:
Does this app work with non rooted phones?
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Nope
Looking for a App that does as above without taking up much memory in the background whilst doing so. I trialed Smart Booster app and it allowed me too disable auto start for apps I don't need and hibernate others etc but sorta felt like the app itself drain my battery just as much as the apps that were auto starting. Thanks in advance
It's not free, $1.49. But it's worked for me in the past. Personally don't think it will be very useful on this device.
https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts
illmatters said:
Looking for a App that does as above without taking up much memory in the background whilst doing so. I trialed Smart Booster app and it allowed me too disable auto start for apps I don't need and hibernate others etc but sorta felt like the app itself drain my battery just as much as the apps that were auto starting. Thanks in advance
Click to expand...
Click to collapse
Why do you want free RAM? Free RAM is wasted RAM. Android doesn't need you to constantly clear the RAM. It's actually bad to do that because you need to use more CPU power to recompile the whole app when you open it again until we fully switch to ART which pre-compiles all apps.
Also Android by design will dynamically close apps to make room if it needs more RAM than you have available. Plus not clearing it will safe battery because the CPU will run less cycles when you use apps.
That's just my opinion, however I'm sure you have a reason as to why you wan to clear the RAM. I just thought it was with mentioning the above in case you didn't know.
Pilz said:
Why do you want free RAM? Free RAM is wasted RAM. Android doesn't need you to constantly clear the RAM. It's actually bad to do that because you need to use more CPU power to recompile the whole app when you open it again until we fully switch to ART which pre-compiles all apps.
Also Android by design will dynamically close apps to make room if it needs more RAM than you have available. Plus not clearing it will safe battery because the CPU will run less cycles when you use apps.
That's just my opinion, however I'm sure you have a reason as to why you wan to clear the RAM. I just thought it was with mentioning the above in case you didn't know.
Click to expand...
Click to collapse
Reason = Battery Drain. I don't use the Radio, EVER. So why is it showing in android os in the battery settings? Just like quite a few other processes sitting in that long ass list. That's why I ask.
illmatters said:
Reason = Battery Drain. I don't use the Radio, EVER. So why is it showing in android os in the battery settings? Just like quite a few other processes sitting in that long ass list. That's why I ask.
Click to expand...
Click to collapse
Why don't your freeze them with titanium backup if you are rooted?
Pilz said:
Why don't your freeze them with titanium backup if you are rooted?
Click to expand...
Click to collapse
Might just do that, thanks. I see LG Suite is using a lot. I dunno why though, that's fine If I freeze also? Requires $5.99. Gonna have to deal with it for a while, ive donated over $30 just today..
illmatters said:
Might just do that, thanks. I see LG Suite is using a lot. I dunno why though, that's fine If I freeze also? Requires $5.99. Gonna have to deal with it for a while, ive donated over $30 just today..
Click to expand...
Click to collapse
There's a free version if the app that allows you to freeze apps still, but it won't let you do batch operations if I remember correctly.