Swiftkey questionmark/exclamation mark-lag? - OnePlus 3T Questions & Answers

I've been using Swiftkey for as long as I can remember and really like the app. But when I switched to the Oneplus 3T recently I noticed some lag when swiping the "period"-button to make either a questionmark or an exclamation mark. I've tried both the beta app and the regular one and both are the same. Does anyone notice the same thing? It works fine with all my other phones.
It's not a terrible lag, but still noticable and pretty annyoing.
Any tips for me?

I believe that's because of the higher touch latency on the OP3T. I did notice it.. was a turn off initially then got used to it (sort of). Trying the Google Keyboard for now.

rezapatel said:
I believe that's because of the higher touch latency on the OP3T. I did notice it.. was a turn off initially then got used to it (sort of). Trying the Google Keyboard for now.
Click to expand...
Click to collapse
Hm.. That sounds weird to me. But you might be right, even though I'm not sure how that could be the reason..

Related

[Q] Phantom Taps, Bad Screens?

Does anyone have a solution for phantom taps on your NC?
I'm on my 3rd Nook Color when I pick up the replacement unit this afternoon.
My general issues are phantom taps - or the NC doing things I don't want it to. So far a very poor experience when typing, turning a page in a book, or even just navigating the ui. The whole issue may be me, it happens regardless if I am plugged in or not. I keep a very clean screen so there is very to little gunk.
I do have sweaty palms on occasion but not out of the ordinary. I have other touch devices that have never given me this issue. If anything I think the screen is overly sensitive - hardware or software issue?
Nope it's not just you. Mine has a multitude of issues with the touchscreen...
Essentially I cannot use the touchscreen when the device is plugged into stock charger/cable as wherever I put my finger, a random touch appears somewhere on the x-axis near my finger.
It seems that the device does not like changes in temperature or humidity either when it is unplugged. Using my tablet while cold was impossible, and likewise while it had been warm.
I'm on my second tablet from Best Buy-- the first one had dead pixels galore (enough to make the best buy rep say "dang!"), and now this one has a bad touchscreen and hard to press power button.
However: I purchased one of these for my mother a few days before mine at Barnes and Noble, and it has no issues whatsoever... at least not yet.
I've come to the conclusion that this hardware is quite beta, but I'm willing to give them a chance since it is the best bang for the buck, even if I have to go through a couple of returns... it's honestly almost worth the time for me since a tablet is so valuable for schoolwork.
Fortunately mine does not do this. I think maybe for those that are having this issue it may be able to be fixed in a firmware update.
My EVO had extremely similar problems when it first came out with the touchscreen and not being able to use the dropdown menu while the device wasn't grounded. After a firmware update the phone was great with touch sensitivity.
my first one did this also. so far the second is doing fine, but the first didn't have any problems till the 13th day of owning it.
i'm hoping it's just an issue that can be fixed via software - maybe someone put an incorrect voltage input somewhere.
I was having the same issues. I bought a screen protector and that seemed to solve it. So far, it's been working fine.
I noticed the screen protector stabilized the touchscreen a lot. Before I seem to have a problem finding the sweet spot for a touch. Now it seems better.
However, my phantom pinky is always touching something while I am trying to navigate. As long I only get one finger near the screen, it's fine.
Mine came from B&N.
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Awats said:
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Click to expand...
Click to collapse
Considering the Nook has neither I think you are okay.
khaytsus said:
Considering the Nook has neither I think you are okay.
Click to expand...
Click to collapse
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Mine only has problem when screen gets dirty. Try a screen protector or use gloves.
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Screen protector helps to solve my problem.
Are you seeing more issues right after cleaning the screen? I see issues then and I think it is because I an using some moisture on the cloth. If I just dust it lightly with a dry cloth and live with a few finger prints there seem to be less of an issue.
Awats said:
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Click to expand...
Click to collapse
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
iolinux333 said:
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Click to expand...
Click to collapse
....no
khaytsus said:
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
....no
Click to expand...
Click to collapse
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Awats said:
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Click to expand...
Click to collapse
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Is this occuring when the nook is plugged in? sometimes the charger can cause phatom touches with the touchscreen. Cleaning the screen and being on a stable ROM usually gets rid of that problem.
If only I weren't so stupid ...
khaytsus said:
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Click to expand...
Click to collapse
LOL! Ok, I sat down with it and played for a bit. It appears some tilt sensor is handling the up and down tilt. If you raise the screen over your head, it shows those stars and if you tilt it down, I see what is below the horizon. That is pretty consistent. But it's also "simulating" a compass inadvertently.
By that I mean that if I happen to turn it on facing north, it appears to track as you turn in a circle but it's really just me tilting it and it's rotating he view. If you do it enough it has no clue the direction it's facing.
I'm just glad I figured this out before I got lost in the Amazon.
Just got mine plugged it in and unplugged and within stew minutes phantom touches couldn't even reboot it im on cyanogen mod 7
Sent from my SCH-I500 using XDA Premium App
Nook Screen Recalibrate
You guys can try my app from the market
assid2 said:
You guys can try my app from the market
Click to expand...
Click to collapse
Wow, it seems to have improved the accuracy! I need to play with it more to be sure.

Multitouch with +5 fingers

****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine
Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
anyone ?
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.

Galaxy Note 5 has an interval where it stops registering one or more tap input

I often play rhythm games with my Note 5 so it's pretty noticeable when I get misses because of this.
I am not particularly sure what's causing this. Stock rom or not (I have LineageOS right now, I even tried the ported S8 Edge rom) the problem is still there.
I can make guesses that it could be input lag, general lag, or something else processing related. Is this a common problem? Could this be more on the hardware end?
Tronitus said:
I often play rhythm games with my Note 5 so it's pretty noticeable when I get misses because of this.
I am not particularly sure what's causing this. Stock rom or not (I have LineageOS right now, I even tried the ported S8 Edge rom) the problem is still there.
I can make guesses that it could be input lag, general lag, or something else processing related. Is this a common problem? Could this be more on the hardware end?
Click to expand...
Click to collapse
https://forum.xda-developers.com/note5/help/fix-regions-display-responding-to-touch-t3862955
milance92 said:
https://forum.xda-developers.com/note5/help/fix-regions-display-responding-to-touch-t3862955
Click to expand...
Click to collapse
Thanks for the suggestion. I actually tried your method but, sadly, no improvements whatsoever.
The problem is still present and I can't keep a combo at all in my game due to random unregistered taps.
EDIT: 12 hours after I did your method, things seem to have improved at least. I'm not certain if the problem is completely solved or it's just my own mistakes in the game now. I think I did more shocks to the phone than what you recommended, though.

Ghost touches

This is a pretty big issue that blue up on the OnePlus forum and Reddit. People are experiencing ghost touches in apps. It's very easy to also experience this by opening cpu-z and letting it sit there for a minute or two not doing anything. It seems not everyone is experiencing this though. I have tested and do experience it. Do you?
Yup. Mine does with cpu-z open. what do we do?
BossJ said:
Yup. Mine does with cpu-z open. what do we do?
Click to expand...
Click to collapse
Depends if it's a hardware or software issue. Personally I already submitted a return request with OnePlus.
I just cancelled my order.. hopefully there is a software fix for you guys
This only happens to me on cpu-z and not in any other app. So I guess a future software update is gonna fix it.
Left it for a minute and didn't notice anything. On 9.5.3, bootloader unlocked and patched boot image with root.
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
I installed CPU-Z just to check on my International 8GB/256 model and I've got no issue with ghost touches. Not sure what is causing this for you all, but I do hope it is sorted out for you all.
When I turned off NFC the issue went away for me glad I don't use it whatsoever haha
Purest said:
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
Click to expand...
Click to collapse
Well that's not a solution disabling a useful feature to not have ghost touch issue.
On screen/off screen gesture are one of my favorite using it, so not a solution to me.
Simple will return the device.
I haven't order yet but i will next couple of days.
There's many reports across oneplus forum.
https://www.androidpolice.com/2019/...ros-are-suffering-phantom-touch-input-issues/
I left CPU-Z running for at least 10 mins.
And all is OK. Maybe it's a rouge program or something to do with the unlock\twrp?
The only way to be sure is to reset to stock and only install CPU-Z
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
romanB_SK said:
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
Click to expand...
Click to collapse
Wow that's seems real bummer.
Why would OP use Novatek display controller since had bad reputation and bad track record.
So the question is how do we know if all that units effected having all of the them Novatek display controller?
Or if there's another supplier for those units that don't have that issue.
Man things are getting much worse if it's hardware related and not software that I thought.
Sent from my V1821A using Tapatalk
It's extremely annoying it has happened to me a few times even when I was boasting about the new device to some colleagues at work. I thought it was me at first until then I read IRS an actual thing. I won't return it yet but I might if it's not sorted soon. It's extremely irritating.
Sent from my [device_name] using XDA-Developers Legacy app
Looks like ghost touches are related to NFC. Try with NFC turned off.
C3C076 said:
Looks like ghost touches are related to NFC. Try with NFC turned off.
Click to expand...
Click to collapse
Can confirm. My Ghost touches seize when NFC is disabled.
Sent from my GM1913 using Tapatalk
I've started yesterday experiencing that ghost touchs and also screen not responsive to touch in some panel sections (mostly the upper right zone). The phone didn't gave me that problem since I bought. I noticed when this happening, pulling the notification bar down to the tile settings makes that zone work again. Same thing happened when that random ghost touchs happens.
Didn't had any problems, don't use NFC, tried turning it on, ghost touches started appearing on cpuz, but not on other apps. As i don't use NFC i probably won't return the phone.
I just tried with CPU-Z and a few seconds after starting the app, the screen turns crazy tapping here and there. Can confirm also disabling NFC solves it.
Turning off nfc or not using gestures or not using cpuz app is just temporary solution.
And there's multiple reports that ghost issues happening other app too.
And we never know if thing get worse over time.
I'm afraid it's a more common issue than we thought but many users simple didn't notice it until now.
Oneplus should clearly take attention on that issue seriously and fix it ASAP.
Shouldn't be happening at all with any kind app or scenario of usage.
Sent from my V1821A using Tapatalk

Low Brightness Flicker (LineageOS & Stock too?)

Hi, sorry if this was posted before, but with XDA moving to XenForo, search seems messed up, i did several searches and nothing comes up for "flicker" in this whole Pixel 4 XL Forum...
Has anyone else dealt with the low brightness screen flicker? I know it can't be just a bad phone, since i just bought three pixel 4 XL phones and they all exhibit this same behavior.
They are all running LineageOS (Official builds) so I don't know if this just affects the ROM or stock as well (although I've read it might affect stock phones too elsewhere).
It makes the phone pretty difficult to use in very low light situations, the screen will constantly flicker (more noticeable on darker backgrounds).
At first I thought it was just the Opera browser (as that's what I prefer), but it's operating system wide... Apps like "Darker" help.... because you can crank up the phone brightness and use a filter to dim the screen.... but it doesn't get the top & bottom menu/buttons, so those remain like spotlights in your eyes with that workaround.
Just curious if anyone knows whats up with this... it's the only phone I've ever seen this behavior on (and i've used Pixel 1,2,3 XL phones all with Lineage, and a myriad of other devices back in the Cyanogenmod days.... I've never seen a screen flicker issue like this).
Thanks for any help
edit / update-
the pro version of "darker" app works to fix this.... you crank the phones brightness to 100% and with the pro version you can dim the rest of the interface.
hopefully this helps anyone else suffering from this HUGE flaw (again i don't know if its just LineageOS or not, i didn't run stock on these except to unlock bootloader etc)
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
edwinek said:
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
Click to expand...
Click to collapse
hmm.... you running stock i guess? i don't see smooth display option in lineage

Categories

Resources