Related
Hi Guys,
Recently reverted back to Android from iOS. I have had low end and mid range Android devices for development purposes as well as a Windows Phone devices all the way through.
Since taking up the HTC M8 as my day to day device, I have been noticing issues (teeth grindingly frustrating issues) regarding touch screen accuracy and responsiveness.
A prime example of this is when using a browser (Any browser, on both GPE and Sense editions). When making a pinch to zoom gestures, my fingers can move almost half an inch apart before the actual zoom process begins. I have tested this on a Samsung GS4 and found this not to be the case on that device. I believe the root cause of this problem is also behind the poor accuracy when typing on *any* keyboard (i find myself re-writing words again and again despite the larger screen size, you'd expect larger on screen keys would equal less frequent miss stokes...). Again this is not the case on the GS4.
I have used a multitouch testing tool to gauge some measure of response time and touch latency. I have found when moving points at any rate of velocity they begin to lag quite substantially behind my finger. I don't know if this is part of the same problem.
I am wondering if anyone could shed light on whether this is an issue with display touch sensitivity settings, something which could be changed at the kernel level or a limitation with the hardware itself,
Is it also possible that the same algorithm used to detect and handle touch for devices with smaller screen real estate is still being used and that the distances and tolerances for touch and gesture recognition are acting proportionally to the screen size.
Hopefully this is something we can fix, it makes the device tiresome to type with and feel clunky and unresponsive.
The screen on this phone has a higher touch response then the iPhone
Sent from my HTC One_M8 using Tapatalk
Go in a store and check out another phone. If yours turns out to be defective (which should be the case), you should get it replaced
Sent from my iPod touch using Tapatalk
No issues with mine.it's better than iPhone5s I had. Which had some issues sensing touch on corners of display
Sent from my HTC One_M8 using xda app-developers app
sabianadmin said:
Hi Guys,
Recently reverted back to Android from iOS. I have had low end and mid range Android devices for development purposes as well as a Windows Phone devices all the way through.
Since taking up the HTC M8 as my day to day device, I have been noticing issues (teeth grindingly frustrating issues) regarding touch screen accuracy and responsiveness.
A prime example of this is when using a browser (Any browser, on both GPE and Sense editions). When making a pinch to zoom gestures, my fingers can move almost half an inch apart before the actual zoom process begins. I have tested this on a Samsung GS4 and found this not to be the case on that device. I believe the root cause of this problem is also behind the poor accuracy when typing on *any* keyboard (i find myself re-writing words again and again despite the larger screen size, you'd expect larger on screen keys would equal less frequent miss stokes...). Again this is not the case on the GS4.
I have used a multitouch testing tool to gauge some measure of response time and touch latency. I have found when moving points at any rate of velocity they begin to lag quite substantially behind my finger. I don't know if this is part of the same problem.
I am wondering if anyone could shed light on whether this is an issue with display touch sensitivity settings, something which could be changed at the kernel level or a limitation with the hardware itself,
Is it also possible that the same algorithm used to detect to handle touch for devices with smaller screen real estate is still being used and that the distances and tolerances for touch and gesture recognition are acting proportionally to the screen size.
Hopefully this is something we can fix, it makes the device tiresome to type with and feel clunky and unresponsive.
Click to expand...
Click to collapse
If you have just moved from the iPhone, then this is a slight orientation problem ... and actually the M8 is the nearest you can get in terms of responsiveness to an iPhone, thanks to the fastest screen response time on the market ... for keyboard, you need to deliberately slow your finger speed down for few days and then you get used to it ... Screen/phone size also play a part in your typing because your mind can remember sub-consciously how much finger movement to do for typing ..
All the above is assuming you were an avid typist for long time on an iPhone
v-b-n said:
If you have just moved from the iPhone, then this is a slight orientation problem ... and actually the M8 is the nearest you can get in terms of responsiveness to an iPhone, thanks to the fastest screen response time on the market ... for keyboard, you need to deliberately slow your finger speed down for few days and then you get used to it ... Screen/phone size also play a part in your typing because your mind can remember sub-consciously how much finger movement to do for typing ..
All the above is assuming you were an avid typist for long time on an iPhone
Click to expand...
Click to collapse
Thanks for all the replies, it is likely that its a transitional issue alright. But before i write it off as such, can anyone verify the issues regarding pinch to zoom? Just trying to figure out if it is a faulty device i have on my hands or not
I get the exactly the same issues. I really thought it was me .
However I had the HTC One M7 and had no issue whatsoever.
LG G2 also same no issues .But since getting
HTC One M8, the touch accuracy is well absolutely useless. I am forever correcting what I type.
I don't think its the hardware but something to do with the Algorithm..No matter what keyboard you use or calibration you do. doesn't make any difference
I am hoping that lollipop cures this problem..
My touch accuracy has always been great. I'd say that if yours isn't it's a hardware problem.
Lostatsea23 said:
The screen on this phone has a higher touch response then the iPhone
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I tried the m8 and iphone 6 instore and compared them. The m8 screen is very sensitive, requiring minimal touch to be activated. This may be why tests are showing that the m8 has a faster touch response. However, when dragging your finger along the screen, such as swiping launcher screens, the iphone is more responsive.
I then tested "show touches" on the m8, the touch lags behind my finger.
Bought this big boy on July over Lenovo MotoG4 Plus. Seems to be a fruitful decision. Here, down below are some of my doubts for which I have been unable to decipher the solution( I definitely have given xda and Internet a search)
This maybe something like that of a personal understanding but since I ain't so deep in modding stuff, I would be needing a simple answer.
1) Since a locked bootloader doesn't allow for any custom recovery to run on the stock firmware memory, does the flashing of TWRP through locked bootloader (Doom Slayer's method) also unlocks the BL in the process? Since I could properly use the CM13 and 14 ROMs
2) Is there any possible way to make MIUI Camera work on any CyanogenMod/Base ROM? Please link to any existing thread if available.
3) Could mpdecision hotplugging driver be supported by Hydrogen? It does on Helium but not on Kenzo
4) Since Quick Charge worked even for earliest ported/non-sourced builds of CyanogenMod (by Annabathina) can it be made available for MIUI ROMs too which do not support it until now
5) This is not actually a doubt just a question regarding the build strength and durability, how many people have dropped your Mi Maxes(the size definitely makes it hard to handle) Mention only the serious consequences incurred. And Thumbs up for the guys having zero falls.
That was all guys. Thank You
1)no installing twrp wont unlock ur bootloader.the only way to unlock bootloader is by using the official miunlocktool,while running a developer miui rom(chinese/global doesnt matter)
2)no,altleast that i know of.cm camera is more configurable anyway
3)im not a dev,but atleast frm ongoing discussions, its still under development. im sure it will be in future.
4)it works atleast according to this thread anyway. http://forum.xda-developers.com/mi-max/how-to/xiaomi-mi-max-quick-charging-3-0-t3439563
5)i dropped my phone face first frm a height of abt 2ft or abt 80cm.just a small separation btw the front & back panels which was solved by applying slight pressure and panels snapped back into place.as far as i know max damage occurs when the point of impact is at the corners.
wingryder said:
1)no installing twrp wont unlock ur bootloader.the only way to unlock bootloader is by using the official miunlocktool,while running a developer miui rom(chinese/global doesnt matter)
2)no,altleast that i know of.cm camera is more configurable anyway
3)im not a dev,but atleast frm ongoing discussions, its still under development. im sure it will be in future.
4)it works atleast according to this thread anyway. http://forum.xda-developers.com/mi-max/how-to/xiaomi-mi-max-quick-charging-3-0-t3439563
5)i dropped my phone face first frm a height of abt 2ft or abt 80cm.just a small separation btw the front & back panels which was solved by applying slight pressure and panels snapped back into place.as far as i know max damage occurs when the point of impact is at the corners.
Click to expand...
Click to collapse
Thanks for answers 1 and 5. Would like a thorough answer for the rest from any Dev maybe
My hydrogen is still on a locked bootloader but I managed to flash TWRP using MiFlash and I'm now running Resurrection Remix.
As for drops... Don't. It's a big phone with a big glass surface up front. I have a soft plastic case that makes the phone more grippy and provides some impact protection. I wouldn't use it without a case because of the slippery metal back, especially if you have oily hands.
techy97 said:
Bought this big boy on July over Lenovo MotoG4 Plus. Seems to be a fruitful decision. Here, down below are some of my doubts for which I have been unable to decipher the solution( I definitely have given xda and Internet a search)
This maybe something like that of a personal understanding but since I ain't so deep in modding stuff, I would be needing a simple answer.
1) Since a locked bootloader doesn't allow for any custom recovery to run on the stock firmware memory, does the flashing of TWRP through locked bootloader (Doom Slayer's method) also unlocks the BL in the process? Since I could properly use the CM13 and 14 ROMs
2) Is there any possible way to make MIUI Camera work on any CyanogenMod/Base ROM? Please link to any existing thread if available.
3) Could mpdecision hotplugging driver be supported by Hydrogen? It does on Helium but not on Kenzo
4) Since Quick Charge worked even for earliest ported/non-sourced builds of CyanogenMod (by Annabathina) can it be made available for MIUI ROMs too which do not support it until now
5) This is not actually a doubt just a question regarding the build strength and durability, how many people have dropped your Mi Maxes(the size definitely makes it hard to handle) Mention only the serious consequences incurred. And Thumbs up for the guys having zero falls.
That was all guys. Thank You
Click to expand...
Click to collapse
1. No, unlock it with a received code.
2. Probably yes but why bother with it? Use Open Camera & enable Hal support for Camera 2 api (in build.prop) as it's full present.
3. Not really certain if property Mpdecision binary blobs can be used on Snapdragon 650 SoC. It's really question for QC & Xiaomi firmware developer's. If their is a kernel source for any phone using Mpdecision with Snapdragon 650 it's safe to say that kernel infrastructure & binary libs can be copied & integrated. Then again in the past 2+ years a dozen of open source hot plugs ware developed for the msm bords of which some rather very good & best part is that they can be individually tuned for the SoC. Funy thing is how good battery life this thing have without any hotplug used & it really shows how power consumption unefficient MTK deca core design really is.
4. Yes with costume kernel that integrate support for it.
5. You can't expect from any big display, bulky, heavy phone to be drop resistant nor high durable. This stands for every phone with such characteristics ever made for instance if you drop a much better build Samsung Galaxy A9 on concrete and it hits by the display side its pretty much a game over same goes for the HTC 10 that is only 5.2“ & built like tank but rather heavy. Using a soft silicon cover with edges will help in most cases, I don't like flip covers even they naturally provide more protection.
I am also near to buy, I do not see any other 6+ phone WITH decent development (read: cm13, cm 14) support...
My only doubt is screen quality, reviewers not like it at all...
ivanox1972 said:
I am also near to buy, I do not see any other 6+ phone WITH decent development (read: cm13, cm 14) support...
My only doubt is screen quality, reviewers not like it at all...
Click to expand...
Click to collapse
It has a decent IPS in cell display not the brightest one available but good enough. Certainly not anything to write about back home but also nothing to get concerned with.
Actuality I don't possess one yet, just ordered it & expecting it to arrive tomorrow.
Concerning the development it's still far cry but I am confident it will get to officiall status regarding CM one day. Partial problematic will be to get the both versions flow less (regular & prime) to candidate for official...
Ok, friend. When you see screen, write how it is for yoi compating to other phones you had.
Thanks
Sent from my SM-T705 using XDA-Developers mobile app
The screen isn't as bright as a Redmi Note 3 on full brightness and black levels aren't great if you watch a lot of dark movies. That said, the screen doesn't go fully black in portrait orientation if you wear polarized sunglasses outdoors. My old Redmi Note 3 had that problem and I could only use the phone in landscape if I was wearing sunglasses.
ivanox1972 said:
Ok, friend. When you see screen, write how it is for yoi compating to other phones you had.
Thanks
Sent from my SM-T705 using XDA-Developers mobile app
Click to expand...
Click to collapse
Got phone today it came with MiUI 7 International.
Display dozen look charming but that is mainly because it's pore calibrated. I set the enchanted contrast on & it become a bit better, unfortunately you can't do much about calibration with firmware available options. How ever I put an good old Kodi 15.2 that still utilise old standalone composition & decoding libs so that I can control display contras, with contrast set to 63 display begins to shine it stil doesn't have punchy colors like my old S3 Neo with similar Dpi Amoled but it's not far behind. Naturally blocks aren't on the same level but they don't look bad. Display is definitely bright enough & better for reading of course compared to Amoled. So as I mentioned before nothing to write back home about nor a top of the pop's but perfectly fine for usage, just don't have to high expectations about it. For me 340 DPI is perfectly enough.
For now only problem I had its a absence of the H265 high 10 bit decoder support, not even software one implemented on default or Kodi player, will try later with new Kodi that use Android video framework but I don't have high hopes regarding it.
I came from a LG G3 recently and I´m about one week with Mi Max. The screen is bright and not really much difference from another ones. If you look closely maybe you notice lower DPI than G3's but hey - I´m used to see my screen in a QuadHD display... so it´s Ok to me.
I´m only with TPU cover that came into my bundle pack and polymer screen protector, so max attention to avoid drops, at least until my temp screen it not in it.
leandrocn said:
I came from a LG G3 recently and I´m about one week with Mi Max. The screen is bright and not really much difference from another ones. If you look closely maybe you notice lower DPI than G3's but hey - I´m used to see my screen in a QuadHD display... so it´s Ok to me.
I´m only with TPU cover that came into my bundle pack and polymer screen protector, so max attention to avoid drops, at least until my temp screen it not in it.
Click to expand...
Click to collapse
- Do they make temp glass protector for the screen?
- If you in USA do you know if its compatible with tmo's 4G LTE?
- Anything you dont like about the phone? Regrets?
I have a8 2018 and am thinking of getting a70 but i am not sure is it worth it?
biggest dissapointment of a8 is how slippery it is, edges of the phone are a disaster and with glass fingerprinty back theres no way to survive without case
other stuff was/is fine i guess, screen, cameras all ok, especialy selfie cam. altho camera app quite slow..
anyone had a8 or tired that can compare it to a70?
i know the specs but whats on the paper dont usually tell the whole story
bigger battery is nice
bigger screen also but is it as good or better?
i know the back is slippery but how are the edges when holding it ?
cameras better or worse?
how does gps work?
how is overall speed of the phone?
thanks
Screen is big and beautiful but it's not well made, so there's the touch issue, where the screen response latency is a little delayed so it's gonna be a nightmare doing stuff that require precession on this device, such as drawing or playing games that require aiming. Check:
Also tho the screen is beautiful, it has an issue where it turns off pixels that are supposed to be dark. So while watching something with a dark atmosphere, most of the time you're not gonna be able to know what part is pitch black, and what part is just darker than the rest. People don't usually notice this issue but I did notice it because I used my brother's A50 for a while and this issue isn't present on it. The issue with touch response latency isn't present on the A50 either.
The Snapdragon 675 isn't optimized by most games so you're gonna struggle with lag in games like PUBG and Asphalt and COD. The Exynos used on the A50 is optimized, tho. And by using the A50, I can clearly see how much of an advantage optimization gives to gaming.
There A70 isn't slippery, I use it without a cover, so that's a plus. I've dropped it a couple of times but there was no effect. The A50 isn't slippery either.
And that's about it. I'm gonna sell my A70 and get an A50, or I'm gonna check the A51 after it gets released. If it doesn't have the issues mentioned here, then it's gonna be a great device with a great screen.
PS: I'm not a hater, I'm just a user that's honest. I love Samsung, but the A70 just isn't good enough to be sold to millions as it is. The A50 is better imo. Good luck mate.
I personally haven't noticed any big touch issues. The only time the display seems finicky is of my hands are sweaty or have water on them, which is pretty normal, (although I did notice this happening more on this device than my previous device). I don't know what to say on the black levels of the device since I've never noticed any problems, but it could be possible. As for games, PUBG and COD run just fine for me on med-high settings, but I did notice that asphalt 9 didn't feel very smooth, 8 for whatever reason is A-okay though, so I do think that this chipset hasn't been fully optimised for all games, but I don't think you'll have many issues.
If you're now deciding between a50 vs a70, then here's the basic differences, you decide if it's worth it.
-A50 has a better GPU, but a70 has stronger CPU
-A70 has larger screen, but both have same resolution (I.e. 1080p)
-A70 has more storage(128gb), and RAM (6gb), and while the A50 has that too, I haven't seen that model being sold anywhere online (at least in NA).
-A70 has a bigger batter and a faster charger
-A50 stock camera doesn't support 4k (could be wrong as they could have pushed out an update for this)
-A50 is cheaper
They're both good phones tbh, I don't think you'll regret either as long as you weigh the pros and cons. Hope this helps!
SniperLolz said:
Also tho the screen is beautiful, it has an issue where it turns off pixels that are supposed to be dark. So while watching something with a dark atmosphere, most of the time you're not gonna be able to know what part is pitch black, and what part is just darker than the rest. People don't usually notice this issue but I did notice it because I used my brother's A50 for a while and this issue isn't present on it.
Click to expand...
Click to collapse
STOP peddling that nonsense. That is an issue with the lock screen ONLY. it is not a hardware issue and it doesn't affect anything other than the lockscreen. I don't know how many times i have to say that for you to listen.
James.Miller said:
STOP peddling that nonsense. That is an issue with the lock screen ONLY. it is not a hardware issue and it doesn't affect anything other than the lockscreen. I don't know how many times i have to say that for you to listen.
Click to expand...
Click to collapse
Look dude, I wouldn't talk about it if it wasn't there. You're just not noticing it because you've never put this device side to side with an A50 or a flagship and compared the displays. If I only had this device I wouldn't know that there are dark parts that I'm missing because the pixels are turned off instead of being dimmed. I only knew that because I watch my stuff on multiple devices, which means that I can notice it when a device has an issue with it's display.
+ If I'm still talking about an issue that you've previously addressed to me, then either I'm an idiot or the issue is indeed there. You're free to think of me as in idiot, but for me, the issue IS there, and I will showcase it later by doing a comparison between the A50's and the A70's displays.
PS: I'm not talking about the polarization on the lock screen. I know that that's a bug that only happens on the lock screen, that's why I'm not taking about it.
SniperLolz said:
You're just not noticing it because you've never put this device side to side with an A50 or a flagship and compared the displays.
Click to expand...
Click to collapse
Massive assumptions aside, My last phone was a S8. That's all I really need to say.
+ If I'm still talking about an issue that you've previously addressed to me, then either I'm an idiot or the issue is indeed there. You're free to think of me as in idiot, but for me, the issue IS there, and I will showcase it later by doing a comparison between the A50's and the A70's displays.
Click to expand...
Click to collapse
Please do. Looking forward to it.
Hi, question: i have a Note 10+ with all updates and updated via adb to Android 10 but my fingerprint scanner is still really awful. I have seen all yt video, seen all tuto on how to set the fingerprint but nothing!
Still awful, especially when finger is a bit wet. Is there a solution or is it better change the phone?
Maybe it is the way you registerd your fingerprints, my fingerprint sensor is accurate all the time
Are you using a screen protector? Mine sucks too. I have a glass one with the thin area in the glad over the sensor and I have used privacy film and it's ehh. It works perfect with nothing on it. Try turning the touch sensitivity up in settings and maybe re-register the print again.
Sent from my SM-N975U1 using Tapatalk
(The touch sensibility have nothing to do with the fingerprint sensor though.)
Maybe they finger print again but dont press to hard
Upside down
denzel09 said:
Hi, question: i have a Note 10+ with all updates and updated via adb to Android 10 but my fingerprint scanner is still really awful. I have seen all yt video, seen all tuto on how to set the fingerprint but nothing!
Still awful, especially when finger is a bit wet. Is there a solution or is it better change the phone?
Click to expand...
Click to collapse
You probably have, but try registering your fingers upside down and side ways.. and register loads of times with the same finger you mainly use, im sure you know all this though
It's awful, specially compared to the OnePlus6T
FCORivers said:
It's awful, specially compared to the OnePlus6T
Click to expand...
Click to collapse
, no, it is not, mine as many others work just fine, the fingerprint sensor for whatever reason doesn't work the same for all, odd, but not a so uncommon issue, and this happens among all brands
I partially blame the size of the sensor as well as the way they guide users through the enrollment process. The standard android fingerprint enrollment process, as i've experienced on my HTC U11 and Razer Phone 2, prompts for more finger edge samples. I actually went through the process on the Note as the software prompts and had mixed results. I then just decided to hit the sensor randomly with some overlap to give it a better overall picture of my finger as opposed to a bunch of samples of the same spot and then a few variants.
If you shine a flashlight at the screen you'll see the sensor size. It is a short rectangle that doesn't seem to cover the area that the fingerprint icon covers. I have an amFilm whitestone-style screen protector and while there is a slight difference, the stock experience was also not that great. I would recommend you try to figure out how you ACTUALLY use the fingerprint unlock. I noticed that while i'm enrolling i'm focusing on pushing with my fingers dead-on, in practice i actually use just the upper right corner of my thumb (if you're looking at the fingernail top-down). When I realized that I trained it with that in mind and it did perform better.
There was mention of the ones in the One Plus devices, which are actually different in that they are optical. Because they light up and read optically they have a more controlled environment than what the ultrasonic sensor on the Samsung phones. I can see someone with a deeper fingerprint patten be able to get better results vs someone with a very faint fingerprint. On oneplus devices though it would just be a different picture, but i'm thinking on an ultrasonic sensor there might not be enough peak and valley information to pass the threshold. Maybe samsung can make the pattern require less data points to match to unlock, but that would also mean it is less secure.
Bottom line is that while the tech has the potential to be more secure than optical under glass, it still has a little ways to go but it is serviceable once you get to it. I don't have big hands so i have to hold the phone in a very specific way to get a good grip on it. Once i figured that out, training the sensor again did yield better results.
I have the same problem. In sorry you haven't received a resolution, especially from Samsung who manufactured the Galaxy Note 10 Plus. I'm believe they were aware that it did not work with many 3rd party cases with protected screen covers. No matter how you register with screen off or on, the reader is intermittent and doesn't work with the cover. I hope you get the resolution as it will solve my issue as well.
The fingerprint registration process seems very glitchy too but after having experienced an awful 40% success rate with waking the phone using my fingerprint I deleted all the stored prints and started again. The secret is in storing decent prints so keep doing this until the phone unlocks with a 90%+ success rate like mine does now.
I purchased a new Galaxy S21 FE a few weeks ago, and I noticed that while the screen is responsive 90-95% of the time, every so often it won’t respond to a tap or swipe, necessitating an extra prod (or a few). Whether it's not pulling down the notification ceiling when swiping, or missing a key (or space bar) when typing despite tapping it, among others.
To reiterate, it’s not a problem with the screen itself because it mostly works fine, but every so often the software interacting with the display that responds to touches seems to glitch. And it’s not connected to any specific part of the screen either. And the phone in general is fast, and there's no lag in animations so it's not a refresh rate issue either.
I should note that a few months ago I returned a new Galaxy A53 with a similar issue. And a relative of mine with the Galaxy A32 5G said she has the same problem as well.
Does anyone else experience this with the S21 FE or any other recent Samsung phones? My 2016 Samsung phone's display/touch has none of these problems, despite being slower in general due to its age, and it being from the Samsung J series.
Anyone?
I come from an s20, and I received the s21 fe this week, and I noticed a little error, in the touch. It's like sometimes he doesn't recognize the fastest or light touch in a few times.
I admit mine does not feel very precise at times. I cannot pinpoint exactly what's going on but it's like it's slippery and I do not have a great accuracy on it. It did have a problem with the screen jumping up and down when scrolling sometimes but with the recent updates, this issue seems to be solved. However I still feel it is not precise or smooth as a S21 Ultra for example.
caiovinniciusbr said:
I come from an s20, and I received the s21 fe this week, and I noticed a little error, in the touch. It's like sometimes he doesn't recognize the fastest or light touch in a few times.
Click to expand...
Click to collapse
Randi03 said:
I admit mine does not feel very precise at times. I cannot pinpoint exactly what's going on but it's like it's slippery and I do not have a great accuracy on it. It did have a problem with the screen jumping up and down when scrolling sometimes but with the recent updates, this issue seems to be solved. However I still feel it is not precise or smooth as a S21 Ultra for example.
Click to expand...
Click to collapse
Please report it in the Samsung members app. With more people reporting these bugs, there's more of a chance that a patch will be released.
xda-eh said:
Anyone?
Click to expand...
Click to collapse
Yes, me. Got this phone a few weeks ago and have noticed it randomly not responding to a tap, pinch or swipe. Exact symptoms as you.
Wondered if this was a known issue with Samsungs or not and whether there was a software patch for it.
Any luck?
+1
I already wrote about it somewhere.
Often I have to double-click first or press a button, then a fingerprint will work. I can't find when this occurs. And I'm sure, this comes in December with Android 13.
tuncan said:
And I'm sure, this comes in December with Android 13.
Click to expand...
Click to collapse
Actually, in my case it seems to have gotten a little better after the Android 13 update, but it's still a problem.
I was adamant that this issue was the device itself. But funnily enough, having removed the glass screen protector, the problem has disappeared.
It must've been that layer interfering with touch recognition.
daveshirman said:
having removed the glass screen protector, the problem has disappeared.
It must've been that later interfering with touch recognition.
Click to expand...
Click to collapse
In my case removing the protector doesn't help.
I don't use a screen protector on my phone.
I am having the same issue anyone got any fix?