Develop Bugs

NOTIFICATION BAR scrolling down without touching it: Static Electr & Capacitive Scrns

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?

[Q] Strange issue with touch detection at the top of my screen

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

Navigation bar issue after oreo update

Hi guys,
Would need some suggestions from you to understand what might have gone wrong.
I have noticed that after updating to oreo the navigation buttons are not properly placed. They are a little bit above the normal possible and doesn't seems to be in the middle of the black bar.
If you look close you can see that while i hover over the button the effect doesn't covers the entire area around.
Your help is much appreciated .

Rishabhv said:
Hi guys,
Would need some suggestions from you to understand what might have gone wrong.
I have noticed that after updating to oreo the navigation buttons are not properly placed. They are a little bit above the normal possible and doesn't seems to be in the middle of the black bar.
If you look close you can see that while i hover over the button the effect doesn't covers the entire area around.
Your help is much appreciated .
Click to expand...
Click to collapse
Can you share the wallpaper please?

Try to turn on and off the fingerprint sensor gesture in Moto Actions, so the navbar should disappear and reappear. If this not solve, try to reboot. If also reboot does not solve, try to clean cache. At the end, if clean cache does not solve, you can only try a factory reset.

Rishabhv said:
Hi guys,
Would need some suggestions from you to understand what might have gone wrong.
I have noticed that after updating to oreo the navigation buttons are not properly placed. They are a little bit above the normal possible and doesn't seems to be in the middle of the black bar.
If you look close you can see that while i hover over the button the effect doesn't covers the entire area around.
Your help is much appreciated .
Click to expand...
Click to collapse
The same for me.
Tryied wipe cache, disabe and enable fingerprint functions and nothing.

Seen this on Lenovo forums and reddit as well. Apparently it's a burn-in preventative method built into Android Oreo. It's supposed to move the buttons and the hit marker shade with every lock and unlock of the device to keep the pixels within that area from being overutilized and thus, burned in. Have you checked to see if the location changes little by little every time you turn the display on and off?
Either way, not an issue for me. I'm perfectly fine with my fingerprint gestures so I can get full screen real estate, not to mention all the z3 play renders point to there being a software button equivalent to the fps gestures we have, which kills the benefits of having such in the first place

NonexistentParan0ia said:
Seen this on Lenovo forums and reddit as well. Apparently it's a burn-in preventative method built into Android Oreo. It's supposed to move the buttons and the hit marker shade with every lock and unlock of the device to keep the pixels within that area from being overutilized and thus, burned in. Have you checked to see if the location changes little by little every time you turn the display on and off?
Either way, not an issue for me. I'm perfectly fine with my fingerprint gestures so I can get full screen real estate, not to mention all the z3 play renders point to there being a software button equivalent to the fps gestures we have, which kills the benefits of having such in the first place
Click to expand...
Click to collapse
Yea, i did noticed that. Not only while i lock and unlock the phone but also when i try to turn on and off the navigation buttons it is changing position a bit eveytime. I always had those buttons turned on and this has made me to use the fingerprint sensor for navigation. ? I am assuming there are going to be other users as well with this issue in their moto with oreo

Crix.Ful92 said:
Can you share the wallpaper please?
Click to expand...
Click to collapse
I am using Backdrops application for wallpaper

Rishabhv said:
Yea, i did noticed that. Not only while i lock and unlock the phone but also when i try to turn on and off the navigation buttons it is changing position a bit eveytime. I always had those buttons turned on and this has made me to use the fingerprint sensor for navigation. I am assuming there are going to be other users as well with this issue in their moto with oreo
Click to expand...
Click to collapse
Same issue here with Brazil version. Sadly, it is very annoying.

I can confirm this issue. The exact issues as described by you all. Thing is I don't have any issues with the placement even though they slightly vary in positions. Just that the navigation buttons aren't as responsive as they were in Nougat.

NonexistentParan0ia said:
Seen this on Lenovo forums and reddit as well. Apparently it's a burn-in preventative method built into Android Oreo. It's supposed to move the buttons and the hit marker shade with every lock and unlock of the device to keep the pixels within that area from being overutilized and thus, burned in. Have you checked to see if the location changes little by little every time you turn the display on and off?
Either way, not an issue for me. I'm perfectly fine with my fingerprint gestures so I can get full screen real estate, not to mention all the z3 play renders point to there being a software button equivalent to the fps gestures we have, which kills the benefits of having such in the first place
Click to expand...
Click to collapse
So... this isn't an actual bug? For me its pretty annoying. especially when i'm on spotify or google play music for example and I unlock the phone and everything gets out of place and it rearrenges again. I factory reseted it but didnt work, was thinking about flashing a stock firmware through adb but now I'm not sure that it is even a problem to begin with.

Nav bar bug
It's is a bug and i have a solution ?

I have exactly the same issue with XT1710-09 RETEU on Oreo. I already got used to it but for me it's a bug of Moto Launcher. When I use LawnChair Launcher the problem seems to disapear.

Can you turn it off?

is there not a way a way to put the navigation bar on moto z2 play like there is the 3rd generation

This is not a bug. It's the design to prevent OLED screen burn-in
At first I thought the same. But after some research I found it as the design and to prevent screen burn-in for OLED display.

Scrolling stops when i take off my finger PLS HELP

So i bought a oneplus 5t with a slightly cracked (only one crack on the top of the screen, and it's not catastrophic) but (almost) fully functional screen.
It detects every touch accurately, 3 fingers same time, etc.
The only problem is, when i want to swipe (even on the home page, when u wanna scroll down the status bar f.e.), it stops scrolling the exact moment i take off my finger, or scrolls just a little bit.
I'm aware, that the crack on the screen might be causing it.
I did the factory mode calibration. I did reset the whole phone, hoping the problem somehow gets solved, but it didnt change anything.
The problem is very consistent, therefore it's useable, if you accept the fact, that the screen responds only when your finger is touching it and no longer.
I feel like if i could change the sensitivity of the touchscreen, or the responsiveness on the gestures it receives, i were able to make it just as new.
Oneplus 5t (OOS 10.0.1, TWRP and Magisk installed, in case you have some app or sth that requires root)
(I couldnt find the parameters that has relation to touch sensitivity in the build.prop file, i'd be glad if someone linked me a guide)

Question Touch/tap problems

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