Serious bug found in 5.0.1

Could this be the source of the problems with rebooting, shutting off all together, or freezing that have been reported by owners of the N6?
 
Could this be the source of the problems with rebooting, shutting off all together, or freezing that have been reported by owners of the N6?

Unlikely. The current theory is that those issues have something to do with accessing storage in certain situations on some units.

What happens here is that your apps close... none of your background apps stay cached in memory and switching in Recents will always cause a complete relaunch. The most obvious symptom of a memory problem is homescreen redraws. Your launcher is an app, just like anything else running on your system. But it also is a high priority one, so it Android will only close it out if it is absolutely slammed as far as memory usage goes and it only has enough space for the active application.

Eventually, what you'd see is that a launched app will close almost immediatly, even if it is active. I saw this on my wife's Nexus 5 when it was at 5.0 (it hasn't done this since I loaded 5.0.1 by the way).

I also see no indication that this affects the Nexus 6. It appears to be mostly 4,5 and 7 users. And I have yet to see any memory bleeds on mine, but I'm fussing with stuff so I'm typically not up for a week... but I'm two days of uptime in now and system is at 547MB. I have never once ran into any kind of behavior that would indication a memory leak on my 6 since I got it a month ago.

Incidently, I DID see some reboots earlier on when I was running 5.0 stock. But I'm kicking a 5.0.2 custom AOSP-based ROM and kernel (Dirty Unicorns) at the moment and haven't had any resets in quite a while (DU has been rock solid steady)
 
Unlikely. The current theory is that those issues have something to do with accessing storage in certain situations on some units.

What happens here is that your apps close... none of your background apps stay cached in memory and switching in Recents will always cause a complete relaunch. The most obvious symptom of a memory problem is homescreen redraws. Your launcher is an app, just like anything else running on your system. But it also is a high priority one, so it Android will only close it out if it is absolutely slammed as far as memory usage goes and it only has enough space for the active application.

Eventually, what you'd see is that a launched app will close almost immediatly, even if it is active. I saw this on my wife's Nexus 5 when it was at 5.0 (it hasn't done this since I loaded 5.0.1 by the way).

I also see no indication that this affects the Nexus 6. It appears to be mostly 4,5 and 7 users. And I have yet to see any memory bleeds on mine, but I'm fussing with stuff so I'm typically not up for a week... but I'm two days of uptime in now and system is at 547MB. I have never once ran into any kind of behavior that would indication a memory leak on my 6 since I got it a month ago.

Incidently, I DID see some reboots earlier on when I was running 5.0 stock. But I'm kicking a 5.0.2 custom AOSP-based ROM and kernel (Dirty Unicorns) at the moment and haven't had any resets in quite a while (DU has been rock solid steady)

Its def happening to my N6. I am currently on 2 weeks 3 days of up time. The system is hogging around 900mb of ram most I have seen is 1.3gb. Battery life has been stable though. Some redraws but not too many. A power cycle helps for about a week or two. Lollipop is getting better with every update.

Posted via THE Nexus 6!
 
Its def happening to my N6. I am currently on 2 weeks 3 days of up time. The system is hogging around 900mb of ram most I have seen is 1.3gb.

That could be related... I think the extra gig of RAM might be keeping the Nexus 6 from suffering most of the pain. The 4, 5 and 7 (2013) all have 2G of RAM..... so 1.3G eaten up by the system is bad juju.
 
Its def happening to my N6. I am currently on 2 weeks 3 days of up time. The system is hogging around 900mb of ram most I have seen is 1.3gb. Battery life has been stable though. Some redraws but not too many. A power cycle helps for about a week or two. Lollipop is getting better with every update.

Posted via THE Nexus 6!

Yeah I have seen 1.8 GB of ram so it's definitely affecting the N6.

Posted via the Android Central App
 
Unlikely. The current theory is that those issues have something to do with accessing storage in certain situations on some units.

Could you elaborate on this? Or maybe provide a link where I could read more? It seems like every time I look into this issue there are more theories that have been put out there. And it seems that some feel it has stopped on their phones, while others are still experiencing issues. Very confusing
 
I am currently on 2 weeks 3 days of up time.

Being that Lollipop is new, it's recommended that you reboot once in a while. Until there's an update, there's not much else to do. I shut down every night and don't have any major problems. If I leave it running for days, that's when I see glitches.
 
Being that Lollipop is new, it's recommended that you reboot once in a while. Until there's an update, there's not much else to do. I shut down every night and don't have any major problems. If I leave it running for days, that's when I see glitches.

Yea, I haven't had any real problems from the over use of ram by the system. Thank god it has 3gb of ram, if it was any less this phone would lock up after a week or two.

Posted via THE Nexus 6!
 
Being that Lollipop is new, it's recommended that you reboot once in a while. Until there's an update, there's not much else to do. I shut down every night and don't have any major problems. If I leave it running for days, that's when I see glitches.

That makes me feel a little better. I generally turn off the phone each night to charge it, since we have a land line as well. So it would not be hardship to do so----as long as they really do correct these issues soon. I can see a manageable problem turning into a big negative if I kept this phone for some years, as I hope to do.
 
Could you elaborate on this?

Look through the elementalX kernel thread on XDA. The dev was investigating reboots and he seems to be orbiting around something with the storage access for the non-kernel ones. Not a lot to go on, but it's better than the shrugs I've seen everywhere else.

Btw... They are getting fixed in the base. I fit a few reboots back when I first got the phone. Been running custom 502 stuff for a bit, not a single reset.
 
By the way, the memory leak is fixed... and it's already showing up in done custom Nexus 6 ROMs. Guess RAM access speeds see a 50% improvement too... but that might just be a couple of users.
 
LeoRex, Thanks so much for the information. I'll look up the thread on XDA, although much of it will probably be over my head. So good to hear that both the reboots and memory leaks are fixed. I'm guessing that, for many, the fixes will come with a future Lollipop release/update? This is such good news, because I have been holding back from purchasing until convinced there is a fix on the way.

So how much credit should Google give to the developers at XDA for helping them to narrow down the source of problems and come up with a fix?
 

Trending Posts

Forum statistics

Threads
956,794
Messages
6,970,071
Members
3,163,627
Latest member
glastek16