So I had Rayman Jungle Run on my Xoom and it worked perfectly. On my Nexus 10, there is a delay between the time I touch the screen and when the game recognizes the input. About a quarter second. This makes the game almost unplayable. I was on stock 4.2.1. I then rooted and am now on AOKP-PUB 4.2.1 and still had the same issue. I flashed the latest Franco kernel and miraculously the game worked perfectly for about two weeks. Just today I noticed this same input lag. It doesn't seem to do this on any other games or apps. Has anyone else experienced this problem? Help!!
Nevermind, just figured our that I had magnification turned on in the accessibility options and this was the culprit. Dang!
had the same problem - drove me nuts - thanks for posting - probably wouldn't have figured it out
simply touch the button on ur screen while holding down the screen with ur other finger, which means it needs multi-touch to process
Related
Hello,
I recently bought Mini Squadron for Android, but what was my disillusionment when I realized that it was unplayable!! The gameplay has nothing to do with gameplay that had in the iphone ... commands are always changing and sometimes the plane goes into free fall when it should be going up !!!!... I understand that the touch of Desire is different, and sometimes it confuses the touch (as seen in some videos) ... but this way it becomes unplayable !!!!...
Anyone else had this experience?!
And... is there any way to fix it?!...
I installed v1.12 last week and have't had any problems. This is a great game on the desire. All controls are smooth and responsive. Maybe you just need to go back to flight school
G
arkha said:
Hello,
I recently bought Mini Squadron for Android, but what was my disillusionment when I realized that it was unplayable!! The gameplay has nothing to do with gameplay that had in the iphone ... commands are always changing and sometimes the plane goes into free fall when it should be going up !!!!... I understand that the touch of Desire is different, and sometimes it confuses the touch (as seen in some videos) ... but this way it becomes unplayable !!!!...
Anyone else had this experience?!
And... is there any way to fix it?!...
Click to expand...
Click to collapse
I installed the game some days ago to try the trial version, no problem at all in flying the plane. They even "solve" the multitouch issue of the desire by putting the stearing touch pad and the "fire" pad in 2 different corners, that way it should have no issue of crossing axes or whatever.
hence cannot confirm any of your issues, great game on desire
Use the trackpad...darf ._.
No problem on my Desire..
When i play games with latest update 3.0 sense and 2.3.5 when u press 1 button like
walk forward then u press turn left, it all stops. only 1 thing works at the time.
sorry 4 unclear english but multi touch used to be 4 fingers. now its 3 fingers?
what happened?
WHAT TO DO?
multi touch aint working properly!?
UPDATE: Rebooting device fixed this problem! well it did not fix the cirkle locker thing but..games are good now...
UPDATE: The Bug is back! Wtf is going on? rebooting fixes it fow little while but is strikes back very fast! and agains 3 multitocuh on antutu tester.?
Fixed: Hard reset fixed this issue, Now all is fine!
If your still interested it was probably a custom lock screen. Like go locker or lockbot.
I am having this exact same issue (also reported at androidforums.com/desire-hd-support-troubleshooting/470923-issues-following-update-2-3-5-a.html) - and I don't have any custom lock screen installed
hard reset fixes all issues.
Hi guys i got some freezing issues, anyone got an idea what could it be? i'm totally new to Android/tablets, so other then this info, i don't know what else to say, or explain the issue better, it just freezing for like 5 sec, and after it works normal, its random freezing. I hope anyone can help me, thanks.
Is it when you update or install apps?
This is normal, the OS can freeze for a few seconds during write operations.
nex86 said:
Is it when you update or install apps?
This is normal, the OS can freeze for a few seconds during write operations.
Click to expand...
Click to collapse
What do you mean by normal it doesent happpen during instal, its random during surfing for example not conncted to installation imho.
dazed1 said:
Hi guys i got some freezing issues, anyone got an idea what could it be? i'm totally new to Android/tablets, so other then this info, i don't know what else to say, or explain the issue better, it just freezing for like 5 sec, and after it works normal, its random freezing. I hope anyone can help me, thanks.
Click to expand...
Click to collapse
What ROM and kernel are you using? Are you over clocked?
hagensieker said:
What ROM and kernel are you using? Are you over clocked?
Click to expand...
Click to collapse
No overclock at all, Kernel - 3.4.0-g9e52a21
Build number JSS15R all stock here. No custom ROM's..
I experience the same BS on an all stock WIFI model (2013.06 date code). Thought it was JB 4.3 teething pain but my Note 3 running 4.3 doesn't do it. Have mainly noticed it playing Great Big War Game where it'll randomly freeze the whole tablet once per launch for about 10 secs where nothing responds (show touch, home, switch task, etc.) then it'll either return to normal or prompt with dialog to wait or close. Have also had it happen in Modern Combat 3 along with the random app close that, again, doesn't affect Note 3. Haven't seen newer apps affected so perhaps it's a software issue and is fixable but it's irritating nevertheless considering it's a Nexus device and after correcting the touch issues with ts10 firmware update. Going to try reflashing the stock image to see if it fixes it otherwise looking forward to dumping this Asus for a Note 10.1 2014 LTE. My Note 10.1 2013 and Note 2 have been 100% solid with never a crash, hang or touch issues.
I had freezing problems when i was trying out the TS20 fix. TS10 seems to yield erratic behaviour randomly after each reboot.
Ever snce i've been testing the ones between TS10 and TS20. TS16 works better for me than TS18 - just being more responsive but both has no reboot issues. Am testing TS14 now and it seems better than TS16 but i needed more time to run it. None of the 14,16 and 18 has given me any kind of freeze after 24hrs of testing on multi-touch intensive apps.
You might wanna give 16 a try... i will be posting a more detailed update in sfhub's thread when i'm done with TS14 and TS12 testing.
Cheers
Thanks for the answers guys, but this is really new to me, i got no idea what is TS 14, TS 18 or TS16, can you guys explain me a bit? thanks.
I had the same issue. Please see my observations at post: http://forum.xda-developers.com/showthread.php?p=46082214#post46082214
However, I have recently tried to uninstall all apps (backing up with titanium backup) and installing back in bunches. With only the apps/games I use daily, the issue appears to have subsided, and I am trying to slowly bring apps back to see what the issue is.
Original post for consolidation purposes:
When it happens: Touch intensive Games (drastic, MMOJ, Dumb Ways) appears to be when the 3D GPU is NOT in use, netflix, when paused for a short while.
What happens:
1. Screen does not update display appears frozen
2. No response from nav bar icons
3. Power, volume buttons give no response.
4. If audio was playing right before it froze, it will keep playing as if nothing wrong.
5. If I hit the power button or the nav button then let it sit for a few minutes, suddenly it will react to every press I did in quick motion and go back to normal.
5a. I had show touches enabled, which showed a random number of the frozen touches working in quick succession when it "unfroze"
6. Sometimes requires a hard restart with no response.
When it started: Right before the Q update starting rolling out, did not have issues out of the box.
Purchase date and location: Right around the time of launch from best buy, 32 GB 2013 version
Troubleshooting steps: Safe mode (doesn't appear as often), full factory restore to the Q image when the R image started rolling out. Issues were gone for a short timeframe, then returned
Config information: Stock, latest firmware version, rooted via TWRP (latest version installed), and SU.
Observation: Appears to occur in select situations, and I believe I always have a GMAIL notification right when it un-freezes.
Let me know what you think and if it should be merged with a different topic, didn't see anything about it un-freezing when it was frozen or audio still playing.
Click to expand...
Click to collapse
Please refer to this thread for a fix:
http://forum.xda-developers.com/showthread.php?t=2428133
The fix from the thread above helps with many touchscreen issues including freezes.
At least it helped with mine. I was experiencing freezes and so called "sticky touches" (like when you short tap on something and the device interprets it as a tap and hold).
My device came with pre-Q and went through three OTA updates. After reflashing with factory R image minus wiping data (remove -w from flash-all.bat file) and with ts10 all appear to be better so far. Modern Combat 3 still randomly closes but it could be Gameloft's crappy coding. Need to run it for a few more days to confirm but reflashing factory R image with ts10 offer the best experience so far.
Mine does too now in addition to the already random reboot. The freezing happens when I try to input text on the keyboard.
Sent from my Nexus 7 using xda app-developers app
So I bought a used N4 sold as is because the seller said he had some issues with the ROM and the touch sensitivity and all it needed was a stock ROM flash. I took up the challenge and flashed stock 4.4.4.
While I'm at the home screen everything's fine, as soon as opened the app drawer there were random touches all over the bottom half of the screen. Some were shown in the center and many at the bottom left corner but most were just random. I mean like 7-8 touches per second. The same happened whenever I went into play store, Opera or Chrome. Didn't test it further since I decided to try another rom.
Flashed Purity ROM and at first glance it worked flawlessly. Not random touches in home screen, app drawer or settings. Then I flash Gapps and the same thing happens with Play and Opera.
The funny thing is that the problem persists but at different circumstances. Can't pinpoint the exact cause. Should I get a new screen and try? Or maybe something else is at fault there?
I've been having the exact same problem as you. It started after I replaced the screen and the usb flex.
Ghost touches 1-2 each second only on some apps (none on homescreen or settings). I noticed that it happen in 4.4.4 app drawer but not in the 4.2.2 app drawer. I got almost no ghost touches on 4.2.2 messaging app also. It happens in almost any app, like play store, dropbox,chrome....
I thought it was the battery so I replaced it, but it did not fix it.
I have been trying to troubleshoot the problem but I ran out of theories. I wish the best luck to find the solution, as I almost gave up on it. If you happen to solve it tell me.
I think i found out what's causing this issue.
My theory was that apps with a lot of white would trigger the ghost touches. So I tested with flashlight screen apps that only show white on the screen. As expected the ghost touches only started to appear when i turned the flashlight on.
Therefore my theory was correct.
In my case I will contact the seller that sold me the screen to see if I can get a replacement.
I've had the intermittent touch screen issue, just above the capacitive buttons and also the ghost touches.
Started about 2+ weeks ago.
I reverted back to the stock "HOME" launcher instead of the Google Now launcher and that seemed to have fixed the issue.
I will have to keep an eye out to see if it lasts.
Nexus4 Ghost touch navbar fixed (for rooted only)
Nubrig said:
So I bought a used N4 sold as is because the seller said he had some issues with the ROM and the touch sensitivity and all it needed was a stock ROM flash. I took up the challenge and flashed stock 4.4.4.
While I'm at the home screen everything's fine, as soon as opened the app drawer there were random touches all over the bottom half of the screen. Some were shown in the center and many at the bottom left corner but most were just random. I mean like 7-8 touches per second. The same happened whenever I went into play store, Opera or Chrome. Didn't test it further since I decided to try another rom.
Flashed Purity ROM and at first glance it worked flawlessly. Not random touches in home screen, app drawer or settings. Then I flash Gapps and the same thing happens with Play and Opera.
The funny thing is that the problem persists but at different circumstances. Can't pinpoint the exact cause. Should I get a new screen and try? Or maybe something else is at fault there?
Click to expand...
Click to collapse
Hi everyone. this is my first post. i may make some grammar mistakes, because english is not my native language.
I found a solution for the ghost touch issue on my nexus 4, so maybe it can help who is having the same problem.
1- Download and instal the NOMone Resolution Changer on Play store
(this is my first post here, so i cant paste de link here, but you will not have trouble to find it)
2- when asked, Allow superuser
3- open the app and change the height resolution to 1250. (it worked for me, but make some tests to see if you need to disable a bigger part of the screen to avoid de problem)
This is not the best way to keep using your phone, because you may lost a part of the usable screen, but worked for me.
Thanks!
I workaround this issue avoid using undervoling in the kernel, and avoid lower temperatures in phone, yes as you read ... this issue give my crazy when my phone was to hot and I tried to cold my phone using one ice cube in screen and back, the temperature of the phone down but ghost touches appears again, so played some videos to warm the phone again and dissapear again.
Don't ask me about how it works, or relation with screen, digitizer or battery, I don't understand but help me to workaround the issue.
I am not sure how many owners of the SM-G730A are mobile gamers at all, but maybe some of you have noticed this...
Since the update to Android KitKat 4.4.2 the touchscreen behaves erratically in certain games, primarily FPS shooters. I know it is not an issue with my particular device, goto Google Play and look up Dead Trigger 2. View the reviews for this device model only, you will see numerous complaints beginning after the date the OTA was released (8/27/14) complaining about the touchscreen controls.
I have downloaded the kernel source code from Samsung for both 4.2.2 and 4.4.2. Upon examining the kernel source, the Atmel touchscreen driver has been updated in 4.4.2. I believe this to be what is causing the problem. I am not sure if it is configured incorrectly or if it is just a poor driver. The Jelly Bean driver gave NO issues what so ever. I would revert back to 4.2.2 Jelly Bean if I could. I also compiled a kernel for KitKat which includes the Jelly Bean Atmel driver, however due to the locked bootloader, it does me no good.
What happens is this, you will have two fingers on the screen. Suddenly it is as though you lifted one, even if you are still touching the screen. Touches are erratic for a few seconds after this happens, then touch returns to normal temporarily until it happens again (usually only a few seconds later). This makes using the device for gaming extremely annoying, and difficult. This issue does not occur in normal use, only gaming, where there is rapidly changing multitouch inputs.
If any of you have noticed this, maybe you can contact Samsung/ATT complaining of the issue, if we're lucky maybe a patch will be released. Or it will be fixed in a future firmware update. I already wrote to both, ATT says they will forward the complaint to their management, Samsung has yet to reply.
http://www.samsung.com/us/support/contact / [email protected]
Also, this is a video I created demonstrating the problem. The video includes annotations describing the issue that can only be viewed from PC YouTube.
https://www.youtube.com/watch?v=3FMEPB51Y-4
Thanks for reading.
Has anybody with this device tried a multi-touch test? I'm starting to wonder if it's related to my screen protector. The issue only started after the KitKat update though, immediately after. I do a good amount of mobile gaming or I'd never have noticed it still to this day. Never presents itself outside of fps games.
Best way to check (within multi-touch test app):
Touch screen with two fingers.
Keep one stationary and rapidly slide the other around for a few seconds then stop and lift that finger only.
The stationary touch will act as though you lifted even though you didn't.
Sometimes touches will be erratic for a while if the test is repeated several times.
If anyone tries this please let me know if you have a screen protector or not and how it behaved. Thanks.
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
quakeaz said:
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
Click to expand...
Click to collapse
Its the phone mine does these same. Might just be a cheap screen make
Deonta23 said:
Its the phone mine does these same. Might just be a cheap screen make
Click to expand...
Click to collapse
Thanks for verifying. It's not the screen itself from what I can tell. I tried this on Jelly Bean with no issues. I did go through the kernel source for KitKat and believe it is the KitKat kernel touch driver. I am hoping for ATT/Samsung to release a kernel patch. The multitouch was perfect in JB.