yashsingh1/xdaforums huggingface dataset:
[Nexus 5 General] vaindil:
You'll note that I did actually point this out above in post 345.

Again, you show that you don't really know what you're talking about. Here's my current RAM usage. I haven't rebooted the phone in just under 16 hours now. This is what it looks like after I open Netflix and start streaming a video, then open Google Music and start streaming music, then open Hearthstone (a pretty RAM-intensive game). See how it went up? Now, after I go back to the home screen and swipe them away from recents, look what happens.

Again, I'm not saying that no leak exists, I've never said that to begin with. I'm simply saying that circlejerking about "MEMORY LEAKS ZOMG" doesn't help anyone.

This will be my last post in this thread unless someone has a legitimate question or something like that. Nope, I'm apparently bored enough to continue commenting.
[Nexus 5 General] bblzd:
I just wanted to say thanks for so eloquently putting what many of us are thinking.
[Nexus 5 General] kaushikd:
Mine is having a strange issue, it will work fine until I go to settings > apps to check the ram. Then the phone becomes slow for sometime. The launcher takes time to respond. This will continue for around 30 seconds to 1 minute after that everything becomes normal.

Sent from Hammerhead!
[Nexus 5 General] kicksilver:
16h? You gotta be kidding us....
[Nexus 5 General] vaindil:
I don't know what you're trying to imply by mentioning that it's roughly 16 hours.
[Nexus 5 General] kicksilver:
Even in 5.0.x, which was MUCH worse than 5.1 at memory management, nothing wrong could be noticed in the first 24h.

Things only got annoying at > 50h, when all of your services would keep rebooting all the time.

I'm at 149h uptime:

SYSTEM: 880mb

APPS: 398mb

FREE: 578

------

CACHED

IN USE: 1,2GB

CACHED: 210MB

FREE: 372MB

Doesn't look normal to me. My phone's been idling in my desk for the past 3 hours.
[Nexus 5 General] vaindil:
Again, I'll point you to post 345 where I specifically said that the memory leak is documented. My point, however, was that a memory leak IS NOT DEPENDENT on time. Sure, certain programming things could cause a memory leak to only occur after a certain amount of time, but memory management doesn't handle any processes any differently after the phone has been on for (example) 24 hours than if it were turned on 10 minutes ago. Therefore, 16 hours vs. 50 hours has literally no effect in this case. (Clarification: I don't mean that time literally isn't involved in memory management; that would be a stupid claim. Memory management [specifically paging] is dependent on many factors, including time. I meant that the memory management method/algorithm itself doesn't change depending on the system uptime.)

An additional edit: If your phone has been idling, the memory management algorithm has nothing to do. Yes, things run in the background like checking emails and push notifications and the like depending on specifically what your phone is running, but there's nothing wrong with having 578MB of free memory space. If an assumption can be made that "My phone's been idling in my desk for the past 3 hours" literally means "I haven't touched my phone in 3 hours", then no new processes are likely to have started in that time. Garbage collection will have run at some point, but after that what is left to clean up? The thing to test would be to check RAM, then let it sit completely idle for 3 hours, and then compare the before and after memory usage.

I don't mean to be arrogant, but I have a degree in computer science. I like to think I know what I'm talking about, and I double-check the things I post about before I post them. If someone proves me wrong I will happily strike out my comments and link to any corrections. I only want to debunk misconceptions. And, again for the record even though I've said it several times, I'm not denying the existence of a leak, I'm merely attempting to correct the semantic misunderstandings that people are pointing out.
[Nexus 5 General] kicksilver:
I get your point, but you're not wanting to see the problem.

It is there.

I wouldn't give a damn if I had 1mb of free RAM, as long as 1,79GB was filled with cached apps, which is NOT the case. The more the time passes, SYSTEM will keep inflating and taking space from the other apps.

You can see it because the services/processes are constantly rebooting after a while.

Also, less apps are kept in cache, and you get constant app realoading while multi-tasking.

In the first 24h of use after rebooting, most apps are held in background. Why is this not happing aftter 100h? Nothing has changed, same apps, same user.
[Nexus 5 General] vaindil:
I have no problem seeing the point. And, yet again, I have stated in almost every single one of my posts in this thread that the memory leak does exist.

Cached apps are background processes that are being held in memory simply because the device has space to do so. From the previously linked page:

So there's no inherent problem with the concept of cached apps. The problem arises if these cached apps are not correctly being freed to the system by the memory management algorithm. This is not what is happening. I'll again preface this by saying that I'm not specifically an Android dev so I don't know the inner workings of Android specifically, but by their very nature system processes aren't typically killed to allow for more memory. System-level processes have priority over user-level processes. I'm not arguing with you--yes, system processes are documented as taking and retaining memory when they clearly shouldn't be. I don't know which system processes are at fault, but system-level processes typically need to explicitly free their memory themselves back to the system, whereas the memory management algorithm will force older user processes to close and take their memory if needed to allow for new processes.

ETA: So, to put it a bit more succinctly: You're seeing fewer apps being held in cached memory (indeed, less cached memory being used overall) the longer the device is on because the system is utilizing more foreground memory, leaving less "just because it can" space for cached apps to be held in. This is because of the system memory leak that has yet to be fixed (for whatever reason that I'm not here to argue for or against).

(Just to clarify my semantics: I know that an "algorithm" isn't a piece of code that runs; it's simply most convenient in this context to refer to the "memory management algorithm" as handling the memory rather than stating something like "...being freed to the system by the system".)
[Nexus 5 General] Edge330:
Omg I also noticed that, maybe is placebo, but when I go in settings and check RAM it's problem starter.
[Nexus 5 General] kaushikd:
Exactly. I have tested this multiple times. :D

Sent from Hammerhead!
[Nexus 5 General] vaindil:
I've noticed this as well, though not to the degree you're describing. My guess is that it takes the system a few moments to poll all of the active processes and parse a human-readable list from them. This would make sense if your phone has been up for a long time, as it would a) have more processes to parse and b) be suffering more from the effects of the memory leak. Just a guess though.
[Nexus 5 General] Gorgtech:
Everybody is talking about some "memory leaks" and to be honest, this topic is really annoying.

I never had any trouble with Android Lollipop and maybe some of the guys complaining need to learn how to handle a device ?

It is normal for Android to use as much RAM as possible in order to keep your active processes ( eg. the launcher, dialer etc. ) alive and too much free RAM = wasted RAM.

I know that some of Google´s Apps are faulty and might indeed cause some trouble but since most of us XDA-Nerds have rooted devices, this is not a problem at all ? Simply freeze / remove the Apps you don´t need.

I use Nova Launcher Prime instead of the Google Launcher and never ever had any lags or redraws. I know how to quit a App properly and don´t install every thrash I find on the Google Playstore.

To me, this whole conversation reminds me of the rage wars against Microsoft Windows. Users claim it is a horrible OS which will get you every Virus available on the net but on the other hand they install *cough* paid content for free or browse the web for "barely dressed ladies" :laugh:

My point is, even if you have plenty of space on your Android devices left, this is not a reason for you to install as many Apps as possible; simply use what you need only instead of gathering many games ( which btw. also install services on their own and will spam you with push notifications while also eating your battery ).
[Nexus 5 General] kicksilver:
You guys gotta be kidding us.

There IS a memory leak in Lollipop, there's no deying. Also, memory management isn't ready for prime time.

I use my device EXACTLY the same way as I did back in Jelly bean, Kitkat, 5.0 and now 5.1. Even the apps haven't changed, every day the same apps, same usage pattern.

Less than a week of uptime, and half of my RAM is taken by the system... When in the first 24h it won't go over 400mb. Same apps, same usage pattern and boom, it doubled? This is bull****.

Look at the cached apps, almost nothing. After a reboot, there'll be more than 800mb of cached apps. Why isn't it like that now?

Guess what, maybe tomorrow, I'll be start getting launcher redraws, when Apex will get kicked from memory. What for? Only Google knows...

It was never like this in Kitkat. I often had system uptime > 300h and the multi-tasking was always optimal, never experienced an app reload while swtiching.
[Nexus 5 General] rolldroids:
What Android reports as free RAM is NOT wasted RAM, it is used RAM that can be freed + unused RAM, so there should always be a lot of "free" RAM!
[Nexus 5 General] TheKorbenDallas:
Precisely. I don't know why it is so difficult to explain to the modern wannabee-experts that the role RAM plays in modern OS is qualitatively different from what it was back in DOS days.

RAM usage means nothing. RAM is not supposed to be released when an application terminates. The fact that you "sweep away" an app and RAM usage remains unchanged means absolutely nothing bad. And no, it does not indicate a memory leak.

I modern OSes (Android included) RAM is never released without a reason, just for the sake of releasing it. A "good reason" in this case is someone else needing that RAM. RAM is freed when some app attempts to allocate RAM and discovers that all RAM is taken. At this moment OS will find RAM areas that are not really used anymore and hand them over to the app requesting memory. This is the moment when the result of your "swiping away" are supposed to materialize and you app's memory is supposed to be released. But not before.

Before that moment your app is supposed to stay in RAM, even if you "swiped it away".
[Nexus 5 General] markdapimp:
The problem is that isn't happening sometimes with the memory leak, To the point where the OS will crash and reboot!

Fear not Google may release the fix in 5.1.1 and if not it'll be fixed in 5.1.2

Surely before the release of Android M.

---------- Post added at 03:56 AM ---------- Previous post was at 03:47 AM ----------

Yeah, Lollipop isn't at prime time yet. Perhaps we'll see it at 5.1.1 or 5.1.2 maybe even then the fix comes out... Nobody will care because Android M should be around the corner by then.
[Nexus 5 General] C3C076:
Android has garbage collector just like any other modern system. It is designed to free memory blocks that are not "valid" anymore (like app which allocated memory has been terminated because other app was requesting more memory than available, etc).

While I don't experience leaks myself, from what I saw I am quite sure to say there is issue with memory management in Lollipop where SYSTEM memory is getting full because unused blocks are not being released as they should be.
[Nexus 5 General] kicksilver:
According to our friends here, its normal...

Oh, look, my Tapatalk just reloaded while I went to check my RAM usage.

This must be perfectly normal..

Enviado do meu Nexus 5
[Nexus 5 General] NickFe:
Isn't that what a memory leak is? Memory is leaked exactly because the garbage collector can't distinguish between memory that still is in use from that that should have been released but it isn't. It's like you have technically been discharged from the hospital, but nobody got notified, so you can't be released. Over time the hospital gets full, and the only way is to, well, you know, kill...
[Nexus 5 General] JonasVFC:
you are the type os users that "if i don't experience this, it must be fake"

you clearly don't understand the issue. perhaps if you would have to reboot your device to make it usable again (due to all apps restarting) may be you would understand the situation. don't be another user like that please.

the other point is, i could count with one hand the number of apps i had installed on lollipop before switched back to kitkat.
[Nexus 5 General] Edge330:
Phone lost battle after 125 hours without reset, lol.
[Nexus 5 General] bregan90:
LOL. No. There is a memory leak as the system RAM usage never decrease in any case, and system is being so huge, it will cause lag and choppiness. On 5.1 and 277 hours, system is now 1GB RAM, leaving only <1GB for apps. System != RAM for cached apps.
[Nexus 5 General] Gorgtech:
Well, I use Lollipop on 2 different devices and don´t have any leaks of any kinds. I guess Google loves me :D
[Nexus 5 General] markdapimp:
If you don't use the apps that cause a memory leak, you won't experience it.
[Nexus 5 General] frigidazzi:
Just to be clear. This restarting is what everyone app list looks like when it starts setting up, right?
[Nexus 5 General] uodii:
For the record, think about what you just said. You've been arguing that there's a major memory leak issue (I'm sure there may be, I know Google has admitted to it), but your statement here says specific apps are the cause of it.
[Nexus 5 General] DummyPLUG:
If you turn off the phone, you won't experience it.
[Nexus 5 General] kicksilver:
Back in 5.0.x that happened after a few days.

In 5.1, im at 230h and services havent restarted, despite the low available RAM.

Much better memory management

Enviado do meu Nexus 5
[Nexus 5 General] pfmiller:
Memory management is the OS's problem. There is likely a specific function which causes the problem that not every app uses. That doesn't make it the apps fault.
[Nexus 5 General] uodii:
I understand that, but his statement was kind of going against what he's been arguing this entire thread. Someone stated that they haven't experienced the memory leak that bogged down their phone causing restarts and/or redraws and he said it's because those people arent using the right apps........

So there could also be a possibility that the system itself has issues, but poorly coded apps are exposing this problem.
[Nexus 5 General] kicksilver:
So, I tried to reach 10 days of uptime (actually it froze on Chrome at 239:48, damn!)

So, this is the result:

It's actually all right at 200h, but from then on, experience was compromised. Every app reloading, and so on.

Well, it's a huge improvement over 5.0.x, where a reboot was mandatory after only 3 days.

Hope 5.1.1 squashes this away indefinitely.
[Nexus 5 General] vADeR_X:
After a lot of testing, by trying to reproduce the issue from Farm Heroes Saga to other applications for around 30-45 minutes (open around 10 app, play around a little, switch to another app, and swipe it to close), it seems the case are not replicable. The System Memory are staying around at 500-600MB only.

Maybe it just bad written app (Farm Heroes Saga)?

Some application that i tested:

Bomber Friends

Brain Wars

Clash of Clans

Crazy Swinger

Crossy Road

Dr. Parking

Froggy VR

Hay Day

Jolly Jam

Lamper VR

Lapso

Microtip

Minion Rush

PvZ 2

Skyward

Space Team

SpaceTerror

Where's My Water

Worms 3

Zombie Shooter

https://code.google.com/p/android/issues/detail?id=159738#c34
[Nexus 5 General] trsix:
Games, memory, battery etc

It's not an xbox or a pc nor is it sold as a gaming device. It also isn't advertised as coming with a die hard battery.

It's sold as a phone.

Reboot your phone more often.
[Nexus 5 General] Kroniq:
To the people complaining about Franco Kernel... Would trying another kernel be out of the question? I've noticed with code blue and Franco r72, there is a WiFi wake lock and higher ram usage. Neither exists for me on elemental x 2.11
[Nexus 5 General] DevJan:
I have a nexus 5 device. I have installed the officially published android 5.1 image. The device was wiped when I unlock the fastboot as expected. After that, I have installed the everyday apps and games from only play store.

The current uptime 61 Hours

Memory usage

System: 1.1 GB

Apps: 310 MB

Free: 434 MB

Device is still responsive. Nothing is restarting, yet! But people says their device uses about 350MB after 24 Hours uptime. I think there must be something wrong. I wasn't expecting that after so long wait. I am really disappointed.
[Nexus 5 General] Kroniq:
Have you rebooted since you've installed 5.1?
[Nexus 5 General] DevJan:
Once, after the device automatically installed all my previous applications. I also locked the fastboot again.
[Nexus 5 General] christopherrrg:
Getting it with the new EA UFC freemium app. Thought it was the app, gonna try farm hero saga.

Sent from my Nexus 5
[Nexus 5 General] MrMarques01:
From the code issue comments:

"This has been fixed internally. We do not currently have a timeline for public release."
[Nexus 5 General] frigidazzi:
In other words. We released Android L last summer and knew about the memory leak then. Don't expect it to be fixed and released by this summer either.
[Nexus 5 General] crispi7:
Thats not a System memory Leak. If you notice that problem, you should contact the game devs. If an apk leave objects and services alive, Android can do nothing. Flame game devs instead. Seems the memory leak has been fixed
[Nexus 5 General] C3C076:
Yeah, but in that case, one would expect excessive memory usage to be reported under "Apps" category, not "System" category.
[Nexus 5 General] Toleraen:
I loaded Final Fantasy 3 several times, swiped it from recent apps, and the system usage never went up. When I installed 5.1 I did a clean install from factory image (complete device wipe). I picked up my N5 days before 5.0 was released, and was always severely disappointed by the battery usage, app re-drawing, etc, but 5.1 over the last few days has been nearly flawless (although Hangouts crashes every few hours after disabling it, and group MMS messages aren't downloading properly).

I'd factory reset and try the apps you're installing. Anytime there's a new OS released certain apps behave poorly. Maybe it is the OS, maybe it's the applications.
[Nexus 5 General] crispi7:
Anyway everybody should know the basics. If it just happen opening an app, obviously its an app problem.
[Nexus 5 General] ruoani:
Already fixed.

https://code.google.com/p/android/issues/detail?id=159738#c34
[Nexus 5 General] jzviagin:
Does 'fixed internally' mean that the code was submitted to AOSP?
[Nexus 5 General] becas22:
Altough is has been fixed now I am not getting any redraws
[Nexus 5 General] pfmiller:
That's just wrong. Misbehaving apps are the kernels problem. An operating system should never need to be restarted because of something it allowed an app to do.
[Nexus 5 General] opssemnik:
thats why memory managers exists, infact ART does have one and its GarbageCollector, now if a DATA APP can cause the whole system to glitch, isn´t a system fault?the GC should have to take care of it, and infact, it always did, you dont see that happening on kitkat, and imagine this, if this is just the apps fault, that mean i can code a bad intentioned app that keeps doing that so your system glitches out... .
[Nexus 5 General] Mohamed Yaser:
Facebook messenger Causes This Proplem
[Nexus 5 General] BennyJr:
Its a good guess, but it doesn't mean it has been. We are on r1 right now, so maybe r2 will have it.
[Nexus 5 General] markdapimp:
The system itself is having issues releasing allocated System memory caused by certain Apps

I can go 12+ days with my Nexus 5 just using only Spotify, Pandora and Snapchat and the memory leak wouldn't plague me one bit.

Let me reiterate this for you; Yes, there is a problem with the OS not releasing allocated memory, HOWEVER it is caused by a handful of apps.

"This issue has been fixed internally" could mean that Google will contact these developers to make some changes as a workaround and or fix it in AOSP.
[Nexus 5 General] opssemnik:
unless it´s fixed in 5.1.1_r3 (LMY48B) don´t get your hopes up (im running 5.1.1_r2 LMY47V)

also you are one lucky guy, or im one unlucky one, after 900mb-1gb all my apps gets to restart(including play music, mixradio, gmaps and even claro´s br own apps) :C, but its definetly better than 5.0.x

EDIT: apex? whoa nostalgia back to ics days
[Nexus 5 General] kicksilver:
Those are AOSP submissions.

Google doesn't document driver and binary modifications on nexus devices, hence different build numbers.

But, fingers are crossed.

Enviado do meu Nexus 5
[Nexus 5 General] opssemnik:
r3 isn´t up for anyone, not even via ota, however the info´s about it have been leaked by sprint on their OTA page.

soon it will be up on AOSP.

TBH at this moment, im more excited about M (5.2?) being show at I/O
[Nexus 5 General] kicksilver:
I didn't understand what you didn't understand.

Enviado do meu Nexus 5
[Nexus 5 General] opssemnik:
the different build number is just a newer revision, it will be uploaded to aosp soon, but at this moment it isn´t live for anyone. i just talked about it because sprint leaked some info about it on their OTA page. see my edited post

http://support.sprint.com/support/a...UpdateTheSoftwareVersionOnYourGoogleNexus5#!/
[Nexus 5 General] kicksilver:
Yes, at this point everyone knows the build number is LMY48B.

You said AOSP's 5.1.1 build hasn't fixed the memory leak. I responded that the changes between the builds aren't just what is in the changeless, because Google doesn't document the modifications in the binaries and drivers.

Anyway, let's hope they have fixed it this time.

Enviado do meu Nexus 5
[Nexus 5 General] opssemnik:
oh now i get, but once again, if it was just the drivers, every other lollipop device wouldn´t have it
[Nexus 5 General] cookiehead2:
Can you try swiping this app off a few times, then uninstall and reinstall it? Also try clear cache and clear data, and see if that fixes the memory issue after you start to see it.
[Nexus 5 General] faizalmzain:
try running stock rom and see whether it still persists.

honestly since 5.1, no more lagging because of memory leak for my stock 5.1, i'm not even root it.
[Nexus 5 General] j3poii:
Memory management was too bad, really. Unfortunately, battery usage suffered too. Less than 10 hours for regular use. Too much lag. The camera! For me, lollipop is crap for gn5.

I'm back to Kitkat, the best and natural rom for GN5. After all, Kitkat is really the rom made for gn5. Lollipop is for gn6. Sadly that is how android works.

It is so much different with ios. I had the ipad 2 since 3 years now, update has always been hassle free. I got the ip6+ now, I like it. My gn5 with KitKat is almost if not as smooth as the ip6. I don't have to reboot unless my battery died. Ah, life with KitKat!

Note: The only thing bugging me is the update notification. But it's ok, it's worth it. I don't want to mess with the system.
[Nexus 5 General] jack-itb:
I also experienced this memory leak with both stock rom and cm 12.1. Stock Rom is unusable after less than a day with my app usage while cm seems to fill the system RAM a little slower. Now I tried rastapop and the leak is gone! The installed apps are the same that I used on the other roms. Can someone confirm that?
[Nexus 5 General] constantinos360:
Yeap. After 278 hour up. :good: