Has anybody noticed an intermittently unresponsive touch screen after the latest OTA? I haven't had any problems since they fixed the original problem way back when.
It goes completely unresponsive and I have to reboot several times to get it to work until it stops again. I'm assuming this is a hardware issue on my end since I haven't heard anybody else talking about it but I just wanted to make sure.
I think I will try a different kernel and/or ROM to see what that does.
Hi,
I have the same issue here, it started a few days ago for me. Up till today I just had to reboot but now it seems completely blocked... I will try again later but this is becoming really annoying
.
I had the same happen to me about 2 months ago. Happened around an OTA.
In the process of trying to replace it. Tried flashing recent factor images but no luck
I've had exactly the same issue as described. Hardware buttons work fine, but no response to touch. Started intermittently and got progressively worse until there is no touch response at all.
The first time this happened, I contacted google support, and they arranged a replacement. That was in June.
The replacement device has now developed the same fault, which progressed in the same way as the first device.
Just got off of the phone with Google support, and my second replacement is now on it's way.
Fingers crossed for 3rd time lucky.
Same thing...
This has started to happen to me -_- replacement is on its way. Doesn't seem like the problem is being fixed more or less just addressed...
DG android fanboy said:
This has started to happen to me -_- replacement is on its way. Doesn't seem like the problem is being fixed more or less just addressed...
Click to expand...
Click to collapse
Sadly they don't think the Pixel c is important enough but least the RMA is straight forward.
Sent from my Pixel C using Tapatalk
Hertshammer said:
I've had exactly the same issue as described. Hardware buttons work fine, but no response to touch. Started intermittently and got progressively worse until there is no touch response at all.
The first time this happened, I contacted google support, and they arranged a replacement....
Click to expand...
Click to collapse
Ditto here. Just received "refurbished" (was actually new--factory wrap, unopened) replacement unit two days ago. Had my initial Pixel C about 10 months with zero issues. Then, a couple weeks ago, touch responsive became spotty, typically cured by putting tablet to sleep and waking. Progressively got worse until no touch response whatsoever. Physical buttons worked fine. Factory reset, tried flashing prior OS versions, etc. Nothing worked. Stock / unrooted.
But, Google customer service was very cool about the replacement.
How were everyone able to contact Google Support? I have the same problems with the touch screen, but am not able to find a way to contact Google about it. I had bought mine straight from Google Store.
DukyY said:
How were everyone able to contact Google Support? I have the same problems with the touch screen, but am not able to find a way to contact Google about it. I had bought mine straight from Google Store.
Click to expand...
Click to collapse
Top right hand corner, "contact Google" > https://support.google.com/store/troubleshooter/3070579?hl=en
I had the same problem after an OTA Security update yesterday. Booting into recovery and erasing cache fixed it for some time, then problem reappeared. Can be fixed by repeating the procedure. Seems a software problem to me.
Same problem. I can't even get it unlocked now as nothing registers.
Sent from my ZTE A2017U using XDA-Developers Legacy app
I guess this is just a hardware issue because it happened to me twice and both times Google provided me with a new tablet. The only advice I can give you is to contact the support because in my opinion nothing can be done at our individual level...
Will they still replace out of warranty? Purchased Dec 21, 15. Tablet had been flawless until yesterday.
Sent from my ZTE A2017U using XDA-Developers Legacy app
Hmmm I highly doubt it, but you can give it a try. Did you try to factory reset yet, just in case?
Yes, initiallyit was slightly working as of Wednesday and I factory reset. No change, but it registers no touches now so I can't even unlock it.
Google is getting me a replacement so I thank them greatly for that.
Sent from my ZTE A2017U using XDA-Developers Legacy app
yeah, google did the right thing by shipping a replacement, bill3508. i just hope whatever hit your device is isolated.
2 issues I've come across lately with my Pixel C tablet:
1. Touchscreen unresponsive
The tablet has lost touchscreen responsiveness. When I touch the screen, nothing happens. Buttons pressing ok - it works.
I have connected the device to the PC by Vysor app. Using a mouse from PC I can manage. I tried diagnostics in programming options (I've turned on show touches on touchscreen and localization of the pointer) but no touches detected however mouse moves yes.
Rebooting didn't help - many trials. Safe mode neither.
I haven't done a full recovery to factory settings yet. I am afraid of loosing USB debugging mode. Looking foreward to finding software resolution before warranty replacement.
2. Power button doesn't light up the screen - possibly backlight fault (software?)
After few trials with power button the screen shows up. Sometimes I try reboot but the problem returns. It is randomly, sometimes after one pressing power buton, sometimes lastlky after few trials withe few rebooting.
When I put the tablet on light (a lamp or sunshine throug window) I can see the view of the screen darkly. So there is the view but without brightness.
Android 7.1.2, N2G47D
I have the same problem now.. However I've noticed the following: When the device is in the case which covers the screen and has a magnet, the problem will persist. If removed from the case and left for a day outside, the problem is gone (so far at least). I will return the device for a replacement and hope google can replicate the issue. Anyone else using a case with a magnet?
Yes I have the same problem and also a magnet case. But for me the problem is not gone, after removed from the case and left for a day outside .
Now I get a replacement from google.
Should I now no longer use a case with magnet? Is the case the reason for a broken pixel c?
Related
I have been having an issue with my screen. Randomly the screen will become unresponsive. I will be playing a game or something and the screen will not respond to my presses, even the buttons at the bottom dont work. If I hit the power button to turn off the screen and wait a second it will become responsive again. This happens while the phone is in my hands so I dont think it is the grounding issue. The other strange thing is sometimes like if I am typing a text it will start doing things on its own like typing a bunch of random letters and such. Or if I am on the homescreen it will try and resize widgets and slide to the next screen.
Anybody come across this issue or know what I can do to fix it? I am running Cyanogen right now but it happened on Fresh as well all with the stock kernels.
Thanks
Yes, I have that issue as well... When I first got the phone it was a rare occurrence, but over time it seems to have gotten worse and worse. It always seems to be worse if it's plugged into the charger, too.
I decided to do something about it today, so I just flashed the stock (rooted) Sprint OTA on it, and am planning to take it to the Sprint store to see if they will replace it under warranty if I can demonstrate the problem.
I'm heading there now. When I get back, I'll post what they say about it here.
Just got back from the Sprint store...
The technician spent about 20 minutes looking at my phone, then returned it to me saying "You're right, that's pretty annoying." and said that they would replace it under warranty for free. He ordered one and said I could come get it on Monday. I know I'll get a refurbished phone, but I figure a refurbished phone that works is better than a new phone that doesn't.
It would seem that it's a hardware problem, and you'll probably also have to get yours replaced, too.
ah bummer, thanks for posting that at least now I know. I just need to figure out how I can make the issue occur so I dont waste my time at the sprint store.
Just an update, they replaced the phone and I have not seen this issue since. I've nandroided the fresh rom I was using before back onto the phone, so it is definitely a hardware issue. Just take the phone into a service center and get them to exchange it and you should be good.
Sent from my PC36100 using XDA App
Am I the only one experiencing some random ghost swipes on both Asus and Google keyboard while typing fast on my Zenfone2 4GB? Don't occur consistently, just here and there but annoying overall.
It's almost the same behaviour of my previous OnePlus One, who had the 1+ possibly knows of what I'm talking about.
Didn't have the chance to record a video thou, but I will.
I would RMA. I had the same issue on OPO, absolutely terrible.
rlaw said:
I would RMA. I had the same issue on OPO, absolutely terrible.
Click to expand...
Click to collapse
Yep. I guess you know what I'm talking about.
I ran some multi touch test and everything works flawlessly, so basically I can't reproduce the issue on purpose. But it happens. I hope the RMA process it's not a firewalk as it was with 1+.
taldeital said:
Yep. I guess you know what I'm talking about.
I ran some multi touch test and everything works flawlessly, so basically I can't reproduce the issue on purpose. But it happens. I hope the RMA process it's not a firewalk as it was with 1+.
Click to expand...
Click to collapse
Just a thought... D'you have swipe typing enabled?
Otherwise, it sucks you got hit with the same issue on two completely different devices. Zf2 actually rated as among the best in touch response. If your issue does persist, you probably got a lemon. =/
rlaw said:
Just a thought... D'you have swipe typing enabled?
Otherwise, it sucks you got hit with the same issue on two completely different devices. Zf2 actually rated as among the best in touch response. If your issue does persist, you probably got a lemon. =/
Click to expand...
Click to collapse
Yes, swipes are enabled. I use to type in both ways because some words are easier to get written with swipes especially on one hand use. I'm quite a fast typer, could be my fault, I guess. But didn't have anything like this with my previous android phones (zte blade, nexus s and nexus 4). It isn't that frequent, but it happens and after the 1+ burst I don't feel confident and comfortable anymore.
taldeital said:
Yes, swipes are enabled. I use to type in both ways because some words are easier to get written with swipes especially on one hand use. I'm quite a fast typer, could be my fault, I guess. But didn't have anything like this with my previous android phones (zte blade, nexus s and nexus 4). It isn't that frequent, but it happens and after the 1+ burst I don't feel confident and comfortable anymore.
Click to expand...
Click to collapse
I am noticing this occasionally as well... it seems to happen in the bottom left-ish area of the screen... to this point I have assumed it to be some wild coincidence related to me accidentally touch another part of the screen while holding the phone.
I got hit with this issue on my 1+1 which is why I bought this phone as I couldnt even unlock my screen, what I noticed is once the heatwave over here hit, 1+ started having issues with typing (same as OP) and everytime it was hot it just wouldnt type correctly. I'm not expert at all but Im thinking it has something to do with the hardware and over heating as 1+ forums are filled with ppl with the same issue. I downgraded all the way back to the very first firmware and was still present.
lostbuddy1 said:
I got hit with this issue on my 1+1 which is why I bought this phone as I couldnt even unlock my screen, what I noticed is once the heatwave over here hit, 1+ started having issues with typing (same as OP) and everytime it was hot it just wouldnt type correctly. I'm not expert at all but Im thinking it has something to do with the hardware and over heating as 1+ forums are filled with ppl with the same issue. I downgraded all the way back to the very first firmware and was still present.
Click to expand...
Click to collapse
Well with one plus was slightly different because it suffered of some serious hardware related problems, mostly connected to the bad grounding of the digitizer. There were some "triggers" that lead to an impossible typing, once you got above some thresholds of temperature or usage, the device was done and nothing could revert back.
Using Yet Another Multitouch Tester the 1+ looked totally gone wild especially when testing different touches on the same x-axis. This problem doesn't occur at all on my Zenfone2 in any condition.
Update: wrote to the CC, the guy told me that is something related to the multitouch behavior of the ASUS keyboard. So, I thought that basically it doesn't recognize two different typing so near in time and swipes instead, merging both touches in one gesture. The disappointing thing is that it does the same also when typing on a multi-touch enabled keyboard like the Google one. Still waiting for a reply to my last email where I asked what I could do furthermore to check things out.
does anybody experiencing this right now? for me it's getting heavier and CC won't do nothing about.
I had this issue on my previous phone i.e nexus 4 and after few days my touch stopped working, so it is better to visit service center and get the touch panel replaced
Sent from my intel inside hand pc
So until day before yesterday, My phone had been working fine, no issues at all. Then suddenly I started getting ghost touches. I thought i twas due to the some smudges on screen. Tried cleaning it, but the touches would remain. Turned screen on and off used to make it go for sometime. Rebooted, the issue seemed sorted. Then yesterday, I started to notice that the part where ghost touches were occurring, touch is not working. Rest part works absolutely fine though. Tried the screen touch test in service test in service menu, it showed that much part to be unresponsive. So is there any chance I can recover by testing with some software or replacing digitizer(which comes with screen I think) is the only option? I have attached the a screenshot of the touch test. The black rectangle in center is the one where touch is not working. I have removed the screenguard, so that was not causing the issue.
I'm on stock, rooted and xposed. Also tried reverting back to a clean PRF(rooted and recovery), but same results were obtained. Once or twice I was able to get a single line of touch across, but that's it.
for a week or two my phone also started getting ghost/phantom touches in roughly the same area. I haven't taught much of it until now, your post has made me concerned that my screen too will stop working.
keep the thread updated if there's any new development
karamancho said:
for a week or two my phone also started getting ghost/phantom touches in roughly the same area. I haven't taught much of it until now, your post has made me concerned that my screen too will stop working.
keep the thread updated if there's any new development
Click to expand...
Click to collapse
Tried a few apps, none are able to register touch in the specified region. Will most probably have to replace digitizer. How is Your phone fairing?
Mirhawk said:
Tried a few apps, none are able to register touch in the specified region. Will most probably have to replace digitizer. How is Your phone fairing?
Click to expand...
Click to collapse
still getting phantom touches in the upper part of the screen. It's not so bad that it wold be considered a problem, only a mild annoyance for now
What did you do to solve it?
I have the same phantom touch issue now, in the exactly same area
patoberli said:
What did you do to solve it?
I have the same phantom touch issue now, in the exactly same area
Click to expand...
Click to collapse
I wasn't able to solve the problem, and I'm using as it is for now as I can't spend much on the phone. One user had said that even replacing the digitizer might not work, not sure why though. Were You also rooted and/or exposed?
patoberli said:
What did you do to solve it?
I have the same phantom touch issue now, in the exactly same area
Click to expand...
Click to collapse
welcome to the club
my situation is the same as with @Mirhawk. I'm using the phone as it is until I can put aside enough money to buy some other phone.
bonus thread
Nope, neither rooted nor xposed.
I sadly can't anymore really use the phone, it started from one day to the other. Luckily I already ordered a new phone a week ago, it just needs to be delivered....
Sorry if there has been a thread I am at work but the last few times when ever my screen goes to being locked it will flash white then go the lock screen. Is this a known issue just got the phone Wednesday. Thanks
Never happened... Can you record a video or something
Sent from my Google Pixel 2 XL using XDA Labs
KevTN said:
Sorry if there has been a thread I am at work but the last few times when ever my screen goes to being locked it will flash white then go the lock screen. Is this a known issue just got the phone Wednesday. Thanks
Click to expand...
Click to collapse
It is a known issue they'll rma it for this reason. On a side note I had that issue for about 12-24 hours and went away on it's own, no restart or factory reset was required for me. Really wish I knew what or why the cause but maybe it will go away, like mine did. :fingers-crossed:
Thanks I hope so too. Really liking the phone but for this money...
agreed I almost gave up, my first 2 were too blue and the 3rd fine except started that flash, but ultimately went away. Loving this phone!
KevTN said:
Sorry if there has been a thread I am at work but the last few times when ever my screen goes to being locked it will flash white then go the lock screen. Is this a known issue just got the phone Wednesday. Thanks
Click to expand...
Click to collapse
Happened with my girls phone..was gonna rma it but decided to flash 8.1 beta 2 and it has fixed it..so looks like Google fixed it in a software update..beta 2 is running well so I would enroll in the beta program and update... should fix that issue right up
Well it got worse so called good rma’d It. So we will see. Glad to see it just wasn’t me...thanks for your input..
KevTN said:
Well it got worse so called good rma’d It. So we will see. Glad to see it just wasn’t me...thanks for your input..
Click to expand...
Click to collapse
Mine just started this week flashing. Running 8.1 since last week. Does your new replacement suffer from the same issue as well?
Thanks
mrcndr82 said:
Mine just started this week flashing. Running 8.1 since last week. Does your new replacement suffer from the same issue as well?
Thanks
Click to expand...
Click to collapse
Mine started today but it has been getting better as the day goes on. I'm curious if its an issue with charging. Prior to a few days ago I had been only using the chargers with that I've received specifically for the phone, but this week--since I'm traveling for the holidays--I've only been using my pixelbook charger, so maybe something isn't properly shielded and the flash is caused by a built up charge? Reason I think that is that it has been less and less noticeable as the day goes on..
sovanyio said:
Mine started today but it has been getting better as the day goes on. I'm curious if its an issue with charging. Prior to a few days ago I had been only using the chargers with that I've received specifically for the phone, but this week--since I'm traveling for the holidays--I've only been using my pixelbook charger, so maybe something isn't properly shielded and the flash is caused by a built up charge? Reason I think that is that it has been less and less noticeable as the day goes on..
Click to expand...
Click to collapse
My flashing went away the next day. I did do a factory reset just because I only had it a few days and no issues since. Although Google RMA’d my phone I sent the replacement back without accepting shipment as mine has been running like a champ since.
KevTN said:
My flashing went away the next day. I did do a factory reset just because I only had it a few days and no issues since. Although Google RMA’d my phone I sent the replacement back without accepting shipment as mine has been running like a champ since.
Click to expand...
Click to collapse
Got my replacement a week ago, 0 flashes so far (finger crossed). I tend now to think it's a hardware issue. Also blue tint is slightly better on new device...
I just got my Pixel 2 XL delivered to me yesterday. Set it all up, didn't get the flashing screen issue at first but now it's doing it. Tried to chat with Pixel support from my phone, they don't have a resolution for it yet.... Hopefully it's a software issue?
Mine started doing this about 3-4 days ago. I noticed that it starts to do it when night mode is on. If I go the RMA route, this will be my 3rd replacement and tbh I'm not looking forward to doing this.
Mine did it once with always on display on, I don't usually use that so I turned it off and it hasn't happened since.
I just received a replacement device yesterday due to a faulty speaker. No issues with the last device, but this device is now exhibiting the screen flash when locking.
mferrara91 said:
I just received a replacement device yesterday due to a faulty speaker. No issues with the last device, but this device is now exhibiting the screen flash when locking.
Click to expand...
Click to collapse
Exact thing with me. I received a brand new device that I got because my previous one had a bad speaker (speaker phone distorted sound). This new one has the screen flashing problem. My original did not. Poor QC ... especially for $850.
Mine has been doing it for a couple of days, and it kept getting worse. On chat with Google Support now. Sounds like it's going to be RMA'd.
I have enabled jump to camera with double power button click. Ever since the may update the camera launches randomly when I try and shut my phone off.
Anyone else seeing this? Fix?
I've been noticing the same behavior. Happens intermittently with no real reason. No noticeable physical difference with the power button either. Still clicks just fine. Definitely seems like a software bug of sorts.
Itachisasuke said:
I've been noticing the same behavior. Happens intermittently with no real reason. No noticeable physical difference with the power button either. Still clicks just fine. Definitely seems like a software bug of sorts.
Click to expand...
Click to collapse
Google RMAed my phone for it (new one comes tomorrow) so I'll let you know if it persists across a hardware swap.
madscribblerz said:
Google RMAed my phone for it (new one comes tomorrow) so I'll let you know if it persists across a hardware swap.
Click to expand...
Click to collapse
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Itachisasuke said:
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Click to expand...
Click to collapse
So far no issues on new hardware, but was intermittent and unpredictable so not entirely certain issue has resolved. Given multiple reports its unlikely hardware.
I did do something slightly differently on this phone though. On my old I went from OPM2 to OPM4 with the June release. This time I stayed with OPM2. Only manually wrote June update, rest was OTA.
Will provide updates as time passes or if I see it again.
Itachisasuke said:
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Click to expand...
Click to collapse
Promised update - since switching to the rma unit I've not seen this issue in any form. It could have been moving over to a clean userdata but otherwise the software and firmware were identical between my old and new phone.
Edit (1 Aug 2018): After one day of the factory reset, the problem started happening again but a lot less frequently than it was before the factory reset. After two days, the problem is back just as bad as it was before I did the reset. I'm certain this is a software problem because of this but it makes no sense to me.
----------------------
I had the same problem with my Pixel 2 XL and had an experience I wanted to share.
I did a factory reset on my phone and restored all of my apps and data from backup except for my device settings. The problem remained for just a few minutes after my phone booted after factory resetting it, but after that, I've never had the problem since.
I'm not too sure if this is a permanent fix yet, but it seems a factory reset solved the issue for me. Fingers crossed it lasts.
exactly the same issue. But i think this is definitely a hardware problem, due to a design defect or quality control. so replace with new machine would not fix this entirely.
hope this could be fixed on pixel 3
The same issue have been happening with my phone , was hoping someone had a solution. It had never been an issue until recently
I had this issue, Google just did an RMA without much question. Just had to check in Safe Mode. I suspect a slight quality issue with the button mechanism registering double clicks despite it only feeling like one click.
pemz82 said:
I had this issue, Google just did an RMA without much question. Just had to check in Safe Mode. I suspect a slight quality issue with the button mechanism registering double clicks despite it only feeling like one click.
Click to expand...
Click to collapse
Started a chat today with them, I got it through the Google Store and they are going to RMA my device as well. This is my second Google phone that had issues after a year. As much as I like the google phone . I can't say I trust it's QC . Nexus 6p was a useless brick after the power issue and bootloop and now this with the Pixel 2
I've also just started having this problem. I'm going to try a full wipe when Android 10 gets released on the 3rd. If that doesn't work, guess I'll be RMAing my 3rd phone.