I'm trying to determine whether my Nexus 10 is faulty or if I've found a bug in Android 4.4.4. Seems fine in earlier versions. Problem reproducible on Slimroms v8.0, and Cyanogenmod 11 (both based on Android 4.4.4)
This test should take less than a minute.
On the developer options, enable "pointer location" so that you see two lines intersecting on the current touch location. Drag your finger around the screen, perhaps on Google Maps (doesn't matter which app), ensuring that it scrolls smoothly and that the two lines are visible all the time.
Then, for about 5 to 20 seconds,quickly tap the screen with all ten fingers/thumbs, then try using Google Maps again (you can do the tapping on Google Maps if you like - doesn't matter where), with just one finger. Drag the map around, seeing if it's still smooth, and if the two lines stay on the screen at all times.
On mine, it's as if there's an invisible "grid" or lines on both the x and y axis, and when your finger passes over those lines no touch events are received. Scrolling around on Google Maps is jerky as your finger passes over those lines.
The problem doesn't only happen with "pointer location" enabled - that's just to make it obvious that there's a problem if you have one. Perhaps an app like "multitouch test" by "easy labs" (free, no permissions required) will make it more obvious. If you can't reproduce it, try the rapid tapping again.
The problem comes and goes after that.
No response, huh? For anyone reading this in the future, it seems to be a known (to users) bug which is being ignored by Google.
Related
Anyone experiencing this on EI22 ROMs, I suggest getting the Bubble Level app from the Market.
If in that app the bubble level graphic doesn't switch to the "line" version when tilting the device to an edge, you may have the same issue I did.
Tap Calibrate, Reset and then exit the app.
Go to the built-in Android Calibration in the Settings menu (under Display, toward the bottom). Try calibrating then with screen up (opposite of what many did with Froyo, but you can try that too if right side up doesn't work). See if your response of screen rotation gets quicker. It did for me.
The nice thing about this strategy is it doesn't involve anything difficult to do and seems to me a low-risk set of steps.
Hi,
I have observed in a few apps a certain problem: Some apps don't support the NST side buttons, so I scroll by swiping my finger over the screen. In most apps this works.
But there are a few where it does not work properly: Somehow these apps seem to have a problem interpreting my swipe correctly. Sometimes they correctly interpret it as attempt to scroll down, but very often they will also interpret it as an attempt to scroll up, even though I am making the same movement. This way reading a long article is really annoying because you always get sent back to the top of the article.
Apps in which I have observed this: Wapedia, International Herald Tribune, Read It Later (this last one does not exist anymore, as it has been replaced by "Pocket" which does not work on Android 2.1).
All of these apps seem to show exactly the same problem, so I suspect a common cause.
Did anyone make similar observations or maybe even has an idea for a fix?
Thanks!
I have the same problem for some apps. If I do long swipe up most of the screen there is no problem.
But it is annoying when I forget.
Greetings.
I discovered some smoothness/FPS issues with even the completely stock ROM install and I really would like your help replicating.
Test #1:
you need to be capable of visually perceiving consistent 60fps screen updates, vs. 30fps/hitching/stuttering/something less than 60fps
download and install LinkBubble Browser.
Go to twitter or google search, search for something, click a link, and use LinkBubble to open it.
in developer options, go to Input and check Show Touches
drag the LinkBubble bubble around with your finger in a circular motion in the middle of the screen
observe whether the bubble follows your finger as smoothly as the Touch Input indicator. Note: it will trail the Touch Input indicator, this is normal. What we're looking for is smoothness. Is it trailing at 60fps? Is it trailing as smoothly as the Touch Input indicator?
If yes, don't reboot for an hour, and try again
If no (me), reboot, and test immediately. Does it run more smoothly?
Test #2:
download and install Swype + Dragon keyboard
configure and switch to this keyboard
instead of continuing to read, you can watch this video, and replicate; otherwise continue reading
repeatedly tap the F and H keys with both thumbs at the same moment about 100 times (or until you observe it detecting a 'swype' instead of taps)
does Swype properly detect both the taps as independent key taps?
or does Swype incorrectly detect both taps as a Swype (line drawn on keyboard)
If it's properly detecting all taps, don't reboot for an hour, and try again
If no (me), reboot, and test immediately. Does it run more smoothly? For me it does.
here's what I've found so far:
uninstalling (disable/freeze is not sufficient, LG software seems to bypass this) SlideAside, Dual Window, and both of the LocationServices shown in Titanium Backup (make a backup of each before uninstalling!) and then rebooting seems to resolve these issues. So far, I think LG's Location Services are to blame. Having uninstalled both, everything is doing much better.
a factory reset stock device has these issues
fresh CloudyStock 2.7 install and factory reset has this issue
I've attached a LogCat from when it was hitching. The earlier one at 13-03 (1:03pm) was when it was hitching, the latter, larger file (14-52 aka 2:52pm) is when it was running buttery smooth. I need to look at these more closely. Maybe it's a garbage collection thing?
Maybe I need something from dmesg?
You decide.
This is really just a PSA for those having multi-touch problems with this phone including developers who may have customers using this device.
I recently noticed that the Bolt multi-touch capability seemed to be broken - at least for anything more than two fingers. Pressing chords with three or more notes on music synthesizer apps simply didn't work.
It would register two simultaneous fingers tapping the screen. However, any attempt at tapping the screen with more than two fingers simultaneously, registered only a single tap location. Holding multiple fingers down one at a time with a short delay between each finger would register all of them. I tested up to ten. So, multi-touch worked sort-of.
It occurred to me that HTC might be trapping multi-touch events with more than two fingers for some reason. Looking around the menus, I found out where they were doing it.
In the Settings menu under "Display, gestures & buttons" you'll find the "Media Gesture" setting that mentions allowing app to recognize "3-finger output gestures". This is some kind of feature to allow you to instantly connect to other devices using three finger gestures. HTC must have some silly API that traps, interprets and broadcasts these events for other apps including their own. IMO it's an ill-conceived feature to start with especially as it breaks the expected behavior of multi-touch AND it's on by default! Fortunately, if you disable that setting, the multi-touch facility goes back to normal operation as it is on any other multi-touch device.
Another feature nobody asked for.
Thanks HTC.
Arpman96 said:
This is really just a PSA for those having multi-touch problems with this phone including developers who may have customers using this device.
I recently noticed that the Bolt multi-touch capability seemed to be broken - at least for anything more than two fingers. Pressing chords with three or more notes on music synthesizer apps simply didn't work.
It would register two simultaneous fingers tapping the screen. However, any attempt at tapping the screen with more than two fingers simultaneously, registered only a single tap location. Holding multiple fingers down one at a time with a short delay between each finger would register all of them. I tested up to ten. So, multi-touch worked sort-of.
It occurred to me that HTC might be trapping multi-touch events with more than two fingers for some reason. Looking around the menus, I found out where they were doing it.
In the Settings menu under "Display, gestures & buttons" you'll find the "Media Gesture" setting that mentions allowing app to recognize "3-finger output gestures". This is some kind of feature to allow you to instantly connect to other devices using three finger gestures. HTC must have some silly API that traps, interprets and broadcasts these events for other apps including their own. IMO it's an ill-conceived feature to start with especially as it breaks the expected behavior of multi-touch AND it's on by default! Fortunately, if you disable that setting, the multi-touch facility goes back to normal operation as it is on any other multi-touch device.
Another feature nobody asked for.
Thanks HTC.
Click to expand...
Click to collapse
That feature has been there for several devices
Sent from my unknown using XDA Labs
Problem with "overly sensitive" touch screen; registers fingers just by hovering it
I changed to Lineage OS 14.1-20170412 yesterday, after having had an about 1-year old Cyanogenmod stable on it.
Now I got a smaller issue with it; I'm pretty sure it didn't do that right away after installation.
It started to register my fingers when they are already hovering above the screen, like 2-3cm away from it. It feels like a proximity sensor, just all over the screen, not turning off the screen when you get close but creating graphical hover effects:
When I'm in the Android settings for example, the settings category rows get a gray back color.
In Chrome, links get underlined when hovering them from far away.
The quick panel creates white bubbles around the tiles.
While this isn't causing any misbehavior (I can't actually press anything of those things by moving my finger up to 3cm towards the screen, and then moving it away immediately), it's visually annoying.
I did not do anything special since it started to happen, and already checked on the following:
- Glove mode is not turned on.
- There's no other "Accessibility" stuff turned on.
- When showing tabs in the developer options, it does not register it as taps, and does not start drawing a line when hovering the finger around on the screen.
Is there any way to "recalibrate" the "sensitivity" or turn this thing off it's a feature and not a bug?
Check Settings > Air view. I'm not sure about custom ROMs but on my stock ROM this is what causes the links in Chrome to get underlined when hovering.
I indeed found something in Settings which i must've accidentally enabled: Language & Input > Touchscreen Hovering (under Mouse/trackpad). When it's on, you get the effects I noticed, so i turned it off.