Related
Lately I have been experiencing a multitouch problem in my xperia play.
I was playing a touchscreen game when the controls were lagging and would get stuck on the screen. I thought it was just the game but to make sure I downloaded this multitouch tester application.
I will explain to you what you should do to replicate the problem.
1. Touch the screen with a finger (Finger A)
2. While keeping Finger A on the screen touch the screen with another finger (Finger B)
3. Do not remove finger A while tapping the screen with Finger B
4. The colors of the dots that indicate the fingers on the screen should change for Finger B after many taps with finger B the application will crash.
What is happening is that every time you remove then press Finger B while keeping Finger A pressed it thinks it is a new touch point think you have 3 or more fingers.
If you use this application to test. You will see it is giving Finger B a different ID every time it touches. This application does not Force close but it starts finger B at ID 0 when it reaches the maximum.
I did a google search and found this information.
http://groups.google.com/group/android-developers/browse_thread/thread/8b14591ead5608a0
^^ That is specific to the Xperia Play so you might want to read through it.
I may be able to get a video of it later.
You pointed me here from my keyboard problem. But my problem also occurs when I'm using just one hand. If I am just using my right thumb and press the delete key, it will sometimes register both the delete key and the button z. Same occurs for example with p and q.
Sent from my R800i using XDA App
Had this prob in 2.3.2 seems to be solved un the update here I made a vid too
http://www.youtube.com/watch?v=q0oEYFfj6Pg&feature=youtube_gdata_player
Sent from my R800i using XDA Premium App
i used that apk and multitouch works fine for 4 fingers on my r800x after 4 fingers the app force closes on me
d2theaher69 said:
i used that apk and multitouch works fine for 4 fingers on my r800x after 4 fingers the app force closes on me
Click to expand...
Click to collapse
but have you tried what I said about leaving 1 finger on at all times then tapping the screen with the other finger?
This can get very bad in racing games. You are holding the accelerator and tapping the brakes. Eventually the controls go crazy.
And 1 year later... I have exactly the same issue on my Sony Xperia U. After 3 taps of my second finger, multitouch didn't detect anymore my second finger.
My Xperia mini pro havn't this problem, this is very troublesome.
Nhialor said:
You pointed me here from my keyboard problem. But my problem also occurs when I'm using just one hand. If I am just using my right thumb and press the delete key, it will sometimes register both the delete key and the button z. Same occurs for example with p and q.
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Lock and unlock the screen and it will sort it. Just do that every time it happens
Using Antutu Tester, I tested the multi-touch, using the experimental kernel. I placed four fingers on the screen, one at a time and they all registered. I then slightly moved all my fingers across the screen, and then the others disappear. Can anyone confirm this? Also got some weird activity with the trackpad wake. When pressed sometimes only the capacitive keys light up, and not the screen. I have to use the power button to power the screen on.
EDIT: Could this be overclocking related?
Sent from my T-Mobile G2 using xda premium
matthewjett said:
Using Antutu Tester, I tested the multi-touch, using the experimental kernel. I placed four fingers on the screen, one at a time and they all registered. I then slightly moved all my fingers across the screen, and then the others disappear. Can anyone confirm this? Also got some weird activity with the trackpad wake. When pressed sometimes only the capacitive keys light up, and not the screen. I have to use the power button to power the screen on.
EDIT: Could this be overclocking related?
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
The screen not coming sounds like it could be OC related.
Question, did you change any of the OC settings manually? If not, I'd recommend opening the OC Beater application and set your screen-on profile to something like 245min-998400max, and screen-off profile to 245min-384max. Let me know if that fixes the problem with the screen not coming on. (If so, I'll add something to the ROMs OP about setting the OC parameters manually if using the experimental kernel)
Ran the multi-touch test using the stock kernel, all 4 fingers registered and moved properly when I moved my fingers.
Makes sense why it's the experimental kernel, right?
tun4f1sh said:
The screen not coming sounds like it could be OC related.
Question, did you change any of the OC settings manually? If not, I'd recommend opening the OC Beater application and set your screen-on profile to something like 245min-998400max, and screen-off profile to 245min-384max. Let me know if that fixes the problem with the screen not coming on. (If so, I'll add something to the ROMs OP about setting the OC parameters manually if using the experimental kernel)
Ran the multi-touch test using the stock kernel, all 4 fingers registered and moved properly when I moved my fingers.
Makes sense why it's the experimental kernel, right?
Click to expand...
Click to collapse
Yeah it makes sense, more fun to play with!
I did actually manually set the oc to the settings you suggested and now I cannot recreate the tp wake issue.
I also had an issue using the "use_4g_icon" customization when flashing. Definitely have it in the root of the glite direc, still no change in the icon. I even did a full wipe and started fresh, still a no go.
Then I tried just changing the icon myself using ROM Toolbox, and boy did it hate that. Status bar fc after a full reboot, had to restore the back up I made. I assume this is because of the framework changes for the apm?
Sent from my T-Mobile G2 using xda premium
I'm having a bit of a problem when using the keyboard or using the soft keys I sometimes end up pressing the wrong thing when closing an app.
Is there any kind of mod to add some bottom spacing to the screen so I'm not constantly making this mistake?? Thanks
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Since the lower software keys bar takes up a lot of the screen space (making this a 4.8" device, instead of 5.2", for most practices), I was wondering how people handle this. There is an option to "auto hide" the key bar (by 3rd party app), but then I wonder how much productivity are we going to miss (by having to tap twice in order to press "BACK", instead of once). Another possibility is to use gesture control to entirely replace that key bar, but the problem with that (at least with my Galaxy S2) is that sometimes it work, and sometimes it doesn't work, I can't make it reliable.
How do you handle it with your G2 ?
Download the auto hide soft keys app & see for yourself. Its not bad.
PIE ? Try it using the LMT Launcher.
tiguy99 said:
Download the auto hide soft keys app & see for yourself. Its not bad.
Click to expand...
Click to collapse
I did it. When I use a "tap" for trigger, I find it very easy to access, but I also find myself sometimes accidentally launching it...
When I use "swipe" for trigger, it will not launch by mistake, but it is also much slower to launch...
I wish there was a way to keep the original key bar, but just make it smaller. If the height would have been half, or even third of what it is now, it would still be very easy to operate. I don't understand why it was programmed for pig fingers.
I used a mod to make the nav buttons "Tiny". So now I have a 5" screen and I'm good with that.
Can you please tell us how you did this?
Sent from my Nexus 7 using xda app-developers app
Hide all the way swipe up to see them and then bye bye
mrstarzan said:
Can you please tell us how you did this?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2457634
I don't think it works on T-Mobile
+1 for the tiny mod
I played some more with "GMD Gesture Control", and I have to say it's starting to look more promising...
I've created the following gestures:
Down-Right (anywhere on the screen) = HOME (just to clarify the gesture: I swipe down, then immediately right)
Left-Down (anywhere on the screen) = Back
Up-Right (anywhere on the screen) = Menu
Right-Down (anywhere on the screen) = Recent apps
I find this much more comfortable than even my Galaxy S2 hardware buttons...(since the hardware buttons are at the bottom of the device, but the gesture work everywhere on the screen).
The possible problems of this approach:
1. It might interfere with other screen swipes (though apart from games, I had no interference as of yet).
2. I have no clue what this does (if at all) to battery life...
Noam23 said:
I played some more with "GMD Gesture Control", and I have to say it's starting to look more promising...
I've created the following gestures:
Down-Right (anywhere on the screen) = HOME (just to clarify the gesture: I swipe down, then immediately right)
Left-Down (anywhere on the screen) = Back
Up-Right (anywhere on the screen) = Menu
Right-Down (anywhere on the screen) = Recent apps
Click to expand...
Click to collapse
Ok, upon some more testing, I did find interference using these gestures, especially when browsing internet (you tend to unintentionally make these gestures when panning windows).
So I've added another "security layer", and the gestures look like this now:
Down-Right-Up (anywhere on the screen) = HOME (just to clarify the gesture: I swipe down, then right, then up)
Left-Down-Right (anywhere on the screen) = Back
Up-Right-Down (anywhere on the screen) = Menu
Right-Down-Left (anywhere on the screen) = Recent apps
So far, so good...
Tried auto hide soft keys pro, works perfectly. Use LMT. launcher. loving my screen.
Sent from my LG-D800 using xda app-developers app
chiballer20 said:
Tried auto hide soft keys pro, works perfectly. Use LMT. launcher. loving my screen.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Do u need to be rooted for this?
LMT requires root, as does auto hide soft keys. If you're going to root anyway, I'd recommend using the qemu.hw.mainkeys=1 build.prop edit to hide them, however, as it doesn't require another service to be running.
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
And I can't recommend LMT enough. So powerful/flexible.
qemu.hw.mainkeys=1 build.prop
where can i get that?
It's just a line you add to your build.prop file. It makes the OS think you have hardware nav keys
Yes, it's a bit of a problem that both Auto hide and gesture control requires root.
I'm going to enter a 24 months contract on the G2, and so I really want to keep those 24 months of warranty...
If I root, have a problem, then un-root, will I get warranty ?
Noam23 said:
Yes, it's a bit of a problem that both Auto hide and gesture control requires root.
I'm going to enter a 24 months contract on the G2, and so I really want to keep those 24 months of warranty...
If I root, have a problem, then un-root, will I get warranty ?
Click to expand...
Click to collapse
The manufacturer's warranty is only for one year or if you have your carrier's insurance then it doesn't really matter if its rooted cuz I've never had issues returning rooted phones to the carriers insurance.
Sent from my LG-D801 using xda app-developers app
xdabbeb said:
It's just a line you add to your build.prop file. It makes the OS think you have hardware nav keys
Click to expand...
Click to collapse
Does this mean that the soft keys will be hidden but the screen will still register the space supposedly occupied by the buttons like invisible but functional buttons? That would be awesome.
Sent from my LG-D802 using xda app-developers app
Sepulture said:
Does this mean that the soft keys will be hidden but the screen will still register the space supposedly occupied by the buttons like invisible but functional buttons? That would be awesome.
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
I did it a couple hours ago.
The screen does not register them at all. Your OS now thinks you have full 1920x1080 to use instead of stock 1778x1080 or whatever it is. The buildprop method is the BEST. First off you don't have to pay for any pro app crap, and also there is no other apps running - it is just a mod that you can undo.
LMT + prop tweak = perfect phone for me.
Hi all I would like to buy a used nexus 4 of 10.10.2013, at the price of 150 euro European warranty, I just doubt the seller declares that the virtual keys on the phone do not work and everything else works before you buy i surely you'll see the phone, so i wanted to know, there is pssibilità or a way to figure out if the problem is with the virtual keys or the screen without first changing rom or restore the phone, that is immediate??
You can remove the virtual keys to use the cell with the only home to see if the part of the screen where the buttons are working?
Sorry for my bad english,i use google translate
Download the app "phone tester". It has a function called " multi-touch test". You can just move your finger over the whole screen to check for any blank spots.
Does the phone come completely stock? Because sometimes s2w and d2w cause problems like this.
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
Download the app "phone tester". It has a function called " multi-touch test". You can just move your finger over the whole screen to check for any blank spots.
Does the phone come completely stock? Because sometimes s2w and d2w cause problems like this.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If your phone has a custom kernel, you can activate and s2w d2w, if your phone has the stock kernel that is not possible. If your phone there are s2w and d2w with phone The application tester will give error in the area of soft keys when you head to the screen?
The app I mentioned is just to see if and where there are blank spots.
I've made the experience that d2w after sometimes makes the left and right side of the screen unresponsive. Others might have made other observations.
Sent from my Nexus 4 using XDA Free mobile app
tanks before I buy it I'll try the screen with the program who advised me
I picked up the phone, the touch works all the rom and the kernel are original, as I solve the problem of virtual keys??
Does touch input work on the complete screen? There's a button on top to make the touch test run in full screen so you can test all borders and edges. If it does I guess flashing a complete stock image should solve the issues.
Sent from my Nexus 4 using XDA Free mobile app
It works all the touch screen, the problem is that the keys back - home - menu, they do not work it vertically horizontally into the side of the phone where they are placed, they only work if I turn the phone and I get them to appear in the side where you is the camera.