Database Develop

[Q] Smart Saving Bug - Anyone else seeing this?

Hello, guys. I am encountering what I think is a very weird bug with Smart Saver. I'm hoping that some other people can test this on their systems and if, it's just me, I'm going to return mine for a new unit.
With Smart Saving enabled, the screen will automatically increase and decrease brightness constantly as different pages and app's come up. In my case, the screen seems to flicker almost every time I swipe and I can't stand it, so I disabled Smart Saver. The icon is OFF on the pull down status panel and it's turned off under settings. However, whenever I reboot, I still encounter the screen flickering and dimming constantly (although it seems to be to a lesser degree). If I pull down the status panel, turn Smart Saving On and then off again, the problem goes away until I reboot the system. This is at least encouraging me that maybe it's just software and I can deal with it for a month or so.
Here's what I want someone else to test for me. Turn Smart Saver off. Turn the tablet off and then on again. Pull down the status menu and carefully watch the screen. The open portion of the home screen will dim once (which is normal). On my system, after about another 1/2 second or so, the screen will flicker or dim again slightly. It does this every time, but it might be hard to notice unless you are looking for it. When side scrolling between home screens, sometimes brightness will increase slightly and other times it will decrease. Pull down status panel, turn on smart saver, turn it off again and the problem goes away.
Help, please? Mine is a US model if that makes any difference on build 10.14.1.47.
Thank you very much in advance.

Did you download the used 10.14.1.47 manually from Asus website or was it an auto update from the device itself.
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD

Manually from the website.

I kinda have the same problem, though on my tab it is only the auto brightness that sometimes will increase/decreased constantly. Disabling Smart Saving or auto brightness helps in my case. I only have the problem when i'm in a room where there's light but the room isn't totally bright, and the tablet is with its back to the light source.

Others can correct me if I'm wrong but the 10.14.1.47 isn't being pushed through the device itself. I'm finding most people are downloading it manually from Asus website. . My estimation, I think Asus is aware that the update has some issues, thus not force updating it through the device until they come out with the latest fix.
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD

You might be right about the update. Although I was thinking more people should have this issue. Maybe they aren't rebooting their tablet often enough to notice it as once I enable/disable Smart Saver, the problem goes away until I reboot. That is a satisfactory work around, but I was hoping for confirmation from at least one other person seeing the same thing in terms of returning the device. Amazon has decent return terms, so I'll probably wait until the next update and see if that fixes it. Thanks.

I'm on .47 and I have the same issue as well. I also noticed that the brightness will increase 2-3 steps every time I bring up "settings". This is regardless of auto-brightness on/off, smart saving on/off, outdoor mode on/off.

Auto-brightness is useless: Usually it's much too dark, and the auto-setting is changing with strange behaviors.... it's kinda jumping up and down as other described...

Thanks, since others are experiencing it too, at least I'm hopeful that it will be fixed in a SW update.

Did someone contact the asus-hotline?

derekk1 said:
Thanks, since others are experiencing it too, at least I'm hopeful that it will be fixed in a SW update.
Click to expand...
Click to collapse
Same thing here, bought the unit in the US and also experiencing the same awkward behavior. This would actually go away when Auto Brightness is turned off.
I am also getting issues when docked. Sometimes after some time (maybe a couple of hours) as soon as I tilt the tablet to its normal position, I would find it completely off. Had to turn the device back on a couple of times now.
These are too many annoyances for such an expensive unit.
Hope they fix the Auto Brightness setting at least.

Disabling Asus Splendid app in settings -> apps seems to stop this behavior.

vBoedefeld said:
Disabling Asus Splendid app in settings -> apps seems to stop this behavior.
Click to expand...
Click to collapse
I am now on 4.3 and it seems to be better (just some hours). It is not as dark as before and doesn't hop up and down every second :good:

Yezariael said:
I am now on 4.3 and it seems to be better (just some hours). It is not as dark as before and doesn't hop up and down every second :good:
Click to expand...
Click to collapse
How did you do the upgrade to 4.3? Seems like it is not yet available for the US. Would you install another SKU from TW lets say, if your tablet were from the US?
I really feel like upgrading cause there are too many things not working well on 4.2.2

efgyy said:
How did you do the upgrade to 4.3? Seems like it is not yet available for the US. Would you install another SKU from TW lets say, if your tablet were from the US?
I really feel like upgrading cause there are too many things not working well on 4.2.2
Click to expand...
Click to collapse
In Switzerland it was OTA :good:
Either download right version from asus.com or wait a bit, I guess it will not take long until it's rolled out everywhere...

Yezariael said:
Auto-brightness is useless: Usually it's much too dark, and the auto-setting is changing with strange behaviors.... it's kinda jumping up and down as other described...
Click to expand...
Click to collapse
I totally agree. It's much too dark on auto and the constant jumping around drives me bat$#! +. For a 4th Gen, nearly $500 tablet, you'd think this sort of thing would be figured out by now.

calimocho said:
I totally agree. It's much too dark on auto and the constant jumping around drives me bat$#! +. For a 4th Gen, nearly $500 tablet, you'd think this sort of thing would be figured out by now.
Click to expand...
Click to collapse
You did not read my statement about update to 4.3, no?
It's very fine now, bright and constant :good:

Yezariael said:
You did not read my statement about update to 4.3, no?
It's very fine now, bright and constant :good:
Click to expand...
Click to collapse
Mine is still the same after the 4.3 update. I can see whatever algorithm it is working. For example, switch to a dark screen, wait 2 seconds, watch it darken a little more once a second for the next three seconds. Then the reverse in switching to a mostly white screen/app.
The good news is the dock doesn't seem to disconnect anymore.
Just can't decide about this thing. I want to love it as much as I loved my TF101 but I just don't (yet?)

calimocho said:
Mine is still the same after the 4.3 update. I can see whatever algorithm it is working. For example, switch to a dark screen, wait 2 seconds, watch it darken a little more once a second for the next three seconds. Then the reverse in switching to a mostly white screen/app.
The good news is the dock doesn't seem to disconnect anymore.
Just can't decide about this thing. I want to love it as much as I loved my TF101 but I just don't (yet?)
Click to expand...
Click to collapse
Theirs nothing wrong with your device. It's the ambient light sensor built into the device. ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xRevilatioNx said:
Theirs nothing wrong with your device. It's the ambient light sensor built into the device. ..
Click to expand...
Click to collapse
Absolutely. It's just really freaking annoying.
I have it right here in a bright office with fluorescent lights, which I would think would vastly marginalize the amount of light reflected from the display itself back into its ambient light sensor. Merely dropping down the notification column causes visible shifts darker (when coming from a light background) in steps, over several seconds. (and it's in the dock on the desk, so the device isn't moving at all)
So my argument is the algorithm used to determine the backlight of the screen puts to much weight on the white balance of the screen. It's distracting and annoying. And it would be one thing if this only happened on "Auto Brightness," which it does not.

Screen flicker (PWM)

I still use the original Note, and I really like the Note 4, but the screen flicker and color shift is making me hesitate about upgrading, because it's partly a downgrade.
If you don't know what screen flickering is, it's when the light from the display is more like a strobe light than a flash light. That is how many displays lower their brightness.
Think of it like a water faucet. Turn it on full blast, and that's the light from the LED at the brightest setting. To make it darker, you'd close the faucet a little, and less water would flow out. Or you could rapidly turn it on and off, and less water would also flow out, but it'd be in spurts.
The original Galaxy Note is like the normal water faucet, where it's a steady stream at full brightness, and as you lower the brightness it simply decreases the force of the steady stream.
The Galaxy Note 4 is like the water faucet that is constantly turning on and off in spurts, even at full brightness. Then as you lower the brightness, it leaves the faucet off longer, so less light comes out over time, and it appears darker.
Why does this matter? Because, a constant steady stream is pleasant, and a jolting repetitive spurt is irritating.
The original Galaxy Note is like a seamless line, and the Note 4 is like a bunch of -----------.
Galaxy Note 4 at maximum brightness (240 Hz):
Code:
-------------------------------------------------
Medium brightness:
Code:
- - - - - - - - - - - - - - - - - - - - - - - - -
Low brightness:
Code:
- - - - - - - - - - - - - - - - -
You can see this on some of the video reviews. It's most noticeable when they have the brightness lowered, and are on a bright white screen. You will see diagonal lines cycling across the screen like waves.
Try this... lower the brightness of your display to the minimum, and go to a white page. Then wave your open hand in front of it. Do you see a normal motion blur like when you do it away from the screen, or do you see a bunch of sharp lines, like trails from a strobe light?
Different people can perceive different rates of strobing light, and some are irritated by it quicker than others. But everyone should prefer a steady stream of light over an abrupt pulsing one.
There's more info on these pages:
tftcentral.co.uk/articles/content/pulse_width_modulation.htm
en.wikipedia.org/wiki/Flicker_%28screen%29
en.wikipedia.org/wiki/Flicker_fusion_threshold

best wait till the Note 5 maybe even the Note 6

It was already brought up here http://forum.xda-developers.com/note-4/general/request-to-samsung-flickering-t2905055 but moderators closed the thread. Sigh.

why Mod closed that thread?

Anyone know if there's any control over the PWM in software? Does Samsung release the display driver code?
With regular LCD displays there might be a kernel driver (drivers/video/backlight), and a sysfs entry (/sys/class/backlight/brightness). But with AMOLED they are using PWM to control the brightness of each sub-pixel, not a panel backlight.
With luck maybe at least there's an interface that could instruct the hardware to not use PWM at maximum brightness. I'd guess all the color calibration adaptive display technology would have to be bypassed though.

The PWM is defined in the kernel driver and it's too complex to change it.

I have a Note 3 and have never noticed anything like this. Does this affect the Note 3? I can't imagine why the Note 4 would do this if the Note 3 didn't. Why take a step back?
Sent from my SM-N900T using XDA Premium 4 mobile app

You know that video recording exaggerates the effect by miles? And your light bulbs flicker in a similar way? The frequency is too high for your eyes to notice though so it doesn't matter.

I found a video that compares the Galaxy Note 3 and 4 side by side. The PWM frequency looks similar in auto mode. But notice how when he changes them both to maximum brightness the Note 3 doesn't flash like the 4 does. For some reason the Galaxy Note 4 flashes all the time, even with full brightness.
youtube.com/watch?v=bHBLA0txReg#t=521
(Fast forward to 9 minutes)
Light bulbs can strobe too, and some people are sensitive. Have you ever been sick and went to a store or office with fluorescent lights? Maybe you've noticed the lighting isn't as comfortable as natural lighting. Sometimes it can make people feel disoriented, like trying to walk through a strobe light.
It would be reassuring if someone sensitive to PWM lighting said that the Galaxy Note 4 screen isn't a problem for them, even after several hours of reading.

screen flicker
Hello,
I have only used iphone since the iphone 3. I preordered the note 4. I researched alot and hope this is not going to be too big. But through my research came about this video and don't know if this is a solution your looking for but may help.
This is my first post and not allowed to link the youtube link.
Search reduce amoled flicker the video was only posted 5 days ago. Hopefully this is a good solution

This one? youtube.com/watch?v=gQNcaa2EV2U
The idea behind that is to set the brightness to maximum so it doesn't use PWM, then put a semi-transparent black layer above everything to make it appear darker.
That could work with other phones, but the Galaxy Note 4 is reported to always uses PWM, even at maximum brightness, so even with that trick there will still be strobing at 240 Hz. That might be better if the frequency would otherwise be real low at the lowest brightness.
But I think there could be other problems, like higher battery usage, rendering artifacts, inaccurate colors, and slower framerates, caused by having to recalculate all output with the transparent layer on top.
I also wonder if that even works the way they expect. If the AMOLED sub-pixels are changing intensity via PWM that is independent of the master brightness, then maybe applying a semi-transparent layer would cause those darker sub-pixels to darken by decreasing the frequency, which would be similar to lowering the master brightness level.

Noterio:
If you can see flicker of amoled displays, simply get an lcd one.
I've owned S2, S3, and S4. And never saw any flickering, especially in the darkness.
The effect on video is simply a mismatch between the framerate of the video and the refresh rate of the screen.

Many LCD displays also use PWM, but for the backlight instead of the sub-pixels. It's a similar strobing effect. I have a desktop display and tablet that use PWM, and I have to set them at maximum brightness to avoid the strobing. I've used them with low brightness for many hours and days, but it feels like staring into a strobe light.
Not everyone is sensitive. It's like, some people watch standard definition on an HD TV and don't understand why you think that's crazy. If you show them HD on the display, they act like there's not much of a difference and can continue watching SD. Other people notice smaller details and it would be too annoying to watch SD like that.
The Galaxy S4 does strobe too. I'm sure if you pay attention you can find ways to see it. One time I often notice PWM the most is when I'm staring at the screen, then look to the side. As I look to the side real fast, in my peripheral vision the flashing screen has a trail effect like when you wave your hand in a dark room lit up by a strobe light.
You could also probably set the brightness to lowest, and swirl it around in a dark room. If you move it fast, and watch the light, you'll probably see it's not a smooth blur, but has sharp jagged edges from the points in time when the pulse bursts to higher brightness.
You can also wave a pen in front of the screen and see the strobing effect.
If you don't ever notice or feel the strobing, then it's fine for you. Just like some people are fine watching SD on a very expensive TV. I don't like having to pay around $800 for a display I'll be looking at for hours every day if it's going to be irritating sometimes. Especially since it flashes even at maximum brightness, so there's no tricks to avoid it.
The fact that most people don't notice or care means there's little incentive for the manufacturers to spend extra money to avoid strobing.

more videos with flickering
note 4 (new video)
http://www.youtube.com/watch?feature=player_embedded&v=UMPfGki0Hcs
others
https://www.youtube.com/watch?feature=player_embedde%85amp;v=amuHUv6hGiM
http://www.youtube.com/watch?v=paMb_cgVkug&list=UUB2527zGV3A0Km_quJiUaeQ#t=869
http://www.youtube.com/watch?v=fQdvK5-Ejag
http://www.youtube.com/watch?v=kKCIuZsp_VQ
http://www.youtube.com/watch?v=dxtItMajHfg
http://www.youtube.com/watch?feature=player_embedded&v=8U6iuzhrgaA
http://www.youtube.com/watch?feature=player_embedded&v=aeDvaMZ8Uxo
http://www.youtube.com/watch?v=EzMdvFUhOW4
http://www.youtube.com/watch?v=FgUgN5S4C0s
http://www.youtube.com/watch?feature=player_embedded&v=fQdvK5-Ejag
https://vimeo.com/101804094
tests (use google translate)
http://www.ixbt.com/mobile/samsung-galaxy-s5.shtml
http://www.ixbt.com/mobile/samsung-galaxy-note4.shtml
http://www.ixbt.com/mobile/samsung-galaxy-note3.shtml
http://www.ixbt.com/mobile/samsung-galaxy-note2.shtml
http://www.ixbt.com/mobile/samsung-galaxy-s4.shtml
Just need to make the frequency of PWM like in Fly IQ444 Diamond 2 Quattro, Motorola Razr HD and lg G Flex

See how the Note 3 has the screen on most of the time at max brightness?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Note 4 looks worse out of all the Notes and S series, because even at max brightness it is abruptly flashing.
Maybe someone can test different settings while looking at the Note 4 through their camera to see if anything affects the PWM.

noterio said:
The Note 4 looks worse out of all the Notes and S series, because even at max brightness it is abruptly flashing.
.
Click to expand...
Click to collapse
It does not matter, the main thing that the chart does not dropped to zero. Harm to the eye and brain (at long view) occurs when there is a full damping.

I had this issue with s4 running factory set rom, after a day or two of purchase I got an update which resolved this issue. Future updates will take care if this issue if it is present at all

The PWM isn't considered a defect, so I'd be very surprised if they changed it in a firmware update.
The big question is at what brightness setting would the graph show it cycling to zero? If it's already dipping below half brightness at the maximum setting, then that's already close to a full strobe, so if you set it to 90% brightness will it be going to zero like 50% does?
Someone should look at it through a camera so they can see the flashing better, and watch to see at what brightness setting it starts to be worse.

Have mine for a day now, up late last night messing with it. Flickering a non issue for my eyes, so glad.

That's good, but has anyone done anymore technical testing? How low can the brightness go before the strobing is more obvious in a camera viewfinder? Has anyone posted any videos of a slow transition from max to min brightness?

DANGER: Severe Burn-in on LCA44B

I don't know exactly what happened, but I think burn-in protection is NOT working on LCA44B. Since yesterday I've had Instaweather faces burn into my watch, and the Red face, which I've used intermittently for 9 months, has now burned into my screen in less than 12 hours of use. Screen brightness is less than 1, something is seriously messed up in the latest firmware. Anyone else experiencing this?
Sent from my Nexus 5 using Tapatalk

Display is shifting, turns out LG is absolutely stupid, so know that THE RED WATCH FACE WILL BURN IN TO YOUR SCREEN. They added massive grey circles to the date and month icons, which burn in. Every tick mark now burns in as well. I have never experienced any issues with burn in over the 10 months I've owned it, and now it's been burned in twice in 2 days. Something is amiss with the latest update, so definitely monitor your watch for signs of burn in.
Sent from my Nexus 5 using Tapatalk

I've been experiencing burn in even with the previous update

I've experienced burn with all my watch faces on this update, and have had issues with burn in ever since flashing the custom kernel to gain WiFI, with the issues persisting even after the burn in was fixed. Sometimes however I do notice the face moving as expected, so I am not sure what is causing the problem overall. If anybody has any ideas as to solutions to this, I'm sure a fair few people would be glad to hear them, as it isn't much fun seeing the hour icons when you're say in the settings menu.
Thanks,
x10man

I highly doubt this has something to do with the latest update.
1. I've had the red face burn into my watch before lollipop was on my watch even, just because the hour marks are too big to be properly shifted in ambient mode
2. I've observed my current watch face (FORM) and it seems to shift just normally

Do you guys happen to have Developer Options enabled? I tried enabling it today and just noticed that the option Force Burn-in Protection was disabled by default.
I don't know whether it was because of that option, the newest update, or just the fact that reading over this thread made me inspect my watch more carefully, but I now notice some burn in on my watch for the first time. It is quite apparent when the notification shade is pulled down.
My watch face also has very thin graphics and I even put a black transparent overlay on my watch face to make it even darker in ambient mode.
Edit: seems the burn-ins are only a temporary (at least for me). Left the screen off for a while and its good again.

I have developer options enabled, and enabling force protection disables again after a reboot. Burn ins are temporary for me too, but I'd still rather they didn't have them at all. I don't just experience burn in on the analogue faces such as red, I currently have a "9" burn onto my watch from 25 minutes of the "together" face and watches with very thin lines such as F04 for Round Wear also burn in, after very short periods of time. It is easy to get these to go again, however I'd prefer the burn in protection to work properly. I never had these issues on 5.0, they've only started since 5.1 for me, although I am not sure if that was 5.1 overall, or 5.1 after the custom kernel flash.
Thanks,
X10man

Forcing the burnin protection has no effect if you did not messed up the default burn-in protection files. The face will still shift no matter how the switch is being set.
If you will force the burnin protection settings file to not shift, then this switch will override that.
I have no burnin at all and I have the watch for almost a year now.

I don't have any problems with burn-in after update (or before). And I'm using Odyssey watchface red + disabled minimal ambient mode so according to everything I read here I should have huge burn-in. I have this watch over 6 months, 0 problems
this is how it looks also in ambient mode ( i have red color)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

timon12 said:
I don't have any problems with burn-in after update (or before). And I'm using Odyssey watchface red + disabled minimal ambient mode so according to everything I read here I should have huge burn-in. I have this watch over 6 months, 0 problems
this is how it looks also in ambient mode ( i have red color)
Click to expand...
Click to collapse
Are you rooted etc? I'm wondering if any of the non-stock portions of my watch are causing this. I have TWRP installed, and my bootloader unlocked. It doesn't seem to make sense that some people have it and some do not, on the same watch faces et cetera. I'm not rooted, and have the stock ROM and kernel installed.
Thanks,
X10man
EDIT: I have reflashed an entirely stock system, performed a factory reset and locked my bootloader, and I can verify my watch face is now moving. I will update further in regards to whether burn in is still an issue, or if this was a fix for me

I'm full stock, never rooted or anything and I have some burn in

x10man said:
Are you rooted etc? I'm wondering if any of the non-stock portions of my watch are causing this. I have TWRP installed, and my bootloader unlocked. It doesn't seem to make sense that some people have it and some do not, on the same watch faces et cetera. I'm not rooted, and have the stock ROM and kernel installed.
Thanks,
X10man
EDIT: I have reflashed an entirely stock system, performed a factory reset and locked my bootloader, and I can verify my watch face is now moving. I will update further in regards to whether burn in is still an issue, or if this was a fix for me
Click to expand...
Click to collapse
Now I'm on stock rom, kernel and recovery, with unlocked bootloader, not rooted. I had Leedroid rom but voice recognition wasn't working that good like on stock (dunno why). Before Leedroid I was on stock without any modifications so IMO software does not affect this burn-in thing. also I'm using 6 brightness all the time + screen always on

timon12 said:
I'm using 6 brightness all the time
Click to expand...
Click to collapse
This is the perfect recipe for a nice burn-in. Of course it all depends on the colours used and the thickness of the lines involved ... but in general, max brightness on an OLED display means burn-in and shorter life.
// sent from my phone //

again, no burn in after many months I'm still using 6 brightness + screen always on.

timon12 said:
again, no burn in after many months I'm still using 6 brightness + screen always on.
Click to expand...
Click to collapse
No burn in here either, had the same face for over 4 months at 3+ brightness and always screen on.

P20 Pro Camera Flickering Bug Issue

My P20 pro has camera flickering issue like that of Google Pixel 2 camera flickering issue.
Photos taken with the camera while pointing to lights are so bad and I'm super annoyed. I bought this device 2 days ago.
I have tried factory reset , safe mode etc but nothing helps.
Can someone tell me if this can be fixed with software updates or this is hardware issue in my unit ?
Is anyone else having the same problem? My P20 Pro model is My unit is CLT-L29
Check this youtube of the flickering issue so you might understand the problem im talking about.
Im unable to post video link here as im a new user. Please go to youtube and write this " Pixel 2 camera issue under LED lights "
I have the same issue with my P20 Pro. My unit is CLT-L29.

waqarx said:
My P20 pro has camera flickering issue like that of Google Pixel 2 camera flickering issue.
Photos taken with the camera while pointing to lights are so bad and I'm super annoyed. I bought this device 2 days ago.
I have tried factory reset , safe mode etc but nothing helps.
Can someone tell me if this can be fixed with software updates or this is hardware issue in my unit ?
Is anyone else having the same problem? My P20 Pro model is My unit is CLT-L29
Check this youtube of the flickering issue so you might understand the problem im talking about.
Im unable to post video link here as im a new user. Please go to youtube and write this " Pixel 2 camera issue under LED lights "
I have the same issue with my P20 Pro. My unit is CLT-L29.
Click to expand...
Click to collapse
I assume it's a refresh rate issue on the screen, lights are constantly flickering I got some cool super slow mo videos of lights on holiday, they are a constant red light but clearly not, I assume that's all you're seeing on the camera as well
https://photos.app.goo.gl/0eQac3HtakfNEdI22

DaveP2611 said:
I assume it's a refresh rate issue on the screen, lights are constantly flickering I got some cool super slow mo videos of lights on holiday, they are a constant red light but clearly not, I assume that's all you're seeing on the camera as well
Hi Dave. In your video that is screen refresh rate because of heavy music and lights i beleive.
But in my P20 Unit it is issue in camera. I mean even if im in my room with two three lights, it gets all black lines everytime and photos,videos taken are so bad.
It is ruining my moments and im disappointed.
I have tested s9+ and Iphone X under same environment but they both work fine and no black lines at all.
Click to expand...
Click to collapse

Same thing on p20...
Poslato sa EML-L29 uz pomoć Tapatoka

Check your settings, and try with the 60fps option on and off
It might have something to do with the refresh rate of the camera and how it's set, try changing it and see if it changes something, for me it worked

AkkYleX said:
It might have something to do with the refresh rate of the camera and how it's set, try changing it and see if it changes something, for me it worked
Click to expand...
Click to collapse
How can we change the refresh rate of camera. Im not sure we can do it on mobile.
its not about display refresh rate.

You can change between 60fps an not 60fps resolutions
Changing between this resolutions is the only change I have seen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I doubt this is a hardware issue because it's more related to the refresh rates of the lighting which happens to synch with the shuttertime of the camera. It causes visible banding across the display. It will happen with all cameras, even DSLR's if you match the shuttertime to the frequency of which the lights refresh.
/ Magnus

Magnus3D said:
I doubt this is a hardware issue because it's more related to the refresh rates of the lighting which happens to synch with the shuttertime of the camera. It causes visible banding across the display. It will happen with all cameras, even DSLR's if you match the shuttertime to the frequency of which the lights refresh.
/ Magnus
Click to expand...
Click to collapse
Yes you are right. This is some hardware issue. But the things is this problem is not present on any Iphone and Samsung. I have tested many samsung phones and iphone x. They all handle lights pretty good but huawei fails at this.
Trust me photos and videos get ruined and you see black and white lines on the picture.
Its just annoying that such expensive phone can't handle lights flickering like cheap samsung phones and old iphones.
Just search Google pixel 2 screen flicker on youtube/google and you'll see what im talking about.

Just use Pro mode with longer shutter , should fix it

tcchuin said:
Just use Pro mode with longer shutter , should fix it
Click to expand...
Click to collapse
Tried it but doesnt work

No, you misunderstood my comment.
Usually this phenomena happens for the reasons i described. It happens on my $6000+ DSLR camera too and the only way to get around it is to change the shutter speed to a different one which does not synchronize with the refresh rates of the light sources. It's not a malfunctioning hardware, it's more like a limitation which can be worked around by either software hacks or shutter adjustments. Although changing the shutter speed might not work as expected with the type of electronic shutters we have in these mobile devices.
Just because you haven't seen the effect on the other devices you mentioned doesn't mean the issues don't exist there. This is a common issue on cameras with electronic shutters such as phone cameras, and even more so when you use auto settings under certain circumstances.
/ Magnus
waqarx said:
Yes you are right. This is some hardware issue. But the things is this problem is not present on any Iphone and Samsung. I have tested many samsung phones and iphone x. They all handle lights pretty good but huawei fails at this.
Trust me photos and videos get ruined and you see black and white lines on the picture.
Its just annoying that such expensive phone can't handle lights flickering like cheap samsung phones and old iphones.
Just search Google pixel 2 screen flicker on youtube/google and you'll see what im talking about.
Click to expand...
Click to collapse

Hi. I have the exact same problem. Were u able to solve the problem?

It's the LED lights that is an issue. It flickers a lot faster than the human eye can see.. but the P20 will pick that up. To get around that, go to Pro and lower the ISO and increase the shutter. It works for me.. the longer the shutter, the more evened out the flickering becomes and it won't be an issue. The LG V20 has manual video and I was able to get around that, but P20 Pro doesn't have manual mode for video.

Burn in concerns?

Until now, I've actively avoided AMOLED screens, in part due to the ability to get screen burn in. I'm still not thrilled about it, but it seems no flagship has LCD anymore and I'll have to make the trade-off.
I get some of the benefits of AMOLED, but this surprised me a bit to find on a gaming phone since games have static images (scores, gauges, maps, icons, etc). I also know that running an AMOLED at full brightness increases the burn in risk, but I'll be using this daily in bright sunlight and will need the screen fairly bright.
So what's the current expectation for the ROG 2 screen when it comes to that? Any word on if burn in will be much of a risk anymore? Would the Asus U.S. Warranty cover that, and for how long?

Burn in is probably a far smaller issue than you'd think. I've used AMOLED displays since 2010 on several different devices and never had an issue. It does happen but probably far less common than you'd think.

The only AMOLED device I've had that experienced burn in was a Samsung Galaxy Note 5, which I used for many years and was my daily phone up until I received this ROG Phone 2 a week ago. Even then, I didn't notice the burn in on it until about a year ago, and only found it by deliberately looking for it by using an app to show full screen solid colors. Even to this day I don't notice the burn in on that Note 5 during normal use. The entire time I used the Note 5 I had the brightness set to max with adaptive brightness on.

willhemmens said:
Burn in is probably a far smaller issue than you'd think. I've used AMOLED displays since 2010 on several different devices and never had an issue. It does happen but probably far less common than you'd think.
Click to expand...
Click to collapse
Especially with gestures replacing the static nav bar. Those would burn in over time. But the status bar stays pretty active, so there shouldn't be much chance their either

bluegizmo83 said:
The only AMOLED device I've had that experienced burn in was a Samsung Galaxy Note 5, which I used for many years and was my daily phone up until I received this ROG Phone 2 a week ago. Even then, I didn't notice the burn in on it until about a year ago, and only found it by deliberately looking for it by using an app to show full screen solid colors. Even to this day I don't notice the burn in on that Note 5 during normal use. The entire time I used the Note 5 I had the brightness set to max with adaptive brightness on.
Click to expand...
Click to collapse
My wife prefers the Notes and every one of hers got burn in. Her last one was the S7 (due to the N7 fiasco), and I noticed burn in within a year. She rarely has the brightness cranked, which is part of why I'm still on the fence.

Now that I have android auto radios in all my cars I don't expect to get much burn in from now on, but my note 8 always has Waze ghosted on the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

As others have mentioned before the benefits of Amoled screens far out take the LCD ones in many areas. For example one thing I hated about LCD screens because of the technology was the uneven side/bottom light spots which can be easily seen in a dark room and were very annoying to see.
Regarding Burn in, there is an easy way to avoid it in the long run by using gestures for system navigation and in regards of the status bar you can use any 3rd party app which can hide the status bar. Personally I use "Immersive manager" app to hide the status bar on ASUS launcher and in some apps which I don't like to see it in, and so because of the switch between the home screen and apps, the status bar isn't static and for that reason i doubt burn in will be an issue.

I would caution about the "Always-On Display" option of the Asus Rog Phone 2. If you go to bed and leave the phone face-up (proximity sensor not covered) then it will leave the static clock graphics up all night. I could imagine that being burned in over time.

RogPhoney said:
I would caution about the "Always-On Display" option of the Asus Rog Phone 2. If you go to bed and leave the phone face-up (proximity sensor not covered) then it will leave the static clock graphics up all night. I could imagine that being burned in over time.
Click to expand...
Click to collapse
I was watching a review video on it yesterday and it showed what looked like the AOD clock shifting (it was a short cutaway shot, so could be mistaken). I will keep an eye on it, though, to see if it does move.

Just like you, I avoid AMOLED screens. I had an S3, burn ins from web browser... I watch YouTube a lot. I am not sure the AMOLED screen is for me. It became difficult to choose a phone.

SchnauzerZoom said:
Just like you, I avoid AMOLED screens. I had an S3, burn ins from web browser... I watch YouTube a lot. I am not sure the AMOLED screen is for me. It became difficult to choose a phone.
Click to expand...
Click to collapse
Just enable Dark Mode within YouTube and assuming you watch in full screen mode, you should not have any problems. I personally run YT for about 3-4 hours everyday: the phone sits below my monitor at work and I have earphones on. Glance at the screen from time to time, since what I usually do doesn't require full concentration at most times. Never faced burn in from YouTube.
I did face some issues on Quora though, but that was with a Moto G4+ and seemed to be temporary. The logo bar on top stayed for a while, ghosting as I used other apps but went away in a few minutes after I left the page.

Amoled screens burn-in is much less likely to happen now due to advancement in screen technology and also software implementation to counter it.
There used to be a time when averagely 30-40% of screens had a form of burn-in or another.
Unless you're unfortunate to get a defective screen, I doubt if burn-in will be an issue for you.
I have a 2-year old Huawei Mate 10 Pro which I've used so much and mostly outside (full screen brightness), but there isn't a sign of burn-in on it.
Though it would be important to know the screen manufacturer for the ROG II as not only you can have an idea of the quality but also aesthetics.

I already have some lines and screen uneveness in lower brightness and mostly gray color, i wouldnt call them burn-ins but the device screen is diffinitely defective as it's only 4 weeks old and the screen was uneven from the beginning
Btw the quality and sharpness of colors is nowhere close to my father's galaxy a40 so either my device is a complete defect or the screen is just not that high-end stuff
And lets not forget the rediculous issue of getting red tine when lowering the brightness it sometimes drives me crazy, still the 120hz refresh rate is so great i cant think about any other phone!