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...
Related
Hello I had read about the problem of stalling. In the OCLF thread, I read that this is due to the RFS used.
BTW anyone can verify if this is still the problem in Android 2.2 build.
Thanks.
Sent from my GT-I9000 using XDA App
dplate07 said:
Hello I had read about the problem of stalling. In the OCLF thread, I read that this is due to the RFS used.
BTW anyone can verify if this is still the problem in Android 2.2 build.
Thanks.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Still rfs in the leaked froyo builds; no one can verify what the official build will be like, because it hasn't been released yet.
Seems pretty unlikely that samsung would consider a change in fs for the i9000 at this stage in it's development. I think manufacturers like to stick to their own proprietary fs...
This is the 1st and the last time I purchase a Samsung Phone Android, no matter what we do, still crapy slow. I start to hate this phone.... Android is cool but I9000 phone have the best hardware but the software suck....
halabibk said:
I start to hate this phone.... Android is cool but I9000 phone have the best hardware but the software suck....
Click to expand...
Click to collapse
No device is perfect. Most problems are fixable, I think. If Samsung doesn't do it, I'm sure the talented developers in this forum will do something - that's the beauty of Android..
the voodoo kernel puts the phone to rights. with that fix, its the fastest thing on the market.
it's just a shame only a small minority of users will see the benefit and the phone will ultimately fail because of this.
are you reading this samsung?
chrissyg123 said:
the voodoo kernel puts the phone to rights. with that fix, its the fastest thing on the market.
it's just a shame only a small minority of users will see the benefit and the phone will ultimately fail because of this.
are you reading this samsung?
Click to expand...
Click to collapse
Hi, may I know what is the voodoo kernel? Can you please provide us with a link to the forum. Cheers.
chrissyg123 said:
the voodoo kernel puts the phone to rights. with that fix, its the fastest thing on the market.
it's just a shame only a small minority of users will see the benefit and the phone will ultimately fail because of this.
are you reading this samsung?
Click to expand...
Click to collapse
I'm sorry to say that even the voodoo kernel starts to lag after a while. I don't know whats wrong with this phone but I'm never ever buying Samsung again, no matter how nice the specs are.
cavinsoo said:
Hi, may I know what is the voodoo kernel? Can you please provide us with a link to the forum. Cheers.
Click to expand...
Click to collapse
public beta 2 should come online within short time
f samsung...this is the first time in my years and years of using a mobile phone that i have to learn about filesystems and mobile phones.....lol
Disagree
kmrdeva said:
No device is perfect. Most problems are fixable, I think. If Samsung doesn't do it, I'm sure the talented developers in this forum will do something - that's the beauty of Android..
Click to expand...
Click to collapse
True that no device is perfect, but for the money we pay to purchase such a device, we expect a product that works out-of-the-box, which is not the case for the Galaxy S.
Compared to the hardware Samsung put into it, its shockingly laggy and other phones in the market with half the hardware specs dont show such lag due to the tweaked software they have
A mobile phone is not just a piece of hardware, its the hardware with its software that enables the optimum use of the hardware and also the accompanying PC software where Samsung has yet failed through the horribel "Kies"
I am a big fan of android, but Samsung has tarnished android through this ****ty product
This will be clearly seen once a pure android 2.2 OS (with no samsung software on top) is available for the SGS with the proper file system and memory manager
There are 2 problems with the phone.
1. File System
2. Memory
File system can be fix by using lag fix. After you implement lag fix, you feel phone is snappy and fast and you start running and install tons of apps.
This started the 2nd problem, even though is 512MB ram, most you get is 200Meg usable, however with some background service it reduces to 130 on average. After few hours of apps used or longer time the available memory can drop down to 30Meg. This is when you feel the 2nd lag. Even with 80Meg ram available you will still feel lag, and swype start behaving funny.
This can only be solve or temp fix (some people say you shouldn't) if you use softwares like ATK, SystemPanel Apps. (Just KILL THEM ALL) when you feel your phone start to slow down and your phone will than be alive!!!
The real fix for the memory issue.. unfortunately.. i believe we need a phone with minimum 6 to 700MB free RAM. Than you should feel the phone responsive all the time until all the apps start clogging up the usable RAM.
I understand where you're coming from, regarding this. However, being somewhat of a tech freak, I am quite happy that so many tweaks have been developed by the experts here in this forum - my Galaxy S works well enough for me, rooted and sped up with the one-click-lagfix app.
My experience so far with Android on the Galaxy S (shortcomings and all) has generally been way better than my previous experiences with S60v5 on the Nokia 5800 and N97.
kmrdeva said:
I understand where you're coming from, regarding this. However, being somewhat of a tech freak, I am quite happy that so many tweaks have been developed by the experts here in this forum - my Galaxy S works well enough for me, rooted and sped up with the one-click-lagfix app.
My experience so far with Android on the Galaxy S (shortcomings and all) has generally been way better than my previous experiences with S60v5 on the Nokia 5800 and N97.
Click to expand...
Click to collapse
I am so so so so so so AGREE WITH YOU!!!!
Maybe that's why we appreciate the problems that comes with Android and SGS.
xtrememorph said:
There are 2 problems with the phone.
1. File System
2. Memory
File system can be fix by using lag fix. After you implement lag fix, you feel phone is snappy and fast and you start running and install tons of apps.
This started the 2nd problem, even though is 512MB ram, most you get is 200Meg usable, however with some background service it reduces to 130 on average. After few hours of apps used or longer time the available memory can drop down to 30Meg. This is when you feel the 2nd lag. Even with 80Meg ram available you will still feel lag, and swype start behaving funny.
This can only be solve or temp fix (some people say you shouldn't) if you use softwares like ATK, SystemPanel Apps. (Just KILL THEM ALL) when you feel your phone start to slow down and your phone will than be alive!!!
The real fix for the memory issue.. unfortunately.. i believe we need a phone with minimum 6 to 700MB free RAM. Than you should feel the phone responsive all the time until all the apps start clogging up the usable RAM.
Click to expand...
Click to collapse
I haven't had these problems for a long time, actually using a taskkiller makes it slower for me. Since JM* it's not possible anymore to have only 30Megs free as the least low memory killer level starts at around 40 Megs which turns into having 50ish free all the time. The only time i get lags is when installing apps but otherwise never with loads of apps installed. I use the oneclick lagfix btw.
The filesystem choice is not wise from samsung, the hardware and software interaction are because samsung is using Hummingbird processor and that google developed android to improve it on snapdragon because the nexus one is running it and most of the andro phones. So samsung has to "fix" android for their processor.
For the memory "issues" like I said on another topic
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Linux however isn’t generally affected by this. While I admit that I don’t know the architecture and reason for this… linux will run the same regardless of if you have 20mb free memory or 200mb.
Click to expand...
Click to collapse
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
I might be missing something coming from a Nexus 6, but the 2GB ram in my new 5x seems to always be full, and just full of Android OS.
I've rebooted and cleared the cache when it gets unbearable, but it seems to make little difference. In a day, I'm right back to maxed out ram and slowness (especially in the Camera app) ensues.
In fact, I've not seen anything less that 1.6 GB ram used, even after both those processes.
I'm probably in the minority (at least here on xda) who never looks at RAM. I've gone into the "memory" setting once since I've owned the phone (11 days). I haven't cleared cache. My 5X works 99% perfect as far as lag/stutters or slow performance, for my use. Do you play a lot of games or use huge memory intensive apps maybe or does your phone slow to a crawl often, could be an app/s?
Depends what you have running, honestly. I use my phone a fair amount. Mostly for texting or to quickly Google something, so I usually don't have 10 apps all running at the same time. Right now my phone is using 1.3gb of RAM. I barely check. I've never felt that it's needed more. That being said, I suppose you can try flashing the clean ROM that has surfaced in the Development forum if you're willing to Root and unlock the bootloader.
I've been noticing this as well.
My Nexus 5X usually runs at 1.3-1.4GB used and from what I've read that is a good thing because that means the RAM is being used efficiently by caching things used a lot and only freeing up memory when something else actually needs it. So far, after 10 days, I've only seen a very tiny bit of lag.
Yah it seems like 2GB is not nearly enough for moderate to heavy use. Another oddity is that the system tells me there is a sizable amount of free RAM (like 600~700 MB) when 3rd party apps say there is less than 200 MB left.
No problems here. Runs just as well (if not better) than my 2 year old Nexus 5.
compared to the S3 with nameless rom 5.0 (the only one that did not randomly freeze up) the 5X is fairly faultless with very few niggles
lopri said:
Yah it seems like 2GB is not nearly enough for moderate to heavy use. Another oddity is that the system tells me there is a sizable amount of free RAM (like 600~700 MB) when 3rd party apps say there is less than 200 MB left.
Click to expand...
Click to collapse
I'm guessing it's because of how memory is likely managed in Android and how the system vs 3rd party app report it. If you look at the Memory tab in the Resource Monitor on Windows 7 you will see memory that is "In Use" which is actually being used by programs. then you have memory that is "Stand By" which is memory that was used by previous programs/files but is technically "available" but keeping the old stuff there in case you use it again soon. If some thing else needs the memory then it is the stuff in "Stand By" that gets reallocated first. Then you have "Free" which really is free. I think Android memory management works in a similar way. If that is the case then the system might be showing you "Free" + "Stand By" since "Stand By" technically is available for use while the 3rd party app just shows what is marked as "Free".
Not sure if this is the case. Just a guess.
I know unused ram is wasted ram, but I'm constantly at 90% ram and it's causing the phone to lag and stutter to the point its unusable unless I reboot then I'm good. Just wanted to see if anybody was going through the same thing or if I have a rouge app up to something.
I've noticed that myself.. That is why I have debloated my phone without root. I have also notice the biggest user of the ram is the Android OS 1.3 Gb.
Joe199799 said:
I know unused ram is wasted ram, but I'm constantly at 90% ram and it's causing the phone to lag and stutter to the point its unusable unless I reboot then I'm good. Just wanted to see if anybody was going through the same thing or if I have a rouge app up to something.
Click to expand...
Click to collapse
Same here. It's a typical LG thing. Their Android mods are slick and lovely, but they're far from lightweight.
I moved from a Sony XZ1 Compact to a G7, and it is generally a significantly slower, laggier experience. With the Sony it would generally use less than 2gb of RAM at the outset. I could come back to an app a week later and it'd still be open. With this G7 I think it's rare to see it under 3gb consumption, and every time I open the camera I'm evicted most other apps from memory.
Then there's the lag! I thought a years newer flagship tech would have minimized the LG lag experience, but no.
Also no, at least for T-Mobile uS G7, no root, no AOSP and official device trees. I am made of regret, definitely never another LG, and Sony for me from here on out.
This phone has given me the least amount of issues with lag and freezes out of any phone I've had. I do a lot of gaming on here and rarely have an issue. I try to install as much as possible on my SD card, I don't know if that would make a difference with RAM usage, and I don't leave a bunch of apps running in the background.
I really love this phone but it's getting old, I'm looking on how I can increase its performance.
I'm currently running LineageOS 19.1 and while perf is decent I want to know what else I can do before looking at getting another device.
I thought I could try overclocking so I rooted it but all the apps are showing normal max cpu frequency. I changed cpu governor to performance but according to Geekbench 5 the gains are minimal. Also I'm not a fan of root, it's too much hassle with SafetyNet etc, but if there is a way to make it faster I will see if I can live with root.
Or is there another kernel that I can try?
Thanks for all the suggestions.
It's probably close to it's maximum performance and an unstable SoC is an ugly thing...
Take out the trash. Apps that are constantly running in the background and aren't needed. No social media, shopping or banking apps should ever be installed. Apps using battery and bandwidth needlessly need to be dealt with. If the app is doing either it's also sucking up your cpu cycles and resources. Use a logging firewall to help spot habitual offenders.
blackhawk said:
It's probably close to it's maximum performance and an unstable SoC is an ugly thing...
Take out the trash. Apps that are constantly running in the background and aren't needed. No social media, shopping or banking apps should ever be installed. Apps using battery and bandwidth needlessly need to be dealt with. If the app is doing either it's also sucking up your cpu cycles and resources. Use a logging firewall to help spot habitual offenders.
Click to expand...
Click to collapse
Thanks, already done as much housekeeping as I could and I have minimum of what I need. Banking apps are among them since I don't like their web versions. I could start uninstalling what is not needed but there is a risk of removing something necessary and I don't want to spend too much time on it. LOS already comes without bloat. I'll do some more monitoring but as you said it's probably close to its max performance. Luckily it's not at the level of being unusable (yet), just slightly annoying, with things like keyboard taking those 3 seconds longer to load haha.
One thing that's really killing performance is the 3gb of ram. It has to constantly juggle that.
After using the N10+'s for years I'm sold on 12gb of ram or more. The additional ram impacts battery life little but provides real time performance increase and future proofing.
Not using scoped storage also aids performance. I still use Android 9 and 10 and will not upgrade either. They would take a performance and usability hit if I did. The performance of newer phones is dismal; it comes at a high power consumption cost, little real time performance increases and decreased functionality/usability. Those are some of the reasons I happily run 2 flagships that are over 3 yo with firmware that old as well.
Seems all Google and Samsung can do anymore is dropped balls. They excel at that now and at bs hype that I'm not buying... literally.
blackhawk said:
One thing that's really killing performance is the 3gb of ram. It has to constantly juggle that.
After using the N10+'s for years I'm sold on 12gb of ram or more. The additional ram impacts battery life little but provides real time performance increase and future proofing.
Not using scoped storage also aids performance. I still use Android 9 and 10 and will not upgrade either. They would take a performance and usability hit if I did. The performance of newer phones is dismal; it comes at a high power consumption cost, little real time performance increases and decreased functionality/usability. Those are some of the reasons I happily run 2 flagships that are over 3 yo with firmware that old as well.
Seems all Google and Samsung can do anymore is dropped balls. They excel at that now and at bs hype that I'm not buying... literally.
Click to expand...
Click to collapse
Yeah, ram seems to be a bottleneck definitely. I tend to buy several years old devices and my budget is low, but I like to have the os up to date as much as possible. I was actually looking at OnePlus 5T with 8G ram. Another thing I like is small form fatcor. Anything larger than 6" seems too big for me. Hence I stick with my Xperia for now.
Paulkw said:
Yeah, ram seems to be a bottleneck definitely. I tend to buy several years old devices and my budget is low, but I like to have the os up to date as much as possible. I was actually looking at OnePlus 5T with 8G ram. Another thing I like is small form fatcor. Anything larger than 6" seems too big for me. Hence I stick with my Xperia for now.
Click to expand...
Click to collapse
Since my N10+'s effectively supersede my laptop the size is desirable for me. It's a relatively light phone and in a Bolt case it still has a reasonably slim profile so it doesn't seem that big. It has a lot of performance enhancing features/add ons including the spen. It's also great for watching vids, all in all a more than fair trade off for me.
However I can see it from your point of view. Form factor is an important consideration and if it will integrate effectively into your lifestyle. The S22U is bigger and 30gms heavier, blah! Then there's the hump back N20U