As smartphones evolved so did their components, jumping from single core processors all the way up to octa-core processors as we’ve seen in the Galaxy S6. RAM has also increased in size and speed over the years and today’s flagships are commonly found with 3GB or 4GB of RAM. In the Galaxy S6 and S6 Edge’s case this is 3GB of LPDDR4, the absolute fastest RAM on the market right now. What users would expect from not only having this much RAM but also the speed of it is of course speed and consistency in multi-tasking, being able to essentially pull up any app they’ve had open recently and not have to wait for it to reload yet again. What’s being reported is just the opposite of that however, and it’s getting on many users’ nerves.
The XDA Developers forum is rife with posts about this issue and it seems there are a number of problems. First we’re seeing users report that they often only have 200-300mb of RAM left, a sign that many users still don’t understand how RAM works. RAM is designed to be used, not to be empty, so having little “free” RAM is actually a good thing and shows that your device is working like it’s supposed to. RAM cleaners and that sort of thing should never, ever be used on Android as it defeats the purpose of how the OS works. Other users are reporting that apps often reload when being moved between, so jumping out of Chrome to chat in Hangouts results in Chrome needing to reload all the pages when the user comes back to it. This is a sign of a problem, as this basically should never happen with this much RAM.
It’s possible that Samsung has created an overzealous task scheduler that ends up killing apps too quickly in order to remove them from RAM. Thankfully this can be fixed with a pretty simple software update from Samsung, a problem that’s already been submitted to Samsung customer care by users. The other issue could lie with Android itself, specifically Android 5.0 Lollipop where we’ve seen RAM management issues since the release of the OS. These issues have apparently been fixed internally but have yet to roll out to any one version of Android on any phone, meaning all phones powered by Android 5.0 Lollipop exhibit this behavior to some extent anyway. Regardless Samsung could very well fix it themselves in a future update, and we’re definitely hoping they do to keep users happy.