Database Info

JF1.41 Bug? changes the way the touchscreen works?

On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?

Well, maybe you should go back to an unrooted phone so that you can play with your steamy window....

LPChris, I would expect a little more maturity from a "senior member"
I am trying to contribute to make JF the best it can be. Maybe your just having a bad night or something, but theres no need to be so childish.
:ed:
Looking through your posts it seems like your just having a bad night
Back on topic:
While this may be a stupid little problem with one application. Should finger-area sensitive applications continue to be made this could isolate JF1.41 from the market. Naturally I dont care much for steamy window, but I would like to prevent other issues in more... useful... applications

I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.

sjbayer3 said:
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Click to expand...
Click to collapse
Ditto about LPChris lol, a lot of his posts sound like that, but yeah I noticed the same thing about the steamy window app before and after using JF 1.41.

Steamy window, LOL! sorry guys. anyway keep up the great work.

Yes, this is a trivial example, but it does identify a real issue.
I was reading through the various google android groups last night and I ran into some info that seems to addresses this issue. From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
your Steamy Window app seems to make use of the size value as it was originally designed. Now with the change, with only one finger input, this value is set to some minimum, producing a thin line.
To test this theory, see if when you touch the screen with two fingers the size of the mark gets bigger.

Why can't a capability bit or other mechanism be defined that could be used to indicate whether or not an application were multi-touch aware, so that the touch handling behavior at the lower levels would revert to "standard" behavior for normal (non-multi-touch) apps? Trying to make the multi-touch hack fully backwards compatible may not be practical.

I tested your idea about multituch possibly fixing steamy window
My only results are really strange.
If I touch with two fingers it will make a line about the width of my 2 fingers, but its located in the top left, no matter where my fingers actually are. Furthermore the line isnt straight its curved.
Now, after my first touch, it seems if I touch it again it just crashes.

ex-MN said:
From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
Click to expand...
Click to collapse
Edit: Hmm... the x-y data of the second finger is stored in separate fields. I think the usage of the size field is just as a boolean to tell multitouch capable programs that second finger data is being sent.

themes and JF RC versions. be careful
TheDudeOfLife said:
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
Click to expand...
Click to collapse
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
BhanG

bhang said:
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
Click to expand...
Click to collapse
After some more testing I have this same issue on 2 1.41 compatible themes (rusty metal and fade to blue) I am going to go back to themeless 1.41 but I think it is more related to the multitouch 'hack' than the theme themselves. I find it hard to believe that a bunch of icons could mess this up. I watches my screen jitter between the left and right screen for 3 minutes today before I just performed a soft reset on my phone.
Note: I also applied each theme from a fresh flash of 1.41...not on top of each other.

this happens with screen crack also, but it doesnt affect me that much until i start not being able to select stuff. i know it may be important its just not to me... yet *knocks on wood*

Yeah Ive noticed it too..
I thought that it was just the app at first.
I might be switching back to .31 then at least til this gets fixed.
Steamy window def is NOT reading my fingers location or size properly.

I've also seen it affect touch paint found in the API Demos. Doesn't even register touch anymore.

It appears multi-touch is premature at this point and to implement multi-touch throughout the OS and not just the browser like everyone seems to think isnt good. It is definitely is throughout the OS and probably will affect any application that uses the second touch value to register touch size.
My other concern is that dev's won't take this hacked multi-touch into account so they will continue to write programs that won't be compatible since its not the "norm"
Taken from and android forum...this is my biggest concern
"Please think about soft keyboards when considering multi-touch APIs,
where the problem isn't detecting the distance between two finger, but
rather is allowing a 2nd finger (or thumb) to come down on a 2nd key
before the first finger (or thumb) has been released. The proposed
API to provide only a centroid and the distance between fingers won't
work at all for this sort of application.
I think you'd ultimately want to package this as additional
GestureDetector subclasses, depending on whether the type of gesture
detection wanted was pinch/zoom or multiple/overlapping taps.
Keyboards (and maybe games) would use one class, browsers another.
Providing the right information from a touch panel to drive either
detector might be challenging, especially if the panel provides
'unpaired' x and y coordinates rather than individual touch locations,
but I believe it could be done. "
JesusFreke,
Any thoughts on this?

Yeah lets hear what JF's got to say.
I originally thought that the multitouch was embedded in the browser, It's too soon to have it throughout the entire OS...
How about 1.41=with multitouch and 1.42=without

I've installed JF1.41 and I have an unusual bug....sometimes the screen behaves like it isn't calibrated..i press the screen on a button and it is pressed another one....have anyone encoutered this problem?

I invite everyone to do the following to find out how ur touch registers on ur screen. Open anycut. Get it if u don't have it.
Click activity and find raw image viewer. Click ok and then click on the shortcut.
Now start moving your finger around and see the results.
Let's all post our results here so we can figure this out.
Post in the same format as me:
ROM: JF1.41
1 finger - it surpisingly followed my finger perfectly. It only registered the very center point of my finger.
2 fingers - it appears that it made the same point as the 1 finger, however now the point was exactly in between my fingers and stayed there as I moved them around.
Ok so now we need ppl with stock rc30 and 1.31 so we can test this out!

You wanna have some real fun? Try it with 3 or 4 fingers.. It goes nuts..

Turn off one finger zoom

Just installed Synergy JB and have noticed that there is one finger zoom in here where you basically slide up and down on the edge of the screen and it zooms in and out. I see people with the note II have this also so it seems it may be a Touchwiz JB feature but I haven't seen a way to turn it off. It's nice but would love to find a way to toggle it. I already checked display, accessibility, and motion controls with no luck and it zooms in any app that can zoom.

If I remember correctly E actually put the GNOTE 2 camera in that ROM so what you are seeing is that actually camera... As far as I know the only way to change that would be to flash a different camera.... HOWEVER.. I do have the NOTE 2 camera on mine also and can pinch to zoom or use the volume keys so there may be different versions of that also... But anyways flash a different camera and that should do the trick

dr12volt1338 said:
If I remember correctly E actually put the GNOTE 2 camera in that ROM so what you are seeing is that actually camera... As far as I know the only way to change that would be to flash a different camera.... HOWEVER.. I do have the NOTE 2 camera on mine also and can pinch to zoom or use the volume keys so there may be different versions of that also... But anyways flash a different camera and that should do the trick
Click to expand...
Click to collapse
Well its not just the camera it's in the browser, wikipedia app, and others

I apologize.. I swear the post said in the camera app.... I know he pulled a few .APK's from the Note 2... All I can suggest is check the settings for the individual apps... You could also try and download a different browser and try that... That would help narrow it down if it is something "Overseeing" the ROM or something specific to certain .APK's....

anyone find a fix for this...it's happening in my browser now and it's killing me?

skillzo1 said:
anyone find a fix for this...it's happening in my browser now and it's killing me?
Click to expand...
Click to collapse
Check your other thread.
Sent from my Unleashed GalaxyMODed ...... um ...... phone?

What Scroll Bars?
skillzo1 said:
anyone find a fix for this...it's happening in my browser now and it's killing me?
Click to expand...
Click to collapse
With all due respect, you may want to look at your screen and take note of the fact there are no scroll bars.
I understand that we are creatures of habit, and as I have been using the GUI, with Scroll Bars since the first Mac (1984) I too tend to use the edge of the screen to scroll, but the truth is, it is a Phone, not a Mac, not a PC. It has no scroll bars. Scroll slightly to the left (or to the right-so to not disenfranchise left handed phone users) or 1/4 of the way across, or 1/3rd, or 1/2 or 3/4 quarters, etc. etc. etc.
Anywhere you'd like. It's a Phone, it's a touch screen. No mouse, no ability to tap in the scroll bar and have the screen advance. No way to position your mouse over the up or down arrow, and have the screen scroll smoothly without any other movement than you holding down the mouse button.
It's a Phone. Get it?
Anyway, what is really infuriating is that Samsung put this feature on the phone, didn't tell anyone, until people started complaining about it and reporting it as a bug, and then rather than either tell people about it, or add the ability through a Setting to disable it, in a new release of the software, the morons simply took it away.
So let me ask you, if your phone came configured with the setting disabled by default, but gave you the option to enable it, try it, see if you liked it, then said, nah, and turned it off, would that have been best for you and guys like me who depend on it all day every day to be able to use my Phone with one hand?
I think the answer is obvious.
Samsung, you are laughable, amateur software developers.
Thankfully we have XDA.
Now I just need one of you on here to figure out where in the heck it is hidden so you can make me a build that includes it with whatever else is in the latest releases.
You see, Android is almost entirely "Hard Coded" so it is not something the average user can just go "teeak" , like following the step by step instructions of someone to simply "Hack" the Windows Registry to make it the way we like it.
All the more reason Samsung is so pitiful.

Touch screen sensitivity issue

Hi guys, apologies if this has already been discussed elsewhere. I've been using the Mate 9 for a couple of days now and I've noticed the touch screen sensitivity can sometimes be unresponsive. There has been a number of times where I've been on a browser or app and had to click on a link/button at least twice before it responds. It's the same when I click on the Settings button at the top of the notification panel and other areas such as the settings page.
I thought it was just me but I've gone back to my Nexus 6P and iPhone 6s to test, and there is a notable difference.
Has anyone else experienced this? It almost seems like Huawei have intentionally done this as the touch sensitivity elsewhere, i.e. lock screen, seems to work just fine.
Does anyone know if this a known issue and is it likely to be fixed?
Thanks in advance.

Same issue here I believe it has been fixed with a firmware update which has yet to land on my UK model

I sometimes experience some unresponsiveness as well, but told myself maybe it's due to the screen protector? Curious to see if others who took off their screen protector experience this same problem.
It's very minor though, for me.

I know the update was supposed to help and did but I just found a pressure sensitivity setting that allowed me to change the sensitivity which made a big difference IMO. I installed Quick Shortcut Maker and found it under settings. Made the shortcut and pressed it and voila I could decrease the pressure needed to respond.

rndchef said:
I know the update was supposed to help and did but I just found a pressure sensitivity setting that allowed me to change the sensitivity which made a big difference IMO. I installed Quick Shortcut Maker and found it under settings. Made the shortcut and pressed it and voila I could decrease the pressure needed to respond.
Click to expand...
Click to collapse
Are you rooted? Because it tells me that access is denied.

Sammath said:
Are you rooted? Because it tells me that access is denied.
Click to expand...
Click to collapse
No. Stock. I never saw anything similar to that. Installed app. Added shortcut to Pressure Sensitivity and then opened shortcut and moved slider all the way to the left to decrease pressure required.

rndchef said:
No. Stock. I never saw anything similar to that. Installed app. Added shortcut to Pressure Sensitivity and then opened shortcut and moved slider all the way to the left to decrease pressure required.
Click to expand...
Click to collapse
Maybe it's the firmware I'm on MHA-L29C432B158

Yes it does exist AFTER removing screen protector.
Mine is too the point I may return it even thou I think it has a better camera than Samsung and LG

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.

tap registering as part of a swipe

I've noticed my tab dropping inputs in somewhat consistent scenarios when playing games, and just recently found out why exactly that's been happening. It seems that if I tap immediately as soon as I release a swipe with another finger, it just extends the swipe. And the range is just outrageous?!? I mostly just want to figure out if there's something that could be done somehow? or if I should give up on this tab.
Your browser is not able to display this video.

meowmeownyanya said:
I've noticed my tab dropping inputs in somewhat consistent scenarios when playing games, and just recently found out why exactly that's been happening. It seems that if I tap immediately as soon as I release a swipe with another finger, it just extends the swipe. And the range is just outrageous?!? I mostly just want to figure out if there's something that could be done somehow? or if I should give up on this tab.
View attachment 5626453
Click to expand...
Click to collapse
I honestly would...
I believe kernel is in charge of touch so a different one might solve it? That's a big might tho and in my experience custom kernels usually are far worse than stock even if it solves the touch issue