Related
NOTIFICATION BAR scrolling down without touching it: Static Electr & Capacitive Scrns
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?
the only time I've had that happen to me is when I use a cheap charger I've got and yeah the screen just skitses out. I am using a hero tho but this is the first time I've seen anyone else encounter this so I thought il'd churp in.
I had something similar only once.
The notification bar went mad. It was flicking up and down constantly without me touching the phone at all.
I had to pull the battery to fix the problem.
Hasn't happened since.
Fon22
Happened to me also when loading a ROM in Nesoid.
So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?
quicksite said:
So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?
Click to expand...
Click to collapse
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Brilliant, Alex... You got right inside my head and answered exactly what i was trying to ask.... the physics of the system.
I'm okay with little glitches here and there, and I am sure I will learn to avoid proximity issues that tend to trigger these mis-fires... just as I learned to adjust my tap-key behavior in typing on the on-screen keyboard on capacitive screen vs all the resistive screens I had used before on Windows Mobile, where fingernails could & would engage the resistive screen -- vs learning that the bottom surface of the finger has to make contact on the keys on capacitive screen... (sorry i am USA and we still resist the world's metric standard, so i don't know the equivalent distance in cm,)... but it's over a 1/4-inch of an upward shift in the position of one's fingers above the capacitive screen from the tip of the fingernail.
But once you train your senses to activate the keys sensors properly, the finger impact behaviors of resistive screens goes away after a while (at least for me)
(oh, btw, I ordered the new HTC capacitive stylus which is a couple of months old now, but is an official DESIRE accessory, so that will be an interesting experience... the thing i miss most about the resistive screen and stylus was being able to scribble notes really fast, way faster than i could ever type -- and draw pretty detailed images or maps and directuions for people. so it will be interesting to see the granularity of control the capacitive stylus will give)
So thanks very much for giving me the exact level of detail I can process as a lay person.. and for assuring me, as the rest of you have as well, that this apparently comes with the territory of this phone -- and therefore should not be seen as a defect. Because i sure as hell didn't want to go shipping this phone back. I can live with an occasional spazzoid misread of intended impact spot on screen...
And, fnally, this was funny -- re the different degree of touch we all consider "normal" --
The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse
thanks!
Alex_w said:
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse
I was thinking it is softwarerelated. The bar remains halfway the screen, is in the layer below the active app, and jumps to front upon touching the screen.
I have the Problem, too. And that since Monday. I went mad since yesterday evening so i tried to go back to stock, unroot and all.
But the problem is still there.
How can i fix it? Or is my Phone damaged?!
The Notification Bar scrolls down without touching the display and then freezes the phone. so i must lock the phone and relock it and then i can use the phone but after a short time the same problem came back!!
So I reckon you're an undertaker for a living?
Sent from my HTC Desire using Tapatalk 2
erklat said:
So I reckon you're an undertaker for a living?
Click to expand...
Click to collapse
Sorry but i don't understand what you mean
The problem makes me crazy because i have now the stock rom because i thougt it was an issue due a custom rom or a kernel or something.
If you can help me please do that, this problem robs me to sleep
But i havent the Desire. I Have the HTC EVO 3D GSM
19Marc89 said:
Sorry but i don't understand what you mean
Click to expand...
Click to collapse
lol digging up the dead
Sent from my HTC Desire
Sorry but I do not understand the background of your information which is in context with my problem of the notification bar.
@19Marc89 He meant that you responded to a an old (dead) post. Listen, I'm trying to recondition an old Motorola Milestone (Droid) with a crazy touchscreen problem, whose cause I believe I've narrowed down to static electricity - can you do me a favor and try stroking the glass side of the phone lengthwise in one direction down your sleeve, preferably if you have a wool sweater on? Call me crazy, but this works for me, at least temporarily. I posted more here:
http://forum.xda-developers.com/showthread.php?t=1041943&page=5
install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!
quicksite said:
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?
Click to expand...
Click to collapse
REPLY :
install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!
I know I am many years late but did you somehow manage to solve this problem?
I noticed after upgrading to Lollipop that it was difficult to navigate menus near the top of the screen in some apps. I turned on the "pointer location" option and sure enough I found very strange results.
i.imgur com/tPdVowo.png (you'll have to add a period after the domain name, new user status prevents me from posting links)
This first screenshot is me running two fingers all the way to the top of the screen, and once i reached the top i ran them towards the edge of the screen. As you can see there is an area where the pointer location bugs out.
i.imgur com/bh5hWeV.png
This image is just a single finger running horizontally across the top of the screen. The top line is where my finger actually was, but the phone also registered extra touches as you can see from the line below. There's even a section where the top line didn't register at all.
This is a Verizon phone, never been rooted, and hasn't been dropped or wet. I noticed while making this post that the area i am having issues with aligns almost perfectly with the top part of Sense's notification menu.
Is this normal or do I need to exchange my phone?
I am having the same issue with my phone. When I turn on show touches in developer options or install a multitouch test app, it'll show an extra touch just below where I'm touching but only when I'm touching at the top of the screen. Stock lollipop, never rooted, no water damage.
Bump
same problem. do you have s-off? downgrade firmware and rom - maybe this fix problem?
bumbarush said:
same problem. do you have s-off? downgrade firmware and rom - maybe this fix problem?
Click to expand...
Click to collapse
I don't. I didn't want to do that yet. Was hoping to see if anyone else had the issue and if they were able to resolve it.
Just want to see if anyone was able to resolve this issue.
fixed!
we need the old piezo lighter's element. The phone must be turned off. A few strokes on the screen near the problem area, and voila, the screen works again. Do not be afraid, the phone will not be damaged
i
on russian:
http://4pda.ru/forum/index.php?showtopic=496511
I have a brand new device and to me it seems that it has some sort of protection of unwanted touches in a way that it, when you touch the screen to scroll or pinch to zoom (app independent), it waits a bit until it reacts to the movement of the finger which results in a movement delay.
When I put my finger on the screen and then move it e.g. downwards it does not react instantly. It seems like it's a software setting to prevent micro scrolls when u accidently touch the screen.
I try to explain it: I put my finger on the screen, move it down, the scroll does not start instantly but after a few milliseconds and then jumps (which feels like a single little stutter) after a threshold of minimum movement has been reached. I feel that this effect is more apparent the slower i move my finger.
When i touch the screen and then move my finger REALLY slow i can even move my finger a couple of cm before the scroll is recognized and is started by jumping to the point where it should have been when there hadn't been this micro touch/move protection.
This effect is NOT present when I touch the screen, move my finger around, stop moving and then start moving it again. No matter how slow i move it, the scrolling does not jump/stutter. This effect only happens for the initial touch/scrolling attempt.
All in all this makes the device feel a bit laggy since this does not happen on my 4y older phone. however, it seems to be software related. Anyone knows what I mean?
Edit: i understand that this makes sense when using an app where u get a pop up when touching and keep holding ur finger against the screen (e.g. in chrome when u want to mark text and then get the cut/copy/paste pop up). This movement protection helps to prevent unwanted screen movement which would prevent the popup because for a popup u need to keep touching without moving the finger. However, I feel that this protection and it's resulting delay is too strong and should be reduced because it feels not so smooth how it is now.
haitower said:
I have a brand new device and to me it seems that it has some sort of protection of unwanted touches in a way that it, when you touch the screen to scroll or pinch to zoom (app independent), it waits a bit until it reacts to the movement of the finger which results in a movement delay.
When I put my finger on the screen and then move it e.g. downwards it does not react instantly. It seems like it's a software setting to prevent micro scrolls when u accidently touch the screen.
I try to explain it: I put my finger on the screen, move it down, the scroll does not start instantly but after a few milliseconds and then jumps (which feels like a single little stutter) after a threshold of minimum movement has been reached. I feel that this effect is more apparent the slower i move my finger.
When i touch the screen and then move my finger REALLY slow i can even move my finger a couple of cm before the scroll is recognized and is started by jumping to the point where it should have been when there hadn't been this micro touch/move protection.
This effect is NOT present when I touch the screen, move my finger around, stop moving and then start moving it again. No matter how slow i move it, the scrolling does not jump/stutter. This effect only happens for the initial touch/scrolling attempt.
All in all this makes the device feel a bit laggy since this does not happen on my 4y older phone. however, it seems to be software related. Anyone knows what I mean?
Edit: i understand that this makes sense when using an app where u get a pop up when touching and keep holding ur finger against the screen (e.g. in chrome when u want to mark text and then get the cut/copy/paste pop up). This movement protection helps to prevent unwanted screen movement which would prevent the popup because for a popup u need to keep touching without moving the finger. However, I feel that this protection and it's resulting delay is too strong and should be reduced because it feels not so smooth how it is now.
Click to expand...
Click to collapse
I have the same problem!!!!
Interesting, I can confirm this too.
I'm currently using OOS, did you tried any custom rom? We could see if it's rom - related.
It's an Android thing.
I don't have that problem with my 5T, on 4.7.6
morback said:
Interesting, I can confirm this too.
I'm currently using OOS, did you tried any custom rom? We could see if it's rom - related.
Click to expand...
Click to collapse
i'm gonna install a custom rom now. i'll report back!
since i guess it's more of a kernel thing, i'm gonna install blu spark or franken kernel as well.
no improvement whatsoever.
i tried:
audax rom -> no change
audax rom & blu spark kernel -> no change
oos oreo beta -> no change
i feel that the effect is worst in chrome. it is not so apparent in youtube scrolling or picture pinch2zoom. however, in chrome the whole experience is just really laggy compared to my 4y old device which is on 4.4.4 kitkat.. :/
that is so sad since i'm 99% sure this is just a software issue that could be easily fixed..
anyone of you guys who also recognize this behaviour have another android device to compare?
You are using oos custom roms. When it's software related you won't solve that problem. I'm using omni and cannot reproduce what you've written.
Trinaaa said:
You are using oos custom roms. When it's software related you won't solve that problem. I'm using omni and cannot reproduce what you've written.
Click to expand...
Click to collapse
you can't know whether it is oos related. it could also be the case that this is just how android 7.0 handles touches these days. my last device was 4.4, so maybe things changed to the worse. also, it is most likely kernel related.
i also think the issue is not recognizeable when you are not used to a 100% buttery smooth device, like my nexus with an AOSP rom was. i bet people coming from a samsung phone would have no clue what i'm talking about even when im doing it right in front of their face
the issue is most apparent when scrolling in chrome. it is negligible when scrolling through other apps, but for chrome it is annoying.
haitower said:
I have a brand new device and to me it seems that it has some sort of protection of unwanted touches in a way that it, when you touch the screen to scroll or pinch to zoom (app independent), it waits a bit until it reacts to the movement of the finger which results in a movement delay.
When I put my finger on the screen and then move it e.g. downwards it does not react instantly. It seems like it's a software setting to prevent micro scrolls when u accidently touch the screen.
I try to explain it: I put my finger on the screen, move it down, the scroll does not start instantly but after a few milliseconds and then jumps (which feels like a single little stutter) after a threshold of minimum movement has been reached. I feel that this effect is more apparent the slower i move my finger.
When i touch the screen and then move my finger REALLY slow i can even move my finger a couple of cm before the scroll is recognized and is started by jumping to the point where it should have been when there hadn't been this micro touch/move protection.
This effect is NOT present when I touch the screen, move my finger around, stop moving and then start moving it again. No matter how slow i move it, the scrolling does not jump/stutter. This effect only happens for the initial touch/scrolling attempt.
All in all this makes the device feel a bit laggy since this does not happen on my 4y older phone. however, it seems to be software related. Anyone knows what I mean?
Edit: i understand that this makes sense when using an app where u get a pop up when touching and keep holding ur finger against the screen (e.g. in chrome when u want to mark text and then get the cut/copy/paste pop up). This movement protection helps to prevent unwanted screen movement which would prevent the popup because for a popup u need to keep touching without moving the finger. However, I feel that this protection and it's resulting delay is too strong and should be reduced because it feels not so smooth how it is now.
Click to expand...
Click to collapse
I noticed this. Does feel like lag. Haven't experienced this on the pixel 2
After installing a new display module on my OP5T, I noticed something weird. The display seems to be perfect, either original or a very good one. Bright, perfect color, no issues with it whatsoever. I've tested it in multiple apps (like Draw on screen) and it works perfectly, recognizing every input, never interrupting the line while I drag. All the buttons I press on the screen in apps work perfectly. When typing letter never gets missed.
However, it does have a SLIGHLY less sensitive touch. Like, if you very lightly tap it with a finger, it won't register, while before, it would. The difference really is miniscule. I usually wouldn't tap that lightly on it either way. However, it works up to be an annoyance, because now certain "swipe left-right" actions lack a certain "inertia" to them, which I think is because of this.
Like, before, to move around the launcher screens, I would just swipe sideways lightly and carelessly and it would switch to the next screen, now it will start moving and roll back. To make sure I switch a screen I have to apply effort with my finger. Same thing with opening notifications or app drawer.
Is this a hardware issue? Faulty touch? Or can I just increase sensitivity a bit with some software tweaking?
dude i am also in the same boat. Did u by any chance buy the replacement screen from lcdbaba?
I'm having problems with my Fold 4 not registering taps. I tap a space on the screen and nothing happens. I do it several more times, and finally it responds. I haven't seen a clear pattern yet, because it's somewhat intermittent. Has anyone else seen this problem?
I'm slightly suspicious of the Microsoft launcher here., but I suspect that's because it gets the majority of my taps, it being the launcher. I haven't had that problem in the past.
Just a minute ago I sat down to make a video of what I was seeing in case I thought an exchange might help. It happened on the first try, and I wound up having to press it five times with escalating pressure to finally get it to react. For the record, I have not seen a correspondence between pressure and the problem. I think I just naturally start pushing harder and when it works, it feels like it was more pressure. But when the problem isn't occurring, it takes very little pressure to register a tap.
Not using the Microsoft Launcher, but I am using SwiftKey, and I do have the same issue, especially with the space key. Mostly with the outside screen BTW.
Ah, I should have been more specific. Yes, I've only seen the problem on the outer screen so far. And I'm using gboard for my keyboard.
I've had a similar issue but it seems to have gotten better. Being intermittent makes it hard to pinpoint
I initially transferred apps and data from my Note 20 and was having issues on the outside and inside screen of taps not registering. Finally did a FDR and set up from scratch, haven't had the issue again. I always setup from scratch and took a shortcut this time, lesson learned!
ggrant3876 said:
I initially transferred apps and data from my Note 20 and was having issues on the outside and inside screen of taps not registering. Finally did a FDR and set up from scratch, haven't had the issue again. I always setup from scratch and took a shortcut this time, lesson learned!
Click to expand...
Click to collapse
I actually did an FDR last yesterday to try and solve the problem. Naada. It was still there for me.
I'm currently using Samsung's OneHome UI to see if it's something with the MS Launcher. Good god, I hate their launcher!
It feels like the sensitivity on the outer (cover) screen is too low, and combined with much smaller keys on keyboards (I use GBoard) there are plenty of missed hits and no response. Try turning on touch sensitivity and see if it improves ( Setting -> Display -> Touch Sensitivity. Mine went a tad better. I also changed the layout preferences to 'normal' keyboard height and most of my misses are now gone..
I'm having same issue but not with the keyboard but with tapping on apps on the home screen. I'm able to almost reproduce it every time in the middle of the screen. Is there any update on this issue?
I've got same issue that a tap on a app gets no action. Happens occasionally. Must be a bug.
After a factory reset mine has come back too. Hopefully we will get some bug fixes with the September security update.
imanony said:
I'm having same issue but not with the keyboard but with tapping on apps on the home screen. I'm able to almost reproduce it every time in the middle of the screen. Is there any update on this issue?
Click to expand...
Click to collapse
Same. I never have a problem in application, it's only when I'm interacting with the launcher.
I think the issue is with the refresh rate dropping. I used the galaxy max hz app and increased the base hz on the phone and I'm noticing response being much better now.
I also have this issue on my Fold 4's cover screen. I've always used the debug option to show where I touch, and when my touches don't register I still see the touch indicator, so I can only assume this is a software issue not deciding what to do with the touch. I think One UI might be overly sensitive for gestures, and detects taps as drags/swipes. A mini swipe on an app or folder on the home screen for instance won't do anything (which happens to me frequently).
I've had that problem quite a few times as well, not enough to drive me crazy but enough to be slightly annoying. It only happened when taping on the bottom of the screen. It often registered my taps as a swipe up. I saw the homescreen starting to go up slightly as if it was going to enter the drawer. Then one day I realized it was my way of tapping the screen that was the culprit. The way I hold my phone makes me ever so slightly swipe up as I tap the screen, but only when taping the bottom part, if I tap anywhere else, I don't tend to move my finger up as I tap. Of course, I'm talking minuscule amount of swiping here, probably less than a millimeter. It's just the way I hold the phone and move my thumb, it's personal, and I think everyone is going to have a different experience depending on how they hold their phone and tap the screen. Anyway, I'm not saying "you're using it wrong", because I think it's a problem samsung must fix, as I don't have that problem on any other phone. Probably too sensitive. I just tried to reproduce the problem as I write this message, and succeeded twice in less than 20 tries, so definitely the problem is still there. It's just that now I tap straight on instead of "sideways", and it works just fine. Just a workaround, I know...
Edit: on the cover screen, of course. Inside screen works fine with crooked taps.
Glad im not the only one. On the outer screen i have had times where I have to tap something 3 times for it to register... I never had this issue with my Z Fold 2