Database Info

Does your "pointer location" follows "touch location" ?

TF700T .30 firmware JB, wipe, cold start. otherwise works ok, but:
development options => enable pointer location (shown in blue traces) and touch location (shown as white glowing plate).
You can see whatever you do on the screen, the touch location always follows your finger.
However, if you touch down on the screen with one finger and move around for a while, you can see that the pointer location trace fails to catch up with the touch location --- it can go as bad as a few seconds delay. I have zero such delay, even after touching down a finger and moving like crazy for a minute, on my 3yr-old nexus one phone w/ JB (admittedly much smaller screen).
Do you guys have this problem? Is it a red flag calling for return??
Thanks.

I'd guess this is just the debug option itself that creates the lag by painting an ever-growing location trace. Do you see any negative effect in real use of apps (with the option off)?

_that said:
I'd guess this is just the debug option itself that creates the lag by painting an ever-growing location trace. Do you see any negative effect in real use of apps (with the option off)?
Click to expand...
Click to collapse
Not that I can notice, so I guess it is fine. I don't see such delay on the old phone with the traces enabled though.
I do feel the system is laggy : chrome or browser freezes from time to time. This is latest firmware , wipe, cold start already ....

mailxd said:
I do feel the system is laggy : chrome or browser freezes from time to time. This is latest firmware , wipe, cold start already ....
Click to expand...
Click to collapse
Unfortunately, that's normal. It gets a little better by installing a custom ROM, but software can only try to work around hardware issues (the internal eMMC has very bad random write performance), not fix them.

The only time I really notice it is if I'm using Sketchbook Pro, but I guess that may be a result of the application or something... It can be hard to draw with it sometimes, since I have to draw slower than I'd like at times.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

Rotation Broken

For some reason my rotation has stopped working and i can't seem to fix it. So far I have:
Restored to stock .23
Cold booted 3 times
Factory reset on stock twice
Auto rotate enabled
Used ultimate rotation control from store and that works
Checked sensors and those seem to be functioning
Any help is appreciated.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Bump! Hopefully someone can help

This really sucks no one knows whats up... Maybe I should exchange?

codyvance said:
This really sucks no one knows whats up... Maybe I should exchange?
Click to expand...
Click to collapse
You did pretty much everything that we could do. However, I have an idea, how about download this third party "Screen Orientation Control by eflow inc." app, once done open up notification and set it to portrait mode, then set it to landscape mode, then finally set it to off (auto) and see if it's working, if it stills not working, there's not much we can do except to return the device for repair/exchange.

buhohitr said:
You did pretty much everything that we could do. However, I have an idea, how about download this third party "Screen Orientation Control by eflow inc." app, once done open up notification and set it to portrait mode, then set it to landscape mode, then finally set it to off (auto) and see if it's working, if it stills not working, there's not much we can do except to return the device for repair/exchange.
Click to expand...
Click to collapse
Damn, I was hopeful, but it still won't rotate... It is weird too because at some point I was able to rotate, so I cant see it being a hardware issue, but I guess I will need to have ASUS repair/exchange.
Thank you for the suggestion though

[Nook HD+] Touchscreen sensitivity experimentation (updated GUI app on 07/13)

Thanks to some testing by @alal690 based on my instructions in the post on how to play with touchscreen sensitivity we have some suggested reduced sensitivity values.
I spent entire day figuring how to do more things in android apps, and here's my next terrible UI attempt: NookTouchscreenSensitivityAdjuster-4.apk (backup link).
It's recommended that you run it with 07/11 cm10.1 release, but it will work with older releases too, just all settings (all but touch sensitivity on 07/06) would reset on screen off.
This minimalistic tool would allow you to change various touchscreen parameters in GUI, so not need to play with adb.
Right now this tool just lets you to play with values, the new values persist until the screen turns off (and the touchscreen resets restoring to default values).
The "save" button only saves the sensitivity and focus settings at this time, and the values persists across reboots (important to grant it root access the first time you run it!), everything else is not saved anywhere (since I am not sure there's any value in that and only included the other settings so you can experiment with them and perhaps get back to me with your awesome finds).
save button only works with 07/06 release, in previous releases save button does not persist anything.
the "reset" button resets values to the "old" values in the touchscreen, meaning pre-sensitivity change (so to 0x11, instead of the new 0x16).
Old post:
Anyway, here's a test zip that you can flash to try the new value. I encourage everybody to try it both if you do and do not feel like you have a touchscreen sensitivity issue.
If there are no downsides (so far I see none on my end), we might make this one to be a standard new default.
touchscreen-test.zip - this is for Nook HD+ (noop on the Nook HD). (Note, this is now included into 6/30 build for ovation)
Do not flash into stock, it'll break it.
I know the raw TS settings is a bit intimidating, so I plan to make an app for that, though that's a bit more effort than what I have time for ATM, so we'll make do with just this topical treatment.

will this work with carbonrom also? i like to switch between them.

What about those of us who felt it wasn't sensitive enough? Is there some sort of weird effect where its so over-sensitive that it feels less sensitive?

Apk07 said:
What about those of us who felt it wasn't sensitive enough? Is there some sort of weird effect where its so over-sensitive that it feels less sensitive?
Click to expand...
Click to collapse
Try it and tell me what you find out.
Feel free to play with other register values as per that other post referenced if you can. No two devices are totally the same. So we'll need a significant amount of testing by all interested parties to come to some middle groumd
Either that, or an app where people would be able to setup volume, touchscreen and other settings for themselves, but we'd still need to have sensible defaults.

bckrupps said:
will this work with carbonrom also? i like to switch between them.
Click to expand...
Click to collapse
It probably will work there too, but I did not test it on anything but my setup.

verygreen said:
It probably will work there too, but I did not test it on anything but my setup.
Click to expand...
Click to collapse
i tried it on both. What a difference already. especially on stock browser. sometimes i wanted to smash the thing lol. you are one hell of a dev. scrolling takes a bit more work but clicking links is so much better now. sometimes i would click a link four or 5 times lol

verygreen said:
Thanks to some testing by @alal690 based on my instructions in the post on how to play with touchscreen sensitivity we have some suggested reduced sensitivity values.
Anyway, here's a test zip that you can flash to try the new value. I encourage everybody to try it both if you do and do not feel like you have a touchscreen sensitivity issue.
Click to expand...
Click to collapse
Can I just flash this zip from CWM... or do I need to do any of the other steps mentioned in the post on playing with touchscreen?

dbrickg said:
Can I just flash this zip from CWM... or do I need to do any of the other steps mentioned in the post on playing with touchscreen?
Click to expand...
Click to collapse
You just flash this one from cwm and you are good to go for just this particular setting change.

verygreen said:
You just flash this one from cwm and you are good to go for just this particular setting change.
Click to expand...
Click to collapse
Thanks. That's what I thought. So I went ahead and did it while I was waiting for your response. So far it seems just fine. I guess I don't notice any great deal of difference. But I'm not sure what the symptoms were that you were trying to cure. I can't figure out how to read any of the context around the link to the post you mention in the OP

dbrickg said:
Thanks. That's what I thought. So I went ahead and did it while I was waiting for your response. So far it seems just fine. I guess I don't notice any great deal of difference. But I'm not sure what the symptoms were that you were trying to cure. I can't figure out how to read any of the context around the link to the post you mention in the OP
Click to expand...
Click to collapse
Basically the problem is: there are multiple complaints about people having too sensitive/too insensitive touchscreens. I don't think I am seeing anything like that, but there is more than one report so perhaps different people have different tolerances and different hardware has it's quirks.
The goal here is to arrive at a different set of defaults that would improve the situation for people that feel there is a problem and at the same time don't make situation worse for everybody else who feels current settings are ok.

verygreen said:
Basically the problem is: there are multiple complaints about people having too sensitive/too insensitive touchscreens. I don't think I am seeing anything like that, but there is more than one report so perhaps different people have different tolerances and different hardware has it's quirks.
The goal here is to arrive at a different set of defaults that would improve the situation for people that feel there is a problem and at the same time don't make situation worse for everybody else who feels current settings are ok.
Click to expand...
Click to collapse
mine personally was very insensitive. when i'm on slickdeals and i know you are also or bleacher report clicking on links such as hot deals and my subscriptions would take multiple tries. i didn't notice much system wide but mostly on the internet clicking smaller links. whatever he did with this zip made mine personally much much better.

verygreen said:
Basically the problem is: there are multiple complaints about people having too sensitive/too insensitive touchscreens. I don't think I am seeing anything like that, but there is more than one report so perhaps different people have different tolerances and different hardware has it's quirks.
Click to expand...
Click to collapse
Aha... then I guess I *did* know about the problem. I noticed it most when reading books. After a few minutes, the page turning touches on the lower right margin would seem to stop. I finally just gave up even trying to use them, and substituted a swiping movement. Anyway, with this zip installed, the sensitivity doesn't seem to be any worse, and might well be better. It hasn't been very long, but I'll keep an eye open for differences.
PS: Just read some of the other people's posts, and see that they were complaining of difficulty in clicking links in web pages. I had certainly noticed that, but hadn't even thought of the possibility of fixing it, so had just ignored it. With this new zip, it does seem like web link sensitivity is much improved.

dbrickg said:
Aha... then I guess I *did* know about the problem. I noticed it most when reading books. After a few minutes, the page turning touches on the lower right margin would seem to stop. I finally just gave up even trying to use them, and substituted a swiping movement. Anyway, with this zip installed, the sensitivity doesn't seem to be any worse, and might well be better. It hasn't been very long, but I'll keep an eye open for differences.
PS: Just read some of the other people's posts, and see that they were complaining of difficulty in clicking links in web pages. I had certainly noticed that, but hadn't even thought of the possibility of fixing it, so had just ignored it. With this new zip, it does seem like web link sensitivity is much improved.
Click to expand...
Click to collapse
mine is much improved. whatever adjustments were made I feel like mine could go even a little more in that direction. I'm at like 85% now lol

Thanks, alal690! I think he deserves to get some "Thanks", too, but he doesn't have any posts! And thanks to verygreen for providing the tools for alal690 to tweak with, of course!

I have noticed more mistypes on the keyboard verygreen if you are still needing input but the positives outweigh that in my book. it really is much better on websites. please thank the other dev that worked on this also alal690.

Big improvement for me, thanks I suspect the issue with pressing ui elements was caused by jitter and phantom touches that may have been caused by oversensitivity even though it seems somewhat counterintuitive... Selecting text was the big issue for me and it's now vastly improved. As has my accuracy on they keyboard - normally I'd have had to retype half of a post this length

BTW, it woul be great if people with some sort of a protective film over the touchscreen will give this a try to make sure it's also ok for them (I know those screen protectors are really popular amongst some people).

I've spent the last week trying to fix this, but it looks like it could be a problem with a driver or the actual hardware itself. If you go to Dev tools, then Pointer Location, you can see the reported values for touch pressure and size. When holding down my finger anywhere on the top 2/3 of my screen, the xy and size values jitter like crazy. If I touch the bottom 1/3 of my screen, there is no jittering and the size value is constant.
I think people that are complaining about low sensitivity are mistaken. I think the touch screen response is actually too sensitive, thus causing the jitter and making it hard to click on hyperlinks.
Reducing the touch sensitivity scale and increasing the touch size in the IDC file has helped a lot, but the jitter is still a problem that I hope someone can figure out how to fix.
Sent from my BN NookHD+ using Tapatalk 4 Beta

phammichael said:
I've spent the last week trying to fix this, but it looks like it could be a problem with a driver or the actual hardware itself. If you go to Dev tools, then Pointer Location, you can see the reported values for touch pressure and size. When holding down my finger anywhere on the top 2/3 of my screen, the xy and size values jitter like crazy. If I touch the bottom 1/3 of my screen, there is no jittering and the size value is constant.
I think people that are complaining about low sensitivity are mistaken. I think the touch screen response is actually too sensitive, thus causing the jitter and making it hard to click on hyperlinks.
Reducing the touch sensitivity scale and increasing the touch size in the IDC file has helped a lot, but the jitter is still a problem that I hope someone can figure out how to fix.
Sent from my BN NookHD+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I agree with phammichael that the real issue here would be jittering, but my symptom is different.
This is what I found so far.
- Pinch out to zoom in something (in gallery or web browser) and hold the 2 fingers on the screen.
- If my fingers are on the right side of the screen surface (portrait mode), the screen jitters. You can see the touch values changing fast and continuously by tiny values.
- If my fingers are on the left side of the screen surface, the screen won't jitter and stay calm.
Am I the only one experiencing this issue?
BTW, this is before I applied verygreen's touch screen patch. I will report back after applying it.

pins2u said:
I agree with phammichael that the real issue here would be jittering, but my symptom is different.
This is what I found so far.
- Pinch out to zoom in something (in gallery or web browser) and hold the 2 fingers on the screen.
- If my fingers are on the right side of the screen surface (portrait mode), the screen jitters. You can see the touch values changing fast and continuously by tiny values.
- If my fingers are on the left side of the screen surface, the screen won't jitter and stay calm.
Am I the only one experiencing this issue?
BTW, this is before I applied verygreen's touch screen patch. I will report back after applying it.
Click to expand...
Click to collapse
The jittery right hand side of the screen in portrait mode is the problem - I have this on my HD+ (which was new) and my Dad has it on his (which was new) as does my friend (again a new unit)
There have also been lots of others reporting the same thing on here.
Put the HD+ into landscape mode and the issue disappears.
I've just applied verygreen's 'fix' zip and I have to say that touch response is loads better - clicking links etc works far more reliably (but right hand side of the screen in portrait mode jitters still exist)
Great work as usual verygreen

[Q] Touchscreen lateral movements delay (sensitvity Issue ?)

Hello, I have an issue with the touchscreen of my nvidia shield tablet.
I bought the tablet only one week ago and I'm on the Stock lollipop version 5.0.1 (2.2), but I had the same issue with the KitKat version.
When I hold my finger on the screen and I change direction, the shield take a long time (about 1 second) before validate this change of direction.
This issue make all my games unplayable in touch mode. (If I use a controller, this problem doesn't exist)
I wanted to post a video to show the problem but I can't because I'm a new user. (I can pm the link if necesserary)
On this video I activated, in the developer mode, the trace of the movement to see that the lines moves very late after my finger. (I'm doing the same test with LG G Pad to compare and see that it respond perfectly)
In the Real Racing Game: I move my finger with very little fast movements and the wheels doesn't move at all.
I tried the calibration tool in lollipop but the problem persists.
I tried also a Custom Rom ([ROM][4.4.2][wx_na_do] AOSP for Nvidia Shield Tablet LTE US)
My questions:
- Does every Nvidia Tablet Shield have this problem or is it only mine?
- Is there a way to configure the pressure and move sensitivity (from the config file /system/usr/idc/touch.idc)
I would like to know if someone has the same issue to know if I have to send back my tablet in warranty.
Thanks in advance for your time.

I've had this issue, but only while charging. More noticeably while charging using 3rd party chargers, though the nvidia charger does have some "lag" as well.

phuzznut said:
I've had this issue, but only while charging. More noticeably while charging using 3rd party chargers, though the nvidia charger does have some "lag" as well.
Click to expand...
Click to collapse
Thanks you for your answer.
I have always this problem, I never tried when the tablet is charging.
In fact the touchscreen is relatively responsive when I touch and release quickly.
The problem is when I let the finger on the touchscreen and I change the direction slowly with small moves.

Hello,
I re-up this post because I really need your help.
I sent back my tablet to the seller for my touchscreen issue.
But they don't undertsand and tell that there is no problem with the touchscreen.
They compared to another Nvidia shield and told me that the response is the same than mine.
I can't believe that all the Nvidia shield has the same response because for me all the games are unplayable.
So I would like to know if someone has the same feeling (delay) about the touchscreen when you slide and change laterally the direction with your finger to play games like racing or platform games.
Thanks in advance

Sorry if I open this again.
I've been going crazy with this issue too and have been looking around for a fix, too.
I tried applying different configurations to my /system/usr/idc/touch.idc file, without any noticeable differences.
The only setting that works for sure is 'touch.size.calibration': the possible values are "none | geometric | diameter | area | default". Whatever I set besides 'none' will make the touchscreen work like a touch pad (you scroll around and there's a little cursor moving, you tap and it taps on the cursor's location).
I'm not sure which setting (if any) can calibrate the touchscreen for small movements. The documentation is a little unclear (I only found this: https://source.android.com/devices/input/touch-devices.html ).
Does anyone know more about this configuration file? I believe it's a common issue for all the shield tablets, it would be great if we were able to fix this.
Please note that root is required to edit that file, of course. Plus, the /system partition needs to be writable (mount -o rw,remount /system).

Same issue on new k1

Same issue on K1
I purchased an new K1 today and am experiencing the same issue. After enabling "show touches" in developer options it is very clear that the display periodically becomes unresponsive. I have also tried to re-calibrate the display with the Sensor Calibration Utility with no change. This happens while NOT connected to a power supply. So, I'm not sure what else to try.
What have others done about this issue? Do you return the device to the reseller? Because as it is, I can't play most games and find a typical browsing experience annoying.
Thanks in advance for any advice.

After trying everything, including full wipe, different Rom etc, I have returned it to the reseller. I got another one and and am very happy with it. Turning screen off and back on gets the responsiveness back for a while. Good luck with swapping it for new one, reseller I dealt with made no issue of it.As I have restored tablet to factory settings,I have just shown a video of a tablet going all crazy to a guy at the counter, and he gave me a new one.

Acidicus said:
After trying everything, including full wipe, different Rom etc, I have returned it to the reseller. I got another one and and am very happy with it. Turning screen off and back on gets the responsiveness back for a while. Good luck with swapping it for new one, reseller I dealt with made no issue of it.As I have restored tablet to factory settings,I have just shown a video of a tablet going all crazy to a guy at the counter, and he gave me a new one.
Click to expand...
Click to collapse
Thanks. I appreciate you sharing your experience on this. I got it from Amazon, so I hope they are cool with it.

Xperia XZ firmware 41.2.A.7.8 – keyboard issues!

Hi guys!
I've updated to 41.2.A.7.8 but the one bug I hate the most on this device is still here on Android 7.1.1 – some of the keypresses are recognized as a straight swipe line when typing fast and thus Swiftkey keeps assuming wrong words. This happened as well on all past firmware versions I’ve tried.
You can easily check this behaviour by entering *#*#SERVICE#*#* on your dialer, choose Service Tests, then Touch, then Free Drawing test, and then pretending you're typing (both thumbs) at high speed.
This is even more evident when you are using Stamina mode, and more so in the more aggressive Stamina options, which leads me to believe it’s processor dependent. Xperia X also had this very same bug but was corrected with firmware updates so… come on, Sony! Stop screwing things up!

MegaSharkXDA said:
Hi guys!
I've updated to 41.2.A.7.8 but the one bug I hate the most on this device is still here on Android 7.1.1 – some of the keypresses are recognized as a straight swipe line when typing fast and thus Swiftkey keeps assuming wrong words. This happened as well on all past firmware versions I’ve tried.
You can easily check this behaviour by entering *#*#SERVICE#*#* on your dialer, choose Service Tests, then Touch, then Free Drawing test, and then pretending you're typing (both thumbs) at high speed.
This is even more evident when you are using Stamina mode, and more so in the more aggressive Stamina options, which leads me to believe it’s processor dependent. Xperia X also had this very same bug but was corrected with firmware updates so… come on, Sony! Stop screwing things up!
Click to expand...
Click to collapse
It's an issue with Sony moving to swiftkey as stock. Sony's own keyboard worked much better on older versions, you can still use it on Nougat, but it's a bit slower in touch response. This is why I use Gboard. If I could disable predictive engine in swiftkey, I wouldn't mind using it that much, it's annoying and I hate that blank bar above the keys, uses up the screen space. I also don't use gesture typing in any form, so the old stock xperia keyboard was always my favorite.
Ditch swiftkey, try something else and see if it's better. The issues people describe with keyboards in 7.0+ are non-existant for me. Or at least disable the gesture typing in swiftkey settings. But still, the predictive engine makes it laggy and glitchy, even though it is by far the best predictive and gesture keyboard out there.
The free drawing test isn't really a good measurement here, it's for drawing lines, not tapping. Use tap test and you'll see no matter how fast you tap, the digitizer registers taps. When you tap on the drawing screen and manage to tap a single pixel without touching the next one, it will stay black, it looks like it didn't register a tap.
The keyboard, and the entire UI in general, being laggy and slower in touch response while using Stamina actually makes sense and is completely normal. It lowers the screen refresh rate, the touch responsiveness and the framerate of the rendered content.

Atrax2010 said:
It's an issue with Sony moving to swiftkey as stock.
Click to expand...
Click to collapse
No it is not. This is an issue with the way touch screen inputs are processed, regardless of the keyboard you are using.
Atrax2010 said:
Ditch swiftkey, try something else and see if it's better.
Click to expand...
Click to collapse
It isn’t better. Every other keyboard behaves exactly the same when the wrong inputs are interpreted.
Atrax2010 said:
The issues people describe with keyboards in 7.0+ are non-existant for me.
Click to expand...
Click to collapse
These issues existed for Xperia XZ on 6.0 as well.
Atrax2010 said:
Or at least disable the gesture typing in swiftkey settings.
Click to expand...
Click to collapse
That is even worse because when you disable gesture swiping, right to left (wrong) swipes are interpreted as deleting the previous word.
Atrax2010 said:
The free drawing test isn't really a good measurement here, it's for drawing lines, not tapping. Use tap test and you'll see no matter how fast you tap, the digitizer registers taps.
Click to expand...
Click to collapse
No, really, free drawing test is exactly what we’re after here.
Atrax2010 said:
The keyboard, and the entire UI in general, being laggy and slower in touch response while using Stamina actually makes sense and is completely normal. It lowers the screen refresh rate, the touch responsiveness and the framerate of the rendered content.
Click to expand...
Click to collapse
When these touch screen issues were solved for Xperia X, you got perfect typing behavior even when Stamina mode was on.

MegaSharkXDA said:
No it is not. This is an issue with the way touch screen inputs are processed, regardless of the keyboard you are using.
It isn’t better. Every other keyboard behaves exactly the same when the wrong inputs are interpreted.
These issues existed for Xperia XZ on 6.0 as well.
That is even worse because when you disable gesture swiping, right to left (wrong) swipes are interpreted as deleting the previous word.
No, really, free drawing test is exactly what we’re after here.
When these touch screen issues were solved for Xperia X, you got perfect typing behavior even when Stamina mode was on.
Click to expand...
Click to collapse
I don't see the keyboard issues when using gboard or atock xperia keyboard, although the stock one is a bit slower in response, so I don't use it.
The way it behaves under Stamina seems normal to me because it's how my ex z3 and z5 behaved and it makes sense. The performance of the phone is reduced, ofcourse it will be less responsive and laggy.
Not until we recieved the swiftkey, I havent seen this issue.
The way they "fixed" the tapping responsivness on the X was by not using so restrictive and conservative stamina profile, it didn't reduce the digitizer responsivness as much. It's a battery saving mode, after all, you can't have both with equal efficiency.
I'm sure they could do the same with the xz, but it would mean affecting battery life as well well.
Free drawing test makes no sense if you are testing tapping speed...
Or are people complaining about swipe input? If that's the case, than drawing test would be useful. For normal tapping on the keyboard, I see no issues.

Atrax2010 said:
I don't see the keyboard issues when using gboard or atock xperia keyboard, although the stock one is a bit slower in response, so I don't use it.
The way it behaves under Stamina seems normal to me because it's how my ex z3 and z5 behaved and it makes sense. The performance of the phone is reduced, ofcourse it will be less responsive and laggy.
Not until we recieved the swiftkey, I havent seen this issue.
The way they "fixed" the tapping responsivness on the X was by not using so restrictive and conservative stamina profile, it didn't reduce the digitizer responsivness as much. It's a battery saving mode, after all, you can't have both with equal efficiency.
I'm sure they could do the same with the xz, but it would mean affecting battery life as well well.
Free drawing test makes no sense if you are testing tapping speed...
Or are people complaining about swipe input? If that's the case, than drawing test would be useful. For normal tapping on the keyboard, I see no issues.
Click to expand...
Click to collapse
Looks like you haven't even actually tried the Drawing Test yourself...
Some of the taps are recognized as a straight swipe line when typing fast and so this problem will always be present regardless of the keyboard software you're using.

Can anyone check this is still present on 41.2.A.7.35?

MegaSharkXDA said:
Looks like you haven't even actually tried the Drawing Test yourself...
Some of the taps are recognized as a straight swipe line when typing fast and so this problem will always be present regardless of the keyboard software you're using.
Click to expand...
Click to collapse
I have tried the drawing test when I read the post, also the tapping test, otherwise I wouldn't even engage in the conversation.
The lines in the drawing test do not appear on my unit, when I tap quickly on the drawing test it doesn't draw these huge lines.
Does this happen in normal mode as well or only in stamina? Cause I didn't try in stamina.
I'm on Customized CE 41.2.A.7.8, and the device is rev.1

Atrax2010 said:
I have tried the drawing test when I read the post, also the tapping test, otherwise I wouldn't even engage in the conversation.
The lines in the drawing test do not appear on my unit, when I tap quickly on the drawing test it doesn't draw these huge lines.
Does this happen in normal mode as well or only in stamina? Cause I didn't try in stamina.
I'm on Customized CE 41.2.A.7.8, and the device is rev.1
Click to expand...
Click to collapse
You have to type even faster
This happens in normal mode as well as in stamina mode, but it becomes much more frequent in Stamina mode - in fact it becomes more noticeable the more aggressive the Stamina mode chosen.

MegaSharkXDA said:
You have to type even faster
This happens in normal mode as well as in stamina mode, but it becomes much more frequent in Stamina mode - in fact it becomes more noticeable the more aggressive the Stamina mode chosen.
Click to expand...
Click to collapse
I was tapping as fast as I could, faster than I would normally while typing a message.
But I guess I'm doing something wrong or I'm just a slowass typer so I don't see the issue.
Good luck eith yours, I hope you solve the issue or Sony fixes it.
Maybe start off by doing a full software reflash to a latest version released today? See if it helps maybe...
Cheers

MegaSharkXDA said:
Hi guys!
I've updated to 41.2.A.7.8 but the one bug I hate the most on this device is still here on Android 7.1.1 – some of the keypresses are recognized as a straight swipe line when typing fast and thus Swiftkey keeps assuming wrong words. This happened as well on all past firmware versions I’ve tried.
You can easily check this behaviour by entering *#*#SERVICE#*#* on your dialer, choose Service Tests, then Touch, then Free Drawing test, and then pretending you're typing (both thumbs) at high speed.
This is even more evident when you are using Stamina mode, and more so in the more aggressive Stamina options, which leads me to believe it’s processor dependent. Xperia X also had this very same bug but was corrected with firmware updates so… come on, Sony! Stop screwing things up!
Click to expand...
Click to collapse
Do you have facebook messengers installed ?

100rabh7791 said:
Do you have facebook messengers installed ?
Click to expand...
Click to collapse
No

Atrax2010 said:
I was tapping as fast as I could, faster than I would normally while typing a message.
But I guess I'm doing something wrong or I'm just a slowass typer so I don't see the issue.
Good luck eith yours, I hope you solve the issue or Sony fixes it.
Maybe start off by doing a full software reflash to a latest version released today? See if it helps maybe...
Cheers
Click to expand...
Click to collapse
Just asked in a different thread whether 41.2.A.7.35 corrects this issue

MegaSharkXDA said:
Just asked in a different thread whether 41.2.A.7.35 corrects this issue
Click to expand...
Click to collapse
Unfortunately, 41.2.A.7.35 still shows this bug.