Problem with "overly sensitive" touch screen; registers fingers just by hovering it - Galaxy S 5 Q&A, Help & Troubleshooting

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.

Related

Putting PPC (Harrier & iMate) app on Treo 700wx Issues

Hi,
I have an application which has been running nicely on Harrier and iMate devices, well any PPC devices really because of their rectangular screen shape.
My client has gone and bought some Palm Treo 700wx devices, and they have a smaller square screen.
In the resource of my project the screens are designed to fit PPC. When it runs on the Treo the Treo automatically pops up a scroll bar to allow the whole view to be seen.
The issue is when I first go into the app I can't see the top of the screen, about 20 odd pixels heigh aren't displayed. The scroll bar still displays and I can scroll down to the bottom of the view, and when I scroll up again the top of the screen is still out of sight.
If I exit the app just by tapping on the x in the top right corner (so the app is still running, not exiting properly via my Exit button which shuts down the app), I exit the app and then when I go back into the app the screens are displayed correctly, there is no missing space at the top of the screen.
If I exit the app via my exit button and then start the app again, the top of the view is missing again.
Does anyone know why the screen isn't displayed correctly when I first enter the app, or why it should come right when reloading the view again? Has anyone else had problems with screen layout when putting PPC apps on the square Treo 700wx?
Thanks
It sounds like you have a 'refresh' problem. I haven't encountered this my self and it is really hard to diagnose when you don't even tell us what language your app is written in, but basically here is what I think happens:
When your app is launched, part of its window doesn't get properly painted (not sure why exactly).
When you click the X the app isn't closed, but minimized.
When you return to it the window is maximized and repainted. Second repaint goes correctly.
The quick solution to this would be to force a window refresh just after the app is fully started.
Sorry I forgot to add the language.. it's written in eVC++ 3.0
I'll give the refresh a go, thanks
Further Questions..
I thought that minimising and then maximising the screen fixed the problem, but only partially..
Because the screen in resource is designed for regular PPC it is bigger than the Treo 700 screen size, so the OS automatically shows a scroll bar.
The new issue I'm seeing is to do with the scroll bar. The steps I take to reproduce the issue are:
1. Go to View1, and I scroll down the view (I'm using CView not CDialog)
2. Go to View2
3. Go back to View1. When I go back to the first view the scrollbar is scrolled down in the position I left it.
4. Scroll up to top of view and some of the controls in the wrong place. Some controls I dynamically create in OnInitialUpdate, and as part of the Create() I pass in CRect to tell it where to create the control.
If I set CRect.top to say 10, it's created 10 down from the top of the visible screen. The problem is that because I've scrolled the view previously the view draws it 10 down on the visible portion of the view.
I had thought that the easiest solution would be to always reset the scroll bar to the top of the view before creating my controls, but I'm not sure how to force the OS scroll bar to the top of the view. I've tried SetScrollPos(0,0) or ScrollWindow(0, y). ScrollWindow moves the actual view up or down, but the OS scrollbar is still in the same position.
Any ideas on how to set my view window to the top and to reset the scrollbar?
Thanks again
How to refresh a view?
I have sorted the issue mentioned just above, by finding the scroll position and factoring in that when I set the value of CRect area of the controls I need to dynamically draw.
I'm now just left with the first issue, of when I first start up the app the top part of the window and scrollbar are covered by the Title/Taskbar at the top of the screen.
If I close the app via the x button and restart the app, the issue resolves itself. Or if I open up any dlg like the About screen or even display an AfxMessageBox, when I close the dialog the original screen is redrawn correctly, in the correct position and scroll bar fully shown.
I have tried calling RecalcLayout(), RefreshWindow(), UpdateWindow(), Sending WM_SIZE messages and a whole range of things, but I can't seem to get the screen refreshing correctly apart from when I open any dialog and close that dialog.
When you close a dialog what messages get sent to the previous view that force it to redraw? Does anyone have any suggestions how I can force a refresh myself?
Thanks again
Did you try InvalidateRect?
I am getting a bit rusty with MFC, since I now try to do things the hard way and use pure win 32, but this should work.
If you can't use it as a class member, call the API directly using you view GetSafeHwnd() function for window handle). Use NULL for lpRect to redraw the whole window and FALSE for bErase to prevent flickering.
Note that UpdateWindow() only triggers repaint if part of the window becomes invalid (the contents needs redrawing).
No I hadn't thought of using InvalidateRect(), so I should give it a go.
In the end I just wanted the issue fixed so opted for a quick 'n dirty solution of displaying a temp CDialog as soon as the app starts and calling EndDialog() immediately in the OnInitDialog() so the dialog disappears before you see it.
It worked and the original screen gets updated to correct size, layout and scroll bar.
Cheers.

HD2 rotation options and keyboard anomalies

i've searched for ways to open up other rotation angles as well as autorotation for any and all apps under the sun. most people suggest bsbtweaks and it really does do the job, but only rotates to the allowed 270degrees angle (thats -90degrees). effectively, it just adds the window class to the list of window classes that the built in HTC g-sensor mechanism will give respect to.
so i looked some more and found "changescreen" to fit the bill. after setting up exceptions, it works quite well to allow all other applications (except for the exceptions which include sense) to rotate to 90degrees, 180degrees (this looks way cool some times!), and the usual 270degrees.
HOWEVER, the point of this new thread is to discuss something that seems to be quite an attractive option if it can be made to work 100%. i've noticed that the onscreen landscape keyboard is MUCH more usable in the 90degrees rotation. this is because those damned cursor keys take up 0.5 inch of space that is balanced out by the hardware keys on the other side, thus placing the rest of the keyboard SQUARELY in the middle of your thumbs! contrast this with the experience on the default 270degrees rotation where the cursor keys and hardware keys end up on the same side, forcing the user to stretch out the right hand thumb to reach the middle of the keyboard.
the amazing thing is that keyboard really works 99% properly in the 90degrees orientation. the 1% catch? the little preview squares that appear while tapping a key seem to be using a buggy rotation matrix when the screen is in this angle! effectively, this makes the preview squares upside down and on the wrong side of the center line of the keyboard!
so for me, TWO things would make life much sweeter on the HD2:
1. keyboard preview squares should appear right side up and on the correct area near the tapped key in 90degree rotation.
2. i would also like to DISABLE the 270degree rotation altogether and force the HTC g-sensor mechanism to think that the 90degree rotation is DEFAULT. i know i can achieve this partially using "changescreen" but sense will still rotate ONLY in the 270degree direction in the album and music tab. with this tweak, one can rely on the built in mechanism and also be able to enjoy the keyboard in the more comfortable 90degree rotation.
any 1337 h4x0r222 with some 1337 suggestions/tweaks?
some updates...
first, there is another anomaly i didn't notice before pertaining to the thumb friendly scroller that pops up when touching a scroll bar. this popup scroller is also being drawn upside down and on the wrong side of the screen in 90degree rotation.
other updates include:
1. tried toggling HKLM\System\GDI\Rotation\LandscapeMode from 0 to 4, followed by soft reset, no joy!
2. tried toggling HKLM\System\GDI\Rotation\LandscapeFixed from 1 to 0, followed by soft reset...the right handed and left handed options in Screen under Settings->System become available but the g-sensor autorotate doesn't seem to respect the choice set here, so no joy!

Possible rotation lag fix

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.

Turn off s-pen hover function

Is there any way to disable the s-pen hover function on the galaxy note? In many apps I get s-pen clicks all over the place, completely unintentionally, because the screen detects the pen hovering close to the screen and reads it as clicks. This is really annoying and I need to turn it off. Most of the time I only want the screen to register my actual clicks with the pen, not the hovering.
bo1e said:
Is there any way to disable the s-pen hover function on the galaxy note? In many apps I get s-pen clicks all over the place, completely unintentionally, because the screen detects the pen hovering close to the screen and reads it as clicks. This is really annoying and I need to turn it off. Most of the time I only want the screen to register my actual clicks with the pen, not the hovering.
Click to expand...
Click to collapse
There is an option under Settings> Pen Settings> Hovering pen icon..try disabling it & see if it helps..
Did try that, it only turns on and off the icon or dot showing where the pen is hovering. It does not change the behaviour of registering clicks when just hovering or even just having the s-pen close to the screen. When I got my Note it already had android 4.0.4, but from what I read, the Note did'nt even have the hover functionality before it got ICS. In my opinion the whole hover-thing is flawed, on my Note anyway. Sometimes it responds to hovering with clicking everything, and sometimes it don't.
Your pen is slightly bugged out. Try shaking it a little or gently tapping the front end of the pen (where the tip is) against your hand.
The pen point still has a contact made inside the pen and causes phantom presses.
The pressure sensor may be stuck. Does it draw a line in S Memo when hovering? The line is supposed to get thicker when you press harder and no line at all when not pressing. When the Note first came out, a lot of people had the problem. There were fixes.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
this is not a Q&A forum
I'm having issues with my note 3. It keeps drawing a line while hovering on text documents? Please what do I do?

Screen overly sensitive

I've got the VS995 with alpha rom and so far it's working great but I've noticed particularly today the screen is very jittery. What I mean by this is that when I'm typing by tapping (swiftkey) the keyboard, it registers too many letters or when I'm using the swiping method it breaks up the single swipe into mulitple words even though I've not lifted my finger. There is also a problem when I'm scrolling up and down my app drawer it will jump into an app I've not tapped on. All this has become worse since earlier today when I disabled all the verizon apps.
Is there any way I can change the sensitivity of the touch screen to limit these false touches.

Categories

Resources