Develop Bugs

[Q] Note 10.1 touchscreen bug or issue whatever it is ? help!

Its been 2 weeks since i bought this tablet. I have a problem since then which is when i use touch screen, while scroolin up and down and stop without drawin my finger, page under my finger vibrates for a few pixels. For example while im using photoshop touch and crop someting to move with my fingers , that cropped piece starts to shake . Does this exist in all devices ? If its not im gonna take the device back to store . Is it a known problem that no one mentions about ? With pen everthing is cool but when I start using my fingers its shaky like 3 4 pixels.

http://forum.xda-developers.com/showthread.php?t=2619898
http://forum.xda-developers.com/showthread.php?t=2491690
http://forum.xda-developers.com/showthread.php?t=2646401
jep it's a very well known issue and pretty much everyone has it. People are pretty sure that it is a software bug that can be fixed in the next update though.
I'm going to wait until the next update hits and hope that it will be fixed, because otherwise the tablet is perfect. Otherwise I'll probably return it as well.

The capacitive touchscreen controller in these tablets attempts to provide touch coordinates that are as accurate as possible. when you place a finger on the screen, you arent touching a single point, but rather a number of points, for which the controller has to determine a center point. For capacitive screens, the calculation of this touch point can vary from one iteration of the calculation to the next as a result of subtle capacitance changes due to humidity, contact pressure, etc. if you load any of a number of test programs that output the touch coordinates, you'll see that they jump around by a few pixels.
What this means is that the driver for the touchscreen doesnt include enough deadband around the touchpoint to eliminate positional jitter. This can be corrected in the driver, but whether a software update will resolve it or not remains to be seen. If the jitter isn't acceptable, I would plan to return the tablet within your applicable return window, rather than count on a software update that may or may not address the problem. Samsung has been slow to respond to these kinds of issues, if they address them at all.
Sent from my SM-P600 using Tapatalk

dpersuhn said:
The capacitive touchscreen controller in these tablets attempts to provide touch coordinates that are as accurate as possible. when you place a finger on the screen, you arent touching a single point, but rather a number of points, for which the controller has to determine a center point. For capacitive screens, the calculation of this touch point can vary from one iteration of the calculation to the next as a result of subtle capacitance changes due to humidity, contact pressure, etc. if you load any of a number of test programs that output the touch coordinates, you'll see that they jump around by a few pixels.
What this means is that the driver for the touchscreen doesnt include enough deadband around the touchpoint to eliminate positional jitter. This can be corrected in the driver, but whether a software update will resolve it or not remains to be seen. If the jitter isn't acceptable, I would plan to return the tablet within your applicable return window, rather than count on a software update that may or may not address the problem. Samsung has been slow to respond to these kinds of issues, if they address them at all.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Very good point. The driver seems to try to be very accurate. One my older tablet (Acer A500) many times when using Chrome it would magnify the area where I touched as it couldn't really tell which link I had pressed. It seems with this tablet that almost never happens, almost as if the driver is trying to be as accurate as the pen. Sorry, my fingers are not that accurate! Maybe its a (incorrect) reaction to the high res of the tablet?
The driver should be averaging the touched area to get the touch point, but it should also give some kind of uncertainty so it doesn't seem unnaturally accurate (pixel width finger).
I should have tested this on the note 12 or the tab pro's at bestbuy last night...

dpersuhn said:
The capacitive touchscreen controller in these tablets attempts to provide touch coordinates that are as accurate as possible. when you place a finger on the screen, you arent touching a single point, but rather a number of points, for which the controller has to determine a center point. For capacitive screens, the calculation of this touch point can vary from one iteration of the calculation to the next as a result of subtle capacitance changes due to humidity, contact pressure, etc. if you load any of a number of test programs that output the touch coordinates, you'll see that they jump around by a few pixels.
What this means is that the driver for the touchscreen doesnt include enough deadband around the touchpoint to eliminate positional jitter. This can be corrected in the driver, but whether a software update will resolve it or not remains to be seen. If the jitter isn't acceptable, I would plan to return the tablet within your applicable return window, rather than count on a software update that may or may not address the problem. Samsung has been slow to respond to these kinds of issues, if they address them at all.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I agree. This is exactly how it looks like. I understand that the touchscreen needs to be as accurate as possible for the pen. But a simple solution or workaround would be to have a "pen mode" for when the pen is out and a finger mode while the pen is docked in the case.
I'm sure there will be a solution for this sooner or later, especially since samsung is releasing more and more devices with wacom digitizers and stylus. And it's more or an annoyance than a deal breaker for me. There aren't any situations where it keeps me from getting my work done or anything. It's just a little annoying sometimes.
And in my experience samsung is actually quite good with fixing things these days.

Thanks for replies! I guess its the driver too. Comparing with apple , yes they dont offer to much of feature but i guess they are best at what they offer and this is the only problem with samsung. Amazing features that we come across via samsung but no perfection.
Sent from my GT-I9500 using xda app-developers app

Screen Issues: Right side of screen lags

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

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

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

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

Just had mine go as well :crying:

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

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

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

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

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

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

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

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

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

Wow really? That's no good!

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

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

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

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

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

Part of Note 10+ Screen Goes Black

This problem just started today, I've done nothing with settings, have not installed any apps recently, did not drop it, expose it to water, or anything that could possibly cause damage. What's happening is that basically about 1 inch-1 inch 1/8 of the bottom of the screen turns black, and at almost random, sometimes it could go a minute and half or so, sometimes 30 seconds, sometimes within 5 or less seconds. The strangest part? The part that goes black still operates fine to touch, so if an icon or letter of the keyboard, or whatever, is located in that area, it can still be selected/operates. Taking a screenshot to try to show it is worthless since it'll show the screen as just fine, so I attached a picture and a video of the problem from an old phone of mine. The blacked out are will go right back to normal if you turn the screen off, wait a second, and turn it back on. Also, if the blacked out area is there, it'll go away after about a half a second when the screen dims right before the screen inactivity turns the screen off. I've only had this phone for a couple months, I got it back on December 7th 2019.

I learned something else. If I manually lower the brightness to a particularly low level, the black goes away, so it seems to in some strange way be related to the phones brightness level (I use auto brightness), this also might explain why the black comes at differing intervals, as my brightness is adjusting constantly to my surroundings, the time before it comes is either shortened or lengthend based on the brightness.

It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.

willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
I was just thinking I might have to do factory reset, if that doesn't work, and it needs repair/replacement, do I go to an authorized Samsung repair place (I know I have one within about a couple miles of my house), it's
obviously well within warranty, or take it to At&t store as I do have that AT&T Protect Advantage coverage for my phone?

willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
Did the factory reset, turned out to be a waste of time. That black bar was showing immediately, right at the setup screen. So I guess it's safe to say that it's a hardware issue, defective whatever. Funny story is that when I bought this phone, my att store only had two of them left, one was immediately defective, it wouldnt get past the main logo screen, and now I got this one and it became defective within just a couple months, got to love it.

willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
Just left AT&T store where I initially purchased the phone. They're shipping out a brand new note 10+ to me today and I'll get it tomorrow ?

Glad to hear! That definitely sounded like faulty hardware. Funny you saw two failures, I guess it will happen with such complex devices.

Note 10 plus screen goes black
Hi i thought i was crazy until i saw your thread. The same thing is happening to me but it does not go continuously so id see two red squares first theyre really small and they appear anywhere on the screen then if try to screenshot them they show upblack in the screenshots instead of red . I just need to know if anyone found a solution yet because my phone came with the warranty booklet but it wasnt filled out.

Tech girl99 said:
Hi i thought i was crazy until i saw your thread. The same thing is happening to me but it does not go continuously so id see two red squares first theyre really small and they appear anywhere on the screen then if try to screenshot them they show upblack in the screenshots instead of red . I just need to know if anyone found a solution yet because my phone came with the warranty booklet but it wasnt filled out.
Click to expand...
Click to collapse
You just need the proof of purchase, or, if you got it on contract, the contract itself will suffice

Weird Digitizer Issue (Just me)?

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

Far left side of OP7t screen doesn't register touch reliably.

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