Related
I have an LG Optimus running OpenSwift (CM6), it is quite smooth but it has less RAM available than the stock ROM. Why is this?
Different ROM images include different apps and services, so RAM usage always differs between them.
And variability in RAM usage is greater between different Android versions.
Agreed, but it only seems to have 30MB of RAM so I have to use a taskkiller app, which drains battery further. . Anyone got any ideas/reasons? They would be greatly appreciated
You can try to delete useless apps from system/app, that can stop executing useless processes and you'll get more free RAM.
Also you can flash your mobile phone with odexed rom which uses less RAM because odexed apps are more optimized.
I have about 60Mb free RAM
RAM
You can try an app call "swapper" there is a free vension of it on the market, it allows you to a swap to you sd card for extra ram, it will depend on your rom and you also will need to have root priviledge. it seem to make my LG540 run abit better.
max1919 said:
You can try to delete useless apps from system/app, that can stop executing useless processes and you'll get more free RAM.
Also you can flash your mobile phone with odexed rom which uses less RAM because odexed apps are more optimized.
I have about 60Mb free RAM
Click to expand...
Click to collapse
Thanks, i'll try this once I have made a backup. Do you think some of the bloatware system apps could be causing this?
androidia said:
You can try an app call "swapper" there is a free vension of it on the market, it allows you to a swap to you sd card for extra ram, it will depend on your rom and you also will need to have root priviledge. it seem to make my LG540 run abit better.
Click to expand...
Click to collapse
Thanks androidia, this worked! Got me more RAM
I have rooted my Asus TF, Put on the H 3.1 os, used Clemsyn Blades kernel, running very nicely. I have rooted it, and uninstalled crap like facebook, books, splashtop etc...lot of useless bloatware is out...However here is the problem........LOW MEMORY....This machine has ram of 1GB, and only 800mb shows, so almost 200 for the GI, and out of that 800, about 400mb is always used, despite using various app killers, I think we should be able to get it to about 200mb used? anyone know where so much of ram is bieng eaten
My question to you great knowledgeable friends is;
1) how to get rid of more useless apps eating memory
2) does using a different launcher reduce ram eating?
3) is it possible to achieve about 200-300mb consistent ram?
This is an awsome machine, I think more tweks we can make is super. I have a Samsung GS2, I have removed most of the stock stuff on it and set up my ownlauncher etc. It runs with amazing memory, 500mb free, and awsome graphics interface. Less nonsense.
MasterfullDON said:
I have rooted my Asus TF, Put on the H 3.1 os, used Clemsyn Blades kernel, running very nicely. I have rooted it, and uninstalled crap like facebook, books, splashtop etc...lot of useless bloatware is out...However here is the problem........LOW MEMORY....This machine has ram of 1GB, and only 800mb shows, so almost 200 for the GI, and out of that 800, about 400mb is always used, despite using various app killers, I think we should be able to get it to about 200mb used? anyone know where so much of ram is bieng eaten
My question to you great knowledgeable friends is;
1) how to get rid of more useless apps eating memory
2) does using a different launcher reduce ram eating?
3) is it possible to achieve about 200-300mb consistent ram?
This is an awsome machine, I think more tweks we can make is super. I have a Samsung GS2, I have removed most of the stock stuff on it and set up my ownlauncher etc. It runs with amazing memory, 500mb free, and awsome graphics interface. Less nonsense.
Click to expand...
Click to collapse
If you haven't done so already you could use Titanium Backup to remove more stuff (including system apps) since you're rooted. I would advise caution however in case you remove the wrong thing. Perhaps someone else can post regarding which particular system apps are safe to remove, as I haven't expreimented with this myself.
jonitfcfan said:
If you haven't done so already you could use Titanium Backup to remove more stuff (including system apps) since you're rooted. I would advise caution however in case you remove the wrong thing. Perhaps someone else can post regarding which particular system apps are safe to remove, as I haven't expreimented with this myself.
Click to expand...
Click to collapse
Ive done that and removed about 10 items. Its running well at 1.4GHz but only problem too much ram usage.
jonitfcfan said:
If you haven't done so already you could use Titanium Backup to remove more stuff (including system apps) since you're rooted. I would advise caution however in case you remove the wrong thing. Perhaps someone else can post regarding which particular system apps are safe to remove, as I haven't expreimented with this myself.
Click to expand...
Click to collapse
He could just freeze them first and play with the tf a couple of days and if there are no problems, delete them.
Removing junk isn't a bad thing to do, but in my experience, app killers do more bad than good in android. Other than in windows, you don't need tons of free ram to run apps smoothly. Android has a great ram management that fills your ram with apps for fast access, and closes the least used/needed when another app requests more ram. So if you use an app killer, your tf will have more to do with restarting the apps you just closed and your performance will actually decrease. Google it and you'll know what I mean.
Regards
Qwer23
Sent from my rooted X10i using awesome custom roms
MasterfullDON said:
Ive done that and removed about 10 items. Its running well at 1.4GHz but only problem too much ram usage.
Click to expand...
Click to collapse
As i said before, much ram usage isn't necessarily a bad thing. It only eats performance if a running app is badly coded and doesn't give its ram free when required. Then you better kill this specific app instead of autokilling stuff. Well coded apps won't eat your performance, no matter how much ram is used.
Sent from my rooted X10i using awesome custom roms
300Mb oof ram are dedicated to Nvidia Tegra 2. For this reason you read "only" 700Mb. Maybe in near future we will able to allocate more memory than 256Mb to our Tegra 2
memory usage doesn't mean too much now if the app/programe is properly coded, when needed, android should be able to release them on the fly......
same goes to my windows 7 machine, it's got 8 gig memory but the free memory always remains under 500M because the system is using them to cache most recently used applications.
Constantly clearing memory will not help too much, and believe or not, it worsens both the performance and the battery life..
but again, android is not as robust as windows in the terms of memory management, so it's not a bad idea to occasionally take a look at the actual memory usage but just don't go too excessive...
Screwing around with app-killers is never a good idea. Are you actually experiencing issues due to insufficient RAM? I've never had an issue with RAM on my Transformer. Android is much better at handling its memory than people are, let it do its thing.
And for the record, RAM is there to be used. It's the fastest memory a device has, so the more it makes use of, the better. If something else needs more RAM, Android will flush out something that doesn't need it.
I think app-killers are one of the biggest issues with Android, in that people seem to think they're necessary. Unless you actually have some app that's misbehaving or has a memory-leak or something, you shouldn't ever really need to manage your running applications. Just leave it all alone for a while and see how you go.
Midda said:
And for the record, RAM is there to be used. It's the fastest memory a device has, so the more it makes use of, the better. If something else needs more RAM, Android will flush out something that doesn't need it.
Click to expand...
Click to collapse
Perfectly said. Don't mess your Transformer around with "Task Manager"-type apps.
Midda said:
Are you actually experiencing issues due to insufficient RAM? go.
Click to expand...
Click to collapse
not at all. The machine is fast, its very quick and loads things quickly. The only time I had problem is using logmein, it crashed and said out of memory...I was a bit perplexed. I cleared a lot on my SGS2, and it was much faster.
Let me know any ideas, otherwise, as suggested, I will see how it goes
From my previous experience with Android devices, it's nearly impossible to increase the amount of free ram. I've tried, and only found one solution that I'll talk about later.
This isn't a bad thing. Ram is not CPU usage, and ram is going to use roughly the same amount of electricity regardless.
What android does is fill up the ram with programs that you will potentially use. That way when you want to use the program, it's already loaded in memory. When you load another program into memory, say a game, it will close apps to make room for the new app.
If you really want more memory, the closest thing is a swap file or partition. I use one on my phone, and it helps a good bit. Don't know if it would help the TF101, since it already has 1GB ram.
If you are still set on more free ram, try a program like auto memory manager (there is also another program very similar, has a blue fish for a logo but I forget the name). This doesn't kill apps in memory. Instead it changes the the when android closes programs in memory based on how much free memory is available and the priority of the program. I used it before on my phone with pretty good success, but now I use a swap file instead.
Right now I don't use a swap file or memory manager on my tf101, sine it runs great without it.
Thanks for all your responses.
I think this article should explain how Android 2.x operates. Even though the article is not about Honeycomb (Android 3.x), I doubt Google has changed how it manages memory in Honeycomb.
Article here: h**p://lifehacker.com/5650894/android-task-killers-explained-what-they-do-and-why-you-shouldnt-use-them
(Sorry, can't link due to XDA's 8+ post policy...)
I only have 55xMB memory shown in the application though.
154MB Used 398MB Free
Hi guys, I've been playing around with different kinds of RAM tweaks(scripts and apps available here in xda and in the market) for a couple of weeks now.
Then a couple of days ago, I finally decided not to use any.
Personally, I think my phone is more snappy, letting android system manage its RAM.
Considering I have around 100 user apps now, the phone is surprisingly still very snappy.
This is what I noticed on android RAM management, when needed more RAM for certain apps(let's say games), android will kill those inactive apps giving some more RAM for the one app you are currently using. Even those persistent apps(like mails, messengers, etc) will be killed to free-up some more RAM.
So I guess with our phone's caliber/specs and current OS version, we almost don't need those RAM tweaks around, same goes with those task killers.
My phone's current settings using doomlord's kernel:
launcher - go launcher(with only few widgets, less than 10)
i/o scheduler - deadline(system default)
cpu governor - ondemand(system default)
CPU min/max frequency - 245MHz/1.3GHz
app2sd - ext3 partition ~900MB(all user apps located here - 160MB used of the total 900MB)
but my dalvik cache still resides in internal memory - 170MB used of the total 380MB
Note that the above is the same settings I used when I was observing my phone with and without RAM tweaks.
So guys please share your experiences on RAM tweaks if it's effective or not on your current setup.
I have to agree, the old android you did need all that tweaking, but I do believe now you don't, just have to give time, the first day I got my arc I wanted to throw it in the Wall! It was the worst phone! But after one update it was 80% better, now with the latest firmware update another 20% and hopefully the next update will even be more better, I just wish that there was more memory
Sent from my LT15i using XDA Premium App
I'm using the V6 Supercharger. It's more or less a tweak for the default Android RAM management system. I kinda like it. While it does make the phone appear slightly less smooth in some rare cases, in general everything is more consistent. No more 4-second waits before the Messaging or Contacts app opens etc. Aside that I don't feel I need anything at all.
Stock firmware, stock kernel (never bootloader unlocked), rooted and Supercharged. 4.0 software!
Yup, I also thought that the default phone and messaging apps are quite slow so I replaced it with touchpal and gosms. Definitely for some default apps, it's better to use 3rd party available from the market.
Btw, I also tried supercharger before but I realized it is not suitable for my usage as I always have more than 32MB of ram(32MB is the default android threshold setting before it starts killing those dormant/inactive apps). The script is very customizable though so it might help those heavy multitaskers.
Sent from my LT15i using XDA Premium App
I had the same problem before the latest update, but now messages, contacts up within seconds
Sent from my LT15i using XDA Premium App
It sounds like everyone would benefit from using this script, but there's no specific guidance for the MyTouch 4G. I assume option 8 or 9 would be best since the phone has 512MB of ram.
Are there some roms that we shouldn't be using V6 SuperCharger with?
Link to V6 SuperCharger: http://forum.xda-developers.com/showthread.php?t=991276
You're wrong on 2 points (possibly more):
1) This script is just the same as Autokiller app, with a small addition - it can (or can't) keep launcher in memory. Nothing new and revolutionary. This app exists for a couple of years.
2) This phone has 768MB of RAM. It won't benefit from a low memory killer (or actually, different settings for an existing in OS lowmemkiller), because it has TONS of memory. I just took a look at my phone, ~100MB of memory free, and ~300MB of remaining memory is taken by CACHED apps. If you don't know what it means - please read up on Android memory management, and I'll give you the short version - it's the same as free memory, but better.
It states in the first post:
Also Note: Nothing else does what The V6 SuperCharger does!
................Not AutoKiller Memory Optimizer, Not Auto Memory Manager, Not Minfree Manager...
The Nook Color has 512 MB of ram and people have noticed a big difference using this script on Cyanogenmod.
but since the Glacier has 768MB of ram, you won't notice much change.
saranhai said:
but since the Glacier has 768MB of ram, you won't notice much change.
Click to expand...
Click to collapse
I have found it useful on ports and ROMs that aren't tweaked specifically for this phone. For instance, if TDJ made the ROM, V6 is useless. In fact, it will only hurt.
Sent from my HTC Glacier using XDA App
I use this script on my evo and its great so I just rooted this phone and flashed the mik runny ROM, I was using it for a day and only stayed at about 100mb of RAM so I decided to use v6 with option 8 and now it stays around 200mb and is running super smooth.
IDK if that helps any but I always loved v6 and know a few people that use it on a few different phones and it always works for the better.
Sent from my HTC Glacier using XDA App
Why do people that know nothing or close to nothing about OS internals, decide that they have better knowledge of memory management should be, then OS and phone designers? The same people who don't know the difference between cached and active apps, and the only number they understand is the (useless) amount of free memory? I see it all over the forums, and it amazes me each time. How do people actually try to judge if something works well or not, without getting at least some basic understanding of how the things work?
Oh well, here it comes again:
http://forum.xda-developers.com/showthread.php?t=678205
Read this. Maybe you will understand something.
Few, if any, 512MB phones and no 768MB phones need this script, or any kind of tweaking for lowmemkiller values, especially not since Gingerbread and when not running Sense (which retains the ability to cache apps, removed in Gingerbread mostly to ease running the OS on older devices). The only thing it does, is to make garbage collector work harder and kick in earlier. It doesn't make your phone "smoother", and whoever think it does - should check the meaning of the word "placebo" in the nearest dictionary. The number that stands for "free memory" means something between "close to nothing" and "absolutely nothing".
I know I shouldn't be surprised, people always tend to have strong opinions on everything, even things they sometimes don't know a thing about. But still, it's XDA-Developers, not XDA-Phone-users, so at least something should be done about it. Even if the education attempts will fail, like they mostly do.
Jack_R1 said:
Why do people that know nothing or close to nothing about OS internals, decide that they have better knowledge of memory management should be, then OS and phone designers? The same people who don't know the difference between cached and active apps, and the only number they understand is the (useless) amount of free memory? I see it all over the forums, and it amazes me each time. How do people actually try to judge if something works well or not, without getting at least some basic understanding of how the things work?
Oh well, here it comes again:
http://forum.xda-developers.com/showthread.php?t=678205
Read this. Maybe you will understand something.
Few, if any, 512MB phones and no 768MB phones need this script, or any kind of tweaking for lowmemkiller values, especially not since Gingerbread and when not running Sense (which retains the ability to cache apps, removed in Gingerbread mostly to ease running the OS on older devices). The only thing it does, is to make garbage collector work harder and kick in earlier. It doesn't make your phone "smoother", and whoever think it does - should check the meaning of the word "placebo" in the nearest dictionary. The number that stands for "free memory" means something between "close to nothing" and "absolutely nothing".
I know I shouldn't be surprised, people always tend to have strong opinions on everything, even things they sometimes don't know a thing about. But still, it's XDA-Developers, not XDA-Phone-users, so at least something should be done about it. Even if the education attempts will fail, like they mostly do.
Click to expand...
Click to collapse
I do understand that in some cases you don't need a memory manager like if your running a stock ROM or an aosp ROM that doesn't take up as much memory.
Now I haven't had this phone long enough to say if this script is all that good for this phone but I know on the evo running a sense 3.0-3.5 ROM that wasn't meant for the phone and hugs up every little bit of memory that the phone has to offer, this scrip makes those ROMs usable.
Without it or something like it the phone can't handle doing simple tasks like using an app without fc something else like the launcher.
So you could say what you want and yes maybe this phone doesn't need it since it has more RAM and ROM but I'll still try things like this to try and see if it will better the phones performance.
Sorry if that doesn't make sense I'm still half asleep.
Sent from my HTC Glacier using XDA App
The instances where i have noticed that this works is while doing benchmarking with quadrant. It has shown increased framerates for me after running the script and I also get higher scores on quadrant, about 500-1k more than without. I dont know if its usefull for much other than benchmarking though. I think the phone runs fine without it though.
What you have to understand is performance is not measured via syntactic benchmarks (ex: Quadrant). The biggest issue with people is that they don't know enough to know that they don't know, so they compare it with silly numbers (ex: score) they can't comprehend what they see, much less put numbers behind real life activities that's not applicable in controlled environment.
Now far as V6-SC script goes its almost obsolete now due to few things. 1) Hardware advancement where now minimum spec requirements for "SmartPhone" are 1ghz single core proc with 512mb ram. But so called "SuperPhone" now has dual core 1ghz-1.5ghz with 768mb-1gb ram. So it make no sense as we don't use 256-566mhz proc with 64-256mb ram because we are more then enough hardware adequate for heavy daily usage. 2) OS development which elements most of it as hardware is more and more powerful. But on software level mostly all custom base rom (ex: CyanogenMod) is highly optimized and tweaked to run on optimal performance.
Now is it all placebo effect? Mostly, but not all. But does it mean it can't be tweaked any further? (Rhetorical) No. How do I know? We (scope outside of XDA) tweaked it to the next level. How you ask?
1) Optimized ext4fs: reduced r/w rate (healthy NAND lifespan), improved journaling (corrupted data writeback integrity) = Which improves the IOPs and performance access rate.
2) HC3.x fugu binaries, patched sqlite libraries, mSD read ahead buffer fix.
3) Modified VM: OOM (Out Of Memory), LMK (Low Memory Killer), VM heap (Virtual Machine), DRA (Dirty Ratio), DBR (Dirty Background Ratio), DWC (Dirty Writeback Centisecs), DEC (Dirty Expired Centisecs), SWP (Swap), VCP (VFS Cache Pressure).
4) Increased minfree value: Background, Foreground, Empty, Hidden, Visible, Secondary, Content.
5) Optimized cache: File and Drop cache, Forced cache (resident loop).
6) Custom kernel: OC/UC, UV/SVS/VDD, BFS/CFS, RSU/VR/SP supported.
7) Custom ROM: Optimized Rom script and props (ex: CyanogenMod).
I bet my superior MT4G can own your inferior MT4G. Cuz you can't touch this as its tweaked to THE next level. I'll stick with AOSP2.3.7GB until ICS4.X is more stable and we understand more as most memory grouping and adjustments might be changed.
Sent from my HTC Glacier
Jack_R1 said:
You're wrong on 2 points (possibly more):
1) This script is just the same as Autokiller app, with a small addition - it can (or can't) keep launcher in memory. Nothing new and revolutionary. This app exists for a couple of years.
2) This phone has 768MB of RAM. It won't benefit from a low memory killer (or actually, different settings for an existing in OS lowmemkiller), because it has TONS of memory. I just took a look at my phone, ~100MB of memory free, and ~300MB of remaining memory is taken by CACHED apps. If you don't know what it means - please read up on Android memory management, and I'll give you the short version - it's the same as free memory, but better.
Click to expand...
Click to collapse
Obviously, you never tried it lol
Here... you may learn something new...
http://www.rt-embedded.com/blog/archives/linux-memory-consumption/
http://forum.xda-developers.com/showpost.php?p=20163493&postcount=6695
Below a certain threshold of free ram (ie. not enough cached), the device WILL gag...
Hundreds if not thousands of users with 1 GB ram devices use it (Atrix, SGSII, etc.) and I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
In fact, the biggest difference he notices is in the use of google maps... never a stutter.
So you're missing out.
zeppelinrox said:
[1] Obviously, you never tried it lol
[2] I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
[3] So you're missing out.
Click to expand...
Click to collapse
First of all as dev of V6-SC you would be very defensive but at same times your not charging money to normal folks for it is a good thing, so thank you. Which I can say less about other folks editing same value claiming it new. Now I don't know about Jack but let's be clear on few points.
1) I did try your so called script and didn't like the whole script manger + busybox cast AFTER the OS startup. Which normally you can achieve via daemon or init.d script after kernel is initialized by declaring and using native shell. So no need for force apply afterwards as it was utilized before it was initiated via script manager. Also V6-SC couldn't keep the selected category minfree value which changed. But in short I didn't notice anything revolutionary as it was fully optimized long before I randomly landed on Android General section and saw your post claiming it maximize the devices performance. Which I was spectacle about as from your post you did seem to have basic knowledge hopefully not from wiki/google but *nix usr exp before landing on to Android.
2) Like I said I don't know about Jacky Boy but I can GRANTEE you I have NEVER had this so called "button delay" you specified. But I did modify the sampling rate and pressure density accommodated by tweaking transition speed. But now I run min:368mhz/max:1027mhz/gov:SmartAssV2. But even when I was battery conscience before I had MP1650mAh I ran on min:230mhz/max:768mhz/gov:SmartAssV1 with custom -75 to -100 VDD using ~14mA idle and ~60-90mA active per unit scale. I never had lag with 200mb used RAM running at least 18-20pcs and 14-15svc. So what your friend is running (Atrix) is irrelevant also isolated.
3) O-RLY am I really missing out? I think ill stick to my own. But don't take this post personal as it was ment for it to be argumentative. Difference is I actually know what I'm talking about as I have strong backgrounds on...
Sent from my HTC Glacier
zeppelinrox said:
Obviously, you never tried it lol
Here... you may learn something new...
http://www.rt-embedded.com/blog/archives/linux-memory-consumption/
http://forum.xda-developers.com/showpost.php?p=20163493&postcount=6695
Below a certain threshold of free ram (ie. not enough cached), the device WILL gag...
Hundreds if not thousands of users with 1 GB ram devices use it (Atrix, SGSII, etc.) and I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
In fact, the biggest difference he notices is in the use of google maps... never a stutter.
So you're missing out.
Click to expand...
Click to collapse
I didn't need to try it to know. I tried Autokiller, I played with lowmemkiller settings and watched the results, and I did it on Nexus One with 512MB of memory. It never needed anything since Gingerbread, and unless I made the settings super-aggressive, Autokiller actually failed to make any difference whatsoever - the apps were killed based on their age and never dropped by replacing apps.
In the current system, I have 100MB free + 250MB cached apps (which is just the same as free - theoretically and practically). The main difference you're not accounting for is - Android isn't a Linux distro, it's a Linux-derived OS, with many changes for mobile activity, especially on the kernel level, especially in the memory management area. "Linux memory consumption" isn't Android memory consumption, since they manage things differently. Linux isn't build to kill running apps, its lowmemkiller can't do it. Linux doesn't have concurrent garbage collector. Many Linux examples are irrelevant. Cached apps in Android aren't cached pages in Linux, freeing cached pages in Linux isn't killing cached apps in Android, and the most important - "performance degradation" doesn't exist in Android, since you ALWAYS have enough memory for any size of task (the largest loading task requires 50MB of memory, and there's 100MB free on my phone), and concurrent garbage collection is ALWAYS present in the system, the only thing you're doing - is calling it earlier, making it actually work more and getting the system more laggy than it could be.
I understand that you want to protect your creation, but in this case, you're wrong, sorry. You won't convince me.
And yes, I don't know what "button lag" are you talking about.
HTC Glacier said:
First of all as dev of V6-SC you would be very defensive but at same times your not charging money to normal folks for it is a good thing, so thank you. Which I can say less about other folks editing same value claiming it new. Now I don't know about Jack but let's be clear on few points.
1) I did try your so called script and didn't like the whole script manger + busybox cast AFTER the OS startup. Which normally you can achieve via daemon or init.d script after kernel is initialized by declaring and using native shell. So no need for force apply afterwards as it was utilized before it was initiated via script manager. Also V6-SC couldn't keep the selected category minfree value which changed. But in short I didn't notice anything revolutionary as it was fully optimized long before I randomly landed on Android General section and saw your post claiming it maximize the devices performance. Which I was spectacle about as from your post you did seem to have basic knowledge hopefully not from wiki/google but *nix usr exp before landing on to Android.
2) Like I said I don't know about Jacky Boy but I can GRANTEE you I have NEVER had this so called "button delay" you specified. But I did modify the sampling rate and pressure density accommodated by tweaking transition speed. But now I run min:368mhz/max:1027mhz/gov:SmartAssV2. But even when I was battery conscience before I had MP1650mAh I ran on min:230mhz/max:768mhz/gov:SmartAssV1 with custom -75 to -100 VDD using ~14mA idle and ~60-90mA active per unit scale. I never had lag with 200mb used RAM running at least 18-20pcs and 14-15svc. So what your friend is running (Atrix) is irrelevant also isolated.
3) O-RLY am I really missing out? I think ill stick to my own. But don't take this post personal as it was ment for it to be argumentative. Difference is I actually know what I'm talking about as I have strong backgrounds on...
Sent from my HTC Glacier
Click to expand...
Click to collapse
Sounds like you never got it working properly.
Also, if you have init.d support no need to run anything on boot with script manager.
Maybe the rom's kernel was applying settings late.
And no my friends atrix is not isolated there is a rather big thread in the atrix forums.
SGSII users see benefits too so seems there is always room for improvement.
Jack_R1 said:
I didn't need to try it to know. I tried Autokiller, I played with lowmemkiller settings and watched the results, and I did it on Nexus One with 512MB of memory. It never needed anything since Gingerbread, and unless I made the settings super-aggressive, Autokiller actually failed to make any difference whatsoever - the apps were killed based on their age and never dropped by replacing apps.
In the current system, I have 100MB free + 250MB cached apps (which is just the same as free - theoretically and practically). The main difference you're not accounting for is - Android isn't a Linux distro, it's a Linux-derived OS, with many changes for mobile activity, especially on the kernel level, especially in the memory management area. "Linux memory consumption" isn't Android memory consumption, since they manage things differently. Linux isn't build to kill running apps, its lowmemkiller can't do it. Linux doesn't have concurrent garbage collector. Many Linux examples are irrelevant. Cached apps in Android aren't cached pages in Linux, freeing cached pages in Linux isn't killing cached apps in Android, and the most important - "performance degradation" doesn't exist in Android, since you ALWAYS have enough memory for any size of task (the largest loading task requires 50MB of memory, and there's 100MB free on my phone), and concurrent garbage collection is ALWAYS present in the system, the only thing you're doing - is calling it earlier, making it actually work more and getting the system more laggy than it could be.
I understand that you want to protect your creation, but in this case, you're wrong, sorry. You won't convince me.
And yes, I don't know what "button lag" are you talking about.
Click to expand...
Click to collapse
I was tempted to stop reading when you admit to not even using it.
If it did the same as AKMO or Auto Memory Manager why on earth would anybody bother.
I sure as hell wouldn't bother writing a 4500+ line script lol.
I totally agree that Android memory is not the same as linux (see my sig) but the similarities are there and the article I posted applies 100%.
Its not about free ram.
Its about the right balance.
In fact, many report LESS free ram, ie. better multitasking, along with better performance and smoother performance.
Because I don't think Android memory should work the same as linux memory either.
Also, you tried AKMO because you felt there could be improvement and it didn't work.
THAT'S why I wrote a 4500+ line script that blows anything else out of the water
zeppelinrox said:
Sounds like you never got it working properly.
Also, if you have init.d support no need to run anything on boot with script manager.
Maybe the rom's kernel was applying settings late.
And no my friends atrix is not isolated there is a rather big thread in the atrix forums.
SGSII users see benefits too so seems there is always room for improvement.
Click to expand...
Click to collapse
Well my highly optimized as is but I am aware of V6 and others using it but personally I would stick to my.
Sent from my HTC Glacier
On my Optimus G (which had 2 GB of RAM) the maximum available RAM at any given time was about 1.5 GB out of 1.85. On the G2, it's never more than 1.2. I've not noticed slowdowns because of it, but what's using so much RAM? Is the interface really that heavy this time? Or is there a glitch somewhere?
Sent from my LG-D800 using xda app-developers app
Yea I noticed that too when comparing to my nexus 4, I have always wondered if GRAM has anything to do with it. If GRAM is eating up my ram but giving me better battery life then I am happy about it.
Sent from my LG-D802 using Tapatalk
Unused RAM is wasted RAM.
Don't worry about the RAM!!! Its there to be used! if it was to high we'd get all these high RAM threads.
As time goes on, apps and services are used. As apps and services are used the necessary pages are brought into memory and executed. They remain there until the minfree threshold is reached and then they are removed from memory. The minfree memory is usually 100-200 mb. This is a value that can usually be adjusted but of course requires root.
Some applications are poorly coded and may contain memory leaks. Find out which ones they are and delete them or contact the developer so they can fix and continue to monitor it if you need it.
Here is a good article but its a little old: http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care