Hey guys,
First off: I used the N5 "as is" for few days. I've set up all the notifications with light flow, and as expected: screen off, event happens (E.g. a received mail), led starts flashing with the expected color. All good.
Then today I unlocked and rooted the N5 with chainfire's auto root.
Now the led won't flash as expected.
I set light flow up and when I use light flow's test option, everything works just fine, but when the screen is off, notifications don't trigger the led... Email comes no led....
I don't know what to do....
momsi said:
I don't know what to do....
Click to expand...
Click to collapse
Contact the developer of lightflow (from the play store) - very responsive guy
Same here, rooted with CF-Auto-Root and notification LED seems to fail color and it blinks in a weird way.
After rooting (I did it right away so can't really say it worked right before) but lightflow didn't run any of the colors during the test, and even before I tried setting up lightflow, I think I've only seen the led 3 times (only in white)
Sent from my Nexus 5 using XDA Premium 4 mobile app
Light Flow just pushed a new update with N5 and 4.4 compatibility. Check it out.
Well after a little messing around it seems to work now. I've uninstalled LF, reinstalled, checked every option in the settings and so on, but I think the update did the trick.
Only glitch I have left is: I've set LF to cycle all notifications, if many notifications are active at once (or when I'm in test all mode) it happens often, that color_1 lights up and dimms down, (normally color_2 should now light up and dimm down but:=> ) color_1 lights up and swaps instantly to color_2. And so on. Any solution for that?
my proximity sensor has been acting up since the 4.3 OTA update, my screen stays black after calls, sometimes after screen time outs and I normally have to wait awhile before it'll turn back on, The infra red light for the proxy sensor stays on as well, it used to just blink occasionally. and yes I can see the infra red light, first sensor to the right of the speaker, for those of you who cant see it try looking at it with a camera and it'll become visible. since this seems to control my screen even while not making a call I need to disable it or calibrate it, I have already disabled it at phone, call settings, turn off screen during calls.
johnwilliams-84 said:
my proximity sensor has been acting up since the 4.3 OTA update, my screen stays black after calls, sometimes after screen time outs and I normally have to wait awhile before it'll turn back on, The infra red light for the proxy sensor stays on as well, it used to just blink occasionally. and yes I can see the infra red light, first sensor to the right of the speaker, for those of you who cant see it try looking at it with a camera and it'll become visible. since this seems to control my screen even while not making a call I need to disable it or calibrate it, I have already disabled it at phone, call settings, turn off screen during calls.
Click to expand...
Click to collapse
The option has been removed from 4.3 OTA, there's no way to calibrate them. Also none of the third part apps are compatible with this. :crying:
I've just got this device 3 days ago~ And i noticed that my led notification light hasnt been consistent or light up at all unless i use Light Flow but even with Light Flow its still inconsistent. I'm on stock KitKat 4.4.4 never rooted etc. Pulse notification led is on.
Without lightflow it just doesn't light up at all for applications like whatsapp,wechat,games(Does the led light up for games too?). Whenever i receive a phone calls however it lights up white for a split second and then it turn itself off.. If i don't pick it up, it doesn't light up to show me that i have a missed call either, but when i turn the screen on, it lights up for a split second and then turn itself off again.
Using lightflow , i haven't get to try it with whatsapp yet but for charging and phone calls it works great but for wechat it only works if i have the screen on. If the screen is off nothing lights up and when i turn on the screen by pressing the power button and then put it to sleep again it works. I have the run in foreground on,Reduce wake on(not sure if i need that), and Nexus 5 force LED Reset.
Also since i'm already here, how long does it takes for google to fix the lollipop if at all? Should i update it to see if the led works on lollipop? Does OTA update introduce problems and bugs? Sorry if my questions are too long and my english is bad.
I got my OP7 Pro today. Double tap to wake with screen off doesn't seem to work. Anyone know what the secret is? What am I missing?
jdgesmlls said:
I got my OP7 Pro today. Double tap to wake with screen off doesn't seem to work. Anyone know what the secret is? What am I missing?
Click to expand...
Click to collapse
You have to turn it on in display settings under ambient display. It's turned off by default, or at least mine was as well as pickup to show.
None of my screen off gestures are working...
truckerdewd said:
You have to turn it on in display settings under ambient display. It's turned off by default, or at least mine was as well as pickup to show.
Click to expand...
Click to collapse
I think he means the feature is broken. It's not working for a bunch of us after the day-one update. It works when it wants to. OnePlus has done nothing to fix this and I'm just about ready to get my money back. Just because it's working fine for you doesn't mean we're doing something wrong.
Yeah, lock screen gestures and single/double tap don't work on the latest update, but I believe they're working on fixing it, going through repro steps right now according to their bug page. I'm sure it'll get fixed soon, and it's not a make or break issue to me by any means.
What version are you guys on?
I'm on oxygen 9.5.5 T-mobile gm1915 not having any issues.
I came here to find this out. It's works randomly.
I don't know what I did, but it is working now. I have rebooted twice and it has persisted so +1 on the issue being random. I more wanted to know if others were experiencing the same behavior. Thanks for the replies!
Having tested this, It works randomly during low light situations, and all the time in normal/extreme light situations, such as outside in the sun or in a bright room.
EchoX860 said:
Having tested this, It works randomly during low light situations, and all the time in normal/extreme light situations, such as outside in the sun or in a bright room.
Click to expand...
Click to collapse
Yup. This is my issue.
So my double tap to wake completely stopped working. Single tap doesn't work at all either. Not happy at all right now. Completely stopped about a half hour ago. Reboots fix nothing.
Got my phone yesterday and rooted 10 min after opening it and took update to 9.5.3. no issues at work double or single tap to wake. Used it all night setting it up and playing with it. Lit room or dark. It's been pretty consistent so far. There is an occasional time I have to tap a second time but still work on the 2nd try.
Not sure why it's random like that. Only thing I can think of is after the update... Did any of you do a factory reset? Maybe some reminant install files are causing some issues
Eric214 said:
Got my phone yesterday and rooted 10 min after opening it and took update to 9.5.3. no issues at work double or single tap to wake. Used it all night setting it up and playing with it. Lit room or dark. It's been pretty consistent so far. There is an occasional time I have to tap a second time but still work on the 2nd try.
Not sure why it's random like that. Only thing I can think of is after the update... Did any of you do a factory reset? Maybe some reminant install files are causing some issues
Click to expand...
Click to collapse
I must be blind but how do you unlock the bootloader and root this phone? Thx
equlizer said:
I must be blind but how do you unlock the bootloader and root this phone? Thx
Click to expand...
Click to collapse
In developer options you have to turn on oem unlocking and USB defining. Have ADB and fastboot SDK installed on PC. Then while in the bootloader type... Fastboot oem unlock.
To root you need Magisk. Follow this thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
The people here saying that it has to do with light are right. I have tested this myself. Even in fairly lit rooms, if the light isn't shining directly on the ambient light sensor, Ambient Display, double-tap-to-wake, and lift-to-wake are all completely disabled. If you shine a flashlight on the light sensor, they suddenly become available. This means that if you aren't using the phone in broad daylight or VERY well lit rooms, you have to hit the power button. Aside from the inconsistency of functionality that creates, I haven't used a power button to wake my phone in 3 years. I certainly hope they plan to fix this soon, as I'm of a mind to return the phone right now. This makes it very annoying to use on a daily basis for me. I keep my house fairly dark at night when I'm watching TV.
For some reason, OnePlus has it using the ambient light sensor rather than the proximity sensor and/or gyroscope for these features. This is not how it should work.
greyhulk said:
The people here saying that it has to do with light are right. I have tested this myself. Even in fairly lit rooms, if the light isn't shining directly on the ambient light sensor, Ambient Display, double-tap-to-wake, and lift-to-wake are all completely disabled. If you shine a flashlight on the light sensor, they suddenly become available. This means that if you aren't using the phone in broad daylight or VERY well lit rooms, you have to hit the power button. Aside from the inconsistency of functionality that creates, I haven't used a power button to wake my phone in 3 years. I certainly hope they plan to fix this soon, as I'm of a mind to return the phone right now. This makes it very annoying to use on a daily basis for me. I keep my house fairly dark at night when I'm watching TV.
For some reason, OnePlus has it using the ambient light sensor rather than the proximity sensor and/or gyroscope for these features. This is not how it should work.
Click to expand...
Click to collapse
But it seems it's different from device to device ? Double tap to wake, the lift feature and the only one tap to activate ambient light works in all light conditions for me.
Just a thought....is there an option to avoid accidental touches when in a pocket? This might explain why it works in well lit rooms and not in dark rooms.
greyhulk said:
The people here saying that it has to do with light are right. I have tested this myself. Even in fairly lit rooms, if the light isn't shining directly on the ambient light sensor, Ambient Display, double-tap-to-wake, and lift-to-wake are all completely disabled. If you shine a flashlight on the light sensor, they suddenly become available. This means that if you aren't using the phone in broad daylight or VERY well lit rooms, you have to hit the power button. Aside from the inconsistency of functionality that creates, I haven't used a power button to wake my phone in 3 years. I certainly hope they plan to fix this soon, as I'm of a mind to return the phone right now. This makes it very annoying to use on a daily basis for me. I keep my house fairly dark at night when I'm watching TV.
For some reason, OnePlus has it using the ambient light sensor rather than the proximity sensor and/or gyroscope for these features. This is not how it should work.
Click to expand...
Click to collapse
Yes! That reproduces the issue exactly for me. I am sure this is not the only one, but this thread on OnePlus support forums reports the issue.
https://forums.oneplus.com/threads/oneplus-7-pro-ambient-display-not-working.1034009/
You can see users reporting the problems inconsistency, and OnePlus seems to acknowledge the problem and they are "looking into it". Please go add your feedback as I am sure the more people that complain, the higher priority the bug will become.
.vermilion said:
But it seems it's different from device to device ? Double tap to wake, the lift feature and the only one tap to activate ambient light works in all light conditions for me.
Click to expand...
Click to collapse
This is where the inconsistency of the issue occurs... I am in my office which is lit the same way each day since I got the device (low light). The off screen gestures magically started working about 6 hours after I got the phone and were working up until this morning. Put the device close to a light source while the screen is dark, and you will see it wake up with no interaction with the screen. Screen off gestures work while in that lighting. I forced closed, cleared storage/cache of the Ambient display service and my phone now works in all lighting. It is almost as if the sensor becomes stuck in 'pocket mode' or something like that.
I noticed some funny:
Which cases are you using?
I was with the one in the box until now and everything worked fine (ambient display, double tap to wake, one tap to show fingerprint, wake when lifting up the phone,...). I'm with the Nylon case since a few minutes and since then the ambient display won't work anymore.
Maybe there's something related?
jdgesmlls said:
This is where the inconsistency of the issue occurs... I am in my office which is lit the same way each day since I got the device (low light). The off screen gestures magically started working about 6 hours after I got the phone and were working up until this morning. Put the device close to a light source while the screen is dark, and you will see it wake up with no interaction with the screen. Screen off gestures work while in that lighting. I forced closed, cleared storage/cache of the Ambient display service and my phone now works in all lighting. It is almost as if the sensor becomes stuck in 'pocket mode' or something like that.
Click to expand...
Click to collapse
Yes, you're totally right! I tested it! When light is shining on the display, my tap gestures will work again. I forced closed and cleared storage of ambient display but unfortunately it doesn't change my current situation, at the moment it won't work... ?
I can confirm this as well. In dark or even dim rooms, I must use the power button to turn the screen on, in well lit environments, I can use tap to wake. Hopefully this can be fixed in an upcoming update.
Sent from my GM1915 using Tapatalk
So, since I updates to android 13 one ui 5.0 my always on display is not working as it should. I use the "tap to show" option, and it works fine the first time i touch my screen when it's off. But that's it. If i don't wake up the screen and touch it again after the screen goes black to see the AOD, it won't show.
I find it very useful to use at night, while sleeping, to see the time and not get blinded by the bright display.
I cleared the phone's cache after the update. Still not working as intended...
Do you use energy saving during day? I set a routine to activate it under 20%, so it deactivate aod, but when I charge it and goes over 20%, I have to enable aod again.
I'm having some issues too. I was using "tap to show", but recently it always come back to "always show" at the moment I lock my phone