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.
It seems that corner touch screen sensitivity issues are prevalent among all nook color users. What I'm wondering is, does nookie Froyo have this issue as well?
Yes, or at least for me.
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
I'm on a rooted stock, but my edge sensitivity issues went away when I loaded one of the overclock kernels. I don't know how the two could be linked, but it is the only explanation I have for the difference. I'm not sure if that's been explored on Nookie, but I thought I would share since that would point to a software issue rather than hardware.
isolated_epidemic said:
I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
That I'm not so sure of. Using "Touch Test" I see all touches, but they seem to get shifted slightly when I press near the edges. Maybe this could get solved in the driver (maybe with some help of calibration tool). I hope to have time to play with this sometime soon.
isolated_epidemic said:
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
How can you be so sure?
If i use google market, sometimes the search button is hard to press,
but using appbrain market it works 100% of the time without problems.
No its not H/W I think, run some tests and corners work fine.
Its certainly something else, I also have better response after loading OC.
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
I've seen the same behaviour as well, some apps the corners take 18,013,108 tries to get to work, other apps I'm all "Whoa, first try and it worked?!".
I put the 950 OC on my autonoot but then I started playing with Froyo on a C10 SD card (very quick) so I don't know if the OC's actually helped with the corners or not. And of course this is the one day I leave it at home since I got it.
Ultimoose said:
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
Click to expand...
Click to collapse
Use Menu>Search instead of trying to touch the top magnifying glass.
Happens to me with Froyo. I seriously doubt its hardware related. Seemed to work fine on the stock B&N.
It is common for digitizers to be less accurate along the edges but the Nook Color seems worse than normal. I've noticed the problem regardless of kernel or rom used.
I'm pretty sure it has something to do with the LCD Density. All buttons/elements are a lot easier to press when I switched to 240-250. It does look ugly though, it'd be a lot prettier when we get a custom rom running.
Sigvard is right. Fixed for me by chaging my LCD Density. I set it to 200, which is a little too large for me, so I may lower it. But since doing that I have had no problems at all.
Guide here: http://forum.xda-developers.com/showthread.php?t=889951&highlight=LCD+Density
Ha! I have the exact problem even with stock rom. I though it was the problem of the particular corner of the unit I got! It is much easier to press the button in landscape view.
I dont believe its the screen. Download AppBrain and tap the search button. it works 100% of the time
It is the screen. Use a drawing program and notice how it is easy to draw a straight line in the middle and not as easy on the sides and corners. Note, you need to drag your finger slowly or else you will see more interpolation.
Raising the LCD density just hides the problem by making the hit zone bigger. Fortunately, I can live with the it.
Device: Nook Color rooted to 1.1
I had my Nook Color in the car today (40 degrees or so), pulled it out to show her what it looked like rooted. While standing in the driveway showing her different things, I found the touch screen was overly sensitive. As I was scrolling through different things (the app list, twitter, facebook), the slightest touch would select/open an item. It normally doesn't do this. It was incredibly frustrating and almost unusable. I pulled it out later and it seems to be behaving like it normally does.
Does temperature affect the NC screen? Where they any touch screen changes in 1.1? Is there a setting to calibrate the touch screen? I can't seem to find one. Any other suggestions?
I tried doing a search on the forum, but the search crashed.
Thanks.
horsemom said:
Is there a setting to calibrate the touch screen? I can't seem to find one.
Click to expand...
Click to collapse
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
I don't know if it's placebo or not, but I feel like this app improved my screen response.
http://forum.xda-developers.com/showthread.php?t=934500
As for the other question, I would expect the screen to be less responsive in cold weather, but I don't have anything to base that on.
Guessing what you experienced was due to condensation on the screen. Doesn't take much and can be 'invisible' to you but the screen is sensitive to 'stuff' on the screen and will become overly sensitive if there is anything on it, like moisture, skin oils, etc .. a screen protector may help but unless it continues that is probably the cause.
tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
What you experience is probably temperature related, but another thing to try is to increase the LCD screen density to around 190, 200, or a little more. For me, I get improved sensitivity, especially near the corners.
My daughter accidentally got a little water on the screen and it was a little erratic. I put it in a ziplock with a handful of rice for about 6 hours and it was like new.
I have owned 3 nook colors, the first one I owned freaked out when I used a damp cloth to wipe the screen. It exhibited some strange behavior and emitted some loud static from the speaker. It would not power down or anything... finally it just went back to normal, so I took it back to B&N and then went and bought one at walmart. I took it back because I thought I wanted the Viewsonic G Tablet. But after trying it I finally bought a Nook Color at Best Buy, bought a screen protector too so that I don't have a repeat of my first NC. The screens on these things are, I believe, rather sensitive and the cold or the moisture may have played a part in your unit's behavior.
migrax
tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
Same here. My screen also seems very inaccurate.
Have you found a fix?
Sent from a NookColor using the xda app
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
tenderidol said:
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
Click to expand...
Click to collapse
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
It's funny, actually... The cold makes your skin less detectable because of vasoconstriction in your fingers as a physiological response to the cold temperature, but a hint of moisture by means of condensation has the opposite effect.
For me, condensation is rarely a problem, but the decreased capillary blood flow effect is quite noticeable.
Sent from my Nexus S using XDA Premium App
One thing that's been mentioned before (and the B&N salesman told me while buying a screenprotector) is that if the screen has a lot of fingerprints, it'll make the nook act weird.
Try wiping the screen of fingerprints.
don_ernesto said:
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
Click to expand...
Click to collapse
Thanks for the reply. Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
tenderidol said:
Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
Click to expand...
Click to collapse
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
don_ernesto said:
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
Click to expand...
Click to collapse
Thanks again for the reply.
Yes, I'd love to take care of it ASAP, since I'm sick of trying to hit a small button on the screen and going somewhere else instead.
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
tenderidol said:
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
Click to expand...
Click to collapse
go ahead! you won't loose any app or any data (not even your progress in Angry Birds)
Of course, before applying this changes i always make a backup. good to have a way back in case something goes wrong
Good test tool
I ran GoJimi's tool, and since then my screen has been flipping out. Typing anything is a good test...I enter one key like "z", and get 2 - "zm". Utterly maddening.
A good tool to see what's going on is "Mutitouch Test" from JerryW in the market.
When I press with one finger, I see a "phantom" 2nd point jumping around. Very quick way to see 1) how good tracking is and 2) if there's any random inintended multitouch action happening.
My stock Touchpad has a weird color problem. Anytime there is some shading/gradient type effect, red/green/blue hues appear. Solid colors seem fine but when I try to watch something like a movie...every person looks like Obama's HOPE poster. Even the normal grey backgrounds of the UI/Cards look like they are running in some 8bit mode or something.
HP live chat previously ASSURED me it is not a hardware problem but rather a software problem. I have done all the updates/factory reset/etc. Nothing has improved. Has anyone seen this type of problem? Is there a 8bit color switch somewhere? Thanks for reading/any help!
I attached a tiny low res pic of the problem. The problem is pretty obvious
Does it work correctly in WebOS? That would tell us if it is a cm problem or a hardware problem. Boot over to WebOS and try watching a movie. I haven't heard of this being a cm problem.
drmarble said:
Does it work correctly in WebOS? That would tell us if it is a cm problem or a hardware problem. Boot over to WebOS and try watching a movie. I haven't heard of this being a cm problem.
Click to expand...
Click to collapse
It doesn't even have CM on it. I'm actually wondering if I flash android on it...it'll get fixed. Will give it a try when I have more time but might just try to call warranty on it. My warranty has passed 1 year but hopefully my credit card company should cover it. I'm thinking I should try that first before wasting time on flashing.
Such a weird problem that has stopped me from using/enjoying my TP
Its hard to even tell what the problem is in your picture. But is your screen discolored in that one spot or is the whole screen discolored? I've never heard of a software issue causing that. And if it was a software issue, running the webOS doctor should have fixed it. So if its still under warranty, i'd go that route first.
jsgraphicart said:
Its hard to even tell what the problem is in your picture. But is your screen discolored in that one spot or is the whole screen discolored? I've never heard of a software issue causing that. And if it was a software issue, running the webOS doctor should have fixed it. So if its still under warranty, i'd go that route first.
Click to expand...
Click to collapse
The issue is the entire screen. The picture is supposed to be mainly dark grey/grey/white. The blue/green tints pretty much appear wherever there is slight color gradients. Its quite obvious on non-solid colored UI and skin. It looks like basically watching a person while on acid.
Anyone know if its possible to have a faulty GPU or something on it and still boot up? The TP does feel sluggish in other aspects as well...open up just a few cards and it becomes pretty damn sluggish. Doesn't even have to be a web browser card...something simple like calculator can sometimes cause problems...
saiko* said:
The issue is the entire screen. The picture is supposed to be mainly dark grey/grey/white. The blue/green tints pretty much appear wherever there is slight color gradients. Its quite obvious on non-solid colored UI and skin. It looks like basically watching a person while on acid.
Anyone know if its possible to have a faulty GPU or something on it and still boot up? The TP does feel sluggish in other aspects as well...open up just a few cards and it becomes pretty damn sluggish. Doesn't even have to be a web browser card...something simple like calculator can sometimes cause problems...
Click to expand...
Click to collapse
If its your whole screen, it could be that your screen is messed up. If you have the warranty still, I'd see if you can get it replaced.
Hello.
Just bought this terminal, D410, and when luminosity is 0% or close there is a little but noticeable flickering on the screen. It's better seen with a white background.
I read some LG phones had this issue, can you confirm it happens with yours, if not I'll just try to replace it.
jesuita said:
Hello.
Just bought this terminal, D410, and when luminosity is 0% or close there is a little but noticeable flickering on the screen. It's better seen with a white background.
I read some LG phones had this issue, can you confirm it happens with yours, if not I'll just try to replace it.
Click to expand...
Click to collapse
looks like that is normal, mine does the same, i was wondering if it was only me, but now i know i am not alone
besides that the phone is great so no complaints
Ahhh and mine is an L90 ( D415)
so looks like that "issue" happens across similar models
Yeah, I thought so. Looks like G2 has the same problems.
The flickering is minimal so I won't bother too much. I can always use screen filter
And yeah, this phone is great!
jesuita said:
Hello.
Just bought this terminal, D410, and when luminosity is 0% or close there is a little but noticeable flickering on the screen. It's better seen with a white background.
I read some LG phones had this issue, can you confirm it happens with yours, if not I'll just try to replace it.
Click to expand...
Click to collapse
That's actually a normal thing to happen, something to do with the frequency at wich the leds pulse to appear "less bright".
Turn brightness up and it will go away.
Hi.
mine also has this problem. For me, it quite annoying, I do not want to use screen filter.
Is there anyone know how to fix it?
Does it happen on non-stock rom (slim, CM...)?
Edit: I have flashed Slim rom. It is great, and I barely see the flicker. In stock 5.0.2, it is annoying, and in Kitkat it is unacceptable for me (I think my eyes are sensitive).
Will anyone try to modify the stock kernel so that the backlight pwm will increase?
nvt992 said:
Hi.
mine also has this problem. For me, it quite annoying, I do not want to use screen filter.
Is there anyone know how to fix it?
Does it happen on non-stock rom (slim, CM...)?
Edit: I have flashed Slim rom. It is great, and I barely see the flicker. In stock 5.0.2, it is annoying, and in Kitkat it is unacceptable for me (I think my eyes are sensitive).
Will anyone try to modify the stock kernel so that the backlight pwm will increase?
Click to expand...
Click to collapse
Which Slim, L or M based? Try using a higher minimum CPU frequency (make sure you pick a governor that allows setting frequencies), I remember reading that it's what made stock Lollipop better regarding screen flickering.
lfom said:
Which Slim, L or M based? Try using a higher minimum CPU frequency (make sure you pick a governor that allows setting frequencies), I remember reading that it's what made stock Lollipop better regarding screen flickering.
Click to expand...
Click to collapse
slim 6.0.1 and cm 12.1. both are almost flicker-free (infact i think i see a little bit, but i dont know if this is just my imagination or not). in both stock 4.4 and 5.0, the flicker is clearly seen.
thank for your information, i will try.
Edit: I have tried with Kitkat v10f. No luck I just dont want stock Lolipop, it is just too laggy compared to Cm 12.1