I have a bit of a weird issue here and I am wondering if anyone else has noticed this:
For those of you in the USA who use Reading Mode - I've noticed that ever since us Yanks moved the clocks forward an hour on Saturday, March 8th, the Good Night's Read setting, which turns on Reading Mode based on sunset time, is now kicking in an hour earlier, like what it was before we moved the clocks an hour forward.
I have tried enabling/disabling Reading Mode, adjusting the system time manually and then turning it back to auto, but nothing works.
It more or less seems like the ROM or Xiaomi is pulling the sunset time from somewhere that hasn't been adjusted for Daylight Savings Time - even the official Xiaomi weather app shows the correct sunset time.
Is this a known bug in Xiaomi.eu ROMs, or MIUI in general? Anyone else experiencing this?
Related
Ever since I've been using this phone I've seen the time on the clock constantly fall behind the real time. It's set to update with the network time, but I can regularly see it throughout the day being off by 2-5 minutes, with sometimes up to 10-20 minutes behind. It seems to update with the network periodically, which brings the time back in sync, but within a few hours it starts falling behind again.
I figured the clock skew may be due to eugene's CPU Sleep App, but I haven't seen anyone specifically complaining about that issue.
I'm running DietICS 7.20.12 on an AT&T GS3, I didn't spend much time on the stock rom, so a hardware issue isn't entirely ruled out. I've done searching across the forum for clock/time skew issues like this and have turned up nothing so far. This is the system time that is having issues as it shows in the top bar, on widgets, on the lock screen, and in the shell (date command).
Anyone seen this before or have any ideas of things to try?
Stock ROM doesn't seem to have this problem, so I'd look into the ROM you have loaded.
wonton164 said:
Ever since I've been using this phone I've seen the time on the clock constantly fall behind the real time. It's set to update with the network time, but I can regularly see it throughout the day being off by 2-5 minutes, with sometimes up to 10-20 minutes behind. It seems to update with the network periodically, which brings the time back in sync, but within a few hours it starts falling behind again.
I figured the clock skew may be due to eugene's CPU Sleep App, but I haven't seen anyone specifically complaining about that issue.
I'm running DietICS 7.20.12 on an AT&T GS3, I didn't spend much time on the stock rom, so a hardware issue isn't entirely ruled out. I've done searching across the forum for clock/time skew issues like this and have turned up nothing so far. This is the system time that is having issues as it shows in the top bar, on widgets, on the lock screen, and in the shell (date command).
Anyone seen this before or have any ideas of things to try?
Click to expand...
Click to collapse
Are you using an app or something that disconnects data when the screen is off? I'm not sure if that would cause it, but it seems logical, no data = no time sync.
stevesprivateaccount said:
Stock ROM doesn't seem to have this problem, so I'd look into the ROM you have loaded.
Click to expand...
Click to collapse
If I can't come up with anything I'll try this, I just haven't seen anyone having issues with the time on DietICS
id_twin said:
Are you using an app or something that disconnects data when the screen is off? I'm not sure if that would cause it, but it seems logical, no data = no time sync.
Click to expand...
Click to collapse
Nope, data is on all the time.
For those who are interested, it appears this was somehow due to having network time enabled. Previous phones I've had have been able to use network time without issue, but for some reason this just can't keep the time in sync. I've disabled network time and set it manually and haven't seen anything more than maybe a minute at most.
Hello guys, I just updated my note to the latest DMA6 stock rom as I saw a lot of good reviews regarding battery life.
However, I was just stdading at my desk and as soon as the phone booted up after the flash, I noticed some massive tearing which annoys me as hell. For those who don't know what it is, it feels like the screen refresh rate has been drastically decreased. In order to detect it on most note 2 you can follow these steps (well most of them are working this way, because I have tested this with some other notes):
-- just lower your brightness bellow 30% go into a dark room and keep looking at a fixed point while moving the phone up and down in front of your face, this while having a bright image on it. If you see a flickering image you're a victim too:S
Another way to notice this is looking at your screen trough another (phone) camera...you will notice the old CRT effect of some horizontal lines scrolling up
I had this on my 4.1.1 as well but only till the brightness was at 40%. On 4.1.2 it goes all the way till 80%.
Being pissed to the max, I flashed my 4.1.1 backup and guess what?! Tearing gone at 40%, thus it seems to be an issue with the latest kernel.
For those wondering...yes I have disabled the screen power saving option in the power saving menu.
Has anyone noticed this? Does anyone knows how to fix it?
Cheers
If you mean to say lag then. Factory reset.
Sent from my GT-N7100 using xda app-developers app
I never recall mentioning lag whereas you probably refer as to graphic rendering delay. The phone's interface is acting as it should be, it is as smooth as expected, no issues there.
Perhaps this video will describe better what I mean http://www.youtube.com/watch?v=vL_6H-0GD3Q You can see the screen flickering very clear. This is why I mentioned that you can test this in a dark room by moving the phone reproducing the old crt effect
My question is why does the flickering/tearing dissapear on some roms at 40% and on other above 80%?
I added the #ARHH:mm#/#ASHH:mm# from "Astronomy" section and although the locality of the widget was not overridden, the times are about 6.5 hrs off (1:13 / 13:23) - a really weird offset, otherwise!!
In fact I have just realized that all time based values from the astrology section are off by the same period of time.
I'm on EST and nothing, really should cause this to happen as my phone is set to use the automatic time zone and nothing else was changed in global settings. Any idea? Can anybody verify this on their phones?
I noticed that the LiveDisplay setting is not turning on by itself if set to automatic. At first I thought it was a bug in the ROM, but after searching around a bit, I found out it requires location to work. It uses our location to determine sunset and sunrise times, and activate/deactivate LiveDisplay accordingly. Correct me if Im wrong here.
My suggestion would be to make this setting user configurable in a way that we can manually set start/stop times of night mode. First of all because we might want to turn if on/off at different times, secondly because having GPS turned on drains battery. Or give an option to use either user set hours or GPS.
Considering the magic the guys usually do, this could be implemented in a matter of hours, and would benefit the users and battery life.
Note: Before some smart ass gets to say "its open source, download and do it yourself" - I do want to do that, I am a developer, but currently I have limited hardware to build LOS and will get to it after I upgrade it.
I second this as in the UK the sun doesn't set till really late.
I found a workaround for this issue as there is still no option to set sunset and sunrise time manually. The workaround is the automation app Automagic . It supports setting of LineageOS System Settings since version v1.36. Root is requiered. In the app you have to look for Lineage OS System Setting "display_temperature_mode" (Value 4- Auto, Value 2 - day).
Anyone else notice the phone also got super snappy and smooth all the time? I tried turning on show refresh rate an hour ago just to find out the phone never go back down to 60hz.
I tried not touching the screen untill it actually auto lock, opening youtube, netflix, tiktok, chrome, settings etc etc. I even rebooted and no change. Battery life has been slightly better which is kinda weird though.
Also i checked twice, the force peak refresh rate is turned off.
Try clearing the system cache.
wanttotree said:
Anyone else notice the phone also got super snappy and smooth all the time? I tried turning on show refresh rate an hour ago just to find out the phone never go back down to 60hz.
I tried not touching the screen untill it actually auto lock, opening youtube, netflix, tiktok, chrome, settings etc etc. I even rebooted and no change. Battery life has been slightly better which is kinda weird though.
Also i checked twice, the force peak refresh rate is turned off.
Click to expand...
Click to collapse
I just checked my phone (updated to .037), and the refresh rate is still dropping to 60hz whenever there is no input, so the adaptive refresh rate still works on my end.
My phone is dropping to 60 when there's no input as well. I just played a YouTube video and it went to 60.
On my device i have the exact same problem. As you already described, it is "always" on 120hz - it only jumps down to 60 Hz for a very brief moment, then again reaches the 120hz. This cicle is repeating itself as long as the display is turned on.
I already tried disabling all overlay services and other settings that could, as far as I could think of, have an impact on these behavior, like apps that have access to usage or device controll etc.
But as for now, I don't have a solution for this.
The strange part is that i also have a better display on time since the last update, but after checking the battery temperature for the last week (i installed the .037 on thursday) it reaches higher temperatures now as it was before the update, with around 34 Celsius on .036 vs 38 Celsius on .037 after around an hour of the same activities in the mostly same environment. The temperature difference does make sense for me, because the screen won't chill as it should. On the other hand, the longer battery life does'nt seem to fit too well in this picture.
Rauchinator said:
On my device i have the exact same problem. As you already described, it is "always" on 120hz - it only jumps down to 60 Hz for a very brief moment, then again reaches the 120hz. This cicle is repeating itself as long as the display is turned on.
I already tried disabling all overlay services and other settings that could, as far as I could think of, have an impact on these behavior, like apps that have access to usage or device controll etc.
But as for now, I don't have a solution for this.
The strange part is that i also have a better display on time since the last update, but after checking the battery temperature for the last week (i installed the .037 on thursday) it reaches higher temperatures now as it was before the update, with around 34 Celsius on .036 vs 38 Celsius on .037 after around an hour of the same activities in the mostly same environment. The temperature difference does make sense for me, because the screen won't chill as it should. On the other hand, the longer battery life does'nt seem to fit too well in this picture.
Click to expand...
Click to collapse
As far as we know, it's currently buggy anyway, since the
Pixel 6 Pro is consuming more power in 60Hz mode than in 120Hz one*
Click to expand...
Click to collapse
Pixel 6 Pro Consuming More Power In 60Hz Mode Than In 120Hz One
The Google Pixel 6 Pro seems to be consuming more power in 60Hz mode, than it does in 120Hz mode. Needless to say, this is not normal, as higher refresh
www.androidheadlines.com
*in certain scenarios, like low brightness
Battery life tests have also shown that there is only a minor difference in battery life between 60hz or 120hz, so it doesn't really matter and you should - because of that - 120hz anyway since it's a much better experience.
Anyone from the UK had this update yet?
I only ask because I don't have any major issues and fingers crossed this update doesn't make anything worse.
wilpang said:
Anyone from the UK had this update yet?
I only ask because I don't have any major issues and fingers crossed this update doesn't make anything worse.
Click to expand...
Click to collapse
Officially it's only a rollout in the USA and Canada, it will come to the rest of the world with the December update (or you manually sideload it, as I did).
Morgrain said:
Officially it's only a rollout in the USA and Canada, it will come to the rest of the world with the December update (or you manually sideload it, as I did).
Click to expand...
Click to collapse
Notice anything major from the update?
Morgrain said:
As far as we know, it's currently buggy anyway, since the
Pixel 6 Pro Consuming More Power In 60Hz Mode Than In 120Hz One
The Google Pixel 6 Pro seems to be consuming more power in 60Hz mode, than it does in 120Hz mode. Needless to say, this is not normal, as higher refresh
www.androidheadlines.com
*in certain scenarios, like low brightness
Battery life tests have also shown that there is only a minor difference in battery life between 60hz or 120hz, so it doesn't really matter and you should - because of that - 120hz anyway since it's a much better experience.
Click to expand...
Click to collapse
Adaptive refresh is totally borked on the 6Pro.