Database Develop

Auto Memory Mangager

Not sure if you all are familiar with this app, I haven't seen anyone speak upon it on XDA yet, so just thought I'd share my experience with it.
http://www.androlib.com/android.application.com-lim-android-automemman-wBjq.aspx
IMO, this app is pretty cool. Very simple and easy to use, although it doesn't come with detailed instructions on how to use, so I felt the need to explain a little bit about it:
Tired of lags to and from Dialer/Contacts/Call Log?
Have you ever pressed the call button to dial a number/contact and nothing happens for 10 to 15 seconds then finally the call goes through and starts to ring?
Ever went back to home screen after fooling around with an app, or web surfing the browser only to find that a widget or two is missing or is not loading/refreshing properly?
Gmail not syncing daily as it usually does?
Market taking forever to load up the downloads page or lagging connection with G-talk to promptly start the download/updates you started?
Well these are the memory/background/content provider situations that need to stay snappy if nothing else does, agree?
Then this app may or may not be the answer to all of your problems.
For me it was. First and foremost, it is a FREE app, yay! (at least to my current knowledge, unless developer has changed it)
*FYI* This app does require root permissions, so if you are not rooted this will be of no use to you.
After installing, when first opening the app, super permissions should pop up, just check the always box and press allow for root access. Close the app, then re-open.
Now, there are 4 options you may choose, DEFAULT< CUSTOM< MILD< AGGRESSIVE
Default settings will be what you see on first use, those are the default Android memory settings for your G1
Custom- self explanatory, you move the bars of each memory category according to how you prefer- *Note* the amount shown is not exact memory, it is a threshold, basically a set amount not to exceed, Your phone will automatically choose how much to use according to how much it needs, but its limitations will be set by the threshold you choose. Go ahead and make your adjustments, then click the custom button, this will save these settings. So the next time you want to re-enter those settings, just hit the custom button, and it will restore.
Mild- Simply a preset application setting
Aggressive- Another preset app setting
You choose what works best for you, I would suggest playing around with different settings until you have achieved a memory usage that gives you the most improvement, *Note* Do note mistake this as a speed app, it only controls memory, so don't expect some super fast change, but if you set it up properly, and memory is being managed to the best case scenario of your usage, speed will increase, believe me.
Start with the presets, see how they work throughout the day, if you notice no difference, or worst than it already was, change it to something else.
Personally, my best experience has been with the Aggressive preset. Its been the most effective for my phone, however; this won't be the case for everyone. Aggressive basically raises the threshold for background data(widgets,home, cache, etc.) And content provider (google apps, settings, G-talk and stuff) And Empty application- this means, IMO, the amount of free memory sitting around available, for soon to come data or apps that you might open later, I.E.- multi-tasking, Call screen, new mms or sms
It also lowers the threshold of the foreground and running apps, so that they don't suck up so much memory the phone lags before it can open other things in memory. Get it? But as I stated, different people will have different preferences.
If you haven't already, try it out! If you don't like it, or don't need it...maybe results won't change things enough for you to have any use for it, you can always uninstall, and it won't harm any memory or data on your phone.
Also, regardless of threshold settings, if you open or use more memory than threshold limits, it will not break or crash you phone causing reboots or anything like that. So don't worry. The app does not prevent you from doing anything on your phone, it simply manages it according to your use.
I hope this comes in handy for someone, as it has been more than useful for me on a daily basis. You can find more information via market or the link above.

Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.

I could be wrong, but I believe the intent of this is to allow the Android internal memory manager to be tweaked so that certain applications/processes have a higher priority and remain in memory and those that you deem as "less important" are removed first.
Here is a thread on the Hero forum about it:
http://forum.xda-developers.com/showthread.php?t=622666
Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
With this App, I do not notice an increase in free (meaning useless) memory... I do notice that key processes that I deem important are still running on CM 4.2.14.1... Even after running many of the ~160 apps I have, including games...
Individual results may vary... Nobody runs the same exact configuration and apps on their G1...
L8r

@Ibcoder
That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it

Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
Click to expand...
Click to collapse
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.

I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).

TeeJay3800 said:
I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).
Click to expand...
Click to collapse
Ok, and I don't blame ya, that's how I test everything on xda, roms,apps, hacks, you name it....but only after I review enough good responses (preferably 3)
But on the contrary, there have been times that something was reviewed poorly, but after my own experience turned out to be great! You'll see that a lot in the android market as well, great apps with two star/3 star ratings all because some asshole didn't know how to use it, LoL
Try it dude, you got nothing to lose...won't break ya phone, but if ya want to play safe nandroid your current stuff first.

Klyentel said:
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.
Click to expand...
Click to collapse
As far as I know, they are pretty much the same... The XDA thread I mentioned above has both the Dev of the App you posted and the Dev of the App I posted... They both created one at around the same time... One with sliders and one with fields... The only difference I think is that AutoKiller uses a service to write the settings on a reboot...
Still playing with this to see if it makes any real difference... I know if I set the values too aggressive, then the browser reloads every time I come back to it...

I know if I set the values too aggressive, then the browser reloads every time I come back to it
Click to expand...
Click to collapse
yeah that has happened to me too.

The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
lbcoder said:
Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse

@dwang-agreed, as I stated @lbcoder, what he is saying is that the app holds everything in memory which slows down system, but it does not do that, and he implied that I stated it limited use of apps, which is incorrect, it does not operate as a limiter, or a kill switch, only a manager. Sort of like, organizing processes by priority based upon setting of threshold tolerance. Of course killing off unwanted apps and processes have to be done manually, via kill widgets or file explorers, When I first posted about this app I assumed that concept to be in mind of the reader....sadly I was wrong. I guess everything around here has to be put in perspective as if the reader knows nothing...sort of like an "101 handbook for Dummies" type thing.

What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Klyentel said:
@Ibcoder
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it
Click to expand...
Click to collapse

lbcoder said:
What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Click to expand...
Click to collapse
First and foremost buddy, I quite frankly don't give a dam how you spell your name with an "I" or an "L"
Secondly, what I am stating is not incorrect, and is possible, because I have the app, use it everyday, and does exactly what I said it does via OP. Thank you very much. If you disagree, then don't download the app. Simple as that.
or heres a better idea create one of your own. I will be more than happy to try it if you feel you can do better, but don't downsize the quality of this one, straying other users away from trying it, as it may be as useful to them as it is me. Got it?
Now get ya DREAM on...(with android that is )
and leave me alone.

[Q] Apps kept coming back after autokill -> memory leak -> lag

Hi all,
1. I've got these applications (Smartone-Vodophone SV app, 5 days weather, google map, social hub and such) that would keep coming back, relaunching themselves even after I put them onto my task manager's autokill list. Seems like they would wait around for me to enable the wifi/3G connection and then launch themselves. I even installed other apps to disable autolaunch and they would still launch themselves in the background every now and then. I had to kill them every time I unlocked my screen and these "launching and killing" cycles eventually depleted my memory down to below 100MB, making the lag situation even worse. Does anyone know how I can stop them from launching, without having to uninstall these apps?
2. I haven't installed the lagfix and I understand that the fix has to do with reformatting the apps' partition with a faster file system to reduce the lag (probably by giving it faster I/O access to the program's binaries?) I'm still waiting for Froyo, which should be out in a couple of weeks in my country. Does anyone know if Froyo would take care of this file system problem? Even with the Froyo or one-click lag fix, it still would not solve the apps launching and memory leak problem, right?
3. I notice that after I've installed more apps, the lag situation got worse. I was playing some songs on the external SD cards and it choked once in a while. I made sure I killed all the other apps and that I still got 100+MB to run just this one song player app and yet it would still choke. This tells me that the lag has nothing to do with available memory. And the player app was stock that came with the phone so there shouldn't be any fragmentation issue (apps installed later might have?) that makes it run slow. And if its the bad file system, this app, running all by itself, should have all the I/O bandwidth to itself so the access to the app's binaries should not have any lag... and neither should the access to the songs on the external SD card. So what exactly is causing the lag then? I don't see how the lagfix would solve this problem either. I actually have read that the lags would come back after a period of usage even with the lagfix. Anyone got an insight to this problem? What exactly is causing the lag? and why installing more apps seem to make it worse? and would Froyo be able to fix all these problems?
Thanks a lot.

@boarder838
I think you really need to read a lot more about just how Android works as you seem to have some strange ideas about how it works.
To start with you need to realise that having 200mb or 100mb of free Ram makes zero difference to performance only when you have no free Ram is it a problem and even then the system will sort it out for you by closing the least used program. Free Ram is just wasted Ram as it's not doing anything and will not make your device respond or work faster using a Auto Task Killer is wasting your battery and slowing down your device not speeding it up and saving battery as you seem to think. As i have pointed out above stop obsessing over your free Ram amount as unless you have none its not a problem stop using a Task Killer and you will most probably see your device responds faster as its not constantly killing things and just leaves them open doing nothing in the back ground which doesn't use Ram or Battery so just leave them be.
Yes Froyo will bring many improvements to our devices but won't fix a problem that doesn't exist re memory leaks and apps launching that you seem to think you have. I don't know but some of those apps may be system apps that need to run all the time which is why they keep relaunching. As for a lag fix well that's what we are all hoping for but if not I'm pretty sure the great people of this forum will come up with an easy to apply fix to it.
I have absolutely no problem playing Music or even streaming it over Bluetooth no lag stutters or break ups at all although my Music is on the Internal SD card. Maybe you should look at the quality that you have encoded your Music in as that may be causing problem. maybe some of the apps you have installed are also causing a problem but its impossible to know as we all install different apps and have different set ups.
I don't know how much experience you have with Android devices or flashing Roms but if you read enough and understand it you have the possibility to flash custom Rom's and various tweaks and fixes to make your device how you want it. That's part of the beauty of Android but don't rush into anything you are not sure about as you can end up with an expensive brick so read things many times and make sure you understand step by step what you are doing if you are going to attempt any of these things.
If you look at my signature you will see i am running a Custom Rom that includes a lag fix and various other tweaks it also allowed me to remove some of the programs in the official Rom that i didn't want or need. For me my device runs nice and smooth and fast of course I'm looking forward to Froyo and all the improvements that will bring but I'm quite happy with my Galaxy S the way it is now. Oh and this is my second Android device and I've never used a Task Killer never mind an Auto Task Killer and have never seen an out of Ram message either.
Marc

exactly what he said ^

Hi Marc,
Thanks for spending time to read through my long post and reply to it. I probably didn't explain my problem clearly in my post.
There were a couple of reasons I wanted to kill/stop the apps from starting:
1. Even before I installed any of those apps killer, I noticed that the available memory kept going down after a couple days of usage and it went down to below 100M. I figured some of the apps would need 10's of MB to run so I thought I should at least keep 100MB around so that it wouldn't run out of memory and start swapping when I start those apps. I don't know enough about Android but I assume its just like linux or other OS, when it runs out of physical memory, it would start swapping and slow things down. Even after I started using task killer and killed all the other tasks, the memory level would still not recover. That seems to point to a memory leak problem but using "Memory Booster" to do garbage collection seems to help. Still, it would be nice to be able to stop them from launching in the first place. <-- my first question.
2. I do not want any jobs/processes/apps that I don't need to run in the background to drain my battery. I don't think I can say for sure that those apps are all just idling and not using much CPU/battery. There are quite a few of them so if each of them use some CPU time/battery, it will add up eventually. Note that these are not system processes (or daemons as in unix's init.d). They are crappy apps from the cellular provider so I'm pretty sure they don't have to be running (they're probably just collecting my personal data or smth). I just thought there would be a way to stop them from launching without uninstalling them.
Thanks for answering my question regarding Froyo. If they would do the filesystem lagfix then I'll just wait for that update.
As for the music stuttering problem, my songs are on the external SD card but my old Nokia E85 phone has no problem playing with those songs on the same SD card. As I have pointed out in my last question, I was only running one app and with plenty of memory so it had nothing to do with available memory. I also suggested that however bad the filesystem was, the I/O bandwidth should still be enough to run this one music player app (access the program binary/libraries?) and to retrieve data from external SD card to play the music smoothly. So applying the lagfix probably won't help this problem though I still haven't tried the lagfix. Now I'm thinking that one of the task killer might be killing some system processes which were needed by the music player. I probably should uninstall all these task killers and see if it would help.
I have gotten the phone for only a couple of weeks so I haven't gotten around to try flashing different roms or rooting my phone. There's so much info scattered around on the web and I can't seem to find a source that really has the authority or complete information. I'll see if I have time later to look into all the tweaks and such but for now its just a phone to me and I just want it to run smoothly without having to spend too much effort to tune it.
Don't get me wrong. I still love the flexibility and customization opportunities provided by the Android platform and I just love to show off my "Beautiful Weather Widget", "Live Aquarium Wall Paper" and my cool 3D scrolling "Launcher Pro" to my iphone4 buddies and make them drool.
Thanks for you comment and let's hope Froyo will bring us a smooth running and stable platform.
Dogmann said:
@boarder838
I think you really need to read a lot more about just how Android works as you seem to have some strange ideas about how it works.
To start with you need to realise that having 200mb or 100mb of free Ram makes zero difference to performance only when you have no free Ram is it a problem and even then the system will sort it out for you by closing the least used program. Free Ram is just wasted Ram as it's not doing anything and will not make your device respond or work faster using a Auto Task Killer is wasting your battery and slowing down your device not speeding it up and saving battery as you seem to think. As i have pointed out above stop obsessing over your free Ram amount as unless you have none its not a problem stop using a Task Killer and you will most probably see your device responds faster as its not constantly killing things and just leaves them open doing nothing in the back ground which doesn't use Ram or Battery so just leave them be.
Yes Froyo will bring many improvements to our devices but won't fix a problem that doesn't exist re memory leaks and apps launching that you seem to think you have. I don't know but some of those apps may be system apps that need to run all the time which is why they keep relaunching. As for a lag fix well that's what we are all hoping for but if not I'm pretty sure the great people of this forum will come up with an easy to apply fix to it.
I have absolutely no problem playing Music or even streaming it over Bluetooth no lag stutters or break ups at all although my Music is on the Internal SD card. Maybe you should look at the quality that you have encoded your Music in as that may be causing problem. maybe some of the apps you have installed are also causing a problem but its impossible to know as we all install different apps and have different set ups.
I don't know how much experience you have with Android devices or flashing Roms but if you read enough and understand it you have the possibility to flash custom Rom's and various tweaks and fixes to make your device how you want it. That's part of the beauty of Android but don't rush into anything you are not sure about as you can end up with an expensive brick so read things many times and make sure you understand step by step what you are doing if you are going to attempt any of these things.
If you look at my signature you will see i am running a Custom Rom that includes a lag fix and various other tweaks it also allowed me to remove some of the programs in the official Rom that i didn't want or need. For me my device runs nice and smooth and fast of course I'm looking forward to Froyo and all the improvements that will bring but I'm quite happy with my Galaxy S the way it is now. Oh and this is my second Android device and I've never used a Task Killer never mind an Auto Task Killer and have never seen an out of Ram message either.
Marc
Click to expand...
Click to collapse

Oh I found the problem with stuttering music. It was the "beautiful weather widget"! I tried removing all the task killers and aquarium etc and it still wouldn't work. As soon as I removed the weather widget there was no problem with music playback anymore. Anyone has the same problem that pretty weather widget?? I've already set the refresh period to every 3 hours but it still wouldn't help?!

How to make your LG Optimus 2x run like a Rocket! (Requires Root)

You don’t need to change your ROM to get the best from your 2x, just a rooted stock ROM and a couple of apps that will change things dramatically. One thing I’ve noticed on the 2x is its memory management is too lenient and gets consumed quickly by background tasks etc. In no time I was down to 40-30Mb free memory and then my phone would run like a dog resulting in a reboot as the only solution.
Installing task and app killers are not the way, as they’ll only give you a short respite before the apps and background tasks you killed relaunch.
However, there is a solution.
1)Root your phone using SuperOneClick (piece of cake, instruction already on this forum)
2)Install “AutoKiller Memory Optimizer” by AndRS Studio free from the market
Optional
3) Install “Watchdog Task Manager” by Zolmut LLC (There’s a free or Paid version) I paid!
4) Install “Root App Remover” by Best of Best Android app
AutoKiller is not a task killer/manager it reconfigures Androids inbuilt memory manager to kill or suppress memory usage by applications and tasks. I now always have about 140-170MB free RAM at all times regardless of what I’m doing (but I do close my apps with the back button rather than click home)
AutoKiller Memory Optimizer Settings
I’ve used the ‘Extreme’ settings to ensure I have around 150MB free, and this makes a huge difference in everything I do with the phone.
----------Optional things you may want to consider-----------
Watchdog
Yeah, I know this is a task killer but Watchdog is different from other task mangers as it monitors CPU usage rather than free RAM, 3D Gallery for example is a CPU hog on my 2X, so I configured it to be killed if it consumes more than 30% CPU whilst running in the background, you’d be surprised what saps your battery!
Root App Remover
Uninstall the tosh supplied on the ROM, I removed the following, AndroidBackup (I use Titanium Backup), CarHome, F-Secure_Mobile_Security, SNS (If you’re not using the built in Facebook and Twitter app).
I also use LauncherPro with Beautiful Widgets to give my phone an almost HTC Sense look and feel and uninstalled LG Home using Root App Remover afterwards.
Hope it makes a difference for you, it did for me, vote if you like

What do you think having 140-170MB RAM free at all times actually does?
Guess what? Nothing.

I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2

We want to see some bench marks.

Thanks for sharing! My phone does become much more responsive
Sent from my LG-P990 using XDA App

I tried the app too and i can say that it works, I also did some of the advanced tweaks.
phone seems more responsive now.

Yes, me too. It's more responsive now. Also when I open app manager, the app list is a lot faster.I know it's more related to file read/write but still it's nice to finally able to browse with less waiting time.
Sent from my LG-P990 using XDA App

thx
good one and simple, thx

cann someone please post some benchmarks?

Here are some screenshots, tested with AnTuTu Benchmark
The first one is v10c stock, some apps like f-secure, carapp etc frozen, second one is with using autokiller memory with preset extreme, third one is to compare, this was while using cm7.1 rc
now we'll see if autokiller works stable ^^
edit: realized that with cm7 something seemed to be wrong with the sd-card, so don't forget to compare the single-scores

spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'm sure Rusty knows what he is talking about. Thing is, this talk about "the more free ram the better" has been repeated so many times, and at the end of the day, it seems to be more about user preference.
The default LG ROM seems to allow tasks to run in the background until it reaches around 50MB free RAM, then it starts to close tasks one by one. For multi-taskers like me, this is fine, I love how I can switch between facebook, tweetdeck, miren browser, google+, gmail, and messaging without seeing the apps reload.
For some, they'd want to open a task, close it, and move on to another without looking back. I guess that is where the 100MB of RAM is good for.
If you guys will be looking at benchmarks, I can guarantee that you will have higher scores with RAM optimizers. As benchmarks do not test multitasking, they simply check the performance of your phone at that point in time. (Which is also why some modders pump up their CPU freq to insane values before doing their bench then posting it.)
I have nothing against AKMO, and I find it very effective for Froyo builds. But I would recommend that each user try it out themselves. It's not a "1 fix for all" thing.

spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space

kiljacken said:
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
Click to expand...
Click to collapse
Does O2X already support swap space in EXT? (Or are your referring to VM heap?)

Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.

akyp said:
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
Click to expand...
Click to collapse
Yeah, FR19 is one of the more stable ROMs out there. Try full wipe then reflash maybe.

Apps Performance issue

Hello evry one. I have problem in my captivate and other models of android. I installed almost every custom rom but problem of loading apps fast still exist. What i mean is.. that when i on my mobile, so first time apps like calender, messenging etc take a little time to load. than when i close the app and open again, it loads very quickly. When mobile goes to standby for more than 10 mins, and when i on it, it again take little time to load apps, and widget menu etc.
Why it is like that ??? and whats the solution to always load the apps quickly

majidshahab091 said:
Hello evry one. I have problem in my captivate and other models of android. I installed almost every custom rom but problem of loading apps fast still exist. What i mean is.. that when i on my mobile, so first time apps like calender, messenging etc take a little time to load. than when i close the app and open again, it loads very quickly. When mobile goes to standby for more than 10 mins, and when i on it, it again take little time to load apps, and widget menu etc.
Why it is like that ??? and whats the solution to always load the apps quickly
Click to expand...
Click to collapse
It's how Android manages memory. It keeps your apps in memory until it needs to free some, at which point it starts to close apps to free some up. If they're already in memory they open fast because they're already open. If they aren't, they open more slowly.
There's not a ton you can do, really. Some 3rd party sms apps let you lock the app in memory, but I honestly never checked to see if it really works or not.
Personally, I restart my phone every morning when I wake up. This frees up the most memory and allows your phone to leave more apps open before closing them.

make sure you arent running any ****ty task killers.

You could flash an I9000 ROM/kernel that let's you tweak the lmk. (low memory killer)
Talon and semaphore both offer that option.
The trick is to make it weak enough to not kill the apps you want, but aggressive enough to not allow to run out of ram completely.
both of those kernels also have a "bigmem" version that gives the user a bit more ram at the cost of being able to record video in 720p.

studacris said:
You could flash an I9000 ROM/kernel that let's you tweak the lmk. (low memory killer)
Talon and semaphore both offer that option.
The trick is to make it weak enough to not kill the apps you want, but aggressive enough to not allow to run out of ram completely.
both of those kernels also have a "bigmem" version that gives the user a bit more ram at the cost of being able to record video in 720p.
Click to expand...
Click to collapse
I like ur answrr. But can u pls guide me abt lmk. I like this idea but never use such tweaks. I m using talon kernel right now and rom is much fast. But have same prb of apps loading

In the app memory freak, that installed with the kernel, there is a slider for you to adjust,
lower number the more aggressive the lmk but the better the overall performance.
Higher number is less aggressive and is better for multitasking, but can be a bit slower.

studacris said:
In the app memory freak, that installed with the kernel, there is a slider for you to adjust,
lower number the more aggressive the lmk but the better the overall performance.
Higher number is less aggressive and is better for multitasking, but can be a bit slower.
Click to expand...
Click to collapse
Where to find app memory freak ? i haven't seen any option in CWM

Should have been installed when you flashed talon. If not, it should be linked in the talon op.

[Q] Trouble with RAM management?

I got my Xperia Z1 about a month ago, and I've noticed some issues with RAM management (or possibly under-optimized third-party apps). Although I haven't had much luck in replicating the problem, I noticed it happen a few times after a Firefox internet session, or after playing a graphically intensive game like Dead Trigger 2. The app would either close by itself (not crash, as in, there were no error messages), or, after I'd close it, I'd notice my launcher (Nova Launcher Prime) go into a restart loop. A quick glance at the running apps section in settings shows 50-100 MB of free ram, and all "constantly running" apps (launcher, viber, zooper widget, k9-mail, swiftkey, tasker, etc.) stuck, for want of a better phrase, in a restarting loop (due to lack of ram I guess).
I tried running Fast Reboot (a task killer) to see if I could regain stability of the system, but it kills only a few system tasks, freeing up to a measly 50 MB of RAM, which makes me wonder (in aggravation) just where the RAM is being used. The only way the running apps would stop closing and restarting (and I need the launcher stable) is to reboot. I'm not sure if the system would stabilize after x minutes, as I only waited for a minute or two before rebooting so that I could open another app/game.
I'm not trying to start yet another debate on necessity of used RAM on Android and efficiency/futility of task managers/killers, but what I described above really seems like poor RAM management to me. I've had a few android devices in the past, and experienced various problems /errors, but never something like this.
Has anybody had a similar issue, or have any tips?
My Xperia Z1 C6903 is currently running on rooted stock 14.2.A.0.290

Although i dont get force closes, but ive noticed most of the ram is taken by the phone itself, right now for me it says i have 1.1gb in use, when i close everything i have just a slight (barely even noticeable) increase in free ram, when i click on cached processes and close all one by one ive seen it increases the ram use instead of decreasing it?
But, do you use apps like setcpu? You can keep it on performance and keep the min slider to the lowest and the max slider to max, it runs stable and gives you performance when you need it, and no performance when you dont need it.
If all fails, try deleting system apps that you barely even use or need... Becareful what you delete tho!

mobzw995 said:
Although i dont get force closes, but ive noticed most of the ram is taken by the phone itself, right now for me it says i have 1.1gb in use, when i close everything i have just a slight (barely even noticeable) increase in free ram, when i click on cached processes and close all one by one ive seen it increases the ram use instead of decreasing it?
But, do you use apps like setcpu? You can keep it on performance and keep the min slider to the lowest and the max slider to max, it runs stable and gives you performance when you need it, and no performance when you dont need it.
If all fails, try deleting system apps that you barely even use or need... Becareful what you delete tho!
Click to expand...
Click to collapse
Thanks for the reply. No, I've used apps like that in the past, but haven't installed anything similar on the Z1, because I noticed in BetterBatteryStats that the CPU speed goes down often when the screen is off, and up when, I suppose, it's required, such as in intensive games...

What apps do you use? For example facebook, YouTube, browser etc
Ive checked again on my cached apps and to my surprise, AOSP browser takes up 208mb!
Facebook takes up 48mb, and youtube takes up 22mb.
It just depends on the apps you have installed, some use the ram even while the phone is asleep.
Ive stopped those and a huge difference was made on freeing up my ram!
What i dont get is tho why sony advertises 2.2ghz quadcore if the phone itself takes most of it?
Just delete the apps you dont need from "all apps".