Develop Bugs

ram after 4.1

After I updated my phone to 4.1 i'm only showing 1.56GB of ram in the task manager app. Has anyone else had this problem?

I did notice that I lost a large chunk of free ram... 4.0.4, I used to consistently have about 1 gig free, now I stay around 500-600 megs free

I've noticed this with any 4.1 rom with touchwiz and bloatware.
It's much better using a custom 4.1 TW rom (bacon!!) with some bloatware removed.
Sent from my SGH-I747M using xda app-developers app

I sent an email to Samsung just now. Let's see what they say.
Anyway, this is def. NOT natural. If you bring up a terminal console and type "free" you will see it state that your phone only has 1.5 gigs of ram.
I'm wondering of project butter is using 500 megs of ram to do the speedup we're seeing...
Response from Samsung 2012-12-6:
Dear ycavan,
Thank you for your inquiry. We understand that the RAM of your phone was reduced after the upgrade made on youe phone. We do apologize for the inconvenience that these issues might have caused you. Thank you for bringing to our attention the issue of your phone model missing. We will forward this information to the appropriate department.
The possible reason why RAM of your phone was reduced after the upgrade made on youe phone is because of the new application that is installed on the phone which is part of the enhancement.
Do you have more questions regarding your Samsung Mobile Phone? For 24 hour information and assistance, we offer our new FAQ/ARS System - Automated Response System at http://www.samsung.com/support.
It's like having your very own personal Samsung Technician at your fingertips.
We appreciate your continued interest in Samsung products.
Sincerely,
Mark
Technical Support
End Response 2012-12-6.
My take-away is that they did, in fact, use the extra 512megs for a new application that is part of the enhancement. My guess is butter.

Its most likely just the system using that RAM, like pretty much every android phone on the planet
Sent from my SGH-I747M using xda premium

Wow. Big difference. I'm seeing the same.
I never thought 2GB would get so low available so quick.

Who cares, really?
I'd rather have my 2Gb completely filled up as it's most likely just cached applications anyway.
If need be, this memory will be released anyway by Android's garbage collector.
On the other hand, history shows us that every new iteration of Android needs more RAM, so that's kinda expected.
My GS1 only has 512Mb which is more than enough if running Android 2.x (Eclair, Froyo & Gingerbread) but rapidly falls short RAM if running ICS.

HiKsFiles said:
Who cares, really?
I'd rather have my 2Gb completely filled up as it's most likely just cached applications anyway.
If need be, this memory will be released anyway by Android's garbage collector.
On the other hand, history shows us that every new iteration of Android needs more RAM, so that's kinda expected.
My GS1 only has 512Mb which is more than enough if running Android 2.x (Eclair, Froyo & Gingerbread) but rapidly falls short RAM if running ICS.
Click to expand...
Click to collapse
free memory is waisted memory for some. I disagree when it comes to devices using a battery. Processes use memory and battery life...
I hate to see apps running in background even when I didn't use them since the last reboot. Self running apps grabbing infos about me suck. If Google dont want to stop these behaviors then its time for a new OS.
My next phone ?: http://www.youtube.com/watch?v=oG3tLxEQEdg&feature=colike

Bagbug said:
free memory is waisted memory for some. I disagree when it comes to devices using a battery. Processes use memory and battery life...
I hate to see apps running in background even when I didn't use them since the last reboot. Self running apps grabbing infos about me suck. If Google dont want to stop these behaviors then its time for a new OS.
My next phone ?: http://www.youtube.com/watch?v=oG3tLxEQEdg&feature=colike
Click to expand...
Click to collapse
You got it wrong.
Cached apps in memory do not actually run.
They are just left there so that they can start more quickly the next time you use them.

Bagbug said:
free memory is waisted memory for some. I disagree when it comes to devices using a battery. Processes use memory and battery life...
I hate to see apps running in background even when I didn't use them since the last reboot. Self running apps grabbing infos about me suck. If Google dont want to stop these behaviors then its time for a new OS.
My next phone ?: http://www.youtube.com/watch?v=oG3tLxEQEdg&feature=colike
Click to expand...
Click to collapse
RAM has to refresh whether it is used or not. The RAM has no idea if a particular bit is used or not.

The last ICS update also lowered the RAM to 1.59GB. I believe it has to do with how much RAM is assigned to the GPU. It is normal.

HiKsFiles said:
Who cares, really?
I'd rather have my 2Gb completely filled up as it's most likely just cached applications anyway.
If need be, this memory will be released anyway by Android's garbage collector.
On the other hand, history shows us that every new iteration of Android needs more RAM, so that's kinda expected.
My GS1 only has 512Mb which is more than enough if running Android 2.x (Eclair, Froyo & Gingerbread) but rapidly falls short RAM if running ICS.
Click to expand...
Click to collapse
I only care because of my past experience: the more apps I load, the more memory gets used, and the slower it runs. I tend to use a log of apps. Memory was a struggle on the ole' Captivate.
I want this phone to perform good for a while.

ewingr said:
I only care because of my past experience: the more apps I load, the more memory gets used, and the slower it runs. I tend to use a log of apps. Memory was a struggle on the ole' Captivate.
I want this phone to perform good for a while.
Click to expand...
Click to collapse
well then just close off some apps, I've never had a problem memory on this phone at all yet
Sent from my SGH-I747M using xda premium

My ram dropped to 1.59 since before Jellybean
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
Actually my first s3 when it released had 1.89 of ram but I sold it. This one I bought on black Friday only has 1.59
Sent from my SAMSUNG-SGH-I747 using xda premium

I'm curious what the International phones have since they only started with 1g
Sent from my SGH-I747M using xda app-developers app

If you dont want any back ground processes go to the developer options and limit the number of background processes
Sent from my SAMSUNG-SGH-I747 using xda premium

[DISCUSS] Why are background apps closing so much more quickly?

Currently running: CM 10.1, build 0319 stock kernel and cpu settings.
TL;DR - The Hercules and its 1GB RAM suddenly seem like it can't multi-task like it once could. However maybe its app developers just heinously demanding more resources so their apps can look amazingly fluid because they forcefully killed everything else in the back?
What's the deal?
I remember a time in yesteryear yonder, whence I would have 5-7 apps running in the back without breaking nary a sweat. SO WHAT THE HELL happened Android? That was back on Touchwiz and Gingerbread!
Today I can't have utorrent and chrome open simultaneously. TWO apps. For instance if I've utorrent downloading, ill switch to Chrome (recent apps switch; not open) and maybe answer a Whatsapp immediately after; utorrent will undoubtedly be killed and must be reactivated.
Now I understand that chrome and utorrent are naturally RAM heavy applications, but it helps further my point. Why are apps being killed so quickly today? Was it Touchwiz that was great at ram management? Was it gingerbread? Or have apps been slowly updating over the last two years and demanding more allocation of RAM from the get go so that everything else gets forcefully killed? I remember when the Hercules was announced and all the reviewers claimed 1GB was such a stupid amount of overkill RAM and we'll never see it taxed. Now that 2GB has become the standard with the introduction of the GS3, I theorize app devs are being more liberal in demanding resources from devices without giving too much consideration for older models. So apps are killed more frequently to make room to the foreground.
So why do you care?
-The stock stopwatch app will die if you run a few more apps afterwards. This is just derp. Really, try this yourself. Can you imagine your morning alarm was silently force killed because you were reading a website before bedtime?
-Some audio apps can be killed as well. ie Doggcatcher. Audio actually stops if certain conditions of apps are opened after Doggcatcher. Derp.
-Device slows to a complete crawl during the course of a day. I don't believe I've ever owned a device (clamshell Sammy, Blackberry or Android) that didn't exhibit facepalm-worthy memory leak issues. If Android was designed to have its RAM filled, why do slowdowns exist?
-Incoming phone calls suffer lag when re-acquiring attention. This seems bizarre because in About > System you can see the Hercules indicates it has 768MB RAM, indicating a quarter is reserved for system apps. Which means it shouldn't really have this problem.
-Application settings requesting 'Persistent Notifications' to ensure app foreground attention. Apps like Tasker, utorrent, Battery Guru request this to remain alive. Is this the solution now? And is this 100% immune if system requires the resources?
-Apps take longer to open. I can't quite pinpoint this. Just a feeling.
Alright man relax, the Galaxy S4 and HTC One come packing with 2GB
Upgrading to a new flagship doesn't seem to be the solution to stifle this issue. App developers are excellent at what they do and naturally want their product to look its best with the resources available to it. With 3D games exhibiting the capabilities of a Snapdragon 600 and Tegra 4, where's the incentive to tell either to slow down? This same logic can be directly applied to the smartphone spec war and the recurring battery life bottleneck story.
Excellent read here from Gizmodo:
http://gizmodo.com/5992917/battery-life-is-the-only-spec-that-matters
Click to expand...
Click to collapse
So what's your point?
I'm not sure I have one. I'm just observing whats happening. We are finally actually seeing applications that are pushing our hardware to its limits. While 1GB of onboard RAM used to be a drool inducing spec, 2GB is not really a huge leap considering the jump the Snapdragon S3 made to the S4, S4 Pro and now the 600 in magnitudes of processing power. 2GB would certainly be astronomical, if it took a trip back in time and only had to run 2011 apps. I guess my point is: I'm throwing a tantrum that the Hercules is showing its age, even if it's not its fault.
Forgive my rambling and lack of proof-reading. At work.

mettleh3d said:
Currently running: CM 10.1, build 0319 stock kernel and cpu settings.
TL;DR - The Hercules and its 1GB RAM suddenly seem like it can't multi-task like it once could. However maybe its app developers just heinously demanding more resources so their apps can look amazingly fluid because they forcefully killed everything else in the back?
What's the deal?
I remember a time in yesteryear yonder, whence I would have 5-7 apps running in the back without breaking nary a sweat. SO WHAT THE HELL happened Android? That was back on Touchwiz and Gingerbread!
Today I can't have utorrent and chrome open simultaneously. TWO apps. For instance if I've utorrent downloading, ill switch to Chrome (recent apps switch; not open) and maybe answer a Whatsapp immediately after; utorrent will undoubtedly be killed and must be reactivated.
Now I understand that chrome and utorrent are naturally RAM heavy applications, but it helps further my point. Why are apps being killed so quickly today? Was it Touchwiz that was great at ram management? Was it gingerbread? Or have apps been slowly updating over the last two years and demanding more allocation of RAM from the get go so that everything else gets forcefully killed? I remember when the Hercules was announced and all the reviewers claimed 1GB was such a stupid amount of overkill RAM and we'll never see it taxed. Now that 2GB has become the standard with the introduction of the GS3, I theorize app devs are being more liberal in demanding resources from devices without giving too much consideration for older models. So apps are killed more frequently to make room to the foreground.
So why do you care?
-The stock stopwatch app will die if you run a few more apps afterwards. This is just derp. Really, try this yourself. Can you imagine your morning alarm was silently force killed because you were reading a website before bedtime?
-Some audio apps can be killed as well. ie Doggcatcher. Audio actually stops if certain conditions of apps are opened after Doggcatcher. Derp.
-Device slows to a complete crawl during the course of a day. I don't believe I've ever owned a device (clamshell Sammy, Blackberry or Android) that didn't exhibit facepalm-worthy memory leak issues. If Android was designed to have its RAM filled, why do slowdowns exist?
-Incoming phone calls suffer lag when re-acquiring attention. This seems bizarre because in About > System you can see the Hercules indicates it has 768MB RAM, indicating a quarter is reserved for system apps. Which means it shouldn't really have this problem.
-Application settings requesting 'Persistent Notifications' to ensure app foreground attention. Apps like Tasker, utorrent, Battery Guru request this to remain alive. Is this the solution now? And is this 100% immune if system requires the resources?
-Apps take longer to open. I can't quite pinpoint this. Just a feeling.
Alright man relax, the Galaxy S4 and HTC One come packing with 2GB
Upgrading to a new flagship doesn't seem to be the solution to stifle this issue. App developers are excellent at what they do and naturally want their product to look its best with the resources available to it. With 3D games exhibiting the capabilities of a Snapdragon 600 and Tegra 4, where's the incentive to tell either to slow down? This same logic can be directly applied to the smartphone spec war and the recurring battery life bottleneck story.
Excellent read here from Gizmodo:
So what's your point?
I'm not sure I have one. I'm just observing whats happening. We are finally actually seeing applications that are pushing our hardware to its limits. While 1GB of onboard RAM used to be a drool inducing spec, 2GB is not really a huge leap considering the jump the Snapdragon S3 made to the S4, S4 Pro and now the 600 in magnitudes of processing power. 2GB would certainly be astronomical, if it took a trip back in time and only had to run 2011 apps. I guess my point is: I'm throwing a tantrum that the Hercules is showing its age, even if it's not its fault.
Forgive my rambling and lack of proof-reading. At work.
Click to expand...
Click to collapse
lol...I totally agree. My apps seem to close a lot quicker, yet my RAM never dips below 280 MB free. Don't really get it myself...

killed all for ground apps TouchWiz UI uses up 2gb of ram?

So this is pretty crazy and weird but I killed all the apps running in the background and it says I'm using up 2.07gb of Ram how is that possible?

gator9422 said:
So this is pretty crazy and weird but I killed all the apps running in the background and it says I'm using up 2.07gb of Ram how is that possible?
Click to expand...
Click to collapse
Why does it matter? There is a ton of memory in this phone, and the OS manages it very, very well. You don't need spare memory. This isn't Windows, you won't run out of memory. It stores what it thinks it needs in RAM and keeps it there for quick access. It uses all the memory all the time (or at least it should). One of the things that prevents lag is to have the stuff loaded and ready at a moments notice.
Its a question of how the OS runs, not how much memory its taking. I would prefer if they hid that stat all together, then people would stop fixating on it, and loading efficiency killing memory manager apps.
Much like running defrag on a modern hard drive (they are supposed to be fragmented, they work better and faster that way) Android is supposed to run 90-95% used memory.. ALL THE TIME. Its the way its designed, and it works better that way.

One of the biggest misconceptions on all of XDA is about used RAM in a phone. People are always saying "OMG, there is only 500mb of unused RAM on my phone, it's going to slow down to a crawl!".
Just to be clear and hopefully people will understand it....unused RAM is wasted RAM. It does NOT have anything to do with slowing your phone down or anything like that. If there is 1gb of free RAM on your Note 4, that's totally fine.
Android manages RAM very well, don't stress. That's actually way more than it needs. You can only have 200mb of RAM free and your phone would still run fine. It's the way it's supposed to work. We have more than enough RAM in this phone.
I just hope this misconception will finally go away. I see at least a few RAM threads in every device forum.

It doesn't matter to me it's just the fact that I don't have any apps open and TouchWiz itself uses up 2gb of Ram to me that's a lot js

gator9422 said:
It doesn't matter to me it's just the fact that I don't have any apps open and TouchWiz itself uses up 2gb of Ram to me that's a lot js
Click to expand...
Click to collapse
It truly is a misconception. Android, windows, nix, any OS, for that matter. You would want too see your RAM being utilized. I would prefer to have my RAM used than not used at all because any unused RAM is a wasted RAM. This is also same with CPU. Unutilized cores are wasted cores. When writing software, one of the best practices is to learn how to use the memory to its full potential. You would want necessary stuff in RAM because using them when needed is faster if they are already loaded in memory than reinitializing the modules again and again every time for use. As far as memory location, RAM still provides the fastest. This is why in many companies that used gigabytes of data in their databases, a common practice in databadse engine technology is that they would actually load entire gigabytes of frequently accessed tables in memory for extremely fast access.
In short, don't worry

Thank you for the replies like they say you learn something new everyday. I appreciate the input

I'm more curious to know how the system manages to use more RAM every year with every new device released. Are there really that many more new features every year where they gobble up RAM?

gator9422 said:
Thank you for the replies like they say you learn something new everyday. I appreciate the input
Click to expand...
Click to collapse
http://searchstorage.techtarget.com/definition/cache-memory

Techweed said:
I'm more curious to know how the system manages to use more RAM every year with every new device released. Are there really that many more new features every year where they gobble up RAM?
Click to expand...
Click to collapse
My first computer had 512 mb RAM and it was fine at the time. Of course, with newer releases, they develop more features. With more features, more modules are created to support those features. Hence, more RAM usage.

^Wow, I think my first PC might have had 512 kb of RAM.

fbauto1 said:
My first computer had 512 mb RAM and it was fine at the time. Of course, with newer releases, they develop more features. With more features, more modules are created to support those features. Hence, more RAM usage.
Click to expand...
Click to collapse
That's true but with Kit Kat we were supposed to get a leaner running OS so that it would run on even old devices with minimum RAM. And I don't see how Touchwiz by itself could add 1 GB of RAM usage between the Note 2 and Note 4.

I would disagree on wanting all the ram to be being used... On previous rooted phones I have had (GS2, GS3, GSA4) getting rid of bloatware/useless apps eating up my ram made it much more responsive and fluid when opening new programs while significantly increasing battery life. Seems people just spew the bull**** marketing lines of Google across the internet and expect people to take it as truth. User experience is what is important, and getting rid of the garbage on any android version will make it faster. Not a difficult concept to understand.

rcracer_tx said:
I would disagree on wanting all the ram to be being used... On previous rooted phones I have had (GS2, GS3, GSA4) getting rid of bloatware/useless apps eating up my ram made it much more responsive and fluid when opening new programs while significantly increasing battery life. Seems people just spew the bull**** marketing lines of Google across the internet and expect people to take it as truth. User experience is what is important, and getting rid of the garbage on any android version will make it faster. Not a difficult concept to understand.
Click to expand...
Click to collapse
There is no bull**** here. Attend college and find out.
It is proven practice to use RAM
My source:
Myself with 15+ years as a software engineer

^^^This man speaks the truth. In my final year of my degree in software development and RAM utilization is common practice. User experience is different for everyone and what you "feel" is faster may or may not be an improvement.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

I think the goal of debloating should be to reduce the use of cpu by unwanted applications and reducing the amount of RAM taken up by them so that other applications may be cached instead. Whenever I debloat I start with watching applications that load and try to trim of the ones I know I don't need at all. I then move onto greenifying applications that run or cache themselves that I'll rarely use. Never in this process do I try to maximize free memory since doing so means applications that are not cached will take longer to launch. Im not sure if this is the right philosophy but it seems effective to me.

fbauto1 said:
There is no bull**** here. Attend college and find out.
It is proven practice to use RAM
My source:
Myself with 15+ years as a software engineer
Click to expand...
Click to collapse
I already have two degrees from a major big 12 university. And do a good amount of IT work for the business I work at. If you think that having your ram eaten up by programs you never use is good practice, maybe you need to re-evaluate the school you got your education. Using your logic our computers should be faster when they are full of **** running in the background... That's asinine. Full AND EFFICIENT utilization of ram is proven practice, not filling up ram full of bloatware.
muzzy996 said:
I think the goal of debloating should be to reduce the use of cpu by unwanted applications and reducing the amount of RAM taken up by them so that other applications may be cached instead. Whenever I debloat I start with watching applications that load and try to trim of the ones I know I don't need at all. I then move onto greenifying applications that run or cache themselves that I'll rarely use. Never in this process do I try to maximize free memory since doing so means applications that are not cached will take longer to launch. Im not sure if this is the right philosophy but it seems effective to me.
Click to expand...
Click to collapse
Well said, I agree. I guess I didn't make the distinction of when freeing up ram being eaten up by crap that will never be opened, What I mean is that cached memory being freed up is then able to be used by apps that I actually use. If over 2gb out of 2.92gb is being used all the time, (with the vast majority being eaten up by bloatware and the rest just being the base OS/UI) then that is not efficient utilization of ram. If you have to kill cached programs constantly and then load the new program you begin using, its going to take longer than having that program already having everything cached. In most times this is only milliseconds difference, but the fluidity of the transition is important to many as it is a significant factor in user experience. Who wants a phone that lags whenever a user input is made?

rcracer_tx said:
Well said, I agree. I guess I didn't make the distinction of when freeing up ram being eaten up by crap that will never be opened, What I mean is that cached memory being freed up is then able to be used by apps that I actually use. If over 2gb out of 2.92gb is being used all the time, (with the vast majority being eaten up by bloatware and the rest just being the base OS/UI) then that is not efficient utilization of ram. If you have to kill cached programs constantly and then load the new program you begin using, its going to take longer than having that program already having everything cached. In most times this is only milliseconds difference, but the fluidity of the transition is important to many as it is a significant factor in user experience. Who wants a phone that lags whenever a user input is made?
Click to expand...
Click to collapse
It is interesting that the vast majority of 2GB of your RAM is being using by bloatware. Between the Touchwiz function for turning off unneeded apps and Android's algorithms for determining what should be kept in memory, I find that "bloatware" apps (i.e., app I don't use) are practically non-existent in RAM...at least for me. That said, even if you still have 0.92 GB free, Android is not likely to decide it needs to kill an existing process to accommodate another program.

rcracer_tx said:
I already have two degrees from a major big 12 university. And do a good amount of IT work for the business I work at. If you think that having your ram eaten up by programs you never use is good practice, maybe you need to re-evaluate the school you got your education. Using your logic our computers should be faster when they are full of **** running in the background... That's asinine. Full AND EFFICIENT utilization of ram is proven practice, not filling up ram full of bloatware.
Well said, I agree. I guess I didn't make the distinction of when freeing up ram being eaten up by crap that will never be opened, What I mean is that cached memory being freed up is then able to be used by apps that I actually use. If over 2gb out of 2.92gb is being used all the time, (with the vast majority being eaten up by bloatware and the rest just being the base OS/UI) then that is not efficient utilization of ram. If you have to kill cached programs constantly and then load the new program you begin using, its going to take longer than having that program already having everything cached. In most times this is only milliseconds difference, but the fluidity of the transition is important to many as it is a significant factor in user experience. Who wants a phone that lags whenever a user input is made?
Click to expand...
Click to collapse
You are comparing RAM utilization to bloatware?
Where did you get your degrees, eBay?

fbauto1 said:
You are comparing RAM utilization to bloatware?
Where did you get your degrees, eBay?
Click to expand...
Click to collapse
No... he's not. Read it again. His point is that programs he doesn't need utilizing ram is bad.
We're playing a game of semantics here. He is working the angle that the original posts saying 'using ram is good' isn't true if it is crap that is using it.
Silly discussion at this point as both sides are correct based on the parameters of their view point.
Sent from my SAMSUNG-SM-N910A

How much free RAM do you guys have?

Is that normal? How much free RAM do you guys have?

doesn't look like it, but mine is the same. I believe it is the lollipop memory leak issue...so as usual we just have to wait it out

Sucks that just as we are finally seeing 3 Gig of RAM we end up in the same situation as when we had 2Gig ?
I have not upgraded to to 2015 Flagship Standard yet but ...
I was hoping to START at the beginning of Boot Up with about
1.7 -2 GIGs of free RAM for Tasking etc.
I think " upgrading" to Lollipop on many Devices could create more problems than it solves - right ?
And the supposed Wifi Calling and VoLTE are not going to work
because they are Carrier Specific Software which must come directly from your Service Provider.

Free RAM is UNUSED/WASTED RAM! Understand? The more software/applications that are pushed into RAM the better because it is available to do whatever it needs to do without having to go and search for it and place into RAM! If and when you need more RAM for something new, say like opening another application...then Android will move out of RAM whatever is not being used and replace it with the new software. If your phone had 10GB of RAM it would still look nearly full. This is a GOOD thing. It's all still available for use when needed. Remember that RAM is always the fastest part of your phone. Of course the more RAM you have the more applications you can have open at any one time without any lag/stutter. But for now 3GB of RAM is quite good for a cell phone on Android.

XxKINGxX2580 said:
Is that normal? How much free RAM do you guys have?
Click to expand...
Click to collapse
Is that a built-in app showing you that?

DanRyb said:
Is that a built-in app showing you that?
Click to expand...
Click to collapse
Yes. it's called Smart Manager.

XxKINGxX2580 said:
Yes. it's called Smart Manager.
Click to expand...
Click to collapse
I just found it a few hours ago but thanks for replying LOL. This is my first Samsung that I'm using TouchWiz in years haha.

jaseman said:
Free RAM is UNUSED/WASTED RAM! Understand? The more software/applications that are pushed into RAM the better because it is available to do whatever it needs to do without having to go and search for it and place into RAM! If and when you need more RAM for something new, say like opening another application...then Android will move out of RAM whatever is not being used and replace it with the new software. If your phone had 10GB of RAM it would still look nearly full. This is a GOOD thing. It's all still available for use when needed. Remember that RAM is always the fastest part of your phone. Of course the more RAM you have the more applications you can have open at any one time without any lag/stutter. But for now 3GB of RAM is quite good for a cell phone on Android.
Click to expand...
Click to collapse
This right here, folks.

jaseman said:
Free RAM is UNUSED/WASTED RAM! Understand? The more software/applications that are pushed into RAM the better because it is available to do whatever it needs to do without having to go and search for it and place into RAM! If and when you need more RAM for something new, say like opening another application...then Android will move out of RAM whatever is not being used and replace it with the new software. If your phone had 10GB of RAM it would still look nearly full. This is a GOOD thing. It's all still available for use when needed. Remember that RAM is always the fastest part of your phone. Of course the more RAM you have the more applications you can have open at any one time without any lag/stutter. But for now 3GB of RAM is quite good for a cell phone on Android.
Click to expand...
Click to collapse
Come on... I have Galaxy S4 now (going for S6 today). The S4 comes with 1.8GB usable memory but when it reaches arount 1.5 GB it starts lagging, and by lagging I mean a lot! The fact is that when the device has less RAM it gets laggy and it works better when it has more free memory.
Anyway the higher memory usage is probably of how Lollipop works - it preloads the entire app in the RAM instead of loading it from the flash. It is meant to speed up loading but it takes more memory and I can argue for the effect.

once there are some custom roms, this "issue" will be addressed.
until then, you just have to deal with it

How much free RAM do you have?

Hi everyone,
Been using my G4 for just over a week now and have noticed that the free RAM drops significantly after some use (just a few hours), on average I have about 80% RAM used meaning that I have around 550MB free, now I haven't noticed any slow downs/lags but am just curious, how much free RAM do you have and what kind of user are you? Lets gather some facts. I am a relatively light user, probably have less third party apps than the amount of apps preloaded (Google + LG).
Note: I am running the latest version of LG's stock MM, no root.

ShinOrochiX said:
Hi everyone,
Been using my G4 for just over a week now and have noticed that the free RAM drops significantly after some use (just a few hours), on average I have about 80% RAM used meaning that I have around 550MB free, now I haven't noticed any slow downs/lags but am just curious, how much free RAM do you have and what kind of user are you? Lets gather some facts. I am a relatively light user, probably have less third party apps than the amount of apps preloaded (Google + LG).
Note: I am running the latest version of LG's stock MM, no root.
Click to expand...
Click to collapse
Android is dicfrent than windowz android manages ram on its own if it runs low itll clear itself to make room for the new i run about the same. All these task killers waste battery now. Its ok leave it be. Ever since kk adroid handles much better

Yes using RAM in modern Linux systems and in Android means that the operating system pre caches things to actually speed up your device.
You had to went away from the idea of having as much free RAM as possible. Having unused RAM is actually a waste of resources isn't it? Why not using that free resources when not needed? Well and the result is a more or less intelligent handling of RAM usage where you will see high RAM usage.
So if you have less free amount of RAM it means all is fine :laugh: :victory:
Sent from my LG-H815 using XDA Labs

I also would like to point that apps like Messenger used around 80mb in my S4 Mini (with 1.5GB) and the same version of the app uses around 150 in this phone. So android is doing its good work using the memory efficiently so you have the best efficiency when switching apps and so.
Sent from my LG-H815 using Tapatalk

I was reading this article which pretty much explained everything RAM related. I used to own the OnePlus X which also had 3GB of RAM and with that I had around 1.5GB free, with the G4 I have less than half that . Then again the OPX pretty much ran on AOSP android with is feature-less.

anytime enough.You run out ram? Your device freezing?

kabirjedi said:
anytime enough.You run out ram? Your device freezing?
Click to expand...
Click to collapse
No my device doesn't freeze, I get occasional stutters/lags but these are minor. So it is not really a major issue, I was just curious. It is all about the balance, AOSP=fastest performance but least features, custom UIs=slower performance but much more features, for me the features and UI presentation are most important, I can slightly compromise on performance, AOSP is just plain boring, nothing about the UI appeals to me.