Database Develop

[Q] Full RAM after using a some apps... with a little analysis

After fixing some lags with I/O system by using filesystem LagFix I still have a Lag problem in my system and I think it's not related to Samsung.
I think this could be an Android problem.
After a fresh reboot I get 124MB of free RAM.
BUT... every day I need to reboot the phone because after 3 hours it became laggy.
Now I analysed this and read a bit about the memory management on several forums and was able to reproduce the lag 2minutes after reboot.
I just need to use much applications one after another to raise the RAM usage for every application.
When the free RAM reaches 40MB I think the system clears some pieces for using it for the app I now want to use and there is the LAG.
Is there any fix for Android not caching every activity of an application in the RAM?
Now for me Android feels like: Usage -> Full RAM -> Lag
Sorry for the new thread but after 2 hours of research I didn't find anything useful over search function.

Yea, every program should have as much ram available as their size. 2gig for program storage on sgs, so there should be the same amount of ram ;D Anyway, theres still less memory for programs on the sgs than for example in the N1. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Sent from my GT-I9000 using XDA App

Not just the RAM for the apps... there's much more...all mails from internet, all google talk conversations, the wather I checked out from internet with any widget, feels like every interaction is cached into the RAM until it reaches the 40mb mark and after that every interaction on my system is laggy... for example: opening the notification bar needs 2-3 seconds.
I already talked to N1 users with the same problem

DasLeo said:
I already talked to N1 users with the same problem
Click to expand...
Click to collapse
Heading out the door in a minute so can't comment on the rest, but I strongly disagree with that part of your statement.
As an N1 owner I've NEVER seen lag like I suffer on the SGS. Never seen the absolute FREEZE in the GUI like the SGS gets.
I'm running FroYo on the N1 now, so can't compare side-by-side to the SGS things like memory usage, but I don't think that's the issue here if you're going to use the N1 as a comparison, despite other users complaining of lag.
You might try Autokiller or the free memory manager app from the Market and see if that improves thing, they'll keep more or less memory free depending on settings. You could test how soon lag comes with default, minimal, and aggressive settings.

I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.

Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App

Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.

rkantos said:
. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Click to expand...
Click to collapse
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing

tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours

Guys please,
Getting off-topic here. Here is Android Development.
Not Q&A or General.
Please post in the right section.
Here is getting too many off-topics that pose no relation to Android Development.
Too cluttered.
Thanks

DasLeo said:
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours
Click to expand...
Click to collapse
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.

I use Memory Booster Lite (free version) app to free up memory, must do that manually but it works very well, if you buy the app it free up memory automaticly.

Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
The phone does have 512mb of ram. It just isn't used properly.
MOJO783010 said:
Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, wrong. The reserved ram is in the form of a ram disk, which seems to be a bit oversized. Not really sure why a ram disk is needed at all, personally.
sammy555 said:
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.
Click to expand...
Click to collapse
This is the correct solution. the JF* series of firmwares have very bad default settings for killing unused apps. Use this app to set them a bit better and you shouldn't have any problems.

Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
It does have 512 of ram, but some is partitioned off for the phone, so that you can always receive phone calls. Just about every device does this, because users would be more upset if they couldn't pick up the phone until they had closed a bundle of running programs. Don't you think that people here would have noticed earlier if the SGS physically had less ram than claimed ?
As far as the OP is concerned, sounds like you are just running too many programs at once. Its not an android problem, its user error.
Any task manager, but particularly an auto-killer will set you right, although alternatively you could try not leaving every app open when you're finished with it. You think your PC would run ok if you left one game open while you opened another ?

DasLeo said:
I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.
Click to expand...
Click to collapse
I wasn't comparing a N1 on FroYo to the SGS on Eclair. My comments were in regard to when I was on Eclair, which was several months...FroYo's only been available for a couple of months. What I said was since I'm on FroYo now, I can't compare side-by-side, but my experience with an N1 on Eclair was never any lag problem or GUI freezes.
Anyways, I also suggested you try Autokiller, and you missed that or misunderstood it by saying you already run a Task Killer (which is generally considered a bad idea, but I see you picked up on Autokiller after someone else suggested it. Enjoy.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
Nah, all phones advertise the actual chip size in it, not the amount the system actually lets you use.

tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
Thank you. This removes almost all lag I'm experiencing.

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] Weird RAM Managment.

Hi,
I have L90 D405n. I have a stock 4.4.2 LG ROM.
I also have installed more than a dozen apps. When I start my phone I have about 200MB free RAM memory. In the next 36h of constant work I have less and less free memory.
Right now before I restarted my L90 I had less than 50MB of free RAM and my apps where in "restarting" mode (settings > apps > running).
Did anyone of you noticed somethink similar ?

That's the thing with our device - it has too little RAM. That's why I have either unnecessary apps (the ones that came with the device and cannot be uninstalled) and their notifications disabled or you could greenify them with an app called Greenify. This basically suspends all the apps (also does it automatically when you lock the device). Also, if you're rooted and have your bootloader unlocked, you could flash CM11, which is based on stock Android. That should also use less RAM as it isn't skinned.
Personally, I rarely saw RAM go below 150MB, but the aforementioned solutions should help.

linasj said:
That's the thing with our device - it has too little RAM. That's why I have either unnecessary apps (the ones that came with the device and cannot be uninstalled) and their notifications disabled or you could greenify them with an app called Greenify. This basically suspends all the apps (also does it automatically when you lock the device). Also, if you're rooted and have your bootloader unlocked, you could flash CM11, which is based on stock Android. That should also use less RAM as it isn't skinned.
Personally, I rarely saw RAM go below 150MB, but the aforementioned solutions should help.
Click to expand...
Click to collapse
Greenify works only for a while, after a few more hours my phone is still out of memory. I also tried CM but it's not working properly on my device. 1GB of RAM is definitely not too little. My brother has MyPhone Cube (Polish manufacturer) he has no Greenify and a lot of apps installed. His phone still manages to get over 500MB of free RAM with all the apps kept in memory. Free memory doesn't shrinks with time on his phone.
So it's definitely a poor RAM managment solutions in L90 and a lots of crappy apps run in background. I can provide logcat and all the necessary log's if someone would like to look into it.

P.S. What is Lost RAM ?
I have over 70MB right now.

Xemidra said:
Greenify works only for a while, after a few more hours my phone is still out of memory. I also tried CM but it's not working properly on my device. 1GB of RAM is definitely not too little. My brother has MyPhone Cube (Polish manufacturer) he has no Greenify and a lot of apps installed. His phone still manages to get over 500MB of free RAM with all the apps kept in memory. Free memory doesn't shrinks with time on his phone.
So it's definitely a poor RAM managment solutions in L90 and a lots of crappy apps run in background. I can provide logcat and all the necessary log's if someone would like to look into it.
Click to expand...
Click to collapse
Then again, it runs almost pure stock Android, while L90 is pretty heavily skinned. Yeah, Greenify is a bet in this case. I myself had it working well in some cases and not so well in other.
I tried (and suggested) probably a good majority of the solutions there are, so it might be up to LG to figure this out (if they're aware of it). But rest assured, you're not the only one with RAM issues. If it weren't for them, it'd probably be an even better device.

linasj said:
Then again, it runs almost pure stock Android, while L90 is pretty heavily skinned. Yeah, Greenify is a bet in this case. I myself had it working well in some cases and not so well in other.
I tried (and suggested) probably a good majority of the solutions there are, so it might be up to LG to figure this out (if they're aware of it). But rest assured, you're not the only one with RAM issues. If it weren't for them, it'd probably be an even better device.
Click to expand...
Click to collapse
CarbonROM worked very nice on my phone but it had serious problem with theme engine (it's a ****ty function) and it disables my clock alarm causing SystemUI force close. Fonts on any CustomROM aren't that sharp like in stock, camera performance and quality is a lot worse and entirely useless IR because it's not working at all. It's also quieter than stock.
I don't understand why manufacturers are stubborn and they are forcing their own overlays. Android could work as fast and stable as Windows Phone if they would start using clean Android.

Xemidra said:
CarbonROM worked very nice on my phone but it had serious problem with theme engine (it's a ****ty function) and it disables my clock alarm causing SystemUI force close. Fonts on any CustomROM aren't that sharp like in stock, camera performance and quality is a lot worse and entirely useless IR because it's not working at all. It's also quieter than stock.
I don't understand why manufacturers are stubborn and they are forcing their own overlays. Android could work as fast and stable as Windows Phone if they would start using clean Android.
Click to expand...
Click to collapse
THIS. I wish Google would pressure OEMs just so that they'd skin Android less. Hell, I would've gotten a Motorola or a Nexus device if I could, but I can't really buy a Motorola device where I live (unless off of Ebay or Amazon, but I guess I'm a bit worried about buying things like that there). Albeit Nexus 5 being quite a budget phone, it's still out of my league. For now.

Memory management (keep maximum in ram)

All I would like to do is to keep apps maximum is possible in ram. My goal is for my daily use of most common apps like phone, whatsapp, google messenger, gmail, contacts, calendar etc. to keep them in ram so switching between them is smooth and fast without loading on anything. My memory is always more then 50% empty and little apps like calendar or contact are getting killed with no reason. That is really going on my nerves more and more.
I am on Pure Nexus CMTE rom and I have tried playing with Kernel Auditor low memory killer and virtual memory settings. What ever I do there my ram usage is always about 1 - 1.4 GB newer more then that. How I can force system to keep apps in ram until critical point? Like in my case with more then 50% of ram still available there should not be any apps removed from memory even if is app not active for some time. Can anyone please help me with this.

Possibly you see 1.5G free now, but it may have temporarily been a lot less free when the apps were killed (usage varies over time). See attached how high chrome can jump at its peak.
Just a thought..very half baked. I'm sure someone will give suggestions for what you want.

electricpete1 said:
Possibly you see 1.5G free now, but it may have temporarily been a lot less free when the apps were killed (usage varies over time). See attached how high chrome can jump at its peak.
Just a thought..very half baked. I'm sure someone will give suggestions for what you want.
Click to expand...
Click to collapse
Yes, I know but Chrome memory usage is still nothing compare to free memory available. I did some reading and end up creating local.prop file in root/data and add some lines there. How much that will help I will find out in day or two. If anyone is interested to know what I did I can post it here after.

Just wanted to add that in Android N preview the low memory kill settings by default were very light (like lighter than kernel adiutor's "very light" preset) and it resulted in very stuttery performance. Setting them back to marshmallow stock settings made everything smoother. Looking forward to anything you may uncover on this though.

StykerB said:
Just wanted to add that in Android N preview the low memory kill settings by default were very light (like lighter than kernel adiutor's "very light" preset) and it resulted in very stuttery performance. Setting them back to marshmallow stock settings made everything smoother. Looking forward to anything you may uncover on this though.
Click to expand...
Click to collapse
Okay this is what is confusing me the most. In Kernel Auditor "very light" preset means that apps will be removed soon is possible, very light means small amount of memory to be used. Am I correct? Aggressive on other hand will give more memory for apps, more apps in memory and less removing from it.
So if is that correct then is very understandable why "N" with less then "very light" preset made bad performance and soon you give it more memory to play everything is back to normal.
However I did test on that many times but in both cases my apps are getting removed from memory with more then 50% still available memory. That's why I need somehow to stop system from emptying memory until critical point. Maybe some build.prop lines can help but I am not really expert in that area.

Emilius said:
Okay this is what is confusing me the most. In Kernel Auditor "very light" preset means that apps will be removed soon is possible, very light means small amount of memory to be used. Am I correct? Aggressive on other hand will give more memory for apps, more apps in memory and less removing from it.
So if is that correct then is very understandable why "N" with less then "very light" preset made bad performance and soon you give it more memory to play everything is back to normal.
However I did test on that many times but in both cases my apps are getting removed from memory with more then 50% still available memory. That's why I need somehow to stop system from emptying memory until critical point. Maybe some build.prop lines can help but I am not really expert in that area.
Click to expand...
Click to collapse
What is the solution for Pixel 2 rom of LG Nexus 5X? os ur build prop gonna help for me? if yes plz replay.

MHS3511 said:
What is the solution for Pixel 2 rom of LG Nexus 5X? os ur build prop gonna help for me? if yes plz replay.
Click to expand...
Click to collapse
No idea man, I don't have LG Nexus 5 anymore. Today roms have that battery optimizations build in. Go there and make the app you like to be in memory "not optimized" and in Kernel auditor or any other app flashing memory to "very light". That should help. Good lack

6Gb RAM utilization option

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.