Hi,
I received my RN8 Pro just yesterday (22nd Oct) (India).
The first thing I noticed is the screen quality.
I find the screen is calibrated a tad bit warmer than usual. Even if you go to the screen settings and tweak it to 'cool', it still remains yellowish.
I came from OnePlus5, which had an AMOLED screen (not fHD/SuperAmoled). There the screen was obviously more crisp, I don't really expect that here. However, the calibration looks bit different if I hold these 2 phones side by side.
What I want to know is, is this just my RN8 Pro, or others also feel the same?
Also, in MIUI where is the 'night light' setting, where I can either manually or automatically turn the screen hue warmer? It's one of the main features in OxygenOS. Actually, the current RN8P calibration looks like 'night light' is already set.
Issue summary:
1) Daytime screen temp looks like as if the 'night mode'/'night light' is already ON. (Note, I don't mean 'reading mode', that's different)
2) Night time screen temp gets very yellowish, almost as if the 'reading mode' is on
3) Screen calibration (warm/default/cool) doesn't change it a lot
4) Can not find the setting to turn off the 'night mode' in #1
Thanks.
In RN8P you can find Night Light in "Reading Mode" in Display option, it turns the screen hue warmer. I'm not sure about the warm color. May "Reading mode" is enabled which is causing this. Try to check that option.
frosthawk said:
In RN8P you can find Night Light in "Reading Mode" in Display option, it turns the screen hue warmer. I'm not sure about the warm color. May "Reading mode" is enabled which is causing this. Try to check that option.
Click to expand...
Click to collapse
No, it's turned off still the screen feelings yellowish.
Exactly. It's so yellowish all the time!
Shubhayudatta said:
Exactly. It's so yellowish all the time!
Click to expand...
Click to collapse
I feel it's not all the time, it's mostly at night. Will compare again now. I got it yesterday afternoon.
Yes. And there is no quick way to disable the night time extra yellow tint.
You think it would be eligible for a replacement?
If you could compare it to another rn8 pro and see an obvious difference then yes you should claim for warranty.
frosthawk said:
If you could compare it to another rn8 pro and see an obvious difference then yes you should claim for warranty.
Click to expand...
Click to collapse
I don't know anyone around who has another RNP8.
I am waiting for others to comment here, for their own devices.
If I find mine is an exceptional issue, I'll try to get it replaced, though I feel that may not exactly come under their replacement policy.
Shubhayudatta said:
I don't know anyone around who has another RNP8.
I am waiting for others to comment here, for their own devices.
If I find mine is an exceptional issue, I'll try to get it replaced, though I feel that may not exactly come under their replacement policy.
Click to expand...
Click to collapse
It's fine in day time, I'm using this phone.
At night the screen turns yellowish automatically, it's miui issue, sceen is fine. Don't bother about replacement, just report the bug from the phone and wait for software update for fix.
@SidDev said:
It's fine in day time, I'm using this phone.
At night the screen turns yellowish automatically, it's miui issue, sceen is fine. Don't bother about replacement, just report the bug from the phone and wait for software update for fix.
Click to expand...
Click to collapse
Goto Settings >> Display >> Reading Mode and turn of Good Night's read option
Its clear that based on the Sunrise and Sunset reading mode is enabling
Its default set as off. And that's the bug, that it's functional even if it's set off.
Shubhayudatta said:
Its default set as off. And that's the bug, that it's functional even if it's set off.
Click to expand...
Click to collapse
Try enabling and disabling it. turn off schedule option if it is enabled.
Check whether night light settings are there in developer option or not
Tried all the enable disable combinations, set as disabled right now, can say it works or not only after the sunset.
And, can't find any related option in the developers setting.
SunilSuni said:
Goto Settings >> Display >> Reading Mode and turn of Good Night's read option
Its clear that based on the Sunrise and Sunset reading mode is enabling
Click to expand...
Click to collapse
Brother with due respect, not everyone is noob.
Those who have phone know what's happening. Everything is turned off in that setting still it gets activated after sunset.
It's a bug and we have to wait for the fix.
---------- Post added at 05:00 PM ---------- Previous post was at 04:58 PM ----------
SunilSuni said:
Try enabling and disabling it. turn off schedule option if it is enabled.
Check whether night light settings are there in developer option or not
Click to expand...
Click to collapse
It's not available, I have wasted some time trying to find what's happening. Trust me, it's a bug.
Shubhayudatta said:
Tried all the enable disable combinations, set as disabled right now, can say it works or not only after the sunset.
And, can't find any related option in the developers setting.
Click to expand...
Click to collapse
Update: All the toggling experiments didn't work. Its again yellowish.
Shubhayudatta said:
Update: All the toggling experiments didn't work. Its again yellowish.
Click to expand...
Click to collapse
As soon as the clock hits 10 pm IST, it became yellowish.
Confirmed bug.
I urge everyone to report this, I have already done that.
@SidDev said:
As soon as the clock hits 10 pm IST, it became yellowish.
Confirmed bug.
I urge everyone to report this, I have already done that.
Click to expand...
Click to collapse
For me it's 6pm. I know 'coz I was waiting for it today.
Shubhayudatta said:
For me it's 6pm. I know 'coz I was waiting for it today.
Click to expand...
Click to collapse
It's 10 pm for me, I hope someone else having phone confirm this too.
Looks like mine got fixed on its own. No more automated yellow tint.
Possibility#1: Xiaomi pushed some OTA
Possibility#2: I forcedly changed the 'good night read' schedule to some random time. 'ON' from 11pm to 1am, and kept the scheduler 'ON'. So, it didn't turn yellow at 6pm (the approx sunset time). Once it's past 6, I turned off everything there. It didn't turn yellow. Rebooted. Didn't turn yellow. Will observe again tomorrow.
Related
Hey ho fellas ,
I was working on adding power management + initialisation/de-initialisation sequence for rhodium´s lcd panel. Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
I would like that all of you users that are willing to help to test the kernel ( zImage+modules + latest commits included ) and give some feedback.
Test the power on/off sequence, leave it sleeping for ~30mins and unlock it,...then give me here some feedback on your lcd panel behaviour.
zImage + modules ( mediafire or attachment ):
http://www.mediafire.com/?ny18wpc3z8utxrf
Prerequisites:
- Backup your data.img if you have some valuable data on it ( anyway it should not affect it )
- Delete pm_sleep cmd from your startup.txt
What do you mean by this?
Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
Click to expand...
Click to collapse
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Lennyz1988 said:
What do you mean by this?
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Click to expand...
Click to collapse
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
lilchicano said:
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
Click to expand...
Click to collapse
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
uub11 said:
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Click to expand...
Click to collapse
Yeah, its a little bit hard to explain, but its like you said.
arrrghhh said:
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
Click to expand...
Click to collapse
Yeah, test it out and post your feedback
ReWind402 said:
Yeah, its a little bit hard to explain, but its like you said.
Yeah, test it out and post your feedback
Click to expand...
Click to collapse
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
I uploaded it here on xda, check the 1st post.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
Ha, responded a little late. I removed it...
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Lennyz1988 said:
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Click to expand...
Click to collapse
It would better that pm_sleep has the default value.
Will give this a try as I go about my day today. I don't OC and use pm_sleep=1 yet still get terrible battery life (b/c I'm a power-user, on e-mail constantly). Any positive change will be wonderful We'll see how it goes.
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Lennyz1988 said:
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Click to expand...
Click to collapse
1. Try deleting pm_sleep from your startup.txt ( then the default value will be used - i recommend that ) or put 1
2. never seen that on android
Anyway i am really sry for the inconvenience regarding launcer pro, kernel change should not affect those kind of settings :s
solevi said:
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Click to expand...
Click to collapse
Yeah its a common problem for now we are investigating this.
So i have a confirmation that the screen is really powered off?
Anyway guys try putting 1 into pm_sleep or deleting it from startup.txt (i recommend the 2nd choice ).
I ran into an interesting problem however I did not see the previous post...
Several time it went into standby (I assume) and the screen was pitch black meaning the backlight was not on. To get it out of standby, I woul click the end button like normal. after a couple of hours I pulled the phone out of my holdster, and it was abnormally hot. I do not have an overclock and my pm sleep is set to 1. I did not press the screen to see if it would respond so maybe that is what was being mentioned in the last post. None of the buttons would bring it back to life and the LED was amber and solid, where typically it would flash with this new zimage and modules. I will try to get it back to that state and see if I can click the screen even though it is dark. One thing that worries me is the battery though. Could this be damaging to it? Even when I did have it overclocked it never reached that temperature.
Anything else I can do to help troubleshoot?
EDIT: Sorry, forgot to mention I am on a Sprint RHOD400
I'm on the RHOD400 model, no OC, pm_sleep=1
Couldn't really get it to be stable, had to switch back to WinMo for the day (and trust me, that's desperation ). Once restarted in my pocket without any interaction on my part. I would press the end key to turn on screen, and had it auto reboot at that point as well. Also got a "sleep of death" twice and had to restart. While in your kernel I didn't have notification LEDs as well (not even for power events), vs the guy above that had blinking red.
I'm sure you'll get it eventually, keep up the hard work!
Hi!
Any news? Are we gonna wait for new kernel with committed code or it development is stalled?
I see a few posts here (and other places) mentioning an Ambient Mode.
I cannot find anything in the User Guide about it and I do not see any settings for it.
I am on: Android 6.0.1 - android Wear 1.4.0.2621048
(On a Zenwatch MSQWI500Q Build # MEC23S)
There is an Always on Screen, but it does not do anything.
I just noticed in the Asus Zenwatch Manager - the Face Settings - Dim Screen after - Never; does work.
w8wca said:
There is an Always on Screen, but it does not do anything.
Click to expand...
Click to collapse
It has always worked okay on mine. It does turn off after a while if you set it down or put it in to charge, but it stays on while wearing it.
w8wca said:
I am on: ...Android Wear 1.4.0.2621048 ... Build # MEC23S)
Click to expand...
Click to collapse
Both of those are old. Are you able to update to the latest versions?
HTML:
CSX321 said:
It has always worked okay on mine. It does turn off after a while if you set it down or put it in to charge, but it stays on while wearing it.
Both of those are old. Are you able to update to the latest versions?
Click to expand...
Click to collapse
When I try to update on my Zenwatch (Settings - about - system updates - it says it is up to date
My Note 4 has AndroidWear 1.5.0.2951640.gms on it
I will try searching to see any way to force this
Maybe unpair - then reset my zenwatch?
It is only a week old (for me - I bought it "refurb")
Hmm. Resetting is worth a try, since there's not really a downside. I also found this, which might help: http://forum.xda-developers.com/zen...-zenwatch-manager-facer-t3334255#post65815338
CSX321 said:
Hmm. Resetting is worth a try, since there's not really a downside. I also found this, which might help: http://forum.xda-developers.com/zen...-zenwatch-manager-facer-t3334255#post65815338
Click to expand...
Click to collapse
Thanks - I will give that idea a try
I have no setting anywhere for a reset <-- Ahh I just found it!
It is called Unpair with phone in settings
It says "unpair & factory reset" when I tap on Unpair
I did manage to get it to update after a good bit of tinkering (unpairing - old versions of Android Wear <-- That did not work for me)
Anyway I now have:
Android Wear 1.5.0.2884951
Build Number MWD48B
I still have no Setting about ambient mode - but at least I am updated Thank You!
It seems to be just a bit smoother now too.
I have searched all over and cannot find ANYTHING that tells how to get ambient mode "on".
I tried a few of the Watch Faces in Asus's Zenwatch app also to see if any had some settings
I wonder if it is something that Google Dropped in 6.0.1 ?
w8wca said:
I have searched all over and cannot find ANYTHING that tells how to get ambient mode "on".
I tried a few of the Watch Faces in Asus's Zenwatch app also to see if any had some settings
I wonder if it is something that Google Dropped in 6.0.1 ?
Click to expand...
Click to collapse
I think maybe the term "ambient mode" is specific to the Moto 360, but I think it's sometimes also used by people to refer to the dim mode of the "Screen always on" option. Will your screen still not stay on all the time with that option on?
CSX321 said:
I think maybe the term "ambient mode" is specific to the Moto 360, but I think it's sometimes also used by people to refer to the dim mode of the "Screen always on" option. Will your screen still not stay on all the time with that option on?
Click to expand...
Click to collapse
If I just set Screen Always on - on my Zenwatch - it goes off in a few seconds (actually to the time set in the Zenwatch Manager App on my Phone)
If I set "Dim screen after" on my phone in Zenwatch Manager App to never, it seems like it will just stay on all the time (My guess is battery would not last long that way)!
I am at almost 20 minutes now and still in full color.
I just layed the Zenwatch on dy desk so I did not wake it up by moving around.
I set it to 30 secound and in apx 30 seconds it goes black/off
With screen always on, the normal behavior is that it's full-color for 8 seconds (I think), then it goes to dim mode, which is just pure black and white on most faces. Using WatchMaker, I have mine set to 10 seconds. The battery on my ZenWatch still lasts about 2 days with screen always on, though I still charge it every night anyway. Try uninstalling ZenWatch Manager. It's not really necessary. I don't have it installed.
Well I uninstalled Zenwatch Manager - installed Watchmaker - picked the first face Steel Blue - Just Digits
Set "Keep Watch Awake" to 10 seconds
And it still goes off in the 10 seconds.
I even rebooted my Phone and my Zenwatch same
What about some setting in Android Wear?
Only one I see is Always On Screen slide switch it is set to on - but setting it to off does not change the way it works
w8wca said:
What about some setting in Android Wear?
Click to expand...
Click to collapse
Yeah, the only thing I have is "Always-on screen," too. I have it, and "Tilt to wake screen" both set to on. I'm at a loss at this point. It seems likely it's a software problem of some kind, but I don't know where to look next.
Well thank you for trying to Help!
I appreciate it!
I just noticed something interesting:
If I set Always On Screen on my Zenwatch: When it goes to sleep (so to say): It first goes dim then it goes black and white. - But then it goes off.
If I have Always On Screen off: It just Goes DIm then off
So my take on mine is it is a glitch of a defect.
I will probably live with it as I bought it as Refurbished
w8wca said:
Well thank you for trying to Help!
I appreciate it!
I just noticed something interesting:
If I set Always On Screen on my Zenwatch: When it goes to sleep (so to say): It first goes dim then it goes black and white. - But then it goes off.
If I have Always On Screen off: It just Goes DIm then off
So my take on mine is it is a glitch of a defect.
I will probably live with it as I bought it as Refurbished
Click to expand...
Click to collapse
Hi!
I have exactly the same problem ! But it came after updating my zenwatch to 6.0.1 (M1D63K) .
Have you found a solution?
I'm on the same boat. Always On Display is activated, tried doing it on the watch, on the Wear App and the ZenWatch manager. No luck. I've received OTA updates regularly, but none have worked.
I'm posting in the hopes of finding a solution. I've had this watch way beyond the warranty period, so there's no way I'll be able to return it to Asus.
Was a solution ever found? i am now experiencing this problem after owning the watch for 2 years. It has never happen before.
Hey everybody,
is ambient display working for anybody when not set as 'always' on and only to pop up when picking up the device?
The display lightens up when I get a notification. It very rarely lightens up when picking up the device (with pending notifications) and it nearly never lighten shows the clock when picking the device up with no notifications (this should be the case, too right?)
I recall this behaviour being more consistent in the beginning when i got this phone some days ago. Now its like ambient display isn't really working
Anyone can relate?
xflowy said:
Hey everybody,
is ambient display working for anybody when not set as 'always' on and only to pop up when picking up the device?
The display lightens up when I get a notification. It very rarely lightens up when picking up the device (with pending notifications) and it nearly never lighten shows the clock when picking the device up with no notifications (this should be the case, too right?)
I recall this behaviour being more consistent in the beginning when i got this phone some days ago. Now its like ambient display isn't really working
Anyone can relate?
Click to expand...
Click to collapse
nobody? :l
xflowy said:
Hey everybody,
is ambient display working for anybody when not set as 'always' on and only to pop up when picking up the device?
The display lightens up when I get a notification. It very rarely lightens up when picking up the device (with pending notifications) and it nearly never lighten shows the clock when picking the device up with no notifications (this should be the case, too right?)
I recall this behaviour being more consistent in the beginning when i got this phone some days ago. Now its like ambient display isn't really working
Anyone can relate?
Click to expand...
Click to collapse
CANNNOT relate.
My IS working when I pick it up & ambient is set to off.
Might have to factory restore it & see if it will work under these conditions.
Try it first under safe mode.
perveeus said:
CANNNOT relate.
My IS working when I pick it up & ambient is set to off.
Might have to factory restore it & see if it will work under these conditions.
Try it first under safe mode.
Click to expand...
Click to collapse
what does is stand for?
and whats safe mode?
xflowy said:
what does is stand for?
Click to expand...
Click to collapse
present tense third-person singular of "be"
xflowy said:
and whats safe mode?
Click to expand...
Click to collapse
https://support.google.com/android/answer/2852139?hl=en
perveeus said:
present tense third-person singular of "be"
https://support.google.com/android/answer/2852139?hl=en
Click to expand...
Click to collapse
well thanks. but: since you did not that excellent in grammer either with your sentence, i wouldnt come of as entitled as you just did...to/and from a non-native speaker, btw.
xflowy said:
well thanks. but: since you did not that excellent in grammer either with your sentence, i wouldnt come of as entitled as you just did...to/and from a non-native speaker, btw.
Click to expand...
Click to collapse
Not sure why you are taking what I wrote the wrong way.
Yes my typing was off but not my grammar (spelled 'Cannot' incorrectly & used MY when I meant mine)
& this from a non-native speaker also.
Oh well, I don't have the problem you have.
It automatically turned to warm colour (image is in attachment).... And night shield is off .... And tried to change but apparently can't.....
Can someone help me
And when i click on phone app it shows normal colour when asked for fingerprint..... And then it goes back to warm colour automatically..
I got a solution
sameer 100 said:
It automatically turned to warm colour (image is in attachment).... And night shield is off .... And tried to change but apparently can't.....
Can someone help me
And when i click on phone app it shows normal colour when asked for fingerprint..... And then it goes back to warm colour automatically..
Click to expand...
Click to collapse
I had a same issue in my realme 6 pro after Romany research and contact to realme customer care finally I fix it my myself.
Steps
1) Backup your contact and media
2) wipe your device reset
3) after resetting when you login with your previous email do not restore system settings say no restore system settings and that's it's.
Basically it's bug it's solve by not restoring system settings sync with your Google acc.
---------- Post added at 04:44 PM ---------- Previous post was at 04:36 PM ----------
Refer this it will help I had a same issue https://forum.xda-developers.com/realme-x2-pro/help/disable-night-filter-t4005543/post83396469#post83396469
sameer 100 said:
It automatically turned to warm colour (image is in attachment).... And night shield is off .... And tried to change but apparently can't.....
Can someone help me
And when i click on phone app it shows normal colour when asked for fingerprint..... And then it goes back to warm colour automatically..
Click to expand...
Click to collapse
Same thing happens when your screen brightness is low and you unlock via fingerprint, the brightness increases for a sec, this is how the optical sensor of the fingerprint reader works. I guess it needs a bright and cool light incoming from the screen to properly capture one's fingerprint to unlock the device. Can't do anything here, works this way only.
prashant2198 said:
Same thing happens when your screen brightness is low and you unlock via fingerprint, the brightness increases for a sec, this is how the optical sensor of the fingerprint reader works. I guess it needs a bright and warm light incoming from the screen to properly capture one's fingerprint to unlock the device. Can't do anything here, works this way only.
Click to expand...
Click to collapse
Let me rephrase
My phones night mode automatically turns on at 7pm and get off in the morning
I.e. display turns into warm colour in evening and switches off automatically in morning
Even though night shield option is off
sameer 100 said:
Let me rephrase
My phones night mode automatically turns on at 7pm and get off in the morning
I.e. display turns into warm colour in evening and switches off automatically in morning
Even though night shield option is off
Click to expand...
Click to collapse
If night shield is turned off and still it gets on means that it is set to automation. Turn off the scheduled time option in night shield.
prashant2198 said:
If night shield is turned off and still it gets on means that it is set to automation. Turn off the scheduled time option in night shield.
Click to expand...
Click to collapse
Please see the above screenshot night light schedule is also off
just get an app for it on play store.
sameer 100 said:
Please see the above screenshot night light schedule is also off
Click to expand...
Click to collapse
Hi,did u get the solution?I am also facing the same issue
noush76 said:
Hi,did u get the solution?I am also facing the same issue
Click to expand...
Click to collapse
I went to service center, they took the log for this issue as' he was from software team' he quoted.
And they fixed that issue but when i later on updated the software it happened again..
I don't have enough time to go back to service center.....
So for now jist change the time to morning pr afternoon ot will disappear for that time...
And of you go to service center please ask them to update your phone...
Sorry for later reply as phone formatted ....
Guys please full reset your device and check by changing your time in mobile and check whether it happens again ? And do many times until it fixes guys i also faced the same problem and I followed same it fixed
kadapa said:
Guys please full reset your device and check by changing your time in mobile and check whether it happens again ? And do many times until it fixes guys i also faced the same problem and I followed same it fixed
Click to expand...
Click to collapse
Ok
When the night mode is on fully reset your phone if it didn’t work then again format your phone and try to set as a new phone without any backup from google
Note:it works when the night mode is on i did it after the sunset when my night mode was on
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
cjvphd said:
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
Click to expand...
Click to collapse
I am also having this issue after the screen has been off for a while. Anyone have a solution?
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
italia0101 said:
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
This has been my experience today.
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Do You have Greenify installed?
Globus.gd said:
Do You have Greenify installed?
Click to expand...
Click to collapse
No.
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Globus.gd said:
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Click to expand...
Click to collapse
What is greenify? And should I have it?
http://greenify.wikidot.com/
italia0101 said:
I also have this issue, [...]
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
cjvphd said:
This has been my experience today.
Click to expand...
Click to collapse
Hey guys,
same for me since today. Until some hours ago all was working fine.
But why you think it's related to dimmer/light. Because for me there is no difference when I turn on the light in room or change the timezone in settings. For now it's just not working (like broken)
I rebooted (also turned off and on) several times, turned off and on the inactivity display settings and some other tests, but nothing helped.
CHEERS
bjs339 said:
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Click to expand...
Click to collapse
Like for some others in the thread the factorymode won't be opened via *#808#
But I see the process installed and running when searching for it in settings. Maybe there is something crashed in bg?!
CHEERS
---------- Post added at 12:40 AM ---------- Previous post was at 12:05 AM ----------
UPDATE
Suddenly it began working again...
No changes in location, lighting or whatever (except 39 minutes).
But not I can confirm this laggy working of this function. No idea why...
Last days it worked like 10/10 but now maybe 4/10.
CHEERS
Launching the camera in landscape mode seems to trigger it for me occasionally.
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
A through clean up resolves the problem for my phone
i am facing the same issue with my phone. sadly i have noticed it is a reoccurring problem and it has something to do with the sensors. i tried all the fixes like toggling tap to wake, toggling face unlock assists light, clearing the cache and app data but nothing helped my case. factory reset is of no help either so i'd say don't even bother with that.
what really helped me fix this issue multiple times was something rather unexpected. what you should do is take off your phone's cover, get a wet towel, and thoroughly clean the phone all around, being especially thorough around the front facing camera and the top two edges. I give it extra attention around the front side being careful of the top speaker and after a couple of cleans and wipes both tap to wake and lift to wake starts working perfectly fine. then i put on the cover and voila it all good. Give it a try and let me know if it helped resolve this issue for you.
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Flamehell said:
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Click to expand...
Click to collapse
Hey!
The (single) tap to wake funktion will show up the ambient display, so that u can see clock, messages and use the fingerprintsensor if u want to enter.
It's a quick awake of screen to see Infos with minimal usage of display resources.
DT2W (double tab to wake) is the same as pressing the power button. So this will fully turn on screen into the lockscreen and also activate the face recognition. (for sure fingerprintsensor can be used, too)
BUT you can only activate one of those things and it will automatically turn off for example tab to wake if you activate DT2W.
Personally I like to use the single tab awake for ambient display, as I always can full activate by power button, which would be a dublicate function then.
CHEERS
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
First ppl with new update (only some hours, max a day of usage) reported in OP Forum that they didn't have any problem for now.
So seems to fix this screen awake problem.
CHEERS