As many of you know, this annoying bug still isn't fixed in any AOSP rom for the G3 after all this time. For me, it's worse than the slightly worse camera issue, because after a few days, I always give up and go back to stock because it's really annoying when, for example, I have to make a call in a hurry and this happens, very frustrating.
Some findings about it:
- Doesn't happen in all the calls, seems to be random, but longer calls seem to produce the bug more frequently
- Enabling touch feedback in dev settings shows what the problem is: there's a ghost touch present on the screen (sometimes more than one) after taking the phone from our face, which makes it seem the screen is being pressed while it's not in reality
- Swiping the screen with 2-5 fingers in any direction makes those ghost stucked touches go away
- Brightness is decreased when this happens
Possible fixes I tried and none worked:
- Enable immersive mode for the dialer and disabling swiping on the status bar to change brightness - makes the brightness bug go away but not the stuck screen.
- Disabling proximity sensor in calls - works, but the screen is still on, sometimes I disconnect the call with my face by mistake.
- Some combination of llama or tasker profiles - Could work but I don't know how to. My solution would be "when in a call, and turn off and lock the screen - then, when we take the phone off our face, turn on and unlock the screen. This would theoretically work, don't know.
So, any ideas?
Related
Hey, everytime I am in a call, my ear taps the taskbar and it opens the notification window which covers my call screen. I have googled and searched this forum with no success.
Apart from TouchLockPro, was just curious as to if there is anything that addresses this issue?
Thanks in advance.
Do you have something (case?) blocking the proximity sensor? The screen should be turning off as soon as you put the phone to your ear.
Yes I do. I've just tested it out, that seems to be the problem. So is there any tweak to prevent this?
i know even with the screen turning off with the proxy censor i will find i am in the screen with the connections and battery info when i am done with a call... its kind of annoying and worrys me a bit i might accadently end the call when the screen is off.... also the flip over to make it a confrence phone is a 50/50 thing... this device is so glitchy
I randomly get this too, I think sometimes the sensor isn't used.. There are times I've noticed I can cover it up completely with my thumb and the screen doesn't go off, but other times it works just fine.
Ryryq said:
Yes I do. I've just tested it out, that seems to be the problem. So is there any tweak to prevent this?
Click to expand...
Click to collapse
Tweak...some testing to see where the sensor is (somewhere along the top near the HTC logo) and an X-acto knife to the case?
same thing happens to me, most of the time somehow I turn on airplane mode and the call disconnects.. sigh
TouchLockPro has a feature which turns the screen off using the G-sensor, but it's not just for calls, if you have it horizontal it'll be on, and if vertical it suspends/screen turns off; this would be good if it was just for calls, especially for those that use a case.
I'm just starting to use TouchLockPro (http://forum.xda-developers.com/showthread.php?t=444215) and I have most of the locking features turned off - I just hit the power button if I want to lock it.
It does keep the screen locked during a call so I no longer hit the buttons. Plus - when it unlocks I'm right back, exactly, where I left off.
There's lots of options to tweak, I think there's something for just about everyone.
I LOVE unlocking with the zoom bar - first time I've used that thing on my phone
~Eric
eknutson said:
I'm just starting to use TouchLockPro (http://forum.xda-developers.com/showthread.php?t=444215) and I have most of the locking features turned off - I just hit the power button if I want to lock it.
It does keep the screen locked during a call so I no longer hit the buttons. Plus - when it unlocks I'm right back, exactly, where I left off.
There's lots of options to tweak, I think there's something for just about everyone.
I LOVE unlocking with the zoom bar - first time I've used that thing on my phone
~Eric
Click to expand...
Click to collapse
Awesome. Mind sharing what settings you have enabled, please?
Sure
Light Sensor, Stylus Sensor, GSensor, Nav Sensor, :
Nothing checked (all disabled)
Keyboard:
Use Slider, Suspend On Slider In, Slider Out Disables LockMode and EnableInputAtSuspend are all checked, everything else is un-checked (HTC Lock API, Double TouchPanel Lock and KeepAliveAlways are un-checked.
BattClock:
just some preferences set for appearance
Telephone API:
Everything is checked (except light)
Software:
Nothing set up
Other Settings:
AutolockOnPowerOn and UnlockOnACPower are checked, everything else is un-checked (added vibrates Lock/Unlock once - I like the extra notification)
~Eric
thanks! works like a charm now, is there any way to lock it if it is idle for like 30 secs or something without havin to hit the power button
There's a number of ways to lock it using the various sensors - you can try one of those and see what fits your habits / style best. You can also click on the BattClock icon to get the menu - the lock icon is right there. That's 2 steps though...
~Eric
Hi,
as measured by Z-DeviceTest, the proximity sensor on my Desire is stuck at 0.000 cm in all lighting conditions (including a very bright torch right on top of it).
At first I suspected this was the known problem with dust settling on the sensor, but I've blown and sucked (teh-eh) with everything I have, from every angle, and the sensor is still stuck at that value.
The problem shows up both in CM7 and with the stock firmware.
I have to assume the sensor is broken.
I'm looking for ways to disable the proximity sensor, and in particular to stop it from locking the screen during calls. Naturally, since the sensor is stuck at 0.0000 cm, any time a call is initiated the screen locks up, preventing me from ending the call, dialing tones and so on.
Alternatively, I'd be happy with a way to override the screen lock via hardware buttons. The power\unlock button doesn't work
Inserting a headset during a call does unlock the screen, but naturally this is not a satisfying solution (for example, I can't use this method to make calls while driving, using the speaker).
Solutions tried with no positive effect:
- editing build.prop with "ro.proximity.delay=0"
- using trackball\volume button wake
- using screebl, screen off to control automatic screen locks
Thank you for your time.
Anyone have any pointers?
Is it really hopeless?
Are you root? If so have you considered flashing a rom with the option to disable the proximity sensor? (for example miui-au has that option)
Yes, I have a rooted device. I didn't know miui had that options, I'll check it out; thank you!
Apologies if this has been addressed before, but I searched and couldn't find something exactly like this...
Randomly one of 3 screen issues seems to be occuring on a daily basis:
1) Auto-Rotate stops working. Cannot get screen to rotate without reset (Yes, I've made sure auto-rotate is on in settings)
2) Screen will not Auto-Off. Even if I change settings to 15 secs, screen will not turn itself off. I have to manually turn it off. And, if I receive a text or any kind of notification it will light up again and stay on indefinitely.
3) Screen will not turn back on when trying to wake up device. Hitting the home button and power button both have no effect. Although the LED is usually blinking, and it seems the phone is still on.
For all 3 of the above issues, manually pulling out the battery and reseting the phone that way seems to always work. But, this is an annoying process to have to go through on a daily basis.
Also, I've noticed that these 3 symptoms don't occur simultaneously. For example, yesterday it wouldn't auto-off, but rotation would still work.
Not running any custom ROMs either
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Not So Pro said:
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Click to expand...
Click to collapse
Is AOD on or off? What happens when it's on?
Badger50 said:
Is AOD on or off? What happens when it's on?
Click to expand...
Click to collapse
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Not So Pro said:
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Click to expand...
Click to collapse
Quite possibly so. I know nothing about snap face, snap chat, or whatever these social media apps do. Although, you may try clearing the app data and cache on said app to see if it helps. No guarantees though. As is the case with many things android! ??
I've had the same issue ever since I installed, I believe, the nav bar immersive mod. Not sure, around same time. I was able to hurt power button twice for camera and that would pull it up and u could switch back to screen. I don't have xposed or Snapchat, so I don't think either of those are it. It's random when it happens to me.
I've had similar issues. I'm not rooted and have never used Snapchat or AOD. I do use immersive mode for some apps so I've thought that might be causing it. Like stated above, I can get the screen to come on my double tap to open the camera or just holding the phone face down and tap the back a couple times then flip back over and the screen comes on.
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
shmity said:
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
Click to expand...
Click to collapse
Ok so a little more testing. When Ambient display is set to always on, I have no issue, maybe a slight lag when waking/unlocking. When ambient is set to tap or pick up i get issues, when ambient display is set to off at all times, i have no issue. Plugging the phone in to charge seems to force the issue to happen.
Edit: Seems that even with ambient display off totally the issue pops up. Strange thing is if i unlock the phone and take a screen shot, its totally black.
I to have this happen and like sportytony I use camera to wake device. Sometimes that too takes a bit. Most of the time when it finally does wake there will be a notification that systemui isn't responding. So I wonder if it's related.
Ok, I've been having this issue happen multiple times a day. I use this immersive app: https://play.google.com/store/apps/details?id=in.tsdo.elw
Since I have turned all ambient display options off and made sure that System UI is unchecked in the immersive app i haven't had an issue at all.
Its definitely related to system UI, com.android.systemui to be precise
i used to try to set up Power Nap on this device, but it can't find System UI in app list, make me unable to whitelist it, thus causing same issue like yours,
Screen wont turn on after sleep, since System UI wake up is blocked
I was using hide navbars and had this issue
I uninstalled and never had that problem again
Sent from my Google Pixel 2 XL using XDA Labs
Didn't expect all these replies but I'm going to try to untick system UI and see what happens. Thank you all!
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Frans1897 said:
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Click to expand...
Click to collapse
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
xprzs said:
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
Click to expand...
Click to collapse
Hey! Thanks for the answer, I can confirm we have the exact same issue. I also have the same brightness issue you described
Anyway, I have always used fingerprint unlock though so I don't know what to answer you.. I only recently noticed the weird behavior. I did a couple things to test and I found out that enabling the "fingerprint" icon showing in the always on display seems to "fix" the issue of the flicker but not the one of the brightness change (after enabling it i've yet to see the problem occur), you should try it and let me know if you see any improvement. It's probably on samsung's end though and hopefully we get it fixed with android 10 or earlier
I'll take this chance to ask you another question; two weeks ago I received a software update and ever since that day I noticed my battery to be lasting waaaay less than it used to, did you update your phone as well? Did you notice a battery drain?
I have the issue both of you talking about.
hello, I had this same issue and what I did was turn the phone off, and booting it up while pressing "Volume Up", after entering a black screen with many options, I selected wipe cache. It has worked without a flaw since then. There's lots of bugs with this phone. I recently had a problem where the USB port will detect a device and "plugged and unplugged" it, making my phone unable to dim. Thankfully I was helpful.