Related
I really want to "Shake to wake" my TrueSmart to just check the time. I have been doing this action with my pebble since I got it and its the last thing I need to address for this to really satisfy my user experience. Thanks to @Lokifish Marz we know about WatchOn and the sensor issue that is with the TS 1/8 1900 Firmware. Does anyone have a work around for this?
cdrom1028 said:
I really want to "Shake to wake" my TrueSmart to just check the time. I have been doing this action with my pebble since I got it and its the last thing I need to address for this to really satisfy my user experience. Thanks to @Lokifish Marz we know about WatchOn and the sensor issue that is with the TS 1/8 1900 Firmware. Does anyone have a work around for this?
Click to expand...
Click to collapse
I use the app "Shake" by Adl_Dev. It works well.
Helgaiden said:
I use the app "Shake" by Adl_Dev. It works well.
Click to expand...
Click to collapse
I have that installed but not much luck. Any config advice?
Sent from my Nexus 5
cdrom1028 said:
I have that installed but not much luck. Any config advice?
Sent from my Nexus 5
Click to expand...
Click to collapse
I think I have the sensitivity at like 14 or 15 or 16. Sometimes it takes a pretty good wrist shake (rapid counter-clockwise to clockwise motion) to get it to wake up, but it works reliably. Generally if I know im gonna look at the watch, ill shake it first then raise it up to look at it.
Great thanks for the info
Sent from my Nexus 5
how is it on battery life? Just installed so thanks as well, but curious to hear since the app warns you that it will consume a lot when off
Try Awesome on/off
I tried several different versions of shake to wake apps and the most consistent was Awesome on/off app. It has a tilt angle sensitivity so when I bring my arm up to look at the watch it turns on the watch face screen so I can tell what time it is. I set my watch for display off in 15 seconds but 30 seconds seems ok. Battery life seems fine. I can run my watch with a full charge all day. I plug it into the charger in the evening. I intermittently play with it through the day and mostly use it for sms notifications from my Note 3 using SMS forward app on my Note 3 and checkbook using anMoney app.
I also use Shake with somewhat what reliable results.
I combined it with Llama to turn the screen off after 7 seconds when Watchfaces is the current app or running in the foreground with it set to cancel if the condition is no longer true.
Both if these work most of the time.
I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version (or possibly an LG-exclusive mod to squeeze even more battery life) or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from our friend with the Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think you are right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...
"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?
im currently running LOS 14.1 on two KIW-L24. both seem to have a sensitivity issue. like many if not all, i keep my phone in my pocket. while on my daily routine which involve school and work my phone often gets very hot. it seems that just keeping my phone in my pocket often awakens the phone and keeps the screen on.
i have DT2W enabled which im sure is the problem. the thing is, i had it enabled with EMUI and it never caused a problem. so, what can i do to stop this while keeping DT2W? i also notice that it takes a bit more effort to wake the phone in EMUI than it does on LOS. can the screen sensitivity be lowered for DT2W?
any and all help is appreciated.
DT2W on mine is normal, just tried it, it doesn't activate that easily even when out of pocket. I do remember having DT2W issues on previous device - I had crazy behavior of music player (DT2W wakes up display in pocket => next contact changes track or stops/pauses music, good thing I had lockscreen PIN and changed default shortcuts to custom ones, god knew who'd it call).
Greater chances are that you have issues with ambient display, esp. if you enabled pocket and pickup mode. I've noticed that mine likes waking up randomly while it's on flat surfaces or during car rides (I keep it in holder next to my gearbox), so I guess accel. sensor is giving false data or gets big value peaks which trigger wakeup.
thanks for the input ShadySquirrel! yeah, i have had a few...... i guess thigh dials?? anyway, i dont have ambient display enabled on my phone and the other phone is now back to running EMUI. for now only my phone is having the problem. im gonna post on the LOS thread since it seems to be more of a Lineage issue.... i think. thanks for the help Squirrel!
I hope that issue is fixed far ago
I'm pretty sure my S7e had the option to turn the screen completely off when in a pocket or face down, even when AOD was turned on. I can't find any way to do that on the S9. Even on auto brightness it stays on, very dimly. On manual brightness, it stays on at whatever brightness you've set. What's the point of having AOD use even a little bit of battery if you can't see the display at all?
Anyone found a way to shut AOD off in these circumstances?
Try Blocking Touches in the Display Options.
Goofytek said:
Try Blocking Touches in the Display Options.
Click to expand...
Click to collapse
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Is this just a rant? Cause it seems like you've answered your own question.
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
meyerweb said:
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Click to expand...
Click to collapse
I've been trying to solve this as well. It seems some models have different wording in the block touches option. My tmobile device says something like prevent touches while in a dark place, pocket. I've been told the wording for that option on other models is more like disable screen in dark places, pockets. I hope it gets changed in an update.
the_scotsman said:
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
Click to expand...
Click to collapse
Actually it does not. What's weird is I swear it did when I first got the phone but it seems like an update broke it or something because it no longer does it.
Really hope a future update brings it back because I haven't found any settings that enable it.
Anyone figure this out?
vintagerock said:
Actually it does not. What's weird is I swear it did when I first got the phone but it seems like an update broke it or something because it no longer does it.
Really hope a future update brings it back because I haven't found any settings that enable it.
Anyone figure this out?
Click to expand...
Click to collapse
What I've figured out is that it works 100% on my S9+.
And my wife's S9+.
And my daughter's S9+.
And my other daughter's S9+.
You may wish to review the settings on your device again.
I hope you find the missing configuration, because I can understand the frustration when something appears to not work as it should.
Having had a number of S7 phones that featured a stuck rotation-lock due to a borked accelerometer, and "glowing" screens while turned off due to bad display drivers, I would not discount the possibility that your device could be defective, if you have turned on the appropriate feature-set and the AOD still does not turn off when the proximity sensors are covered.
the_scotsman said:
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
Click to expand...
Click to collapse
Nope. If I put it face down on a table or desk in a completely dark room, I can see the light from the screen reflecting off the surface. (My case lifts the screen slightly off the table.) And if I take it out of my pocket, I can see the AOD is very dim immediately after coming out, and then brightens after a split second.
afh3 said:
What I've figured out is that it works 100% on my S9+.
And my wife's S9+.
And my daughter's S9+.
And my other daughter's S9+.
You may wish to review the settings on your device again.
I hope you find the missing configuration, because I can understand the frustration when something appears to not work as it should.
Having had a number of S7 phones that featured a stuck rotation-lock due to a borked accelerometer, and "glowing" screens while turned off due to bad display drivers, I would not discount the possibility that your device could be defective, if you have turned on the appropriate feature-set and the AOD still does not turn off when the proximity sensors are covered.
Click to expand...
Click to collapse
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
meyerweb said:
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
Click to expand...
Click to collapse
I think I see where at least some of the misunderstanding is now.
What you describe is expected behavior in the dark/low-light scenario.
Note that the AOD turns off (if you've enabled "Block accidental touches" in the display settings) only if the >proximity< sensor detects that the phone is, well, in proximity to something - such as when it is face-down or in a pocket.
If not in proximity to something, what can be expected is that the illumination sensor will simply adjust the AOD brightness (if in the automatic mode) in response to the ambient light it detects - bright in bright light, and dim in low or no light. Just as you've described your experience.
Again, if your "Block accidental touches" feature is on, and the AOD isn't turning off when it is in proximity to an object (in a pocket, face-down, etc.) you may have a defect.
meyerweb said:
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
Click to expand...
Click to collapse
I don't have block accidental touches on but it does turn off when it's in my pocket or faced down. It might be just your device. It always turns off for me when it should.
chickenbb said:
I don't have block accidental touches on but it does turn off when it's in my pocket or faced down. It might be just your device. It always turns off for me when it should.
Click to expand...
Click to collapse
Interesting. I was always under the belief that the setting was required in order to assure AOD would turn off in those situations.
Turns out, it does work regardless of the state of that feature!
I still think that having that turned on just makes sense for those times when it is in a pocket, but you are correct in that it does not preclude the AOD turn-off feature.
afh3 said:
Interesting. I was always under the belief that the setting was required in order to assure AOD would turn off in those situations.
Turns out, it does work regardless of the state of that feature!
I still think that having that turned on just makes sense for those times when it is in a pocket, but you are correct in that it does not preclude the AOD turn-off feature.
Click to expand...
Click to collapse
I have that setting on but it still won't turn off AOD in my pocket. I was worried my proximity sensor was defective so I tested it but it appears to be working fine.
What model/carrier do you guys have. I have the attached branded snapdragon model. Like I said before it used to work but now it doesn't. Not sure if it coincides with an update or not
vintagerock said:
I have that setting on but it still won't turn off AOD in my pocket. I was worried my proximity sensor was defective so I tested it but it appears to be working fine.
What model/carrier do you guys have. I have the attached branded snapdragon model. Like I said before it used to work but now it doesn't. Not sure if it coincides with an update or not
Click to expand...
Click to collapse
Verizon branded S9+ [ARBG] here.
afh3 said:
Verizon branded S9+ [ARBG] here.
Click to expand...
Click to collapse
Hmm interesting.
I meant to say att branded is what I have.
vintagerock said:
Hmm interesting.
I meant to say att branded is what I have.
Click to expand...
Click to collapse
You could always factory-reset the device and see if the functionality returns.
With an SD card and a SmartSwitch backup, it's not that painful to reset the phone and get it back to (more or less) the configuration you have right now.
After a reset, I'd probably test it >before< restoring the SmartSwitch backup - just to confirm that it isn't some app that is breaking the AOD turn-off deal.
Best of luck with this.
meyerweb said:
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Click to expand...
Click to collapse
Don't know if you've figured out your issue yet but I finally figured out what was causing mine to not turn off. It was bcActions app I was using to remap bixby button.
vintagerock said:
Don't know if you've figured out your issue yet but I finally figured out what was causing mine to not turn off. It was bcActions app I was using to remap bixby button.
Click to expand...
Click to collapse
I have the exynos version. Are you sure it's the bxActions app causing it? Because I have it and the AOD still turns off for me.
chickenbb said:
I have the exynos version. Are you sure it's the bxActions app causing it? Because I have it and the AOD still turns off for me.
Click to expand...
Click to collapse
Yeah I stopped bxaactions and it instantly fixed the AOD problem. What actions do you have your button mapped to?
Hi, I just got the notification that the Android 13 update is ready for my phone. But I'm not really sure if it's worth to go through with the update. I wouldn't want to wait another 6 months for stupid fixes needed. If anyone was brave enough to install it let me know how your experience has been so far. Thanks!
CONFIRMED BUGS FOUND BY USERS AFTER THE UPDATE:
Screen flickering when using auto refresh rate. The screen quickly changes between 120hz and lower causing flickering especially on darker tones (from grey to black). This is almost certain to happen, be ready if you choose to go through with the update!
Increased contrast. Screen constrast has been increased requiring increased brightness for outdoor visibility. Poor viewing performance in bright day light and overall darker hues at lower brightness levels
Charging issues. Phones are not charging correctly when turned on, constantly disconnecting. Charging when the phone is off is the only solution. Wireless charging is also affected and unusable due to overheating that stops the phone from chaeging
Moto Secure folder locked. Moto Secure folders cause the phone to crash and can't be unlocked anymore. Do not use Moto Secure folders to avoid data loss!
Ready For broken. If you try to connect your smartphone to the TV no output is displayed
HDR video playback is broken. When trying to play back HDR video from any app it shows as SDR. No brightness increase as it was in Android 12.
POSSIBLE ISSUES:
Overall performance degradation. Some users are experiencing slow downs and an increased heat output from the device
Audio playback not working. Some users are reporting audio not working after boot. Startup sound works as usual
Increased battery consumption
Connectivity issues might appear during calls or mobile data usage. Reports are not clear about specific conditions in which these issue appears
Screen flashes white when waking the device through the fingerprint reader
Fingerprint reader breaks and might show up as not working in the built in diagnostic software
MISSING FEATURES AFTER THE UPDATE:
Dolby app lost the custom EQ setting
WORKAROUNDS:
A device reset might get rid of most of the issues, beside the flashing screen when using auto refresh rate
To fix the auto refresh rate it is possible to lower the maximum refresh rate from 120Hz to 90Hz. Thanks to @mansell68 for posting it in the thread. Download the app https://play.google.com/store/apps/details?id=by4a.setedit22 and change the parameter "peak_refresh_value" to 90. This will solve the issue for now and let the phone switch between 60 and 90Hz correctly.
Read here.
My friend have the edge 30 pro, after update he had the same issue.
I told him to completely reset the phone after update, but he didn't do it.
giacomowrc said:
Read here.
My friend have the edge 30 pro, after update he had the same issue.
I told him to completely reset the phone after update, but he didn't do it.
Click to expand...
Click to collapse
I update my edge about 2 days ago and this is the only issue that i found with, just like says on Lenovo's forums I set the refresh rate on 60hz for the moment until we get an update.
@giacomowrc thank you very much for reporting this issue! I knew there would be something wrong with the update. Motorola just doesn't care anymore.
@iOrizon thank you a lot too for reporting back on the issue. So there's no amount of resetting it to factory that would fix this issue?
@MeltingSnowman tbh this issue doesn't affect me so much so I prefer to wait for a fix instead of reset my phone. There is no a mayor issue that force me to do that, for me at least, and in general I think that is a solid update.
I update it yesterday.
Everything is perfect, no issues, 144hz and automatic refresh working.
Very Stanley and fluid.
With all turner on on the night ONLY consumes 6% of battery on 12 hours.
Great job from Motorola.
Waiting for official a13 update.
@giacomowrc @iOrizon @almmpt you might be having two different releases? The one is asking me to update to is T1SH33.35-23-20. Also I think I got one of the first batch of units since I got it soon after launch. So I might be more affected in case they different hardware revisions that act differently depending on the software.
Also 6% on a 12h night is a bit much to be honest. I wish they addressed the incorrect scheduling that kills this phone's battery but doesn't seem to be the case.
MeltingSnowman said:
@giacomowrc @iOrizon @almmpt you might be having two different releases? The one is asking me to update to is T1SH33.35-23-20. Also I think I got one of the first batch of units since I got it soon after launch. So I might be more affected in case they different hardware revisions that act differently depending on the software.
Also 6% on a 12h night is a bit much to be honest. I wish they addressed the incorrect scheduling that kills this phone's battery but doesn't seem to be the case.
Click to expand...
Click to collapse
I have This.
With bluetooth, WiFi, and paired with Samsung Smartwatch 5 Pro with all sensors enabled.
100% imperial.
I have the Chinese variant and we still haven't received android 13
almmpt said:
I have This.
With bluetooth, WiFi, and paired with Samsung Smartwatch 5 Pro with all sensors enabled.
100% imperial.
Click to expand...
Click to collapse
The wifi and bluetooth pairing with the smartwatch might explain the battery drain, makes sense.
Thanks for the screenshot. But I'm seeing that your play store security updates are stuck to last year and the security patches for the OS are from february. Do they don't get updated with Android 13?
MeltingSnowman said:
The wifi and bluetooth pairing with the smartwatch might explain the battery drain, makes sense.
Thanks for the screenshot. But I'm seeing that your play store security updates are stuck to last year and the security patches for the OS are from february. Do they don't get updated with Android 13?
Click to expand...
Click to collapse
Hi. The security patch is only from february 2023 on A13.
mansell68 said:
Hi. The security patch is only from february 2023 on A13.
Click to expand...
Click to collapse
Bruh, this is so stupid! So the security patch is basically rolled back one month. This doesn't make sense. Thanks for the insight.
I updated a couple of days ago. I feel like the battery drain increased, but maybe it'll bounce back? I definitely like the split data/wifi buttons in the notification - I like turning off unneeded services.
I loved the side bar in 12 and it's still great, but I definitely don't see a reason to give it a permanent on-screen indicator in 13 (the half-transparent bar near the power button). It makes a visual mess if I'm using something that has a scroll bar. Let us turn it off...
Samug11 said:
I updated a couple of days ago. I feel like the battery drain increased, but maybe it'll bounce back? I definitely like the split data/wifi buttons in the notification - I like turning off unneeded services.
I loved the side bar in 12 and it's still great, but I definitely don't see a reason to give it a permanent on-screen indicator in 13 (the half-transparent bar near the power button). It makes a visual mess if I'm using something that has a scroll bar. Let us turn it off...
Click to expand...
Click to collapse
Thanks a lot for the feedback. I was concerned that they would make a mess of it and it happens to be the case, adding to the screen flickering an increased battery drain.
So there's no option to disable the indicator and keep the double tap on the power button to make that side bar appear? What a bummer...
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
MeltingSnowman said:
Thanks a lot for the feedback. I was concerned that they would make a mess of it and it happens to be the case, adding to the screen flickering an increased battery drain.
So there's no option to disable the indicator and keep the double tap on the power button to make that side bar appear? What a bummer...
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
Click to expand...
Click to collapse
To be fair I hadn't noticed any screen flickering yet, but I keep the refresh rate at 60 Hz.
Samug11 said:
To be fair I hadn't noticed any screen flickering yet, but I keep the refresh rate at 60 Hz.
Click to expand...
Click to collapse
If you don't mind trying, see if auto refresh is bugged.
MeltingSnowman said:
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
Click to expand...
Click to collapse
I got the phone the moment it was available in EU - a little over a year ago. Didn't notice anything extraordinary when it comes to colors.
Will try adaptive refresh rate for a few days.
Samug11 said:
I got the phone the moment it was available in EU - a little over a year ago. Didn't notice anything extraordinary when it comes to colors.
Will try adaptive refresh rate for a few days.
Click to expand...
Click to collapse
Mine's from the same batch.
Thank you for being so helpful, I really appreciate it. I can link you the Lenovo forum's thread where people are reporting the issue, if you happen to experience it aswell.
Finally arrived in India. Downloading now and will update on my experience soon