Related
As this is my first Windows Phone and I wasn't really sure what to expect when it came to fluidity, I was pleased with how smooth everything is. However I've begun noticing a decent (read: annoying) bit of lag when I open up the messaging app and begin typing. The letters take a second to appear and autocorrect is slow if it comes up at all. The lag only last maybe 3-5 seconds but annoying none the less. I've also had some rather bad experience with laggy apps, with Skype being the worst culprit. I read good things about the recent refresh, but it's pretty much unusable for me. I've also been having issues with losing LTE and having it drop down to "4G". A simple toggle of airplane mode fixes it, but it's gone from happening rarely to happening once or twice a day now. When I do have LTE though, I have 4-5 bars constantly.
Anywho, bit of a wall of text but I just wanted to see if anyone else is having similar issues and if it's worth going to AT&T and seeing if they'll replace the phone for me as I'm still within my 30 day return window.
EDIT- Just remembered 2 more issues. Had it reboot on my when adjusting the volume and there's a weird clicking noise that happens when I swipe from the first picture in the camera roll. The phone is on silent, and it only happens going from the first to second picture. Little odd but not a big deal.
avengeryarr said:
As this is my first Windows Phone and I wasn't really sure what to expect when it came to fluidity, I was pleased with how smooth everything is. However I've begun noticing a decent (read: annoying) bit of lag when I open up the messaging app and begin typing. The letters take a second to appear and autocorrect is slow if it comes up at all. The lag only last maybe 3-5 seconds but annoying none the less. I've also had some rather bad experience with laggy apps, with Skype being the worst culprit. I read good things about the recent refresh, but it's pretty much unusable for me. I've also been having issues with losing LTE and having it drop down to "4G". A simple toggle of airplane mode fixes it, but it's gone from happening rarely to happening once or twice a day now. When I do have LTE though, I have 4-5 bars constantly.
Anywho, bit of a wall of text but I just wanted to see if anyone else is having similar issues and if it's worth going to AT&T and seeing if they'll replace the phone for me as I'm still within my 30 day return window.
EDIT- Just remembered 2 more issues. Had it reboot on my when adjusting the volume and there's a weird clicking noise that happens when I swipe from the first picture in the camera roll. The phone is on silent, and it only happens going from the first to second picture. Little odd but not a big deal.
Click to expand...
Click to collapse
The only problem i have seen is:
When i switch off my phone and turn it on sometimes it freezes and i have to turn it of an on 2 or 3 times in order to get it working. this has been happening recently i dono whthere it is to do with some apps or firmware issue.
sometimes the touch screen also give hiccups specially on facebook app.
No other problem. coming from samsung galaxy s 2, i only miss the ability to change my homescreen every week with a different launcher and layout. The apps that i miss are Tweetdeck, 100% working Pulse, Youtube and Facebook App.
My Lumia 900 playing Angry birds is so much faster and smoother compared to SGS2.
Overall i am happy with the looks and performance of my phone.
I get that messaging problem as well sometimes where the keyboard lags and the typing noise doesn't keep pace with my inputs.
Mildly annoying and it's not constant so no big deal for me.
Sometimes, multitasking stops working and I have to do a quick power-off.
Actually, all issues are resolved with a quick reboot as opposed to a reset with my Lumia 900 which is something I can't say about my HD7.
I agree with above. The only lag I get is the occasional facebook load time lag. Some apps take longer to load than others, it's perfectly reasonable. As for overall lag, I had one experience yesterday where everything just slowed to a standstill. It was the first time I had to restart the phone, but after that, I've seen no problems. I can imagine it was a corrupt app as I had been downloading quite a bit of them that day. Coming from android for 2 years, the experience here is much much smoother. My advice, as i learned from the past 2 years, is to retrace your steps and find out when exactly it started to lag. When you find the beginning see if you downloaded any poorly rated or laggy third party app, or if you changed a seeting on your phone. If it continues to lag for no reason, you might just have a bad device. Best of luck.
Minor
I just upgraded from a Samsung Focus. My very first reaction was that the screen was slightly less responsive than the Focus, which was buttery smooth and instantaneous. It felt slightly, but noticeably less responsive. After using it for a day, I don't notice it anymore. I am sure it is there, but my memory of the Focus is not as near. As far as true lag goes, I have not experienced any after 2 weeks use, and no reboots or freezes.
JamesAllen said:
I just upgraded from a Samsung Focus. My very first reaction was that the screen was slightly less responsive than the Focus, which was buttery smooth and instantaneous. It felt slightly, but noticeably less responsive. After using it for a day, I don't notice it anymore. I am sure it is there, but my memory of the Focus is not as near. As far as true lag goes, I have not experienced any after 2 weeks use, and no reboots or freezes.
Click to expand...
Click to collapse
I'm glad you are enjoying it but I came from the original focus myself and had the exact opposite reaction. That it was much faster and smoother than my old focus... I still have it and my kids play the old games on it so I can compare regularly and still feel the same.
Does anybody have lag when they are pinching and zooming on heavy desktops websites? i am getting a lot of lag here where my htc titan did not get that lag.
The only issue I seem to be having is when playing any kind of music or watching videos. If I touch any of the capacitive buttons, it's as if I long press them. Not a huge deal since I usually only touch the back arrow anyway, but that's all I get.
i was wondering if anyone else had this problem. My lumia has consistently not displayed maps in nokia maps or the maps app. It will show my location on a blank black or patterned screen (depending on the app). It's not a wifi or data issue because it's happened on both. It's happened five times in 3 days. Each time i've had to shut the phone off and restart it and it works again. Is this just a problem with mine? Thanks.e
bigwavesurfer4 said:
i was wondering if anyone else had this problem. My lumia has consistently not displayed maps in nokia maps or the maps app. It will show my location on a blank black or patterned screen (depending on the app). It's not a wifi or data issue because it's happened on both. It's happened five times in 3 days. Each time i've had to shut the phone off and restart it and it works again. Is this just a problem with mine? Thanks.e
Click to expand...
Click to collapse
it is a problem with your device, so do you have web browser lag or is that problem only with my device.
[Update March 5th 2014]
Probably all 2014 Note 10.1's sold these past few months are suffering from one or more multitouch issues. From what we now know these appear to be software issues, effecting all current firmware versions for this device.
There are 2 known manifestations of this bug (or more likely: these bugs), described below. In both cases it seems to be a software issue because normally the 2014 Note 10.1 will work fine and the process of re-creating the issues is very clear and repeatable.
It looks like the multitouch driver becomes unstable if either one of the following occurs:
1. (Some models) You place (a part of) your hand on the screen for (at least) 5 seconds without moving it. This would usually happen when you are writing or drawing with the S-Pen.
2. (All models?) You place a finger (or several) on the screen for a longer time (close to 30 seconds) without moving it (them).
After either of these situations a 'defective unit' will show very erratic multitouch behaviour for a while.
It is easiest to see what happens if you use a so-called "Multitouch testing tool" (available Free on the Play Store). Such a tool typically shows all the screen areas where screen touches are detected by the device (in this case: the 2014 Note 10.1). Examples of such tools are: MultiTouch Test, MultiTouch Tester and YAMTT.
Erratic behaviour will usually start with all screen touches suddenly disappearing, meaning the device forgets that you have fingers (or part of your hand) on the screen. If you remove fingers (your hand) from the screen and again touch the screen several times a whole range of behaviour is seen: touches are detected and erroneously forgotten in quick succession. Sometimes so-called ghost-touches appear (meaning, the device will detect touches not anywhere close to where you are actually touching the screen).
This erratic behaviour will usually disappear when you leave the screen alone for a while, although several people (including me) have reported longer running issues (for instance during typing and editing using an on-screen keyboard). A surefire way to get rid of the issues is rebooting your device.
Since this is a "Note" device many people who's 2014 Note 10.1 suffers from these multitouch issues will encounter it while (or after!!) using the S-Pen. Others will notice issues while gaming or during typing/ editing.
The following clip by Kizune shows an example of what can happen while being inside a Multitouch testing app:
More videos you can find below (in post #16) and in the SwiftKey not working well on 2014 Note 10.1 topic, where the roots for starting this topic sprout from.
As of yet Samsung appears to be unaware of these issues, although several have approached them about this, returned their Note tablet, exchanged it or even handed one in for repairs. Hopefully we get this fixed soon.
Note 1: from early reports (in post #83) it looks like the new Note Pro 12.2 doesn't suffer from these issues.
Note 2: It is possible that a build up of static charge (through capacitance) is causing these issues, possibly caused by bad wiring (grounding) of the touch/ S-Pen detection circuitry.
Note 3: A new video has surfaced (in post #89) which shows 'noise' introduced in the touch-detection software while pinching/ zooming (see video below). It is unclear if this is related to the issues mentioned above.
i noticed this using the stock kb. i'm not a particulary fast typist on the screen but i'd get far too many lack of responses when typing on the split kb. standard qwerty was fine, but that have been b/c i'd type slower. i'm able to hit keys quicker on my gn8 without any misregistering of keystokes.
the fact there has been to OTA's in just a week is a sign they let this one out before it was ready. i still love the tablet though.
It happens to me too just like you see in the youtube video.
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it.
Click to expand...
Click to collapse
Did you try the "whole hand" thing too? It would be super if Samsung solved things that quickly, but I feel a little aprehensive. We didn't get the recent updates yet in my area so I cannot see for myself.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
no, I took both OTA's Just before rooting.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
atg284 said:
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
Click to expand...
Click to collapse
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Ettepetje said:
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Click to expand...
Click to collapse
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Edit: the YAMTT app seems buggy because the other touch apps don't go crazy when all ten fingers on on it. But I could not replicate what YAMTT app was doing to the one in the video.
atg284 said:
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Click to expand...
Click to collapse
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Ettepetje said:
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Click to expand...
Click to collapse
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
atg284 said:
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
Click to expand...
Click to collapse
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Ettepetje said:
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Click to expand...
Click to collapse
Oh I don't have that at all. no ghost finger touches ever. I have not rebooted over the period of testing either today. Are you fully updated?
I will keep checking this over time though.
Ettepetje said:
The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Click to expand...
Click to collapse
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
What problems are people seeing due to this?
Click to expand...
Click to collapse
1. When taking notes at the university, I sometimes move the viewport in S Note using the zoom gesture without the zooming motion. And as you can see, putting my hand on the screen as shown in the video triggers the problem for me, so doing that gesture is almost impossible for me. I know there are scrollbars, but they move the viewport too slowly (but of course I use them when I notice the multitouch issues are occurring).
2. Same as above, but when drawing in Sketchbook or ArtFlow. And here it's extremely annoying because there are no scrollbars I could use.
3. A small annoyance compared to the others but: When I play Carmageddon, the multitouch issues get triggered once in a while. And then I can only either control the car, or accelerate or break, but not both simultaneously. Sometimes my touches aren't even registered at all. I often get destroyed due to the multitouch issues.
Kizune said:
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
Click to expand...
Click to collapse
I changed the description in the opening post. I never had it happen like that yet. Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Did you find another way to get rid of the issues besides resetting your Note?
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Ettepetje said:
Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Click to expand...
Click to collapse
Exactly, I noticed it while taking notes. And then I made this my test method to replicate the error.
Anyway, here are some videos. The first shows a real-life situation in S Note with that problem, the second and third show that the problem also occurs in other multitouch test apps (yes, I'm looking at you, atg284 ).
And to make it more "real-world friendly", I used my old "provocation method" because that's how you put your hand on the screen while drawing and writing.
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Click to expand...
Click to collapse
Yup. And I even got that tank-like bonus police car, so they die just by touching my car tank.
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Click to expand...
Click to collapse
Did it take longer to get the erratic behavior like you said in pm? I'm trying to get the description in the opening post right, since we got 4 people now who claim they don't have it. I think the score should be 100%, and just included the Poll so that people at Samsung would quickly realise how big the impact is.
I can duplicate this.. just didn't figure how to repeat consistently until now..
First noticed when trying to pinch zoom in adobe reader .. you get very jerky redraw back and forth.. this could be app specific , but i haven't seen this on other devices
Sent from my SM-P600 using xda app-developers app
I'm also experiencing this. It's a terrible issue when taking notes in class.
Can we expect a fix?
Hi
something weird happened to me. My Note2 (TW rom + root) fell from my pocket and hit the ground, while I was driving my scooter, and I realized only a few KMs later...
After :crying: I was lucky enough to find a nice person that gave it back to me. So I was happy even if the screen was broken. The weird aspect is that since this damage, the phone is not working very well. It hangs (temporarily) and stutters, the battery is consumed more than normal, when you slide down the notification it get stuck in the middle of the screen. It is still usable and generally when you launch an app it works almost perfectly but the system is weirdly behaving. Another example is that when playing Google Music songs I have gaps.
It SEEMS that the processor is busy or has spikes of power that makes the other apps to behave slower.
So the question is: could be that a damaged screen impacts the sw behaviour (just an educated guess: maybe it's receiving lots of touch inputs due to the breaks...). If i repair the screen, will it go away?
Thanks
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Clear Data,Cache and retry maybe it's just a lag?did you face any heating problem?
I recommend you to 'tick' show touches option in Developers Options!
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I play clash of clans. This is happening because you are lagging. Just close all other apps before playing. Its all smooth for me
DUHAsianSKILLZ said:
I play clash of clans. This is happening because you are lagging. Just close all other apps before playing. Its all smooth for me
Click to expand...
Click to collapse
Hmm, still happening tonight. I did a fresh reboot and made sure only CoC was running in the task manager. Still had the issue with missed clicks, maybe about 1 in every 8.
enable the deiveloper options (google if you don't know how, it is easy and required to be able to playdeus ex the fall for reasons)
Under developer options there are 2 options under input enable both of them. That will give you a graphical representation of your touches and swipes.
While we are in settings check device/display for touch sensitivity and try checking or unchecking the box to see if that helps you out.
one last thing if you are comming from a smaller screen device you may not have have noticed but touch screens are not pixel perfect in the best of worlds. And on a smaller screen with less pixels it tends to be easier to hit the area you want. Check to see if you are not hitting somethine else by a building by placing walls surrounding a building like a mine or a pump then touch to collect.
This is happening for me also, and it is really annoying. Clash of Clans is the main thing I use the tablet for.
I tried enabling the developer options like was suggested, and it is still happening. Even with the graphical touch and swipe showing where I tapped on something, Clash of Clans is apparently ignoring the action.
Use stylus
It works better if you use a stylus. I have the same problem but I have not yet found the ideal solution. Therefor most of the time, I keep on using my Motorola Xoom to play with CoC.
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I bet you guys using marshmallow os wright ? I have this problem too.. i suspect thr os isnt compatible to coc, or the coc isnt compatible to marshmallow. We need some fixes from both.
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues? Can't play at all atm. Really frustrating
Hi there,
So I finally got my beautiful panda Pixel 2 XL and I absolutely love it, except for one thing - touch latency or sensitivity.
UPDATE
If you're having similar issues, be sure to "+1" the following thread on Google forum and also comment: https://productforums.google.com/forum/#!topic/phone-by-google/3XDqX3LgpvQ;context-place=topicsearchin/phone-by-google/category$3Agoogle-pixel-2%7Csort:relevance%7Cspell:false
I took off the glass screen protector and I'm now using it naked. I feel some improvement BUT this is still far from perfect. I was expecting such phone coming straight from Google to blow me away in terms of touch latency and such, but for now it feels like my Oneplus 3 is actually more responsive. Super strange.
I'm not entirely sure what's going on, but basically I feel like I'm having a hard time registering a touch on the first try TOO OFTEN. Sometimes I would even try to scroll up or down a web page and it wouldn't register for a few tries.
Things to note I'm NOT using the screen naked, I'm rocking an AmFilm tempered glass screen protector, it's a dot matrix kind of screen protector, one that doesn't actually stick to the screen entirely, only at the edges. Could this be the issue?
Is anyone else having similar issues with or without a screen protector?
Again, other than that, the device is perfect. Also very minimal blue shift that doesn't bother me at all.
Thanks for your help
How is the sensitivity with the screen protector off?
Sent from my [device_name] using XDA-Developers Legacy app
Patch7 said:
How is the sensitivity with the screen protector off?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I know it's silly, but I don't want to take off the screen protector because I got it aligned perfectly and the only replacement I have is a different type - a tpu film.
The thing is, I didn't even have a chance to try out the phone without a protector since this was the first thing I did when I unboxed it :/
Was mainly wondering if anyone else is having touch screen issues with a tempered glass screen protector of any kind?
UPDATE I took off the glass screen protector and I'm now using it naked. I feel some improvement BUT this is still far from perfect. I was expecting such phone coming straight from Google to blow me away in terms of touch latency and such, but for now it feels like my Oneplus 3 is actually more responsive. Super strange.
You on latest 8.1?
I notice some touch sensitivity issues in the far edges of the screen. I'm not using any screen protection at the moment.
galaxys said:
You on latest 8.1?
Click to expand...
Click to collapse
Yep, I'm on the stable 8.1 all stock not rooted or anything.
This is mostly apparent when scrolling, I would sometimes scroll down and the page would move downward and sideways altogether, as if it is registered as a swipe to the side with a scroll down. Same when scrolling up. Very annoying.
nimrodiny said:
Yep, I'm on the stable 8.1 all stock not rooted or anything.
This is mostly apparent when scrolling, I would sometimes scroll down and the page would move downward and sideways altogether, as if it is registered as a swipe to the side with a scroll down. Same when scrolling up. Very annoying.
Click to expand...
Click to collapse
What's your Animation Scale set to in Developer settings? I changed mine to .5x and noticed improvements in scrolling & response...
galaxys said:
What's your Animation Scale set to in Developer settings? I changed mine to .5x and noticed improvements in scrolling & response...
Click to expand...
Click to collapse
Yeah, definitely. I'm already on 0.5 scale unfortunately so this can't be it. Thanks for your help anyways! Appreciate it
Same problem after the 8.1 update answering a call is so hard. even unlocking my phone with a swipe up is very difficult. Swiping away notification takes 3 tries. I'm actually regretting the 128gb with google protect! So much money with so many problems. I came from a GS7 edge and it was way better performance wise then this phone. Feels like I'm just a beta tester for google. Seems like every update fixes one thing and breaks 4 more.
mikepopo99 said:
Same problem after the 8.1 update answering a call is so hard. even unlocking my phone with a swipe up is very difficult. Swiping away notification takes 3 tries. I'm actually regretting the 128gb with google protect! So much money with so many problems. I came from a GS7 edge and it was way better performance wise then this phone. Feels like I'm just a beta tester for google. Seems like every update fixes one thing and breaks 4 more.
Click to expand...
Click to collapse
Agreed. I actually miss my Oneplus 3 in terms of performance and fluidity. I can't type or browse with this phone without having weird glitches. Sometimes the tap wouldn't register, sometimes it's the scrolling acting up.. Very annoying as I said
I'm having similar issues. Randomly my phone decides I touched somewhere in the middle of the screen I didn't at all, or when scrolling down a list eg. YouTube or Twitter, it suddenly jumps me back to the top as if I swiped down at super human speed.
More over the most consistent issues I'm having is tapping on the edge. Eg. The elipsis (3 vertical dots) when looking at 'my channel' or a playlist such as my attached screenshot. I cannot touch the elipsis at all even with a stylist.
My device is Google Pixel 2 XL, 8.1.0, build OPM 1.171019.011
P.S I'm using the phone 'naked', no case, no screen protector.
Damn. Looks like we've got an actual issue here.
For me it is most consistent when I'm scrolling up or down a list that can also go sideways, like Instagram Stories stickers for example, or an email on Gmail where you can swipe left to get to the next message. It will randomly go right/left when I'm actually swiping up/down.
It also happens to me, sometimes, while scrolling up or down, 5 or 6 times successively, it doesn't recognizes one of the touches.
nimrodiny said:
Damn. Looks like we've got an actual issue here.
For me it is most consistent when I'm scrolling up or down a list that can also go sideways, like Instagram Stories stickers for example, or an email on Gmail where you can swipe left to get to the next message. It will randomly go right/left when I'm actually swiping up/down.
Click to expand...
Click to collapse
Nimrodiny, would you mind trying to go on the YouTube app, and either on your 'my channel' list or a playlist try to tap on the ellipse?
It's completely impossible for me, every time either nothing happens or it decides I touched the video itself to play it. I'd like to know if my issue is not unique.
Addendum: I tried viewing this page in desktop view mode in Chrome and zoomed in. I was able to scroll up and down over and over without any side scrolling happening at least.
I have noticed sometimes it freezes when loadng a web page thought it was chrome but updated to the beta.
Same effect, something is off with the touch sensitivity but not always.
Dav_Edward said:
Nimrodiny, would you mind trying to go on the YouTube app, and either on your 'my channel' list or a playlist try to tap on the ellipse?
It's completely impossible for me, every time either nothing happens or it decides I touched the video itself to play it. I'd like to know if my issue is not unique.
Addendum: I tried viewing this page in desktop view mode in Chrome and zoomed in. I was able to scroll up and down over and over without any side scrolling happening at least.
Click to expand...
Click to collapse
Yep. I can definitely tap on the ellipse on YouTube via my channel.
BTW, just made a scrolling comparison - same website, same browser, on my Pixel 2 XL vs the OP3 and... The OP3 absolutely killed it. It was way smoother and never stuttered while the Pixel had tons of stutters and misreading of my swipes
Thanks for testing Nimrodiny. In that case I best go back to the store and exchange my phone, as edge tapping is definitely broken for me.
Ya. Happens to me.. not acurate touch.. try touching that 3 dots on YouTube app on full screen ( where u change resolution of youtube play back)
Ufff fed up with this.. display, speaker, touch.. how many more
I came from OnePlus 3 n got panda pixel 2 xl. I faced some touch sensitive issue while typing n sometimes browsing. M using my pixel with iq shield screen protector film. I did a factory reset it did helped with swipe issues to some extent. Also I disabled vibration n sound for touch and feel bit better while typing. Mostly while typing I had hard time pressing space bar , most of the time I had to press twice to register a space. lts like phone is unable to keep up with my typing speed(m not that fast though). It doesn't feel like using a flagship phone . I would say touch is good but definitely not great.
Other than that I face no display issues like screen burn in or weird sound issues . Ya blue tint is there but it's part of the display not an issue.
I would suggest try factory reset once n disable sound and vibration on touch and see if it does help some how.