Status Update
Comments
ro...@gmail.com <ro...@gmail.com> #2
Well, I just noticed a torrent I was downloading still is at 0,5%, because the app that was downloading in background was shut downm, without warning,
This is really unpleasant.
This is really unpleasant.
dn...@google.com <dn...@google.com>
dn...@google.com <dn...@google.com> #4
Hi,
Can you provide the below requested information to better understand the issue:
logcat output
Seehttp://developer.android.com/tools/help/logcat.html . Copy and paste relevant sections of the logcat output into this issue.
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Can you provide the below requested information to better understand the issue:
logcat output
See
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
ro...@gmail.com <ro...@gmail.com> #5
Hi Dnaga,
Just a little update:
I'm at 696 hours (29 days) and multi tasking is compromised. All apps reload upon being brought to foreground.
Media players, downloads and all kinds of app that keep running in background also get shut down unexpectedly.
"System UI" is higher than ever, sitting at > 500mb.
As for the bug report, I've already shared with the email you provided, and here's the link anyway:
https://drive.google.com/folder/d/0B6JvEuk7Tm_aenA4LUxvSjlzNGc/edit
Just a little update:
I'm at 696 hours (29 days) and multi tasking is compromised. All apps reload upon being brought to foreground.
Media players, downloads and all kinds of app that keep running in background also get shut down unexpectedly.
"System UI" is higher than ever, sitting at > 500mb.
As for the bug report, I've already shared with the email you provided, and here's the link anyway:
dn...@google.com <dn...@google.com> #6
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
ro...@gmail.com <ro...@gmail.com> #7
Appreciate the quick response, Dnaga.
Hope you guys can work this out once for all.
I've just hit 720h (1 month) and System UI won't stop growing on RAM.
I suspect the system won't last much longer, soon it'll reboot on its own.
Until that, I'm unable to multi-task of even listen to music, because everything in background gets shut down in no longer than 5 minutes.
If you need anything else, feel free to ask.
Hope you guys can work this out once for all.
I've just hit 720h (1 month) and System UI won't stop growing on RAM.
I suspect the system won't last much longer, soon it'll reboot on its own.
Until that, I'm unable to multi-task of even listen to music, because everything in background gets shut down in no longer than 5 minutes.
If you need anything else, feel free to ask.
ro...@gmail.com <ro...@gmail.com> #8
The device shut off by itself today, at 725h of uptime.
Fyi
Fyi
ma...@gmail.com <ma...@gmail.com> #9
Same here,the last time i've rebotted my nexus it was when I've taken the last security update weeks ago, today the phone was slow, the launcher reload itself often , wuze and the others apps were not usable.
ra...@gmail.com <ra...@gmail.com> #10
HERE WE GO AGAIN. Google and their uneducated testing methods. It kills me man. I actually saw this issue when I got the update and my launcher was redrawing more often than it did on Android L 5.1.1. This was on my Nexus 7 2013, which had finally started to behave smooth since it's last two updates on L. Now on Android M, it's basically memory leak issues again.
As for my phones. I had an Moto E and Moto X 2014,2015. Both of which with 5.1, never had the issue fix. It's even worst on the E with 1GB of ram. The leak caused a terrible experience on an otherwise good phone. It would happen after 24hrs, things got real slow and relaunched alot. Yet, some days it would run real smooth with same apps after 48hrs. Motorola engineers told me there is no issue. Called them idiots because the issue was clearly present. They, like Google, don't seem to know how to test well since they are lazy and don't care for user experience. Also they seem factory reset very often and test with limited apps as if that's gonna be a real user scenario.
Now I have 6P. With so much RAM, it's hardly a issue. But there days were my launcher still redraws and music app kills itself after I open a site.
I love Android. Just wish they'd focus on the user more.
As for my phones. I had an Moto E and Moto X 2014,2015. Both of which with 5.1, never had the issue fix. It's even worst on the E with 1GB of ram. The leak caused a terrible experience on an otherwise good phone. It would happen after 24hrs, things got real slow and relaunched alot. Yet, some days it would run real smooth with same apps after 48hrs. Motorola engineers told me there is no issue. Called them idiots because the issue was clearly present. They, like Google, don't seem to know how to test well since they are lazy and don't care for user experience. Also they seem factory reset very often and test with limited apps as if that's gonna be a real user scenario.
Now I have 6P. With so much RAM, it's hardly a issue. But there days were my launcher still redraws and music app kills itself after I open a site.
I love Android. Just wish they'd focus on the user more.
ro...@gmail.com <ro...@gmail.com> #11
Yeah, what a shame.
Hope they can sort this out this time.
Hope they can sort this out this time.
ta...@gmail.com <ta...@gmail.com> #12
Since this wasn't the case in 4.4 Kitkat, I bet it has to do with ART runtime. 1 year and 5 months since Lollipop Preview and still isn't fixed, good work Google!
ia...@gmail.com <ia...@gmail.com> #13
Please Google PLEASE fix Android! There have been so so SO many issues since the first Lollipop preview. And Marshmallow still has so many issues :/
It's sad.
It's sad.
gi...@gmail.com <gi...@gmail.com> #14
** READ THIS BEFORE POSTING A COMMENT **
Posting "me too" or bashing Google delays fixing this issue. Google ignores bug reports with unrelated posts. If you want this issue fixed as soon as possible, please star the issue (top left corner of the page) without commenting. Thank you.
** READ THIS BEFORE POSTING A COMMENT **
Posting "me too" or bashing Google delays fixing this issue. Google ignores bug reports with unrelated posts. If you want this issue fixed as soon as possible, please star the issue (top left corner of the page) without commenting. Thank you.
** READ THIS BEFORE POSTING A COMMENT **
az...@gmail.com <az...@gmail.com> #15
Doubt it's really ART. I enabled ART on KitKat and didn't encounter this. If anything, my device ran faster
ad...@gmail.com <ad...@gmail.com> #16
Here are some links where this issue is hitting Nexus 5x users really hard. Please take a look for more user feedback.
Priority should be changed to something higher than Small.
https://productforums.google.com/forum/#!topic/nexus/VDpAhli9X3c;context-place=topicsearch/5x$20lag
https://www.reddit.com/r/Android/comments/3ua0ad/nexus_5x_performance_issues/
Priority should be changed to something higher than Small.
ro...@gmail.com <ro...@gmail.com> #18
Update:
Uptime: 724h (30 days or 1 month)
SYSTEM UI grows in RAM non-stop. After a reboot it'll sit under 100mb, now it's over 5x that amount...
Uptime: 724h (30 days or 1 month)
SYSTEM UI grows in RAM non-stop. After a reboot it'll sit under 100mb, now it's over 5x that amount...
ro...@gmail.com <ro...@gmail.com> #19
I'm really GLAD to announce that this has been fixed in MMB29V.
Over 180h and SYSTEM UI hasn't grown at all.
Thanks Google for stepping up.
Over 180h and SYSTEM UI hasn't grown at all.
Thanks Google for stepping up.
ss...@google.com <ss...@google.com> #21
Hi,
The development team has fixed the issue that you have reported and it will be available in a future build.
Thanks
The development team has fixed the issue that you have reported and it will be available in a future build.
Thanks
ro...@gmail.com <ro...@gmail.com> #22
Hi there,
I wonder what happened since build MMB29V, where this problem was not present. Then, it returned in the following builds.
I suppose the changes you're making to the device tree is being overriden when generating newer builds?
I urge Google to pay attention to this, because this affects the user experience heavily. No one likes their phone to perform like a 256MB RAM equipped one.
Thanks for the attention anyway, hope not to run into this anymore in future builds.
I wonder what happened since build MMB29V, where this problem was not present. Then, it returned in the following builds.
I suppose the changes you're making to the device tree is being overriden when generating newer builds?
I urge Google to pay attention to this, because this affects the user experience heavily. No one likes their phone to perform like a 256MB RAM equipped one.
Thanks for the attention anyway, hope not to run into this anymore in future builds.
gr...@googlemail.com <gr...@googlemail.com> #23
Which future build is meant?
Next Monthly Update, Android 7 or later?
Next Monthly Update, Android 7 or later?
ro...@gmail.com <ro...@gmail.com> #24
#23,
Most likely July security patch.
Most likely July security patch.
ro...@gmail.com <ro...@gmail.com> #25
Will this fix be rolled into the new 'N' Beta that is out. I'm seeing similar memory issues on that.
ka...@gmail.com <ka...@gmail.com> #26
Please fix this in next monthly update! Any delay will definitely cause Android losing the market shares to iOS ( I am the potential customer ).
aj...@gmail.com <aj...@gmail.com> #27
Can you pls provide the patch which fixes this issue?
ja...@gmail.com <ja...@gmail.com> #28
hello, could you please help to provide the patch for this issue? thank you.
ka...@gmail.com <ka...@gmail.com> #29
Is this included in July 2016 patch?
ja...@gmail.com <ja...@gmail.com> #30
I have checked the N pre-release and security patch of July. None of those has the change regarding to this issue. How come? We've been waiting for so long.
he...@gmail.com <he...@gmail.com> #31
My Nexus 5 has low sound since upgrading. Please can someone help?
ka...@gmail.com <ka...@gmail.com> #33
The iPhone is “faster; smoother. Android freezes up” and has to be restarted too often, the source said. The problem with the Android is particularly noticeable when viewing live feed from an unmanned aerial system such as Instant Eye, the source said.
http://www.dodbuzz.com/2016/07/15/army-sof-to-trade-in-its-androids-for-iphones/
Not sure if there is anything to do with this bug. But what a shame for Google and Google is still acting slow for bug fix.
Not sure if there is anything to do with this bug. But what a shame for Google and Google is still acting slow for bug fix.
ro...@gmail.com <ro...@gmail.com> #34
Yep, after KitKat there is no android version that deserves the "stable end-user release" status. I'd suggest to completely stop developing new features for at least one year and just fix bugs and finally fix the the Nexus 9 performance issues as I bought an expensive high end tablet that is only useful for waiting for a fix and now eol is near and I couldn't use it yet.
lo...@gmail.com <lo...@gmail.com> #35
#34, +1 to that...
je...@gmail.com <je...@gmail.com> #36
Phone gets almost full memory quite fast in daily use.
ro...@gmail.com <ro...@gmail.com> #37
Dear Google,
According to #21, this was fixed and was scheduled for "Future Release".
I don't know whether that meant the next security update (July) would fiz the issue, but if it was the case, I'm sorry to inform it failed.
The issue persists on MOB30P.
According to #21, this was fixed and was scheduled for "Future Release".
I don't know whether that meant the next security update (July) would fiz the issue, but if it was the case, I'm sorry to inform it failed.
The issue persists on MOB30P.
le...@gmail.com <le...@gmail.com> #38
Google is sluggish on this, treating it like it isn't even important...
re...@gmail.com <re...@gmail.com> #39
Srsly Google, why don't you just release a HOTFIX for this issue instead of letting us wait for an undefined amount of time because you don't tell us when the fix will be released!? I've to say I'm very disappointed by you at the moment cause of the huge issues in the last few releases...
ro...@gmail.com <ro...@gmail.com> #40
What frustrates me the most, is that hey have the fix (MMB29V) and they refuse to release it.
ep...@gmail.com <ep...@gmail.com> #41
Google do something.
I can't use my phone and i use it for my job.
Nexus 5 after last update microphone not work can talk only from speaker phone.
Any video, music not hear it.
WHAT YOU GONNA DO GOOGLE???
I can't use my phone and i use it for my job.
Nexus 5 after last update microphone not work can talk only from speaker phone.
Any video, music not hear it.
WHAT YOU GONNA DO GOOGLE???
an...@gmail.com <an...@gmail.com> #42
[Comment deleted]
lo...@gmail.com <lo...@gmail.com> #43
Oh, for God sake, people, we're receiving monthly SECURITY patches. Except one month with fix Nexus 5X, all of them didn't include any other changes made to the system (as far as I remember) and historically changes as big as this only included in a next major/minor release that never happened with 6.x.
It's like keep saying "Are we there yet?" I have it just as much as everyone release, but behave like a grown-up.
It's like keep saying "Are we there yet?" I have it just as much as everyone release, but behave like a grown-up.
ka...@gmail.com <ka...@gmail.com> #44
I agree, this is no place to complain. Just to talk about problems found and possible fixes or workarounds.
Whenever they think it has to be included, it will be. I guess they do not give it the importance many of you do, because it will be affecting a small percentage of users. So "Priority-Small".
Whenever they think it has to be included, it will be. I guess they do not give it the importance many of you do, because it will be affecting a small percentage of users. So "Priority-Small".
ri...@gmail.com <ri...@gmail.com> #45
After updating my motog2 to android6 my phone's memory usage goes up to 94%, which hardly reached 60% usage while on lollipop with same number of apps installed. My phone freezes, chrome gets crashed. I've done mistake to upgrade my phone to Android marshmallow.
as...@gmail.com <as...@gmail.com> #46
#42 may be right, but that likely means that the fix will never reach Nexus 5, since it's not getting 7.0
le...@gmail.com <le...@gmail.com> #47
Back up your MotoG and Hard Reset it. Marshmallow needs a reset on some
devices. I have a friend that had that very same issue and now has it
solved.
devices. I have a friend that had that very same issue and now has it
solved.
ia...@gmail.com <ia...@gmail.com> #48
Symptoms caused by this memory leak, cannot, under coder/developer terminology, be classified as "priority small".
Can anyone from Google confirm a release build or date that this fix will be released? That's what a reputable company would do, especially for a product affecting millions of users! As an Android user, I am not satisfied with "fixed...will be released in a future build..." Could you please be more specific?
Can anyone from Google confirm a release build or date that this fix will be released? That's what a reputable company would do, especially for a product affecting millions of users! As an Android user, I am not satisfied with "fixed...will be released in a future build..." Could you please be more specific?
ro...@gmail.com <ro...@gmail.com> #49
Unfortunately, this is not fixed in MOB30Y.
178h of uptime, and System UI is averaging at 170mb... Whereas in my girlfriend's Moto X 2014 running 6.0.1, it's at 70mb-ish with a 201h uptime.
This was solved in MMB29V, I don't know why Google can't fix this once for all.
178h of uptime, and System UI is averaging at 170mb... Whereas in my girlfriend's Moto X 2014 running 6.0.1, it's at 70mb-ish with a 201h uptime.
This was solved in MMB29V, I don't know why Google can't fix this once for all.
sj...@gmail.com <sj...@gmail.com> #50
@Google Is this fixed in Android 7.0 (Build NRD90M) on the Nexus 5X? After a few days of uptime I again had the symptoms of a memory leak in terms of unresponsive UI etc. I hope this fix is not in NRD90M and comes with the next monthly update or else the issue has not been resolved and needs further investigation :(
ka...@gmail.com <ka...@gmail.com> #51
Same here , still having UI not responsive.
Nexus 6p.
One more thing to add: my Antutu score is around 40k only. The way it score
is much lower then it should be . Nexus 6p now become middle to low end
phone. I wonder whats wrong ? Does this related to why the phone is perform
badly ?
Nexus 6p.
One more thing to add: my Antutu score is around 40k only. The way it score
is much lower then it should be . Nexus 6p now become middle to low end
phone. I wonder whats wrong ? Does this related to why the phone is perform
badly ?
sj...@gmail.com <sj...@gmail.com> #52
This obviously has also not been fixed in 7.0 build NRD90S since again after a few days I have memory leak symptoms and heavy performance issues. Hey Google, when will this fix finally be released?! It's VERY annoying :(
dn...@google.com <dn...@google.com> #53
Please provide the bugreport for the issue which you are facing on android N latest build.
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
jo...@joshstein.com <jo...@joshstein.com> #54
Google, since you said it was fixed, how about you share which build/release? Thank you!
sj...@gmail.com <sj...@gmail.com> #56
@ #54: Exactly! It would be nice if Google could explain in which version this has been fixed so that we can stop speculating and being frustrated...
Is it so hard to have a proper information policy?
Is it so hard to have a proper information policy?
so...@gmail.com <so...@gmail.com> #57
If you still encounter problems, please follow along with the instructions in post #53.
jo...@joshstein.com <jo...@joshstein.com> #58
@57: For those of us not on N, we would like to know if it was fixed before N and if so what version.
re...@gmail.com <re...@gmail.com> #59
I've still the memory leak issue on Android N, Nexus 5X.
After running the phone for several days, Android System takes a huge amount of memory, so that the average memory usage is about 1.6GB (of 1.8GB total).
Pls find the bug report here (I've shared this folder with you):https://drive.google.com/open?id=0B2FhIjFi96zBcEQ1QWxxaGM1aDA
After running the phone for several days, Android System takes a huge amount of memory, so that the average memory usage is about 1.6GB (of 1.8GB total).
Pls find the bug report here (I've shared this folder with you):
bo...@gmail.com <bo...@gmail.com> #60
It's same for me. I have Android 7.0 build NRD90R
sj...@gmail.com <sj...@gmail.com> #61
Attached you'll find a video displaying a very sluggish responsiveness of the Nexus 5X (7.0 build NBD90W) after a few days of uptime. You'll see that clicks on the power button as well as touch events sometimes are not registered or are delayed. Also you'll see that the launcher seems to be re-instantiated.
Additionally I attached a screenshot of the memory usage of the last 24 hours.
Additionally I attached a screenshot of the memory usage of the last 24 hours.
ma...@gmail.com <ma...@gmail.com> #62
After 213 hours, the system now do not permit the multitasking and the apps lag, if I put into background an app, android force close it and the launcher take a lot of time to show icons. Mayor use of battery. Nexus 5 all updated ota.
ma...@gmail.com <ma...@gmail.com> #63
Attachments
ro...@gmail.com <ro...@gmail.com> #64
It's unbelievable that this issue is still present in M4B30Z.
l....@gmail.com <l....@gmail.com> #65
It is indeed
l....@gmail.com <l....@gmail.com> #66
Did anyone try a custom kernel?
Description
I've been keeping my device ON for almost 28 days now, only to find out that "System" will continue to eat through your RAM non-stop, again.
Right after boot, it's at 300-400mb, and now I'm at almost 1 GB of usage, and it never decreases.
The symptons of lack of RAM are already well known:
- Launcher redrawing constantly when returning from home screen
- Musics apps get terminated for no reason in background, and you end up thinking your earbuds died
- Multi-tasking is virtually impossible, because the apps reload upon launching them, thus losing all your input info, like text, for example.
However, with Marshmallow's new "Memory" dedicated submenu, I think I managed to spot the culprit.
I noticed that "System UI" won't stop growing it's footprint. As you can see in the attached screenshots, it's maximum RAM usage exceeded the 580mb mark, and the average use is 472mb, which is more or less 4x the usage after a fresh boot.
All the other apps are OK in this regard. Even "Android OS" is keeping it cool.
I'm willing to help however I can, providing prints, logcats and whatever else is needed to investigate this.
- Nexus 5 D821
- Android 6.0 MRA58K
- Locked bootloder, totally stock software