Database Develop

flickering screen of NC

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.

[Q] blue artefacts / subpixels all over the screen

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

[Q] Chances of official JB update fixing black clipping?

Hi guys,
So somehow, (and I really have no idea how I even managed to do this) I went three months without noticing the horrendous black clipping on my Int. Note. Last night I was cursing YouTube's streaming and then realised something was up. After a quick look at the test PNG which I quickly discovered I'm unable to see 1, 2 and 3 which makes for a pretty ugly experience when watching darker videos.
So my question is this. Should I root and go ParanoidAndroid to try and alleviate my issue (I assume part of this process will include flashing a new kernel which is where the issue lies?) or is there a chance that Samsung will ship a new kernel with the imminent (we hope) JB update?
I'm no newbie to rooting and totally hacked my HTC Desire to within an inch of it's life (figuratively speaking, I never bricked it) and I'm always tinkering with an Advent Vega for fun. However, I'm a bit worn out by rooting and reading up on all the proper routes, new radios, kernel issues, bugs etc. I'd like a 'quiet' life with the Note where possible!
Do you think I'll 'get away' with rooting this time or is it going to be likely needed to fix this problem?

DavieMarshall said:
Hi guys,
So somehow, (and I really have no idea how I even managed to do this) I went three months without noticing the horrendous black clipping on my Int. Note. Last night I was cursing YouTube's streaming and then realised something was up. After a quick look at the test PNG which I quickly discovered I'm unable to see 1, 2 and 3 which makes for a pretty ugly experience when watching darker videos.
So my question is this. Should I root and go ParanoidAndroid to try and alleviate my issue (I assume part of this process will include flashing a new kernel which is where the issue lies?) or is there a chance that Samsung will ship a new kernel with the imminent (we hope) JB update?
Do you think I'll 'get away' with rooting this time or is it going to be likely needed to fix this problem?
Click to expand...
Click to collapse
My opinion:
Samsung correcting the Gamma table on the firmware, so dark colors appear really dark and not light gray or completly black is unlikely. They are following the strategy embraced by other manufacturers and just release a new model with a slightly better CPU and fixes for the bugs of the previous model.
xda-developers community releasing a ROM that is realy usable and fixes this: not likely either. A ROM that has no support for camera, HD recording, FM radio or S-Pen is not going to convince many people to switch.
I recently took my Note to Samsung technical service because the screen looked yellow (another known manufacturing defect), and they replaced the entire screen, but the new one shows the same black clipping problem.
Apps like filter your screen just lower the contrast so the blacks become more gray, but the darkest tone of gray the Note can show is still too bright, leading to anything below RGB (50,50,50) appearing almost the same tone of gray.
I have just moved to a phone by other company and compared it to the Galaxy Note:
Screen is IPS, viewing angle is not so ample as in an AMOLED but at least white appears white, not light brown
The gammatest.png image is displayed correctly, top row of squares going from black to very dark gray.
Brightness on the Note is limited to avoid burning the AMOLED too fast, and even so, I had burn-in on the top of the screen after only 3 months
My new phone has 1 GB RAM, and 980 MB are listed, not 808, and I have 400 used normally, with 580 free. Note had usually 700 MB used
My new phone seems to spend more time on deep sleep, no Samsung apps or services working on the background

Serious problem with AMOLED monitor of my NOTE.

Hello guys,
i'm new to the Galaxy Note and the Forum, start by thanking everyone for the great job you have done and are doing.
- Before:
I bought a Galaxy Note, I am fine and i love him like a son (maybe because I have no children).
There was the original version of Android 4.1.2 firmware N7000XXLSA with NO brand.
I flashed from the original recovery kernel that is here (forum.xda-developers.com/showthread.php?t=1901191) to be precise "Philz-cwm6-XXLSA-DBT-v3.99" (I do not know why I chose this among others, perhaps because it reminded me of the original LSA final XXLSA and makes me wonder: the "Philz-cwm6-ZCLS8-CHN-v3.99" is newer than the one I flashed?).
From ClockworkModRecovery I installed, after fullwipe, the last Nightly of CyanogenMod 10.1 and the gapps (as I did on other phones like Nexus S and Nexus 7 and it is always gone smoothly).
- The problem:
Everything works fine (apart from a phenomenon of Battery Drain, but I have to recalibrate it and recharging from consuming it all off for at least 4 hours and then delete the stats etc ...), but there is one thing wrong: the monitor.
The icons on the desktop can be seen very well, ultra bright and the text looks really HD! (I come from Nexus S and I also have the Nexus 7, bright colors and blacks amazing!) But the background, some photos appear, or the shades of black phone menus you see badly.
If I use MXPlayer to see a video all blacks are pixelated, gradients are sheared.
As if it was in safe mode, type windows xp in safe mode that NOT loaded the video card drivers.
I read around on the issue and there was talk of color banding, 16bit software compared to 24bit monitors hardware, but in essence what?
Depends on the kernel?
I have to go in customer care to replace the monitor (which also occasionally changes almost imperceptibly color, for example while navigating, then on the white background of the pages, from white light turns yellow, then brown, and so on).
What do you recommend? Does anyone have or have had the same problem?
UPDATE:
This morning I tried the phone around, the street outside and the problem seems to disappear.
I set auto brightness. So maybe with strong light, increasing the brightness of the blacks are softened better.
Now I'm recovering from the last original software Samsung Kies, the much-hyped premium suite, see what happens and if the problem remains.
Thanks in advance to all.

Low Brightness Flicker (LineageOS & Stock too?)

Hi, sorry if this was posted before, but with XDA moving to XenForo, search seems messed up, i did several searches and nothing comes up for "flicker" in this whole Pixel 4 XL Forum...
Has anyone else dealt with the low brightness screen flicker? I know it can't be just a bad phone, since i just bought three pixel 4 XL phones and they all exhibit this same behavior.
They are all running LineageOS (Official builds) so I don't know if this just affects the ROM or stock as well (although I've read it might affect stock phones too elsewhere).
It makes the phone pretty difficult to use in very low light situations, the screen will constantly flicker (more noticeable on darker backgrounds).
At first I thought it was just the Opera browser (as that's what I prefer), but it's operating system wide... Apps like "Darker" help.... because you can crank up the phone brightness and use a filter to dim the screen.... but it doesn't get the top & bottom menu/buttons, so those remain like spotlights in your eyes with that workaround.
Just curious if anyone knows whats up with this... it's the only phone I've ever seen this behavior on (and i've used Pixel 1,2,3 XL phones all with Lineage, and a myriad of other devices back in the Cyanogenmod days.... I've never seen a screen flicker issue like this).
Thanks for any help
edit / update-
the pro version of "darker" app works to fix this.... you crank the phones brightness to 100% and with the pro version you can dim the rest of the interface.
hopefully this helps anyone else suffering from this HUGE flaw (again i don't know if its just LineageOS or not, i didn't run stock on these except to unlock bootloader etc)

Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.

edwinek said:
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
Click to expand...
Click to collapse
hmm.... you running stock i guess? i don't see smooth display option in lineage