Develop Bugs

[Q] Dead spot at top of screen

Right around the "Clear" for notifications, panning left to right, I cannot touch.
For about a month and a week or so, my touch screen has been acting really weird, and hasn't been responding to touches, locking up, phantom clicking, and spazzing out. More recently, about the last 2 weeks its gotten really bad and makes the phone unusable for a bit. Usually the issue clears if I turn off the screen but a couple days ago two areas came up where I couldn't touch at all. One of them went away but the other is about 1/4" inch tall, going from left to right across the screen about 1/3" down that I can no touch (like to clear notifications).
I've tried flashing new ROMs, rebooting, nand back ups, battery pulls, etc. It's a hardware issue I'm guessing related to the screen separation issue. My screen separation isn't very much, but when I touch the bottom left edge of the glass, I get phantom clicks around the lower middle part of my screen, and that some times locks up the screen.
I know that it's related to hardware, but I was wondering if anyone else has this issue, or knows some type of solution besides returning it or repairing the screen? Or if you know a good way to approach getting a new phone, that'd be welcome.

Why can't you return it under warranty? Clearly that sounds like a hardware issue thats easy to reproduce at the store.

surrealmethod said:
Why can't you return it under warranty? Clearly that sounds like a hardware issue thats easy to reproduce at the store.
Click to expand...
Click to collapse
Oh yeah, very easy to reproduce, but my dad when he got our phones didn't feel the need to get any type of warranty or anything...

mistersquirrle said:
Oh yeah, very easy to reproduce, but my dad when he got our phones didn't feel the need to get any type of warranty or anything...
Click to expand...
Click to collapse
Your phone comes with a 1 year hardware warranty. Take it in and show them the problem.

Does it now? I didn't know that, thanks. I can just take it into a Sprint store and ask them about it right? I don't need to involve HTC?

Did you ever resolve this? Mine just started doing the exact same thing.

christovski said:
Did you ever resolve this? Mine just started doing the exact same thing.
Click to expand...
Click to collapse
Hate to bump an old thread, but I'm having the same problem, although I've only noticed it after rooting. Could it be a problem with the ROMs?

Accelerometer completely dead?

This poor phone has been through hell since I got it as a warranty replacement a few weeks ago.
Lost it in a snow bank, got pushed around by a snow plow.. was found, everything worked just a scratch on the screen.. Two weeks ago I dropped it and put a small crack in the screen then a couple days later it fell out of my pocked and completely shattered the display. New screen on the way. Now I see the accelerometer isn't working at all. See attached pic. It registers nothing at all.
I have rebooted, reinstalled my rom (liquidsmooth beta3 which is great btw).. I haven't yet done a full wipe / reload and if at all possible I'd like to avoid it.
I have no idea where to go from here. I don't see sensorservice running, not sure if that's a problem.
Anything I can look at, reconfig, remove that might help kick it back into working?

gsxr1kmatt said:
This poor phone has been through hell since I got it as a warranty replacement a few weeks ago.
Lost it in a snow bank, got pushed around by a snow plow.. was found, everything worked just a scratch on the screen.. Two weeks ago I dropped it and put a small crack in the screen then a couple days later it fell out of my pocked and completely shattered the display. New screen on the way. Now I see the accelerometer isn't working at all. See attached pic. It registers nothing at all.
I have rebooted, reinstalled my rom (liquidsmooth beta3 which is great btw).. I haven't yet done a full wipe / reload and if at all possible I'd like to avoid it.
I have no idea where to go from here. I don't see sensorservice running, not sure if that's a problem.
Anything I can look at, reconfig, remove that might help kick it back into working?
Click to expand...
Click to collapse
Damn man. Hold on to that damn thing or get an Otterbox or just opt for a gophone lol. No but seriously you need to buy a bulky case.
First thing that comes to mind is the auto-rotation function.. Is it turned on?

You need to learn how to take care of your things. That's just insane. I agree with WiredPirate!

Yea I've checked the rotation settings.. chrome, maps, and the accelerometer apps all are unresponsive to rotation / tilt.
I'm going to clean wipe / reformat today.
And I've never used a case / whatever on my phones and I've never had a problem. Amazingly right away when I get this one it just started being suicidal.

gsxr1kmatt said:
And I've never used a case / whatever on my phones and I've never had a problem. Amazingly right away when I get this one it just started being suicidal.
Click to expand...
Click to collapse
Or u could just blame it on the phone, haha
Otter box is nice.. I got the one with the clip. Whatever its called.. And works with the extended battery
Sent from my Galaxy Nexus using Tapatalk 2

LiquidXed said:
Or u could just blame it on the phone, haha
Otter box is nice.. I got the one with the clip. Whatever its called.. And works with the extended battery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm not serious. Actually looking for information to troubleshoot the accelerometer. not because I don't want to reinstall, but because I don't think that is the only way to fix (if it isn't actually physically broken)

No response on bringing arm up

The screen does not wake on raising my arm or even with multiple gestures. The steps counter works fine however. Tried resetting a few times with no luck. Anything I can do?

swapnil said:
The screen does not wake on raising my arm or even with multiple gestures. The steps counter works fine however. Tried resetting a few times with no luck. Anything I can do?
Click to expand...
Click to collapse
I had the same problem with my 360! I had the watch loose on my wrist! I adjusted my watch to be a bit tighter and it seems to be working OK now!

Ldgv408 said:
I had the same problem with my 360! I had the watch loose on my wrist! I adjusted my watch to be a bit tighter and it seems to be working OK now!
Click to expand...
Click to collapse
Thanks but doesn't seem to do the trick.

I'm with the OP on this one. Sometimes, the screen turns on and sometimes it doesn't. I've tried flicking my wrist and that doesn't work either. Then when I start trying to make the problem happen, the screen comes on every time I bring my arm up.
I just wonder what is the precise action the watch is looking for to make the determination that you are looking at the watch (e.g., to tell time).
If anyone knows, I'd like to know so I can do precisely that.
Dennis
ps. Sometimes I miss my real watch because it always had the time. But I'm coming to the conclusion that we should stop calling these things, and comparing them to, "watches". They are really smart phone remotes.

It would be real nice to have a better understanding of the "secret handshake" to get the screen to turn on. If there is an irritation with the 360, this is seemingly my only one.
I would venture a guess, that those who root will probably wind up with a cool little gyroscope/debug feature that could probably begin to answer this question...

The trick is height, you can't just flick your wrist or turn it, you just have to raise it upwards too, I agree kinda sucks

Tried everything. Looks like a dud accelerometer so I just returned it. Going to wait for the Canadian release.

swapnil said:
Tried everything. Looks like a dud accelerometer so I just returned it. Going to wait for the Canadian release.
Click to expand...
Click to collapse
Yeah, that sounds defective. Did you have the latest update, the one released a few days ago? With it, I can raise my arm just slightly and flick my wrist and it turns on. The update made it more intuitive. Plus, make sure you are running stock clock faces. Some of the third party app clock faces stutter a bit and don't come on/off so smoothly.

I believe the trick is to tilt the watch towards you... as in lifting the top of the watch so that its at a 45 degree angle. I don't think speed or height have anything to do with it.

swapnil said:
Tried everything. Looks like a dud accelerometer so I just returned it. Going to wait for the Canadian release.
Click to expand...
Click to collapse
Hopefully you didn't return it before applying the newest Moto update that was released just a few days ago...it fixes that exact issue (and a few other issues). =0

siciliano777 said:
Hopefully you didn't return it before applying the newest Moto update that was released just a few days ago...it fixes that exact issue (and a few other issues). =0
Click to expand...
Click to collapse
Haha unfortuantely I did. Its okay though, I was always worried about having a US device in Canada. There would always be a warranty hassle. I'll get it when they finally do release it here. Thanks

swapnil said:
Haha unfortuantely I did. Its okay though, I was always worried about having a US device in Canada. There would always be a warranty hassle. I'll get it when they finally do release it here. Thanks
Click to expand...
Click to collapse
I have one of these dud accelerometers too. Nothing aside from a screen tap or button press wakes it. So annoying, going to get an exchange.

man i got depressed once i found this thread.
my watch has been working fine for a couple of days and now it doesnt work when i bring up my arm. it was perfect i loved every minute of it i couldn't complain. and now i have to tape the screen twice or click on the knob to get it to tell me the time. it still lights up and vibrates when i get notifications but whats the point.
hope someone resolves this issue real soon

Issue
Slorks said:
man i got depressed once i found this thread.
my watch has been working fine for a couple of days and now it doesnt work when i bring up my arm. it was perfect i loved every minute of it i couldn't complain. and now i have to tape the screen twice or click on the knob to get it to tell me the time. it still lights up and vibrates when i get notifications but whats the point.
hope someone resolves this issue real soon
Click to expand...
Click to collapse
Just sent mine in and waiting for the replacement. I don't think it's a software issue as it's not more widespread.

fix
I had the same problem and was pretty despondent. Then I found a tilt to wake setting in the android wear app off on my phone, switched on and fixed!

Screen Issues: Right side of screen lags

After using my Pixel daily for 6 months (got the first batch, pre December 25th) and having next to no issues with it (wifi strength sucks, even with Xceed kernel, but it's better than it was), half of my screen decided it wanted to go goofy. I was using it two days ago and everything was working fine, I used it yesterday morning for a few minutes and then plugged it into the Google charger that came with it and let it sit on my couch for a few hours while it was charging. I got on the bus, and pressed the power button to wake the screen and nothing happened. Thinking I had it turned off I held the power button for a few second, and still nothing. So I held it for 30 seconds and when it brought up the bootloader warning the right side of the screen was glitching, same thing happened on the Google logo, boot animation, and continued into Android. I powered it off, hoping it would go away but it didn't. The slight glitch then turned into static "snow" which will then change sporadically based on what I'm doing on the tablet. That area of the screen still works perfectly because touch input works, and when I take a screenshot and view that area of the screen it shows up just as it should. It seems like there is an overlay on the right side of the screen that won't go away. Since it happens from the moment you turn it on makes me think it's a hardware issue but the fact that the screen itself still works perfectly makes me think it's a software issue. I haven't flashed the stock ROM back on it yet or locked it backup yet since I don't have a type c to type a adapter with me, it's still under warranty but I wanted to see if you guys could help me fix it before I sent it back.
TL; DR

This just started happening to me today, exactly as you described.

Interesting. I just RMA'd mine, should be receiving it within the next few days.

I'm returning mine too. I've determined that it's hardware because when I applied pressure around the edges of the screen I felt something slightly pop into place and then the problem was temporarily corrected. If I apply slight pressure to parts of the screen it happens again.
At this point I've flashed back to stock and I'm in an eternal recovery bootloop that I can't fix because acquiring USB drivers that work is incomprehensively difficult.

Just had mine go as well :crying:

Oh wow, that sucks. At least I'm not the only one though. I just got my new one a few days ago and all is well so far, hopefully this one won't screw up. RMA process was very smooth.
As for the USB drivers I usually have to install them manually by using the "select driver from a list"
Sent from my Pixel C using Tapatalk

Same issue on my first one
Here's my post from the mapping problems to serial # thread.
Google RMA process was fine once I was finally able to get a chat window with them.
Be sure to post to the problem mapping thread to help others!!

Add me to the list. Just went through the RMA process and am now waiting for the replacement to come. I can deal with the wifi issue and the random reboots, but having half of your screen corrupted is unacceptable. I don't even know how this is possible unless some genius at the pixel C team decided that it's cheaper to source half a screen and glue them together.

It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.

brando56894 said:
It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.
Click to expand...
Click to collapse
Most likely some latently defective silicon from Nvidia.
Sent from my Pixel C using Tapatalk

pkelly517 said:
Most likely some latently defective silicon from Nvidia.
Click to expand...
Click to collapse
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.

brando56894 said:
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.
Click to expand...
Click to collapse
Of course screenshots would come out perfectly. It's just a memory dump of the video RAM. This is a problem with getting that memory to the display. I think the display driver is part of the SoC. I could be wrong. Maybe it's a cable.
But it seems like a bit in the display driver is never getting enabled.
Sent from my Nexus 5X using Tapatalk

I'm fairly certain that it's a physical issue with the screen or the connection to the screen. When I had this issue I saw a visible change when I applied some light pressure around the edges of the screen. At one point it almost felt like something popped into place and the problem went away (then resumed.) Also, if I applied some pressure on the lagging side of the screen I would see some odd behavior as if the connection was fluctuating. I didn't squeeze hard, but it didn't take much.

I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?

Wow really? That's no good!

Pixel C Screen Issues
Add me to the list, as of this morning. 8 months old.

SpaceGooner said:
I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?
Click to expand...
Click to collapse
what's the serial# of your replacement?

lude219 said:
what's the serial# of your replacement?
Click to expand...
Click to collapse
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.

SpaceGooner said:
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.
Click to expand...
Click to collapse
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.

lude219 said:
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.
Click to expand...
Click to collapse
Thanks for the info. Not sure I'll be able to determine what s/n Google sends me next time, but here's hoping I get a good one and that I've just been unlucky so far. I won't be able to RMA until I get home from vacation later in the week anyway. If they send me another Pixel C that develops the half screen problem down the line, I will surely have to get a refund and maybe go for a top end Chromebook (with Google Play of course) next time.

Fingure Print Sensor Not Working As Good? Anyone?

What's up guys? Has anyone else noticed that the fingure print Sensor barley works. For me, it usually takes all 4 attemps and I have to end up putting my code in. Once upgraded to Pie I factory reset and started from scratch. Seemed to be happening for a while now, maybe since about 4 months ago? IDK, I know of no fixes. Anyone else experience the same thing?

Quadrider10 said:
What's up guys? Has anyone else noticed that the fingure print Sensor barley works. For me, it usually takes all 4 attemps and I have to end up putting my code in. Once upgraded to Pie I factory reset and started from scratch. Seemed to be happening for a while now, maybe since about 4 months ago? IDK, I know of no fixes. Anyone else experience the same thing?
Click to expand...
Click to collapse
First time every time

siggey said:
First time every time
Click to expand...
Click to collapse
I just cleaned it with alcohol and re did my fingure prints, we'll see how long this lasts lol

Mine's similar to yours OP. I can't say it's ever worked first time. Ever. I'm a super clean freak so I know I'm not covered in oils etc haha. Maybe we're just the unlucky ones
Sent from my Pixel 2 XL using Tapatalk

siggey said:
First time every time
Click to expand...
Click to collapse
Pikakun said:
Mine's similar to yours OP. I can't say it's ever worked first time. Ever. I'm a super clean freak so I know I'm not covered in oils etc haha. Maybe we're just the unlucky ones
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Mine use to work perfectly, every time, then they did an update where it didn't turn the screen on instantly anymore, maybe 1 or 2 months after that, it just started to reject my print 9 out of 10 times.

Quadrider10 said:
Mine use to work perfectly, every time, then they did an update where it didn't turn the screen on instantly anymore, maybe 1 or 2 months after that, it just started to reject my print 9 out of 10 times.
Click to expand...
Click to collapse
I am having a similar issue.
Not quite as bad as 9 out of 10 rejections, but its definitely about 3 or 4 tries before it works. Used to be flawless.
The sensor is not dirty either, and fingerprints are not that old. Going to try redoing them now though see if that helps.

Mine is much slower than when I first got the phone, it is sad really that updates have ruined the sensor. This is the first year that I am not pre-ordering a new google phone. I am intrigued by the Pixel 3 (not XL), it would be kinda nice to go back to a smaller sized phone.

Cleaning with alcohol and deleting/re-adding my prints seemed to fix the issue. Will report more later down the road.

Quadrider10 said:
Cleaning with alcohol and deleting/re-adding my prints seemed to fix the issue. Will report more later down the road.
Click to expand...
Click to collapse
I was researching a fix for this, today.
The number one suggestion was cleaning the sensor.
For me it is sporadic failure of one or two tries and then I purposefully position my finger as perfectly at possible and it will usually recognize by the third try.
Although, today, after reading search results, I picked the screen with the power button and was able to unlock with fingerprint ten times while trying to place my finger awkwardly or not perfect.
Go figure...
I still haven't gotten around to breaking out the alcohol.

This problem started for me with the Pie upgrade. Others have posted about it also. Re-registering a print or cleaning does not help and is not the issue even though often the message given for not working is a dirty sensor. I have just gotten used to it. Works more than 1/2 the time and the others I just go old fashioned and enter my code.

I just went into ABOUT PHONE and sent feedback for unreliable fingerprint sensor, since pie update and requested an update to fix.

The alcohol seemed to help a bit. Most of the time my fingure is registered. Still not nearly as good as it was when I got the phone.