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?
Any way to deactivate this so the screen doesn't keep turning on/off every time I put the phone to my head? Thanks in advance.
I'm rooted and running Virtuous Sense if that makes a difference.
Sent from my HTC Vision using XDA App
Just wondering....why? You would be hanging up on people a lot. Hell in google voicemail I put the phone up to my ear and it pauses it all the time.
From my permarooted 1209mhz G2 with CM7 nightly 6
I just get a lot of calls. Looking at the phone when I get call waiting, or having to conference a call, or mute a call....always have to wait for the screen to turn on. It may only seem like a half-second to you, but when you use your phone non stop during the course of your business day it adds up to one big annoyance.
Flyin18T said:
I just get a lot of calls. Looking at the phone when I get call waiting, or having to conference a call, or mute a call....always have to wait for the screen to turn on. It may only seem like a half-second to you, but when you use your phone non stop during the course of your business day it adds up to one big annoyance.
Click to expand...
Click to collapse
Makes sense, but what about the risk of your ear hanging up on people?
From my permarooted 1209mhz G2 with CM7 nightly 6
I'm not 15 feet tall. I think that would have to be one big ear. The speaker is at the top of the phone, and the END button is at the bottom of the screen. I'm not too worried about my ear coming near it.
I'd rather just tap the power button to turn off the screen when I know I'm going to be talking for a while and no longer need the screen on to manipulate the call(s).
Sent from my HTC Vision using XDA App
Won't pressing the power button hang up on the person?
Sent from my HTC Vision using XDA App
I hope not.
BTW, does anyone know if I can deactivate the screen sensor?
I may actually switch from Sense back to CM7 because of this issue. With CM7 the sensor reacts much faster than with Sense. However I really am enjoying this Sense ROM so I'd rather not have to switch back.
Sent from my HTC Vision using XDA App
I'm pretty sure if you look in cm settings there's a place thatyou can set the screen to stay on on calls.. I know its there just not entirely sure where as I've been running miui for about a month now.. and its not necesarrily your ear.. if yourr cheek were to touch the screen that could cause it to hang up also
*I'm just sayin...
I believe you're correct about that feature in CM7. However, that feature, along with a couple apps I found in market, will keep the screen on and prevent it from timing out.....possibly even dimming the screen. However, the proximity sensor still kicks in and completely turns off the screen every time you put the phone to your ear. It's almost as if the proximity sensor has immunity from the feature list. Kind of surprised this hasn't been pursued before in here.
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'm wondering if this is possible, I'd like to keep the vibration notifications coming in, but I'd like to disable the screen on feature when a notification comes in. Any ideas?
>>>This<<< be of help for you?
Oskar-2 said:
>>>This<<< be of help for you?
Click to expand...
Click to collapse
No, it isn't.
He still wants to receive the notification on the watch and have it vibrate, just not activate the screen.
This is unfortunately not possible. The amount of control that Google has given us for notifications is absolutely pathetic considering that the entire purpose of this device is to provide notifications.
Dekz said:
No, it isn't.
He still wants to receive the notification on the watch and have it vibrate, just not activate the screen.
This is unfortunately not possible. The amount of control that Google had given us for notifications is absolutely pathetic considering that the entire purpose of this device is to provide notifications.
Click to expand...
Click to collapse
What's weirder is a lot of android handsets function this way (notification, screen remains off). Why they chose the other way round for the watch, who knows.
I'm bumping this cause I'm curious if anyone's found a work around for this.
I hoped Lollipop would bring this, but apparently it does not (from what I hear). Even if it requires unlocking the thing, installing a custom ROM/build.prop/etc/etc/etc.
Disable tilt to wake the watch.. In the android wear app
The watch will only light up when you touch the screen
Sent from my SM-N910C using Tapatalk 2
I'm having issues with the screen not turning back on after a call or even listening to audio messages. I have to relock and then unlock to get it to work, very annoying.
I'm on 8.1, on magisk with xposed.
Could someone recommend me an app or a module?
https://issuetracker.google.com/issues/71510515
You along with a bunch of us... ota messed it up
Good to know, I'm not the only one. Doesn't seem related to screen protector.
Really wish I can disable the proximity sensor for now.
I guess I came to the wrong thread. I don't have any issues like that or at least I don't notice it because I is the power button to turn the screen in/off all the time and I set my lock screen to not relock the phone for 5 minutes or something like that. That way I don't gotta enter my unlock code. There also is a setting which is supposed to keep your phone unlocked as long as you don't set it down. There also is a setting that keeps your phone from locking if you are within range of a Bluetooth (headseat maybe) device. I dunno try some of those options maybe you won't need to type your code in as much.
Personally I came here because I am looking for a way to completely disable my proximity sensor. I absolutely hate them on all phones. How stupid is it that they put the proximity sensor I right up next to where you have to put your hand if you want to pull down the menu bar??? It's like I go to pull down the menu bar - screen off. ****! Power button, slide open the lock screen (no code needed). Pull menu bar - screen off ****! Power.... Slide....menu bar - screen off. Of course it only does that during calls however that's a pretty annoying time because you're usually focused on other things and not wanting to **** with the screen going on and off.
Who the needs a proximity sensor to detect one's face anyway? I just click the power button every time I put the phone to my ear. Any time I don't do that, I run the risk of my cheek pressing the mute button for the 9000th time in my life. I do love Android though.
KirkH420 said:
I guess I came to the wrong thread. I don't have any issues like that or at least I don't notice it because I is the power button to turn the screen in/off all the time and I set my lock screen to not relock the phone for 5 minutes or something like that. That way I don't gotta enter my unlock code. There also is a setting which is supposed to keep your phone unlocked as long as you don't set it down. There also is a setting that keeps your phone from locking if you are within range of a Bluetooth (headseat maybe) device. I dunno try some of those options maybe you won't need to type your code in as much.
Personally I came here because I am looking for a way to completely disable my proximity sensor. I absolutely hate them on all phones. How stupid is it that they put the proximity sensor I right up next to where you have to put your hand if you want to pull down the menu bar??? It's like I go to pull down the menu bar - screen off. ****! Power button, slide open the lock screen (no code needed). Pull menu bar - screen off ****! Power.... Slide....menu bar - screen off. Of course it only does that during calls however that's a pretty annoying time because you're usually focused on other things and not wanting to **** with the screen going on and off.
Who the needs a proximity sensor to detect one's face anyway? I just click the power button every time I put the phone to my ear. Any time I don't do that, I run the risk of my cheek pressing the mute button for the 9000th time in my life. I do love Android though.
Click to expand...
Click to collapse
So it works too well for you with your finger but not enough for your face to prevent muting? LOL. Sorry never had that problem. I just avoid the middle if I had to get to the notifications during a call.
It happens often when I'm trying to toggle BT because my BT icon is directly under it.... For example. Anyway, I don't find it useful to even have an proximity sensor. That's why I stumbled in here, my search query was the exact title. I'm not really experiencing the problem the others were talking about though....
EeZeEpEe said:
So it works too well for you with your finger but not enough for your face to prevent muting? LOL. Sorry never had that problem. I just avoid the middle if I had to get to the notifications during a call.
Click to expand...
Click to collapse
xringo said:
I'm having issues with the screen not turning back on after a call or even listening to audio messages. I have to relock and then unlock to get it to work, very annoying.
I'm on 8.1, on magisk with xposed.
Could someone recommend me an app or a module?
Click to expand...
Click to collapse
It's an option to disable proximity in gravitybox.
Sent from my Pixel 2 XL using XDA Labs
KirkH420 said:
I guess I came to the wrong thread. I don't have any issues like that or at least I don't notice it because I is the power button to turn the screen in/off all the time and I set my lock screen to not relock the phone for 5 minutes or something like that. That way I don't gotta enter my unlock code. There also is a setting which is supposed to keep your phone unlocked as long as you don't set it down. There also is a setting that keeps your phone from locking if you are within range of a Bluetooth (headseat maybe) device. I dunno try some of those options maybe you won't need to type your code in as much.
Personally I came here because I am looking for a way to completely disable my proximity sensor. I absolutely hate them on all phones. How stupid is it that they put the proximity sensor I right up next to where you have to put your hand if you want to pull down the menu bar??? It's like I go to pull down the menu bar - screen off. ****! Power button, slide open the lock screen (no code needed). Pull menu bar - screen off ****! Power.... Slide....menu bar - screen off. Of course it only does that during calls however that's a pretty annoying time because you're usually focused on other things and not wanting to **** with the screen going on and off.
Who the needs a proximity sensor to detect one's face anyway? I just click the power button every time I put the phone to my ear. Any time I don't do that, I run the risk of my cheek pressing the mute button for the 9000th time in my life. I do love Android though.
Click to expand...
Click to collapse
Who needs a proximity sensor? Really? You basically answered your own question. To turn off the screen when you put it to your face so that your face doesn't press anything on the screen. Having to press the power button every time you put the phone to your face and then press it again every time you take it away from your face would suck.
jimv1983 said:
Who needs a proximity sensor? Really? You basically answered your own question. To turn off the screen when you put it to your face so that your face doesn't press anything on the screen. Having to press the power button every time you put the phone to your face and then press it again every time you take it away from your face would suck.
Click to expand...
Click to collapse
I always use speaker or bluetooth and proximity sometimes turns the phone off spuriously so I disable it.
Sent from my Pixel 2 XL using XDA Labs
Yeah.....no basically pressing the power button is where it's at. It the again I'm not one who likes everything done for me. Absolutely NO PHONE I've ever owned has had a proximity sensor that was worth a ****. They all, at one time or another, allow the screen to wake up subsequently letting the microphone mute button to enable. The mute button is another piece of Android trash that needs redesigning. It is not often that mute is needed so why not out that in a drop-down menu or something since it inevitably gets pressed during calls due to a ****y proximity sensor and Screen wake setup.
I also drive a manual transmission car. Actually the last 5 cars I've owned have been manual shifted. When YOU are in 100% control of your devices, there are certain niceities which are otherwise unavailable. But that's only if you're the type who doesn't gotta have everything done for them.
As far as you go buddy, if you like the proximity sensor that's fine. Personally I don't ****ing care what you like. thanks for a wasted Fred post which contacted my email to have me come back here to tell you what a waste of time that was thanks.
jimv1983 said:
Who needs a proximity sensor? Really? You basically answered your own question. To turn off the screen when you put it to your face so that your face doesn't press anything on the screen. Having to press the power button every time you put the phone to your face and then press it again every time you take it away from your face would suck.
Click to expand...
Click to collapse
KirkH420 said:
Yeah.....no basically pressing the power button is where it's at. It the again I'm not one who likes everything done for me. Absolutely NO PHONE I've ever owned has had a proximity sensor that was worth a ****. They all, at one time or another, allow the screen to wake up subsequently letting the microphone mute button to enable. The mute button is another piece of Android trash that needs redesigning. It is not often that mute is needed so why not out that in a drop-down menu or something since it inevitably gets pressed during calls due to a ****y proximity sensor and Screen wake setup.
I also drive a manual transmission car. Actually the last 5 cars I've owned have been manual shifted. When YOU are in 100% control of your devices, there are certain niceities which are otherwise unavailable. But that's only if you're the type who doesn't gotta have everything done for them.
As far as you go buddy, if you like the proximity sensor that's fine. Personally I don't ****ing care what you like. thanks for a wasted Fred post which contacted my email to have me come back here to tell you what a waste of time that was thanks.
Click to expand...
Click to collapse
Relax. It's not that serious.
Sent from my Pixel 2 XL using Tapatalk
No man, the point is that you quoted me so that I would be alerted to your message but didn't even attempt to input anything useful to the conversation. My post is actually a request, with explaination, asking if there is a way to do something. You on the other hand made a comment. This is XDA Developer's Forum. This isn't Facebook or YouTube where everyone has some smartass **** they can't resist saying. We is this for information. So again, thanks for your Nothing input.
EeZeEpEe said:
Relax. It's not that serious.
Click to expand...
Click to collapse
KirkH420 said:
No man, the point is that you quoted me so that I would be alerted to your message but didn't even attempt to input anything useful to the conversation. My post is actually a request, with explaination, asking if there is a way to do something. You on the other hand made a comment. This is XDA Developer's Forum. This isn't Facebook or YouTube where everyone has some smartass **** they can't resist saying. We is this for information. So again, thanks for your Nothing input.
Click to expand...
Click to collapse
I quoted you because you're so upset people don't agree with you that you can't express your frustration withOUT asterisk words. You got your answer:
"It's an option to disable proximity in gravitybox."
Move along.
Sent from my Pixel 2 XL using Tapatalk
Sure that's fine, be one of those snide Facebook commenters always gotta add their smartass quip or opinion like it's an itch you can't help but scratch. I just think it's pathetic that you get some kind of satisfaction out of that. But..... you know, everybody needs to feel like they make an impact in the world. Have a fufulling life. ?
EeZeEpEe said:
I quoted you because you're so upset people don't agree with you that you can't express your frustration with asterisk words. You got your answer:
"It's an option to disable proximity in gravitybox."
Move along.
Click to expand...
Click to collapse
.
So I assume you have earbuds, or if not, you can get some really cheap earbuds from the gas station, and when needed, you can plug it in, and it will register that it has earbuds in and will light up again, disabling the proximity sensor. You can leave it in as well, until you need it to talk, unless it will work while calling. This should work, I haven't personally tried it.
Solution
xringo said:
I'm having issues with the screen not turning back on after a call or even listening to audio messages. I have to relock and then unlock to get it to work, very annoying.
I'm on 8.1, on magisk with xposed.
Could someone recommend me an app or a module?
Click to expand...
Click to collapse
Hi,
Hope you managed to solve the issue.
If you haven't then
1. Install sensor disable from xposed repo. It's an old app so there are a few bugs when you try to remove the sensor as such.
2. Buy the Pro version or use lucky patcher to disable in app purchases for Sensor Disabler.
3. Go to the settings of Sensor Disabler and blacklist the apps that you don't want the proximity to work on.(I had problems with my WhatsApp. But it works perfectly now.)