Got my OP5 days ago, I found there is a constant black wave when I shoot in low light, like the attachment:
Anyone have seen this before? Is it a hardware issue?
Is this happening at any camera orientation and in light source?
I am asking because it might be some weird effect caused by a frequency mismatch (frequency at which the light bulbs emit vs frequency at which the sensor records)
Happening with every orientation, but only with light source. I have not seen things like this use my girlfriend's iPhone. The room light source is not complex, tried using a single light, still see it. So I wonder if it is a known issue or I just got lucky
https://www.youtube.com/watch?v=dNVtMmLlnoE
Now I understand why it happens, I just assume the phone has some kind of mechanism to deal with that, afterall none of my previous device / my girlfriend's phone has this issue.
Related
I played with my NC nearly one week and I like it. But I want to know dose anyone notice the screen of NC is flickering. If you couldn't understand what I mean, please refer to below video,
http://www.youtube.com/watch?v=iDnBSWF44rM
it is not so obvious in real world as in video, but it is noticeable and uncomfortable. I have ipad with IPS LCD but never find this kind of issue. It like some kind of low fresh rate issue in early PC screen, so I want to know whether it is possible to fix it via adjust screen refresh rate in OS level.
Your comments are welcome!
Mine does that but only on the gray background, otherwise I don't see any flickering.
I exchanged my first NC because of this issue. The salespeople thought I was nuts until I demonstrated it for them. My new one still does it but MUCH more faintly and not all the time. I do believe that Barnes & Noble is aware of it (or at least that's something I read in another thread here somewhere..).
It seems to only happen at middling levels of brightness. My first NC exhibited the issue under very specific settings and times, the brightness had to be set between 20%-40% and I had to be displaying a solid area of mid-range colors. I saw it all the time when the screen would dim to display a menu.
From personal experience, you MIGHT be able to get a unit that's better if you exchange. It does seem to be a very common issue, though. Rumor has it that it might be fixable through a firmware update.. we shall see.
I had a pocket pc with this problem many moons ago...The fix was to adjust a trim pot on the display...
No idea if anything like that would apply here, but just wanted to mention it.
I do have similar problem, could any people advise on how to check the refresh rate and increase it?
Many thanks.
Are you planning on rooting or installing another ROM on your Nook? The overclock kernels fix this issue.
from what I see there in the video, if that is what you are seeing...not refresh rate. Rather it looks like a cycling in the backligt control. Almost looks like the PWM duty cycle is out of wack...would explain why it happens at mid range of the brightness.
My first nook color had this problem, I solved it by leaving the brightness up all the time which seemed to prevent it. I got it replaced for other display issues, and my new one doesn't flicker at any brightness, so yeah it sounds like a defect.
Not a defect. It's a problem with stupid coding in the backlight driver.
They set the PWM (pulse width modulation) rate too low, at 40Hz if I remember right. It's easy to fix by setting it up to 60Hz in the driver, which I did in my old Quickie kernel. Totally gets rid of the flicker, and I've seen no side-effects, nor have any been reported to me.
I don't have the time to keep up with the kernel anymore, and for some reason no other kernel dev has pulled my driver fix into theirs. You might talk to Dalingrin or one of the other devs if you really want it, and put them in contact with me at [email protected] and I can help them get it integrated into their kernel.
Can you link to the github commit?
Tx
Sent from my HTC Vision using XDA App
Hmmmm.... my Nook definitely had the flicker issue on most gray colors, especially at dimmer brightness settings. I'm not using your kernel, but I am using Dalingrin's. I haven't seen flicker in months. Could this issue be limited to the stock ROM only?
911jason said:
Hmmmm.... my Nook definitely had the flicker issue on most gray colors, especially at dimmer brightness settings. I'm not using your kernel, but I am using Dalingrin's. I haven't seen flicker in months. Could this issue be limited to the stock ROM only?
Click to expand...
Click to collapse
It appears that way from my experience. I was running the dual boot package with stock and CM7 nightly.
The stock rom flickered very noticeably on greyish type backgrounds. Using CM7 and now Phiremod, the flickering has totally gone away.
Actually the fix is already in init.encore.rc:
Code:
write /sys/devices/omapdss/display0/timings 68000,1024/70/200/40,600/10/11/10
That said, it's going into the driver too.
Hey!
I bought my galaxy 6 months ago. Not long after I noticed a minor issue with my AMOLED display. I could see blue "artefacts" in some bright areas of the screen from time to time. Nothing serious, just blue dots and stripes, subpixels. I even posted a picture of it on reddit (second attachment) more out of curiosity than anything but was later convinced it was probably a software issue. I did have some suspicions something might be wrong with my phone but it actually happened so rarely and the issue was so minor that I just got used to it because it didn't bother me that much.
I recently flashed dark core 2.2 along with rc6 and it got *significantly* worse. I could see blue subpixels all over the screen wherever there's bright white, generally on the lowest brightness setting. Now, I believed that the hardware got worse and it's time to ask for a replacement. So before doing so I obviously had to flash stock firmware and guess what - it all disappeared. So I flashed just the dark core again to go back to rc6 - and it was back again.
The thing is, I really love this ROM and I love the voodoo improvements that come with it. I don't think I can live without them any more. On the other hand, it might be difficult to convince people from samsung that there's actually something wrong with my phone - since it happens so rarely on stock ROM. And I think that this display defect is intensified by the screen improvements from voodoo/dark core.
My only idea is to somehow make it show up on stock ROM and send it to them just then. But is this even possible without rooting my phone? Does anyone has an idea why would these blue subpixels show up in white areas? Is it something they check with specialized equipment or do they boot the phone first to see what's wrong?
Anyway, guys if you could point me in the right direction or had any better ideas... Seriously, It would be helpful even if you said that I should just return my phone and hope for the best. I'm a student and I can't really afford to be charged for returning - what they think is - an operational phone
I attached two pictures
1. a picture of how my screen behaves after flashing the latest dark kernel
2. a picture of how my screen sometimes behave on stock kernels
I'd appreciate any help or advice
Hello. I received my handset on Saturday morning from P4U and have been very impressed so far, especially compared to my experience with the One X last year where I had to swap 3 handsets before finding one without a major problem.
I have noticed however a possible glitch with the camera. When using the camera outside in bright sunlight I sometimes get glitches on the screen in the form of a jumping/rippling effect which is sometimes accompanied by a faint crackling/clicking notice. On one occasion it would not focus at all, with the screen rippling the whole time and refusing to focus. Following turning off and on again I have not had the problem to the same same degree, although it does happen occasionally with maybe just one of two ripples before the image on the screen settles down. The issue does not seem to arise in other scenarios (indoors, etc). Had I not had the situation where the camera could not focus at all I would just have put it down to the particular way that the camera focuses
Also I noticed that when the issue was most pronounced, I was standing outside our house in a bad/poor mobile reception area, just on fringe of out Wifi connection within the house. The phone was also set to auto update and was trying to do so. Could this therefore be some sort if interference issue interfering with the camera sensor or imaging chip?
Hs anyone else experienced anything similar? I am very pleased with the handset so if this is standard I would not exchange it. However if this is an indication that I have a dodgy camera module or imaging chip I would want to do something about it now.
Many thanks.
Just tried to use the camera to take photos at the theatre in combination of dark foreground and bright background. Camera struggled to focus on a number of occasions, with repeated clicking and pulsing/ripples on the screen as before. Never seen anything like it with a digital camera. Might be something to do with ultrapixel technology but it can't be right can it? Any ideas? Looks like an exchange may be necessary...
Reminds me of another thread...you should check out this thread : http://forum.xda-developers.com/showthread.php?t=2196059
Might be the same problem.
Thanks - I had seen that one too. Not the same effect, but I have seen that issue as well.
I called P4U today and got given a swap code to exchange the handset in-store, which I did earlier today. Not had a chance to test the new one, but hopefully it won't have the same issue as I have not seen anyone else complain about it before.
pclark666 said:
Thanks - I had seen that one too. Not the same effect, but I have seen that issue as well.
I called P4U today and got given a swap code to exchange the handset in-store, which I did earlier today. Not had a chance to test the new one, but hopefully it won't have the same issue as I have not seen anyone else complain about it before.
Click to expand...
Click to collapse
Do you have a video clip to show the ripple effect you have mention?
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
zetsumeikuro said:
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
Click to expand...
Click to collapse
Yeah, I saw that thread. Some funky stuff going on with display calibration and 90Hz. Since I know that the HW is not defective and the SW is the source of the issue I am less bothered now (I cannot stand exchanging HW). I haven't specifically observed that effect on my phone and while I did try forcing 90Hz, I actually went back to the stock setting since I noticed that forced 90Hz further sucked down the battery that already is not particularly stellar despite this being the XL version. I presume Google will refine the 90Hz calibration and function over the next few months. I will say though that I am a bit confused why they need to have different calibration at different refresh rates. I calibrate all of my desktop monitors and despite the fact that I have a 100Hz monitor I never have to change calibration with refresh rate. Maybe an OLED thing :shrug:
dhorgas said:
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Click to expand...
Click to collapse
I just noticed this on my pixel 4 xl tonight. But It only happens when the proximity sensor is triggered. Ex: like after making a phone call except it made everything on the screen seem over saturated on the screen and well as the same color shift you had stated. It seems to go away once I lock the device and unlock it again. It did it with smooth display on and off as well as force 90hz on and off.
There are a couple threads discussing this. Here's one of them:
https://forum.xda-developers.com/pixel-4-xl/how-to/smooth-display-colour-issues-t4000087
And another:
https://forum.xda-developers.com/showthread.php?t=3998907
Sent from my Pixel 4 XL using Tapatalk
Hello,
Have been loving this phone since I got it early this year, around Feb, apart from the battery life.
Unfortunately, recently the display has been cooked (literally) after the phone was overheated while gaming. I'm not sure what happened exactly, but at low brightness settings there is now a very noticeable greenish gradient on the display, more intense closer to where the phone got hotter. There is also an odd black line down the centre of the screen that is only visible on certain parts of the lock screen (notification banners). There is also some noticeable graininess to the screen as well now. Seems fine when brightness is increased.
Has anyone else experienced an issue like this? Unfortunately I will probably be looking to replace the phone soon, as this has made it very frustrating to use in low-light, and I'm not sure whether the severity will increase over time. I doubt there is any fix other than replacing the display unit. Any overheating has probably shortened the already poor battery life as well, unfortunately.
I did try to get an image, but sadly the effects are not very obvious in a photograph.
Make sure you are on the latest firmware and that you are not using the 90Hz refresh rate, it is known to have weird colours/a green tint. Other than that, maybe it did in fact overheat and get damaged, but I think it is unlikely at the temperatures a phone can get to, so probably a defect screen. If you can get it checked by Asus they might replace it
Adaoh said:
Make sure you are on the latest firmware and that you are not using the 90Hz refresh rate, it is known to have weird colours/a green tint. Other than that, maybe it did in fact overheat and get damaged, but I think it is unlikely at the temperatures a phone can get to, so probably a defect screen. If you can get it checked by Asus they might replace it
Click to expand...
Click to collapse
I haven't had the issue prior to the overheating. Phone is always on 60Hz because the battery life is even worse otherwise, so definitely not that.
In fiddling around it looks like the issue only happens when DC dimming is enabled though. Sadly having it off makes the display look like an LCD for anything except pure black, where the pixels turn off.
Unfortunately I probably couldn't get it repaired by Asus (without a fee anyway), as I have the bootloader unlocked and root access, and the unlocker reports the serial # to Asus. I live in Australia and we haven't had right to repair enforced like America has.
I am on latest Android 12 firmware.