Related
Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
gupta.anurag08 said:
Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm running on the Advanced Task Killer, I do not have any issues with them. What's your problem?
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Yeah, ATK is the best task killer app I've been using
gupta.anurag08 said:
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Click to expand...
Click to collapse
It is because different task killer have different security policy, which allow them to show the system apps or not. So, in the lower security policy, you can see more running apps and gain more memory after kill them
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Nope, that is the reason why i have to use task killer
For me, it help me save much of battery
Since I stopped using a task killer my battery is better.
Don't use a task killer for a week and watch the difference.
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
yes and yes!
if your phone requires the resources, it will kill tasks that are no longer required. its all automatic. let it do it itself and you will have a much happier phone
AND better battery life, because the android OS is not continually restarting processes that your task killer deems unnecessary. I would trust the actual OS over a 3rd party app. It is designed that way for a reason (see my previous post).
mrtim123 said:
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
Click to expand...
Click to collapse
The idea is absolutely right if memory is being used for apps you are likely to open frequently. ATK allows you to unselect the apps you want to keep running. That way you can unselect the ones you use the most and then use the widget to kill everything else.
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
There are advantages in both approaches and I find a mixed combination (available with ATK) makes it best, although the user need to use some common sense to do it right. Killing everything means the system will be more responsive but regularly used apps will take longer to start up. Not killing means the apps you use a lot "startup" faster when you use them repeatedly (as in fact they never stop running) but after a bit the system will lag when using other apps and may need to use pagefile/swap to atone for the lack of free RAM. That causes page faults which make the system even slower.
The iphone developers aren't complete idiots for killing every app. They have a priority for system responsiveness and they did achieve it at the cost of background running apps. I like the possibility to choose what I want to keep running and kill the apps I'm not likely to use again and it's one of the reasons I picked android.
A little Offtopic to both ifanboys and ihaters:
I never owned any apple product as I think of them as over priced. That said I think the iphone has great merit and I doubt very much we would have Android if the iphone didn't pave the way. Besides I jailbreak my brother's 3G and made it multitask enabled. Now it runs apps in background and there is little diference between it and my android. Except for the extra 200€ it cost, the lower hardware specs and expensive service provider contract my brother pays for a mandatory 24 months, while my X10 cost ~65% initially and came free of any contract.
well said, PCO
pco.vaz said:
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
Click to expand...
Click to collapse
Thats what I and others have found, which is why some people choose to use one, myself included. Someone posted a link to an article last week with similar information posted here about the OS handling itself, but the comments section of the article were full of comments similar to what pco and myself have said, so it's all down to personal preference whether or not you choose to use one.
I did use a task killer for a while, then stopped. Personally my phone is better without. I have nothing except weather that updates automatically, I do it manually when I need it.
It is one of those things, just like on a laptop, everyone has different configurations and usage patterns that results will vary.
Sent from my X10i using XDA App
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
gavriel18 said:
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
Click to expand...
Click to collapse
The browser for instance doesn't. Same with many other. I think it's up to each individual developer to program that behavior for his app.
I got Visual task switcher and I notice lots of apps just stay running forever.
Task killer caused probs for me. A daily switch off doesnt hurt, but have run mine for 7 days and been ok. Even a bberry cant do that!
Sent from my X10i using XDA App
Guys, don't use home button to exit apps.
Will just send them in background.
Use the back button... this won't exit (most of) the apps but will put them in a "sleep" state so, next time when you will use it, it will load faster.
So, again, home button will put the app in background, still running.
Test it with an audio player for ex.
Or a browser... send it in background with home button and the player will still play or the browser will still have that page loaded.
With back button, after all views are "closed" the app will close too (well, put in sleep state).
I use ATK only to kill the apps i use once in a while ... the rest of the stuff, is always in memory.
My X10 has usually about 25Mb free
Actually I used ATK to kill application that need to connect to internet, and in my case there is extra charge payment. But after i used ATK I don't notice that the battery live is longer. So I ever ask someone in my thread about after ATK kill applications and so forth....
And somebody told me to quit using ATK and now I realize that the battery last longer than before.
But one thing still bother me is:
Setting - Wireless control - mobile network - mms & data (no checklist)
means: I can not access internet and receive or send mms either.
Actually I only need MMS, not internet.
May be somebody can help me solve this problem.
Thanks.
But my conclusion:
NO NEED ADVANCE TASK KILLER.
After I uninstall ATK, my phone still running smooth and the battery last longer.
May be we just need best Cache cleaner. But I still trying some of that.
@pco.vaz
I don't want to be mean, but you are wrong.
Even those iOS versions that are not multitasking enabled keep apps in memory. Leaving an app on an iPhone resets its UI state and halts its processes, but parts of the app are left in the memory. You can see the difference in loading speed if you decide to reopen it.
There were apps that could show memory usage and clean it on the App Store, but Apple removed them. You can still get them through Cydia and see for yourself how memory management on iTouch devices actually works. Basically the iPhone goes as low as 3-4 megs of free memory and handles it in smiliar way as Android.
On both Android and iOS, apps that are in background are paused after a while and do not use processor cycles. Memory they keep occupying is overwritten if needed by another process.
I do not recommend using task killer to people who do not know what they are doing exactly. Killing even simple processes often causes phone instability and drains battery faster, as others have already said.
If you feel your phone is stalled, perform a simple reboot. There are apps that run in background (in most cases you are warned about this) or are poorly coded that could cause this behavior. Other than that, inbuilt application manager is able to force close apps pretty well, if you need to kill a single app causing problems
Is Autokiller Memory Optimizer still relevent? I first learned of it in KaosFroyo v36? I think?
I realize it is not a "killer" the same way most task killers are, and it just adjust the limits of the actual systems ram limits. I am familiar with the way linux handles memory but with newer roms and newer versions of cyanogen coming has anyone noticed a difference with or without it? I will freeze it tonight and see if I notice anything.
I quit using it when I switched to Gingerbread. Don't need it. With Froyo I felt it was necessary.
Sent from my GSBv1.9 ERIS using XDA Premium App
I still use it. Why? Because even with gingerbread there's an obvious difference in available memory with and without it. My memory improves on average 20mb with it vs without it (just random checking it). now I realize that can hurt or help (having something already running in the background serves its purpose for quick access. too much stuff running you used and are NOT going to access anytime soon hurts). overall I havent noticed it hurting performance/speed at all and I'd rather have the free space available for operating apps so I use it. less things running even in background should at least theorically help battery life a little. I dont think its NEEDED by any means but the way I bang app after app it works for me.
I still use it because I've used it since KaosFroyo, and so on the move to GSB I couldn't help but continue to use it. Sometimes it really does help, and sometimes it doesn't make a difference.
I've uninstalled it two days ago. Haven't noticed a difference at all. I've been using GingerTazz12. cm7/2.3 has better built in memory management?
winchendonsprings said:
I've uninstalled it two days ago. Haven't noticed a difference at all. I've been using GingerTazz12. cm7/2.3 has better built in memory management?
Click to expand...
Click to collapse
2.2 definitely has better mem management over 2.1, and 2.3 has even better over 2.2.
Memory Managers are a placebo to me. Why not just let your phone manage things on its own? It's not based on Windows where RAM is key in performance, it just simply knocks out the things you haven't used in a while to give it more room for the next program.
It will really effect your "multitasking" ie switching between apps, because there will be memory left over, just not for the app you just finished using
willwgp said:
Memory Managers are a placebo to me. Why not just let your phone manage things on its own? It's not based on Windows where RAM is key in performance, it just simply knocks out the things you haven't used in a while to give it more room for the next program.
Click to expand...
Click to collapse
The thing is, some of those background apps still running could be poorly optimized and still take CPU and not just RAM. You could be using an app and be good on memory, but you could have some background app taking resources and CPU cycles and possibly slowing your phone down in that manner, as well as draining your battery a bit more than usual.
i havent used it at all and im running gtood gsb2.0
I haven't used any memory optimizer/task killer since the first time I tried xtrSENSE, probably last July. zach.xtr includes scripts for GScript to change Android's built in memory manager settings, although I've since stopped changing any ROMs defaults as far as that's concerned.
I decided to not install any mem managers, autokiller & startup auditor, when I moved to GSB from xtrROM. At this point I feel I don't need autokiller at all. Startup Auditor maybe, but the few that do startup on their own are not causing issues. To me AK has become an option, NOT a necessity!
Sent from my ERIS GSBv2.1 using XDA App
Is there any other system besides minfree, which frees up memory in android? Have strange behavior of FBReader, which I set to OOM -17 (both processes), chmod to r/o oom_adj files to force it to stick and still cant hold it in memory. It seems to me, that after some time when I dont use phone (hour or two) it is just released and starting again instead of just resuming from memory. If I try to force FBR from memory just by running many other programs, it sticks there no problem. I can run everything it never happened to me that FBR is released and starting again. But when I sleep phone ane leave it, then after some unpredictable time, FBR (and other apps) are just released and starting again. It seems to me, that there is running other process, which just releases apps in Empty app state. Or maybe there is some timeout for empty app, which is then automaticaly ended?
I'm using Nik3r EX8 kernel with 192mb swap enabled, latest viper rom.
Wlk said:
Is there any other system besides minfree, which frees up memory in android? Have strange behavior of FBReader, which I set to OOM -17 (both processes), chmod to r/o oom_adj files to force it to stick and still cant hold it in memory. It seems to me, that after some time when I dont use phone (hour or two) it is just released and starting again instead of just resuming from memory. If I try to force FBR from memory just by running many other programs, it sticks there no problem. I can run everything it never happened to me that FBR is released and starting again. But when I sleep phone ane leave it, then after some unpredictable time, FBR (and other apps) are just released and starting again. It seems to me, that there is running other process, which just releases apps in Empty app state. Or maybe there is some timeout for empty app, which is then automaticaly ended?
I'm using Nik3r EX8 kernel with 192mb swap enabled, latest viper rom.
Click to expand...
Click to collapse
You`ve probably already heard this but android will automatically free up ram by killing of the launcher/system processes as a user app draws more ram, if you run out, android will kill the app using the most ram, usually the app you are trying to use hence crashing/stopping. You can tell if something is using too much ram when the launcher/Htc Sense frequently reloads. If you experience this flash the 256mb swap. Leave minfrees as stock, that way multitasking will actually work (with swap mod). If that doesn`t work, ARHD 6.5 has an enhance multitasking tweak in aroma, download the rom, unzip and in the aroma or extra folder just extract the mod and copy to your phone using root explorer.
I use the ultimate minfree setting in Viper settings, you have to disable usb debugging in developer settings for this to work i read somewhere, restart once set.
-smc
ryanjsoo said:
You`ve probably already heard this but android will automatically free up ram by killing of the launcher/system processes as a user app draws more ram, if you run out, android will kill the app using the most ram, usually the app you are trying to use hence crashing/stopping.
Click to expand...
Click to collapse
Sure, this is Minfree proces, but my problem is bit different. It seems to me, that system has enough ram and allows me to run quite a lot of apps without forcing my FBReader out of memory - when I try in one session. I even set FBR to have OOM value -17, which should force Minfree to ignore this process completely, same as it should do for launcher. But as soon as I leave phone for some time in sleep mode, there seems to be some other mechanism besides Minfree. And this one kills my app - and I dunno why and what is it...
somemadcaaant said:
I use the ultimate minfree setting in Viper settings, you have to disable usb debugging in developer settings for this to work i read somewhere, restart once set.
Click to expand...
Click to collapse
Trying to restart, because I set it without it before, but it didnt hold after phone wake up - already reported this in Viper thread. Lets see if it gets better with reboot - and it doesnt. You can easily check in adb shell by running
Code:
cat /sys/module/lowmemorykiller/parameters/minfree
Minfree is reset every time you sleep/wake up phone...
I confirm the problem.
Whichever ROM I use, I can hardly reply SMS/Whatsapp without loosing Browser or CoolReader.
Actually, I counted limit of 2 hot apps.
The scenario is:
1) I read a book or RSS-reader
2) I receive a text via SMS or WhatsApp
3) For answering I need a browsing for some fact-quoting. At the moment I open a browser, the first application (Book or RSS reader) is killed.
Scenario may vary, but when I open third app, the first one is killed for sure.
I tuned minfree as well, and detected that it is overwritten every reboot too. I usually have 160-200MB free of RAM, and minfree values, either mine (24MB) or default (80MB) are always lower than actual size of available memory.
I switched on "Developer mode" (touch 7 times something in About System. probably ROM version), and specified background limit "At most 4 apps" instead of "Standard limit" (unknown to me). It doesn't help either - third app kills the first.
And I never managed to obtain a solution.
Just adding my vote to the problem (thus bumping the topic).
I found an application named AutoKiller Memory Optimizer by which applying its tweaks It makes my phone more smoothly and saves my battery very well!
There are some reviews below links:
http://forum.xda-developers.com/showthread.php?t=622666
http://andrs.w3pla.net/autokiller
http://andrs.w3pla.net/autokiller/details
http://andrs.w3pla.net/autokiller/kernel
If anyone has installed this application plz give your opinion !
and why would you post it in Q and A ?
All these task killers are about the war on RAM.
We, the people who grew up using windows, have an inner belief that more free RAM equals to more speed.
The thing is that android is not windows but linux based, so the rules changes to the more RAM the better perfomance.
What dois this has to do with performance & drain?
Android would load apps before you try to open them, so when you finally do, it's already opened. Android doesn't have to work hence the battery doesn't have to gas it.
Sent from the little guy
gastonw said:
All these task killers are about the war on RAM.
We, the people who grew up using windows, have an inner belief that more free RAM equals to more speed.
The thing is that android is not windows but linux based, so the rules changes to the more RAM the better perfomance.
What dois this has to do with performance & drain?
Android would load apps before you try to open them, so when you finally do, it's already opened. Android doesn't have to work hence the battery doesn't have to gas it.
Sent from the little guy
Click to expand...
Click to collapse
I suggest to try it. you will find the changes i mean
Can't, already posted that these apps are crap.
Sent from the little guy
gastonw said:
Can't, already posted that these apps are crap.
Sent from the little guy
Click to expand...
Click to collapse
It's not a regular task killer such as advanced task killer or easy task killer. It's more different.
Really, what does it do?
Sent from the little guy
gastonw said:
Really, what does it do?
Sent from the little guy
Click to expand...
Click to collapse
It's not a task killer. It's an app that modify your lmk and add some tweaks. But you can kill some apps from this app too.
First Plz read reviews in first post and also these two reviews:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Releasing RAM With Autokiller Memory Optimizer
Have you ever wished to speed up your Android, but now known how? Have you tried task killers, but found it hard to tell whether you made an improvement? In this post, we’ll look at Autokiller Memory Optimizer, an app that gives you more control over how Android releases its system resources.
“You shouldn’t be using a task killer with Android” clearly explains why the task killers are not a good solution to fasten up your system in the Android interface. Briefly, we might say that the reason that task killers are no good for Android is that the same system regulates itself for releasing RAM memory. Process are not killed when you close the app; instead the process stays open until the system itself realizes it needs more memory to run a new process. This way, you can actually gain some speed when you restart the app, as its resources may still be in memory.
Just like a computer, a smartphone uses Random Access Memory (RAM) for processing the functionality of softwares and apps. When you are running low on RAM, your phone will start to slow down, because it needs more memory than is available. As a solution to this problem, Android devices has an autokiller that automatically shuts apps down when the memory used is close to the limit. Obviously this limit depends on the capabilities and configuration of your phone.
If you root your phone (and I totally recommend you to do that) you can use apps for changing your system parameters like the RAM auto killing. One of this apps is Autokiller Memory Optimizer available on the Android Market.
As the developer says: “AutoKiller Memory Optimizer is designed to fine-tune Android system’s inner memory manager routines to keep your device fast and smooth. It also features a full-powered process manager which lets you control your whole system.”
Warning: Messing around with system configurations like this is potentially dangerous to your phone, and not for the faint-hearted! Check out our other How To articles for safer tips on improving performance.
Going for It
The system itself divides the process into six different types, and here’s where it gets technical. The six types are as follows.
FOREGROUND_APP: This is the process running the current foreground app. We’d really rather not kill it! Value set in system/rootdir/init.rc on startup.
VISIBLE_APP: This is a process only hosting activities that are visible to the user, so we’d prefer they don’t disappear. Value set in system/rootdir/init.rc on startup.
SECONDARY_SERVER: This is a process holding a secondary server — killing it will not have much of an impact as far as the user is concerned. Value set in system/rootdir/init.rc on startup.
HIDDEN_APP: This is a process only hosting activities that are not visible, so it can be killed without any disruption. Value set in system/rootdir/init.rc on startup.
CONTENT_PROVIDER: This is a process with a content provider that does not have any clients attached to it. If it did have any clients, its adjustment would be the one for the highest-priority of those processes.
EMPTY_APP: This is a process without anything currently running in it. Definitely the first to go! Value set in system/rootdir/init.rc on startup. This value is initialized in the constructor, careful when refering to this static variable externally.
For every type of app, the system has a limit of pages (1 page=4 kilobytes) predefined. Autokiller Memory Optimizer allows you to modify this.
For the changes you can make you have the freedom to set as you wish, but there is a lock on the three first types of apps (this can be removed in the Preferences tab) and there isalso a list of presets configuration as follows (the numbers corresponds to megabytes remaining before shutting apps in the last 3 types of apps): Moderate (30, 35, 40), Optimum (40, 50, 60), Strict (60, 70, 80), Aggressive (82, 90, 98), Extreme (150, 160, 170), Ultimate (200, 225, 250) and (a wink from the developer about the TV series) Lost (4, 8, 15, 16, 23, 42).
Autokiller presets
Within these presets, you should try different ones, because every phone has its own RAM capacity and it would not be a good idea to set a killing parameter that is very close to your RAM total capacity as your phone would be killing apps constantly and you wouldn’t be able to use it at all.
Processes list
The app also categorizes the running apps in the six types and you can kill them manually for RAM release in the tab processes and the same occurs with the services in the current tab.
Services list
This app has also a donate version with some more features like the Chuck Norris mode when you can configure the app to use aggressive killing to release memory. It also gives the ability to set a different preset when the screen of the phone is off (this is very useful because when the screen is off you do not need memory to run new apps, but it still consumes battery).
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Tweak your system thanks to AutoKiller Memory Optimizer
Summary
Relax, I’m not trying to fool you into thinking that a task killer is really a tweak. Don’t be fooled by the ‘AutoKiller’ part of the app’s name, focus on the other words instead, because AutoKiller Memory Optimizer will allow you to fiddle around and make a few adjustments. Read on and find out what kind of adjustments I’m talking about, and whether the app is worth your time.
Features & Use
AutoKiller Memory Optimizer is there to help you bring your system up to par by conducting a bit of fine tuning. The app comes with a task manager. Use the task manager to get rid of lagging processes, the logic behind this being that if you’ve got something running that’s not really doing anything useful, but does consume 98% of the CPU as well as a hefty chunk of memory you should really unload energy hoggers. Your system will thank you by running smoothly. The task manager also displays the oom_value for ever app—more details below.
The app allows you to regulate the settings for the OOM killer, the automatic killer integrated in every Android device whose role it is to create more memory space wherever possible. As you know, in the Android world applications are never halted or shut down, they are merely rendered inactive—until the memory pipes up and the Out Of Memory Killer rears its head. But when does memory shortage become critical? And who decides which apps should be banished, and when should this occur? If you want to make these types of decisions yourself take a look at AutoKiller Memory Optimizer.
Android divides running apps into six categories ranging from the app that you’re currently working with to ‘empty apps’ (i.e. apps that you left by hitting the back button at some point). Once RAM space becomes too low the OOM killer will start by banishing said empty apps, and, if need be, continue working its way up. AutoKiller Memory Optimizer lets you decide how much free RAM space is required for your device run smoothly. There are different presettings to pick from (‘moderate’, ‘aggressive’, etc) and you can check out the developer’s website to read up on user experiences.
Bottom line:
AutoKiller Memory Optimizer affords you easy access to essential systems settings, allowing your Android to perform as optimally as possible. How essential this kind of app is is contingent on lots of factors: which device you’re working with, how good the manufacturer’s presettings are and what can be done to adjust them.
Screen & Controls
AutoKiller Memory Optimizer is set up in a very logical way. While high skilled, expert knowledge of Android isn’t essential in order to get the best performance out of the controls, it doesn’t hurt to have some experience. You can find in depth information and details regarding the settings options on the developer’s website, which means that you really don’t need much background knowledge in order to get something out of this app.
If you have a bit of experience you will find that the app’s controls are intuitive; if you’ve never worked with tweaking before I recommend that you give this app a miss.
Speed & Stability
AutoKiller Memory Optimizer is fast, stabil and dependable. I’ve been using the app for just over a month and it hasn’t crashed once so far.
Yada yada, that app tells android how to behave.
Custom kernels do that as well, so there you have it
Sent from the little guy
gastonw said:
Yada yada, that app tells android how to behave.
Custom kernels do that as well, so there you have it
Sent from the little guy
Click to expand...
Click to collapse
Lol yes, the more ram android uses the better performance BUT it makes most apps to run and remain active in the background using valuable memory which I might need for something else, for example something like a HD game like NOVA 3, and battery life does increase because active app = active CPU = battery drain.
Sent from my GT-I9100 using xda app-developers app
Hello world,
I have been using several ROMs for my 16GB Nexus 4 and I have a complain about RAM usage: it is never close to its full potential.
I did the following experiment: I opened up lots of apps(dialer, messaging, browser, facebook etc) not very demanding the ram usage was about 50-60% and most of the apps were loaded in RAM as there was no latency in switching between them. The I've opened up GTA 3. And the RAM usage was barely around 60-65%. Overall not much of an increase. I figured out that even though I had over 30% free RAM and android killed my other apps because even though they were in Recents it took the same time to open up.
So my QUESTION is: Is there any way to enable agressive multi tasking (90-95% ram usage) or a way to disable android task killimg mecanics in order to achieve a higher number of apps loaded in ram, therfore improving the overall speed?
Now I am running PSX ROM with S4 patch and Neo kernel
Peace
You can look into supercharging and adding swap or compcache/zram
Depending on how you use your phone will tell you if any of this will help or hinder your device
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
You can look into supercharging and adding swap or compcache/zram
Depending on how you use your phone will tell you if any of this will help or hinder your device
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the tips, but I want app switching to be fast, therfore no ZRam. As far as I know zram is slow virtual ram that allows many apps to stay in "memory" but switching to them is not fast. If I am getting something wrong, please tell me. Also I want to use the full potential of my RAM not having maximum 65% in high stress situations.
Try tweaking minfree values, google android ram minfree to get a better concept of it.
Basically its to adjust the number of pages at wich the system will start killing apps/processes with a given priority (foreground, background, services, system, etc).
dxppxd said:
Try tweaking minfree values, google android ram minfree to get a better concept of it.
Basically its to adjust the number of pages at wich the system will start killing apps/processes with a given priority (foreground, background, services, system, etc).
Click to expand...
Click to collapse
Higher minram=killing tasks much often, right?
DEV_Geek said:
Higher minram=killing tasks much often, right?
Click to expand...
Click to collapse
Yes, exactly that. So keep minfree as low as posible, but still give system core processes the priority. This way, ram will have to be really full (really low free ram) for apps to get killed.
dxppxd said:
Yes, exactly that. So keep minfree as low as posible, but still give system core processes the priority. This way, ram will have to be really full (really low free ram) for apps to get killed.
Click to expand...
Click to collapse
Will try soon. Thanks once again for helping a noob. I will keep you posted with the results.
Peace
dxppxd said:
Yes, exactly that. So keep minfree as low as posible, but still give system core processes the priority. This way, ram will have to be really full (really low free ram) for apps to get killed.
Click to expand...
Click to collapse
Didn't worked out quite well, all my minfree settings are below 6MB, but still below 1GB ram is used