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'm not sure if this is something that's already been observed, but it's certainly not something I've seen in any of the One X's promotional material.
Essentially, the touch screen seems to actually extend to below the screen, encompassing all the buttons. That is, the buttons actually aren't discrete tap zones, but rather part of the digitizer that simply doesn't have a screen behind it.
This can be seen on the (stock) lock screen, where you can pull down the ring, and still manipulate it's position while your finger's over the top of the buttons.
Anyway, I'm not sure if there's any practical way that this can be used (not being a developer myself), but it does seem like it could be used for gestures, as we saw a few years ago on the Palm Pre.
It was like this on my DHD too. It's awesome for games as long as you don't tap while swiping across the home button.
Sent from my HTC One X using xda premium
This is the behaviour I've seen on almost every android-phone I've had.
Its because the whole front panel is a digitizer so instead of manufacturing separate parts for the buttons they can cut costs and make one part.
Noticed this when I scrolled past the bottom of the screen while picking music to listen to. Bloody nice feature, I've never seen a phone do that before. It's also neat because it seems that when I drag up from the bottom to close the notification bar, the phone knows that I hit the home button but that I meant to drag the notification bar up, so I don't accidentally go to the homescreen.
I had noticed this soon after getting my HOX. It's really handy, though I wouldn't really call it a feature.
I had an issue pop up about 5 days ago that I haven't been able to find any help about so I was hoping someone could point me in the right direction. When touching the top of my screen from about mid-screen all the way to the left edge half the time it won't recognize my input now. The status bar still expands so the issue is starting right below that. Alot of times when I am trying to use a back button on the top left corner or type an address into the web browser etc the screen will not register my touch at all. Maybe 1 out of 30 taps it will work but this is baffling me. I have tried fresh rom installs and switching keyboards/apps but that doesn't do anything. Could it be screen calibration or the screen going bad?
the easiest way I can explain this issue and consistently replicate it is if I take an app on the home screen and long press and try to drag it to the "remove" trashcan, about the time I get to the trash can the app will jump above the trashcan.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
I posted this on Android Central, hoping to see if anyone on here has any information regarding this.
So I've noticed that anytime I'm on a phone call, it requires a little more effort to successfully pulldown the notification shade.
Usually I just quickly flick from the top of the screen with my right thumb (and I mean a very quick flick), but anytime I'm on a call, that same motion doesn't fully register. Instead I see that the notification shade looks like it will come down but it retracts as if it was an accidental gesture. In short, it seems like it wants more effort before being pulled down. Once I slow down my pulldown gesture, then it registers and pulls down.
Funny though, tapping the top of the screen registers.
It's almost as if the sensitivity of the screen drops or they've got some logic that makes you use more effort.
Anyone else have this problem. I can't decide if I should return/replace the phone over this. It's really infuriating though.
Sent from my HTC 10 using Tapatalk
I think I have experienced the same thing on the 10 and my M7 as well, but I wouldnt call it an issue just yet as it appears to be intentional.
Tarima said:
I think I have experienced the same thing on the 10 and my M7 as well, but I wouldnt call it an issue just yet as it appears to be intentional.
Click to expand...
Click to collapse
I'm almost positive it's intentional (as others have noticed it too); nonetheless, any help getting around it would be appreciated.
Sent from my HTC 10 using Tapatalk
Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
marshle said:
Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
Click to expand...
Click to collapse
I tried to replicate what your talking about. However, I couldn't do it. Maybe because I'm using Nova launcher, which may be a viable option for you. A factory reset might be helpful, however, we all know how much fun that ISN'T! Definitely an interesting issue your having. Then again, I think these devices have a mind of their own at times ?
Thanks for your reply. Forgot to mention, I have tried safe mode and done a factory reset and it did not remove the issue. It seems after a factory reset you are still on Oreo 8.1, so I'm not able to confirm it the issue exists in 8.0. I also have tried Nova Launcher.