Xperia XZ firmware 41.2.A.7.8 – keyboard issues! - Sony Xperia XZ Questions & Answers

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.

Related

[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] General Interface Lag

Hello everyone!
I have just received a brand new T-mobile branded Z3. I am coming from a Nexus 5 which I absolutely loved minus the camera and battery life. So far I am really enjoying the Z3 and most everything seems to run great, other then just general interface navigation. It seems that scrolling, web surfing, facebook, or anything that requires lots of scrolling, just seems to be extremely laggy compared to my Nexus 5. I have tried Nova, Google Now Launcher, Stock Xperia Launcher, and everything just seems to have general lagginess about it.
Does anyone experience this as well? If so, any suggestions for what I might try? I'm not running in stamina mode and see no difference in general interface performance between the two modes. I really want to enjoy everything that the Z3 has, but the lag is getting to me and maybe I am just expecting too much. Thanks in advance for any details or suggestions.
Seems pretty fluid till now, no lag here.
Seems odd have you tried a full reset?
abhinav.tella said:
Seems pretty fluid till now, no lag here.
Seems odd have you tried a full reset?
Click to expand...
Click to collapse
Yea, I find it odd as well. I am proceeding with a full factory reset to see if this helps out a bit. I will report back. Thanks for your suggestion.
No lag at all for me, although I have the standard D6603 model, but I am running go launcher ex which is quite intensive - what's your running/outstanding RAM within the apps section of the settings menu? I'm also running CM (Clean Master) Battery which gives you an option to close the most recent app within that app's settings. It's a one click feature that flashes up whenever you exit anything that doesn't close automatically, and it's not overly intrusive.
Did you disable triple tap to zoom? Mine was off by default but some had it enabled and it caused lags.
abhinav.tella said:
Did you disable triple tap to zoom? Mine was off by default but some had it enabled and it caused lags.
Click to expand...
Click to collapse
Well, I performed a factory reset and that seems to have helped and my battery is noticeably even better from what it was, which was already great. It appears that triple tap to zoom is disable for me. Thanks for the suggestion!
Glad things worked out.

Multitouch/screen issue ?

Hi there,
I just received my new Mi MIX 2S (actually, I got it 360 hours ago, if you know what I mean...) and I'm very satisfied with this toy
I'm on the last MIUI 10 Global Beta (8.7.5) since this afternoon, with SuperSU v2.82-SR5 and of course, with an unlocked bootloader.
However, I noticed a "strange" glitch/issue when I quick touching/typing.
It's seems that the screen not considering the different touch but acts like it does "two in one" touch.
I made a small video to illustrate the issue :
https://youtu.be/NdW8Zeo1MLQ
Does anyone has this too ?
Do you think it's an hardware or a software issue (like calibrate or touch-delay update) ?
Thanks
lafritte57 said:
Hi there,
I just received my new Mi MIX 2S (actually, I got it 360 hours ago, if you know what I mean...) and I'm very satisfied with this toy
I'm on the last MIUI 10 Global Beta (8.7.5) since this afternoon, with SuperSU v2.82-SR5 and of course, with an unlocked bootloader.
However, I noticed a "strange" glitch/issue when I quick touching/typing.
It's seems that the screen not considering the different touch but acts like it does "two in one" touch.
I made a small video to illustrate the issue :
https://youtu.be/NdW8Zeo1MLQ
Does anyone has this too ?
Do you think it's an hardware or a software issue (like calibrate or touch-delay update) ?
Thanks
Click to expand...
Click to collapse
Hardware issue, I have the same issue.
https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/miui-im-swiping-t3803874
Damn... I bought mine on Joybuy, I'll try to deal with them about the warranty because I guess I can't contact Xiaomi directly.
The XDA Gesture workaround seems to be a good temporary way but, I really don't want to stay on a defective device...
I already did this with my Oneplus One (as a early buyer, I got a similar issue) and it was worst with time, I regret to had never return them
lafritte57 said:
Damn... I bought mine on Joybuy, I'll try to deal with them about the warranty because I guess I can't contact Xiaomi directly.
The XDA Gesture workaround seems to be a good temporary way but, I really don't want to stay on a defective device...
I already did this with my Oneplus One (as a early buyer, I got a similar issue) and it was worst with time, I regret to had never return them
Click to expand...
Click to collapse
Bought mine on Aliexpress, no way I'll get a warranty without me paying $30 of shipping and lose a month without the phone.
I tried the XDA gesture thing, but you can't really get the same gestures as on MIUI (alsway have to make the gestures from the bottom of the phone it seems). So for now I'm just using it with this "bug", with the keyboard closing from time to time when I type.
Probably gonna get a Mi Max 3 to replace it anyway sooner or later.
I just made the thest you did with a drawing app and I got the same results when I multi touched the screen very quickly. I hadn't noticed this earlier because it didn't cause any problem for my daily use. Specifically, in which context did you notice that issue?
hayatesan said:
Bought mine on Aliexpress, no way I'll get a warranty without me paying $30 of shipping and lose a month without the phone.
I tried the XDA gesture thing, but you can't really get the same gestures as on MIUI (alsway have to make the gestures from the bottom of the phone it seems). So for now I'm just using it with this "bug", with the keyboard closing from time to time when I type.
Probably gonna get a Mi Max 3 to replace it anyway sooner or later.
Click to expand...
Click to collapse
I guess JoyBuy has the same warranty policy, which means cost return and more than a month without phone...
I haven't tried the XDA Gesture workaround yet, but I'm not too happy about losing the MIUI gesture
Hope that's JoyBuy will be understanding...
rodaven said:
I just made the thest you did with a drawing app and I got the same results when I multi touched the screen very quickly. I hadn't noticed this earlier because it didn't cause any problem for my daily use. Specifically, in which context did you notice that issue?
Click to expand...
Click to collapse
Thanks for your test and your answer.
In my case, it's very annoying when I (fast) typing a message, it causes a "fake" swipe and recude the keyboard or go back to home screen. I'll try to make a better screencast to show you in-use case.
lafritte57 said:
I guess JoyBuy has the same warranty policy, which means cost return and more than a month without phone...
I haven't tried the XDA Gesture workaround yet, but I'm not too happy about losing the MIUI gesture
Hope that's JoyBuy will be understanding...
Thanks for your test and your answer.
In my case, it's very annoying when I (fast) typing a message, it causes a "fake" swipe and recude the keyboard or go back to home screen. I'll try to make a better screencast to show you in-use case.
Click to expand...
Click to collapse
Fine, I'll tell you my experience. I use to had the same problem, it's only noticeable using the keyboard and specially when you tap the letters located near the edge of the screen, specially like the Q and P. I'm almost completely sure that the problem is related to gestures, because the system thinks you're swiping, in my case I got some lag too in addition to the false back gesture. What I did to fix this is use the keyboard (Google keyboard) in one hand mode (long press the "," and this option will pop up next to the emoticon) and moving it to the center and the problem is gone. It's actually more comfortable this way because the space bar moves up and it's more accessible. You can play then with the keyboard size if you think it's too small. There are two others threads talking about the same problem and I recommended this solution in both, and it seems to work for others too. Try it and tell us.
https://forum.xda-developers.com/showpost.php?p=76789600&postcount=13
I have this issue too, are you sure it's a hardware problem and it does not affect everybody?
Thank you.
stark0 said:
I have this issue too, are you sure it's a hardware problem and it does not affect everybody?
Thank you.
Click to expand...
Click to collapse
Hi,
Actually, I think it's more an OS issue than an hardware one.
After some tries and research, I noticed that these "screen glitches" are bad interpretations of fast multitouching, translate into swipe/gesture.
These swipe/gesture come with the gesture navigation mode, included in full-screen desplay (and which allow to hide the bottom navigation bar).
If you re-enable the "classic" display, with the bottom bar, the issue doesn't seem to exist. So, I guess for MIUI, some fast-typing/touching are interpreted as gestures (swipe down-to-up = home, left-to-right = previous...)
In the same registry, I noticed that, if you use a scrollable widget (Google Agenda in planning display) and if you scroll down on it (in order to see the bottom lines for example), MIUI interpret it as a down-to-up gesture (and so, go back to home, or search).
So, I really hope that in a future update, the sensibility of these gestures could be decreased/improved...
For now, you could :
Enable the one-hand mode ok Google Keyboard as proposed by @rodaven (but personnaly, I dislike the fact to have a small keyboard with a lot of lost space around it...)
Disable the full sceen display mode (and so, say goodbye to the gestures feature)
Stay on full screen mode and gestures, get upset when you write a message and pray for un update
lafritte57 said:
Hi,
Actually, I think it's more an OS issue than an hardware one.
After some tries and research, I noticed that these "screen glitches" are bad interpretations of fast multitouching, translate into swipe/gesture.
These swipe/gesture come with the gesture navigation mode, included in full-screen desplay (and which allow to hide the bottom navigation bar).
If you re-enable the "classic" display, with the bottom bar, the issue doesn't seem to exist. So, I guess for MIUI, some fast-typing/touching are interpreted as gestures (swipe down-to-up = home, left-to-right = previous...)
In the same registry, I noticed that, if you use a scrollable widget (Google Agenda in planning display) and if you scroll down on it (in order to see the bottom lines for example), MIUI interpret it as a down-to-up gesture (and so, go back to home, or search).
So, I really hope that in a future update, the sensibility of these gestures could be decreased/improved...
For now, you could :
Enable the one-hand mode ok Google Keyboard as proposed by @rodaven (but personnaly, I dislike the fact to have a small keyboard with a lot of lost space around it...)
Disable the full sceen display mode (and so, say goodbye to the gestures feature)
Stay on full screen mode and gestures, get upset when you write a message and pray for un update
Click to expand...
Click to collapse
Thank you so much!
I have the gestures disabled because of that but it still happens in the keyboard (I don't like the one-hand mode). So, we need to wait hoping it'll be solved.
stark0 said:
Thank you so much!
I have the gestures disabled because of that but it still happens in the keyboard (I don't like the one-hand mode). So, we need to wait hoping it'll be solved.
Click to expand...
Click to collapse
I just found that this issue was submit on MIUI website in January : http://en.miui.com/thread-1539964-1-1.html
lafritte57 said:
I just found that this issue was submit on MIUI website in January : http://en.miui.com/thread-1539964-1-1.html
Click to expand...
Click to collapse
But that's different from the multitouch issue that is in the main post (https://www.youtube.com/watch?v=NdW8Zeo1MLQ&feature=youtu.be), isn't it?
stark0 said:
But that's different from the multitouch issue that is in the main post (https://www.youtube.com/watch?v=NdW8Zeo1MLQ&feature=youtu.be), isn't it?
Click to expand...
Click to collapse
In my opinion, it's the same issue.
Due to the full screen/gesture feature, fast multitouches are interpreted as a gesture.
On my video, you could see it.
On the issue from MIUI website, users asked that swipe/gesture are disable over keyboard when it's on-screen.
I think it should be a solution to combine gesture navigation and fast multitouch/type.
Personnaly, I disable full screen/gesture navigation (for now, sadly) and the issue desappear, that's why I'm pretty sure it's a software issue (which concern very model with this feature).
I changed my screen
Actually i cracked my screen and replaced new lcd from aliexpress claimed original. I checked it is JDI. But the touch issues still persist. I think its xiaomi driver.. or i dont know.. i really regret having this phone
lafritte57 said:
In my opinion, it's the same issue.
Due to the full screen/gesture feature, fast multitouches are interpreted as a gesture.
On my video, you could see it.
On the issue from MIUI website, users asked that swipe/gesture are disable over keyboard when it's on-screen.
I think it should be a solution to combine gesture navigation and fast multitouch/type.
Personnaly, I disable full screen/gesture navigation (for now, sadly) and the issue desappear, that's why I'm pretty sure it's a software issue (which concern very model with this feature).
Click to expand...
Click to collapse
I tested more, disabling fulls creen gestures and the problem persist. There is a video with the keyboard trying to type "alguna", sometimes it makes a gesture "left to right":
https://www.youtube.com/watch?v=N8EgUfaN5C0
It's very disapointing, I had touch screen problems with my oneplus one and now with the mix 2s.

Android 10 [Q] Features Report/Feedback

So I know there are other android 10 threads out there but I felt like y'all should get a list of whats new in front of your eyes instead of looking around:
**Improved night camera quality - Yes I have felt and improvement it is slight however, but it did get somewhat better.
**Google's new navigation gestures (I felt like I should write this because last updates, Sony phones did not get the nav gestures) however the new gestures seem just a tiny bit laggy -rarely though- and when in landscape mode, the slide down bar drops not in a symmetric way but rather drops right sided which makes things look out of place
**New CinemaPro app features - the app now has the levels of both phone microphones like on the v50 and also has aspect ratio check lines (if you want to shoot a video on cinema pro it only shoots 21/9 but you can have check lines to see whats being viewed in any other aspect ratio you choose and you also have a meter inside the camera to show you if youre in the frame or not)
**Dark mode - works on most apps, but I can't seem to activate it on my phone app, any suggestions?
**UI click sounds changed - yup! I love the new ones they sound more like Android rather than Sony and I do love Android!
**FINGERPRINT!!!! - Yes!! finally fingerprint scanner is way more responsive now!! before it was sooo strict about the cleanness and the angle, I registered 3 fingers and it only could recognize one of them because of the angle it provides, but now every finger on any angle with less cleanness is verry responsive! (could still be worked on, but im so happy with it at this moment)
**Sadly no more face unlock, even though I never used it but it worked surprisingly fast when I had the option available, but now it doesnt exist, good thing they improved the fingerprint scanner XD
**Slightly improved battery life - I only noticed it when I tested it, but if youre not a detailed tester you wont be able to recognize throughout the day, maybe if youre a slight user, yes you will notice the phone lasting 2/3 hours longer (overall usage and not screen on time) because I can tell they worked greatly on improving the idle drain.
**Speaker loudness - I think the phone got louder? I am not sure but defiantly notice something that didnt exist, not necessarily higher quality but I do notice something increasing in volume I cant tell if its volume or distortion lol but when I go to max volume there is something that makes you think, a little lower than max sounded like max on previous android but I cant tell if max here is actually louder or just more noisy especially with dolby atmos
**Some people reported signal drops? or bad signal? I havent noticed a difference here so thats good news
**Performance - the phone was fast enough to almost be the king of speed and smoothness so yah even if its better on android 10 I cant even feel the difference but it is VERY smooth even on a new android which means its pretty sick!
**Recent apps button (in old school 3 button nav bar) doesnt seem to do anything if you have custom launcher, but works on default sony launcher.
UPDATE!!
**one handed mode, which I use alot when im in bed, cant seem to be activated in the new navigation gestures, because you have to double tap home button but u dont have it in new gestures, so heres what i did:
Enabled side sense, i know it doesn't work properly, but now you have an option of controlling how to access it, You can actually enable the inside the screen tap rather than from the side (if you have a case on, this will really help you) , adjust sensitivity, position, transparency of the slide activators, and change the gestures of how it works, now i changed the double tap side sense from opening the side sense menu, to activate one handed mode, and now side sense works smoothly with gestures and i can activate one handed mode in new android nav gestures, youre welcome
Thx u for this thread
UI seems a lot smoother. I'm liking the android 10 gestures which adds to the "smoothness".
Can't really say about photo quality, haven't been using the camera much. I can definitely notice a better battery life compared to before.
Basically no issues just yet! Aside from me getting used to the new gestures (+ side sense)
Im using the google dialer app in play store. It has a way better ui, better icons and dark mode compatible. Set it as default and it's all good. I don't understand why sony have decided to use the "stock" google messenger app but not dialer... the dialer seems customized in some way idk
There is a bug that I noticed: when going back home using the gesture, if the app icon is on the dock, the icons a bit laggy and will flash for once. don't really know how to describe it
Someone can make a full review of android 10 and post it on youtube ?
Sugarcube8th said:
Im using the google dialer app in play store. It has a way better ui, better icons and dark mode compatible. Set it as default and it's all good. I don't understand why sony have decided to use the "stock" google messenger app but not dialer... the dialer seems customized in some way idk
There is a bug that I noticed: when going back home using the gesture, if the app icon is on the dock, the icons a bit laggy and will flash for once. don't really know how to describe it
Click to expand...
Click to collapse
Yah you just reminded me to add that bug, also if you on landscape mode the slide down bar is off place slides from the right rather than the middle of the screen
Pandemic said:
Someone can make a full review of android 10 and post it on youtube ?
Click to expand...
Click to collapse
I will try to do so soon, when I have free time from work
Agree with you.
- about the signal, i notice less signals bar (1-2 signal bars most of the time), but no connection drop (yet)
- wifi Mac address new option, set by default at "random Mac address"
Here's a preview of the swipe up animation bug?
https://youtu.be/ZM0Exs9F4yQ
Does anyone else have a weird audio bug where when you pause music or a video the sound spikes up for a second before it pauses. I've only tested it on the native music app and YouTube. I don't use any music streaming service such as Spotify or Pandora. I think I've concluded that this is a software bug since I when I flashed back to the previous firmware and didn't have the same problem. Maybe my device is just strange. Any opinion?
Arsyian said:
Does anyone else have a weird audio bug where when you pause music or a video the sound spikes up for a second before it pauses. I've only tested it on the native music app and YouTube. I don't use any music streaming service such as Spotify or Pandora. I think I've concluded that this is a software bug since I when I flashed back to the previous firmware and didn't have the same problem. Maybe my device is just strange. Any opinion?
Click to expand...
Click to collapse
Yes,I have the same issue, but as I remember this issue also existing on Pie.
t238z said:
Yes,I have the same issue, but as I remember this issue also existing on Pie.
Click to expand...
Click to collapse
That's strange cause I never had the problem till updating to Android 10.
I think i have a bug i have notification from album that i cant remove it. Even though i have restar my phone
It always check the update
blegs said:
I think i have a bug i have notification from album that i cant remove it. Even though i have restar my phone
It always check the update
Click to expand...
Click to collapse
this happens with me with BG player.. I simply turned off its notifications
Sugarcube8th said:
There is a bug that I noticed: when going back home using the gesture, if the app icon is on the dock, the icons a bit laggy and will flash for once. don't really know how to describe it
Click to expand...
Click to collapse
Precisely, IDK if that happens with pixel or one plus devices, but I know that it happens with Xperia 1. When you go back to the app, let's just say it's inside a folder, app shows in the dock then the folder pops back. Then if you open an app let's just say dialer then you switch to camera with recent menu and you go back to home screen it shows dialer app on where the camera icon then you get the camera icon back in the dock. Am I right?
[Bug report] Recent key not working in Android 10.
Screenshot as below: https://www.youtube.com/watch?v=hUlHZ0weCfs&feature=youtu.be
When you press Recent button, there is just nothing.
Remember people more updates will vome of android 10, this is the 1st release so except some tiny bugs. Sony/google will fix that
just added some more updates about bugs and updates in main post check it out
kevinkoo said:
[Bug report] Recent key not working in Android 10.
Screenshot as below: https://www.youtube.com/watch?v=hUlHZ0weCfs&feature=youtu.be
When you press Recent button, there is just nothing.
Click to expand...
Click to collapse
whats that launcher?
Just got mine an hour ago. Hoping that I don't experience those bugs.

All issues Android 10 update xz2 compact

I think it would be useful to have a collection of all bugs of the android 10 update. From my point of view it is a disaster.
I noticed the following (after I factory reset it) :
Touch issues - touching the screen lightly does nothing. I have the actually tap it... This makes writing a pain, as hard to reach keys do not always register
Backlight auto adjustment issues - now it's very aggressive and basically stupid. I'm sitting in home, in the evening, almost without moving, definetly in the same spot and the backlight just jumps around in big increments
Lag and shutter in daily usage - a restart solves this for a couple of hours...
apps are now often reloaded - memory manager is too agresive and kills background apps
GPS NOT WORKING. It was flawless before update ?
build-in swiftKey keyboard does NOT remember how and where you type IF you change the keyboard layout /position (compact, split, side, etc...). This essentially makes it useless
A factory reset is not enough , try software repair using Sony companion
Im not having touch or GPS issues, but my phone is definitely slower and laggier since the upgrade to android 10. ALso my battery seems to be depleting faster. Is there any way to roll back to 9?
veverone said:
I think it would be useful to have a collection of all bugs of the android 10 update. From my point of view it is a disaster.
I noticed the following (after I factory reset it) :
Touch issues - touching the screen lightly does nothing. I have the actually tap it... This makes writing a pain, as hard to reach keys do not always register
Backlight auto adjustment issues - now it's very aggressive and basically stupid. I'm sitting in home, in the evening, almost without moving, definetly in the same spot and the backlight just jumps around in big increments
Lag and shutter in daily usage - a restart solves this for a couple of hours...
apps are now often reloaded - memory manager is too agresive and kills background apps
GPS NOT WORKING. It was flawless before update
build-in swiftKey keyboard does NOT remember how and where you type IF you change the keyboard layout /position (compact, split, side, etc...). This essentially makes it useless
Click to expand...
Click to collapse
Wifi is often lost and quickly reconnects
fingerprint sensor isn´t as sensitive as it was before
battery drain is bigger than before
bluetooth pairing with tablet doesn´t work properly...being paired: YES, but no connection at all...tried three different tablets...bluetooth headphones work!
The camera application is crashing when I take photos.... :crying:
I really haven't faced any of those issues. The fingerprint is the only things that have become laggy, the phone is louder now when playing music, camera works great even with unlocked bootloader.
You should try to do a clean install with newflasher my phone is even rooted and works great.
carloszf said:
Im not having touch or GPS issues, but my phone is definitely slower and laggier since the upgrade to android 10. ALso my battery seems to be depleting faster. Is there any way to roll back to 9?
Click to expand...
Click to collapse
Scratch that... I am experiencing all the issues from OP's post. It is especially severe when trying to use two apps at the same time in split screen.
Sony mobile engineers answer my bug report
Android Beam doesn't work (transferring files by touching two phones with NFC).
Nothing works on this phone any more!
I will never buy another Sony phone and surely I will advice others against buying such sh*t.
------------------
I contacted the Sony support in my country and they said "the download must have been corrupt" and I "should try to reinstall" via the Xperia companion (some kind of desktop app).
Mind boggling is the fact that this answer comes "directly from Sony engineers".
Now... I guess it is clear for everyone why they f*ucked this phone so bad. Their engineers think that a corrupt file can 1) be installed successfully 2) cause all these bugs...
Hamzakovsky said:
A factory reset is not enough , try software repair using Sony companion
Click to expand...
Click to collapse
Why factory reset is not enough?
If the corect procedure is to use that "companion", WHY they pushed the update via OTA?
veverone said:
Why factory reset is not enough?
If the corect procedure is to use that "companion", WHY they pushed the update via OTA?
Click to expand...
Click to collapse
The only brand who has this crappy issue is Sony ! Companion fills all the missing files or damaged files .. during the ota download and installation sometimes things go wrong
For everyone reading this thread: there is no such thing as instalation with corrupt or missing files.
All files in today's IT world are uniquely identified and double checked after download.
Their answear is only a way of not telling us that they f*cked up this + they think that we are stupid. Some of us might be fooled by this, but surely the majority won't be.
We have primarily the camera issue, a reboot resolves it temporarily.
Anyone managed to fix these issues with a fresh Sony companion install?
52.1.A.0.618 here. Fingerprint is slower and the battery drains faster while screen on. (Standby and deep sleep are both ok). Everything else is the same as Pie, at least for me.
Add me to list of unhappy xz2 compact owners. Phone is almost unusable since the update. More often than not the finger scanner only works when you press the power button first, it lags awfully in most apps, I get errors in apps I never did before, battery drain is about the same as previous. Overall this is my last Sony. Very very poor. Should add I did full companion restore and it made zero difference
I have to add my voice to this thread, short as it happily/sadly is. Since the update I've experienced a number of issues: Fingerprint scanner is less sensitive and sometimes doesn't work, the wake-up procedure is strange, in that the icons will appear before the background loads and even though I have security set to not show notification details on the lock screen, they'll reveal for a split second before waking up to the home screen, the camera is unreliable, the timer app doesn't reset or dismiss when appearing on the notification bar..
It's the first time I've ever emailed Sony Support on what was (and I hope still will be) my favourite ever phone. They of course just tell me to factory reset. Such a shame and I hope they fix it.
majorwedgy said:
Add me to list of unhappy xz2 compact owners. Phone is almost unusable since the update. More often than not the finger scanner only works when you press the power button first, it lags awfully in most apps, I get errors in apps I never did before, battery drain is about the same as previous. Overall this is my last Sony. Very very poor. Should add I did full companion restore and it made zero difference
Click to expand...
Click to collapse
I'm having the same issue. Not sure what is wrong. I have not factory restored my phone. That is ridiculous
I also add the bug of Google Assistant in Stamina Mode:
I always keep It disabled when long press home button, but when Stamina Mode turns on, Google Assistant switches on again automatically although in settings shows that is off.
wow its been 2 years since I bought the XZ2C, had issues with the wifi and data so I went back to android 8.0, and use it for O2 priority only. Came back to see if android 10 fixed the problems. Disappointing.
I am not surprised at all that Sony still hasn't fixed any of the issues.
With today's New Update the the voicemail-Record-Volume Bug is fixed.
Finally. Too good to bei true.
tyrael11 said:
With today's New Update the the voicemail-Record-Volume Bug is fixed.
Finally. Too good to bei true.
Click to expand...
Click to collapse
there are still a lot of vital features that were bugged in android10 and i´m not sure they´ll be adressed in the near future.

Categories

Resources