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?
Hello,
I just noticed a couple of days ago that a section of my screen has become slighly unresponsive. It appears to be intermittent, and Swype in Landscape mode is primarily affected.
In landscape mode, keys m, j, and u are not responding. During shutdown as well, the power off confirmation both yes and no button locations are unresponsive.
These areas of the screen are responsive usually, except during power off confirmation and using Swype. Could this be a software issue?
Does anyone know what might be the cause, or how to fix it?
I have not yet tried any fixes, though I may just restore using a backup ROM I made shortly after I rooted my device. If that doesn't work... then :|
EDIT: This appears to have started shortly after I installed LauncherPro, or it may have also occurred since I removed all pre-loaded Google Apps to replace with the newest versions off the Market. :\
EDIT 2: Restored my ROM, m key has regained some responsiveness, other keys no good. Using Swype, the line goes near them, and then just breaks, sometimes. Other times, if I swype really fast, I can passover and include the key, but cannot swype up vertically among them. Unable to press them directly either.
Switch to Android keyboard and things seem to be ok again... fully responsive... this is weird.
EDIT 3: Crap... one row in the middle seems to be affected... somewhat. Downloaded a drawing app, and this one row doesn't want to play nice. It responds properly in most instances, yet there definitely seems to be a problem.
EDIT 4: Appears that a section of my screen is non-responsive. A whole row. Argh. When I move shortcuts, passing nearby this 'dead row' the icons jump. In swype, it acts like an invisible barrier, either I move really fast and it sorta jumps across that key, or I move really slow, and it's like my finger is lifted off the screen. Android appears to be compensating heavily for the non-responsive section and guessing my inputs. Tapping in this area still appears to be somewhat responsive, dragging or swiping across this area is producing very mix to bad results.
I need to have the touchscreen/digitizer replaced, right? The LCD panel appears to have no issue. Argh. Could it be due to the InvisibleShield I put on top?
I had a similar problem with my G2. I tried putting one of the Zagg protective covers on it and immediately afterwards the touchscreen would not respond properly. I would have dead spots on top right of screen and bottom left. At first I thought it might have been from the solution seeping into the phone, but I think I might have used too much pressure and damaged the digitizer. I ordered one earlier this week and will update you with my results.
The screen is capacitive... which means that your finger completes an ELECTRICAL CIRCUIT. If your screen protector is blocking current at all, this will manifest as a loss of sensitivity.
The second thing to understand is that you can't just touch the screen with your finger to complete the circuit, the other end of the circuit has to be completed as well. The metal ring around the screen is the other side of the circuit! You need to be touching that metal ring in order for it to work properly. Even with the phone just resting on your hand, you may not be contacting the ring and may experience a loss of sensitivity. In portrait mode, try clamping your fingers around the back of the phone to contact the ring on the far side. In landscape mode, use your index fingers to touch the top part of the ring.
If these suggestions don't help (including removing the screen protector), then you most likely have a bad digitizer. Check the ribbon wires to make sure that they haven't pulled out at all before replacing.
Just replaced my digitizer and it works great now.
Sent from my Nexus One using XDA App
johntinman said:
Just replaced my digitizer and it works great now.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The one u bought is it the one with t mobile with it??
Sent from my HTC Vision using XDA App
Yes, i got it from repairsuniverse.com for ~ $70
Sent from my HTC Desire using XDA App
After a few months of use...
Notifications - opens every (ear listening) call, apparently my ear shape hits the top bar and the machine thinks I want to see notifications. Since the machine knows it's orientation - it there a way to prevent an ear-activated notification request when phone is vertical, or during a call?
Screen overlays - I bought some and added one, it got scratched and I peeled it off, and now I see at least 2 more! I think I see a glass that fills the frame, a smaller overlay, and another, smaller overlay. My basic thought is to keep peeling as they scratch. I want to make sure that if I get to 'glass' that I have not messed anything up - a decorative overlay (maybe with the browser size slider markings?) or a functional part of the touchscreen assembly. Is there anything I can mess up if I just keep peeling?
Thanks any and all!
Eep, I know know if I'd "keep peeling". If you feel like the screen itself is pulling back, I wouldn't do it. Resistive touchscreens do have 'layers' if you will...
Weird, in WinMo the prox sensor should work just fine - make sure it's enabled, the screen should turn off when your face gets close to the screen.
See this video for a demo.
Thanks for reply.
I'll look for cabs that may have affected the sensor (basically OEM update + a few goodies) as I can find no HTC/WinMo setting.
Were you saying you don't know if you'd... or now know?
Should there be a factory layer, exposed the user, that I should NOT peel off? ( I knew factory touchscreen at one time, they were soft overlays over CRT's.)
THX
tshephard said:
Thanks for reply.
I'll look for cabs that may have affected the sensor (basically OEM update + a few goodies) as I can find no HTC/WinMo setting.
Were you saying you don't know if you'd... or now know?
Should there be a factory layer, exposed the user, that I should NOT peel off? ( I knew factory touchscreen at one time, they were soft overlays over CRT's.)
THX
Click to expand...
Click to collapse
I have no idea, since I can't see what you're peeling. I've never completely disassembled one of these, but I've seen pics/videos. I also know a little bit about how touchscreens work (a little!) and I know there are layers that you should not be peeling back - without seeing a detailed pic or the device in person, I don't feel comfortable saying "yea, peel away" when you could be potentially damaging your phone.
OK - I removed all cabs, still not working, did reflash, same, did task 29 and reflashed, still not working.
Found something called 'Advanced Configuration', played with Light sensor settings, and now that works great, never knew it didn't before (auto did nothing).
Is there something similar for proximity settings? ( I would have thought a connector inside was loose - that's why I messed with light sensor - but that 'healed' and now I want to 'heal' Prox too!)
I peeled down to a full chrome-filling ?glass? layer that looks thick and just a bit wavy - still no Prox activity - and put a new screen saver on that - so that's not it.
Anyone know settings/cab/registry for Prox activity?
Still don't have proximity function... I'm thinking in call, object (ear) near HTC symbol should blank screen and also deny touch response.
I downloaded registry editor, and found some settings. Tried, well many combinations but no results.
I do find that some don't stay set - I change them, and reboot, and they go back to say "0". They are ProximityDetectStatus and ProximitySensorOn . I'm thinking (supposition) resistry settings are static - that they do not reflect machine activity, only editor or user's other software actually changing values to store - rather than indicators of current machine activty (button is now pressed, button is now un-pressed). Is my regedit process (change, close, boot) correct?
I'm left wondering - are registry settings reflective of current activity while regedit is open or even the moment it opened? IE, can I use regedit to show me if a switch is pressed?
Anyone else, help?
I'm on OE ROM, CHT and CHT editor
all was well with my Dinc except for I had 2 blown speakers. I ordered new ones from ebay and replaced both. After replacing both, the bottom of my screen seems to not be working correctly. Whenever I go into SMS and hit the bottom for the keyboard to come up, it doesn't. I try using Whatsapp and it does the same thing. Its weird because the "attachment" button on the bottom of a sms works fine. It might just be that bottom/middle area. Is there any way to fix this? I had a feeling once I removed those ribbons to replace my ear speaker It was gonna mess something up .
I'm on MIUI android 2.3.5.
Is there any fix to this? or am I gonna have to just live with it for awhile?
EDIT: forgot to add, when I'm in WhatsAPP and I try clicking the bottom to bring out the keyboard, it highlights the message a little bit above where the text box is at, so its not reading where I'm pressing correctly. Its reading a little higher when I press in the bottom/middle area of the screen. Hope I explained that well enough for you guys to understand
A quick way to test if your screen is buggered is to downloading a drawing app and try to draw on the parts of the screen that you think aren't working. If you can't draw there you either a.) didn't connect a ribbon all the way b.) damaged a ribbon c.) electrically damaged something.
or d.) terrible coincidence and your touchscreen was on its way out anyways
It might be time for a new touchscreen. I had a similar problem where my screen wouldn't respond to touch in certain parts. I never took apart my phone prior to that so it wasn't (i don't think) my doing. Replaced with a new screen and I was good to go.
Take apart your phone and disconnect/reconnect the ribbons to ensure they are on there good. If that doesn't solve it I'd say a new touchscreen is in your future
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