yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] NastyNeil:
Ordered my phone on November 23rd. Received the phone December 23rd. Had the problem since the first day and when I saw other people on the forums complaining of same issue I knew I had a dud. I contacted Moto last Monday and they gave me two options. One was to send my phone back and when they got it they would ship me a replacement, or they would put a hold of 500 dollars on my credit card and ship me a replacement with a prepaid envelope and box to send back my faulty phone. I chose the second option because I didn't want to be without a phone. The phone arrived Wednesday.
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Got it. I've had my phone for almost two months... Wonder if I'm outside the window for any free options.
[Nexus 6 Q&A, Help & Troubleshooting] SpL3rG3:
Sending my Nexus 6 back today! Finally the screen freeze issue happened on stock. Its definitely much less frequent on full stock but eventually it does happen. Strangely enough, on custom ROM's the problem appeared mainly when there was a video playing (be it a facebook autoplay video or a youtube video). On pure stock however, I had the issue happen more frequently when reading emails and/or forums on the phone. Not really a rhyme or reason to the issue which makes it more difficult to explain and resolve.

One other point. If you try to take a screenshot of this issue on the phone, the screenshot will NOT reflect the issue. This clearly makes it a hardware issue as the software acts as normal. I can also confirm that when this issue occurs, the phone's performance takes a nosedive and is barely functional (one could say 50% functional? lulz).
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
The new thing that I found out is that it is only the right hand side of the screen for me.

I normally have my phone in landscape with the power button down and the bottom would freeze. So I assumed that it was always the "bottom" of the screen that froze.

The other night I set it the other way (power button up) and the top froze.

I thought that it was always going to be which ever side was down however it's not. It the right side only for me.
[Nexus 6 Q&A, Help & Troubleshooting] altimax98:
Mine is doing the exact same thing, typically when unlocking the device. When it happens it is so awfully laggy. I just got mine on Monday so back it goes :(
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Right side for me as well. Can you guys give any recommendations on getting a replacement? Got it nearly two months ago on launch day from a T-Mobile store. Don't really want to use a claim on squaretrade for something that came from the factory like this... I should have returned the first week -_-
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Just called T-Mobile. They are sending me a free replacement (free shipping, no exchange fee) that should arrive in 10 days or so. Year long manufacturer warranty FTW!

Perfect!
[Nexus 6 Q&A, Help & Troubleshooting] NastyNeil:
Out of curiosity, is yours 32 or 64GB? They couldn't offer that for me because mine was 64 and they didn't have any to send. I had to go through Moto.
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
32
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Got my new one about 2 hours ago, now the process of setting it up. The date on this box is December 5th so here's hoping for good luck.
[Nexus 6 Q&A, Help & Troubleshooting] asrr62:
this problem happens on the stock rom with nothing altered?
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Yes
[Nexus 6 Q&A, Help & Troubleshooting] PhilDX:
did you guys change your DPI? seems like a lot folks who get the half screen did...
[Nexus 6 Q&A, Help & Troubleshooting] rgraville:
when I see this issue the right half doesn't go black, it just freezes. Usually in Dolphin browser. The phone gets really laggy. I tried a screenshot but the screenshot was of what the screen "should" have been showing. Also touchscreen still worked on the frozen side if I knew where to press to activate things I could not see.

I have changed my DPI

I tried to launch a terminal to run top, but couldn't see it to launch it.
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Nope, everything was stock. Only bootloader unlocked.
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Nope. Bone stock everything
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Crap, I just had the issue on my new (replacement) phone.

Manufactured date is December 5th.

Grrrr

Now what do I do... do I try and get another replacement...
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Probably wise. I for one do not want to risk something happening down the line if the issue gets worse / becomes permanent
[Nexus 6 Q&A, Help & Troubleshooting] TheAnarchist1:
Hey folks. I asked Franco about this over in the kernel thread, thinking it might be something with his kernel, and he provided me with a fantastic response that makes a lot of sense, on the issue. I am just re-posting it below. Do not go over and storm the man's thread, but take it for what it really might be, a software issue, rather than risking getting a bum device through RMA:

"It's a bug that exists even on 100% stock configuration. I'm mostly inclined to a bug on the video subsystem. Google + CodeAurora guys that work with Google butchered the MDSS (video/display) subsystem. I've read the entire commit history since the Google started to bring up Shamu's hardware, there are a couple interesting commit messages about some bugs they had but couldn't fix in time so they put a couple bandaids until the root cause it's fixed. We're not even using the full potential of the display power saving capabilities (called mdss idle power collapse) and there's a 10mA power hit by not having it enabled. There's nothing I can do about it, the video subsystem is a complete cluster**** of hard code. The only guy that claims to know the subsystem is Kondik. I don't even dare to try and fully comprehend it beyond the basic. Sorry dude, you gotta wait for the next OTA."

I just figured this should be shared.
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Well, glad my original theory of it being software (for me) was correct. Though, I feel bad that I am getting a replacement device now... I have other issues though with crackling speakers and such that I guess could warrant a replacement..
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Well that is good to know. I will hold of getting a replacement for a now to see if there is any more conformation.
[Nexus 6 Q&A, Help & Troubleshooting] NastyNeil:
That may very well be true, but since getting a replacement, knock on wood, I haven't had the issue even once. Screen has not froze at all. So maybe it is a software issue, but I'm still thinking it could have been faulty hardware on a batch of devices.
[Nexus 6 Q&A, Help & Troubleshooting] TheAnarchist1:
Alright folks, so update from me, since I dropped that huge post and then disappeared.

I was within my 14 days with T-Mobile, so I did decide in the end to do an exchange, intentionally having them show me their entire stock as to determine manufacture dates. The date of manufacture on the device I had that was doing the screen thing was 12/11/2014.

The device I went with last night from T-Mobile was manufactured on 12/17/2014. Thus far I am running roughly the same configuration, except that I switched this morning from Pure Shamu, back to CM 12, with Lean Kernel this time, and I have not had a freezing issue (yet). I will keep you updated if something pops up.
[Nexus 6 Q&A, Help & Troubleshooting] assdksl:
I have the screen freeze occasionally, I figure it out that it happens a lot more frequently when battery saver is enabled and battery drops below 15%. When I turned off battery saver, it only happened once in two weeks. Also I am sure it is a sw bug because I managed to reproduce it in both orientations, so different parts of the screen were frozen (vertical orientation , and horizontal orientation) .

Someone says that is experiencing crackling noise. I also noticed this only from top speaker, and only in special cases, like when playing game, but when I play music or some other sound, or when having a call on speaker, it sounds perfect, no noise... I guess yet another lollipop sw bug.
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
Thanks for this dude. Does the issue line up exactly with the previous pictures I posted (I'll link to them again if you'd like)?.

Only reason I ask is that I've received two "new" phones from T-Mobile that are absolute garbage.

The screens have a horribly yellow tint and brightness is maybe 2/3 of what my original phone is. I had filed a return claim before your post as others had convinced me it was a HW issue. If it isn't, I'd rather just quit the bs and keep my original phone rather than getting "new" (ie: refurbs) from T-Mobile that were returned probably due to horrible screens in the first place! Lol
[Nexus 6 Q&A, Help & Troubleshooting] bmwh0r3:
I recently started having this issue. I didn't have it while on Verizon. Just recently switched to at&t. On stock firmware, it installs at&t apps. I imagine maybe one of their apps are causing the conflict possibly. I don't know though. I'm no dev. I break my phone more often than not lmao
[Nexus 6 Q&A, Help & Troubleshooting] bmwh0r3:
Is this what everyone is experiencing? Just to make sure...
[Nexus 6 Q&A, Help & Troubleshooting] akellar:
Has nothing to do with carrier
[Nexus 6 Q&A, Help & Troubleshooting] bmwh0r3:
Okay. Well do you have a fix? I decided to test my theory and remove at&t apps I had installed to keep track of my account. I removed all of their stuff and haven't had the glitch since. Maybe I'm one of the few having a carrier app conflict with something. Its an idea. Like I said, I had no issues on vzw. Then again I didn't have any bloat installed of theirs. With switching to a new carrier, I wanted to keep an eye one it all. Remove it all and no issue.
[Nexus 6 Q&A, Help & Troubleshooting] akellar:
Nobody has a fix, if they did it would be posted here. I'm on Verizon and have never been on anything else, it happens here too. There's no way to definitively recreate it or fix it.
[Nexus 6 Q&A, Help & Troubleshooting] USA-RedDragon:
Do you have a custom kernel
[Nexus 6 Q&A, Help & Troubleshooting] akellar:
Some kernels seem to make it occur more than others but it happens in stock too.
[Nexus 6 Q&A, Help & Troubleshooting] USA-RedDragon:
There's been rumors of it having to do with GPU frequency scaling
[Nexus 6 Q&A, Help & Troubleshooting] lifeisfun:
I got good pointers from the ElementalX developer on how to duplicate the problem.

Cold phone and/or long period of inactivity. This will recreate it on my friends phone 95% of the time.

Apparently hardware problem :(

https://productforums.google.com/forum/#!topic/nexus/ezVMM-nTiD4
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
For what it's worth to anyone, I got another replacement from T-Mobile (new in box), it has not occurred in weeks. Same situations, same apps, not happening at all.

With my original launch phone and a refurbished replacement it was happening multiple times a day and I could reproduce it. I can not get it to happen with the new hardware.
[Nexus 6 Q&A, Help & Troubleshooting] jason1332:
This happened to me last night when trying a new kernal and governor. Went over to another kernal/governor and it hasn't happened since. I know there are thoughts this could be h.w. related but I am doubtful of that. Jm2c.
[Nexus 6 Q&A, Help & Troubleshooting] ptesmoke:
two weeks on omni and leankernel and no issue here since. previous including stock I got it constantly, hot or cold.
[Nexus 6 Q&A, Help & Troubleshooting] jason1332:
My update, chroma Rom + Franco kernel r17 and haven't had it happen once since clean flash.
[Nexus 6 Q&A, Help & Troubleshooting] New Rising:
I had it several times with Franco and lean kernel. Been running stock for a day and haven't had the issue yet. I'm gonna use stock a few more days and see how it goes.
[Nexus 6 Q&A, Help & Troubleshooting] lianw:
As per my post back on the first page of this thread, I really do not think this is a software issue.

I was on 100% stock when I was experiencing this issue.

I received my replacement device on Dec 31 and I have not experienced the same problem

at all

with the new one.

In fact, with the new one, I have tried different kernels, switched the DPI several times (for example, to run Hearthstone on the phone) and have watched entire seasons of TV shows (playing videos was what was triggering this the most for me) and zero issues.
[Nexus 6 Q&A, Help & Troubleshooting] ptesmoke:
interesting, i was last on Chroma and Franco and it was so bad i couldnt use the device.

its interesting to say the least, 100% stock also has the issue, but from what ive found theres some messy messy code in regards to mdss, hwcomposer, which hopefully 5.1 fixes
[Nexus 6 Q&A, Help & Troubleshooting] jason1332:
So strange. I have read similar comments on the code. Apparently Steve Kondik is thought to be the only one outside of Google who could clean the code up its so bad. Either way, I'm just thankful that this is a software issue (not a hardware failure as originally seen on some units) and it has not reared it's ugly head for me since wiping and flashing.
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
I also think it is a hardware issue.

Talking to Moto Customer support they seem to indicate that it was and I just got back from picking my phone up after sending it in for repair. The work sheet does say replaced part (it just doesn't say which part).

I will see how it goes with this fix.
[Nexus 6 Q&A, Help & Troubleshooting] lifeisfun:
Please keep us updated!

Thanks
[Nexus 6 Q&A, Help & Troubleshooting] ptesmoke:
I'm sure you won't have an issue, the problem is most support centers have no idea what the root cause is of something like this, chances are they received it, could or couldn't reproduce it, and usually they'd just swap out the main board or daughter board depending where the video stuff lies and call it a day.

I'm still convinced its a hardware glitch...caused by the right combination of software bugs...leading to only certain devices under certain circumstances affected.

also, just left my phone in my truck in -25C for two hours while I played ball hockey. came back and tried my best to induce the problem...and no issues. I'm assuming that squashes the "let your device get cold" idea..

I'm not trying to prove anybody wrong here either, just trying to help figure out wtf the issue is lol. I will be flashing the stock kernel tomorrow to see if that induces it.
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Crap.

My nadroid doesn't resotre :( the data gets to 12% and then just sits there, grrr.

Also on a side note the system auto back up thing is strange. When I walked out of the store today to setup my phone it asked me to restore from a saved backup 7 days ago (exactly the length of time that it has been out for repair) and another 1 from 70 days ago. I skipped as I just assumed that my nadriod would work.

Nadroid didn't so I just restored system and now there is no backups... looks like I will be starting from scratch. uhgg.

oh and it looks like I forgot to copy my titanium back up folder.

I suck.
[Nexus 6 Q&A, Help & Troubleshooting] lifeisfun:
Sorry to hear that :(

Did the IMEI of the device stay the same?

If not it would be safe to say you got new phone or new motherboard.
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Same
[Nexus 6 Q&A, Help & Troubleshooting] htc fan89:
those that RMA their nexus 6, did you re-lock the bootloader? Mine has the same problem, but mine occurs once in a half-moon
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Mine hadn't happened in a while but I thought I might as well do it. I wiped, flashed stock and locked the bootloader just to be safe. No issues.
[Nexus 6 Q&A, Help & Troubleshooting] lifeisfun:
Interesting, makes you wonder what they changed if anything :confused:
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
My guess is nothing. I just had the issue last night. :(

They did take it apart as my wireless charging no longer works either. grrr

On the phone with Rogers (My carrier) as I type hoping to get it a replacement.

It all depends on who you talk to...

First person I called, 1st they didn't even know that there was such a thing as wireless charging (no big deal) but she said my only option was to take it back to the store and be without a phone until it gets sent back (minimum 1 week) I asked if there was any other option and she said basically said no unless I wanted to pay a fee. I said that wasn't going to work and hung up.

Called right back - As soon as I told the guy I had the same issue (I didn't even get to the wireless part) he said ok I am going to send a note to the next level up to get them to waive the fee and send you another phone. It will take 3-5 days for them to get back to me but I can wait with this issue.
[Nexus 6 Q&A, Help & Troubleshooting] DroidOnRoids:
My replacement is coming in the mail tomorrow. Someone on Google+ who works for Motorola said that if the 'issue is intermittent, it's a software issue and it's being worked on.' Regardless, I'm still getting this replaced as I'm not taking a chance nor am I waiting for another version of Android. This sucks man.
[Nexus 6 Q&A, Help & Troubleshooting] jacobmervine:
I had the same issue for months, trying different roms and factory flashing images trying to fix it. Finally I contacted google support and they shipped out a new phone. The new one currently does not have the issue and I am using the same rom and settings on this phone. I did factory re-image and locked back my boot loader on the phone I was sending in. I really do believe it is a hardware issue, it would be random on my phone sometimes all day sometimes not. I could not figure out what made it happen, because it would happen on everything screen no matter the app. If it where a software issue Rom should of made a difference unless it is in the core android 5.0. I tried different Kernels and everything nothing would fix it. Contact where you bought it from and get a replacement!
[Nexus 6 Q&A, Help & Troubleshooting] lifeisfun:
I hope you'll get your replacement!
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Well the black and blue dress has turned around my luck. Yes, I said BLACK and BLUE.

I used Titanium backup to restore some apps from my nadroid (I forgot that it could do that) and I just got an e-mail from my carrier saying that a replacement is on the way.

But what ever they did to "fix" it has made it worse, it now happens everyday. Oh well.
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
As stated in my op. I was able to replicate this every single morning. Set my phone to daydream (digital clock) wake up, right half of screen = owned.

Tried roms. Kernels. Nothing helped.

Got a new device, been almost a month now, hasn't happened once. Whether leaving daydream on overnight, which I do every night, or using the phone normally, seems to be 100% device dependent to me. I've got the same apps, same settings, completely stock. Glad I got a replacement.
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
[MENTION=2266619]EmperorX[/MENTION] I agree that I think it is hardware, what I find strange is this:

I use daydream (digital clock) everyday also and it would only happen once every couple of weeks. But I decided to send it in any ways, I send it in for "repair" and so far 2 nights in a row it happens. So the "fix" is worse than it originally was.

I am glad my replacement is on the way also.
[Nexus 6 Q&A, Help & Troubleshooting] DroidOnRoids:
Has anyone theorized whether this issue could be due to the type of storage it has? Example: the N6 with this half screen issue was built using Hynix memory chips while the replacement I just received is running on Samsung/Sandisk chips. I'm just trying to theorize here as the N6 before both of these was a Samsung/Sandisk and I never had screen glitches.
[Nexus 6 Q&A, Help & Troubleshooting] EmperorX:
I previously had Samsung and Samsung on the phone that did this every day. Haven't checked the new phone but don't think it would be caused by storage. Who knows....
[Nexus 6 Q&A, Help & Troubleshooting] Sleeepy2:
Day 2 with my replacement and no issues so far and for the record this has the Hynix memory.
[Nexus 6 Q&A, Help & Troubleshooting] Gorjira:
After spending over a half an hour on the line with Motorola. I gave up. My girlfriend on the other hand didn't. She ended up calling T-Mobile and ended up getting an exchange in less than 15 minutes. The reps at Motorola were terrible, I know what it's like working customer service I understand that pain but these guys were bad. One guy kept cutting me off while I was talking. He kept asking, “ Where did you hear that half of the screen freezing is a problem? If you didn't hear it from Motorola than it must not be a common problem." That guy I wanted to tear into.

Otherwise, I still VERY much enjoy this device, I just happened to get a bunk one.
[Nexus 6 Q&A, Help & Troubleshooting] ambulance:
I am curious if anyone ended up keeping their Nexus 6 with this issue? I just bought an amazon warehouse one that has this issue. I loaded chroma on the phone and would see it a few times a day. Since I am returning it, I decided to load everything back to stock with the latest shamu images directly from Google. To my surprise, the issue has not happened in more than 24hrs even after trying to make it happen. Did 5.1 from Google somehow fix the issue? Is that even possible?
[Nexus 6 Q&A, Help & Troubleshooting] moopile:
I've kept mine. Problem happened often when I first switched to Chroma. Switched from the Franco kernel he uses to Lean Kernel and rarely got 1/2 screen freezes. Currently running Terminus and have only had it happen once in 3 days.
[Nexus 6 Q&A, Help & Troubleshooting] ambulance:
Interesting. Have you tried flashing all of the current stock images? I have a theory that Google may have updated some on-board components within the latest release. Either that or I haven't waited long enough for a freeze.
[Nexus 6 Q&A, Help & Troubleshooting] akellar:
I had the issue repeat on the newest factory images. I got the device replaced by Motorola and got the issue again on the replacement device. At this point it's not worth the time or effort to deal with another exchange (seriously do not buy this device from Motorola, avoid them at all costs) so I'll just deal with the random times this pops up.
[Nexus 6 Q&A, Help & Troubleshooting] rgraville:
It still occurs on mine on 5.1 but seemingly only when using "auto-rotate" display setting. If I force the display to stay in portrait except for apps that force the display to landscape, then the issue does not appear to happen. With the results people are getting on replacements (best case the issue still exists, worst case there is some other problem on the refurbished phone) I don't see a need to exchange at this time.
[Nexus 6 Q&A, Help & Troubleshooting] ambulance:
I followed the procedure in Method 2 as seen here http://xdaforums.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 . I have STILL not seen it happen again! A replacement is on the way and once it arrives I will flash Chroma back on it to see if anything has changed.
[Nexus 6 Q&A, Help & Troubleshooting] zandander:
So, here is my mini horror story. Ordered a Nexus 6 through VZW wednesday night around midnight. Received the phone today at 11:30. It was DOA. Half the screen is screwed, like the old CRT tvs with static and just constantly boot loops. Good first impression so far!! lol

EDIT: Went by a corporate store today and got a new one. Working just as it should so it's all good now! Loving this phone :D
[Nexus 6 Q&A, Help & Troubleshooting] ambulance:
My phone just took a nose dive. After praising it for being fixed it started shutting itself off randomly. I tried re-flashing all stock images again including the franco kernel. It just dies as if the battery is dead. Off to a great start, Google/ Motorola.