Hey, was playing Gameloft's Modern Combat 3 on my G2x running Eaglesblood sandwich, build 3, and i noticed something strange that greatly hindered gameplay.
The issue i was facing is that the floating analog joystick logs my input while moving the player only for like 2-3 seconds and then just reverts to its originaly postion forcing me to touch the screen again to make it register my input. This basically causes the player to move in spurts!
I don't know whether this is a game specific issue, isolated issue or an issue related to the ROM. Hope it's isolated. I'm not trying to allocate blame here, but i think the new Trinity kernel with the UMS feature that came with EB build 3 might have a different touchscreen sensitivity compared to other kernels.... dunno if im right, but just a guess.
Anyone else having similar issues?
Get "Phone Tester" from the market and go to Multi-Touch test. Hold down your fingers and move around then leave them on the screen for a bit (just imitate playing). That'll tell you if it's an application specific issue or not.
https://play.google.com/store/apps/details?id=com.mtorres.phonetester&feature=search_result
Jufjufjuf said:
Get "Phone Tester" from the market and go to Multi-Touch test. Hold down your fingers and move around then leave them on the screen for a bit (just imitate playing). That'll tell you if it's an application specific issue or not.
https://play.google.com/store/apps/details?id=com.mtorres.phonetester&feature=search_result
Click to expand...
Click to collapse
The G2x should have no problems with multi-touch. It supports up to 10-touch points simultaneously.
Theonew said:
The G2x should have no problems with multi-touch. It supports up to 10-touch points simultaneously.
Click to expand...
Click to collapse
The point of the test is to figure out whether his problem is application specific or not. Not to show whether multi-touch works but that the points stay on the screen.
Will take a look at phone tester.. Thanks
But did anyone experience similar issues?
Related
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..
I wrote a simple program to listen to the new TYPE_ROTATION_VECTOR sensor and just print out the values to the screen.
It runs for a little while (~5 to 10s), and then reports 0.5 in all fields, and then finally NaNs. Has anyone else tried out this new API successfully? If needed I can upload my test program somewhere, but I really just listened to the calls and printed the values out to the screen.
developer.android.com/reference/android/hardware/SensorEvent.html
OK, I got my apk ready to go.
If other people would be nice enough to test this for me, let me know if the numbers eventually go to .5 and then to NaNs.
Thanks!
Uggghhhhh, forgot the attachment.... >.>
Tested for you.
Same results as on your device. Gives numbers for 10secs or less, then .5s then NaN.
EDIT: That's in portrait. Immediate NaN in landscape.
Be aware that you have to reboot the phone to get it to reset.
This is some sort of API lockup.
I'm getting the same issue as everyone else. If I force close the app and start it back up I will get rotation data for 10s and then +/- 0.5, then NaN after about 15s.
chadrockey said:
Be aware that you have to reboot the phone to get it to reset.
This is some sort of API lockup.
Click to expand...
Click to collapse
Portrait I was able to do it a couple of times just fine.
But you're right about the reboot on landscape. After doing that, it exhibited the same behavior as portrait. Dunno if any of this helps, but figured I'd try!
Yea, thanks everyone.
I'm pretty sure this means the cool new orientation API is broken.
If anyone wants to see what this API is supposed to give us, see this InvenSense Google tech talk:
http://www.youtube.com/watch?v=C7JQ7Rpwn2k
They were the company that made the Wii MotionPlus.
Here's the Gingerbread press release from InvenSense:
http://www.invensense.com/mems/gyro...is_Sensor_Fusion_For_Android_Gingerbread.html
OK, I got it resolved!
There are 4 different speeds you can request when you make a sensor listener:
SENSOR_DELAY_FASTEST ( ~30Hz)
SENSOR_DELAY_GAME (~30Hz)
SENSOR_DELAY_UI (~16.7Hz)
SENSOR_DELAY_NORMAL (~8Hz)
I did not realize that Normal meant for slow, screen rotation sort of events.
However, the bug happens only when you use SENSOR_DELAY_NORMAL. The other 3 (I suspect GAME and FASTEST are the same) all work well.
Here is code that works on my phone. If anyone wants to test this program or look at the absolute orientation of your phone in Rotation vector, quaternion, and Euler angles, give it a shot. Thanks for your help, everyone.
Hi!
I recently bought an O3D and I'm getting some multi-touch problems.
As you can see, when you tap 3 times with another finger already tapping, multi-touch goes totally wrong. This happens after unlock/lock screen sometimes, and if you tap 3 times again the problem disappears.
Video from other user.
Kernel problem? Is there any solution? This makes playing multi-touch games (Nova for example) really anoying or zooming in browser with two fingers.
So sad to see the behavior of your touch screen, cause when I do the same test on my O3D it recognize 8 fingers without any problems. Are you rooted? Did you try for example my ROM to see if it makes any difference?
Sent from my amazing LG O3D using ThiaiZO3D V2.4
ThiaiZ said:
So sad to see the behavior of your touch screen, cause when I do the same test on my O3D it recognize 8 fingers without any problems. Are you rooted? Did you try for example my ROM to see if it makes any difference?
Sent from my amazing LG O3D using ThiaiZO3D V2.4
Click to expand...
Click to collapse
Mine recognizes up to 10, but when this happens only recognizes one at time. If you tap three times the problem is gone until you tap 3 times again.
I've tried with custom roms (one of them is yours), rooted, etc.
i confirm the problem...but the games looks not to be affected by it...they works perfectly.Only with touch test i have the problem...very strange and i have your rom thiaiZ...any other experice of it?
I have the same problem...
I'm on CM7 nightly 32 (for the P925 because of the Baseband problems)
but it is a bit strange.. sometimes it works and sometimes it doesnt, i don't know why
I have similar problem.
When I play a game the touch screen with 1 finger is okay but when I play with 2 fingers it stops to recognize the both fingers.
So I have to walk and then stop and then aim and then fire which sucks.
I have the same problem. Is this problem related with hardware?
hi everyone,
i tested this too and i noticed a certain pattern. If i turn off my phone and then turn it on and then run the multitouch tester i will get the issue you described. However if i turn it off and then turn it on and then move my finger from the left of the screen to the right of the screen 3 times(on the homescreen) and then I run the multitouch tester the issue is gone and the touch screen works perfect afterwards. Its a very weird bug. can someone confirm this on their phone also. If a programmer can develop an app that imitates 3 swipes when the phone unlocks then this annoyance is fixed.
Multitouch problem-any permament solution?
Have anyone found a permament solution?The thing is annoying.Has anyone got hardware fixing solution to this problem?Maybe the flat cable (placed at power button)?I've noticed it after 5 months of use.I haven't tried it myself with any other optimus 3d device.Could anyone confirm not having a problem?Btw, I use 2.35 official, without root or any kind of mod.Please, help.
rgunara said:
hi everyone,
(...)However if i turn it off and then turn it on and then move my finger from the left of the screen to the right of the screen 3 times(on the homescreen) and then I run the multitouch tester the issue is gone and the touch screen works perfect afterwards. (...)
Click to expand...
Click to collapse
Yeah, I've noticed this problem too and your three swipe solution seems to work fine. I also realised that I don't need to be on the home screen for this to work. I swiped on the tester screen itself and multitouch resumes working.
Testing with Antutu Tester I can get 10 simultaneous touches. The hard thing is to make 10 fingers fit into the screen
Sent from my LG-P920H using xda app-developers app
Those who don't know there are some people having ghost touch issues on POCO f1 and one guy able to capture it on the video. I personally didn't had the issue but after trying I was able to recreate the issue on my device. soon after I found the cause and able to fix the issue. this may or may not work on your device but absolutely worked for me. this seems to be a software bug. and no-one needs to panic. hopefully it will be fixed in next update.
how to recreate the issue?
Steps
1. download a multi touch tester app I used this
2. first do some testing yourself see if you can spot the issue
3. now do 3 finger swipe down (phone will take screenshot)
4. now randomly touch your screen with 1 or 2 fingers you'll notice 1 or 2 ghost touches.
How to fix Fix it?
Steps
1. go to settings>additional settings>button and gesture shortcuts>take a screenshot
2. and set it to none.
3. reboot
that's it!
the issue should be fixed
please let me know whether this worked for you or not
Yes.
As you mentioned issue was there.
But fixed with those steps.
okaraosp29 said:
Those who don't know there are some people having ghost touch issues on POCO f1 and one guy able to capture it on the video. I personally didn't had the issue but after trying I was able to recreate the issue on my device. soon after I found the cause and able to fix the issue. this may or may not work on your device but absolutely worked for me. this seems to be a software bug. and no-one needs to panic. hopefully it will be fixed in next update.
how to recreate the issue?
Steps
1. download a multi touch tester app I used this
2. first do some testing yourself see if you can spot the issue
3. now do 3 finger swipe down (phone will take screenshot)
4. now randomly touch your screen with 1 or 2 fingers you'll notice 1 or 2 ghost touches.
How to fix Fix it?
Steps
1. go to settings>additional settings>button and gesture shortcuts>take a screenshot
2. and set it to none.
3. reboot
that's it!
the issue should be fixed
please let me know whether this worked for you or not
Click to expand...
Click to collapse
Good stuff. I was skeptical at first since I knew something was off sometimes. Thanks for confirming it. Should be fixed if they took notice of this bug.
Thanks! The issue is 100% reproducible with the app. By turning off 3 finger screenshot shortcut, the issue goes away.
Guys, please file a bug, so this can be fixed and we can go back to using this feature.
1.Yes, that issue is due to the screenshot feature, but shouldn't the phone be able to distinguish between 3 finger touch and more than 3? Either take screenshot on four finger swipe or register it.
2.Can you please confirm if there is accuracy problem in PUBG aiming when you use multitouch? Like the multitouch bugs in Pixel and Zenfone Max Pro but quite subtle, the thing about the other devices are, they look and have been acknowledged by the respective companies regarding the issue but in our case, Xiaomi or Poco is making no announcement or anything.
https://www.youtube.com/watch?v=e5K2N6McC_s
The issue comes up after taking a 3 finger screenshot, but disabling may not be the only solution as this feature is quite useful also
What I have noticed is that after taking screenshot ghost touch is there till we use 1,2 or 3 fingers. Once we use 4, 5 or higher fingers the issue goes away.
Isn't it better to just touch screen with 4 fingers after taking a screenshot which somehow resets the ghost touch issue.
Have tried this solution with multi touch tester app
Mine is just fine even when 3 finger swipe screenshot is switched on
I can confirm that ghost touch issue still persist even when disabling three finger screenshot.
Mostly visible in pubg.
Great, fix worked
I didn't relize the issue but nice posting
Stop it! This is not an issue. It happens on mostly every phone that supports gestures. Test it on OnePlus 6 and you will get the same result.
GizmoFreak said:
Stop it! This is not an issue. It happens on mostly every phone that supports gestures. Test it on OnePlus 6 and you will get the same result.
Click to expand...
Click to collapse
it is software bug which creates inconvenient experience with touch screen.. this fix is just a workaround until official fix..
raj7749 said:
it is software bug which creates inconvenient experience with touch screen.. this fix is just a workaround until official fix..
Click to expand...
Click to collapse
Okay, show me how this affects your usage of phone. Don't show me on touch testing apps. Show me a real use problem.
GizmoFreak said:
Okay, show me how this affects your usage of phone. Don't show me on touch testing apps. Show me a real use problem.
Click to expand...
Click to collapse
lol.. i don't need to prove to you anything about this, don't care wht u think.
However ill tell for the benefits of the others, it was effecting me while playing games.. specially RPG games where multitouch is heavily use. I was seeing weird behaviours sometimes, when selecting troops.. thts how i came to know
raj7749 said:
lol.. i don't need to prove to you anything about this, don't care wht u think.
However ill tell for the benefits of the others, it was effecting me while playing games.. specially RPG games where multitouch is heavily use. I was seeing weird behaviours sometimes, when selecting troops.. thts how i came to know
Click to expand...
Click to collapse
Okay, please record a video of you playing and of course don't show me but share for the benefit of the community.
GizmoFreak said:
Okay, please record a video of you playing and of course don't show me but share for the benefit of the community.
Click to expand...
Click to collapse
xD, if needed will do M too lazy to do that for now
raj7749 said:
lol.. i don't need to prove to you anything about this, don't care wht u think.
However ill tell for the benefits of the others, it was effecting me while playing games.. specially RPG games where multitouch is heavily use. I was seeing weird behaviours sometimes, when selecting troops.. thts how i came to know
Click to expand...
Click to collapse
Exactly! There is no need to prove this issue because Google itself confirms that they have done a mistake by releasing it in Oreo and they have also promised to give a fix in later Pie updates. And people who wants proofs can look up in the internet about the "Multi touch Oreo Bug" problem and how it effects user experience rather than spamming here to make a point.
$hivaM Manav said:
Exactly! There is no need to prove this issue because Google itself confirms that they have done a mistake by releasing it in Oreo and they have also promised to give a fix in later Pie updates. And people who wants proofs can look up in the internet about the "Multi touch Oreo Bug" problem and how it effects user experience rather than spamming here to make a point.
Click to expand...
Click to collapse
Dude, google fixed the issue in the May or June patch and all other OEM's had to merge their builds to fix it. The problem is not there in MiA1 or MiA2.
Here is the bug:
http://en.miui.com/thread-3746297-1-1.html
Thanks
Maybe the original solution for 8.1 and P devices will work for this? It will either cause a bootloop, do nothing, or fix it... worth trying! Obviously an unlocked bootloader is needed for this (Magisk).
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