Nexus 6p MHC19I high RAM usage? - Nexus 6P Q&A, Help & Troubleshooting

Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.

Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...

Alex338 said:
Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Click to expand...
Click to collapse
That's so odd for someone on the bleeding edge to have issues. Give it time

do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs

dontbeweakvato said:
That's so odd for someone on the bleeding edge to have issues. Give it time
Click to expand...
Click to collapse
I'm impatient. They've had a whole day to work out the bugs
Pain-N-Panic said:
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Click to expand...
Click to collapse
Yeah Feb factory image was basically perfect for me. I don't use Bluetooth much so didn't have any of those issues. I had no issues flashing, but like I said I'm stock with no root, so no twrp to worry about. And yes we buy these phones to experiment!
Update: Had the phone completely freeze on me. First it lagged like crazy and wouldn't respond to touch, then screen went blank. Had to hold down power until finally it shut off. Seems to be fine after a reboot. I definitely never had anything like that happen since I got the phone. Hopefully it was some random one off bug!

quantumqweef said:
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
Yep I'm aware of all that. Like I said, not really a complaint, more of an observation.

Related

I don't know how anyone is stable with GB.

Whether it's a Gingerbread ROM, or just pre-rooted GB Motorola ROM, I am not stable. I get random freezes sometimes, but more often I just can't turn the screen on. It turns on, but is completely black (but you can tell it's on) and I have to do a battery pull. Liberty GB (all versions) do this as well. No GB ROM in existence is stable. I go back to .340 stock Froyo SBF or back to some other Froyo-based ROM, everything is fine. The problem never happens once.
HOW ARE YOU GUYS HAVING STABLE GINGERBREAD ON THE DX?
Ugh. Rant over. If it was a hardware problem, it'd happen at least occasionally on Froyo.
My next phone is so going to be an HTC or Samsung.
Absolutely no problems at all using Apex 2.0 RC2. Gingerbread AOSP.
No problems on prerooted GB. I was having that issue with rooted Froyo towards the end before I upgraded. It would mainly happen when I used Maps and as far as I could tell it was the GPS screwing up because when I turned off GPS my phone worked fine. I have yet to turn on GPS on GB, food for thought.
Sent from my DROIDX using XDA App
Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86
try cyanogen its pretty fukin awesome. only bugs so far are vieo camera and hdmi. other than that its fast n stable...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
Cyph' said:
Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86
Click to expand...
Click to collapse
I don't think it's Win7 64bit causing the issue, I'm running it at home and work and I haven't had any issues connecting or disconnecting my phone. I would really recommend SBF'ing back to Froyo, clearing data and cache a few times, and starting with a fresh ROM. And if you have TB backing up any system data, don't restore that, just apps + data.
I love how people say they will switch to a different device manufacturer as if they expect that device to be 100% flawless.
I use prerooted GB .588 and I don't have any freezes and the random reboots stopped after I did a factory reset.
I,ve been running 596 deodexed since the first day it came out with no issues. Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Sent from my DROIDX using XDA Premium App
.596 rooted deodexed. Perfectly stable. Are you overclocked?
The only time mine froze was when I went from having it underclocked at 800 MHz to overclocking at 1.4 GHz. But I expected that to happen lol
Sent from my DROIDX using XDA App
Liberty is working great for me. I have had one freeze up since may.
Sent from my Xoom using XDA Premium App
My Verizon Droid X works great with GB. Even pushed it with Netflix and Hulu. I burn about 2200 min a month of cell time on avg. No issues.
I am running the latest DarkSlideX on my DX. It's flashed on top of TBH's 2-part 596. It's fast, stable, and has pretty good battery life, too. I had a reboot issue the first day with it, but a couple reboots and it hasn't hiccuped in over a week.
My DroidX Thrives on the DarkSlide!!
I have had about 1 of the problems you've discribed: The lockscreen blackout but that only happened once.
The problem is that you are probably deleting necessary files with Titanium backup. The crappy thing about GB is that half of the apps on the system that moto puts in there are interconnected with everything else so if you kill one app it'll make your phone die. I have never had the random freezing; but If I were you I'd delete WInzip if you have it on your phone. This is the main reason for a lot of my gingerbread issues. I now use ProPlayer: you can either get it free somewhere online, or off the market[place for like 3 bucks.
Everything is now working great.
Massgainer said:
Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Click to expand...
Click to collapse
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.
You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.
BBJohnnyT said:
You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.
Click to expand...
Click to collapse
After SBF'ing, I've always had to (so far) wipe data and cache to stop it from bootlooping anyways, which is basically the same thing as doing a factory reset.
Roland Deschain said:
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.
Click to expand...
Click to collapse
Nothing to add, just wanted to say "Hile, Gunslinger!" (just finished the audiobook version of DT 7).

[Q] Help a fellow Epic user out please!

So I'm really struggling here. I hate using stock ROM's because the battery life really blows and they are slow.
I've flashed a number of custom ROM's that speed up the phone significantly and drastically improve battery life. The only problem is after a few days of use I almost always start to get intermittent problems like random reboots, force closes and texts not going through etc.
I always follow the install instructions to a "t" and I still get problems. I must be missing a step somewhere along the way or not fully understand the cons of running custom ROM's or something.
I'm at my wits end. At one time I thought it must be the phone so I swapped with Sprint but I still have the same problems.
Currently I am running Scrambled EGgs22 V7 and I love it (when it works). I've tried bonsai, urban roms, you name it. Its the same results with every one. They work fantastic at first and then slowly become unusable.
Is there anybody out there who has experienced something similar to this and can help me remedy?
Having journaling enabled does help with data corruption if you find yourself having to start over a lot due to force closes.
Are you under/overclocking and/or undervolting at all? IIRC, stock speeds are ~400/1000Mhz.
Sounds like journaling is youjr answer. Make sure it is enabled and never pull the battery without shutting the phone completely down..after the vibration.
Sent from my SPH-D700 using XDA App
Kafluke said:
So I'm really struggling here. I hate using stock ROM's because the battery life really blows and they are slow.
I've flashed a number of custom ROM's that speed up the phone significantly and drastically improve battery life. The only problem is after a few days of use I almost always start to get intermittent problems like random reboots, force closes and texts not going through etc.
I always follow the install instructions to a "t" and I still get problems. I must be missing a step somewhere along the way or not fully understand the cons of running custom ROM's or something.
I'm at my wits end. At one time I thought it must be the phone so I swapped with Sprint but I still have the same problems.
Currently I am running Scrambled EGgs22 V7 and I love it (when it works). I've tried bonsai, urban roms, you name it. Its the same results with every one. They work fantastic at first and then slowly become unusable.
Is there anybody out there who has experienced something similar to this and can help me remedy?
Click to expand...
Click to collapse
Kafluke said:
So I'm really struggling here. I hate using stock ROM's because the battery life really blows and they are slow.
That's about the biggest lie over stock.. I started with a custom rom and it sucked the world's biggest donkey balls on battery life. It can last me the whole day on EC05. Just gotta learn how to optimize bro.
SchizioPunk's Epic Experience 2.1 Eclair -> Odin to EC05 Froyo. Rooted. Bloatware Removed. Voodoo Sound V9 Module Loaded. TouchWiz4. Enjoying my Customized Stock Experience.
Click to expand...
Click to collapse
Run 'Fix Permissions' from Rom Manager. That has solved FC problems for me in the past.
Have you tried reformatting your SD card? If it has gotten mucked up, I imagine that could start causing issues.
justppc said:
Run 'Fix Permissions' from Rom Manager. That has solved FC problems for me in the past.
Click to expand...
Click to collapse
Dont forget clearing dalvik and cache does also. I'm assuming people think that'll erase their stuff but It doesn't.
Sent from my Epix 4G using XDA
So how do I turn on journaling exactly?
Kafluke said:
So how do I turn on journaling exactly?
Click to expand...
Click to collapse
Edit: there should be a zip file that came with Epicurean to enable journaling.
There I a zip file that you can flash. I'll look for it
Posted by Mr. Z's Epic 4G.
I can't win. I enabled Journaling and my performance and speed went to crap. I guess I either have to suffer through the crappy stock rom or deal with force closes and random crapiness with a custom rom.
Kafluke said:
I can't win. I enabled Journaling and my performance and speed went to crap. I guess I either have to suffer through the crappy stock rom or deal with force closes and random crapiness with a custom rom.
Click to expand...
Click to collapse
If you want to disable journaling then just make sure to never shutdown your phone improperly or drop it and keep good backups to restore from. I like to do a nand every 3 or 4 days then I can always do a restore advanced data only.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
If you want to disable journaling then just make sure to never shutdown your phone improperly or drop it and keep good backups to restore from. I like to do a nand every 3 or 4 days then I can always do a restore advanced data only.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Are you serious? I don't ever drop my phone or shut it down improperly. I shouldn't have to back up my phone and restore twice a week in order to have a working device.I should be able to use this 400 dollar device without restoring it every fourth day or charging it twice a day.
Did you try the stock EG22 leak? Thats what I use, deodexed from decadence with the plus kernal from chris41g. It performs well and is the best battery life I ever had.
Kafluke said:
Are you serious? I don't ever drop my phone or shut it down improperly. I shouldn't have to back up my phone and restore twice a week in order to have a working device.I should be able to use this 400 dollar device without restoring it every fourth day or charging it twice a day.
Click to expand...
Click to collapse
True, that is why your $400 device comes with stock ROMs that are RFS so none of these FCs happen unless a third party app is written poorly. If you run custom ROMs these are the chances and prices you pay.
A $2000 computer still requires regular backups for the very same reason.
Kafluke said:
Are you serious? I don't ever drop my phone or shut it down improperly. I shouldn't have to back up my phone and restore twice a week in order to have a working device.I should be able to use this 400 dollar device without restoring it every fourth day or charging it twice a day.
Click to expand...
Click to collapse
BUT! Your forgetting something: you paid $400 for a phone
which Sammy provided to you via the vender of your choice with a STOCK ROM preloaded which works that way they have wanted.
Now from the moment you came over to the dark side and preloaded a rom there are good things and bad things that come with the package and you can't blame sammy for them.
Also, this is the world of trial and error: what may work fine for 500 phones will not work sometimes with yours. Every part of your phone though it could of been made the same day and from the same batch of my phone, are different and this will make you have different results.
Keep that in mind, your in a world that pose much risk to your device, but that's the fun part! Taking the risk and rolling with it!
Sent from an Epic with 4G
I am running SFR 1.2 with journaling on and can get all day with 3 to 4 hours screen on time , no force closes or any problems and all the smooth and fast goodness that comes with the rom.
Sent from my SPH-D700 using XDA App
megabiteg said:
BUT! Your forgetting something: you paid $400 for a phone
which Sammy provided to you via the vender of your choice with a STOCK ROM preloaded which works that way they have wanted.
Now from the moment you came over to the dark side and preloaded a rom there are good things and bad things that come with the package and you can't blame sammy for them.
Also, this is the world of trial and error: what may work fine for 500 phones will not work sometimes with yours. Every part of your phone though it could of been made the same day and from the same batch of my phone, are different and this will make you have different results.
Keep that in mind, your in a world that pose much risk to your device, but that's the fun part! Taking the risk and rolling with it!
Sent from an Epic with 4G
Click to expand...
Click to collapse
I don't have any problems with the stock rom. I'd love to have a stock rom that doesn't blow on battery life.
I understand that there are risks and pros and cons with custom roms but I can't seem to get a custom rom that is stable in any way shape or form. I assume that its my fault because I don't see anybody else having the same problems.
I guess I'm just looking for some help in getting a "half decent" custom rom experience but I can't even get that far. Without fail, every time I load a custom rom I get force closes and random issues. Then I go back to stock rom and I'm charging after two hours of use. I can't win.
@mark8503 I'll give that stock EG22 leak a shot and see what happens.
Thank you for everyone's help!
@mark8503
I assuming this is the stock rom you speak of:
http://forum.xda-developers.com/showthread.php?t=1183558
and this is the kernel:
http://forum.xda-developers.com/showthread.php?t=1185221
Please confirm.
IMO, if turning journaling on slowed down your phone enough for you to notice, something went wrong
I've run the on and off zips, and the difference is hard to see
Also, since RFS has a journal feature, I can't see how EXT4 with journaling on would be slower, all other factors being the same
You want stable and solid, ODIN an EC05 modem, install SRF 1.2, do you voltage setting, and call it a day
If you want the bleeding edge, you just have to accept you need precautions, as on the edge, **** happens.
Pick your poison and go with it
This Epic post as brought to you via Tapatalk
5:50 pm and battery is awesome! So far so good, this deodexed stock EG22 is running great, no FC's, no random reboots and battery life is excellent with chris41gs kernel. I just hope I didn't jinx it.
I'll report back after a few days of use.

Spontaneous Reboots Atrix / OTA Gingerbread

My Atrix is running stock Gingerbread, rooted. It has spontaneously rebooted between twice a day and once every-other day since I did the OTA update last summer. I am experiencing 8 to 10 reboots per week.
I don't care at all about the finger-print scanner and only care somewhat about webtop. I do care about the reboots. This makes me consider CM7.
I don't know the root cause of these reboots, the usual suspects being, poorly written apps, kernel bugs and flaky RAM. I have not been able to detect any pattern that points to any one cause.
Q1: Is this typical OTA-GB behavior on Atrix?
Q2: What is the stability of the latest CM7 beta? Does anyone actively running it (daily usage) experience this level of random reboots. I am hoping for responses from CM7 daily drivers, not users who swap ROMs frequently.
Thank you.
Q1. Yes, I had a 4-5 reboots in a week. Usually happened when my data got stuck.
Q2. Not one reboot, yet. On CM7 for alittle over a month now.
Sent from my SAMSUNG-SGH-I997 using XDA App
I am running CM7, and have been since the beta came out. No problems whatsoever, except maybe the wifi, but that's to be expected. Before that I was running stock GB, updated OTA, also no reboots. I think it's a little weird that yours is rebooting that often, how long have you had that phone? Perhaps it's hardware related?
Sent from my MB860 using Tapatalk
I got my Atrix on opening day. If it is failing RAM, I need to check on my warranty limits with ATT.
What is the issue with Wifi and CM7? I have not noticed wifi issues on OTA-GB.
The media apps I frequently run are TuneIn, Podtrapper, PowerAmp, I also run news apps for BBC, NYTimes, Bloomberg, CNN & NPR. Many of my reboots happen when moving in or out of TuneIn and PodTrapper. I can't definitively say these apps are the problem because I keep them running most of the time.
Good data point. Thanks.
I have delt with reboots since purchasing the phone, and accross all of the roms that I have tried(both official and unofficial). Recently my WiFi failed. If I turned on the wifi it would just say error and sometimes reboot the phone. after wiping the phone completely I tried stock, cherry pi, and cm7. CM7 was the only one that would last more than 2 minutes without rebooting but I could still not turn on wifi. I became convinced that I had defective hardware and had the phone replaced. There is a good chance that you have defective hardware.
Shortly after starting this thread I changed from LauncherPro to GO Launcher. Since then the reboots have dropped to 1 or 2 total in the past month.
I don't that know all rebooting was the fault of LauncherPro but it seems clear that it was a significant contributor.
Sent from my MB860 using xda premium
More then likely it's one apps that you have installed are was undated from market.. Try doing factory reset then adding app"s 1 @ time to see which one is causing the issue.
No wifi or bluetooth
I'm running a rooted, unlocked, stock gingerbread. Everytime I attempt to kick off wifi or bluetooth, it reloads. I'm going to try CM7 and see if that helps
rlillard said:
My Atrix is running stock Gingerbread, rooted. It has spontaneously rebooted between twice a day and once every-other day since I did the OTA update last summer. I am experiencing 8 to 10 reboots per week.
I don't care at all about the finger-print scanner and only care somewhat about webtop. I do care about the reboots. This makes me consider CM7.
I don't know the root cause of these reboots, the usual suspects being, poorly written apps, kernel bugs and flaky RAM. I have not been able to detect any pattern that points to any one cause.
Q1: Is this typical OTA-GB behavior on Atrix?
Q2: What is the stability of the latest CM7 beta? Does anyone actively running it (daily usage) experience this level of random reboots. I am hoping for responses from CM7 daily drivers, not users who swap ROMs frequently.
Thank you.
Click to expand...
Click to collapse
Well at this point, it's not broke and l'm not going to fix anything.
As I said, I don't entirely blame LauncherPro, but suspect it was conflicting with another application. I haven't seen a flood of complaints about LP.
At this point, I am quite pleased with my Atrix. I have no desire to get one of the new phones.
Sent from my MB860 using xda premium

It's Too Slow...

Stock, unrooted, 16GB, original Nexus 7 (with plenty of free space 6GB), but over the past few updates it has slowed to a crawl. I have wiped the App's caches and cache partition (which help for a short while), but it is still painful to use.
It is running 4.4.4 at the moment, and am wondering if a full reset will actually help for the long term. I thought the whole idea of KK was to improve performance on less capable hardware. If that is really the case, something is horribly wrong on mine.
Note that I have no interest in rooting or flashing unless it is absolutely necessary.
My original Nexus 7 with 8gb has recently been horribly slower too. I am rooted and running the latest official release of CyanogenMod. I have over 1 gb free. I am guessing this problem is fairly basic or low level and that (hopefully) others are seeing it too so it can be fixed.
16 GB and it can get painfully slow, at times.
I uninstalled Facebook which made a world of difference, and now I can reboot when it crawls to get it back to decent speeds.
Yeah, rebooting it helps, but only for a short while. So none of you have recently done a factory reset?
Sent from my XT1095 using Tapatalk

Android N 7.0 performance issues

After upgrading everything was nice and smooth for the first couple days but now I've hit some hard performance and lag issues especially keyboard lag. I experienced these on the developer previews on every preview so I always downgraded but this is kinda ridiculous to experience this on the official release of Nougat. Anyone else having these problems? Any fix? Clearing cache is not a workable fix, it only helps for a small amount of time say 20mins and then it's right back yo lag central. Hugely frustrating as this is my only device.
Worse than MM? I'm honestly disappointed with the performance of the device. Recommended it to my girlfriend when she had to upgrade from her iPhone, and performance is atrocious on MM. It seemed like a memory leak, because rebooting would help for a day or so, then the stuttery laggy mess comes back. It's performace pales next to my Oneplus One . I hoped the Nougat update would help fix those issues?
Ive never had any lag issues on MM or Nougat
Didn't have lag issues on MM(I'd say performance went doing after the 6.0.1 release especially in the battery dept tho.) but Nougat has been atrocious. I don't understand how mkbhd was saying he had no problems with developer preview or 7.0 because its apparent after a day of use. I've rebooted my phone like 5 times so far tonight clearing my cache each time and sure enough an hour or more later it's right back to lag town. I will say it's gotten better since dev preview 5 but it's still too bad for daily driver. Who the actual **** is working on the Android team at Google? This has been reported and known since preview 1 and yet it seems to never be addressed
Lately Google's quality of work seems to be: ¯\_(?)_/¯
Yeah, I'm seeing bad intermittent lag and stutter on 7. I also saw it on 6. 0.1 though. It may just be a hardware issue with the rubbish 810?
Sent from my Nexus 6P using Tapatalk
7.1??
shanxybeast said:
7.1??
Click to expand...
Click to collapse
He didn't say seven dot one (7.1), he said seven period space (capital) eye (7. I).
So here's something interesting, after I uninstalled screenwise panel I haven't been experiencing the keyboard and performance lag
No lag here on stock unrooted nougat. Has to be a third party app. Battery life has been a unicorn on nougat I must say. When the phone dirty flashed nougat over marshmallow i had terrible battery life. Lost 25% precent in just two hours! Factory reset cleared that up so o thought. This morning after leaving the house and the charger, phone felt slightly warm on hostler. Checked it and sure enough, down to 80% in 2 hours. Rebooted and problem was gone. I hope i don't have to reboot every day to get good battery life. I believe this is not the same update Google will push to non beta members. Hopefully the "release" version will have these things sorted out.
Sent from my Nexus 6P using XDA-Developers mobile app
The 7.0 pushed to the beta users is the same release version, there aren't two different Roms. Also while uninstalling screenwise panel seems to have cleared up the majority of the lag, there is still Ram Memory problems and slight stuttering
Factory data reset after EVERY MAJOR ANDROID UPDATE. If you haven't, you need to do that. After an update a lot of the time the temp and backup files aren't erased after the update and they can lead to performance issues. Especially on a new device you should not see any lag on the 6P on MM or Nougat.
In fact, I have seen my 6P even smoother and snappier on N over MM.
I never experienced any kind off issues on MM was very happy with the performance. Now that I have taking the Full OTA update to 7 I can tell a big difference in battery life and it's amazing. 7 has been running very smooth and buttery for me. But I've noticed that a lot of people that moved to 7 never factory reset their phone BC of losing data n such and most of them seem to be having a bad experience.
Soon as 7 booted after the update I then went in to stock recovery and factory reset the phone then went through the set up installed all my apps then flashed TWRP 3.0.2.1 then made a backup of r he stock ROM. Then flashed superuserUpdate 2.76 booted the phone and restored all app data via Titanium backup ran for a few days to make sure no issues was going to pop up then made another backup.
Currently I'm 7 all stock with stock kernel and root. The only mod I flashed was the soft key swap.
And during the wipe n stock recovery I wiped the internal storage also..
But hope you get it figured out man BC it's really worth the move..
Sent from my Nexus 6P using Tapatalk
Eric214 said:
Factory data reset after EVERY MAJOR ANDROID UPDATE. If you haven't, you need to do that. After an update a lot of the time the temp and backup files aren't erased after the update and they can lead to performance issues. Especially on a new device you should not see any lag on the 6P on MM or Nougat.
In fact, I have seen my 6P even smoother and snappier on N over MM.
Click to expand...
Click to collapse
why not just download a free app like cc cleaner that can get rid of files like those?
My 6P started acting weird the last 4 days. Apps will freeze then the pop up says app not responding close it or wait. Also the screen will not turn on when I hit the power button or use the fingerprint reader. I have to hit it many times before it comes on. I have booted into safe mode and still have the problem. I was running Preview 5 so my phone updated to 7.0 stable the day it was released. Everything was running smooth until Saturday night. Now it is about useless. Im hoping someone has a recommendation other than factory reset but I'm afraid that is going to be my only hope. Just don't want to waste another day setting this thing back up.

Resources