Fellow Pixel-ers,
So, I broke my screen about 8 months ago. It had coverage and got it replaced by a Google authorized screen fixer place.
I noticed early on that things didn't seem quite right. If I pushed down too hard on the screen, my touch wouldn't register. But, it didn't happen too often and I didn't want to have to deal with arguing that they may have poorly installed the new screen/digitizer and that it wasn't 'my fault'.
As time went on I started noticing that the almost bottom of my screen would not register a touch but mostly only at night. Again, it didn't happen too often and it usually went away after a little poking/prodding/pushing/.
I also thought it might be an application that I gave 'screen Overlay' rights that I shouldn't have and it was causing issues.
I validated my issue by using a Touchscreen Test app.
When I use an app like Vysor I am able to 'access' that area of the screen even when my fingers cannot. Does that validate this is a hardware issue?
The area affected was definitely more than just a few pixels (see screenshots).
More recently it was happening more frequently (not just at night) and it almost never goes away.
I wanted to make sure it wasn't a software issue. So I planned on dirty flashing my OS (AquariOS), but actually ended up accidentally upgrading to a clean version of Android 10. Unfortunately, the issue was still there.
I then did a clean flash and downgraded back to Pie w/AquariOS.
Shortly after getting back up the issue showed up again.
At this point, I have virtually lost all touch response for the bottom 1/8 (not quite the very bottom) of my screen. I've had to use a floating keyboard because the space bar falls right in that area. Sometimes I can't click 'next' or 'continue' in apps or web sites.
Has anyone ever experienced this very odd digitizer issue like this? Any thoughts/suggestions/ideas.
I'm guessing the only solution is a new phone as it is not worth the money to fix it.
So now I'm just waiting for either the Pixel 4A or 5 to come out so I can get a new phone I guess.
I just find this very odd how specific this area of 'dead pixels' is. I always thought it was more random than a specific rectangle.
I look forward to hearing from anyone.
A (not working with a full screen) Bug
I've faced the same issue mate....
a_bug said:
Fellow Pixel-ers,
So, I broke my screen about 8 months ago. It had coverage and got it replaced by a Google authorized screen fixer place.
I noticed early on that things didn't seem quite right. If I pushed down too hard on the screen, my touch wouldn't register. But, it didn't happen too often and I didn't want to have to deal with arguing that they may have poorly installed the new screen/digitizer and that it wasn't 'my fault'.
As time went on I started noticing that the almost bottom of my screen would not register a touch but mostly only at night. Again, it didn't happen too often and it usually went away after a little poking/prodding/pushing/.
I also thought it might be an application that I gave 'screen Overlay' rights that I shouldn't have and it was causing issues.
I validated my issue by using a Touchscreen Test app.
When I use an app like Vysor I am able to 'access' that area of the screen even when my fingers cannot. Does that validate this is a hardware issue?
The area affected was definitely more than just a few pixels (see screenshots).
More recently it was happening more frequently (not just at night) and it almost never goes away.
I wanted to make sure it wasn't a software issue. So I planned on dirty flashing my OS (AquariOS), but actually ended up accidentally upgrading to a clean version of Android 10. Unfortunately, the issue was still there.
I then did a clean flash and downgraded back to Pie w/AquariOS.
Shortly after getting back up the issue showed up again.
At this point, I have virtually lost all touch response for the bottom 1/8 (not quite the very bottom) of my screen. I've had to use a floating keyboard because the space bar falls right in that area. Sometimes I can't click 'next' or 'continue' in apps or web sites.
Has anyone ever experienced this very odd digitizer issue like this? Any thoughts/suggestions/ideas.
I'm guessing the only solution is a new phone as it is not worth the money to fix it.
So now I'm just waiting for either the Pixel 4A or 5 to come out so I can get a new phone I guess.
I just find this very odd how specific this area of 'dead pixels' is. I always thought it was more random than a specific rectangle.
I look forward to hearing from anyone.
A (not working with a full screen) Bug
Click to expand...
Click to collapse
Hi bro, I've face the exact same issue, but for me it was at the center of the screen. Luckily my phone was under warranty, but getting them to replace my touch digitizer was a whole different thing. At first they just didn't acknowledge the issue, then I tried showing them proofs but they didn't believe as they were from some third party apps. Finally, I used markup to show them the issue and recorded it took some screenshots as well. So, they replaced my digitizer at last after constantly speaking them for 2-3 weeks. I can only suggest you that if your phone is still under warranty or you have accidental damage coverage, ask them to replace them. Otherwise, it'll be better to buy a new phone as replacing the screen from your pocket may be very costly.
For anyone who reads this thread,
I resigned myself to having a bad digitizer but was starting to look to replace the phone. Then about a week later I inadvertently dropped the phone in a pool. Unfortunately, as the screen had been replaced the waterproofing was no longer good and phone was a brick. So I never resolved the issue but will always assume that the company that replaced the screen did a less perfect job and that when a screen is replace the phone looses it's waterproofing ability
-A (new Pixel 3XL owning) Bug
Related
Hi to all,
A couple of days ago I noticed that when I answered a call the colors of the screen looked bad, and I didn't pay attention to it.
Now my screen has transparent horizontal lines which are pretty visible, kind of like interference you get in computer screens when you take a picture of them.
I would like to mention that I haven't dropped the phone even once.
I'm considering doing a factory resest in hopes that it will solve the problem, but I doubt that it is a software issue.
What do you guys think?
Please advise
Itay
Sounds like a broken screen to me. And definitely like a warrenty case. Restore stock f/w if you have flashed and return it.
Restore the original firmware (if you have flashed the phone) and call the samsung service for the assistance.
the thing is that now I don't see it at all.
It's as if it came and gone.
I disabled my task killer and juice defender, performed a complete titanium backup, in case I want to restore afterwards, and now everything is normal.
It does sound like a hardware issue, but do you think there's a chance it is software related?
I'm asking because I purchased it in europe, and I don't live there, so sending it for repair is something I would rather avoid.
Of course, if it is indeed 100% hardare issue, I have no choice.
That is why I'm asking, to be certain and to see if there are others who experienced this issue.
Your replies are much appreciated
update:
It appeared again -> Did a Factory Reset -> It's still there -> Sending for repair.
Must be a hardware issue.
Thank you for your replies.
I've actually always had slight screen issues with my Galaxy S also. The screen flickers slightly once in a while. I don't know if the radio is actually the cause but it's the kind of thing you might expect from radio interference.
Has anybody else noticed this?
Benjamin Dobell said:
Has anybody else noticed this?
Click to expand...
Click to collapse
Nope, never seen any flicker. My screen seems to have a defect of it's own though, but I'm not sure if it's worth the effort to send it in, because I imported mine from the UK while I live in South Africa.
When in the sun or under bright light I can see a two vertical lines near the sides and a horizontal line on dark/black colours and when the screen is off. As if those pixels have a grey/brown tint to them. The line is mostly one pixel thick but in places it is two pixels.
They are almost impossible to see unless under sunlight where they are clearly visible where the screen is black.
Does anyone else see this or know anything about it?
Edit: Apparently it's just the motherboard or something visible through the screen and they all have it, so I'm worrying about nothing...
That's interesting...
It used to come and go, but I think now it's here to stay.
It's really annoying and the screen, while usable, is really not a pleasant sight to look at.
I've attached some photos showing the problem.
With a normal screen I would say that it looks that way because that's what you see when you photograph a screen of an electronic device, but the sad thing is that what you see in the picture is exactly what I'm seeing now.
I did a factory reset, so it's in german now.
I heard some Droid X had a similar problem, but didn't know Galaxy S was having it as well.
In any event, can you confirm that after a factory reset, I no longer have root access?
Just making sure so that they don't give me problems with the warranty.
seem like the phone was dropped, and the screen got damaged
the connectors are lose
double posted again....
Really?
That's very weird...
The only time it was "dropped" was from half a meter , it didn't fall directly but partially sideways, it was with a case, and it landed on its back, not on the screen.
I wouldn't even call that a fall.
Unless, someone in my family dropped it without telling me...
Either way, I think there's no escape but to send it to repair.
If you think it's a problem with the connectors, would you try and give it to some local lab to try and fix it or send it to samsung for replacement?
I faced similar problem.
This problem only occurs when I use the phone in 2g mode.
there are occasions whereby the signal bar for 2g is full and when I place the phone near some conductive surfaces the lines becomes very obvious, to the point of irritating.
nit sure if anyone has such problems too
I have same problems with horizontal lines.
I never paid attention if i am on 2g or 3g when it happens. I will now.
Edit: rooted on jm5
-------------
It seems that my phone too has started to do the same thing since last night.
I have called Samsung and am waiting to hear from them now.
I hope this is a thing covered in the warranty.
I have reverted to the local ROM for India and have deleted everything on my device.
Yet it shows lines flickering like you can see on old computer monitors.
Its not as bad as the ones on the attachment above but it is starting to annoy me.
It usually happens when the screen is completely filled with a single color except black.
Eg. When you pull down the notification tray down.
Also I seem to notice that when the wifi is off, it stops.(I dunno maybe a placebo effect)
aditya_t90 ,
I have sent it to Samsung for repair, and they should tell me in the coming days exactly what the problem is and whether it can be fixed under warranty or not.
I will update as soon as I hear from them.
Until then, try to see if it changes when you hold the phone differently, for example if you grip it more firmly or hold it in another way.
itaykoren said:
aditya_t90 ,
I have sent it to Samsung for repair, and they should tell me in the coming days exactly what the problem is and whether it can be fixed under warranty or not.
I will update as soon as I hear from them.
Until then, try to see if it changes when you hold the phone differently, for example if you grip it more firmly or hold it in another way.
Click to expand...
Click to collapse
When did you send it in and when did they receive it(if you were not there when they got it).
Also how long has it been without your phone?
The samsung service center is shut in my area today.
I will go to them tomorrow and get this sorted out.
Its not like the phone was cheap or anything.
I actually sent it to my uncle in Germany because it was purchased there.
He went to the store where he bought it and the store owner immediately sent it to samsung and said that probably by this Tuesday or Wednesday (so tomorrow or in 2 days) he will get an answer from them and see what's going on.
aditya_90 ,
Just to let you know that Samsung are sending me a new phone to replace the damaged one.
I sent in my phone for repairs and they replaced the LCD module. The problem is now gone.
I suggest that you should do the same while the warranty still holds since it appears to be the LCD that failed somewhat.
Hi
I upgraded to my new DHD less than 3 weeks ago. It is not rooted and I did the recent OTA update over Christmas.
Over the last couple of days I have started to experience difficulty unlocking the device on the slide-to-unlock screen. The problem seems intermittent - somethimes it will unlock fine, and other times the slider just seems to "get stuck" at the bottom of the screen.
At first I thought this a bug or something, but after some investigation I am concerned there is a problem with the digitiser. I opened a picture and zoomed in to fill the screen and tested the touchscreen in different places by sliding the picture around. What I found was that the bottom 1cm of the screen above the keys does not respond properly to Up and Down swipes. It is fine however with side-to-side and also individual taps. This is obviously a problem when trying to move the unlock slider!
I've had a screen protector on for about a week - I don't imagine this has caused the issue but haven't removed it to test as yet as I don't have a spare. Aside from this, the device has been very well looked after, definitely no bumps etc and kept in an HTC leather pouch.
Any ideas? Should I return it to CW?
Thanks
OK, I seem to have resolved this for the time being but expect the problem to return.
I downloaded a screen test app that allows you to draw on the screen and got some very strange results. A 1cm band of screen about 1cm up from the bottom was completely unresponsive. Trying to draw a horizontal line within this band would result in lines being drawn either above or below it, or strange vertical lines "jumping" around. The rest of the screen was fine. I realised this is why I have been struggling to close the keyboard - the button is placed within this band and trying to press it would result in on of the buttons above or below being pressed. Also have had problems with the sapce bar.
I did a restart (not fast) and this has resolved the issue, however I expect it may return as I did a restart only yesterday.
At least it is obviously software and not the digitiser....
Hi again. As expected, the issue returned after a couple of hours. This time however, restarting is not making a difference.
I resorted to a hard rest, which has not changed anything either.
Any help/ideas would really be appreciated...
Best to return it for repairs or exchange. Seems like the digitiser is faulty.
Sent from my Desire HD using XDA App
olivierlee said:
Best to return it for repairs or exchange. Seems like the digitiser is faulty.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I agree, this definitely sounds like a hardware problem.
Hello xda! , i have just bought i nexus 7 (2013) last wednesday and today i have noticed that there is a certain area of the screen where if i swipe my finger from another location it terminates the touch and starts another one, i enabled developer options and turned on the pointer location to see what was happening and it shows the line when im close to the "spot" but when i strike through it it starts another line after that "spot" but if i tap its okay i discovered this while playing draw something and when i go through that location it just start a new brush line or whatever and its a little annoying, the thing is that i bought it at RadioShack but didn't add the warranty but still have the 31 day warranty.
Hope you understand what im saying
1. Is this a reason to replace my tablet?
2. Will they replace it or what?
1. Yes
2. No reason why not, you're within a week.
(if you used a CC you've got even more leverage)
Now that you know what to look for you can test before you even leave with it. :thumbup:
Yeah I Think i'll keep it for a few days (15 or 20) if google launches a patch i'll keep it if not i'll try to replace if the same issue is present on the replacement i'll ask my money back
Sent from my Nexus 7
I don't think that a dead spot that's repeatable is software, but, what the heck. They're pushing out an update right now that's supposed to fix the touch issue, so you'll know soon enough...
Hello Guys, i just updated my tablet to JSS15Q and the multitouch issue has been corrected but my problem with the vertical dead spot i mentioned is still there today i'll back up everything that i can and tomorrow will take it to RadioShack for replacement. Thanks
Sent from my Nexus 7
danvee said:
I don't think that a dead spot that's repeatable is software, but, what the heck. They're pushing out an update right now that's supposed to fix the touch issue, so you'll know soon enough...
Click to expand...
Click to collapse
It usually isn't a true dead spot in the sense that there is no voltage drop or current going through that area. It is usually that for that area they need to use a different threshold to trigger detection. I saw in the firmware changes they can fine tune even edge responses, so I assume they can have some sort of matrix where the thresholds are specified for different parts of the screen. The problem might arise that if they make some area more sensitive, displays that are already more sensitive in that area might start having undesirable behavior.
I have seen areas where the screen won't register taps but will register swipes. I've also seen areas that won't register taps or swipes, but when you hold the unit it starts to register them, so clearly the wiring is there for the input to be registered, but the thresholds to determine noise vs input may need to be tuned.
It does seem there is a lot of variance on these touchscreens which appears to be making it hard for them to come up with one firmware that fixes everything.
They may need to add some user tunable functionality to account for the different variances.
Is that even possible?
Interesting, but it's not a constant in my case.
The upper ⅓ in portrait becomes decreasingly sensitive toward the top, but only periodically. Maybe 2-3X/day.
Can't reproduce it at will, or by introducing any series of events (at least consciously).
It just happens.....
The occasional freezing happens, maybe once/day, and again, not reproduce able at will.
One plus is that any spontaneous rebooting has been while it's 'sleeping', hasn't done it during use.
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.
Yesterday I received a gently used Oneplus 7t I bought from ebay. I noticed as I was trying to log in to my Google account during setup that the letter "a" wasn't registering very well, but it seemed like when I unplugged it from the charger it worked again, so I figured it was the result of using a cheap cable.plugged into a laptop and kept setting it up. Later I noticed it happening again, all along the left side - I couldn't toggle the wifi quick setting. So I started testing and experimenting. If you start the touch elsewhere on the screen and go to the left edge, it registers fine, but if you start anywhere in the "dead zone" it rarely ever works. Dead zone is less than 1 cm in width (enough to make it difficult to get the letter a or the shift button and almost impossible to type the letter q) and spans the entire left side. All other edges work fine. I thought maybe it was software related (I'm on OOS 10.3.7) so I tried a couple different kernels (arter97 and bluspark); they definitely didn't improve the issue and might have made it a bit worse. The result of the engineering mode test was "touchpanel fail", which implies it's a hardware failure, but could it be if that part of the screen does work some of the time? I took a phonecall as I was typing this and after I hung up, the dead zone seems to be more responsive, although it still misses taps fairly often. That again makes me think it's likely a software issue. But I can't find anyone else with the issue while googling the problem, which leads me back toward a hardware issue. Really don't want to fool with sending it back and finding another one to purchase if I don't have to.
There's a sort of relevant thread on the 1+ support forum from 05/20
https://forums.oneplus.com/threads/latest-update-terrible-touchscreen-sensitivity.1233414/
1+ answer is
According to your update history and how you updated, a cache cleaning might be necessary.
You could even have to clean flash a new ROM.
Click to expand...
Click to collapse
wfred said:
There's a sort of relevant thread on the 1+ support forum from 05/20
https://forums.oneplus.com/threads/latest-update-terrible-touchscreen-sensitivity.1233414/
1+ answer is
Click to expand...
Click to collapse
While that thread does seem pretty relevant on its face, this is a factory reset phone that was clean flashed (no OTA delta because I had unlocked the bootloader). And the sensitivity was fine across the screen except for that strip on the left side.
So I kept hunting for answers, and one of the crazier ones I found was to take the electronic igniter out of a lighter and click it on the screen. Would you believe that actually improved it, to the point of me almost declaring it fixed? That is, until I plugged it in the charge again. Not only does the problem come back full force when plugged it, but it remains somewhat after unplugging (I think it has missed at least 4 "a"s in this post). So I guess it is some kind of hardware issue