Develop Bugs

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)

ATT NOTE 4 phantom touches and screen dead spots

I have had this happen a few times, especially after texting. The lower part of he screen becomes no responsive. Other times I will open an app and another will open before it and that app is no where near each other.
Just wondering if anyone else has seen this. Probably going to factory reset and try again, and see if these issues come back.
I've had to pull the battery out several times to get the screen to respond.

raiu said:
I have had this happen a few times, especially after texting. The lower part of he screen becomes no responsive. Other times I will open an app and another will open before it and that app is no where near each other.
Just wondering if anyone else has seen this. Probably going to factory reset and try again, and see if these issues come back.
I've had to pull the battery out several times to get the screen to respond.
Click to expand...
Click to collapse
I'd just exchange it asap man. Hopefully you're within your time to do that.

Clienterror said:
I'd just exchange it asap man. Hopefully you're within your time to do that.
Click to expand...
Click to collapse
I'm in refurb land now lol

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.

Pixel 2 fingerprint scanner problems

Has anyone else had problems with the fingerprint scanner on their phone?
I have registered the same finger multiple times and it can not recognize it even after cleaning. It ranges from saying the scanner is dirty, to saying my finger moved to fast, and sometimes ill place it on the scanner perfectly and it won't even detect my finger.
Never had a problem with any other phones fingerprint scanner before this.
Should I RMA?

I'd RMA. I haven't had this issue
Sent from my Pixel 2 XL using Tapatalk

I've had similar issues with my 6p sporadic. But when it happened it would happen for couple of hours. I would erase all fingers and redo and maybe restart. Usually worked.
I'm having a ***** of a time getting my bootloader unlocked. Done it 20 times in my life and this just isn't going

pakman5391 said:
Has anyone else had problems with the fingerprint scanner on their phone?
I have registered the same finger multiple times and it can not recognize it even after cleaning. It ranges from saying the scanner is dirty, to saying my finger moved to fast, and sometimes ill place it on the scanner perfectly and it won't even detect my finger.
Never had a problem with any other phones fingerprint scanner before this.
Should I RMA?
Click to expand...
Click to collapse
I'm having similar issues. Sometimes it works fine, but sometimes I get the too fast message, no acknowledgement, "not recognized" or "cannot process fingerprint." However, cleaning the fingerprint scanner almost always fixes the issue. This is my first fingerprint scanner-equipped phone, so I'm not really sure how well they usually work. I have to clean the sensor every 10 unlocks or so to get it working again. Is this typical or do I just have really oily fingers?
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
dontbeweakvato said:
I've had similar issues with my 6p sporadic. But when it happened it would happen for couple of hours. I would erase all fingers and redo and maybe restart. Usually worked.
I'm having a ***** of a time getting my bootloader unlocked. Done it 20 times in my life and this just isn't going
Click to expand...
Click to collapse
This is off topic, and there are a lot of threads out there about this, but the commands are different than they have been in the past.
1. Make sure you're using the latest version of fastboot
2. fastboot flashing unlock
3. fastboot flashing unlock_critical
Both commands are necessary.

TheSt33v said:
I'm having similar issues. Sometimes it works fine, but sometimes I get the too fast message, no acknowledgement, "not recognized" or "cannot process fingerprint." However, cleaning the fingerprint scanner almost always fixes the issue. This is my first fingerprint scanner-equipped phone, so I'm not really sure how well they usually work. I have to clean the sensor every 10 unlocks or so to get it working again. Is this typical or do I just have really oily fingers?
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
This is off topic, and there are a lot of threads out there about this, but the commands are different than they have been in the past.
1. Make sure you're using the latest version of fastboot
2. fastboot flashing unlock
3. fastboot flashing unlock_critical
Both commands are necessary.
Click to expand...
Click to collapse
Forgot to reboot my PC after assigning the platform-tools after I downloaded. I think I deleted the old ones and downloaded the new ones and they got moved around in the directory. So I guess part was earned part wasn't or something.Lol. I rebooted my PC and BOOM it worked.

TheSt33v said:
This is my first fingerprint scanner-equipped phone, so I'm not really sure how well they usually work. I have to clean the sensor every 10 unlocks or so to get it working again. Is this typical or do I just have really oily fingers?
Click to expand...
Click to collapse
Every 10 unlocks is way too often. You either really do have very oily fingers or something is up with your scanner. Never had that even with my 5X.
For the original poster, something is definitely wrong. I would get a replacement.
Sent from my Pixel 2 XL using Tapatalk

I do have exactly the same problem. I tried again & again but it didn’t recognize my fingerprint. I also tried with another finger but no luck

I talked to Google and they're sent out a replacement because it's obviously not normal. I'd suggest doing the same. My assumption is a bad batch of sensors.
While I love this phone, its sure had it's share of problems.

Glad I'm not the only one. Had it on 8.0 and just upgraded to 8.1 beta in hopes of something, but no different. Makes unlocking annoying, but even more so using LastPass with finger print is near impossible with this issue.

Ok this might be weird I have the same issue and it depends on how I touch the sensor. If I make sure my finger does not touch the sides of the sensor(the circumference) then it works flawlessly. As my fingers are pretty fat there is a high chance that I hit the sides of the sensor. If I position my finger perfectly over the centre of the sensor, then it works fine. I've had a one plus 2 before and I have never faced this sort of a behavior with sensors.

clank19 said:
Ok this might be weird I have the same issue and it depends on how I touch the sensor. If I make sure my finger does not touch the sides of the sensor(the circumference) then it works flawlessly. As my fingers are pretty fat there is a high chance that I hit the sides of the sensor. If I position my finger perfectly over the centre of the sensor, then it works fine. I've had a one plus 2 before and I have never faced this sort of a behavior with sensors.
Click to expand...
Click to collapse
That still sounds like something is wrong. I just put my finger on the sensor with the tip over and past the circumference and it unlocked fine.
Sent from my Pixel 2 XL using Tapatalk

My pixel 2 has lost all semblance of a fingerprint scanner. It quit working and disappeared from the settings. They are sending me a new one but this is unfortunate.

got my new one and the fingerprint scanner is working now. so if you're having this issue get a new one.

I've recently had issues with the fingerprint sensor. I have both my index fingers registered and noticed when the sensor is kinda dirty it will not read my fingerprint at all and forces me to enter my pin. Once I clean the sensor it functions perfectly
Sent from my Pixel 2 XL using Tapatalk

When I first got mine I had this problem. However I think the issue was adhesive from the packaging was stuck to it because I was able to rub some gunk off with some water and micro fiber and now its fine.

I have this issue and happens randomly. It's very annoying though and forces me to unlock manually often enough that I felt I had to contact support. No amount of cleaning seemed to work.
I am currently in the process of troubleshooting it via support. They want me to run it on safe mode and try factory resetting although I'm doubtful either of them will work.

when i did my fingerprint setup, i went slow, and varied the angle of my finger, it seem to help and is almost too sensitive. i also attempted to get a larger area of my finger and not just the tip ;-P try to do another additional setup with the same primary finger. see if that helps.

Pixelimprint could not detect my fingers a few times today . i had to manually enter my passcode on lockscreen, bofa and chase, because it says ive made the maximum amount of attempts. i also have my L & R index fingers registered twice.ive cleaned the sensor and as of now im still having this issue.
Sent from my 2 XL using XDA Labs

Google replaced my phone for this last week and just like the first phone, the fingerprint scanner worked fine for a few days.
Now I can unlock the phone using my fingerprint just about every attempt but when I try to unlock apps (1Password, Chase, Robinhood) it fails 99/100. It's to the point where I'm surprised when it works.
When I called Google the first phone gave me a hard time enrolling my fingerprint after a factory reset. It kept saying that the sensor was dirty. I wiped it down with everything from microfiber to a cotton ball with rubbing alcohol. Nothing really helped until it randomly took. Then I had the same issue with apps.
I'm still not sure if it's a hardware or software problem as I can get into the device consistently right now.

eddiezane said:
Google replaced my phone for this last week and just like the first phone, the fingerprint scanner worked fine for a few days.
Now I can unlock the phone using my fingerprint just about every attempt but when I try to unlock apps (1Password, Chase, Robinhood) it fails 99/100. It's to the point where I'm surprised when it works.
When I called Google the first phone gave me a hard time enrolling my fingerprint after a factory reset. It kept saying that the sensor was dirty. I wiped it down with everything from microfiber to a cotton ball with rubbing alcohol. Nothing really helped until it randomly took. Then I had the same issue with apps.
I'm still not sure if it's a hardware or software problem as I can get into the device consistently right now.
Click to expand...
Click to collapse
That's really strange. You've had a phone with a fingerprint sensor before and no issues?
Sent from my Pixel 2 XL using Tapatalk

1cm thick dead line on touch display

Hi, just noticed that a bit of a upper display's screen touch is dead and won't respond to touch input. It started I think 4 days ago. I don't remember dropping the phone or anything similar like that. Is there a trick to fix it or its simply dead and it won't recover? I know that if that happened on my old nexus 7 2012, cold restarting fixed it, but it's not working with my HTC 10. I can kinda work around it, it's a spot I don't use too often (although I can't check format Cache in TWRP )
So, any meaningful idea? I can't afford to replace the screen for the second time in a year...
There's screenshot of the line, from left to right whole part.

Better screenshot

FluffyDiscord said:
Better screenshot
Click to expand...
Click to collapse
I've got the same problem.
For a while I managed to get away with zapping it w/ igniter from a MAP gas torch. Now it's really dead
Basically, you remove the piezoelectric igniter from any lighter / torch and zap the screen.
Follow this video:
https://www.google.com/url?sa=t&sou...Vaw2vhhgjSKm7U9Oq4sJQuneH&cshid=1566003709050

mcmorariu said:
I've got the same problem.
For a while I managed to get away with zapping it w/ igniter from a MAP gas torch. Now it's really dead
Basically, you remove the piezoelectric igniter from any lighter / torch and zap the screen.
Follow this video:
https://www.google.com/url?sa=t&sou...Vaw2vhhgjSKm7U9Oq4sJQuneH&cshid=1566003709050
Click to expand...
Click to collapse
Looks promising, can you define "for a while* ?

Also it's morning now, just tried the test again and now it's working. I suppose it's a software issue

FluffyDiscord said:
Looks promising, can you define "for a while* ?
Click to expand...
Click to collapse
Sure, did it about 3 times, lasted for a couple months each time, i tried a couple more times afterwards and there is no more improvement.
Its time to replace the LCD for me.

mcmorariu said:
Sure, did it about 3 times, lasted for a couple months each time, i tried a couple more times afterwards and there is no more improvement.
Its time to replace the LCD for me.
Click to expand...
Click to collapse
I think imma give it a try, it's back again. Thanks for your time