Related
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.
So, i've tried many different roms out there on my SGS. Never got any major issue with flashing or setting them up. Supposedly a custom rom has something improved but there was one think i kept thinking they all fail and i was wondering if anyone else feels the same.
I see random posts all the time telling how great multitasking in android is. But all these roms i keep using try their very best to close just about everything i have running. As far as i can tell, a few seconds after i switch to anything else, my first app gets closed. For example, everytime i'd leave browsing to manage what im listening to or sort out files on some file manager i'd find i needed to open my browser again instead of being there opened and waiting for me to return.
After searching for a while, the best explanation i could find out is to prevent battery drain from opened apps and to keep things smooth by having free ram, which kind of makes sense. Goes against what i read in a paper from google about android multitasking but fair enough.
Except the other day i happened to returned to a froyo stock rom (JS8 with darkcore 1.4) on my SGS and found out this does not happen. Apps stay open for the most part, except when i run something really heavy (like a game). And i dont really notice any performance decrease or extra battery drain from my usual usage.
Granted, i could be just told something along the lines "well dude, just use whatever works for you" and i totally plan on doing so, hence me experimenting, but thats not really my point. What i'm going for is, are custom roms being overzealous? because this really spoils any attempt at multitasking...
Again, this is not a rant of any sort, i was just wondering what are other people's thoughts about it
I'm suffering same problem
i want to have the browser and messenger at the same time
it close one after swetching to the other
i have 80mb free ram
I had the same problems, although lack of multitasking appeared on my stock rom, not a custom... sgs couldn't handle faceboom messager, viber, and a browser at the same time, everytime I switch from my browser to something else - it gets killed, which is frustrating
at the same time I saw how nexus s work, and how much free memory it has, compared to mine, the difference was huge!
I tried cyanogen at first, which was very close to stock nexus s, but it doesn't work good with sgs's camera and crashes once in a while
so eventually I installed JVT with voodoo and uninstalled different samsung stock apps, which gave me about 50mb of additional RAM compared to stock, and there doesn't seem to be any aggressive memory cleaners working, so I can now finally switch between all the apps I need
If you want the best roms for multitasking, go for the final builds of Froyo 2.2.1. They have plenty of free ram and are very smooth. I'd recommend Froyo ZSJPK. You can download it from XDA.
I think it depends on the ram settings in your ROM. The way android works is there are a bunch of system settings on how much ram to keep clear, and if it drops beneath certain values they start killing apps.
It's highly possible these values were tweaked in the custom roms, to improve the perceived smoothness and so on, but at the same time reducing multitasking. There's a trade off between performance and multitasking (guess why apple was so reluctant to add multitasking?)
I'm not really an expert on it, but I'm sure some quick searches around will find out where those values are and how to change them.. some rom/app probably even allows you to tweak them to your liking.
All Gingerbread roms do the same, closing apps after moving away from this, don't know why, but froyo didn't do this and ginger does.
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
MaoJie said:
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
Click to expand...
Click to collapse
ok i downloaded galaxy tuner but idk how to change threshold
I have a Droid A855 rooted, CM7 installed. I have the latest build. I have two issues, one is that the free RAM is ridiculously low with like 5 apps open it has about 20MB of RAM free. This is unacceptable because my Huawei Ascend has 90 free with many apps open, and the Droid has twice the ram of the Ascend. Is there any suggestions about this? Also the camera was working great and then it started freezing, and now the camera force closes when I press the button to take a picture. If I go to the camcorder it works fine, but otherwise I get force close. Any help would be greatly appreciated.
AtmosFEAR4701 said:
I have a Droid A855 rooted, CM7 installed. I have the latest build. I have two issues, one is that the free RAM is ridiculously low with like 5 apps open it has about 20MB of RAM free. This is unacceptable because my Huawei Ascend has 90 free with many apps open, and the Droid has twice the ram of the Ascend. Is there any suggestions about this? Also the camera was working great and then it started freezing, and now the camera force closes when I press the button to take a picture. If I go to the camcorder it works fine, but otherwise I get force close. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Personally CM7 has just never ran smooth. No matter what I have tried. Gingerbread was never really meant for the Droid so most roms have built in stuff to help with memory that I do not believe CM7 ever had added. and the camera is outright terrible lately, I have it force closing on all my roms. I really don't know how to help all I can really try suggesting is trying out other roms
durandgir said:
Personally CM7 has just never ran smooth. No matter what I have tried. Gingerbread was never really meant for the Droid so most roms have built in stuff to help with memory that I do not believe CM7 ever had added. and the camera is outright terrible lately, I have it force closing on all my roms. I really don't know how to help all I can really try suggesting is trying out other roms
Click to expand...
Click to collapse
Thanks for the quick reply, I beg to differ on the Gingerbread not being for the droid part, my old Ascend runs Gingerbread Cm7 with flying colors, and this droid has double the performance...
AtmosFEAR4701 said:
Thanks for the quick reply, I beg to differ on the Gingerbread not being for the droid part, my old Ascend runs Gingerbread Cm7 with flying colors, and this droid has double the performance...
Click to expand...
Click to collapse
Try Peter Alfonsos GB, I found that it gave me the most amount of free ram at any time
taptaptouch said:
Try Peter Alfonsos GB, I found that it gave me the most amount of free ram at any time
Click to expand...
Click to collapse
Hmm
Sent from my Droid using xda premium
I think you guys are missing a crucial part about how Android is built. Free RAM is wasted RAM.
Newer versions of Android, especially Gingerbread, are better at RAM management than older versions. Granted, there's an ever-growing need for more RAM for basic system functions, but Android is designed to free up RAM on-demand for the things that need it.
Just because RAM isn't free doesn't mean that the system is going to slow down. Android will put the stuff that's not being used anymore into a swap file so that the stuff you need to work with can do what it wants.
projektorboy said:
I think you guys are missing a crucial part about how Android is built. Free RAM is wasted RAM.
Newer versions of Android, especially Gingerbread, are better at RAM management than older versions. Granted, there's an ever-growing need for more RAM for basic system functions, but Android is designed to free up RAM on-demand for the things that need it.
Just because RAM isn't free doesn't mean that the system is going to slow down. Android will put the stuff that's not being used anymore into a swap file so that the stuff you need to work with can do what it wants.
Click to expand...
Click to collapse
Yes but the ram is going so low that it is closing my applications like music when I go to a different screen.. it's frustrating
information ++
sfahadzb said:
information ++
Click to expand...
Click to collapse
What? I dont understand
I agree with you and I will like to agree with you but it just won't work. This is like Windows Vista, they use all the memory, but it is very slow when you try to open application which you don't use a lot.. and it also causes a lot of slowness when you try to use more ram for soemthing else, like modify a huge image in photoshop and then switch to some other application.
Get back to the real story, my phone get memory lower than 50 free MB easily. and when I open Google current in this stage, it just hangs for 5 minutes. then I get a message "force closed". However, if I have 100 free MB, then I am safe, I don't see that popup message. Moreover, when I go to 40 free MB, I even have hard time to open skype and pick up the phone, it just rings, but the screen just hangs! when the screen refresh back, people get into mailbox already....
anyway, I found a software to temp solve this problem ZDbox. I set up when the screen hangs, "kill all apps in the memory" it is not best, but at least I can pick calls, I can run application without getting "force closed" message all the time.. because I need to reboot few times a day to solve ram issue.
perhaps, you can do a test yourself.
- install CM7
- install facebook app and run
- install google reader and run
- install google current and run
- install skype and run
- install gmail and run
- install google voice serach and run
- install google book and run
- install whatsapp and run
- install naver LINE and run
- install twitter and run
- install zdbox and run
- install lookout and run
- install go laucher
well after all this, your phone show be in less than free 50MB.. if so, try to run other application and you will see the problem.. screen hangs.....very slow response....not able to pick calls...
projektorboy said:
Just because RAM isn't free doesn't mean that the system is going to slow down. Android will put the stuff that's not being used anymore into a swap file so that the stuff you need to work with can do what it wants.
Click to expand...
Click to collapse
Yeah but even though "free ram is wasted ram" it still causes instability and force closes along with just pure out lag. My D1 lags when it has only 30mb of ram or less anything over 50 and it flies along. It lags to the point were even simple tasks are slow when they should not be.
AtmosFEAR4701 said:
I have a Droid A855 rooted, CM7 installed. I have the latest build. I have two issues, one is that the free RAM is ridiculously low with like 5 apps open it has about 20MB of RAM free. This is unacceptable because my Huawei Ascend has 90 free with many apps open, and the Droid has twice the ram of the Ascend. Is there any suggestions about this? Also the camera was working great and then it started freezing, and now the camera force closes when I press the button to take a picture. If I go to the camcorder it works fine, but otherwise I get force close. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Droid has 256MB RAM. (Actually, there's only 226MB RAM available to kernel.)
If the Droid has twice the RAM of your Huawei Ascend, then your Ascend has only 128MB RAM.
If it has 90MB RAM free with many apps open, then it means that all the system services and all the "many" open apps has to fit to 38MB of RAM.
That's hard to believe.
And btw., you can't compare RAM consumption on devices with different display resolution. Droid drives 854x480 pixels and uses hdpi bitmaps. I guess that the Ascend has lower resolution. The RAM demand is much higher on WVGA hdpi devices compared to low resolution HVGA/QVGA mdpi/ldpi devices.
When I my HTC Desire Z, I was in love, awe of the beautiful interface HTC Sense and the many adjustments I needed to make experience to a higher level, the Android. However, as I went about installing my wealth of applications, games and widgets (more than a hundred, are addictive), Sense started getting so instead of improving my experience. The initial screen would start every few hours re; each faucet took longer to record; Screen rotation when the keyboard sliding open continue for centuries; and each phone looked like he was struggling to get by.
Just a thought about memory utilization....
So Oneplus 3 is the first mainstream (not the first overall) android phone with 6Gb. Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones. There is really no point in wasted RAM. Having a lot of open apps in memory is truly great and could be the best use for it, but it also can present some issues. Background apps on android are not always suspended in the best way and can waste resources (CPU, battery). Of course if app and system are optimized correctly this shouldn't happen, but unfortunately it is not always the case. While google optimizes the system with dose features etc, I'm wondering about a simpler option until the better one is built into the system.
RAM is 10 times faster than storage, so why not use a portion of it as a RAMDISK, like in old days (MS DOS times). For those who don't know, RAMDISK is a portion of RAM that is used as a temporary storage (like flash memory), that will be 10 times faster than permanent flash storage.
Basically out of 6Gb RAM that phone has (Oneplus 3), 3Gb would be used as regular RAM and 3GB would be used as a RAMDISK. RAMDISK completely looses all the data after reboot, but the good thing is that phones don't really need to be restarted often. So RAMDISK would be almost permanent. Lets say you have 100 apps on your phone. Out of those you use 30 all the time. It is a bit inconvenient when app that you use often (for example Facebook) is kicked out from the memory and has to reload from flash storage (slow). Instead you could have those 30 apps to be loaded/copied/synchronized to the RAMDISK during initial boot. If app is kicked from regular RAM and needs to be restarted/resumed it would load 10 times faster from the RAMDISK. During regular intervals and before reboot data/cache from RAMDISK can be permanently saved (synchronized) back to the flash storage. If you have your favorite app that keeps misbehaving in the background (uses too much CPU, doesn't let phone to go into deep sleep and kills battery) you can just have it removed from background processes (swipe away, greenify, kill it etc), but then it will be almost instantly reloaded from RAMDISK when you need it later. So in the end you would have all your favorite apps loading super fast, even if it is not currently running in the background. You would sacrifice some RAM for faster app loading, possibly also minimizing battery loss due to some bad apps.
My knowledge of Android system is very limited and I might be very mistaken regarding this option, it's implementation and benefits. I would love to hear what people with better knowledge can say on this topic.
Droff said:
Just a thought about memory utilization....
So Oneplus 3 is the first mainstream (not the first overall) android phone with 6Gb. Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones. There is really no point in wasted RAM. Having a lot of open apps in memory is truly great and could be the best use for it, but it also can present some issues. Background apps on android are not always suspended in the best way and can waste resources (CPU, battery). Of course if app and system are optimized correctly this shouldn't happen, but unfortunately it is not always the case. While google optimizes the system with dose features etc, I'm wondering about a simpler option until the better one is built into the system.
RAM is 10 times faster than storage, so why not use a portion of it as a RAMDISK, like in old days (MS DOS times). For those who don't know, RAMDISK is a portion of RAM that is used as a temporary storage (like flash memory), that will be 10 times faster than permanent flash storage.
Basically out of 6Gb RAM that phone has (Oneplus 3), 3Gb would be used as regular RAM and 3GB would be used as a RAMDISK. RAMDISK completely looses all the data after reboot, but the good thing is that phones don't really need to be restarted often. So RAMDISK would be almost permanent. Lets say you have 100 apps on your phone. Out of those you use 30 all the time. It is a bit inconvenient when app that you use often (for example Facebook) is kicked out from the memory and has to reload from flash storage (slow). Instead you could have those 30 apps to be loaded/copied/synchronized to the RAMDISK during initial boot. If app is kicked from regular RAM and needs to be restarted/resumed it would load 10 times faster from the RAMDISK. During regular intervals and before reboot data/cache from RAMDISK can be permanently saved (synchronized) back to the flash storage. If you have your favorite app that keeps misbehaving in the background (uses too much CPU, doesn't let phone to go into deep sleep and kills battery) you can just have it removed from background processes (swipe away, greenify, kill it etc), but then it will be almost instantly reloaded from RAMDISK when you need it later. So in the end you would have all your favorite apps loading super fast, even if it is not currently running in the background. You would sacrifice some RAM for faster app loading, possibly also minimizing battery loss due to some bad apps.
My knowledge of Android system is very limited and I might be very mistaken regarding this option, it's implementation and benefits. I would love to hear what people with better knowledge can say on this topic.
Click to expand...
Click to collapse
Never mind, wrong post.
gee2012 said:
Did you read this http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/.
Click to expand...
Click to collapse
It is not about fixing the number of apps that can be held in memory, it is about different use for the RAM. When you have 40 apps in the background some of them can kill the battery. That is probably why Oneplus limited the number of apps. RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Droff said:
Did you read the post? It is not about fixing the number of apps that can be held in memory, it is about different use for the RAM. When you have 40 apps in the background some of them can kill the battery. That is probably why Oneplus limited the number of apps. RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Click to expand...
Click to collapse
I corrected my post didn`t i?
gee2012 said:
I corrected my post didn`t i?
Click to expand...
Click to collapse
I wrote reply while you did the correction. I think it is good to leave my reply there anyways, in case if someone else misreads the topic. Let me know if you think otherwise.
Droff said:
I wrote reply while you did the correction. I think it is good to leave my reply there anyways, in case if someone else misreads the topic. Let me know if you think otherwise.
Click to expand...
Click to collapse
Its cool
Droff said:
Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones.
Click to expand...
Click to collapse
Could you explain further why you think it is not being utilised ?
Droff said:
RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Click to expand...
Click to collapse
Android can not address any RAMDISK, it just makes no sense here.
One Twelve said:
Could you explain further why you think it is not being utilised ?
Click to expand...
Click to collapse
Look at the amount of free RAM in average use. There will be plenty that is unused. Keeping lots of apps cached is the best use for the free ram, but in some cases those background apps need to be removed from the active memory to prevent app from keeping device awake (and killing battery as a result). For example RAMDISK would allow to greenify all the bad written apps, stopping them from draining the battery, but then reloading them back to the active RAM almost instantly (much faster than from flash storage), when user wants to access the app again.
This situation (RAM "waste") can sure change with advances in android system itself, but as of now I just think RAMDISK is not a bad option for new devices with a lot of RAM onboard. Apparently we will see android phones with 8Gb Ram pretty soon.
dragon-tmd said:
Android can not address any RAMDISK, it just makes no sense here.
Click to expand...
Click to collapse
There is no such thing currently, but it doesn't mean that it cannot be created (at least in my understanding) and implemented via kernel or just an application (background service).
Here is info from WiKi
https://en.wikipedia.org/wiki/RAM_drive
Here are the examples of programs/apps for PC:
http://www.radeonramdisk.com/software_downloads.php
http://memory.dataram.com/products-and-services/software/ramdisk
Here some more info:
http://www.pcworld.com/article/260918/how_to_supercharge_your_pc_with_a_ram_disk.html
Plenty more can be found online.
I remember we used to do that on the HD2 - it was pretty cool!
blackalice said:
I remember we used to do that on the HD2 - it was pretty cool!
Click to expand...
Click to collapse
Pity it was just Windows Mobile OS.
Droff said:
Look at the amount of free RAM in average use. There will be plenty that is unused.
Click to expand...
Click to collapse
The impression i got that was not all that ram was not available and was reserved for the system. To the point one questioned that 6GB was available, felt like less.
How much RAM does the OP3 mention as free after a restart ?
One Twelve said:
The impression i got that was not all that ram was not available and was reserved for the system. To the point one questioned that 6GB was available, felt like less.
How much RAM does the OP3 mention as free after a restart ?
Click to expand...
Click to collapse
It shows about 4.5Gb free. I'm yet to fully test OP3 and see my average memory usage, but I doubt that I will have less than 2Gb free
Droff said:
It shows about 4.5Gb free. I'm yet to fully test OP3 and see my average memory usage, but I doubt that I will have less than 2Gb free
Click to expand...
Click to collapse
4.5GB free implies its working as stated.
You're saying in use that memory gets reserved and drops, that is more than it should.
Do u have any ideas how can that be done?
Sent from my HTC 10 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
That would be really cool
Sent from my HTC 10 using Tapatalk
Xperia U Lover said:
Do u have any ideas how can that be done?
Sent from my HTC 10 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
That would be really cool
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
As far as I know, there is no RAMDISK app for android at this time. I would love try it out myself. Unfortunately I don't have much coding experience to create this app (or kernel).
On a side note, after more time with a 6Gb phone I can see that this RAM can get utilized quite a bit. After editing the build.prop to magical number 42 and running bunch of apps (regular operation, nothing really extreme), the free cache reported by OS (developer options) is 1.2GB - 1.3GB. at the same time in RUNNING SERVICES it shows 2.8GB free. SYSTEM got bloated to 2.0GB
From what I can see, the apps that I use didn't misbehave so far and even with such heavy load on RAM, my battery didn't take a hit. As a matter of fact I'm very surprised by battery performance so far, but I'm only 1/4 way through.
That being said, I would still love to create 2Gb RAMDISK from that 6GB and play with it more.
Man your battery life is really good!
Sent from my HTC 10 using Tapatalk
Actually, my RAM is well used and i am grateful for having 6 GB in the phone, that is, because i am using two profiles and on 4GB phones they were always operating at the limit. with the oneplus 3 finally this is over.
Praise the lord.
Hello fellow MI5 users,
I received my phone one week ago and I start having some issues with the RAM. In fact, at the start of the phone, it's already at 70% filled up which is too much for me. Indeed I use a lot of RAM and I'm that type of guy who let the apps running in background everytime because I keep opening them everytime. I was wondering if it was possible to have a link to a better ROM because I guess it's the problem and also a link for a tutorial on how to flash it I'm a newbie in this type of manipulation but I'm very interested so I hope you will help me guys. By the way, my MIUI version is the MIUI 8 Global 6.8.18. I honestly don't know what can i give as information but I'll answer ASAP at any questions
Have a good day
This is working as design - Android keeps apps in RAM to reduce I/O on resuming from background - faster & more energy efficient.
You can change the number of background processes via the development settings or you can kill apps on closing.
adwinp said:
This is working as design - Android keeps apps in RAM to reduce I/O on resuming from background - faster & more energy efficient.
You can change the number of background processes via the development settings or you can kill apps on closing.
Click to expand...
Click to collapse
I've seen that indeed but it was set at standard so I'll probably put it at 3 I guess. How should I set the memory optimization? I've read it should be set off, altough I tried middle and I feel comfortable like that?
Is it normal to start at 70% without anything started ?
Unitae said:
I've seen that indeed but it was set at standard so I'll probably put it at 3 I guess. How should I set the memory optimization? I've read it should be set off, altough I tried middle and I feel comfortable like that?
Is it normal to start at 70% without anything started ?
Click to expand...
Click to collapse
For the 3GB version? Pretty much. MIUI is horrible.
After booting I typically had 1.3GB / 3.0GB free but after a while this averaged to around 650MB free.
free ram is useless ram , which cant accelerate anything
ps2lover said:
free ram is useless ram , which cant accelerate anything
Click to expand...
Click to collapse
I know that but I need more because I use multi-task a lot. Is there a way to change the ROM so I have more space to work with? Even if the ROM itself is beautiful.
Indeed it's the 3gb version 32gb. It have lags sometimes and I think it's due to the full RAM. Can I have a link to a custom ROM which works fine on this device?
I'm a little confused, you want as much RAM available but you want as many processes in the background as well? That sounds contradicting to me. Memory optimization maps to ZRAM, if you set it off there will be no memory compression and thus even less processes will be kept in the background. If you set it high, you can have as many processes as possible, but there could be lag due to (de)compression time overhead.
Try different Rom
Try to use a different Rom. On the Stock Rom is a lot of bloatware which is using your RAM too.
First you need to get an Bootloader unlock permission and have to unlock the BL.
It could take up to 10 Days to get the permission from Xiaomi
http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
After that you have to flash a recovery like trwp via ADB. Google it for videos or threads how to do it.
http://forum.xda-developers.com/mi-5/development/recovery-twrp-xiaomi-mi-5-t3412123
After that you can flash a developer Rom.
I use the Resurrection Remix and it works fine. The CM 13 stucks in Bootloop. Maybe because I made a full wipe and had to sideload my rom.
Because you don't have a SD card option you have to have the room installed on your hard drive. But just follow the description below
http://forum.xda-developers.com/mi-5/development/unofficial-resurrection-remix-m-5-6-9-t3395945
It took me just 1 day to get the unlock permit but don't try do do it without it. You brick your phone.
The RR Rom works really fine. Fingerprint and everything. It has no bloatware and you have to get the gaps like in the description. Arm64 nano seems enough.
Good luck and fun with a great phone.
Normally the android system kills the unused apps even in background. But i also experienced lack in multitasking.
leledumbo said:
I'm a little confused, you want as much RAM available but you want as many processes in the background as well? That sounds contradicting to me. Memory optimization maps to ZRAM, if you set it off there will be no memory compression and thus even less processes will be kept in the background. If you set it high, you can have as many processes as possible, but there could be lag due to (de)compression time overhead.
Click to expand...
Click to collapse
I think you misunderstood the OP question, he wanted more free RAM at start in order to have as many as possible apps in the background.
lapocompris said:
I think you misunderstood the OP question, he wanted more free RAM at start in order to have as many as possible app in the background.
Click to expand...
Click to collapse
Yup exactly
Try trwp 3.0.2.0 with 3.0.2.1 people experience bootloop
Omied said:
Try trwp 3.0.2.0 with 3.0.2.1 people experience bootloop
Click to expand...
Click to collapse
In fact, I'm just doing some research before asking because I'm very new. I have found some videos but they are pretty old and not on this phone but I guess it works more or less the same way
lapocompris said:
I think you misunderstood the OP question, he wanted more free RAM at start in order to have as many as possible apps in the background.
Click to expand...
Click to collapse
OK, in that case, just open Security->Permissions->Autostart and disable those which aren't immediately needed upon start. I have 18 autostart items (mostly system monitoring & social media apps) and I usually start with 1.5 GB free RAM.