Oh, after using jelly bean for 3 days, i noticed that it eats all of Ram, only 60-110 MB free!!!!
And this cause very slow downs and FC alot,
While on ics there is about 200-250 MB Free!!! With the same apps
Is this bec. Of beta, running, and freezing all bloatware and the same aetup in every aspect
, is 1GB of ram isn't enough now days!!!
Again, i tried to use swap file using various methods with no success due to kernel support, is there any kernel or method to have working swap, or is there any workaround to have some thing similar to swap.
Sent from my GT-N7000 using xda premium
The note actually only has 800mb, so it's not even a gig.
well ram works differently on android then on windows pc, if its full it doesnt necessary mean that's why device is slowed down. Memory works differently.
Secondly jb, you are using now is not for everyday use. So you are bound to run into issues like this one. Also there is a memory leak in current builds. Which means that JB doesnt do that, but the current build does that because of a bug.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
well ram works differently on android then on windows pc, if its full it doesnt necessary mean that's why device is slowed down. Memory works differently.
Secondly jb, you are using now is not for everyday use. So you are bound to run into issues like this one. Also there is a memory leak in current builds. Which means that JB doesnt do that, but the current build does that because of a bug.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yes i know that full ram may not cause slow downs, well it will slow down only when riched critical value and cause FCs , but you say that this problem in JB is due to beta stage, so this is good, so we have to wait for fully working build or at least stable enough to run system without FCs or slowdowna
Sent from my GT-N7000 using xda premium
Yep definately.
I guess it takes extra clean installs with prenightly roms.
Maybe, because you got this far you can get comfortable with logfiles and troubleshooting. Try to get to the root cause of the issue. You might be able to contribute there.At this point if I knew how, I'd help you.
Sent from my GT-N7000 using Tapatalk 2
little-vince said:
The note actually only has 800mb, so it's not even a gig.
Click to expand...
Click to collapse
Is that true? I don't think so. I think it's how it's allocated and counted. Like when you go buy a 1TB drive, you only have access to 931GB. It's how it's formatted and allocated.
Probably the same with Android with memory allocation or something like that. It's false advertising to say "It has 1024MB of RAM" when they actually only include 800. 800 is accessible, but there's probably 1GB in there.
zkyevolved said:
Is that true? I don't think so. I think it's how it's allocated and counted. Like when you go buy a 1TB drive, you only have access to 931GB. It's how it's formatted and allocated.
Probably the same with Android with memory allocation or something like that. It's false advertising to say "It has 1024MB of RAM" when they actually only include 800. 800 is accessible, but there's probably 1GB in there.
Click to expand...
Click to collapse
There almost certainly is 1GB of RAM in there, but the graphics processor needs some of it to do it's job, say probably 128MB. Then just like the PC there are other other parts of the device that need to have blocks of memory to do their jobs, and the kernel and other core OS will probably snarf some memory to do what they need to do.
Voila, 1GB of RAM immediately reduced to 500-800MB of actual "usable" RAM.
Yup, the 1gb is a lie.. galaxy note has the same amount of ram of desire hd
Sent from my GT-N7000 using xda app-developers app
LoVeRice said:
Yup, the 1gb is a lie.. galaxy note has the same amount of ram of desire hd
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
No dear, desireHD has 786 MB BUT ONLY about 600 MB usable, the same story as note and every android device
Sent from my GT-N7000 using xda premium
evaworld said:
No dear, desireHD has 786 MB BUT ONLY about 600 MB usable, the same story as note and every android device
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Based on every nand device out there, ssd, emmc, all of them allocate sectors to general use.
Sent from my GT-N7000 using xda premium
Can part of internal sd or ext sd become an extended ram or something?
Would that make the device any faster?
Sent from my GT-N7000 using xda app-developers app
fr3ker said:
Can part of internal sd or ext sd become an extended ram or something?
Would that make the device any faster?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes it can.
No that won't make it any faster. In fact, it will make it slower.
The way Android works is, it says "the kernel says I need X amount for gpu, X amount for sound, X amount for the OS".
And then it allocates a certain threashold and says "okay this much I'm keeping free".
Then it says "these functions of the OS aren't used often, I'll leave them out".
Then it says "okay so I've got extra ram room, I'm going to fill them up with Apps".
Why does it work this way?
It based on Linux, RAM is shared dynamically.
What does this mean?
A bloated kernel and OS will use more RAM for itself.
Why does it leave free ram?
In case it needs to execute a function that's not used often or is memory intensive (eg Browser).
Why does it store Apps?
So that its readily available. They just pop open. Or resume from last state.
...okay, so what does this mean about my Free RAM "issues" with Jelly Bean?
It means that you are uneducated. It means Jelly Bean, or the specific setup you have either is more bloated than your previous setup OR it has a low "free ram allocation" setting. Solution? There is no problem, though you can trim down the ram allocation and kill off some memory things (apps, hidden background tasks) you can increase the amount of Free RAM, but its more likely to slow down the system. Remember, Jelly Bean builds are still Alpha/Beta stage, so they can/do have memory leaks.
Another point I should mention:
OS RAM use increased a lot from 1.6 -> 2.1
OS RAM use increased from 2.1 -> 2.2
OS RAM use increased a lot from 2.2 -> 2.3
OS RAM use increased a lot from 2.3 -> 4.0
< I haven't checked JB, but I'm willing to bet its increased from ICS, even if slightly >
This is Android, not Windows. Its behaves differently and has different symptoms. A quick Google search could've answered your questions.
Kangal said:
Yes it can.
No that won't make it any faster. In fact, it will make it slower.
The way Android works is, it says "the kernel says I need X amount for gpu, X amount for sound, X amount for the OS".
And then it allocates a certain threashold and says "okay this much I'm keeping free".
Then it says "these functions of the OS aren't used often, I'll leave them out".
Then it says "okay so I've got extra ram room, I'm going to fill them up with Apps".
Why does it work this way?
It based on Linux, RAM is shared dynamically.
What does this mean?
A bloated kernel and OS will use more RAM for itself.
Why does it leave free ram?
In case it needs to execute a function that's not used often or is memory intensive (eg Browser).
Why does it store Apps?
So that its readily available. They just pop open. Or resume from last state.
...okay, so what does this mean about my Free RAM "issues" with Jelly Bean?
It means that you are uneducated. It means Jelly Bean, or the specific setup you have either is more bloated than your previous setup OR it has a low "free ram allocation" setting. Solution? There is no problem, though you can trim down the ram allocation and kill off some memory things (apps, hidden background tasks) you can increase the amount of Free RAM, but its more likely to slow down the system. Remember, Jelly Bean builds are still Alpha/Beta stage, so they can/do have memory leaks.
Another point I should mention:
OS RAM use increased a lot from 1.6 -> 2.1
OS RAM use increased from 2.1 -> 2.2
OS RAM use increased a lot from 2.2 -> 2.3
OS RAM use increased a lot from 2.3 -> 4.0
< I haven't checked JB, but I'm willing to bet its increased from ICS, even if slightly >
This is Android, not Windows. Its behaves differently and has different symptoms. A quick Google search could've answered your questions.
Click to expand...
Click to collapse
Thanks for the lecture here :thumbup: I see now, I never get to know linux base very well. Just starting to get myself familiar with it.
I've used a few types of JB rom before and I discovered that its using double the ram from ICS making my phone lags and does funny things ut shouldn't. Ahaks
Than I noticed that JB was released to phones such as S3 and such, phones that has double the ram size to compare with note. Its when I started to wonder...
Sent from my GT-N7000 using xda app-developers app
Related
Does the froyo update make the full 512 mb ram available? I had heard earlier that only a part of it was available due to 2.1 limitations.
Sent from my GT-I9000 ADJF1 using XDA App
They were always available, ~300Mb for Programs and the rest for the system files... Why should that change?
I think what the OP meant was whether one had more memory for apps as ht tp:// developer.android.com/sdk/android-2.2-highlights.html claims that the 2.6.32 kernel upgrade would bring "HIGHMEM support for RAM >256MB".
At the moment, we do not have the full memory available in the Linux system:
Code:
$ adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ free
total used free shared buffers
Mem: 333420 329988 3432 0 34724
Swap: 0 0 0
Total: 333420 329988 3432
I do not know whether that is related to the graphics hardware taking some of the memory, or to the kernel version:
Code:
$ uname -r
2.6.29
Edit: What do you mean by 'system files'? The OS is stored on mass storage, right? And Dalvik and friends should appear as userspace processes taking up regular memory.
satta said:
I think what the OP meant was whether one had more memory for apps as developer.android.com/sdk/android-2.2-highlights.html claims that the 2.6.32 kernel upgrade would bring "HIGHMEM support for RAM >256MB".
Click to expand...
Click to collapse
You do understand that this does not compute, since there has always been more than 256MB available
Or has there?
I was wondering about the same thing, kernel 2.6.32.9 (JP3) also shows a little more than 300mb...
buddy01 said:
You do understand that this does not compute, since there has always been more than 256MB available
Or has there?
Click to expand...
Click to collapse
Hey, I'm just quoting from an official AOSP site
Mine shows 30 mb available under advanced task killer. What am I missing?
Sent from my GT-I9000 using XDA App
@satta yeah that's what I meant and that's what I had read. Cheers
Sent from my GT-I9000 using XDA App
I've seen Desire have over 400MB of memory available for applications in a video with a some sort of task manager on..
Are you sure, max i got on my nexus one was 312MB in some rare cases, using it without closing apps at all, never got below 100MB... But my Galaxy's max is 170MB, is almost half what my nexus gave me, that kinda suck (don't know if it matter bu tit feels bad in my head )
Desire has 576MB memory.. N1 has 512MB
Sent from my GT-I9000 using XDA App
Maximum free RAM i got from my sgs is 210mb, easily achieved by using Astro's process manager and killing all non-essential services.
why t.f. do you guys always want to have lots of fre ram? please read a little about android memory management... free ram is wasted ram!
FadeFx said:
why t.f. do you guys always want to have lots of fre ram? please read a little about android memory management... free ram is wasted ram!
Click to expand...
Click to collapse
So? We all still want our phones to be as future proof as we hoped they would be when we bought them. And we want the extra RAM simply because it's supposed to be there.
Sent from my GT-I9000 using XDA App
FadeFx said:
why t.f. do you guys always want to have lots of fre ram? please read a little about android memory management... free ram is wasted ram!
Click to expand...
Click to collapse
As long as it doesn't go below that ~70mb when the phones actually start lagging
Might also want to take into consideration that the counterpart Desire used in this thread is also an android phone, sure too much free memory is wasted memory but too little usable memory = lag and if there isn't a lot to use in the first place then it won't take much for the phone to start lagging.
Some help in JG and onward firmwares but it's still quite funny that a simple user can make a fix to create a solution for the entire problem and Samsung hasn't either thought about this or taken it into consideration. (Mimocan is my hero <3)
edit: WOO my first post after actually following these forums for almost half a year, just registered recently
Hey,
Actually you do not need that much RAM. Im running on JG5, which IMO is the most stable and usable firmware out there. Has been running the phone for 3 days straight without any ATK like apps, and has not experience any lags.
Another thing is that, IMHO ATKs slow down the system.
Sent from my GT-I9000 using XDA App
The current Samsung froyo builds do not support highmem. It is a kernel compile time config option. Samsung will hopefully enable it in later builds.
Highmem made a noticeable difference in performance on my nexus one.
ed10000 said:
So? We all still want our phones to be as future proof as we hoped they would be when we bought them. And we want the extra RAM simply because it's supposed to be there.
Click to expand...
Click to collapse
Nonsense. You are not entitled to more free ram in any way.
Every os uses a part of the ram for the kernel code and its buffers.
In addition the advanced graphics will need memory for its texture storage and graphic representation.
A froyo kernel will not make a major difference.
The sg has 512 memory today and it is using it as it should...
akselic said:
As long as it doesn't go below that ~70mb when the phones actually start lagging
Might also want to take into consideration that the counterpart Desire used in this thread is also an android phone, sure too much free memory is wasted memory but too little usable memory = lag and if there isn't a lot to use in the first place then it won't take much for the phone to start lagging.
Some help in JG and onward firmwares but it's still quite funny that a simple user can make a fix to create a solution for the entire problem and Samsung hasn't either thought about this or taken it into consideration. (Mimocan is my hero <3)
edit: WOO my first post after actually following these forums for almost half a year, just registered recently
Click to expand...
Click to collapse
lagging is actually not caused by to less free ram, in android there is no such. the used ram is caused by apps that you opened and then exited again. if you open a new app that needs more ram than aviailable (actually with a little gap of some mb) the system will close apps that are not used anymore and only kept in ram for faster opening. the lag comes from bad i/o speeds of the nand (internal memory) where apps data is stored. on i7500 there is 192mb of ram and it works ok with froyo (thanx to drakaz and gaosp team!) only thing is that every app you open forces the app you opened before to be kicked out of ram what makes switching between apps makes somewhat a pain.
also free memory and usable memory is apples and pears, useable is all memory that contains no actually running in foreground app or service. and free memory is the rest that contains absolutely no information and thus WASTED
edit: btw i7500 is running well with 20mb free ram.
I often have no more than 30 MBs free, and not running THAT many apps. What is strange is that sometimes there is 70-80 MB free, and I have not done anyting. What happens in the background is a mystery... Any suggestions?
When I bought my galaxy s, it was on a 2.2 rom, though I don't remember the exact name. After a while, I flashed it with ZSJPK 2.2.1. Then, I went on to use JVP, JVQ and now, JVR. However, I felt that 2.2 and ZSJPK were both smoother and less laggy than JVP and JVQ. JVR is nearly as smooth as the two froyos, but it's RAM drops to very low levels, 70-80Mb after a day's usage. So, my question is, does anyone else experience such a thing in which their froyo roms were faster/less laggy? Or could it be that I somehow missed something when flashing the gingerbread roms? Thanks.
Why do you care about the RAM being "so low". Memory management works different in Linux than on MS systems. Android (or the underlying linux kernel) keeps apps in memory as long as possible to make a re-start of the app faster. As soon as the memory is needed by a different app, the memory is freed anyway.
My desktop with 4 GB RAM does the same on Linux: 64 MB are free, but if I take buffers and cache into account 1900 MB are available in case an application needs it....
I experienced a better battery life with smoother operation in every day use after installing GB (I guess first that was I9000XXJVK). This got only better with JVH, JVO, JVP, JVQ, JVR and now JVS.
I wouldn't care about the RAM, actually. But whenever my free RAM drops to below 80Mb or so, the phone begins to lag, because it has to close certain processes in order to start up the apps. Also, when the RAM is low and when I try to play certain HD games like the gameloft ones, the phone sometimes crashes.
elhennig said:
Why do you care about the RAM being "so low". Memory management works different in Linux than on MS systems. Android (or the underlying linux kernel) keeps apps in memory as long as possible to make a re-start of the app faster. As soon as the memory is needed by a different app, the memory is freed anyway.
My desktop with 4 GB RAM does the same on Linux: 64 MB are free, but if I take buffers and cache into account 1900 MB are available in case an application needs it....
I experienced a better battery life with smoother operation in every day use after installing GB (I guess first that was I9000XXJVK). This got only better with JVH, JVO, JVP, JVQ, JVR and now JVS.
Click to expand...
Click to collapse
An Android with free ram available is still much faster than an Android phone that continues to swap.
I've done tests in regards to this in System Panel. Plus on occasion whenever I clear my Dalvic Cache, I usually double my memory in System Panel, and my phone feels like "day 1" fast...
Sent from my MB860 using xda premium
ccrows said:
An Android with free ram available is still much faster than an Android phone that continues to swap.
Click to expand...
Click to collapse
Where should the mem be swapped to? Android does not swap if there is no swap device or file specified.
elhennig said:
Where should the mem be swapped to? Android does not swap if there is no swap device or file specified.
Click to expand...
Click to collapse
I'm saying that there is a benefit to freeing up ram...
Sent from my MB860 using xda premium
ccrows said:
I'm saying that there is a benefit to freeing up ram...
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, it's beneficial to have free RAM rather than to have to free up the RAM when you need it. If you already have free RAM, running a new application is fast, but if you don't, you cpu needs to free some RAM first before it can load a new application, hence causing some lagginess. That's what I meant when I said that froyo seemed faster, especially after a day of usage.
I was using Froyo for quite a long time before giving a chance to Gingerbread. And I must say I regret I didn't give a chance to GB earlier as the phone is "flying" now. At least for me it was a good switch. When I bought my SGS it was on 2.1 (Eclair) which was a real laggy disaster.
stiwipl said:
I was using Froyo for quite a long time before giving a chance to Gingerbread. And I must say I regret I didn't give a chance to GB earlier as the phone is "flying" now. At least for me it was a good switch. When I bought my SGS it was on 2.1 (Eclair) which was a real laggy disaster.
Click to expand...
Click to collapse
Which froyo build were you using? Because the earlier froyos, ie 2.2, were rather lousy. I'm comparing 2.2.1 with 2.3.4
Every phone I buy always has less than the advertised storage space, I understand some will be taken by the rom and apps.
What I wanna know is what the heck is eating almost 8 gigs? That's a retarded high amount.
Sent from my HTCONE using xda premium
the phone OS i believe, i could be wrong though.
what about the 2gb of ram?
theres always about 600-700mb free. wtf?
then when you free it up with a task killer, theres only about 1gb of free ram.
Rippley05 said:
Every phone I buy always has less than the advertised storage space, I understand some will be taken by the rom and apps.
What I wanna know is what the heck is eating almost 8 gigs? That's a retarded high amount.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
It seems to be system reserved storage. The size gets larger as you go up in storage size. Considering the benchmarks on the I/O being chart toppers, it's possible that it is being reserved as a performance booster of some sort.
TorxT3D said:
what about the 2gb of ram?
theres always about 600-700mb free. wtf?
then when you free it up with a task killer, theres only about 1gb of free ram.
Click to expand...
Click to collapse
You have to factor in reserved RAM (my S3 has 2GB but only 1630MB is available to apps. Part of that is dedicated to the graphics chip and the rest is system reserved.
That said, you will not have RAM issues with 6-700MB free. I run a ton of apps at the same time on mine and with the exception of some huge games, I rarely have run out of RAM and had a background app killed by the OS.
512MB phones only had like 384MB available total because of the other 128 going to the GPU.
Sent from my SGH-T999
EtherealRemnant said:
It seems to be system reserved storage. The size gets larger as you go up in storage size. Considering the benchmarks on the I/O being chart toppers, it's possible that it is being reserved as a performance booster of some sort.
You have to factor in reserved RAM (my S3 has 2GB but only 1630MB is available to apps. Part of that is dedicated to the graphics chip and the rest is system reserved.
That said, you will not have RAM issues with 6-700MB free. I run a ton of apps at the same time on mine and with the exception of some huge games, I rarely have run out of RAM and had a background app killed by the OS.
512MB phones only had like 384MB available total because of the other 128 going to the GPU.
Sent from my SGH-T999
Click to expand...
Click to collapse
My browser is constantly killed regardless to what app I use in between...and this isn't only on one handset
Sent from my HTCONE using xda app-developers app
I think he meant storage....not memory like ram.
david279 said:
I think he meant storage....not memory like ram.
Click to expand...
Click to collapse
Yea my bad.
It's a 32 Gb phone, and you can see by the pic that almost 8 gigs is being eaten up by "other". That's about what the LTE came with. That's just an insane number. They shouldn't be able to advertise a 32 gig phone when all you're really getting is 24-25 gigs.
Rippley05 said:
Every phone I buy always has less than the advertised storage space, I understand some will be taken by the rom and apps.
What I wanna know is what the heck is eating almost 8 gigs? That's a retarded high amount.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
For one thing, it's measured differently. When ANY manufacturer of Memory based ANYTHING (except RAM for some reason.) says "this-many-gigs" they are actually measuring the bytes. So, they really mean 32,000,000 bytes. When converted to Gb this is only 29.8 GB.
False advertising? Kind of. But seriously every storage manufacturer does this so it's common practice at this point.
So then we see that the OS and all the other stuff is taking up around 7GB. That still seems ridiculous given a Windows 7 install can take up as little as 8GB.
felacio said:
For one thing, it's measured differently. When ANY manufacturer of Memory based ANYTHING (except RAM for some reason.) says "this-many-gigs" they are actually measuring the bytes. So, they really mean 32,000,000 bytes. When converted to Gb this is only 29.8 GB.
False advertising? Kind of. But seriously every storage manufacturer does this so it's common practice at this point.
So then we see that the OS and all the other stuff is taking up around 7GB. That still seems ridiculous given a Windows 7 install can take up as little as 8GB.
Click to expand...
Click to collapse
Yea I know it's alway gonna have some side twisted story..I do understand that.
8gb is just flat retarded and I'm surprised nobody is making a big deal of it.
Sent from my HTCONE using xda premium
You think our phones are bad check out the amount of usable storage on the s4.
Sent from my HTCONE using Tapatalk 2
Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app
butler0607 said:
Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
I think so, the spare RAM should make the ROM about 3 times more spare RAM, and quite fast.
butler0607 said:
Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
Short answer.. your way off..
Long Answer..
The big change is that the system now degrades gracefully on low resource devices.. so things like animations and textures are reduced to maintain the systems overall performance even on low resource devices.. versus say jellybean and ICS which simply tried to run regardless even on the original G1.. bringing the entire system down to a crawl (this is a vastly oversimplified version of a portion of what is going on in 4.4 and is not meant to be exhaustive explanation)
The second part of your question is why I want to strangle every marketing person from the beginning of time.. just because the system CAN operate with less ram does NOT mean that it is not USING all of the ram in your device.. the system will invariably use up as much as it can get its hands on (and still try to grab some more!)
OK, I think I get it! Thanks for the help
Sent from my HTC Desire C using xda app-developers app
Improved memory management should (in theory) also help the Tegra 3 chip since it has slow single-channel ram.
Not sure if you all know this or not but the memory leak from 5.0 is still present in 5.0.2. Screenshots show it. First is before restart, second is after restart.
Sent from my Nexus 5 with the N5X LRX22G ROM
procitysam said:
Not sure if you all know this or not but the memory leak from 5.0 is still present in 5.0.2. Screenshots show it. First is before restart, second is after restart.
Sent from my Nexus 5 with the N5X LRX22G ROM
Click to expand...
Click to collapse
So u conclude this only because less ram is free ? Or the device becomes unusable?
Pretty sure everyone knows, and if you look at a changelog there was no mention of it being fixed: http://aosp.changelog.to/aosp-LRX22C-LRX22G.html
There are commits that fix a memory leak (https://github.com/Lethargy/android_frameworks_base/commit/da2133d046e59b590e51448eda31d710da217d40 and https://github.com/Lethargy/android_frameworks_base/commit/e30ccdbeac2c53b04a389c7ffd8e9d500c93ef30), however I do not experience such memory leak myself so I cannot say if it fixed the issue for others.
Lethargy said:
Pretty sure everyone knows, and if you look at a changelog there was no mention of it being fixed: http://aosp.changelog.to/aosp-LRX22C-LRX22G.html
There are commits that fix a memory leak (https://github.com/Lethargy/android_frameworks_base/commit/da2133d046e59b590e51448eda31d710da217d40 and https://github.com/Lethargy/android_frameworks_base/commit/e30ccdbeac2c53b04a389c7ffd8e9d500c93ef30), however I do not experience such memory leak myself so I cannot say if it fixed the issue for others.
Click to expand...
Click to collapse
Just asking regrading the 2 links you posted... Is it the screen off animation causing the memory leak and maybe if you switch off the animation in developer settings will it fix it?
tanjiajun_34 said:
Just asking regrading the 2 links you posted... Is it the screen off animation causing the memory leak and maybe if you switch off the animation in developer settings will it fix it?
Click to expand...
Click to collapse
I'm not sure if those commits fix the memory leak that is widely experienced by some users. I only know it fixes "a" memory leak. Again, I did not experience a memory leak myself before merging those commits to my ROM source, so I can't comment on whether it helps or not.
Not sure if turning off animation will make a difference or not, but I don't think it will.
doctor_droid said:
So u conclude this only because less ram is free ? Or the device becomes unusable?
Click to expand...
Click to collapse
I conclude this because yes there is less RAM available and it then causes the device to become very laggy and difficult to use.
Sent from my Nexus 5 with the N5X LRX22G ROM
Always got to have one pedantic one. Yes the memory leak still exists.
So is there any chance to fix it?
Uptime: 235:34:19
Stock 5.0.1
Also 3 Day usage with 3 h sot on data (3g) and wifi on but connected only during 22 to 10.
There's a memory leak?
1.3Gb free here, been on stock 5.0.1 for something like a week now. Maybe there's something else eating up your RAM.
Some say it is the Google Experience Launcher...
Gesendet von meinem Nexus 5 mit Tapatalk
This memory leak obviously is not hitting every device, me and 2 of my buds are seeing this issue (system fills up RAM and handling the device becomes a struggle), while a fourth friend is not seeing it on his N5.
3 days ago i ditched the Google Now launcher and returned to Nova, and i think the problem is not that severe anymore, but i have to keep an eye on it for a bit longer to be able to say for sure.
doctor_droid said:
So u conclude this only because less ram is free ? Or the device becomes unusable?
Click to expand...
Click to collapse
How is this a memory leak? When more memory is needed, it will open up. Contrary to a long time "windows user" mentality, using memory is good. Especially on android. Why do people think using ram is bad? Using ram helps speed things up.
On a semi side note, after perusing computer forums for many years, I've seen many people get as much RAM as possible then try to get their systems to use as little as possible. It makes no sense. RAM is your friend. Use it.
I haven't had this 'memory leak' ever..even from 5.0.0
Yes using ram speeds things up but only when its being used for things like caching preloading and keeping apps in memory. Even then too little free ram can result in lots of paging when using multiple apps so the system tries to achieve a balance keeping some things in memory while having enough free to not cause paging. In this case people are reporting the opposite that after a few days the phone becomes slow and laggy and memory usage is very high even when they have no apps open so there is no swapping it paging going on. If it was just the is caching things it would just delete them to make room for the current app but that is not the case, the only explanation there fore is that something is leaking memory and consuming it till there is very little left for anything else. Also the os might not be managing memory properly but that seems unlikely as android has always been pretty good at memory management.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I'm thinking the highly modified ROM/kernel combination might have more of an effect on OPs free RAM than any "memory leak". Stocks working just fine. Still 1.3Gb free after games, forums, screen on/off, been on for three days, etc.
Can't post screenshots with XDA one app?
killersloth said:
I'm thinking the highly modified ROM/kernel combination might have more of an effect on OPs free RAM than any "memory leak". Stocks working just fine. Still 1.3Gb free after games, forums, screen on/off, been on for three days, etc.
Can't post screenshots with XDA one app?
Click to expand...
Click to collapse
I don't think so.. i have the "laggy phone Problem" with 5.0.0 and 5.0.1 . Always absolutely stock. It's very frustrating...
killersloth said:
I'm thinking the highly modified ROM/kernel combination might have more of an effect on OPs free RAM than any "memory leak". Stocks working just fine. Still 1.3Gb free after games, forums, screen on/off, been on for three days, etc.
Can't post screenshots with XDA one app?
Click to expand...
Click to collapse
It has nothing to do with amount of free RAM. As shown in my pictures you can see 600 mb free ram, but phone starts shutting down apps. This happens on stock ROM without installing extra apps too by the way. Navigation and google music streaming quickly makes this happen it seems for me.
Duh, most of the changes for 5.0.2 were for Tegra N7.
wolfen69 said:
How is this a memory leak? When more memory is needed, it will open up. Contrary to a long time "windows user" mentality, using memory is good. Especially on android. Why do people think using ram is bad? Using ram helps speed things up.
On a semi side note, after perusing computer forums for many years, I've seen many people get as much RAM as possible then try to get their systems to use as little as possible. It makes no sense. RAM is your friend. Use it.
Click to expand...
Click to collapse
It's not the usage of RAM the issue, I think it's more about RAM management, if bigger apps need more RAM let them take it up. But the issues arises when the OS does not release the memory take up by the previous app back into the pool, so then each time we take the same program it takes more and more of the space until other apps cannot access it easily. Presto launcher redraws or apps fc's(or not even running or abruptly stopping the background music playback service) in phones, and whole system freeze or "hang" of the OS in desktop environments.