Related
Huawei watch
AW 1.5
Sometimes ambient mode doesn't kick in, no matter how still I keep the watch or how long I wait. Only a reboot will fix it. On reboot, ambient mode works correctly. The problem will happen randomly, about once a day. It can happen with stock or Watchmaker watch faces.
Settings:
brightness - 1
wrist gestures - off
always on - on
screen lock - off
Phone AW settings:
always on - on
tilt to wake - off
Note, this is not the 'ambient always on' problem. Also, it's not a watchface problem. Yes, all the watchfaces have an ambient mode. When the problem occurs, switching to another watchface doesn't fix it.
Anyone else have this problem?
mageus said:
Huawei watch
AW 1.5
Sometimes ambient mode doesn't kick in, no matter how still I keep the watch or how long I wait. Only a reboot will fix it. On reboot, ambient mode works correctly. The problem will happen randomly, about once a day. It can happen with stock or Watchmaker watch faces.
Settings:
brightness - 1
wrist gestures - off
always on - on
screen lock - off
Phone AW settings:
always on - on
tilt to wake - off
Note, this is not the 'ambient always on' problem. Also, it's not a watchface problem. Yes, all the watchfaces have an ambient mode. When the problem occurs, switching to another watchface doesn't fix it.
Anyone else have this problem?
Click to expand...
Click to collapse
Someone just posted a bug where his ambient mode doesn't kick in after an alarm goes off until he reboots. Could this be your case too?
I have this too. Been happening about a week. Either an alarm or a timer going off will cause it.
Yes, that's it!
This morning I figured out that it always happens first thing in the morning. I thought it was from being on the charger all night long.
I can confirm this 100% reproducible bug.
Nicholb, did you notice this after the 1.5 update?
Although this is a major bug, there are some relatively easy fixes:
- If you only use the alarm to wake up in the morning, restart your watch after you wake up.
- Try another alarm app (the ones I saw were all pay apps or didn't work).
- For timers, use another app. I recommend MoveUp! MultiTimer.
mageus said:
Nicholb, did you notice this after the 1.5 update?
Click to expand...
Click to collapse
No, it was working fine after the 1.5 update. Something else must have updated within the last week. I did notice that last night there was an app update to "clock". I'll know tonight if that helped. I've just been rebooting the watch after an alarm goes off as a workaround.
That was it. The update to the clock app has fixed the problem for me.
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!
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Had this happen as well. Not rooted. Can't remember but i vaguely recall this with other versions of android
mcgleevn said:
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Click to expand...
Click to collapse
got a crappy screen protector? that'd be my guess
Nope nothing, naked
mcgleevn said:
Nope nothing, naked
Click to expand...
Click to collapse
Same. And it doesn't happen every time.
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Possibly unrelated, but about every 1 in 5 reboots my screen won't turn on. Stays black, no back light. The phone still responds to ADB and fastboot commands, but nothing will turn the screen on until I hold down power to restart.
Same here.its happened multiple times. naked Pixel here, not rooted. its annoying.
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
honestly after some more calls with this issue, i think my dirty ear and is causing the close proximity reading... after the most recent episode, i went to the droid info app and it was reading the sensor at 0 cm and after wiping the notch off, it started to read correctly (5.0 cm) >>> i dont really want to give the haters another reason to dog the notch but, in my case, i think its going to be an issue. i may switch the "power button to end call" on and see if that will alleviate my issue for now -
mcgleevn said:
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Click to expand...
Click to collapse
Same exact thing happened with me yesterday, could it be a RAM management issue?
Roll3r said:
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
Click to expand...
Click to collapse
Thanks for the heads up. I have unrooted and naked 3 XL. This screen off thing was affecting all calls. If the remote party hung up, I was fine. If I got into someones VM, I had to sit quietly until the call dropped.
I added myself to the Phone app Beta program and updated. After several test calls, I think it's fixed.
Ever since I bought the phone I had this issue which has not been solved with recent rom updates nor application updates. Basically while playing a voice message, either in WhatsApp or Telegram, the screen goes black (without putting the phone close to the head) and the audio switch from the speaker to the ear capsule. Even more, when this happens, the screen is stuck and I can't turn it on neither by double tapping the screen or pressing the power button. The only way to turn it back on is to put the phone "parallel to the ground", I know it's strange but that is. Other times, when this happens the audio is also distorted.
Are you experiencing the same problem?
Cheers.
Just checked. No problems. Do you have anything that covers the distance sensor?
Nothing installed on the phone (tempered glass etc.) it happens with just the MI cover installed. Also, it happens when I have the phone in my hand, if it's flat on a surface there's no problem.
Just made a research on the official forum and I found out that a lot of other users are experiencing this issue.
I'm facing the problem with distorted audio when recording whatsapp messages. But happens only sometimes, don't know how to reproduce. Proximity sensor bugs also sometimes... in my case the screen doesn't goes black, which leads to accidental touches..
PurPLe SKy said:
Ever since I bought the phone I had this issue which has not been solved with recent rom updates nor application updates. Basically while playing a voice message, either in WhatsApp or Telegram, the screen goes black (without putting the phone close to the head) and the audio switch from the speaker to the ear capsule. Even more, when this happens, the screen is stuck and I can't turn it on neither by double tapping the screen or pressing the power button. The only way to turn it back on is to put the phone "parallel to the ground", I know it's strange but that is. Other times, when this happens the audio is also distorted.
Are you experiencing the same problem?
Cheers.
Click to expand...
Click to collapse
The same thing happened with me.
Any solution?
I think this happens only when i get a message... i guess the sound notification from the incoming message disturb the ongoing voice WhatsApp message
Tgcastro said:
The same thing happened with me.
Any solution?
Click to expand...
Click to collapse
None. This problem is quite common even on other Xiaomi devices (MI 9, Redmi Note 7 etc.) but not everyone is complaining about it.
I have the same problem -and always had- on a Xiaomi Mi MIX 2 running LineageOS, so I guess it depends on the firmware.
I've same issue
Solutions?
Thank you
No problem package blocking WhatsApp at all...
Hi,
I have a problem with my OP 9Pro.
After a phone call, the display sometimes stays black and it takes a while before you can use the device again.
Does anyone else have that and, above all, how can I solve the problem?
Many greetings and thanks
Mars
Are you on OOS12? I only experienced that bug in the short time I ran OOS12. One of the main reasons I reverted to OOS11 actually.
Yeah I get this too. From what I can tell, it seems to have something to do with the proximity sensor killing the screen when you put it up to your ear, then hanging when the call ends.
OOS11
Me too. On 11. Thinking it may be from Nova or Adguard. Until I figured out that I could hit the "screen on" button to regain control I would wait till the other person hung up. So, as a workaround that's what I do, hit the button.
That happens when the proximity sensor it's being blocked. If you have any screen protector over the camera notch (where the proximity sensor is) then that's why it's turning the screen off.
If you don't have anything covering the sensor then try making a call on another app (like WhatsApp) to see if the issue persists there too. If not then it might be the dial app, try restarting your phone.
If it happens on many messaging apps, and there's nothing covering the sensor, try downloading a sensor tester app to see if the proximity sensor is being triggered all the time. If it is then it's a hardware issue and you'll have to return your phone a get a new one.
chetqwerty said:
Me too. On 11. Thinking it may be from Nova or Adguard. Until I figured out that I could hit the "screen on" button to regain control I would wait till the other person hung up. So, as a workaround that's what I do, hit the button.
Click to expand...
Click to collapse
Power button is unresponsive when the phone goes pitch black. Even switching the alert slider to something different doesn't trigger the fingerprint sensor on.
I'll try disabling pocket mode. I also found positive feedback about this when you enable the "Override force-dark" setting in Developer Options. See if that helps.
Has been happening to me from time to time since A12. I just hold volume up, volume down and power button at same time and reboot to recovery and restart from there. That fixes it really quick for me.
Yes, I'm on A12 because I thought it would get better here. But I had the same problem with the A11.
I haven't managed to solve the problem yet.
It also happens on Android 11 but it's not quite as bad here. The display turns on after a little while.
Where is the sensor actually? It's not the camera. It's to the right of the speaker. or?
Hi, Guess!
I got a solution from the Oneplus team. (1800 202 8888) / general phone tech support team helped me with these steps:
1- under setting search reset
2- click on Reset all settings
3- Reset all settings. click it.
As this is a normal reset will not lose your data.
The last option is if this doesn't work then we have to backup all data from the phone and do a factory reset.
or it's a hardware issue.
e-regards!
Piyush Sahni