the HOX is my first Android phone, and it's mostly fine, but there are annoyances.
One is the length of time the volume overlay stays on-screen when changing volume. It's visible almost two seconds, which, at least to me, is really annoying, especially since it is a rather large, opaque overlay right in the middle of the screen. It's especially annoying while watching a video. Does a stock Android do this as well?
Anyone know of an app to circumvent this? I haven't found anything.
rib king said:
the HOX is my first Android phone, and it's mostly fine, but there are annoyances.
One is the length of time the volume overlay stays on-screen when changing volume. It's visible almost two seconds, which, at least to me, is really annoying, especially since it is a rather large, opaque overlay right in the middle of the screen. It's especially annoying while watching a video. Does a stock Android do this as well?
Anyone know of an app to circumvent this? I haven't found anything.
Click to expand...
Click to collapse
Every android device has it, but you can just tap screen anywhere except the volume bar and it will disappear immediately
Send from my HTC One X.
POOOLSKAAAA BIALOOOO CZEEERWONIIIII!!!!!
Hey thanks, but that doesn't work for me in full screen mode unless I touch twice and each touch is still registered, so my full screen video player then displays a menu and reacts unless I use a safe touch area. Still kind of annoying imho.
rib king said:
the HOX is my first Android phone, and it's mostly fine, but there are annoyances.
One is the length of time the volume overlay stays on-screen when changing volume. It's visible almost two seconds, which, at least to me, is really annoying, especially since it is a rather large, opaque overlay right in the middle of the screen. It's especially annoying while watching a video. Does a stock Android do this as well?
Anyone know of an app to circumvent this? I haven't found anything.
Click to expand...
Click to collapse
I dont think there is an app for this. But, there might be some custom roms that have tweaked the overlay time.
Venom ViperX JB takes about 3 seconds. It really irritated me on stock, while playing games! aargh!
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?
Hi guys,
First time android user here. I've had a search on google and on this forum and I can't seem to find an answer to this so:
The HOX displays music controls in a widget when the lock screen is activated. However when there is no signal (such as when I am underground) this is replaced by a gigantic "no signal!" notification.
This is really annoying as it means I then have to go through the password screen and switch to the player before being able to switch track.
Is there any way to disable this notification? I mean, I can see there's no signal right there in the top corner...
Thanks in advance.
Bump
The lock screen player is amazingly buggy.
The controls often fail to work, and when there is no signal that "no signal!" message will often randomly switch back and forth with playback controls entirely unpredictably. I've come to the conclusion that this is a bug so hopefully there'll be a fix soon.
It's disappointing to see how rough around the edges a lot of the sense stuff is. It has very good intentions but frankly if this is supposed to be HTC's answer to iOS it's got a looooong way to go.
FodT said:
It's disappointing to see how rough around the edges a lot of the sense stuff is. It has very good intentions but frankly if this is supposed to be HTC's answer to iOS it's got a looooong way to go.
Click to expand...
Click to collapse
iOS doesn't even do anything, thats why it appears to work. theres no actual functions to get buggered up in the first place.
Thanks, but that doesn't actually help me with my phone. If you haven't noticed I bought an android device, not an iPhone.
FodT said:
Hi guys,
First time android user here. I've had a search on google and on this forum and I can't seem to find an answer to this so:
The HOX displays music controls in a widget when the lock screen is activated. However when there is no signal (such as when I am underground) this is replaced by a gigantic "no signal!" notification.
This is really annoying as it means I then have to go through the password screen and switch to the player before being able to switch track.
Is there any way to disable this notification? I mean, I can see there's no signal right there in the top corner...
Thanks in advance.
Click to expand...
Click to collapse
one way i got round this is by pressing power button a couple more times to get the controls back on the lock screen when screen switched on again. might work for you too. still better than going through password etc.
but i agree not clever from htc. it's things like these which make products well tested and thought through.
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
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.
Thid weird issue started today in the morning, first I noticed that the clock widget had changed size, and that the led me know ring around the cam hole was out of place, but, when trying to write in whatsapp, I no longer could make the keyboard to appear by taping the wrinting field, in fact, nothing located in the bottom worked, what is odd, the bottom gestures worked, as I hid the nav bar since day one, tried everything, changed dpi, changed keyboards, retired the screen protector, wiped cache, to no avail, reluctantly, I updated to android 10, but no luck, after digging more, I found a work around, I changed the resolution from quad hd to full hd, now all is normal, but, this is just a work around, not a real solution, somebody have an idea of what would be the reason for this?
Did you have your phone linked to windows, your computer online and the phone screen displayed at that time? In this case, if you chose to use your computer's hardware keyboard in Your phone settings on your computer, then, when trying to write something in whatsapp, the virtual keyboard on your phone is not displayed or it is partially displayed. In my case, using the AI Type keyboard, only the top row of the keyboard was displayed because the app thought I'm using my computer's keyboard.
Sent from my SM-N975F using Tapatalk
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
winol said:
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
Click to expand...
Click to collapse
Was your phone charging at the time by any chance?
I found the solution!
I had the exact same problem with my note 10 plus, the gestures worked, and I tested the bottom part of the screen to make sure everything was working and it was, but the buttons in apps like instagram at the very bottom of the screen still were unresponsive most of the time. The solution is to ho to your settings, switch the navigation bar to the other gesture variant and then back to you preffered one and it should work. It worked for me.
Thanks man, I just found what triggers the issue, as odd as it seems, changing resolutions from qhd to fhd id what causes the issue, odd, because I used a bixby routine to save power at nights, by setting medium power saving, which among other things, lowered the screen resolution to fhd, when the routine ended, it should reverse to qhd, and that precisely triggered the issue, I used this routine for months, until, out of the blue, it started to cause this problem