Related
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
1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux. The N4 was much better as you could make a distinction between the dim light and no light at all.
On the new N5 you have to set the zero lux level so it's bright enought for moderate light, which means it's far too bright at night.
Why is the N5 sensor so poor? Or is the kernel? Really, this is pretty basic stuff. Come on Google, we want the autobrightness to work fine without having to download apps to try and fix the most basic settings.
(As per other threads, the N5 stock autobrightness is almost unusable!)
Same here. Only occurs in the kitchen under the spotlights. I've had 2 phones and the same has happened on both using lux.
Sent from my Nexus 5 using Tapatalk
Happy to see others having this issue as well. I always figured it was a Kitkat bug.
I had some dead pixels on my first N5, so I got a replacement. The replacement is now exhibiting this weird sensor issue (also spiking up to 30,000lux based on device orientation).
I have the same issue on my N5, sudden freak peaks of 15000 lux or more, then suddenly back to normal values of 50-80. Same behavior on stock kernel and Francos Kernel.
Hoping for a quick fix by Google.
Kusie
I'm having the same issue too, but it appears to be under certain lightbulbs that I have this issue. For example in 2 different situations, one I was in a restaurant and another while I was in my bathroom, and my phone would constantly pick up either 0 lux or 30000 lux (depending on the angle of the phone under the light). This is under halogen lighting.
When I get out of the restaurant and under regular lighting and when I'm in my bedroom (LED/CCFL lights), the light sensor would behave normally.
Anyone else have these issues?
Aria807 said:
Anyone else have these issues?
Click to expand...
Click to collapse
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Can the sensor be calibrated or is it just bad hardware? This is a real annoyance. My S4 doesn't read 0 lux unless there is absolutely zero and it never jumps around. Even it's own screen reflecting on my face will cause it to read 1-10. That level of sensitivity is great for setting up lux to go subzero. Maybe the kernel is translating the sensor voltage output incorrectly?
Sent from my Nexus 5 using xda app-developers app
rabaker07 said:
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Click to expand...
Click to collapse
Lux is a measurement of brightness.
I thought it was Lux causing it, but I have tried full wipe + reflashing a new rom, and my sensors still go a lil whack. This is flashing new rom + immediately downloading a sensor tool and checking the readings before installing Lux or any other apps.
However, Lux came out with a new version a week or so ago and it seems to have been waiving those spiked readings, so my phone atm isn't acting up super dim to super bright and back.
I still have this issue on 4.2.2.,very annoying. Is this a software issue or bad sensors?
Starts to piss me off so badly I think about sending my N5 back to google.
Happens both on stock auto brightness and yaab.
Help please?
Kusie
Yeah same here, very annoying, have to use Manuel britness very often
I have this same problem too. Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
I feel like the sensor is too far recessed into the phone and causing a tunnel effect. If the phone is looking at a dark shirt or surface that's a foot away from it, it will register 0 even though there's plenty of ambient light. This seems like a design flaw or a flaw in android's API.
Using the full version of Lux app might be able to fix it since it allows you to use the camera for ambient light detection but I haven't purchased the full app yet so I don't know.
Really wish android would have a solution for this because it's quite irritating.
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
clocinnorcal said:
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
Click to expand...
Click to collapse
With the stock auto brightness it was too bright in most cases and also in some cases the brightness would spike. Downloaded the free version of lux app in order to try to fix the problem and while it can adjust the brightness to be lower, the problem is that the light sensor gives low readings straight from the api.
I just installed Lux and I can't reproduce it on my Nexus. Mine always behaves correctly in automatic brightness, so I guess it's a hardware problem that only affects some devices?
I jump now in here as i have the same problem unfortunatley. I have no clue if its hardware related or software, but on my HTC One with kitkat running the same rom i dont have such issues s i guess its a HW fault. If anyone finds a solution or something that fixes this mess, would highly appreciate if wwe could keep this thread alive
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
coolguy949 said:
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
Click to expand...
Click to collapse
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
n3ocort3x said:
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
Click to expand...
Click to collapse
I remember reading something weeks ago that the sensor doesn't work well with certain bulbs. I can't seem to locate the thread though.
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.
Just got my phantom black, 12/256 exynos version delivered today, been using it since this morning and I noticed that on mobile data I have little to no connection even though the 5g icon is stable in the Taskbar, as soon as I connect to wifi everything runs normally. I also had the purple glitch when touching the fingerprint sensor but solved it by disabling the dinamic animated lock screen wallpaper and putting in a normal, static one.
Another issue is that the phone locks itself (goes to lock screen) while browsing the apps (just like double tapping on home screen) but not while using any app.
I hope this is just firmware issue since they are shipping all the phones with the same firmware region based but maybe they still need feedback from some carriers (hence the mobile data issue) and also the display glitches I believe are nothing that a firmware update wouldn't fix.
P. S. : in these first few hours I didn't get at 1 hz refresh rate
Masterkill88 said:
Just got my phantom black, 12/256 exynos version delivered today, been using it since this morning and I noticed that on mobile data I have little to no connection even though the 5g icon is stable in the Taskbar, as soon as I connect to wifi everything runs normally. I also had the purple glitch when touching the fingerprint sensor but solved it by disabling the dinamic animated lock screen wallpaper and putting in a normal, static one.
Another issue is that the phone locks itself (goes to lock screen) while browsing the apps (just like double tapping on home screen) but not while using any app.
I hope this is just firmware issue since they are shipping all the phones with the same firmware region based but maybe they still need feedback from some carriers (hence the mobile data issue) and also the display glitches I believe are nothing that a firmware update wouldn't fix.
P. S. : in these first few hours I didn't get at 1 hz refresh rate
Click to expand...
Click to collapse
With my xiaomi 12 pro if the screen brightness is dim it doesn't go to its lowest refresh rate. Increase the screen brightness and see if it goes to 1 hertz
I am having exactly all the same problems as OP with my 12/512 Exynos version. Now wondering if it is hardware or software issue with the screen glitching when using the fingerprint sensor. The glitch only occurs when using 3088x1440 wqhd+ resolution and dynamic animated lock screen. Position of the screen interference is always the same but can differ in size.
Masterkill88 said:
Just got my phantom black, 12/256 exynos version delivered today, been using it since this morning and I noticed that on mobile data I have little to no connection even though the 5g icon is stable in the Taskbar, as soon as I connect to wifi everything runs normally. I also had the purple glitch when touching the fingerprint sensor but solved it by disabling the dinamic animated lock screen wallpaper and putting in a normal, static one.
Another issue is that the phone locks itself (goes to lock screen) while browsing the apps (just like double tapping on home screen) but not while using any app.
I hope this is just firmware issue since they are shipping all the phones with the same firmware region based but maybe they still need feedback from some carriers (hence the mobile data issue) and also the display glitches I believe are nothing that a firmware update wouldn't fix.
P. S. : in these first few hours I didn't get at 1 hz refresh rate
Click to expand...
Click to collapse
I have the same issue with my S22 Ultra.
See my post : https://forum.xda-developers.com/t/first-impressions-24h.4403463/post-86438225
Same lags there. SM-S908B EUX
Exy always sucks. Why not get a snappy?
bs3pro said:
Exy always sucks. Why not get a snappy?
Click to expand...
Click to collapse
If only there we had a choice between exy and SD *sigh*
Some users have this very strange screen problem...
Some users have this strange screen problem .
Its random and it lasts for 1-2' sec
Anyone else?
I envy those who received their device already, over here they will be delivered next Friday so we have to wait a bit longer. However I don't envy the issues you guys are having, fingers crossed I don't have to return the device shortly after I get it in my hands.
anergos13 said:
Some users have this strange screen problem .
Its random and it lasts for 1-2' sec
Anyone else?
Click to expand...
Click to collapse
I've found a clip on YouTube with similar problem
xdocent said:
I've found a clip on YouTube with similar problem
Click to expand...
Click to collapse
That’s most definitely in need of a screen replacement. That’sa hardware failure. I would think one could get that fixed for free
freebee269 said:
That’s most definitely in need of a screen replacement. That’sa hardware failure. I would think one could get that fixed for free
Click to expand...
Click to collapse
What's interesting is that the guy reported the problem only when using WQHD+ on youtube. When used in say gallery the problem was not there.
I've found this guy's post with details on our national samsung group
xdocent said:
What's interesting is that the guy reported the problem only when using WQHD+ on youtube. When used in say gallery the problem was not there.
I've found this guy's post with details on our national samsung group
Click to expand...
Click to collapse
Could this also be a YouTube thing also? Like how Netflix has to certify certain devices in order to use HDR content. Maybe these new 2.0 panels need to have apps updated to work with them.
Masterkill88 said:
Just got my phantom black, 12/256 exynos version delivered today, been using it since this morning and I noticed that on mobile data I have little to no connection even though the 5g icon is stable in the Taskbar, as soon as I connect to wifi everything runs normally. I also had the purple glitch when touching the fingerprint sensor but solved it by disabling the dinamic animated lock screen wallpaper and putting in a normal, static one.
Another issue is that the phone locks itself (goes to lock screen) while browsing the apps (just like double tapping on home screen) but not while using any app.
I hope this is just firmware issue since they are shipping all the phones with the same firmware region based but maybe they still need feedback from some carriers (hence the mobile data issue) and also the display glitches I believe are nothing that a firmware update wouldn't fix.
P. S. : in these first few hours I didn't get at 1 hz refresh rate
Click to expand...
Click to collapse
About the refresh rate, did you see this article?
Samsung Galaxy S22+ and S22 Ultra refresh rate explained
There is a lot of confusion surrounding the Galaxy S22 series and the refresh rates of their displays. There is a lot of confusion surrounding the Galaxy...
www.gsmarena.com
BigDisplay said:
About the refresh rate, did you see this article?
Samsung Galaxy S22+ and S22 Ultra refresh rate explained
There is a lot of confusion surrounding the Galaxy S22 series and the refresh rates of their displays. There is a lot of confusion surrounding the Galaxy...
www.gsmarena.com
Click to expand...
Click to collapse
They forgot to mention one thing. The adaptive refresh rate only works, if your brightness is above 8% or ambient light sensor reads more than 40 lux.
So if you are some like me, with low brightness and low ambient light, get ready for your battery to dissappear as it will be stuck at 120Hz...
on some forums it is mentioned that on Vivis setting for display, the problem does not occur anymore; can you confirm?
anyway, the fact that these artefacts are not displayed when in FHD setting, shows that it is not a display problem, but a software or GPU
I've posted this in a separate thread. I don't think my issue is linked to the screen issues described here. I have a flashing green pixel. Seems like hardware. See the pics.
I have a mountain of problems too, with S22 Ultra black 12/256.
I've got:
Overheating and rebooting in my pocket when doing nothing
Random hanging whilst scrolling down a long list
Intermittent flashing green dots (I think four) across the screen
Horrendous battery life (had it for only 48 hours, but still)
S-Pen sometimes doesn't fire the Air Actions menu when removed (or basically just doesn't notice it's been removed?)
And not really a problem, but after 4 generations it still can't record HDR and 60 frames per second, when in 4k.
This is a huge disappointment, and the fastest tech return ever from me.
nathan.rich said:
I've posted this in a separate thread. I don't think my issue is linked to the screen issues described here. I have a flashing green pixel. Seems like hardware. See the pics.
View attachment 5542745 View attachment 5542747 View attachment 5542749
Click to expand...
Click to collapse
Mine gets delivered today. and if I have a green pixel like that on mine it is going back so fast.
Anyone else notice this? I did find a small thread on Samsung.com so not sure if its a hardware issue or if all of them have it. - https://us.community.samsung.com/t5...t-flickering-on-video-recordings/td-p/2209967
Seems to only do it at 60fps options 1080p60 and 4K60.
Except its just not flash light related or LED light related. It'll do it outside as well Highly annoying!
I tested it and don't have this issue.
Monipeev said:
I tested it and don't have this issue.
Click to expand...
Click to collapse
Its not a 100% all the time issue. Its under certain lighting specific lighting conditons. Usually lower light for me
for low light always use auto fps. it was tested to show its actually better and brighter and clearer
chillsen said:
for low light always use auto fps. it was tested to show its actually better and brighter and clearer
Click to expand...
Click to collapse
Last year on the 12 Pro Max Auto FPS ruined a video that couldnt be remade. It for some reason switched despite being in the bright outside, on top of that it recorded 24fps and made the clip choppy. Not saying samsung would do this but its not worth the risk keeping that enabled.
But the weird flickering has happened with it being bright outside as well
hyelton said:
Last year on the 12 Pro Max Auto FPS ruined a video that couldnt be remade. It for some reason switched despite being in the bright outside, on top of that it recorded 24fps and made the clip choppy. Not saying samsung would do this but its not worth the risk keeping that enabled.
But the weird flickering has happened with it being bright outside as well
Click to expand...
Click to collapse
something doesn't seem to be syncing. i would say the flickering is due to hardware more than software. but yea i only switch on auto fps in low light and its been impressive. i forget where but there's a video of the s22u side by side and auto fps was much more preferable since it could slow down frames meaning it would be brighter with less artificial noise reduction
Looks like a PWM frequency issue depending on the brightness of the (flash LED).
Literally just made a thread about this. The exact same problem. Glad to see i'm not the only one, because I wasn't able to find any other person experiencing this. You can see my example videos here:
Is it normal that my camera flickers on videos when the lighting level changes ? Does it happen on you too ?
It's not happening because of the lamps above, it happens on natural lighting too. It happens when camera focuses to a new area where the lighting level is different. Is this a defect, or is it the same for everyone ? Here are 2 example videos...
forum.xda-developers.com
Hope it's not a hardware problem and they fix it with an update
I'm so happy to say that May update I just received (S908EXXU2AVDA) fixed this problem. Can you check if it's fixed for you too ? @hyelton I tried every specific condition that it flickered before and it doesn't flicker anymore, made me happy that it wasn't a hardware problem and they were aware of the issue.
wholelottared said:
I'm so happy to say that May update I just received (S908EXXU2AVDA) fixed this problem. Can you check if it's fixed for you too ? @hyelton I tried every specific condition that it flickered before and it doesn't flicker anymore, made me happy that it wasn't a hardware problem and they were aware of the issue.
Click to expand...
Click to collapse
The US model doesn't have the update. I have the U/U1 model which we just got an update not long ago. So I'm sure it'll he awhile.
Glad it was fixed in an update!
hyelton said:
The US model doesn't have the update. I have the U/U1 model which we just got an update not long ago. So I'm sure it'll he awhile.
Glad it was fixed in an update!
Click to expand...
Click to collapse
Alright, tell me when you receive the update and check please, you're the only one I can ask this since nobody else was realizing about this problem lol. Hope it gets fixed for you too!
wholelottared said:
Alright, tell me when you receive the update and check please, you're the only one I can ask this since nobody else was realizing about this problem lol. Hope it gets fixed for you too!
Click to expand...
Click to collapse
I'll post here if it ever gets fixed. Yeah I'm sure it's just people don't notice it.
Example
I can hand my phone to my mom and set it to 60hz. And low power mode. She will think it's crazy fast and no lag. When it most certainly is not LOL
She does now find her old S10 slow after using a S21 FE the past few weeks.