Related
I have been playing with my TF for a little over a month. I updated to 3.1 so I don't know it this is an issue. My problem is the ambient light sensor. It doesnt seem to work. No matter what brightness i have or if it's on auto or not I have never seen my screen get dimmer or brighter in any situation. I put a flashlight right on the sensor and I see nothing change onscreen. Anyone else have this going on?
My light sensor appears to work. It does have a fair amout of hysterisis in it otherwise it would drive you nuts.
Sounds like you're either not shining your torch at the actual sensor or yours really doesnt work. It's about an inch to the left of the front camera in case it's the former. It should poll every 4 seconds when on 'auto' brightness, and change the screen accordingly. I find that it works, but it doesnt really change the screen brightness to the best level for viewing. I'm sure there's an app to deal with this although I usually just set it manually. It's easy enough to do.
Oyeve said:
I have been playing with my TF for a little over a month. I updated to 3.1 so I don't know it this is an issue. My problem is the ambient light sensor. It doesnt seem to work. No matter what brightness i have or if it's on auto or not I have never seen my screen get dimmer or brighter in any situation. I put a flashlight right on the sensor and I see nothing change onscreen. Anyone else have this going on?
Click to expand...
Click to collapse
It's perfectly possible the sensor is sensitive to IR or some other wavelength in daylight that's not emitted by your flashlight. The sensor definitely works just fine for me.
I never notice the screen changing brightness (it's designed to gradually change according to the different light exposure so human eyes don't notice it changed, but in reality it did change). When I'm in a car however, if there's trees near by and it blocks the sun every so often, I can clearly see the brightness suddenly shooting up and dropping down. I don't think it works with lamps though (turning on my lights didn't make the display brighter), only light from the sun.
It works quite well now that I'm updated to 3.1. It went through various stages of not working or just messing up back on the 3.0 updates. Now it reacts, increases and decreases and the screen is bright enough.
Mine seems broken too. Strange, because this would be the first thing wrong with me Transformer and it doesn't even seem like a common problem.
This and the browser typing lag alone are making me think of selling it.
Okay, mine is definitely broken.
I just tried it by going out in the balcony and then going in the bathroom and shutting the door - nothing happens.
Seriously Asus, what were you doing when you designed and built this thing? My Tranformer is otherwise perfect - no light bleed, no creaks, no pubes under the screen, no issue at all. Except the light sensor... it seems maybe the perfect Transformer doesn't exist.
mine works
Okay, some progress.
Shinning my HD2's bright dual LED's right onto the sensor actually makes the sensor work.
But still, this thing is apparently not calibrated well because going from outside to a totally dark room didn't change the brightness - it doesn't matter if putting two LEDs right onto the sensor makes it work, that's not why it's there.
On my TF, it takes about a minute for the brightness to change when I move from a dark room to the great outdoors.
Give it a little time for the software loop to kick in
Is this any way to calibrate this sensor? It's works horrible!
Shawn_230 said:
Okay, some progress.
Shinning my HD2's bright dual LED's right onto the sensor actually makes the sensor work.
But still, this thing is apparently not calibrated well because going from outside to a totally dark room didn't change the brightness - it doesn't matter if putting two LEDs right onto the sensor makes it work, that's not why it's there.
Click to expand...
Click to collapse
Do you have a screen protector?
Not to go off topic but I only had keyboard lag when I was using the Asus keyboard Shawn, have you tried the default Android keyboard?
There is an app in the market called androsensor that will tellyou the values for many sensors including the light sensor.
Mine is measured in lux and ranges from 0 to 400 indoors it does not update quickly mine updates every few seconds.
Sent from my Transformer TF101
vladdt said:
Is this any way to calibrate this sensor? It's works horrible!
Click to expand...
Click to collapse
There is a paid program i use and love called lux
Well worth the price imo. It essentially lets you manually adjust the screen brightness for the various light levels over time, remembers these and will automatically put the screen at those levels next time. It alo has some logic too but i cant talk to that.
Sent from my Transformer TF101
It seems to work for me except that it doesn't adjust the levels properly. I can be in a somewhat bright room and the brightness is still at its lowest level, making it difficult to read. However, in broad daylight, the brightness shoots up.
I might try Lux as suggested previously.
lrissman said:
There is a paid program i use and love called lux
Well worth the price imo. It essentially lets you manually adjust the screen brightness for the various light levels over time, remembers these and will automatically put the screen at those levels next time. It alo has some logic too but i cant talk to that.
Sent from my Transformer TF101
Click to expand...
Click to collapse
+1 for Lux - great app
Sent from my Transformer TF101 using Tapatalkr
It seems to me that Samsung has screwed up the screen calibration inadvertently in their cluster-F of an OS. The S4 shows black clipping in images, gamma test charts, and videos, but I found some remnants of a more capable screen here!
http://youtu.be/V7T4rEQt27o
Seriously Samsung, don't give a crap if it gives somewhat better battery life, FIX THE DAMN THING! What's the point of releasing an FHD phone and having that black clipping and blue tint? At least leave an option to switch it on and off.
Will be fixed with custom kernels as with S3/Note 2, hopefully.
Noticed this last night while multitasking.
Kind of annoying, I do think its software related because my SystemUI crashed at one point, among other things, and it stopped happening.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
burningembers said:
Noticed this last night while multitasking.
Kind of annoying, I do think its software related because my SystemUI crashed at one point, among other things, and it stopped happening.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Whats stopped happening after the UI crash? Did the clipping go away?
that would be a step in the right direction
sam2c said:
Whats stopped happening after the UI crash? Did the clipping go away?
that would be a step in the right direction
Click to expand...
Click to collapse
Correct. Whereas before going from one screen to the other would cause a momentary jump in brightness, then a quick lowering of brightness by a noticeable but nearly insignificant degree - post a ton of errors/crashes, it stopped happening.
At one point the phone jumped a few notches in brightness (without my touching anything). And from then on out, all my screen swaps from light/dark, dark/light, different apps stopped having that ever-so-slight adjustment.
So it *seems* like it is an adjustment made on-the-fly of sorts, and I would really love to just be able to disable it...
This was a major problem in the OG Note and was never fixed.
Samsung needs to fix their screen because it's terrible compared to other phones. I can barely see the screen in daylight when I'm outside.
As an experienced Android and iPhone user, this phone is the biggest disappointment of my life. The lag is horrible and there are so many annoyances like the screen brightness changing all of a sudden (with auto brightness off). We need CM10
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I can confirm that this happens in Netflix as well. If you pause on a scene with clipping, and hold down the menu button, the clipping goes away or atleast improves substantially, right before the Netflix app fades away.
There definitely seems to be something crippling the gamma across the OS
Is it me or am I the only one happy with the screen? It's not that bad in daylight as long as you bump up the brightness and you can adjust the color mode on the screen so it mimics the HTC One color saturation.
Also I don't notice any clipping, fault screen perhaps?
I leave auto brightness on all day I live in sunny Miami Florida and I see my phone perfectly outside. I never have any jump of brightness but in the settings menu I do get a little bit of this blue smearing and whites go a little darker but its minor not enough to make you annoyed. I don't know but I'm having no problems with my phone and I love it
Sent from my SGH-M919 using xda app-developers app
Thermalwolf said:
Is it me or am I the only one happy with the screen? It's not that bad in daylight as long as you bump up the brightness and you can adjust the color mode on the screen so it mimics the HTC One color saturation.
Also I don't notice any clipping, fault screen perhaps?
Click to expand...
Click to collapse
Go to the Play Store and watch the Trailer for Django Unchained.....no clipping? Clipping is present on every AMOLED, just to different degrees
As far as is my understanding, either the screen smears on grey on black, or you have reddish blacks. Some might not notice it or care really
pezlomd said:
I leave auto brightness on all day I live in sunny Miami Florida and I see my phone perfectly outside. I never have any jump of brightness but in the settings menu I do get a little bit of this blue smearing and whites go a little darker but its minor not enough to make you annoyed. I don't know but I'm having no problems with my phone and I love it
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
The smearing can be reduced by using the appear app Scream Adjuster and setting red green and blue to + 5 to +10 depending on how badly it smears.
Yea it sucks. But an update can easily address this issue
can someone give me a specific example of where they're having problems?
I just ran the black/white/APL clipping patterns from AVSHD-709. Movie, Photo, and Standard all show no problems. Dynamic however, crushes blacks. Those who are having issues, are you all running Dynamic screen mode?
edit: upon further inspection, it would appear that 17 and 18 get clipped in movie/photo/standard. It's not perfect, and that's all this guy seems to be demonstrating, but I can't imagine a situation where any of you could be legitimately noticing it. It's well below 10% luminance. Just leaning back in your computer chair can clip that many shades of black or more on an LCD monitor. Just as an example; this would not show up on a calibration report, even if gamma was done in 5% steps instead of the typical 10%.
If any of you are really seeing crushed blacks, I would bet that you're using dynamic mode.
Same issuse
Sent from my GT-I9500 using Tapatalk 2
King Shady said:
As an experienced Android and iPhone user, this phone is the biggest disappointment of my life. The lag is horrible and there are so many annoyances like the screen brightness changing all of a sudden (with auto brightness off). We need CM10
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
You must have a good life.....
King Shady said:
As an experienced Android and iPhone user, this phone is the biggest disappointment of my life. The lag is horrible and there are so many annoyances like the screen brightness changing all of a sudden (with auto brightness off). We need CM10
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Then you need to exchange your phone. I got the 32GB on the 10th and installed the Titanium backup setup from my GS3 and the S4 destroys it in every way. Absolutely no lag, much better battery life, more natural screen saturation, although still oversaturated on the greens. I havent changed the default setting for the screen, which was set on adapt. I am a full time video editor and I just watched the Django trailer off the play store and it was flawless, blacks were crisp, no pixellation or overcrushed blacks and the brightness did not pulsate with changes in luminance from scene to scene. With auto brightness on in a dark room or fully lit room.
I do remember when I got the S3 with ICS stock how terrible the autobrightness was and terribly laggy camera was but after wither the JB update or custom ROMs, all that went away. But none of that exists on this 32GB one I have, so if you applied the latest update and you have the same probs then def get an exchange.
the black clipping is a known issue, and if you're still complaining about lag, swap your phone as everyone who's done that hasn't had any since. as for random brightness changes, noone's mentioned them since the ota
Got rid of the lag by switching launcher to nova and froze a lot of **** from AT&T and Samsung. It hasn't freeze ever since.
The smearing is present but only in the settings menu when I scroll up/down. Not a big deal but I hope it gets fixed.
Besides that the screen is gorgeous and have no complaints. Excellent battery life.
Sent from my Samsung Galaxy S4
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
I don't even think about it.
I share the same concerns.
The last OLED phone I had was a Galaxy Nexus and I told myself I'd never get an OLED screen again after that nightmare.
Dealing with the OLED issues has been better with improvements in the technology and overall quality control.
Android OS also has some changes that help prevent burn in. For example the navigation bar and status bar change colors based on the app.
With AOD I know Samsung for example slowly moves the elements around so it doesn't burn in. You can enable the Oneplus AOD with root but Always on Display isn't the same as the Ambient Display on stock Oneplus. Ambient display doesn't stay on screen long enough to really cause any burn in.
Best practices are to avoid high brightness, stay at half or less. If you have a game HUD or other static elements on screen for extended periods of time, rotate the phone when in landscape so it is less likely to burn in.
I'm not an expert on this so i'd like to hear others responses too. This is a more expensive flagship phone so I want to use it for games but avoid the burn in.
I've already read some reports of burn-in on Oneplus Chinese board. The culprits seem to be some Tencent games and its video streaming service. All have very high contrast UI elements, and users tend to turn the brightness very high.
This was the case with my plasma TV. Civ4 left some nasty burn-in in the first year but after so many years of heavy PC usage those remain the only true burn-ins on the TV. It depends on the app. Are there some ways to measure contrast of onscreen elements? In addition to phones I need to replace my plasma with OLED in the coming years.
I got burn in on my OnePlus 3 bc I keep it in my car and use it for a music player, there were times I left it on overnight on a static image multiple times, so if u plan keeping ur phone on all the time on a certain image then u don't have anything to worry about.
I used the Galaxy S3, Oneplus 3, Oneplus 5T all with OLEDs. No burn in. Never. Of course if you are and extrem case and you leave the screen static on for a lot of hours on several days there MIGHT be the risk. But with normal to "normal" heavy usage you shouldnt really be concerned.
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
Better u only turn it on for a few seconds, be carefull after 10 sec it gets critical..
Just don't leave the screen on at max brightness for long periods of time and you'll avoid burn in.
Because the pixels are self-illuminating and will eventually wear out/start dimming in an OLED display over time, this will probably be a concern with any phone that has such a display.
I had burn-in with my OnePlus 3T starting after a little over a year of use. I had my 6T for about 7 months and hadn't noticed any problems with it by that point.
I think the biggest culprit in long-term use is the notifications area of the status bar, unfortunately. The notification icons usually directly contrast with whatever is on the screen at the time, which ends up causing the pixels to wear out at different rates. While the burn-in on my 3T wasn't defined or crisp, there was a noticeable brightness difference where the icons usually display, and it was apparent any time there was a solid color in that area of the screen.
https://www.cnet.com/news/oled-screen-burn-in-what-you-need-to-know/
To fight this, keep up to date with swiping away notifications, and use gesture controls in OOS instead of the navigation bar.
Use Auto brightness and enjoy the phone...
Honestly, I would be concerned. I have noticed screen burn on my 7 Pro already. My specific case is that I use Waze while driving, and on long (> 1 hour) drives I get the UI lightly burned in. After I noticed it, I alternate the phone orientation 180 degrees to minimize its effects. I also have the "Colors" screen saver activate whenever plugged in, which has noticeably reduced & corrected the issue. Just be aware and adjust the phone orientation regularly and you should not see anything burn in.
My Galaxy S4 and 1+ 3T both had burn in, but after several years of use. (Same app was the culprit.) I think the reason it happened on my 7 Pro faster is because of the higher brightness and 90Hz refresh rate. Once I kicked it down to 60Hz it does not happen near as often .
thedr9669 said:
Honestly, I would be concerned. I have noticed screen burn on my 7 Pro already. My specific case is that I use Waze while driving, and on long (> 1 hour) drives I get the UI lightly burned in. After I noticed it, I alternate the phone orientation 180 degrees to minimize its effects. I also have the "Colors" screen saver activate whenever plugged in, which has noticeably reduced & corrected the issue. Just be aware and adjust the phone orientation regularly and you should not see anything burn in.
My Galaxy S4 and 1+ 3T both had burn in, but after several years of use. (Same app was the culprit.) I think the reason it happened on my 7 Pro faster is because of the higher brightness and 90Hz refresh rate. Once I kicked it down to 60Hz it does not happen near as often .
Click to expand...
Click to collapse
Do you have your screen turned to full brightness when using waze? I keep mine at about 40-50% brightness. I use maps for 2-3 hours a day 4 or 5 days a week and I have had my 7 Pro since launch and I have zero burn in. I have never had burn in going back to my note 3 days either. I/m actually looking at my OP6 right now as well and no burn in there either (bought that on launch day as well). I also activated forced 90hz all apps on my 7Pro as well and nothing yet. I'm guessing it's your screen brightness that is doing it. Nothing else makes any sense.
Tmobile demo both phone in my store have burn in.... But also does the note 9 and a few others.
Those have the same image on the screen 90% of the time and the screens are set to max brightness to show off the display. All AMOLED displays will burn in if you test your phone the same. When I use maps, I turn off auto brightness and just set it bright enough to see the screen which usually is about 40% brightness. I also change my wallpaper like once a week as well
Had burn in on both 6p and s9 and all in status bar and navigation bar. Now I've installed system tuner and switched on full immersive mode. You need to be rooted though. Using battery widget to look at battery life.
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
Used my OP3 for 3 years straight until I switched to the 7 pro. Never had to think about burn in. Just chill and enjoy the device
When using google maps or waze on long trips, keep the screen off till the next turn. That's what i do. I NEVER keep the screen on long enough with a static image. I don't think there is any tech that will not give a burn in with a static image over long periods of time. I will still pick OLED over LCD any day.
equlizer said:
When using google maps or waze on long trips, keep the screen off till the next turn. That's what i do. I NEVER keep the screen on long enough with a static image. I don't think there is any tech that will not give a burn in with a static image over long periods of time. I will still pick OLED over LCD any day.
Click to expand...
Click to collapse
Everyone should just have a spare lcd phone for navigation. I use an iphone 6s for navigation in my card. Tether data from my phone and dont have tk worry about burn in
I use mine for navigation ,i drive a convertible so the screen is always on high brightness.
Never had any issues with my galaxy s8 which i had for over a year and used it the same way. Poor thing had the maps on more than anything else.i broke the display before the any burn ins.
The display should not have any burn ins even after prolonged use.
However you might want to keep it at 90%max brightness.
I make the most of my oneplus 7 pro so if i notice any burn ins i'll just return it to warranty. I don't care ,i use the phone however i want to.
Also the colors are going to be visibly washed out after a few years of use compared to when it was new,that's why i always insure my phones and just get a brand new one before my contract expires.
In order to avoid getting burn-in you have to:
1. Avoid displaying images with static contents for more than one hour at a time. Many people get their keyboard burnt in because they text obsessively.
2. Avoid using a higher brightness than you need.
3. Maybe use the gesture based navigation.
Tipically burn in is a non-issue but displaying static content for more than an hour uninterrupted can get it to appear, depends on the panel, brightness and color being displayed.. Just pause what you're doing every once in a while and you should be fine.
Hey guys
Do you experience also light sensor issues like wrong brightness in certain environments and the sensor is to slow in adjustment?
Yeah i do, mostly in the camera App. It always gets really dark for no reason.
Yeah, i've noticed this in low-light areas, the brightness goes back and forth a lot but mostly stays lower than expected
Light sensor in xperias is adaptive. If you think that your mobile got brightness wrong in a certain environment just correct it by using brightness slider. After couple of days and adjustments it will get every light situation right.
I find this approach to work better then with other brands even though it takes som time to get it just right
Thanks for all the answers. I can also confirm that the expected brightness is lower and after some days off correction the results are getting better.
It has pwm even on full brightness. I tried the pwmfree app https://forum.xda-developers.com/t/app-amoled-pwmfree.3898070/ but it still hasn't fixed the problem.
Doesn't it bother you? My eyes hurt while looking at the screen.
I've read a bit about it on the link you've provided. How did you know if our phones have it? I am quite interested in this!
You use the camera from another smartphone or another device to look at the screen of the a52. And you change the shutter speed or exposure in the camera until you will see the bars pulsating on the screen of the a52.
Oh well then it seems like most of my phones since 2015 or so have had that, and I've never really suffered from headaches from it, not that I've noticed.
You can't notice it consciously, but some people, including me, are affected by it. The thing is this could easily fixed by samsung, but they wont do it. Other companies have removed the pwm effects on their amoled screens.
dragon.. said:
You can't notice it consciously, but some people, including me, are affected by it. The thing is this could easily fixed by samsung, but they wont do it. Other companies have removed the pwm effects on their amoled screens.
Click to expand...
Click to collapse
Damn that sucks, especially when you know its an easy fix from the OEM to implement.
One thing though, from what I've read off the PWM Free apk page, it uses a transparent black overlay and increases its opacity as you decrease brightness. If that's the case then you could use Twilight to acheive the same goal, right? Just max out the brightness and turn off auto brightness, then use Twilight as your brightness adjuster, turning the bluelight option down. Could that work?
The weird thing about the a52 is that it has pwm even on max brightness, so probably twilight wont work as well. I will try it later though. Same problem on the premium samsung range: https://eu.community.samsung.com/t5...been-addressed-on-the-s21-series/td-p/2641628
dragon.. said:
The weird thing about the a52 is that it has pwm even on max brightness, so probably twilight wont work as well. I will try it later though. Same problem on the premium samsung range: https://eu.community.samsung.com/t5...been-addressed-on-the-s21-series/td-p/2641628
Click to expand...
Click to collapse
Yeah, it still flickers even at full brightness. Maybe setting it at 60hz could fix that? I'll try it later to see if that could work. My previous phone doesn't have that issue at full brightness, so I'll gauge the difference based on the difference between the two.
I use mine only on 60hz and it still flickers.
Yeah, I've tested it and there is a difference between 60hz and 90hz, but the flicker is still present.
Edit: I also re did the test on my old device, a J7 Pro, and it stops to flicker altogether at peak brightness. So yeah, this phone has very prominent PWM.
ashraftheboss said:
Edit: I also re did the test on my old device, a J7 Pro, and it stops to flicker altogether at peak brightness. So yeah, this phone has very prominent PWM.
Click to expand...
Click to collapse
Yeah, that's why samsung should do something about it. Because we still have flickering at max brightness, we can't use other software to correct the issue.
dragon.. said:
The weird thing about the a52 is that it has pwm even on max brightness, ...
Click to expand...
Click to collapse
I suspect you didn't actually have the brightness set to maximum. This cannot be set manually, but is only set when the ambient brightness sensor (front camera) is illuminated by a very bright light - the sun, or a very bright flashlight. The brightness of the display is then visibly increased above the normal maximum.
Well, if the max brightness can't be controlled then it's not relevant. In this review https://www.notebookcheck.net/Samsu...ntly-more-affordable-without-5G.539956.0.html they tested the pwm on the display with an osciloscope and it shows that when you manually set the display at 100% brightness it still has pwm. This is one of the worst pwm out there, and a shame for samsung to do something like this.
is a shame unless samsung make a change in the firmaware the a52 is a pain in the eyes i need to sell mine now i cant play any video game unless i want a eyestrain
Pwm sensitive here.
Samsung A71 was OK pwm 240 hz.
Samsung 21fe was OK pwm 240 hz.
Samsung s6 edge was OK pwm 240hz
Mi 11 ultra not OK pwm 480hz. Not OK even with anti-flickering or pwm_free / oledsaver app. Mi 11 ultra has Samsung display E4.
I really don't understand. Maybe is the highs and Bottoms in the amplitudes.
Works well on my galaxy s8
ashraftheboss said:
I've read a bit about it on the link you've provided. How did you know if our phones have it? I am quite interested in this!
Click to expand...
Click to collapse
Hi. I realised the negative effects last year after a year of using amoled display on redmi note 10. It gave me headaches and also my eye power changed from 0.5 to 1.5 for both the eyes in just less than a year. I do 3 hours of use a day. That's how I learnt about PWM and the headache it gives to people.
edit - REDMI NOTE 10 died a week ago and I am searching for a phone which doesn't have PWM issue in it. For past 7 days I am using LCD screen and my eyes feels a lot better.