SUroot
Extreme Android User
Exactly.
Slow ripple effect on lock screen is most likely due to low clock frequency of the CPU whilst it is coming out of "Sleep".
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help The RAM keeps on increasing until i restart my phone
- Thread starter silverblood990
- Start date
-
- Tags
- samsung galaxy s3
Exactly.
Slow ripple effect on lock screen is most likely due to low clock frequency of the CPU whilst it is coming out of "Sleep".
I totally understand what your saying and have understood what both you and SU have said. HOWEVER the S3 i9300 (international version) only has 1GB of ram. Yes this should be enough BUT it isnt due to some memory leak?
I have the same problem as the OP and the facts are:
When i reboot my phone i have around 550mb used up which makes the phone super fast.
3/4 days later the phone beings to lag (slow keyboard pop up, non smooth UI etc) and each time i notice the RAM is low, only 30 mb is free even if i clear all apps.
Sometimes if i change some of the rom settings, then change it back to what it was before, it sometimes fixes the lag and it shows i have atleast 150mb free RAM and my phone is back to being fast again.
Now i know your going to blame the ROM for being crap or something but NO..i have noticed this on several different roms as well as the stock S3 rom. Even if i check cached processes, it seems completely normal only 5 or so apps in there. I really dont understand the phone and makes me want to go back to apple again
This. This keeps happening. I've had S3 (Android 4.4.4) (I frankly don't remember this problem on S3, but I mostly used ArchiDroid, maybe the guy had a unique fix), Note 4 (Android 6) and Note9 (Android 9 and 10) with stock ROMs. The latter two have this problem. RAM slowly disappearing, no cleaning fixes it, only a reboot. It's not that bad on a 6GB device, but I can still see that the number of apps I can run concurrently and the number of tabs kept in memory is way worse 3 days after rebooting the phone than 1 day after doing so. What is this across multiple models and Android versions? How is it never getting fixed? What is eating up the RAM?
android is a very efficient at using ram. you actually want the phone to use up ram. since android is linux based any free ram becomes useless. the more ram used the better the phone should run. especially for apps. any app that uses ram is a good thing. by having the data in ram, it saves the app from re-writing the data over and over again.
by messing with ram you can potentially make things worse. by constantly clearing ram, your apps will have a harder time opening. this could also mess with your battery life and even slow your phone down. this is why it is not recommended that you use any ram booster apps that are out in the market.
i never had any issues with ram or anything and i have owned pretty much most of the note series phones. i have had note 2-5, i skipped the note 7, note 8, and i also skipped the note 9. i currently have the note 10+ and could not be any happier with my phone.
That's all good and understandable, and I don't even use RAM cleaners (only for experimental purposes, but it doesn't help with anything, obviously). What I'm miffed about is that there's usually something in the system that doesn't get released even when a single app demands extreme amounts of RAM, like a browser with lots of tabs. And somehow that unreleased RAM grows over time, unless a reboot is performed. Otherwise, the number of possible concurrent tabs in memory shrinks. Weird and annoying.
Hmmm, I'm with @ocnbrze with this one. I've never encountered anything like that either. I've had Android phones since the Nexus One and memory limits have never been a noticeable issue for me, even on some of the early Galaxy phones. You might want to look at installed apps or services. That sounds like something that's poorly coded to try and run multiple instances of itself. I personally am not a fan of Samsung phones, but the Mrs. loves them. She's currently got an S10e and the thing will prompt her to reboot her phone every week or so to "improve performance". Maybe Samsung's developers thought that was a better solution than writing decent apps?
There are two possible explanations which occur to me here. Unfortunately neither offers an obvious solution.
The first is simply that the RAM management is not as well tuned as it could be. The manufacturer does make some choices here, and some don't do as well as others. I have a Galaxy Note 10.1 (2014 edition) tablet and my previous phone was an HTC One (m7). The HTC had 2GB RAM while the Note had 3GB and was used more lightly than the phone, but it was always the tablet that did more app reloads and generally multitasked less well. Samsung do load more stuff into the ROM, but even so given the extra GB I always suspected their tuning was inferior. (As an aside, there have been much clearer-cut examples, such as the OnePlus software release for one device which always kept about half of the RAM free, with the result that it behaved like a phone with half as much RAM as it really had. The point is that the choices the manufacturer makes with their software can make a difference).
Unfortunately unless you are willing to root the phone there is nothing you can do here. If you do root it it's possible that there is a custom kernel out there that will manage this better, if this is the problem in the first place. But no guarantees.
The second is what's called a "memory leak". This is simply a bug, where something allocates memory but fails to deallocate it, with the result that RAM usage grows continually until something fails. This is a class of problem very familiar to C++ programmers, as C++ does not perform automatic garbage collection, but can occur in other languages too. If this is the cause then it could be a problem in one of your frequently-used apps (in which cases uninstalling or disabling it and using an alternative would fix it, if you knew what app it was), or it could be a problem with part of the OS (the manufacturer always has to adapt Android to their own hardware, and includes their own system apps and processes, so it's also possible for them to introduce bugs that aren't in the based Android version). In the latter case there will be nothing you can do unless you can root and find a custom ROM that doesn't have the problem. I was hoping I could find a system monitor on my phone that would tell me how much RAM each app was using, since something like that might enable you to identify the culprit (or might not: browsers naturally grow as you open tabs, so it would be hard to tell), but none of the ones I have seems to have that capability (at least not on my current unrooted phone).
I don't think this is a generic android feature, as I've never observed such behaviour myself. My current phone is on Android 11, so probably tells you nothing about your device, but even back when I was running Android 4 I never saw this type of thing, and would usually go months between reboots. But I never owned an S3 so don't know whether this was a common feature of that model.
The first is simply that the RAM management is not as well tuned as it could be. The manufacturer does make some choices here, and some don't do as well as others. I have a Galaxy Note 10.1 (2014 edition) tablet and my previous phone was an HTC One (m7). The HTC had 2GB RAM while the Note had 3GB and was used more lightly than the phone, but it was always the tablet that did more app reloads and generally multitasked less well. Samsung do load more stuff into the ROM, but even so given the extra GB I always suspected their tuning was inferior. (As an aside, there have been much clearer-cut examples, such as the OnePlus software release for one device which always kept about half of the RAM free, with the result that it behaved like a phone with half as much RAM as it really had. The point is that the choices the manufacturer makes with their software can make a difference).
Unfortunately unless you are willing to root the phone there is nothing you can do here. If you do root it it's possible that there is a custom kernel out there that will manage this better, if this is the problem in the first place. But no guarantees.
The second is what's called a "memory leak". This is simply a bug, where something allocates memory but fails to deallocate it, with the result that RAM usage grows continually until something fails. This is a class of problem very familiar to C++ programmers, as C++ does not perform automatic garbage collection, but can occur in other languages too. If this is the cause then it could be a problem in one of your frequently-used apps (in which cases uninstalling or disabling it and using an alternative would fix it, if you knew what app it was), or it could be a problem with part of the OS (the manufacturer always has to adapt Android to their own hardware, and includes their own system apps and processes, so it's also possible for them to introduce bugs that aren't in the based Android version). In the latter case there will be nothing you can do unless you can root and find a custom ROM that doesn't have the problem. I was hoping I could find a system monitor on my phone that would tell me how much RAM each app was using, since something like that might enable you to identify the culprit (or might not: browsers naturally grow as you open tabs, so it would be hard to tell), but none of the ones I have seems to have that capability (at least not on my current unrooted phone).
I don't think this is a generic android feature, as I've never observed such behaviour myself. My current phone is on Android 11, so probably tells you nothing about your device, but even back when I was running Android 4 I never saw this type of thing, and would usually go months between reboots. But I never owned an S3 so don't know whether this was a common feature of that model.