I have serious problems with my Pixel C's touchsreen like Ars Technica:
Our only complaint about the display is that the touchscreen on our device just doesn't work. Taps frequently go unnoticed, which makes navigation and typing on the touch screen very error prone. Scrolling is unreliable, too—swipes meant for scrolling were often interpreted as taps, which led to us accidentally opening things when we wanted to scroll past them. The high error rate makes using the touchscreen an exercise in frustration. If we were given more time with the device, we'd try out a second unit to see if this issue exists in a different model, but with the quick turnaround from receiving a device to embargo, all we can do is list the issues our unit had.http://arstechnica.com/gadgets/2015...res-an-android-tablets-core-problem-software/
I made two recordings to show them, see good case vs bad case on Youtube. Actually the problems vanish on every second reboot. It is pretty predictable unfortunately, so I return my Pixel C tomorrow and buy a second one.
For me my problem don't look like this http://forum.xda-developers.com/pixel-c/help/pixel-c-touchscreen-issue-video-t3268729 but wanted to reference it for people googling about this kind of problem.
vollekannehoschi said:
I have serious problems with my Pixel C's touchsreen like Ars Technica:
Our only complaint about the display is that the touchscreen on our device just doesn't work. Taps frequently go unnoticed, which makes navigation and typing on the touch screen very error prone. Scrolling is unreliable, too—swipes meant for scrolling were often interpreted as taps, which led to us accidentally opening things when we wanted to scroll past them. The high error rate makes using the touchscreen an exercise in frustration. If we were given more time with the device, we'd try out a second unit to see if this issue exists in a different model, but with the quick turnaround from receiving a device to embargo, all we can do is list the issues our unit had.http://arstechnica.com/gadgets/2015...res-an-android-tablets-core-problem-software/
I made two recordings to show them, see good case vs bad case on Youtube. Actually the problems vanish on every second reboot. It is pretty predictable unfortunately, so I return my Pixel C tomorrow and buy a second one.
For me my problem don't look like this http://forum.xda-developers.com/pixel-c/help/pixel-c-touchscreen-issue-video-t3268729 but wanted to reference it for people googling about this kind of problem.
Click to expand...
Click to collapse
I fear my unit may have the same issue.
You say you bought a second one; did google not just exchange it?
They don't exchange units, at least in Germany. You have to buy a new one by yourself
Your "bad" case looks exactly like what I typically see. Sometimes it's worse; for example in Instragram, flicking sometimes results in scrolling the wrong direction.
I just called Google support to see if it's a known issue, and they said no, so I can imagine it might take multiple exchanges to get one that works.
Pixel C Touchscreen Problem
I am seeing a similar issue. Very sporadic and seem to last through reboots. It renders the touchscreen useless but the tablet operates fine as long as I just use the keyboard. It happens at least once per day. I have tried a factory reset and the issue still came back. Eventually a reboot does fix it but I have not seen any pattern to it, this morning it was a hard reset (holding the power until it rebooted) other times it was 2-3 reboots.
In my video, using the "MultiTouch Tester" app shows the inconsistent readings. XDA is preventing me from posting a link to my video because I am a new user the video ID on youtube is XplgTK3ahL0
I did contact Google and they are sending a replacement, I was hopeful that this was an isolated case.
I haven't had any issues with my touchscreen. I don't have the keyboard though
Same issue but reseting from scratch repair the problem. For how long?
Envoyé de mon ONE A2003 en utilisant Tapatalk
I have just been onto google support and had the problem while using the tablet.
When I booted into safe mode, all seemed to be well.
I have transferred accounts with the google setup and it transferred all my apps too, so I will now factory reset and setup again.
Toninho64 said:
Same issue but reseting from scratch repair the problem. For how long?
Envoyé de mon ONE A2003 en utilisant Tapatalk
Click to expand...
Click to collapse
The problem recurred within 24 hours after a factory reset. I have done a factory reset twice now. It happens at least once per day if not twice. Currently, a hard reset (holding down the power button until it reboots) has fixed it the last 2 times.
FLJ74 said:
The problem recurred within 24 hours after a factory reset. I have done a factory reset twice now. It happens at least once per day if not twice. Currently, a hard reset (holding down the power button until it reboots) has fixed it the last 2 times.
Click to expand...
Click to collapse
Thanks for that.
I insisted google did not close the case until I have tried for a few days withou any recurrence.
Will see.
vollekannehoschi said:
I have serious problems with my Pixel C's touchsreen like Ars Technica:
Our only complaint about the display is that the touchscreen on our device just doesn't work. Taps frequently go unnoticed, which makes navigation and typing on the touch screen very error prone. Scrolling is unreliable, too—swipes meant for scrolling were often interpreted as taps, which led to us accidentally opening things when we wanted to scroll past them. The high error rate makes using the touchscreen an exercise in frustration. If we were given more time with the device, we'd try out a second unit to see if this issue exists in a different model, but with the quick turnaround from receiving a device to embargo, all we can do is list the issues our unit had.http://arstechnica.com/gadgets/2015...res-an-android-tablets-core-problem-software/
I made two recordings to show them, see good case vs bad case on Youtube. Actually the problems vanish on every second reboot. It is pretty predictable unfortunately, so I return my Pixel C tomorrow and buy a second one.
For me my problem don't look like this http://forum.xda-developers.com/pixel-c/help/pixel-c-touchscreen-issue-video-t3268729 but wanted to reference it for people googling about this kind of problem.
Click to expand...
Click to collapse
Looking at your video it almost seems as you're having issues only when your using your index finger.
Maybe your finger doesn't have enough contact on the screen. When you used your thumb the screen became "responsive"
Just my two cents. I have yet to see a video that shows hard evidence. They all show something similar where someone seems to be making contact with the screen but maybe they aren't.
Sent from my Pixel C using Tapatalk
FLJ74 said:
I did contact Google and they are sending a replacement, I was hopeful that this was an isolated case.
Click to expand...
Click to collapse
So you got already the second tablet and it still has the same problems? Or I missunderstood something?
vollekannehoschi said:
So you got already the second tablet and it still has the same problems? Or I missunderstood something?
Click to expand...
Click to collapse
Google issued a replacement order, but it has not shipped yet. I am still on the first tablet and still having the issue. (twice yesterday and once this morning already). I have a co-worker that also has one but has not seen this issue at all, he has not had to reboot his tablet since he turned it on last week.
superchilpil said:
Looking at your video it almost seems as you're having issues only when your using your index finger.
Maybe your finger doesn't have enough contact on the screen. When you used your thumb the screen became "responsive"
Just my two cents. I have yet to see a video that shows hard evidence. They all show something similar where someone seems to be making contact with the screen but maybe they aren't.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I hit more than I touch with my thumb. Beating the space key for over 15 years now leads through this I think I get your point about the evidence problem in videos, do you have a better idea to demonstrate such issues?
Google somehow made a mistake and sent me two tablets and two keyboards. The first one had this same issue. When I enabled the "show touches" option, it looked like swipes were generally being broken up into separate quick touches instead of a continuous swipe. Generally made the tablet very frustrating to use. I'm attempting to return it. The touch response on the other one is great, and the difference is night-and-day.
A hard reset does not fix this problem for me. The touchscreen isn't working correctly immediately after the reset.
vollekannehoschi said:
I hit more than I touch with my thumb. Beating the space key for over 15 years now leads through this I think I get your point about the evidence problem in videos, do you have a better idea to demonstrate such issues?
Click to expand...
Click to collapse
Use a touch tester app
like the multitouch test app in the play store
My touchscreen seems a little unresponsive at times, I play Vainglory a lot and occasionally it's not picking up quick screen presses and It's got my killed a few times, I'm now noticing this in general use as well.
It's kind of annoying, I hope this is a software issue.
I am 24 hours on my replacement tablet with no issue....fingers crossed.
FLJ74 said:
I am 24 hours on my replacement tablet with no issue....fingers crossed.
Click to expand...
Click to collapse
you have let a new pixel ? you use the guarantee ? what delay ? how works the guarantee
thanks a lot
Related
[Update March 5th 2014]
Probably all 2014 Note 10.1's sold these past few months are suffering from one or more multitouch issues. From what we now know these appear to be software issues, effecting all current firmware versions for this device.
There are 2 known manifestations of this bug (or more likely: these bugs), described below. In both cases it seems to be a software issue because normally the 2014 Note 10.1 will work fine and the process of re-creating the issues is very clear and repeatable.
It looks like the multitouch driver becomes unstable if either one of the following occurs:
1. (Some models) You place (a part of) your hand on the screen for (at least) 5 seconds without moving it. This would usually happen when you are writing or drawing with the S-Pen.
2. (All models?) You place a finger (or several) on the screen for a longer time (close to 30 seconds) without moving it (them).
After either of these situations a 'defective unit' will show very erratic multitouch behaviour for a while.
It is easiest to see what happens if you use a so-called "Multitouch testing tool" (available Free on the Play Store). Such a tool typically shows all the screen areas where screen touches are detected by the device (in this case: the 2014 Note 10.1). Examples of such tools are: MultiTouch Test, MultiTouch Tester and YAMTT.
Erratic behaviour will usually start with all screen touches suddenly disappearing, meaning the device forgets that you have fingers (or part of your hand) on the screen. If you remove fingers (your hand) from the screen and again touch the screen several times a whole range of behaviour is seen: touches are detected and erroneously forgotten in quick succession. Sometimes so-called ghost-touches appear (meaning, the device will detect touches not anywhere close to where you are actually touching the screen).
This erratic behaviour will usually disappear when you leave the screen alone for a while, although several people (including me) have reported longer running issues (for instance during typing and editing using an on-screen keyboard). A surefire way to get rid of the issues is rebooting your device.
Since this is a "Note" device many people who's 2014 Note 10.1 suffers from these multitouch issues will encounter it while (or after!!) using the S-Pen. Others will notice issues while gaming or during typing/ editing.
The following clip by Kizune shows an example of what can happen while being inside a Multitouch testing app:
More videos you can find below (in post #16) and in the SwiftKey not working well on 2014 Note 10.1 topic, where the roots for starting this topic sprout from.
As of yet Samsung appears to be unaware of these issues, although several have approached them about this, returned their Note tablet, exchanged it or even handed one in for repairs. Hopefully we get this fixed soon.
Note 1: from early reports (in post #83) it looks like the new Note Pro 12.2 doesn't suffer from these issues.
Note 2: It is possible that a build up of static charge (through capacitance) is causing these issues, possibly caused by bad wiring (grounding) of the touch/ S-Pen detection circuitry.
Note 3: A new video has surfaced (in post #89) which shows 'noise' introduced in the touch-detection software while pinching/ zooming (see video below). It is unclear if this is related to the issues mentioned above.
i noticed this using the stock kb. i'm not a particulary fast typist on the screen but i'd get far too many lack of responses when typing on the split kb. standard qwerty was fine, but that have been b/c i'd type slower. i'm able to hit keys quicker on my gn8 without any misregistering of keystokes.
the fact there has been to OTA's in just a week is a sign they let this one out before it was ready. i still love the tablet though.
It happens to me too just like you see in the youtube video.
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it.
Click to expand...
Click to collapse
Did you try the "whole hand" thing too? It would be super if Samsung solved things that quickly, but I feel a little aprehensive. We didn't get the recent updates yet in my area so I cannot see for myself.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
no, I took both OTA's Just before rooting.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
atg284 said:
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
Click to expand...
Click to collapse
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Ettepetje said:
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Click to expand...
Click to collapse
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Edit: the YAMTT app seems buggy because the other touch apps don't go crazy when all ten fingers on on it. But I could not replicate what YAMTT app was doing to the one in the video.
atg284 said:
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Click to expand...
Click to collapse
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Ettepetje said:
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Click to expand...
Click to collapse
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
atg284 said:
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
Click to expand...
Click to collapse
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Ettepetje said:
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Click to expand...
Click to collapse
Oh I don't have that at all. no ghost finger touches ever. I have not rebooted over the period of testing either today. Are you fully updated?
I will keep checking this over time though.
Ettepetje said:
The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Click to expand...
Click to collapse
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
What problems are people seeing due to this?
Click to expand...
Click to collapse
1. When taking notes at the university, I sometimes move the viewport in S Note using the zoom gesture without the zooming motion. And as you can see, putting my hand on the screen as shown in the video triggers the problem for me, so doing that gesture is almost impossible for me. I know there are scrollbars, but they move the viewport too slowly (but of course I use them when I notice the multitouch issues are occurring).
2. Same as above, but when drawing in Sketchbook or ArtFlow. And here it's extremely annoying because there are no scrollbars I could use.
3. A small annoyance compared to the others but: When I play Carmageddon, the multitouch issues get triggered once in a while. And then I can only either control the car, or accelerate or break, but not both simultaneously. Sometimes my touches aren't even registered at all. I often get destroyed due to the multitouch issues.
Kizune said:
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
Click to expand...
Click to collapse
I changed the description in the opening post. I never had it happen like that yet. Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Did you find another way to get rid of the issues besides resetting your Note?
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Ettepetje said:
Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Click to expand...
Click to collapse
Exactly, I noticed it while taking notes. And then I made this my test method to replicate the error.
Anyway, here are some videos. The first shows a real-life situation in S Note with that problem, the second and third show that the problem also occurs in other multitouch test apps (yes, I'm looking at you, atg284 ).
And to make it more "real-world friendly", I used my old "provocation method" because that's how you put your hand on the screen while drawing and writing.
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Click to expand...
Click to collapse
Yup. And I even got that tank-like bonus police car, so they die just by touching my car tank.
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Click to expand...
Click to collapse
Did it take longer to get the erratic behavior like you said in pm? I'm trying to get the description in the opening post right, since we got 4 people now who claim they don't have it. I think the score should be 100%, and just included the Poll so that people at Samsung would quickly realise how big the impact is.
I can duplicate this.. just didn't figure how to repeat consistently until now..
First noticed when trying to pinch zoom in adobe reader .. you get very jerky redraw back and forth.. this could be app specific , but i haven't seen this on other devices
Sent from my SM-P600 using xda app-developers app
I'm also experiencing this. It's a terrible issue when taking notes in class.
Can we expect a fix?
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
RealEvil_UK said:
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
Click to expand...
Click to collapse
I have same issues with my g4 here in the US.
Unfortunately same here, on a G4, korean model F500S.
I have the same issues on my G4. So probably returning it won't solve it. I notice it the most when I am scrolling in Facebook or web pages I will open a link accidently.
I have the same, occasionally it just won't respond to some taps, i find just pressing the standby on/off button quickly sorts it but it is very annoying.
same here in israel, sometimes do not respond to double tap on lock screen to wake the G4 up
im sure its a software issue, prolly the LP 5.1
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
20degrees said:
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
Click to expand...
Click to collapse
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Try...SGS Touchscreen Booster - Google Play Store
I have run into this same problem with my Verizon G4 (VS986). Many of my taps have gone unrecognized.
I did find this.... http://forum.xda-developers.com/g4/help/fix-touch-screen-registering-touches-t3128518
I tested the software that was recommended...and IT WORKED!
Give it a try...can't hurt!
nipun1110 said:
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Click to expand...
Click to collapse
After market but plastic.
Just started to get issues where taps on the far left-hand side of the screen don't work.
blackknightavalon said:
Just started to get issues where taps on the far left-hand side of the screen don't work.
Click to expand...
Click to collapse
Okay, I was able to replicate my bug. It happens after playing a game and stops after some time. Turning autorotate back on and switching back and forth from landscape view fixed it.
Hey guys.
I was searching the forums for a fix that solves the phantom/ghost touches I'm getting frequently on my LG G4, H815 model.
Sorry for the long post but my case looks a little more complex than the ones I've been seen in here.
In my case, that's how it happens:
I receive several multi-touches at the same time, usually when Data is enabled. Sometimes it starts right when I switch from Wi-Fi.
It happens often when I'm driving and using Location+Data as well, which drives me crazy. I does also happens (like another user mentioned in this thread) when scrolling down a feed (such as on Facebook) and it suddenly likes/shares a photo/post. It also drives me crazy! And there is also the case where it taps the keyboard and send crazy typos on chat apps when you are real-time texting someone! Another hassle is right after using the camera and opening the gallery to show someone the taken photo...it suddenly scrolls the gallery and open another photo. I just can't make it to see the taken pic. Therefore, I really wanna fix this so bad since it happens every time I need something right away.
A workaround that's been helping, though it's a pain:
I found that pressing the On/Off button and giving it a few seconds will return it to a normal state. The problem is when it happens while I'm driving and are supposed to take an exit/make a turn at the moment. There are some other cases where I'm into something and giving this few seconds is not an option.
Trying right now:
Someone suggested in this thread to use the SGS Touchscreen Booster. I'm giving it a try right now.
Important notes:
This issue has been happening since I got this phone on November, 2015. We got this 6.0 update recently and I was hoping that it would fix it. It didn't.
I have an after market screen protector that I applied in order to see if the issue would go away. It also didn't.
I have been searching about a digitizer replacement but I don't think is a hardware issue, since it just doesn't happens when I'm only on Wifi at home with Data disabled. I believe that the problem is the Data connection that triggers smth.
Any thoughts?
Does anyone have any idea or have experienced the same scenario before? Any thoughts on my guess of data enabling triggering the ghost touches?
Sorry for the long post and thank you so much for reading it.
I think it's both, its hardware and software, LG tried to fixed it but it makes it worst. You can solve the problem for few seconds putting your five fingers at the home menu, It goes crazy and after it stopped making ****. Anyway this phone is great but all the problems make it ****.
I am going to use this thread even though I think my problem is not as serious as yours are.
My problem is that touches are registered, but no action is taken.
For example. Quickly tapping on an icon on the home screen will highlight it, but it will not open the application. I enabled the option in Developer mode to display the touches and the touch is registered. It's just that the app will not load. If I click for a tad longer - it loads. Happens on both stock Launcher and Action Launcher. I have not noticed it happening outside the launcher.
I read something about a keyboard update, but in the Update Center I don't have anything related to the keyboard.
The icons I see it happening with are located in the lower part of the screen.
I am almost sure that this is a software problem, but several updates have not fixed it. Currently on v20d.
Any suggestions or ideas?
After a few more testing and monitoring, I found out that the ghost touches only take place when I'm on LTE.
And even more weird, while driving through some specific areas when I'm commuting.
It's just so weird to think that some towers may send a LTE signal that may cause the ghost touches.
At home, at work, wifi or data, it doesn't happen.
I've been recently getting some instances where I would lock the phone and the fingerprint sensor won't respond to my finger.
This really started when I changed my lock to pattern swiping. Anyone have the same issue? I rebooted and changed it back to pin lock and it seems to be working all the time again, but I don't know what caused it in the first place.
Thoughts?
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
jbdan said:
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
Click to expand...
Click to collapse
It's not that it doesn't recognize my fingerprints, but it doesn't recognize fingerprints in general. So when I put my finger on it, it doesn't do the double buzz, it's just non responsive.
this happened to me yesterday several times. And i received phone yesterday... . I have two prints. Left and right index fingers. It didnt fail, just was as my finger wasnt in the reader
MDB08L
experienced the same thing this morning. phone was plugged charging and finger print would not detect, had to manually hit the power button then it worked. i find there are a lot of issues when the phone is charging though, screen sometimes becomes very unresponsive while charging. i think there was a similar thread about that as well.
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
ajmalott said:
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
Click to expand...
Click to collapse
Any luck? I did a system wipe after unlocking, and flashed new factory images but still happening.
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
ajmalott said:
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
Click to expand...
Click to collapse
I was able to find a bit more about this issue. When it happened again, I pressed the power button and quickly checked the fingerprint icon at the bottom of the lockscreen and it turned red and said "fingerprint hardware not available" for a split second before turning white again. I searched that error message and got this thread https://www.reddit.com/r/nexus5x/comments/3pm3lv/fingerprint_hardware_not_available/
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
jadesocket said:
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
Click to expand...
Click to collapse
I'm not much of a tinkerer, but I'll give this a shot. If it clears it up then okay, but if it happens again I'll probably RMA too. Not willing to put up with such inconsistencies on a brand new phone with such a highly touted feature.
Unrelated, this is actually already my second Nexus 5X. The first one I received would not take a charge, and I didn't have another USB Type-C cable to test, so they sent me an entirely new package. If wiping cache doesn't do it, I'm really not sure if I should bother with a third Nexus 5X. Kind of disheartening. I really enjoy the device otherwise.
So far so good for me, Let me know how it goes for you!
jadesocket said:
So far so good for me, Let me know how it goes for you!
Click to expand...
Click to collapse
Still happening today.
ajmalott said:
Still happening today.
Click to expand...
Click to collapse
That's a bummer. It actually happened again today for me too.
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
ajmalott said:
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
I had hope Looks like RMA imminent for me. I put that glass screen protector on so well...
ajmalott said:
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
Lots of apps updated in the past week. The problem hasn't resurfaced for a whole 48 hours now. Hoping I can put this behind me
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
It happened to me too, stock phone, no third apps installed. I will keep an eye on this.
off-topic: the discoloration of the back of the phone it's very bad!
ajmalott said:
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
Click to expand...
Click to collapse
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
jadesocket said:
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
Click to expand...
Click to collapse
Did a factory reset, and the problem came back almost immediately. Google tech support wanted me to reinstall OS entirely, but I don't have the right cable (type C to type A) to hook up to computer, so they just gave RMA. Got the new one on Friday, so far so good. But then, with the last phone, the issue didn't appear until after a week or two. Fingers pressed. Tech support really seemed to take my case as a rarity, and they were unable to recreate it with their own device. Here's hoping it's just limited to a few devices.
P.S. Off topic, but Google support wouldn't give me anything for the Black Friday deal. I asked multiple times in multiple ways. Oh well.
Is anyone else having issues with what appears to be dead areas when scrolling, swipe texting or otherwise using your phone? In typing this message the phone just lost my finger on 4 occasions. When scrolling webpages it often just stops and clicks an area where my finger was. I'll get occasional double clicking on things when I do try to click. I have trouble purposely replicating my problems but in regular us it is driving me nuts. Because I can't constantly replicate I'm not sure trying to take the phone back will be successful. Anyone else having issues? Could there be something I'm missing somewhere?
Sounds kind of mean but I hope your issue is isolated. I saw the ifixit teardown and the ease with how the digitizer came off of the glass has me worried about the longevity of the digitizer.
Happening to me insanely often on my regular Pixel.
This happens to me occasionally. Sometimes, when typing it spams v and b. If I find anything I will fill you in.
Yes, I'm having this problem with my Pixel. It happens across all apps, even in Settings. Generally it happens if I start scrolling after not touching the screen for a little while.. for example when reading a news article. The scrolling freezes, and I can move my finger around on the screen and it doesn't react, but then it might pick up my finger again and the screen jumps around or clicks on something even though I've not lifted my finger from the screen. I tested it in safe mode and it happens there also. I even got my original device exchanged, and the same thing happened immediately on the new phone. I've been in touch with Google Help this morning and they've confirmed it's a software issue. They've asked me to submit a bug report. It'll help them if more people report the bug though and they have more data to fix it, so if you're experiencing the same issue, please report it! You can chat directly to Google support through settings on your Pixel.
Haven't had any issues but I know the google keyboard can be a bit glitchy at times. I used to have a nexus 6P and I would get weird issues with that keyboard as well on that phone. Getting them less on my Pixel though.
Having issues with typing on my 6P, it's so odd as sometimes I can not type when in desktop mode and sometimes not when in mobile. Switching the webpage screen mode and also doing a soft shut off on the phone and coming back both fix it temporarily. Thought at first using a different keyboard app might help but what app it runs does not solve the problem.
Same problem here. Google pixel
Happening to me as well. Did a factory image flash and it seems to have helped but still happens once in a while. I notice it the most when I'm using reddit sync. Seems to just happen too frequently.
Just an update on this... After doing a few steps suggested by google tech support like, test on safe mode, factory reset using bootloader method, etc... They just replaced my unit. I'm using a new one today and problem is not existent now. I would assume the problem would be hardware.
To be honest, I'm quite happy with their tech support...24/7 support and the staff are really competent. This in my opinion, is worth the high price of the pixel. Good job google!
I have the standard Pixel, and I too had issues with typing (occasionally wrong letters or spaces would register), and dead areas in the top corners of my screen when trying to open apps. I was going to return it one day after confirming that the dead areas at the top of the screen were persistent, but for some reason I decided to grab an App from the bottom of the screen and move it by sliding to the top area. Instantly this cured the dead area issue, even after I moved the app back to the bottom of the screen. It's as if it recalibrated the touch sensitivity vertically as it stopped erroneous spaces when typing too.
Pixel 2 one handed thumb scrolling issue
I have the pixel 2 and I have intermittent scrolling issues when I hold it one handed and try to scroll with my thumb. I realized it's because the base of my thumb is brushing the opposite side of the screen and preventing it from scrolling freely.
Newpixel2 said:
I have the pixel 2 and I have intermittent scrolling issues when I hold it one handed and try to scroll with my thumb. I realized it's because the base of my thumb is brushing the opposite side of the screen and preventing it from scrolling freely.
Click to expand...
Click to collapse
You should probably post about that in the Pixel 2 forums.
Been using the phone for the last 12 hours and I noticed something towards the end of my use last night.
The screen seemed to become unresponsive. And when it would work it would start to make its own input when scrolling and opening any app or link my finger would drag over while scrolling.
Changed refresh rates, changed resolutions, even seen if the blue light filter was the issue. Nothing.
Almost seems like the screen drops frames when scrolling, like it gets caught on something.
New development. Fingerprint sensor doesn't respond at all and inputting a pattern is damn near impossible. Going to try removing the screen protector to see if that could also be the issue
Did a factory reset
Issue seems to be where the finger print scanner is
It's almost like a dead or unresponsive zone.
Sounds like a factory defect, better have it replaced if resetting didn't worked.
Small video showing when scrolling over the fingerprint reader, the screen almost loses input
Defect.
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
imtjnotu said:
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
Click to expand...
Click to collapse
Sounds like Samsung support LOL...sorry you're having issues
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Return that pal, that doesn't sound good at all.
lovers74 said:
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Click to expand...
Click to collapse
one of the first things i did to trouble shoot. still having the issue. sometimes the screen completely loses all touch registration and it doesnt even know im trying to swipe or push on things. just realized it did this also after tmobiles new software update.
im still waiting here to hear back from samsung on how they are going to fix this issue
The same thing happens to me. Pulling down the notification shade seems to be the only thing that still works. It seems to goose the phone and it starts working again.
Test using the *#0*# diagnostic menu and use the Touch test.