Database Users

Horrible Stutters and Freezes on New Replacement Device

I got a replacement device with stock rom recently and it suddenly started to experience stutters, lags and freezes frequently. For example, I'd be typing on the keyboard and suddenly everything stops responding. It happens in Chrome, randomly whenever I'm using the keyboard, and basically throughout the rom.
One solution is for me to wait 2 minutes and it might suddenly start responding. But the only sure solution that always works is for me to lock and unlock the device a few times (using the power button) and everything goes back to normal for two minutes until it lags and freezes again.
Thoughts anyone?
I had all the same previous apps on my previous Nexus 4 and had no problems....

RMA karma.......
........

These are tough to troubleshoot, but to narrow it down to hardware vs. software, I'd do a Factory Reset, and test, before signing into your Google Account and d/l'ing all your apps. If it works fine for a time/day, THEN sign in and only add a few apps (set Market auto update/restore off for the time being). Naturally do the apps your require daily first, and check stability for some time before adding back your 'fluff' apps. Often a poor app can be the culprit.

This happened to my nexus 7. I had it for about a month and i noiced that it started lagging really bad. Watching a video was just horrible and the responsiveness of it was bad. I just thought that it was a app or the custom rom i was running. I factory restored it and locked the bootloader and it still lagged. I just RMA'd it and i got a new one that was much better.

wideasleep1 said:
These are tough to troubleshoot, but to narrow it down to hardware vs. software, I'd do a Factory Reset, and test, before signing into your Google Account and d/l'ing all your apps. If it works fine for a time/day, THEN sign in and only add a few apps (set Market auto update/restore off for the time being). Naturally do the apps your require daily first, and check stability for some time before adding back your 'fluff' apps. Often a poor app can be the culprit.
Click to expand...
Click to collapse
Actually the keyboard is screwed up too. In gesture typing it randomly draws lower on the keyboard than I'm actually drawing. I'm guessing that it is a hardware or touchscreen sensor problem. I did an RMA and Fido Asurion promised to have a replacement to me by July 3rd. The only problem is that they only seem to send out refurbished phones for RMA's.

montrealguy said:
Actually the keyboard is screwed up too. In gesture typing it randomly draws lower on the keyboard than I'm actually drawing. I'm guessing that it is a hardware or touchscreen sensor problem. I did an RMA and Fido Asurion promised to have a replacement to me by July 3rd. The only problem is that they only seem to send out refurbished phones for RMA's.
Click to expand...
Click to collapse
Yeah..if it's acting up after a Factory Reset, then no amount of fiddling will solve it. Sorry man!

[Q] Phone sensors unresponsive for a few secs when receiving call.

Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!

I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app

Anyone found a fix for chromecast

Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk

Can you elaborate some more? I'm not having any issues like yours so give some extra information please.

mantrajt said:
Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk
Click to expand...
Click to collapse
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix

chgambini said:
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Hope this doesn't take them soooo looooong
Enviado desde mi SM-P600 mediante Tapatalk

I wonder if the Samsung phones running 4.4 have this too or is it just the tablets? I know the 12 inch version has this issue too.
It's the primary reason I'm still running 4.3.

chgambini said:
I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.

BarryH_GEG said:
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.
Click to expand...
Click to collapse
I think the percentage is bigger than we think. I have tried all the floor models at my local best buy and they to mess up. I to doubt samsung will fix this. I am not sure how to isolate the problem. The note pro I have access to is completely stock, the stock wallpapers for lock and home screens have not even been changed. I have factory reset both devices and have not installed any app other than the pre-installed stuff. Calling samsung doesnt help, I have already read of other forum members sending their tablets in to just have them sent back without being "fixed". There are more than one thread about this throughout XDA and other sites.
I have owned my 2014 since nov 2013. I haven't changed anything on it other than the update to 4.4. Thats why I beleive it is the cause. The moment after the update was complete, the chromecast problem happened.
I will say again, chromecast works as always fof many, many apps. Listening to google play music and google play movies seems to be the biggest offenders. I have read that the Crackle app has problems too.
My 2014 and pro are bogh 32g US version purchased straight from samsung. Both have never been rooted.

chgambini said:
I think the percentage is bigger than we think.
Click to expand...
Click to collapse
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.

blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
I assume your using google play music/movies too

chgambini said:
I assume your using google play music/movies too
Click to expand...
Click to collapse
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.

blinkingled said:
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.
Click to expand...
Click to collapse
I can watch youtube and hbogo with no problems. Do you have the video playback issues as well? If I try to watch a video from g+ or a preview of a movie on google play, I will either get a black screen with audio only, or massive stuttering and lines while watching on the tablet in full screen.
I have sent feed back to Google on the music and movies apps. Lets see what kind of reply we get from them

blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.

SamsE=BarryH_GEG;52798927]What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.[/QUOTE]
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.

chgambini said:
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.
Click to expand...
Click to collapse
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.

BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
Yes I have done a hard reset on both devices, skiping past adding any accounts and unchecking the restore app data box.
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
No sdcard. I will try a hard reset again, unchecking all the google sync stuff. Got nothing to lose.......

Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?

BarryH_GEG said:
Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?
Click to expand...
Click to collapse
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data and added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use allsharecast to my Samsung TV and not the chromecast though

chgambini said:
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data aND added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use all casts hare to my Samsung TV and not the chrome cast though
Click to expand...
Click to collapse
Try turning off Chrome in Application Manager.

BarryH_GEG said:
Try turning off Chrome in Application Manager.
Click to expand...
Click to collapse
No change, still crashes

BarryH_GEG said:
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
That's an extensive and well thought out debugging list - thanks :good: (I had posted a message some time ago to gather info from people having and not having the issue - but I think we only got 2-3 uncertain data points.) But at this point I have tried everything in your post - reset, with and without SD, without restoring apps, with and without updates. It still crashes. And the ChromeCast firmware was last updated was in mid April when it didn't have an issue with 4.3 - so that doesn't seem to be a factor either.
About being in the US - I think OP's tablet is Latin American version if I am not mistaken. It's really a mystery at this point as to why some of them work.

Nexus 6p freezing a lot

I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.

Juandos23 said:
I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.
Click to expand...
Click to collapse
Don't mean to scare you, but that is exactly what was happening to me right before going into an unrecoverable bootloop. Nothing I tried revived the device, although there have been some that have been able to. I ended up RMA'ing my device as nothing I did brought it back to life. You might be in a different situation but just giving you a heads up.

*Bump*
Stock 7.1.1 and rooted here. I've been on the official 7.1.1 release for our 6P's since early December, and for the past week or so, I've been experiencing freezing as well. I'd be in the middle of typing in Hangouts, streaming music in the car via bluetooth and Spotify, or just waking the phone up from sleep. For the past few days, I've been getting 3-4 freezes per day.
On rare occasions, I've left the phone alone to settle, and it returns to normal, but more times than not, a hard reset is the only 'fix'; until the next freeze.
I reluctantly wiped the phone, unrooted, flashed stock 7.1.1 and re-rooted all via NRT last night. The phone froze again this morning coming off the charger...
Granted, it decided to restore 528mb's worth of WhatsApp history as soon as I unplugged it (why it didn't restore on charger overnight is beyond me though). Will update if it freezes again.
The phone runs butter smooth with zero issues other than these freezing occurrences though. MO, the 6P is the best all-rounded phone currently available, even if it's a year old already.
Appreciate any help or suggestions!!

That's odd try ex kernel and over clock or try HEBF manager on play store

Quick update. Couldn't bear the multiple freezes per day, so I called Google to ask for help. Apparently I've done everything I can on my end (including a factory reset and updating to the latest firmware), so they sent out a replacement 6P to me free of charge. They'll also be covering the courier/shipping costs for my old 6P too. Fantastic customer service. Kudos to them!! I called them Tuesday morning (20th Dec) Australian time, and received my replacement 6P Friday afternoon (23rd Dec). Very quick indeed
Half a day after setting up my replacement 6P, including updating to 7.1.1, I started getting the same symptoms as my old 6P. Freezing, unresponsiveness, etc. Persisted for another day and had enough. I've since done a full wipe and downgraded back to the final 6.0.1 release, and it's been stable as a rock for 3 days now. No freezes, lagginess, nothing.
So I deduce it might actually be a software issue with 7.1.1, and not a hardware problem. It appears a growing number of Pixel and Pixel XL users are also experiencing random freezes on their new phones running 7.1.1 too...
Looks like I'll stick with 6.0.1 until Google makes a formal announcement and something is done about 7.1.1. I've missed Xposed and GravityBox too, so 6.0.1 is all good. Most importantly, it's stable

Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1

redduc900 said:
Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1
Click to expand...
Click to collapse
Thanks for the pro tip. I did consider doing that with the replacement 6P, but the only apps that I had installed were the stock Google ones that came with 7.1.1, WhatsApp, Facebook, Twitter, Instagram and SwiftKey. I just assumed if such popular apps were the cause, a lot more people would have pinpointed them as the problem?
I did however read a few users claiming SwiftKey to be the culprit prior to RMA'ing my old device, but even after uninstalling that from my old phone, I was still getting the freezing issues.

[ISSUE] Possible Digitizer Malfunction?

I purchased the Turbo 2 a month ago and until about 2 weeks in I had no issues with the device. Out of, seemingly nowhere, the screen would go completely "static-y" until I got an SMS via Textra. I thought this would be because of a recent software update, but to my surprise, checking for another update (a fix), was a dead end.
Two days ago, I got rid of Textra in favor for another SMS app, and the issue occurred once more, this time after I had gotten a series of long Skype messages. A quick Google search told me that it may be an issue with the digitizer, but I do not think this is the case as it happened as a result of possible high use of the CPU (it's best NOT to quote me on this, hardware is not my strong point!). Any help would be greatly appreciated as I do not want to purchase a new phone.
Android 7.1.1, ‎XT1585