Related
Hello
I'm wondering just how durable an E3D is, namely the touch sensors inside it.
Recently I dropped the phone twice on a hard surface, and started noticing strange behaviours, firstly with the touch functions and secondly with the phone always freezing up.
Not always, but sometimes when typeing, it's just a mess, the capitalizer writes a letter, multi letter feature is inaccessible, basically none of the characters work like they were ment to. The only solution thus far is to lock and unlock the phone, which fixes the keyboard and the touch functionality.
Sometimes I can't unlock the phone because the ring moves 3 times shorter of a distance, opposed to when its working properly, and if so you can forget about dragging icons into the circle to answer a call, it just won't go in all the way.
Oh and the freezes, completely, none of the touch sensitive buttons or the screen responds, sometimes the screen is the only responsive part while the buttons are completely dead, a lock/unlock is needed to fix it short term, also the buttons led go out, becoming none responsive, sometimes the led is off, yet I still get a vibrational feedback (Have it enabled) So all these irregularities are new, it never happened before dropping the phone! The only touch sensitive related issue I had before, from time to time, was the unlock pattern gesture not tracing, instead of sticking to the first circle I begin at, it moves to the next I drag my finger over. (also fixable by relock/unlocking)
During this post the keyboard wasn't acting up thankfully, but its getting more and more irritating to lock and unlock the phone while typing a message to someone.
First I was suspecting a virus, or low memory causing this behaviour, but after thoroughly cleaning the phone and acquiring more memory (by closing apps) I was still having the problem.
Any idea how sensitive the components are if subject to repeated shock from a distance of 1.5m or 5ft?
What are my options here if the irregularities persist?
G4m3rHead said:
Hello
I'm wondering just how durable an E3D is, namely the touch sensors inside it.
Recently I dropped the phone twice on a hard surface, and started noticing strange behaviours, firstly with the touch functions and secondly with the phone always freezing up.
Not always, but sometimes when typeing, it's just a mess, the capitalizer writes a letter, multi letter feature is inaccessible, basically none of the characters work like they were ment to. The only solution thus far is to lock and unlock the phone, which fixes the keyboard and the touch functionality.
Sometimes I can't unlock the phone because the ring moves 3 times shorter of a distance, opposed to when its working properly, and if so you can forget about dragging icons into the circle to answer a call, it just won't go in all the way.
Oh and the freezes, completely, none of the touch sensitive buttons or the screen responds, sometimes the screen is the only responsive part while the buttons are completely dead, a lock/unlock is needed to fix it short term, also the buttons led go out, becoming none responsive, sometimes the led is off, yet I still get a vibrational feedback (Have it enabled) So all these irregularities are new, it never happened before dropping the phone! The only touch sensitive related issue I had before, from time to time, was the unlock pattern gesture not tracing, instead of sticking to the first circle I begin at, it moves to the next I drag my finger over. (also fixable by relock/unlocking)
During this post the keyboard wasn't acting up thankfully, but its getting more and more irritating to lock and unlock the phone while typing a message to someone.
First I was suspecting a virus, or low memory causing this behaviour, but after thoroughly cleaning the phone and acquiring more memory (by closing apps) I was still having the problem.
Any idea how sensitive the components are if subject to repeated shock from a distance of 1.5m or 5ft?
What are my options here if the irregularities persist?
Click to expand...
Click to collapse
Don't know how durable it is...but I too face the unlock pattern issue sometimes, IMO it is a software issue .. Also if you take too much time to draw the pattern the screen goes off (even if you keep your fingers touched)......
The only solution thus far is to lock and unlock the phone, which fixes the keyboard and the touch functionality.
Click to expand...
Click to collapse
If a reboot fixes the problem, then it's not hardware, its a software problem. Do a factory reset.
Recently I dropped the phone twice on a hard surface,
Click to expand...
Click to collapse
Dropping your phone will usually cause hardware problems. Get a case or don't drop the phone anymore.
First I was suspecting a virus
Click to expand...
Click to collapse
There are no android viruses.
but after thoroughly cleaning the phone and acquiring more memory (by closing apps) I was still having the problem.
Click to expand...
Click to collapse
DON'T use task killers or force close apps, that only makes things worse, and is probably what is causing your problem.
sitlet said:
If a reboot fixes the problem, then it's not hardware, its a software problem. Do a factory reset.
Dropping your phone will usually cause hardware problems. Get a case or don't drop the phone anymore.
There are no android viruses.
DON'T use task killers or force close apps, that only makes things worse, and is probably what is causing your problem.
Click to expand...
Click to collapse
Well when app's foreclose there isn't much to do but close them ?
The task killer, well, I don't really use it much, I just have it, its called eRay..
Sent from my HTC EVO 3D X515m using XDA
sitlet said:
If a reboot fixes the problem, then it's not hardware, its a software problem. Do a factory reset.
Click to expand...
Click to collapse
It's not a reboot, just a lock/unlock of the screen/phone..
Sent from my HTC EVO 3D X515m using XDA
What on Earth is a 3vo!? Is it anything like an iphone 4!?
joehunni said:
What on Earth is a 3vo!? Is it anything like am iphone 4!?
Click to expand...
Click to collapse
An 3VO or E3D are abbreviations for the EVO 3D from HTC
Sent from my HTC EVO 3D X515m using XDA
Here's an update on this issue...
I've noticed that the upper left corner is the cause. How?
Well, in landscape mode on my homescreen, trying to pull the notification bar down (then from, the bottom left since were in landscape) will instead (without any animation) try to go to full homescreen view where I see all my 7 homescreen, but it does it in a zoom like feature, where the more I pull it to the side the more it will zoom in until final animation frame is reached LMAO.. I'm actually crying...
The sensor might be off, in that corner of the screen as dropped phone tend to land/hit the corners first...
I should ask an xda dev. to cook me up a "sensor status check" app to check if any of them are functioning incorrectly..
I don't know what more then that I could do?!..
Sent from my HTC EVO 3D X515m using XDA
Hey guys, thought I drop my final verdict on this issue.
As you all (who read this thread) knows, I was having an irritating problem with my E3D, namely the touch functionality of the screen was messed up, but only in a certain area, where I thought the sensors got discalibrated from the drops the Phone went through on hard surfaces.. I have used an app called "Check My Android" and the feature "MultiTouch" to identify the spot on the screen, where if I touched, a daemon took over my phone and started all kinds of wired behaviour such as item triggers on the other side of the screen and freezing, even slow mo zooming of the homescreen, one touch passive zooming of webpages and so forth..
Now with that app, I was certain that everything with it is not in order, but I didn't have the slightest clue on what to do about it. I ran across a comment about the built in utility diagnostics tool code for the Phone while browsing on U2B (YouTube), so by typing "*#*#3424#*#*" (which starts as you enter the lasts star) will basically allow you to test every aspect of functionality of your phone, where i also went for the screen draw test, and found myself strengthening what I already thought was the problem "an area on the screen messing everything else up" as I pressed within this area I found a straight line jump, from the "dead zone" to the bottom middle of the screen, as I was drawing circles, it drew a straight line there as i went over it with my finger every time. Than browsing on after that code's discovery, for "EVO 3D touchscreen problems" I ended up on a video offering similar problems..
Now the breakthrough or rather yet the solution came from that videos second and only comments, saying how "Disabling the ScreenLock of the Phone would fix that problem" and so it did!!! I'm not having any disturbance while typing, flipping pages touching that area or anything out of the ordinary, otherwise the Phone was almost unusable. It let's me to believe its a software miscoading flaw, but it wasn't always like that even though I used the screenlock since day one, so I'm not entirely sure what's up? other than its fixed...
I hope this fix can relieve others just as it did me
And the diagnostics code is also useful.. should be stickyd :]
Sent from my HTC EVO 3D X515m using XDA
G4m3rHead said:
Hey guys, thought I drop my final verdict on this issue.
As you all (who read this thread) knows, I was having an irritating problem with my E3D, namely the touch functionality of the screen was messed up, but only in a certain area, where I thought the sensors got discalibrated from the drops the Phone went through on hard surfaces.. I have used an app called "Check My Android" and the feature "MultiTouch" to identify the spot on the screen, where if I touched, a daemon took over my phone and started all kinds of wired behaviour such as item triggers on the other side of the screen and freezing, even slow mo zooming of the homescreen, one touch passive zooming of webpages and so forth..
Now with that app, I was certain that everything with it is not in order, but I didn't have the slightest clue on what to do about it. I ran across a comment about the built in utility diagnostics tool code for the Phone while browsing on U2B (YouTube), so by typing "*#*#3424#*#*" (which starts as you enter the lasts star) will basically allow you to test every aspect of functionality of your phone, where i also went for the screen draw test, and found myself strengthening what I already thought was the problem "an area on the screen messing everything else up" as I pressed within this area I found a straight line jump, from the "dead zone" to the bottom middle of the screen, as I was drawing circles, it drew a straight line there as i went over it with my finger every time. Than browsing on after that code's discovery, for "EVO 3D touchscreen problems" I ended up on a video offering similar problems..
Now the breakthrough or rather yet the solution came from that videos second and only comments, saying how "Disabling the ScreenLock of the Phone would fix that problem" and so it did!!! I'm not having any disturbance while typing, flipping pages touching that area or anything out of the ordinary, otherwise the Phone was almost unusable. It let's me to believe its a software miscoading flaw, but it wasn't always like that even though I used the screenlock since day one, so I'm not entirely sure what's up? other than its fixed...
I hope this fix can relieve others just as it did me
And the diagnostics code is also useful.. should be stickyd :]
Sent from my HTC EVO 3D X515m using XDA
Click to expand...
Click to collapse
Never mind that, it was only a temporary fix, as it started doing it again after a while...
Try calibrating your screen via display settings if you haven't already. Also are you having just touch screen issues or are reboots part of the issue as well ??
#Root-Hack_Mod*Always\
laie1472 said:
Try calibrating your screen via display settings if you haven't already. Also are you having just touch screen issues or are reboots part of the issue as well ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
It's screen issues only, no reboot problems yet..
I have calibrated the G-Sensor several times...
In another post someone replied, that its a grounding issue, and trying that once it did give a result, but then again, I'm not having that, unusable level of the issue I was having, after a hard reset.. so I'm not really sure weather this is a grounding problem, an app caused problem, all I know is that I still get an extra touch input on the screen, when I approach the upper left corner.. with every multi touch app I test..
Have you tried that app called touch screen booster ??? If not give it a shot. Set the multi touch point settings to two. Then apply then start the service and select run at boot. Then reboot and see if it helps any. Also a way of trouble shooting to find out if it is a rogue app is to Uninstall all of your apps. Then see if you still have the issue.
#Root-Hack_Mod*Always\
laie1472 said:
Have you tried that app called touch screen booster ??? If not give it a shot. Set the multi touch point settings to two. Then apply then start the service and select run at boot. Then reboot and see if it helps any. Also a way of trouble shooting to find out if it is a rogue app is to Uninstall all of your apps. Then see if you still have the issue.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Yes i have, thanks to you, but it was futile. Had no impact what so ever...
It's handed in for repairs, so I'll know what it was soon..
G4m3rHead said:
Yes i have, thanks to you, but it was futile. Had no impact what so ever...
It's handed in for repairs, so I'll know what it was soon..
Click to expand...
Click to collapse
Bummer. Well at least you'll get it back fixed.
#Root-Hack_Mod*Always\
are you running any of the custom kernels? If I run why kennel besides stock I get the exact same behavior
Sent from my PG86100 using XDA
punkerEVO said:
are you running any of the custom kernels? If I run why kennel besides stock I get the exact same behavior
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
No i have not rooted, i was waiting for the official ICS before i root.
So I'm on the Stock... everything lol
This is my second 3D. The first one stopped responding to touches. Sprint replaced it for $30 even though I bought it from wirefly.
In my own experience, I had the exact same symptoms. Only difference is I didn't even drop my phone. After a few months of owning the phone it started to show the aforementioned symptoms occasionally. Eventually, it just got worse. After a lot of forum searching, google searching, etc, it turned out to be the digitizer that was faulty. I had tried everything from flashing different ROMs, Kernels etc before I was finally able to narrow it down to a hardware issue. The digitizer seems to be an issue for a lot of 3VOs from what I understand.
Luckily I had a friend who replaced the entire front housing of my phone so I wouldn't have to exchange it since I was unlocked on HBOOT 1.40. At the time I was afraid that, had I gotten it replaced, I'd have to deal with Hboot 1.50 and HTC's half ass unlock method. Either way, after that it was like a brand new phone but better cuz I didn't have to redownload apps, etc since the motherboard and software weren't touched at all.
Hope it all works out for ya... G'luck, brothah!
Sent from my PG86100 using XDA
Shame I hadn't seen this thread sooner, I could have saved you a lot of time. I am on my 3rd 3d. Basically any fall which lands on the touchscreen will cause this problem.
What makes it worse, I was rooted with my last phone, and when it happened, I had to unroot before I could take it in for repairs. The touchscreen was so badly damaged with this problem, I could hardly do anything.
TL;DR get a case that will cover the screen and protect it from flat on touchscreen falls.
having a problem with my touch screen. i've factory reset, wiped, and have even flashed a few different roms, i'm convinced the problem is with my phone and i'm hoping it's not broken. i turned on the touch indicator option and can see that sometimes when i wake my phone there is already input on the very center of my screen, almost where the Sense unlock ring would be. if i'm touching the edge of my screen and wake it happens a lot more often, and i was just playing with it and i'm able to make this occur by touching where the screen meets the bezel. anyone have any suggestions? it's really annoying, it'll open apps, unlock my phone, hang up calls, ect. thanks for any time in reading this and any suggestions you may have!
chrisosaur said:
having a problem with my touch screen. i've factory reset, wiped, and have even flashed a few different roms, i'm convinced the problem is with my phone and i'm hoping it's not broken. i turned on the touch indicator option and can see that sometimes when i wake my phone there is already input on the very center of my screen, almost where the Sense unlock ring would be. if i'm touching the edge of my screen and wake it happens a lot more often, and i was just playing with it and i'm able to make this occur by touching where the screen meets the bezel. anyone have any suggestions? it's really annoying, it'll open apps, unlock my phone, hang up calls, ect. thanks for any time in reading this and any suggestions you may have!
Click to expand...
Click to collapse
I had the same issue with my Samsung Gal ( the org) and ended up having to get it replaced at Verizon. But again i also had the issue on my DINC and that was just some dirt after taking it apart and cleaning everything was good to go...other then that it very well could be the screen
Just got a new Tab S7+, and I found that I was getting a heck of lot of repeating keys from the Samsung keyboard and the Gboard keyboard. Hadn't noticed any problems elsewhere.
I finally got fed up with it and get Touch Screen Test, and I can see clearly there that the screen is registering a touch with my finger maybe 0.5mm away from it. That fits with what I see on the keyboard, where I can get keys to fire with tiny finger movements just away from the screen.
I can't find any settings in Android 10 to adjust this. It's surprising for a table that's been out of the box a couple of weeks, and possibly it's worsening.
I had an idea after I'd posted this - I often use the tablet connected to the 25W charger that came with it. If I use it on battery, the problem is much diminished , and possibly gone. Electrical interference, then???
Is it a return-as-faulty, would you say? Any test options I can use to help with this?
Thanks
Alan
Latest update fix that issues
bicubic said:
Latest update fix that issues
Click to expand...
Click to collapse
Many thanks for that. My tablet has T970XXU1AT12 / T9700XM1AT12, no update showing as of a moment ago. I expect it will reach the UK soon and I will be able type!!
I think the touchscreen of this tablet does have some interesting behaviors, as I've also observed some touches being registered when my finger was a still a short distance away. I suspect this might have something to do with palm-related gestures (like palm swipe from right to left for screenshooting).
I play rhythm games on this tablet mostly, and I'm seeing some cases of taps not being registered properly (unexpected misses), which happened less often, when I was playing those same games on my phone (before migrating them to the tablet).
I don't constantly put the tablet on the charger, as I've lessons learned from my previous tablet, Pixel C, whose battery went swollen after having placed it constantly on the charger for quite a long while that I ended up replacing the swollen battery with a new one by myself. While it was a lot of effort in overall, but the swollen battery had made the glues between the screen and the chassis mostly visible, that removing the screen became much easier.
I couldn't confirm this issue.
I've installed a safety glas on top of the screen. Fingerprint and S Pen is working but I've no issue's with a to sensitive Display
Update came yesterday. Still not fixed
I'm also using a tempered glass screen protector and my personal experience with such protectors on different devices has always been positive, with few issues directly related to such protectors as long as the quality appears to be good enough. I don't connect the charger while gaming, but I do attach a Type-c audio cable for connecting the tablet to desktop speakers.
On the other hand, some lower quality charging cables would certainly cause issues with touchscreens regardless of device. Usually with stock chargers and cables (or those from very reputable vendors) you can mostly rule out this possibility.
EDIT 6: Moved the rest of the issues I'm having to a separate thread.
UPDATE 2: Sadly the situation has worsened during the period and the touchscreen loses responsiveness much more often that some games are virtually unplayable. I've moved the games back to my good old Pixel C. Although it's indeed ill-equipped to play some newer games (that they have very low framerate and could sometimes slow down to a near-frozen state, even on lowest detail settings), at least I've no issues with its touchscreen, just that games may get too low framerate to accurately register them on time.
Should point out that S-Pen is apparently not affected by this issue, even with GSI, because S-Pen is treated as a pointer device (with significantly higher sampling rate) and in most cases does not count as touchscreen taps but instead count as left-clicks (e.g. games that exclusively expects touchscreen taps rather than mouse clicks would not respond to S-Pen taps, which is intended). Because of this, whenever I have the issue in-game I always need to pull out the S-Pen to perform some actions, like opening up the ingame menu, or bring up the navbar and go back to home screen, as I usually would have difficulty doing it directly with fingers whenever that happens (usually needs 3-4 taps/swipes to actually get it register once, but with S-Pen it always worked on first try).
Maybe I indeed have a faulty hardware (it doesn't matter anymore now that I've voided my warranty), but the possibility that software issues are contributing to the problem remains high, so for now I have no other choice but to follow kernel and ROM development process for a while to see if there are possible fixes/mitigations. Given this experience, I'm considering looking for another Android tablet with similar features this year but I'm yet to see one (especially considering 120Hz), and of course, I most likely won't get another Samsung device for serious purposes from this point on.
EDIT: Guess this Reddit thread about Galaxy S20 FE is relevant as many issues mentioned there seem to match mine... so this might be an issue specific to Samsung in overall, not just this device.
UPDATE: I'm putting the original post inside a spoiler as the old stuffs were a bit messy and outdated. Most of the original post were written during Android 10 and things have changed quite a bit since then.
Simply put, the touchscreen of this tablet is a bit problematic which makes it not a good idea for serious gaming, though it doesn't seem to affect office/production use as much.
The cause is still unknown and I can't be sure if this is due to hardware or software, or a mix of both. Should point out that the issues persist after switching to a GSI, so the stock ROM is not entirely to blame.
Some ongoing issues:
1. Touches randomly fail to register, and with inconsistent response time (sometimes early or late than average).
2. Touchscreen occasionally stops responding, dropping or delaying a lot of taps. This has become worse since BUD2 as I started having longer periods, and now virtually no touches get registered when it happens. I wonder if this is a side effect of the ghost tap mitigations, as this becomes significantly worse since BUD2 while I hardly ever get any ghost taps since then.
3. Jittery scrolling. Apparently I'm having this issue for quite long. Bounces (a quick scroll in reverse direction) can happen in apps when releasing the finger after scrolling. In games, this bounce registers as an additional flick. Should note that this is actually an indicator of the problem. Whenever I start noticing additional flicks being registered, the actually problem (touchscreen losing nearly all responsiveness) will likely kick in after a while.
Some issues appeared to have been mitigated after FW upgrades:
1. Ghost taps during holds and swipes. This has become lessened since Android 11 and is mostly gone since BUD2.
2. Random auto taps at the edges of screen. Haven't gotten once since BUC1 but I can't be sure it's really gone away.
3. Touches may get registered prematurely (when finger is still a few millimeters away from the screen). This has become lessened since Android 11.
Spoiler: Original post (messy and may be outdated)
It seems the tablet's touchscreen has several issues that I cannot be sure whether the issue is hardware related, software related, or a mix of both. I've been following this thread, but it seems the issue I'm having is more than what the OP was having so I'm considering moving the questions here.
I'm currently experiencing a variety of issues with the touchscreen that, while not a major problem for normal use, can be a serious issue for some games where accurate taps matter. However, the issue is very hard to track as while the problem happened a bit too often inside games, I couldn't easily reproduce the issue outside those games on testing apps despite trying to mimic the original situation. Although the game itself might be having issues, I don't think it's likely as I've played some of them on my smartphone before migrating them to this tablet and I never had any significant issues back then.
The tablet currently has a a tempered glass screen protector installed, and I'm using the tablet with a Type-C audio cable to play its audio from my desktop speakers. (NOTE: S7/S7+ has limited accessories support, that for now, I can only either charge or connect the tablet to the speakers, but not both, as splitters aren't supported) The possibility of the audio cable can be mostly ruled out as I'm encountering those touch issues both with and without it.
The tablet underwent about 3-4 updates and is currently up-to-date. I don't think there were any difference in this among the versions.
Here's what I've found about my tablet's touchscreen:
(DISCLAIMER: I can't prove the reliability of the app used for testing, Multi Touch Test, so it's mostly a reference in case someone wants to try to reproduce. There are more apps that can be used for such testing.)
1. Touchscreen may sometimes not registering taps, or late. In some games this is observed as some taps missed, or registered late (a tap/hold being recognized by the game as much as ~1s later). However, I can't really reproduce this in the test app.
2. Touchscreen may register touches before the finger physically reaches the screen (about 1-2 mm). I'm not sure if static electricity can cause it and this might be considered a normal behavior, but personally I'm feeling the response range is still too long compared to other phones/tablets I have, that it's easier to accidentally tap something, or let something register too early.
3. A tap may be registered more than once. It appears to be easier to reproduce when doing multi touches, but it still happens in some games with fewer simultaneous taps. I managed to get 5 touch/hold events registered with the test app despite using only 4 fingers (4 real touches) sometimes. Although I know bad charger cables can cause this (as well as other erratic touch behaviors), in my case there were no chargers attached (since the port's already been used by the audio cable).
4. When holding and dragging, additional taps may be generated (it can be noticed in some games that have tap sounds for all taps, including invalid ones, as these additional "taps" can be heard). Again, this appears to be easier to reproduce when doing multi touches, as I'm able to occasionally get 5-6 touch events when dragging with only 4 fingers. The drag itself seems consistent, as I haven't observed any abrupt interruptions of valid dragging actions in-game and in other places.
UPDATE (2020.11.22): At one time I was able to reliably reproduce the problematic behavior at some specific regions with the Multi-Touch Test app. To be precise, with the tablet placed landscape (camera facing up), while holding the lower-right part of the screen with my right hand finger, holding and dragging the lower-left region with my left hand finger resulted in a ghosted, inconsistent 3rd tap near where my left hand finger was holding/dragging (matching the issue I'm currently having within some games). It seems for some reasons that particular region of the touchscreen is indeed oversensitive as I was also able to reliably reproduce issues 2/3 at that time. The issue mostly went away after powering the device off and cleaning the screen as I was not able to reproduce it afterwards. Not sure about my current protector's quality, but I might need to look for an option that's more sweat-resilent, as my hands tend to produce sweat over time and that used to cause some serious issues with touching.
5. While testing in the test app, The taps might be stuck if I also let finger pads touch the screen while holding it with fingertip, and it stayed there even after I released my hand and touched elsewhere. Make as many multi touch events might clear it. Not sure if this is a normal behavior (possibly related to palm-related interactions such as palm swipe to take screenshot), or is an error with the test app itself.
6. In rare cases, the touchscreen would stop responding to most of the taps which I suspect this might be hardware related as the issues occur at specific regions. I used to experience such issues with iPads before (4th gen and Pro 2015) which is why I decided to go on with Android-based ones. This issue is not consistent and would go away after a while so usually pausing and doing something else would work.
UPDATE(2020.12.13): I witnessed something interesting. When the tablet stops registering the taps, it might be due to it continuously generating ghost taps on some screen edges near the last few spots I previously touched, completely on its own (my hands weren't even near the tablet). The issue went away after reboot. I forgot to make a logcat as I was in a bit hurry... I'm currently on the November update, but the issue happened even before the updates. It doesn't frequently happen, though.
UPDATE: This is after using the tablet a bit more...
1. Having a screen protector may or may not affect touches, but usually should not be significant, unless the protector is of very poor quality. The market for such can be a bit messy, and quality varies even with the same product. A same protector might work very well for some, but not for others.
2. Under my current circumstances, my S7+ can at most reliably take 3 multi-touches, and sometimes 4 (despite the touchscren can register at most 10). Putting more multi-touches would gradually cause the touch sensor to err and become unable to register taps on time. (While I usually use at most my index and middle fingers, sometimes things can get too complicated that requires me to use my ring fingers as well, and that's when touch-related problems usually start to occur).
3. Although not that often, when the touchscreen started to err, touches might randomly get registered even with my finger hovering quite a few millimeters above the place I'm thinking about touching. I'm still looking for the reason why.
4. The effectiveness of Touchscreen Repair is still uncertain, but it seems to work to some extent to help mitigating issues. However, it doesn't appear to allow me to repeatedly calibrate the screen.
5. Forcing the tablet to run at 60Hz (Motion Smoothness: Standard) would mitigate touch issues with some games that can't really achieve 120fps with most effects turned on. Sadly, some games can be quite demanding even on this tablet's SoC. Some touch issues are more likely to reproduce when the system starts to stutter, so it may be a good idea to turn off some effects if feasible. Not sure if the overall performance can be improved with a custom kernel in the future.
I've had similar issues with mine, during game play - it starts off fine, then the screen starts to lag and many missed inputs... Had an update yesterday, but haven't tried it yet
cheetah2k said:
I've had similar issues with mine, during game play - it starts off fine, then the screen starts to lag and many missed inputs... Had an update yesterday, but haven't tried it yet
Click to expand...
Click to collapse
Not sure what might be causing the issues. While not really an issue for normal use, but in some games it can be really frustrating to find it so difficult to full combo even on lower difficulty levels such as Easy because at least one tap would fail to register correctly in almost every play.
In my cases, the tablet mainly lags/stutters when it throttles due to overheat (if played for a prolonged amount of time). There's really no easy fix for that issue as it's very normal for such beefy SoCs to reach high temperatures.
Honestly, the tablet is too bloated in terms of touchscreen-related features (like S-Pen and palm gestures). Not sure if the touchscreen sensitivity was adjusted to make sure these features work without major issues, which in turn can cause some side effects that only gamers would find them annoying. The touchscreen is indeed oversensitive as some other people have reported, that touches sometimes get registered too easily to the point that it sometimes results in undesired touches, such as being too early (registered before the finger actually landed), or ghosted (a touch appeared as two or more).
Back then I got myself a Pixel C that I flashed with custom ROMs since day one and I never had any issues like this. Although it started developing similar symptoms later on, it turned out to be caused by a swollen battery and the issues went away after replacing it.
Unlike that time, for S7+ I hardly ever had the charger plugged (only when I turned it off and when the battery is really getting low), and there are also no apparent signs of a potential battery issue developing as far as I can see.
EDIT: I'm yet to be able to get another update... but it seems with prolonged gameplay the tablet may become very hot and the touchscreen becomes completely erratic in-game despite the game itself might not be stuttering (and sometimes this would cost me dearly).
I suspect when the SoC overheats the throttle impaired the system's touchscreen recognition and the reason why I'm not able to reproduce every issue outside games is that the tablet would not be as hot as when in-game due to reduced load. Guess I need to look for a way to keep the tablet cool while playing... Once again, it the nature for such beefy SoC to overheat over time.
Bumping this myself as I discovered something.
It seems forcing the S7+ to 60fps (Display -> Motion Smoothness -> Standard) can significantly mitigate the repeated/ghosted taps issue, and varying improvements regarding other touchscreen issues. I cannot say the issue is completely gone this way as I still encounter it from time to time, but with the tablet running at 60fps these issues are significantly less frequent to happen.
Either some background services might be interfering, or that some games can't really handle 120fps with most effects turned on. Guess I might need to experiment on how to disable certain system apps/features that I don't use and can't be disabled normally from the App settings, to further reduce background resource consumption. Hope the pm shell commands can work even without root.
As for stuttering, if caused by the tablet being overheating badly, placing it on a laptop cooling pad (that has fans in it) might help reducing the device's temperature a little bit. Also, tablet covers may block the airflow and limit such method's effectiveness, but I'm worried that the tablet's body might be too slippery without an appropriate cover to maintain enough friction to prevent the tablet from moving while using it.
EDIT: It seems some apps could misbehave when tapping repeatedly somehow (for trying to quickly skip some result screens)... and taps would start registering late, as late as ~1s. It appears as when tapping on a button, at first nothing happens, about a second later the tap against the button gets registered and things would proceed. The problem usually goes away after restarting the app.
The tablet currently has a a tempered glass screen protector installed,
Sorry I did not read All you wrote, I have S7+5G with latest Nov Update.
Personally I would REMOVE the Screen protector, do not like them and they create UI problems, why do you think you need one?, are you rough with Tablet (or Phone), just clean class regularly, try it??
MyAndroids said:
The tablet currently has a a tempered glass screen protector installed,
Sorry I did not read All you wrote, I have S7+5G with latest Nov Update.
Personally I would REMOVE the Screen protector, do not like them and they create UI problems, why do you think you need one?, are you rough with Tablet (or Phone), just clean class regularly, try it??
Click to expand...
Click to collapse
I cannot rule out the screen protector might affect input, but personally the impact on input sensitivity/precision with tempered glass ones is not that significant. With this tablet I do regularly clean the screen. Nowadays I also use such protectors on my phone, and I hardly ever had any touch-related issues directly caused by screen protectors.
On the other hand, a long time ago I had an iPad Pro which started developing similar symptoms (missed taps, interrupted holds). Back then I had a PET screen protector installed on it, and because of that I removed the protector later on, thinking that might be the culprit, but the symptoms were still there, so the screen protector was NOT the real issue.
And honestly my fingers can indeed be a bit rough with tablet and phones that it's necessary to install a protector, or it'll leave some permanent marks after prolonged use (that when I clean the screen, the areas that I swiped most frequent during gaming would be visible).
EDIT: Not sure when did the November update come out. My device is still on October update and as of now no new updates are available.
EDIT 2: Will update the OP a bit.
EDIT 3: I think some Samsung stuffs is indeed interfering (or at least taking up precious resources) as I did a logcat and noticed something mentioning Game Manager (which I do not want to activate, but it doesn't appear to be disabled completely). Does anyone have a good list about what I can safely disable via adb?
LSS4181 said:
I cannot rule out the screen protector might affect input, but personally the impact on input sensitivity/precision with tempered glass ones is not that significant. With this tablet I do regularly clean the screen. Nowadays I also use such protectors on my phone, and I hardly ever had any touch-related issues directly caused by screen protectors.
On the other hand, a long time ago I had an iPad Pro which started developing similar symptoms (missed taps, interrupted holds). Back then I had a PET screen protector installed on it, and because of that I removed the protector later on, thinking that might be the culprit, but the symptoms were still there, so the screen protector was NOT the real issue.
And honestly my fingers can indeed be a bit rough with tablet and phones that it's necessary to install a protector, or it'll leave some permanent marks after prolonged use (that when I clean the screen, the areas that I swiped most frequent during gaming would be visible).
EDIT: Not sure when did the November update come out. My device is still on October update and as of now no new updates are available.
EDIT 2: Will update the OP a bit.
EDIT 3: I think some Samsung stuffs is indeed interfering (or at least taking up precious resources) as I did a logcat and noticed something mentioning Game Manager (which I do not want to activate, but it doesn't appear to be disabled completely). Does anyone have a good list about what I can safely disable via adb?
Click to expand...
Click to collapse
I can send you the list of what I have disabled on my Tab S4 with android 10. After many trials and errors nothing crashes. Well rules of survival crashes from time to time but I think it might be normal. I left the game mode. Feel free to get rid of it. I based my list on some galaxy S10 debloat threads if I remember correctly. There were some pretty detailed lists. Note that I'm not rooted. I have tried to root but there was more hassle than positive effects.
Ok I got an S7 plus 8/256. The hardware is a beast but the touch screen shows the exact same problems of the non plus version I had tried some weeks ago.
While playing rules of survival, sometimes the left thumb that controls the movement loses the touch and the character gets stuck. Since I play with a pair of triggers, sometimes the left trigger gets irresponsive and my weapon cannot shoot steadily. The right portion of the screen seems to be less affected by this kind of problems. I should flip the tablet and test the opposite side. I am using a glass screen protector. It might be affecting the touch performance, but I'm not entirely sure, since it has been applied without any bubble.
The option to disable unwanted touches is obviously disabled. I did not touch any of the other options about the long press timing or the other one that I cannot remember now.
I have tried a screen testing app and I did not see any ghost touches or other issues.
This is getting annoying. I have 3 weeks before I cannot send it back to Amazon. I bought it on the German warehouse.
Hi All, I have the exact same problem... have you found any solution or Samsung helped you?
nyersike said:
Hi All, I have the exact same problem... have you found any solution or Samsung helped you?
Click to expand...
Click to collapse
I've unlocked and rooted the device as I tried to look into the issue further so I can't really rely on Samsung anymore. I haven't really updated the thread since then as I've been busy and am trying to live on with the issue which I think it's just natural for touch screens to have issues and I really can't avoid such...
With Android 10 FW, the issue seems to be able to affect everywhere as I could witness them happening in home screen and in touch test apps. However, things become different with Android 11 that the issue seems to be constrained to the particular app/game and I could no longer reliably reproduce them outside, only in some rare cases.
Since the BUD2 upgrade, I noticed that the additional taps I used to have during swipe/flick actions mostly disappeared, indicating some form of mitigations. However, with BUD2 I had times where touchscreen stopped working almost completely. Nearly all taps were dropped during the period that I couldn't pause the game nor call out the navbar, until I held the power button that caused the game to lose focus (pausing it in the process), and then touchscreen works again. Either I have a faulty hardware, or at that particular moment there were no CPU cores handling the incoming touch inputs at all.
I'm still looking at what might be causing the issue, but the logcat is too bloated to read, and I still need time to understand the meaning of every line in the kernel dmesg I dumped while playing and experimenting.
In overall, the tablet's framerate is very unstable while playing. On games that limit themselves to 60fps regardless, the game feels janky despite the framerate shown on PerfMon stayed stable at 60. On the other hand, the same games looked very fluid on my SD845-powered Razer Phone 2. I'm starting to wonder, if SD845 is a perfect SOC1 example, and SD865+ being a perfect SOC2 example, for this testcase.
Although I have systemlessly removed GOS via Magisk, it doesn't seem to have it removed completely as there are some logcats coming from system_server mentioning about GOS (especially, a watchdog), just that it couldn't find the apk to reinstall/re-enable. Also, I noticed some kernel dmesg lines containing "Input Booster" talking about something like "Del Ib instance" and I wonder if it has anything to do with GOS (as GOS stuffs tend to call themselves Boosters, like Game Booster).
Still, I'm noticing something that might be affecting the system performance. One of the games I play on the tablet could normally manage to reach near 120fps in-game, but it falls to 30-40 fps ingame after the app loses focus (e.g. switching to home screen or to another app) for at least once. Setting Motion Smoothness to Standard (60Hz) in this case would only make matters worse as it further cut the framerate by half (that is, I have 30-40fps before setting to 60Hz, after that I only get about 10-20fps). It may be because of the game itself (that's based on Unity), but I'm not perfectly sure. For that particular game I need to force close it and run it again in order to make it able to reach 120fps in-game again.
I have used SmartPack to set the GPU on performance governor with power level set to 0, in order to actually keep it on 670MHz as otherwise it stayed on 305MHz most of the time which I suspected it might be the cause of the performance issues, but right now, I'm seeing little gain in video performance and I noticed that the GPU clock can still go down to 525MHz after a while, something which I don't think it should happen on performance governor.
LSS4181 said:
Not sure what might be causing the issues. While not really an issue for normal use, but in some games it can be really frustrating to find it so difficult to full combo even on lower difficulty levels such as Easy because at least one tap would fail to register correctly in almost every play.
In my cases, the tablet mainly lags/stutters when it throttles due to overheat (if played for a prolonged amount of time). There's really no easy fix for that issue as it's very normal for such beefy SoCs to reach high temperatures.
Honestly, the tablet is too bloated in terms of touchscreen-related features (like S-Pen and palm gestures). Not sure if the touchscreen sensitivity was adjusted to make sure these features work without major issues, which in turn can cause some side effects that only gamers would find them annoying. The touchscreen is indeed oversensitive as some other people have reported, that touches sometimes get registered too easily to the point that it sometimes results in undesired touches, such as being too early (registered before the finger actually landed), or ghosted (a touch appeared as two or more).
Back then I got myself a Pixel C that I flashed with custom ROMs since day one and I never had any issues like this. Although it started developing similar symptoms later on, it turned out to be caused by a swollen battery and the issues went away after replacing it.
Unlike that time, for S7+ I hardly ever had the charger plugged (only when I turned it off and when the battery is really getting low), and there are also no apparent signs of a potential battery issue developing as far as I can see.
EDIT: I'm yet to be able to get another update... but it seems with prolonged gameplay the tablet may become very hot and the touchscreen becomes completely erratic in-game despite the game itself might not be stuttering (and sometimes this would cost me dearly).
I suspect when the SoC overheats the throttle impaired the system's touchscreen recognition and the reason why I'm not able to reproduce every issue outside games is that the tablet would not be as hot as when in-game due to reduced load. Guess I need to look for a way to keep the tablet cool while playing... Once again, it the nature for such beefy SoC to overheat over time.
Click to expand...
Click to collapse
The touchscreen went unresponsive today again and I noticed these in the kernel dmesg... Actually, similar dmesg entries happen all the time while the device is running, I just took something that looks relevant.
[ 708.540205] IRQ 5: no longer affine to CPU6
[ 708.561407] fts_touch 4-0049: [sec_input][P] tID:0.1680 z:23 major:16 minor:13 loc:C.C tc:1 type:0 p:0 nlvl:1 maxS:134 hid:0
[ 708.561538] set_freq_limit: id(1) freq(1401600)
[ 708.561548] cpufreq_limit_get: touch min same values(1401600,0) entered. just return.
[ 708.618420] fts_touch 4-0049: [sec_input][R] tID:0 loc:C.C dd:-7,1 mc:6 tc:0 p:0 nlvl:1 maxS:137 hid:0
[ 708.692113] set_freq_limit: id(1) freq(1401600)
[ 708.692130] cpufreq_limit_get: touch min same values(1401600,0) entered. just return.
[ 708.832303] [Input Booster] Release Timeout Func :::: 71's TV No Exist(1)
[ 708.832380] [Input Booster] Release Timeout Func :::: 71's TV No Exist(3)
[ 708.832399] set_freq_limit: id(1) freq(1401600)
[ 708.832412] cpufreq_limit_get: touch min same values(1401600,0) entered. just return.
[ 708.832479] [Input Booster] Del Ib Instance's Id : 71
[ 708.860192] IRQ 5: no longer affine to CPU7
I've set my CPU governors to ondemand and set a much higher minimum clock just because it tends to underclock, yet from the dmesg it's still trying to underclock to a value lower than that.
Also, I noticed several "Release Timeout Func" entries that seems to match the moments when touchscreen stopped responding to almost anything. Again, I don't know what this "Input Booster" really is. It's still hard to determine what exactly happened, though.
Tablet have some serious display problems.
I have sent mine already third time to repair and having same issue all the time.
First time they changed display on it, second time apparently couldn't find any issues. Now i send it third time and waiting to see what's going to happen.
ahaznada said:
Tablet have some serious display problems.
I have sent mine already third time to repair and having same issue all the time.
First time they changed display on it, second time apparently couldn't find any issues. Now i send it third time and waiting to see what's going to happen.
Click to expand...
Click to collapse
Just saw your video. It seems your issue is much worse and more consistent than the ones I'm having.
I don't know if the game engines can also be related, as one of my games uses Unity and the issues happened there most of the times. In other games the issues are less often but still present.
From the looks of it, despite its specs the tablet is not really meant to be used for serious gaming. The SOC might be good, but the touchscreen hardware certainly isn't.
I guess one is supposed to be using S-Pen most of the time for some office/production activities. From what I tested on GSI, S-Pen is considered a pointer device with significantly higher sampling rate. When testing using Touch Screen Benchmark app, with my finger I get 120 touch points per second, but with S-Pen I get about 360 touch points per second.
I'm not sure what Samsung might do to test/repair the touchscreen but I certainly can't ask them anymore, as my warranty is already void (0x1).
LSS4181 said:
Just saw your video. It seems your issue is much worse and more consistent than the ones I'm having.
I don't know if the game engines can also be related, as one of my games uses Unity and the issues happened there most of the times. In other games the issues are less often but still present.
From the looks of it, despite its specs the tablet is not really meant to be used for serious gaming. The SOC might be good, but the touchscreen hardware certainly isn't.
I guess one is supposed to be using S-Pen most of the time for some office/production activities. From what I tested on GSI, S-Pen is considered a pointer device with significantly higher sampling rate. When testing using Touch Screen Benchmark app, with my finger I get 120 touch points per second, but with S-Pen I get about 360 touch points per second.
I'm not sure what Samsung might do to test/repair the touchscreen but I certainly can't ask them anymore, as my warranty is already void (0x1).
Click to expand...
Click to collapse
I have same issues on all apps not just games like internet browsers, play store even on home screen
ahaznada said:
I have same issues on all apps not just games like internet browsers, play store even on home screen
Click to expand...
Click to collapse
On Android 10 I used to have similar situations that when it happens, I would still be affected by it even after switching out the game. On Android 11 it seems to mostly affect the particular game and would mostly go away when I switch back to home screen. I usually would test if the issue's still there in the Touchscreen Benchmark app, but in most cases I couldn't reproduce it there (mainly the Sensitivity test). Of at least 40 test attempts, I only managed to record actual interruptions once, plus a few actual delays (a few missed areas near the beginning).
On the other hand, actually Android does differentiate between touchscreen taps and "mouse" clicks. S-Pen taps are considered "left clicks" and would not work on games I play (just tested it and found out), although games usually do allow such "left clicks" to function in other places like menus. This is how it behaves in GSIs. Maybe it behaves differently in stock ROM but I didn't pay too much attention.
But in overall the tablet's touch response time is not stable. I get much more inconsistent numbers when calibrating touch timings in some games, compared to my phone and my old tablet, Pixel C.
Sadly the issues persist even after I switched to a GSI (it made no noticeable difference). I'm starting to wonder if there really is something wrong with the hardware, though I couldn't really find any really helpful info from logcats and kernel dmesgs that could point out the real cause. Again, RMA is not an option as my warranty has already been voided at this point.
Not sure that all S7+ have this issue or only a few people have this issue, but mine has that issue too.
I purchased the S7+ to use as a second monitor, so didn't notice earlier.
2 months later, I started playing a driving game. While playing the game, suddenly 3" whole left side touchscreen is not responding. After 1~2 seconds, it comes back to normal. And then suddenly it stops for 1~2 seconds and then comes back to normal, repeat.
I flipped the table and played the same game. Then, the right side is the problem. Yeah, as other people also have the issue on the left side, the S7+ really has an issue on the left side.
I installed a tempered glass screen protector and Poetic Revolution case. When I play 10 matches with the screen protector and case, the touch screen issue occurred 2~4 times. Without the screen protector and case, the touch screen issue occurred 0~2 times. Much better, but can't say it is normal.
When I play the same game using my Essential Phone[PH-1], it doesn't have the issue.
I purchased the S7+ three months ago, so claimed a warranty. Not sure Samsung can fix this issue or return without fixing it or fixed it but made more issues. Let's see.
I have same issues on all apps not just games like internet browsers, play store even on home screen
Yachoparis said:
I have same issues on all apps not just games like internet browsers, play store even on home screen
Click to expand...
Click to collapse
Yeah, it doesn't just affect games. It's just some games show symptoms easier than others, probably due to load or maybe optimization-related reasons. Also, in one of the games, I started to feel noticeable touch lags which I didn't notice before (not sure which side caused the issue).
With GSI, it seems touchscreen may not be responsive at startup, that sometimes I have difficulty drawing my lockscreen pattern correctly until the system stabilizes a bit.
I don't know if there are any prebuilt binaries for the `frameworks/base/tests/TouchLatency` test (mentioned here) available, so I can further examine if the issue I'm having is hardware or software related.
Maybe the issue is a mixture of both, as one time, when I had the issue in game I was able to pause the game just fine with my S-Pen (technically on GSI, S-Pen taps are considered left-clicks instead of touchscreen taps so it probably was not affected). I can't be 100% certain, though.
EDIT: Today I had a time when the touch screen stopped responding to anything. I tried bringing up the navbar but was not successful, then I pulled out the S-Pen and was able to bring up the navbar and switch back to home screen without any issue.
Looks like the touchscreen part of this Samsung hardware is really flawed. This doesn't necessarily affect S-Pen as it's being processed differently from normal touches.
Additionally, I noticed that if I hover the S-Pen on the screen (the mouse pointer visible), touchscreen taps may not function correctly in some circumstances (despite they are registered, as the buttons tapped did respond). This seems to be more app-specific and not necessarily an issue with the hardware.
I have the same. New tablet, updated to android 11.
Today I had a time when the touch screen stopped responding to anything.
Ja pierdole....
background: came from Pixel 3 XL and numerous other Nexus/Pixel devices. running latest update stock w/ root
NEVER HAD THIS ISSUE on a prior device. Is it *my* phone malfunctioning? Are you experiencing this?
Issue: multiple times a day, I will go to tap some element in an app, whether it be discord, or tiktok, or otherwise, and instead of registering me tapping the button sized element, the phone recognizes my touch as a swipe up, and minimizes the app, sending me to the homescreen. The minimize gboard v button is a HUGE offender here. So many times does tapping it minimize the entire app instead of the keyboard.
Now you might think I am simply accidentally using more of a swipe gesture than I realize when I go to tap but I assure you nothing has changed in a decade+ of how I use android touchscreens. Frequently I have repeated the exact motion I just did to cause the unwanted behaviour (a stab / tap), and can't even reproduce the mistake unless I made a very pointed effort to do the actual swiping gesture that would produce it (a distinct swipe up instead of a single tap).
Something is different about this phone's hardware or software. The bottom ~1/6th of the screen is crazy sensitive in a bad way, or touches in that area are bugged under certain frequent conditions. It somewhat feels like it's the first tap in that area after some time has passed or X number of taps on other area of the screen has crossed a threshold; the next one is registered as a swipe, then soon after taps are ok, for a bit...
It's driving me crazy, happening reliably throughout any period of sustained use. I am aware of the settings function to minimize the size of the SIDE touch sensitivity areas, but there's no such thing for the bottom as far as I can see. I want it to be a tiny thin line like I made my side areas.
There may be related unwanted touch/gesture behaviours, like taps in that bottom 1/6th registered as app switching (left / right swipes), or taps in that area not registering as anything(?), but I'm focusing on the most understandable and repeated one I can identify.
Anyone else? Help? It's so bad.
It may be the case and the way you are holding the phone.
In any case. Look for an app called Edge Block by flar. It can be set up to stop edge touches.
I'm holding it the same way I've held every phone.
Also, to be clear, these aren't what I would call edge touches. But maybe that app will fix it regardless.
@deusfaux Did you ever think this is an RMA situation since this has not been widely reported? You ask if it's just your phone and I suggest that it very well might be. Get yourself a replacement device, they're pretty good. But it also depends on your situation, location, place of purchase etc. Good luck.
bobby janow said:
@deusfaux Did you ever think this is an RMA situation since this has not been widely reported? You ask if it's just your phone and I suggest that it very well might be. Get yourself a replacement device, they're pretty good. But it also depends on your situation, location, place of purchase etc. Good luck.
Click to expand...
Click to collapse
Well that's what this thread is here to help me ascertain. If nobody is giving me the 'me too' then talking to Google is a likely next step
deusfaux said:
Well that's what this thread is here to help me ascertain. If nobody is giving me the 'me too' then talking to Google is a likely next step
Click to expand...
Click to collapse
I'm sure you'll get a couple of me too but not enough to declare it a Pixel 6 issue in general. The phone has been out since October and nary a situation exactly like yours. I suspect that is enough to ascertain you have a faulty device.
If it's software related then it could be part of a recent update or something else I've done to my phone. I'm not narrowing my suspicion to hardware alone at this point.
I can say that I have experienced something like this, as well as occasional non responsive touches. These experiences are intermittent and I have chalked them up to user error at times, but definitely appears to be an issue with touch sensors at times. Just my humblest opinion from my experience.
deusfaux said:
If it's software related then it could be part of a recent update or something else I've done to my phone. I'm not narrowing my suspicion to hardware alone at this point.
Click to expand...
Click to collapse
That's a horse of a different color. What did you do to your phone that distinguishes it from every other? If it was a software update then everyone would be experiencing what you are. That is not the case.
phaino00 said:
I can say that I have experienced something like this, as well as occasional non responsive touches. These experiences are intermittent and I have chalked them up to user error at times, but definitely appears to be an issue with touch sensors at times. Just my humblest opinion from my experience.
Click to expand...
Click to collapse
Different issue than the OP. I get that too once in a while and have been since early Pixels and maybe even the Nexus, although I can't remember that far back. lol But my P5 all the way back to the P3 or the P3a had that IIRC.
deusfaux said:
background: came from Pixel 3 XL and numerous other Nexus/Pixel devices. running latest update stock w/ root
NEVER HAD THIS ISSUE on a prior device. Is it *my* phone malfunctioning? Are you experiencing this?
Issue: multiple times a day, I will go to tap some element in an app, whether it be discord, or tiktok, or otherwise, and instead of registering me tapping the button sized element, the phone recognizes my touch as a swipe up, and minimizes the app, sending me to the homescreen. The minimize gboard v button is a HUGE offender here. So many times does tapping it minimize the entire app instead of the keyboard.
Now you might think I am simply accidentally using more of a swipe gesture than I realize when I go to tap but I assure you nothing has changed in a decade+ of how I use android touchscreens. Frequently I have repeated the exact motion I just did to cause the unwanted behaviour (a stab / tap), and can't even reproduce the mistake unless I made a very pointed effort to do the actual swiping gesture that would produce it (a distinct swipe up instead of a single tap).
Something is different about this phone's hardware or software. The bottom ~1/6th of the screen is crazy sensitive in a bad way, or touches in that area are bugged under certain frequent conditions. It somewhat feels like it's the first tap in that area after some time has passed or X number of taps on other area of the screen has crossed a threshold; the next one is registered as a swipe, then soon after taps are ok, for a bit...
It's driving me crazy, happening reliably throughout any period of sustained use. I am aware of the settings function to minimize the size of the SIDE touch sensitivity areas, but there's no such thing for the bottom as far as I can see. I want it to be a tiny thin line like I made my side areas.
There may be related unwanted touch/gesture behaviours, like taps in that bottom 1/6th registered as app switching (left / right swipes), or taps in that area not registering as anything(?), but I'm focusing on the most understandable and repeated one I can identify.
Anyone else? Help? It's so bad.
Click to expand...
Click to collapse
Not sure if it will help, but may want to try this. Settings>Accessibility>Timing Controls>Touch & Hold Delay>change to medium