Touch input not detecting small movements. - Shield Tablet Q&A, Help & Troubleshooting

Nevermind, sold the tablet.

have you tried setting the delay to disabled in settings direct stylus input?
Had similar issue with tegra note 7 and that helped sort it
But it wasn't as extreme as you've described
Fwiw I've tested my shield tab and it doesnt show what you've described. It tracks really fine movements very well
Sent from my SHIELD Tablet using Tapatalk

Related

Sometimes unresponsive touch screen? i9020T

evening all
Does anyone else find themselves sometimes having to tap multiple times to get something to work? (e.g. one example - clicking into a text box to bring up the keyboard)
I'm running 4.0.3 but to be honest it was the same with 2.3.6. It's certainly not terrible / unusable and I'm wondering if it is merely "lag" or an intermittent hardware fault.
Screen test applications seem to work fine by the way, possibly pointing towards "lag"?
By the way, If I tap VERY quickly too those taps are often NOT recognised, but I tested that scenario too with a friends' HTC desire and his was the same, sometimes recognised and sometimes not.
I previously had an i9023 by the way, on which I never noticed an issue. Do the 2 models have different controllers I wonder!
B
I find its finger oils that cause that. A quick wipe or turning screen off and on quick restores functionality.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
I'm having similar issues.. either lag or the answer mentioned above. It could also be a software glitch. However I doubt it's a hardware problem since for that, the screen would be dead in a certain area 24 7 which is not your problem.

Air Control HD

Works great on my Nexus 7 but on the TF700T I can't consistently draw trajectories to the landing. Tried all kinds of setting, in and out of the game, but no luck. Anyone successfully using this?
Just gave it a quick spin and it seems to work fine here. I only tried it for 2-3 minutes though, since I'm horribly bad at it
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Works fine for me too.
Are you on JB?
Yep, I'm on JB. Arre you using the HD (paid) version? If I draw a long trajectory line, the line stops after a short distance. I've tried turning off h/w acceleration within the game and different tablet settings. Also reinstalled the game, to no avail.
Air Control HD works fine here.
Sent from my ASUS Transformer Pad TF700T
Had a thought and downloaded Sketchbook Mobile and found that when I draw in it I see the same issue as in Air Control - as I draw my finger across the screen in Sketchbook, a line will be drawn for a short distance and then will stop. So the screen is losing my touch/drag detection.
I tested it with Air Control HD, yeah. Bought it during the 25c sales earlier, haven't had a chance to test it properly until now. Works fine, though. I also tried drawing some long lines in Sketchbook Pro (yet another 25c purchase ) and it works fine as well.
It seems that your touch panel might be defective. You could try a re-flash of JB manually, but I don't know if the touch panel firmware will be reinstalled as well then. I doubt it, but it's worth a try.
Edit: If you're not on JB yet, you might want to try updating that. There have been some touch panel firmware updates since the release of the tablet, maybe that'll help.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Odd thing is that something like dragging an icon from one end of the screen to another works just fine and I don't see any other anomalies other than this line draw issue.
sparksd said:
Odd thing is that something like dragging an icon from one end of the screen to another works just fine and I don't see any other anomalies other than this line draw issue.
Click to expand...
Click to collapse
And another - I can readily draw lines in the Notemaster app so it would seem that this is not a h/w problem. I have cold booted several times, too.
This is a h/w problem. Here is my RMA request to Asus:
Center of screen is dead and unresponsive to touch.
I can go into Developer Options and enable Debugging Mode. If I enable Pointer Location and then draw my finger back and forth across the screen in landscape mode I can see an area about half an inch wide in the middle of the screen where the drawn line is broken. This dead area extends from the top of the screen to the bottom. If I enable Show Touches, I can see the visual feedback jump over this dead area, not glide through it. I have done a factory reset but no change occurred.
Ah, too bad :\ Good luck with the RMA, though!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[Q] Note 10.1 + Bluetooth Keyboard&Mouse

Hello!
I have one question that I could not find answer on internet. I have note 10.1 and have been using BT keyboard - Canyon, and it has been working flawless with a bit disconnect here and there. But recently I have bought BT Mouse - HP and it works just great. But when they are both connected at same time they both misbehave a lot. If I use mouse my keyboard just dc and it won't respond unless I hit few keys and sometimes keyboard lags/button stuck like "dddddddd...." untill my mouse dc. When my mouse dc keyboard is fine once again and this apply to vise versa but with mouse it is not responded well like move around for 2s late...
So now my question is if there is any program or script that will help with this situation? I know tablets aren't made to be used as PC but on college my battery last for like 9-10 hours while others with laptops cant get 3-5 hours full writting. I can even play games and my battery wont be below 30% when I get home. I have rooted ofc and I am using android revolution HD 9.0 since it is most polished. I dont wanna go to other android stock roms cuzz s-pen does not work well. I do not use pen often but heck, if I have it I want it to work perfect.
I hope someone had similiar situation and had it fixed.
Cheers
I have the same problem. I did not find a solution to bluetooth interference either... so I am thinking to move to usb based keyboard and mouse for better user experience.
Sent from my GT-N8013 using Tapatalk
smrsxn said:
I have the same problem. I did not find a solution to bluetooth interference either... so I am thinking to move to usb based keyboard and mouse for better user experience.
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
Yeq but i want BT i was checking utube for some tips. All i have got is that some brands dont have problem. Most problem cause microsoft products with android on other hand ms mouse is better...so yeah hope someone can help.
Cheers
I have found a way to help it. I bought external keyboard helper for 2€ and it works amazing now. I have also tryed Null keyboard which is free and it basicly just hides ur onscreen eyboard from appearing. Guess this was the problem.
I hope someone will also fix their issue with this 2 apps. Cheers
It's those devices. I have several BT Keyboards and Mice and they work perfectly together. There's no app that can really do anything about stuttering mice or duplicate letters, as the issue is in the RF layer of the BT protocol.

Anyone have luck with game mode miracast

I can get it to connect and play for maybe 2 minutes until it starts freaking out and I have to disconnect it. The latency is great up until then. That feature is a very important one to me but it won't work. I know it's in beta but i'm not sure if that's what needs to be worked on or if they just want to reduce the latency more and improve the image quality. I have other miracast devices and they act the same way with the exception of 2 of them. The nexus 7 doesn't work right, i have a galaxy s4 clone and my main phone that work badly.
I used it one night while playing ShineRunner with my wife. I had her screen miracast on the TV so I could help her out. It worked great for about 10 minutes then started acting up and I had to kill it.
I wanted to know the same thing and am shocked nobody has really tested a few devises for least lag and shuttering.
I bought the Actiontec ScreenBeam Pro and updated its FW.
I'd say the lag is minimal and is not my main issue now.
Random shuttering can be a pain. It can vary from a only few times to a lot. At this point it seems to be trigger by some games more than others.
Afterburner with a touch profile shuttered a lot (35% of the time) not sure if it a resource issue with the touch profile or general interference in my room.
I played dead trigger 2 with native controls shuttered a lot less(10-15% of the time)
I had the device less than 5 ft during my tests.
This site has done some basic latency tests a handful of these miracast devices. It seems the Netgear Push2TV (PTV3000) had the least lag when used in a pc environment.
http://data.withinwindows.com/miracast-display-devices-and-windows-81-compatibility/
I think I will go buy the Netgear Push2TV tonight on my way home from work and test it.
Note
Having a game mode on the tv helps a lot with lag. If you stack the lag with the non-game mode picture processing of the tv and the miracast protocol it becomes very noticeable.
It's a good thing I searched the web first before buying a Miracast dongle. Sounds like it's not yet stable for gaming.

Modern Combat 5 MOGA Controller Fix

After much messing about we have Modern Combat 5 & MOGA controller working with limited lag. The secret is to remove any additional helper apps you have installed for the Moga, remove the controller from Pivot and resync as B MODE.
Then start Modern Combat 5 and set your Sensitivity to 100% and Aim Sensitivity to 75% (Thanks bradleyg5 for the settings)
It's not perfect but it's considerably better than A mode and is close to playable with only a slight slugish feeling, also gone is the Iron site bug which is great and makes it much more playable.
androidizen said:
After much messing about we have Modern Combat 5 & MOGA controller working with limited lag. The secret is to remove any additional helper apps you have installed for the Moga, remove the controller from Pivot and resync as B MODE.
Then start Modern Combat 5 and set your Sensitivity to 100% and Aim Sensitivity to 75% (Thanks bradleyg5 for the settings)
It's not perfect but it's considerably better than A mode and is close to playable with only a slight slugish feeling, also gone is the Iron site bug which is great and makes it much more playable.
Click to expand...
Click to collapse
It won't work with the pocket, as it has no b mode nor could I even get any input from it in game whatsoever. Just a warning unless someone has a solution. The Pocket seems not to work with MC5.
Archienj7 said:
It won't work with the pocket, as it has no b mode nor could I even get any input from it in game whatsoever. Just a warning unless someone has a solution. The Pocket seems not to work with MC5.
Click to expand...
Click to collapse
You can get it to work with the Universal MOGA Driver. But the problem is that the pocket has only one row of back buttons for example you can't shoot because there is no button on the moga for So we have to wait until a proper support from gameloft comes...
flopower1996 said:
You can get it to work with the Universal MOGA Driver. But the problem is that the pocket has only one row of back buttons for example you can't shoot because there is no button on the moga for So we have to wait until a proper support from gameloft comes...
Click to expand...
Click to collapse
My moga universal driver app crashes when I hit the enable driver button, on my galaxy s5
please take no offense but i feel like your fix is more of a semi functional work around that should be obvious to most people right away
when i saw the game was out, i bought it and immediately began looking for my moga pro. i saw that the phone recognized the moga in "a" mode, but the mc5 app didnt detect it, so i flipped the mode to off and then to "b" and once again the os saw the controller, but this time mc5 recognized the controller and so i was happy until i noticed how slow/low sensitivity was.
i cranked up the sensitivity to 100%, but it still is about 30% too slow for my liking.
a true fix/solution would be to get the controller working whether its in moga's mode, that appears to be loosing support, but this could be slow too, or getting hid mode to work with a acceptable output/input.
i wonder is there is someway to adjust the hid joystick sensitivity. im guessing with 6axis or what ever its called probably works beautifully since its touch emulation with tons of tweaks, realizing that the on screen thumb sticks are fast enough as is.
Thanks worked great
potna said:
please take no offense but i feel like your fix is more of a semi functional work around that should be obvious to most people right away
when i saw the game was out, i bought it and immediately began looking for my moga pro. i saw that the phone recognized the moga in "a" mode, but the mc5 app didnt detect it, so i flipped the mode to off and then to "b" and once again the os saw the controller, but this time mc5 recognized the controller and so i was happy until i noticed how slow/low sensitivity was.
i cranked up the sensitivity to 100%, but it still is about 30% too slow for my liking.
a true fix/solution would be to get the controller working whether its in moga's mode, that appears to be loosing support, but this could be slow too, or getting hid mode to work with a acceptable output/input.
i wonder is there is someway to adjust the hid joystick sensitivity. im guessing with 6axis or what ever its called probably works beautifully since its touch emulation with tons of tweaks, realizing that the on screen thumb sticks are fast enough as is.
Click to expand...
Click to collapse
There is an app for touch emulation. But still not playable It's called Game Controller 2 Touch.
What makes it Unplayable? Seems like mc5 wouldn't even know it's I/O was being spoofed, let alone care?
I'm going to some reading on that app you pointed out. If it works the way I envision it i will be tossing some coin towards the dev. Thanks
Sent from my SM-N900P using xda app-developers app
Still a tad bit laggy. May need to switch to my PS3 controller and use the touch emulation for now.
potna said:
What makes it Unplayable? Seems like mc5 wouldn't even know it's I/O was being spoofed, let alone care?
I'm going to some reading on that app you pointed out. If it works the way I envision it i will be tossing some coin towards the dev. Thanks
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
ok, so i bought the app and i have been messing around with for 3 days and i still dont have it working, the dev points towards 2 issues, one being kernel permissive issues and another problem with knox. i tried 2 of the 3 fixes and i cant get it, but i also dont know what i am doing. i emailed the dev last night so we will see what happens. i will try to report back.
potna said:
ok, so i bought the app and i have been messing around with for 3 days and i still dont have it working, the dev points towards 2 issues, one being kernel permissive issues and another problem with knox. i tried 2 of the 3 fixes and i cant get it, but i also dont know what i am doing. i emailed the dev last night so we will see what happens. i will try to report back.
Click to expand...
Click to collapse
The Six axis app does work pretty well. Not lag in the inputs, but the need for proper HID implementation would be better. Or at least release the updated for A mode on the Moga Pro.
I know the thread is nearly dead but I have a question. Has anyone been able to use touch emulation with MC5 and a MOGA Pro? Every app I've tried won't register touch emu for my MOGA, MC5 just continues registering the controller as input. I want to use touch emu because the sticks are god awful for aiming with such low sensitivity. And yes, ivebgot it set to 100%. Any help please?
How to turn 180 degrees, i am new to this
I have a problem with moga pro wont recognisw my controller it works on the begining you chooae multiplayer and as soon as the game starts ir wont respond its on b mode and the controller works with other emulators so its not a hardware problem does any one know why

Categories

Resources