Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
yanouch said:
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
Click to expand...
Click to collapse
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
xbad1 said:
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
Click to expand...
Click to collapse
Yeah that's what i expected but wanted just to know if others had the same problem and if there was already a workaround for this
Many people have this problem, including a number of reviewers.
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
The customer is left in the cold!
Some people have a return policy - what if one waits for a software update, the return period expires, the update comes, but it doesn't fix the problem and it turns out to be a hardware problem??
The information politics of Sony and other companies (yes, Google, you too!) is an absolute PILE OF S**T!!
Yup, me too. The annoying thing it is difficult to document. Yesterday my tablet was charging and I turned the screen on using power button - lock screen didn't react at all to my inputs. Tried switching screen on/off a few times but it didn't help. Also tried double-tap to wake with no success. Went to get my camera to document, then of course it started working...
I've written this elsewhere, but this is how I notice the touch screen problems:
For me the tablet randomly doesn't recognize touches during the below instances. In all cases either going to the home screen and relaunching the app or turning the screen off/on will solve the problem. The problems occur several times per day but not constantly.
Sometimes opening apps will cause everything but the bottom android-buttons to be non-responsive. This can happen in any app it seems, including native ones such as Google Play.
Sometimes the lockscreen doesn't recognize touches at all.
While charging I've had issues getting the touchscreen to recognize touches, disconnecting the charger has helped.
Double-tap to wake seems to be very moody, sometimes working sometimes not. Sometimes it turns the screen on even by me just holding the tablet with my palm resting against the screen.
While not a bug per se, also the android-buttons seem very picky that you have to hit them right on the spot to work.
Other threads on same topic:
http://talk.sonymobile.com/t5/Xperia-Z2-Tablet/Touch-screen-problem/m-p/620325
http://community.sony.fi/t5/Tablets/Xperia-Z2-tablet-touch-screen-issue/td-p/1582051
http://www.android-hilfe.de/sony-xp...screen-reagiert-nicht-immer-zuverlaessig.html
Damn ! i'm not alone....
One forumer said he thinks that switching OFF Stamina mode helped a little bit...
I don't have my tablet with me, can someone test this ?
"A little bit" help is NOT enough.
The touchscreen MUST work perfectly, whether with Stamina Mode on or off or whether with Mode XY on or off. No discussion.
Sony HAS to fix this.
Already solved in .55 firmware
hasenbein1966 said:
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
Click to expand...
Click to collapse
The same experience with Z1 compact and support. Told them the camera is really broken - they told me there is absolutely nothing wrong with the camera and I'm the first one who got this problem. That was some weeks before, now they officialy added that maybe some devices are defect.
But that´s Sony, they give a **** about u, don't even try to contact the support.
I'm also having this issue, if I'm using the Sony sleve it's impossible to use the touchscreen as it will tip over when I press hard enoug for the screen to actually register it.
No problem here.
Only early days yet. The only prob I've got atm is Dropbox isn't showing up in the Album.
Edit: Fixed the Dropbox problem by using the Dropsync app.
I also seem to get this. The tablet works fine when tilted at an angle but for some reason can be completely unresponsive when it's laid flat. Would this suggest a hardware issue or a software bug?
I also get this, sometimes it's like I just need to press harder (so hard the tablet falls over when using the cover as a stand), but other times it seems that no matter how hard I press or how many fingers I apply it doesn't register a thing for periods at a time.
I'm lead to believe that this is either software or firmware considering the intermittent nature. Are there any custom ROMs out yet that we could flash to eliminate the software aspect?
I have same problem, most noticeable in Chrome, switching tabs fails to register 10% of time. I can only think Sony have a hardware quality control issue with the digitizer as if it was firmware related, surely everyone would be suffering. Strange none of the reviews have picked this up, but I'm going to have to return mine.
No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.
Interesting theory, just gave it a go, inclusive, but does seem worse in case. However if Sony aware, why have they not rushed out firmware as otherwise initial user experience is ruined.
QUOTE=hasenbein1966;52005720]No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.[/QUOTE]
POTENTIAL FIX FOUND (ROOTED ONLY)!
Rooted users can try this fix, works for me! Touch seems to work perfectly now, also when tablet not in hands and lying on non-conducting surface!
Edit the file
/system/usr/idc/clearpad.idc
and alter these two lines:
Code:
touch.pressure.scale = 0.0001
(original value: 0.1)
and
Code:
touch.filter.level = 1
(original value: 2)
Don't forget a nandroid before
Please report whether it helped! :good:
P.S.: just for the curious - on the first Tablet Z, the two values are also lower: touch.pressure.scale is 0.0074, and touch.filter.level is also only 1.
Thanks for suggestion but dont wish to root (I use it to watch Sky which wont work if rooted) - seems there is more assistance on this forum to the issue than from Sony. I'll give it another week for a firmware fix before returning it.
elaborate...
nos1609 said:
Already solved in .55 firmware
Click to expand...
Click to collapse
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
---------- Post added at 09:17 PM ---------- Previous post was at 09:11 PM ----------
homme_fromage said:
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
Click to expand...
Click to collapse
My bad, didn't read all the way through, ignore me.
Now after a few days I can say:
With the root fix described above, my tablet works like butter. Simply perfect. :good:
Only instance where I have still problems is when the tablet was lying around for a while and I try to operate the touchscreen without taking it in my hands. Then sometimes (not always) the screen doesn't react, but only for a short time.
The problem seems to be related to static electricity.
So some of you with white Z5 compact phones might have had this touch sceen bug with repetitive key presses and unstable touch screen behaviour bug which was previously "fixed" by a software upgrade:
http://www.xperiablog.net/2015/10/21/white-xperia-z5-compact-touch-screen-fix-arriving-next-week/
Lo and behold. This bug is back in MM, and there is another guy in the thread which I can see also have the bug come back
It is not always there, but sometimes its just there. I dont know what triggers it. A restart seems to help until it comes back again.
For those of you not familiar with this bug, it usually shows by repetitive touches, and highly unstable touch screen.
For example when i press the key "s", it usually put in "sssssss" like i have pushed that key 5-6 times.
Also the bugs shows, when for example you are scrolling in facebook/internet, it will not let you scroll. Whenever you touch the screen, it will enter, whereever you lay your finger on screen.
Lastly it also shows by the screen becoming completely unresponsive when you press anywhere.
I have clean installed MM and restored my apps via Sony Backup/restore app.
I am so pissed how a phone color (white) can somehow decide the behavior of the phone touch screen, and I believe sony is hiding something.
In the beginning I was thinking that maybe they made different builds for the different Z5 colors, so they might not have included the "newest" touch screen drivers for at launch time for the white version.
But the same bug appearing AGAIN in MM i have a very hard time understanding that should be the case that it was a software bug. I believe there are some hardware bug, they have somehow omitted by a software circumvention, and they forgot to add it to the white version for the MM launch.
Personally I have always had a problem with the "return" key when the phone is placed. Patch or not, this button works once out of 10.
For information, I just bought this phone. I also think there is a hardware problem. This is average for a manufacturer like Sony. I thought for a moment it back in service but when I see the number of dissatisfied with the service Sony in France, I preferred to keep my phone in the hope that a solution comes a day. We have the right to expect in my opinion ...
I did clean install via flastool also and i have/had this problem. Yesterday i did software repair via pc companion and restores apps after that and so far problem has not occured.
I also made a repair with PC Companion but nothing changed.
So there are other people here with this annoying problem.
You all have a white xperia yes?
This bug is so annoying I feel sometimes like tossing the phone into a wall.
If there was an alternative to this phone in this form factor and specs, I would have bought it yesterday.
But unfortunately there isn't
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
hipsterfont said:
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
Click to expand...
Click to collapse
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
I also have Sony Z5 compact white version which had the touch problem from start. Now after the Marshmallow update its back. As said above, it could happen while browsing (or on home screen) e.g. Entering links instead of scolling i.e. It triggers multi click. In these situations all menu keys will also be none responsive. Its starts acting normal again after a quick push of the power button, i.e. puttning the screen to sleep.
As a former developer for mobile software, both for apps and the android platform, i thinking i would agree with the above conclusion that the problem is hardware based, and not due to a difference in the delivery software version, as i was hopping. So the question is; will this always be a problem for these versions of Z5c white, i.e. they are forgotten in new builds?
Unfortunately I'm having the same problem with my white z5 compact...
mcmanuf said:
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
Click to expand...
Click to collapse
it happens that for different colors are used different materials.. probably white ones have different properties..
i can confirm that using bad cable/chargers this kind of bug happens with every device, with random touches and impossible scrolling.. if you have a well-known bad adapter and you note no differences with your white z5c, that's definitively the answer..
i think sony should recall all white z5cs and replace them with newer or different release
What revision of compact Z5 are you? Personally I have a revision 3 (that is written on the box).
I also had a touch of problem before moving to the latest version of Android (6).
My girlfriend also bought white Z5 Compact and funny thing... I put the Panzer Glass on the screen and guess what? Sometimes she can't turn off the alarm clock in the morning and sometimes navigation buttons are not responding. I tried then without the screen and it works without a problem. I am not sure if this is a problem with Panzer glass or sony's bug.
I have Z5 and have no problems, but mine is black edition
Mine is z5c white version as well. The bug started again on MM
And the bug quite annoying.
I bought it on updated lollipop.
And never had this problem before.
This plus Bluetooth is really making me hold off on not moving up from .200 lol
Argh - just saw the visual representation of this bug:
http://www.xperiablog.net/2015/10/06/xperia-z5-compact-owners-reporting-touch-screen-problems/
and it sounds A LOT like the one from the OnePlus One (driver & firmware issue)
easy blame: Synaptics - fix your ****
Anyway:
try enabling the double-tap-to-wake if it's not already enabled, lock the screen - give it some time to settle (~ 30 seconds),
wake it up (double-tap) - do some stuff - disable the double-tap-to-wake and lock the screen again.
Unlock it via power button and see if that improved the "situation".
Sony recommended a few times to boot into Safe Mode,
does this Mode exist on Android Marshmallow ?
Does it make any change ?
Had this in Nougat is there a fix?
It feels like a software problem! You can try to reinstall the system!
First consider whether it is a system problem. You can refresh the system to see if it is back to normal. If it still does not, then you may need to update a new LCD screen. You can go online to find the repaired video as a reference. The witrigs repair video is doing great, you can check it out!
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....