Related
One gripe I have with my Nexus One is the inaccuracy of the colors on its screen. They appear oversaturated esp. with the reds.
Is there a fix for this or will it be possible that a firmware update may fix this in the future?
My understanding is it could be trivially fixed with a firmware update. I think the reason none of the modded/third-party kernels have done is is because it would require special colour measurement equipment, and (given that the technical docs for the AMOLED are not publically available) quite a bit of patience.
See http://android.git.kernel.org/?p=ke...74950cb35551;hb=refs/heads/android-msm-2.6.32
-- you can see the RGB gamma tables. Tweaking these should be able to change the saturation, colour balance, colour temperature, and theoretically (mostly due to changing the color temperature) improve brightness and display life.
One disadvantage of AMOLEDs at this point in time [since they are relatively new] is the software isn't exactly up-to-date with the hardware... and like @hugonz, we need to have info abt the hardware to tweak the software...
craigacgomez said:
... and like @hugonz, we need to have info abt the hardware to tweak the software...
Click to expand...
Click to collapse
That's not exactly what I said; it would be easier with hardware documentation, but the table looks pretty self-explanatory to me (for each brightness level there is a 7-point gamma curve for each of the R, G, and B components). I haven't yet rooted my phone but it's something I'll definitely look at doing once I start working on kernels (assuming no-one else does it first). Maybe I should try plotting the curves to see if that would inspire any kernel devs to try hacking on this issue now.
@hugonz, I understood ur point... but for us it's more a trial and error effort... and different AMOLEDs probably have different tweak values...
Well I hope it gets started as soon as possible.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Now that Android can be installed from NAND, I had assumed that the problem with the screen only displaying 65k colors would be fixed. It still isn't, is there a known way to fix it or any progress being made to fix it? At the very least, is it known what the issue is? I thought it was a problem with WM utilizing only 65k of the screen and that carried over to android when it was run over WM, but now that WM is eliminated that's obviously not it. Anyone know?
Sent from my HTC HD2 using XDA App
ShotSkydiver said:
Now that Android can be installed from NAND, I had assumed that the problem with the screen only displaying 65k colors would be fixed. It still isn't, is there a known way to fix it or any progress being made to fix it? At the very least, is it known what the issue is? I thought it was a problem with WM utilizing only 65k of the screen and that carried over to android when it was run over WM, but now that WM is eliminated that's obviously not it. Anyone know?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
someone correct me if am wrong but is the screen hardware it self only capable of displaying 65K.
jagger2k said:
someone correct me if am wrong but is the screen hardware it self only capable of displaying 65K.
Click to expand...
Click to collapse
There was a discussion about this back in 2010: http://forum.xda-developers.com/showthread.php?t=807307
Some say its 262K. Others 265K or 16M. It's all very vague.
According to Microsoft its 262k
http://www.microsoft.com/windowsphone/en-us/buy/6/phones.aspx#detail=1366
I hope someone sheds some light on this, gradients look awful on my screen.
shadiku said:
I hope someone sheds some light on this, gradients look awful on my screen.
Click to expand...
Click to collapse
Seriously, it's the only thing holding me back from using this phone full-time. You can see a great example of it in the widgets.
I agree, widgets look terrible, specifically news and weather widgets (genie.apk), power control, etc (anything with the black gradient background).
However, they only look bad on some launchers (on launcher pro, for example, with high quality scrolling turned on, widgets look exactly how they are meant to look - somehow launcher pro manages to 'smooth' the gradient).
I think this should be made a priority as the banding is very visible in many apps, and especially when watching videos on the device. It is very noticeable in the new gingerbread ROMs, which make use of more subtle gradients (take the notifications bar, the phone application for example) - fixing this issue would bring android on the HD2 up to a whole new level!
I'm going to do some digging and see what I can find...
i dont think we can improve the screen to much higher than what is meant to be.if you have a normal plasma tv.you cant watch 3d movies from it,because it was not intended for 3d.same thing with the hd2 screen.
justwonder said:
According to Microsoft its 262k
http://www.microsoft.com/windowsphone/en-us/buy/6/phones.aspx#detail=1366
Click to expand...
Click to collapse
But isnt that always MS's way of looking at things, being conservative opposed to using the capabilities? MS has never used anything to its fullest capacity, they are always on the reserved side so to them less means better compatibility and less issues. I wouldnt go based on MS's articles or opinions, I think the best to answer the screen capability would be HTC - the maker.
But thats just my opinion.
For me, some sense builds look more colorful than others do.
is it possible that these builds make use of the displays capability?
Cause when I use Froyo everything seems to be paler and less colorful.
And its not just the wallpaper..
This is a concern of mine aswell, I hope it really is not a hardware limitation
Sent from my HTC HD2 using XDA App
MS said that LEO suqqort 262k.
Sent from my HTC HD2 using XDA App
I thought that limitation was just because that's all WM6.5 could handle. I'd be surprised if the screen couldn't handle 16.7million colours. It's just a standard TFT device after all.
Perhaps it comes down to drivers?
jonboyuk said:
Perhaps it comes down to drivers?
Click to expand...
Click to collapse
Maybe it was regulated somewhere in IPL or SPL? Because we just use IPL, SPL and radio to boot android...
Ok, so there are quite a few threads about colour banding, 4 or 5 I think. All/most saying different things, sometimes the same things in different ways
Neways, although I really didn't want to add to it, I wanted to show everyone a few things about android colour.
Note: In order to really do these tests you need to set brightness to 100% so there is a common mark from which to draw any conclusions.
I believe the following:
1. It's apparent that super duper amazing amoled plus and then some Shows more detail (maybe due to sub pixel processing nature of the screen).
2. Due to point 1. and added to the fact that by default and quite often chosen by developers that most apps are set to use the 565 mode (5bits red, 6bits green (human eye sees more green) 5bits blue) or 16bit mode for performance reasons. With this we see banding in some colour transitions (More so green)
3. There are many bitmaps/images/textures that have been palletised in conversion and compressed for in-app performance reasons. This also produces artefacts that can be seen on our wonderful displays
So in collusion to those points it quite impossible to say banding is a software problem or hardware problem unless:
1. You wrote the app yourself and have forced the 888 mode.
2. You compressed the resources (bitmaps etc) yourself and know that they should be perfect while also doing point 1.
(NOTE: you cant just use a browser or image viewer to look at an image and say well that shouldn't look like that without thinking about all of the above!)
Ok so how do we look at these things?
Well 1st off, I'm doing an nice app with a theme framework that uses lots of bitmaps for the default theme, so I put in the ability to change from 16 to 24 colour modes, so I can allow users to pick from SPEED or LOOK preference! This shows how both the SGS2 and TAB7 can have banding on a drop shadow, or not:
View example (View the 720p)
Sorry about audio, couldn't be arsed setting up a proper studio mic!
Also sorry about the blur box I HAD to use
http://www.youtube.com/watch?v=8QlnuoNSdXo
OK so a few other tests on your own device
Test 1. UPDATED
Using the attached bandingTestUPDATED
Ok altered this little thing to show 2 photos I took, one of mighty mugs Prime!!! and one of a robin! The app forces 888 mode and allows you to switch images with settings/menu button. It displays at 100% so you cant zoom out or in, you can just view as is. For comparison these are the images in use :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Test 2.
Using the attached xda-gradtest
This is an app that is set to 888 and uses procedural gradients rather than bitmaps (as in the gradient is program generated rather than image based).
What you should see is only very slight banding in low greens due to our eye being very very very good at green colours compared with blue and red. There should be little or no banding on anything else.
More Info / Conclusion:
Well the gradientTest app is the best thing to look at, and the real test, the reason we see more banding on low green is 2 reasons.
The first:
Well we all see sh*t loads more green than any other colour (cause were ace) I recommend you look into human eye perception theory regarding both colour and detail perception as I have had to do over my many years in game console art development (wicked reading ).
Second:
I believe oled screens are not as good as others at low intensity low contrast due to the nature of how colour is processed.
I have many android devices ranging from the crappiest tablets you can buy of ebay, up to the best and even have iphone ipads also. I must say that with a finite gradient in 565 on the crap tablets and lesser displays, it looks better cause they are actually crap (dithered and filter to hell)
The same is true of this display I'm typing on now compared to another I have on my mac pro. One is an IPS pro colour variant of an LCD panel and one is not. Crap looks better on the lesser monitor! But Amazing looks amazing on the IPS pro panel that I HAVE to use for my 3D Graphics, Photography and Video work.
more..
If you plan to use apps that are set to 565, you have to deal with the banding or get a lesser display that just doesn't show it!
If you plan to use lots of apps (24bit)(888) that use low contrast dark green to black transition graphics, you will have to deal with the gradient banding
Alternatively
You could wait till the average target device has a minimum spec like the sgs2 and also a min OS of 2.3.* then probably most apps will have higher colour set and higher fidelity resources (bitmaps etc) in use But as it stands the mass market is much lower spec and the dominant os version is a mix of 2.1 and 2.2 devices
New info
previous to some 2.2 and all 2.1 android os defaulted to low colour if a developer didn't set it. Now in 2.3+ it defaults to high colour if they dont set it.
UPDATE 14 June
As some have mentioned (godutch etc) dnie (Digital Natural Image engine) by samsung is a colour/image processor that could be in use. Having looked at test 1 with the images, there is hardly any banding at all, but just a tiny bit I can see in primes left window. With this in mind and only mildly pissing me off, started to look at ROM and found many different " mdnie_profiles " that are apparently used and have different settings in each profile relating to all the major visual aspects (video, gallery blaaa blaaa)
So gonna have a play (these are in /etc/mdnie_* ) but I dont reccomend ne1 doing this unless you really know what your doing.
SO....
Hope this helps kill lots of thread activity on the same subject across multiple threads where info is getting hard to find and peeps just cant read all of those posts.
As always due to who I am I will say that I could be in part or on a whole wrong on this to any degree, but I believe this info to be correct as of the time of this post and this is only for the purpose of putting a few peoples minds at ease and also as information that doesn't sit 50 posts into some of these massive threads
Wow! I'm not a techie person like you but the way you explained it I kinda get the idea.. I'm very thankful for people like you who share their knowledge to educate us so we can come up with a decision whether to buy sgs2 or not. I'm looking forward to upgrade my Samsung i8910hd to sgs2 come July, and I'm researching in the forums to check the users' feedback as to their personal experience with their new sgs2.
As said above, I'm not a techie (Not as much as the OP anyway ) though am also grateful for people who post up tech info like this.
To the 2nd poster.... Ignore negative comments given by a lot of users, regardless of whatever bugs may be present, the S2 is an amazing phone and you will not be disappointed!
People are too quick too moan, yet don't talk about the plus sides
Thank you for the time and energy you put in to explaining this. It's sometimes hard to participate in certain technical conversations/threads because there are so many moving parts and so many different theories. This thread is refreshing.
But there's still very noticeable banding on 888. Less than 565 but there still is. So the banding problem really exists.
Sent from my GT-I9100 using XDA App
EleCtrOx666 said:
But there's still very noticeable banding on 888. Less than 565 but there still is. So the banding problem really exists.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Read the post and instructions fully, along with expected results!! Cause if your talking about angry birds bg, then I explained that! So no1 knows what your on about unless your precise. I've yet to find a problem with anyones display in this manner, thats not to say there may not be a first, but you have to be clear and read properly, then I would look to do some proper display test apps.
deanwray said:
Read the post and instructions fully, along with expected results!! Cause if your talking about angry birds bg, then I explained that! So no1 knows what your on about unless your precise. I've yet to find a problem with anyones display in this manner, thats not to say there may not be a first, but you have to be clear and read properly, then I would look to do some proper display test apps.
Click to expand...
Click to collapse
I read everything. With Xda Gradtest the green has the banding issue, so yes maybe our eyes are more sensible to it, but that doesn't excuse it & the problem exists, the green banding on a larger scale can be very noticeable.
Sent from my GT-I9100 using XDA App
Well my samsung galaxy tab had the same problem with gradients and it just had a simple lcd display. So I believe the problem lays with samsung as no other device I owned had that issue.
Sent from my GT-I9100 using Tapatalk
I don't know see any banding on my htc desire though, and the gradients look super smooth on it.
godutch said:
I don't know see any banding on my htc desire though, and the gradients look super smooth on it.
Click to expand...
Click to collapse
Cause it dosent have a high colour high detail display like amoled plus, on the galaxy s 2, which is what this thread is for
Sent from my GT-P1000 using XDA Premium App
Thank you deanwray for your work and explanation.
Discussion apart ... what can be done in the firmware (by Samsung) to correct this problem with the actual 16bit "low quality" apps and OS? the OS can be improved, only depends on Samsung, but will we have to wait for the apps developers to give us better IQ in their future releases?
Thanks again!
jvidia said:
Thank you deanwray for your work and explanation.
Discussion apart ... what can be done in the firmware (by Samsung) to correct this problem with the actual 16bit "low quality" apps and OS? the OS can be improved, only depends on Samsung, but will we have to wait for the apps developers to give us better IQ in their future releases?
Thanks again!
Click to expand...
Click to collapse
Well the os supports full 24bit colour with another 8bit for various non-palletized blending modes. Thats just Android, but most of the base functions you see in android are indeed independent apps like phone, calendar, contacts etc.
So the OS is fine.
As for applications, to the best of my knowledge, you cannot force an app to be 24bit mode, but even if you did, as the test app shows with angry birds bg, the source resources (images, textures etc) have to be of a quality that fits.
So in short, nothing to OS, as for apps, ask devs to put more work into them to do different resource graphics and optional 24bit colour mode. 24bit switch is only in my apps cause I'm and artist If I were a full blown programmer I probably wouldn't bother Also the market figures say it would be quite a bit of work for a very very very small percentage of ppl
thanks we will have to await for developers to work better. At leat the apps included by Samsung should be 24 bits !
It's a crime not do do so in a device like S2.
A little off-topic ... as a developer I am I'm currious ... you developed those 2 apps in what language? .net + Android SDK, Basic4Android, ... ?
jvidia said:
thanks we will have to await for developers to work better. At leat the apps included by Samsung should be 24 bits ! It's a crime not do do so in a device like S2.
A little off-topic ... as a developer I am I'm currious ... you developed those 2 apps in what language? .net + Android SDK, Basic4Android, ... ?
Click to expand...
Click to collapse
the two sh*tty test apps are about 20 lines of java using android sdk
The app in the video is a big combo (mess) of everything
I don't get why you're saying that banding doesn't occurs in 24-bit mode if it does occur ?! (talking in general)
EleCtrOx666 said:
I don't get why you're saying that banding doesn't occurs in 24-bit mode if it does occur ?!
Click to expand...
Click to collapse
it does only on low luminance green, but tbh, it's on every display depending on how subjective you are. But the horrid banding ppl talk about mostly is not an issue if resources are good and app is set to 24bit.
deanwray said:
Cause it dosent have a high colour high detail display like amoled plus, on the galaxy s 2, which is what this thread is for
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
It has (I have the slcd version) and gradients are super smooth, anyway something weird is going on, I already posted this earlier:
take a screenshot with home+power and look at the pic on your computer ->banding
take a screenshot with qtadb and look at the pic on your computer -> no banding
godutch said:
It has (I have the slcd version) and gradients are super smooth, anyway something weird is going on, I already posted this earlier:
take a screenshot with home+power and look at the pic on your computer ->banding
take a screenshot with qtadb and look at the pic on your computer -> no banding
Click to expand...
Click to collapse
..and where did you find a S-LCD version of GS II?
I was talking about my desire
a couple of points. the nexus one and other amoled phones all had horrible banding for the last year, till the 2.3.3 update, and now the banding is gone completely. for example the XDA tapatalk app splash screen had banding. once 2.3.3 came out, the xda tapatalk app banding was gone. the app did not change from RGB565 to RGB888, the OS itself was updated with "something" which we arent clear on.
now considering the super amoled plus display has MORE sub pixels than the amoled with pentile sub pixel arrangement, it would be easy to think that banding should be even less on the plus version since there are more pixels for the same resolution.
anyway it still doesnt fully explain why angry birds on a nexus one, or any other phone, doesnt show the banding. but it DOES show banding on the SGS2. its the same app version. also considering the nexus one WAS seeing banding on these apps, but since 2.3.3 update, that banding is now gone, it makes me highly inclined to say this is a samsung software issue.
for fun i installed the test apks on n1, no banding on minimum brightness on RGB_888 on either apk. of course it was there on angry birds background RGB_565, but playing the app itself does NOT show the banding (only thanks to the android 2.3.3 update).
I have installed Paranoid Android on my Note and noticed that there is severe clipping in the CM9 UI elements. Even the default ICS wallpaper , the one with the"rainbow" coloing stripes show severe clipping on the lockscreen. It looks just plain ugly. And since most of the CM9 UI backgrounds are a shade of grey, there is severe clipping of these grey elements to a purplish pixellation and to black. You can notice this if you take the settings page in Paranoid android or any other CM9 based ROM (assuming most CM9 based ROMS have the same default theme) Look under the status bar where the grey background fades to black and you may notice severe pixellation like issues at that area. Now, go to advanced, screen settings and MDNIE mode, you will notice that the clipping keeps changing when changing modes but its still there in every screen mode.
How many of you are experiencing this? Assuming a majority of the people who run Custom ROMS run a CM9 based ROM, why isnt this issue reported anywhere? I'm asking because, the issue is plainly visible in these grey areas and UI elements making the visual experience really bad. And why is Gamma Control disabled in these CM9 kernels? I believe lowering the gamma would solve the problem.
I've noticed that CM9 kernels have the worst clipping whereas in other stock based kernels, the clipping is comparitively lower, closer to the stock kernels.
So once again users of CM9, please do report if you face this issue.
CM9 users please report back because I havent seen anybody talking about this issue in any of the CM9 related ROMS thread. People seem to ignore an issue which stares back right at the face even in ambient lighting. Why havent this been reported?
I dont have much idea about who develops CM9 kernels for the note. How can we contact the CM9 developers and let them know of this issue and request to enable Gamma Control within the kernel?
Somebody please help me out here. Because its been a month after I bought my note and I've been struggling and doing my best to find a solution to this horrible clipping. I had got in touch with GSMArena and got this issue published, yet Samsung never responded, I tried kernel after kernel and realised that the intensity of the issue varies from kernel to kernel. I've seen that whomever I ask about the clipping in this forum says they have it but then everyone seems to be happy running different ROMS and in these CM9 based ROMs which look as close to stock Google ICS UI have severe clipping all over the UI and yet people dont seem to bother.
So what can I conclude from this? Is this an isolated issue or are all of you Note users who have this issue just keeping silent and living with it?
I do not mean to spoil anybody's peace or anything. I clearly dont know how to get in touch with the CM9 devs for the Note, somebody help me if possible. And if you feel that this is an isolated issue, do let me know otherwise. Because, when the basic UI shows severe clipping, the whole user experience is spoiled and nobody wants to live in fear with bright UI elements and bright wallpapers dreading the clipping if anything at all has to be dark. We paid a premium for this device and even Samsung seems to ignore. I have the SGS3 and there is no clipping on it but just that everything seems darker on the GS3 when compared to the Note. This alone shows that Gamma is a culprit here and I could just sell away my Note and just live with the GS3. But that doesn't help anybody who is facing this issue and wants to see a solution. Even I personally like the note more than the GS3 and I want to keep it but for this issue. Not everybody has the money to jump to the next flagship every now and then and for the people who spent their money on the Note doesn't have to "live with it" just because they decided to buy it without knowing such an issue existed. Not every store lets you try and trial their devices before buying them.
Samsung has even seemed to ignore the EMMC issue even after claiming they are "working on it" I dont see anything productive from Samsung's side as even a device which was previously unaffected had the affected kernels pushed to it via an update. So basically if it was not for people like Entropy who works day and night for that issue, Samsung could keep replacing motherboards for every random wipe a user does. They basically want to sell the note until the Note 2 and then this wouldn't be their problem anymore. Problems like the emmc bug is a MISTAKE from Samsung's part and they should be ready to repair devices even beyond warranty as the user may have only done the most harmless thing, i.e to reset the device to factory settings.
So, coming back to topic, how do we get in touch with the CM9 devs and enable gamma control on these ROMs? Most ROMS have gamma control under MDNIE settings which is greyed out, most probably because the kernel doesnt support it. This is the best I can do for the people who are affected by the clipping issue as I'm not a developer. This issue isnt an isolated case in my opinion and affects every Note I've got a chance to see.
It might help if you actually posted requests in the cm9 discussion thread? #commonsense
Seriously after reading TS long posts still*cannot figure out his problem
please post shots to show your issues
I have been using CM9 roms since build 2 and do not seem to notice such issues or maybe i am blind ?
mobile88 said:
Seriously after reading TS long posts still*cannot figure out his problem
please post shots to show your issues
I have been using CM9 roms since build 2 and do not seem to notice such issues or maybe i am blind ?
Click to expand...
Click to collapse
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Entropy512 said:
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Click to expand...
Click to collapse
Oops..I'm sorry for the long post. Its basically about the severe "black clipping" which has been affecting the Note since release. This issue is best seen when displaying dark shadows in images and videos. There were many threads discussing this issue. And GSMArena had published this issue in their news after I mailed them about the same.
What I wanted to tell was, I feel this is caused by the Note's screen having the gamma cranked up quite high and I believe lowering the gamma would resolve this issue.
The default CM9 theme shows severe clipping in backgrounds and UI elements. All the grey backgrounds, (the default theme) clip to black just below the status bar.
Even all the videos which have dark shadows are totally blocky due to this and the clipping makes them literally unwatchable.
I had reported this issue to GSMArena
http://www.gsmarena.com/samsung_galaxy_note_plagued_by_display_issues-news-4513.php
I wanted the Gamma Control feature which is presently disabled to be enabled in the CM9 kernels so that we can tune down the Gamma to eliminate this clipping
The same issues existed on the GNexus and was fixed with the Lean Kernel which had Gamma Tuning.
So once again, in short, I'm talking about the "Black clipping\crush" on the Note when displaying darker shades of colours.
All the notes have this problem, and we need to access to gamma control but as supercurio said it won't solve all the problems of the black clipping and banding issues
Sent from my GT-N7000 using xda premium
Satishp, i know what are you talking about. Just take a picture of your note and post it here. Of course, you won't use a screenshot feature but a camera.
I sold my note bc of the black clipping issue, but now I cannot buy an s3 or HoX cause their screens are just to small, that is, narrow. Gonna buy Note again and hope some solution will come out. It is too bad to buy a phone for its screen and get a crappy quality. Issue on s3 is solved with lowered gamma. Comparing with the Note, s3 has much darker screen. Sometimes too much.
Entropy512 said:
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Click to expand...
Click to collapse
It's a very real issue affecting EVERY Note, derp
NotablyNice said:
It's a very real issue affecting EVERY Note, derp
Click to expand...
Click to collapse
http://www.gsmarena.com/samsung_galaxy_note_plagued_by_display_issues-news-4513.php
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Same. I don't often stare at my phone from a distance of 3cm to see any imperfections.
Sent from my GT-N7000 using xda premium
All of the speculation and misinformation of this issue is really starting to get frustrating. First, the issue IS with the hardware. It may be possible to reduce it's impact using software but the fact remains this is a hardware issue. How do I know? I have replaced my Note's screen and the newer screen I have isn't as good as the old one.
The new one isn't awful, it simply isn't as good as the other.
2nd point - everyone will have this issue. It is simply an inherent problem with the screen hardware and it is completely implausible that there are 1 or 2 'perfect' screens out there. There will simply be variations. Some people WILL have better screens than others. For some people the issue may be completely unnoticeable and for others it will be glaringly obvious. Don't judge or hate on people because their screen is worse than yours and vice versa.
3rd the issue is MORE noticeable at lower brightness values than high brightness values. If you have your note on higher brightness values then you're unlikely to notice it. In my case, I can not see any clipping if I am in a lit room. The only time I can see it is when I'm sat in the dark with very low brightness. As I said above this will vary from person to person.
I have attached 2 photos below. One is a normal exposure where you can see the clipping is hard to see. Another is a long exposure which amplifies the issue more and makes it more noticeable (I used a longer exposure on my camera to show this). Fortunately it isn't so bad for me, but for some people my long exposure image is the reality unfortunately.
Standard: http://i48.tinypic.com/4uxnia.jpg
Long Exposure: http://i48.tinypic.com/5akew3.jpg
Why have we got a clipping problem and can software solve it? I believe it is highly unlikely that this issue can be solvable. I also think the issue stems from one simple shortcoming to the screen; the minimum brightness achievable per pixel. The problem is the jump from this minimum brightness to the 'off' (perfectly black) pixel is too great. There is no transition. Can gamma control solve this? I'm not convinced. I think the issue is more to do with what the lowest pixel brightness the screen is capable of. For the poorer people this minimum brightness will be quite bright. For others the minimum brightness will be lower.
If any devs know of a way of controlling pixel brightness on a level where it can be noticeably changed and if it is possible to reduce this minimum brightness then sure, it would certainly be a possibility. But I don't think this is possible.
Part of this might be a limitation of the HD Pentile AMOLED technology. But if you notice, both the Galaxy Nexus and the Galaxy S3 share the same technology. For people who argue that the S3 uses a different manufacturing procedure, Samsung has no where mentioned this and its just an assumption.
The GNexus had the same issue but was solved with the LEAN kernel which implemented a gamma control within the kernel. If you've seen the S3's screen ( I own an S3 too, So I've spent a good time comparing), you will notice that the S3's screen is visibly darker than the Note's screen. Images tend to look darker and this shows that the S3's screen has its gamma set to a lower value which eliminates the clipping.
More proof for you, lets take the gammatest image and view it on our PC. Most PCs use an LCD display and still you can see the greys gradually fading to black.
Now increase the gamma of your display from your display adapter's color settings and view the same image again. You will see that you can see all the way upto 1 and then black just like how the image is displayed by the note.
http://forum.xda-developers.com/showthread.php?t=1800117
Now view a 720p or 1080p clip on your PC with the gamma values still high, you will see the clipping in every dark scene. Try it yourself.
This shows that gamma calibration can correct the issue to atleast some extent.
Hmm. There appears to be truth in what you say. Unfortunately the Note is lacking somewhat in the developer department. And the few devs there are have other pressing issues to deal with so the question becomes who can implement gamma control on the Note?
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Yup. Despite being pentile, compared to my I9100/I777 the screen is even more gorgeous.
I'm on minimum brightness nearly all the time. No clipping issues whatsoever.
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Yup, and it's even better when you switch the screen mode to "Dynamic" (Advanced Settings).
Sent from my GT-N7000 using xda premium
I have the clipping regardless of which mode I put it in, apart from the clipping the screen is mint, which makes me even more pissed off when I watch a movie and a dark scene comes on, then the shade between black and grey turns into a lego block mess. I really cant beleive so many people are happy with it, half of u guys must be blind, I exchanged my Note twice, tested my cousins and my bosses Notes, all have the exact same problem. I even bluetoothed the gamma test image to a few in carphone warehouse , same with them, even the samsung rep I spoke to over the phone said the one they have in the office also has the issue. Total crap imo, Samsung total FAIL.
Entropy512 said:
Yup. Despite being pentile, compared to my I9100/I777 the screen is even more gorgeous.
I'm on minimum brightness nearly all the time. No clipping issues whatsoever.
Click to expand...
Click to collapse
Actually use your Note and go watch a dark movie... It's there
NotablyNice said:
Actually use your Note and go watch a dark movie... It's there
Click to expand...
Click to collapse
I've watched plenty of dark movies... As good as if not better than my I9100/I777.
Entropy512 said:
I've watched plenty of dark movies... As good as if not better than my I9100/I777.
Click to expand...
Click to collapse
Please take a picture if your note displaying the gamma test image (blocks numbered 1 to 20) with stock gallery app in a dark room, screen mode dynamic, max brightnes with auto adjust switched off, I bet number 4 is light grey, then number 3 is black, if so your device has black clipping. There should be no abrupt drop from grey to black, it should be a gentle fade.
Thanks.
So I saw this in the build prop
"qualcomm sensors enable
#
# LGE CHANGE_S, 2013-10-29, [email protected]
# below sensor is default true by HAL source.
#ro.qualcomm.sensors.qmd=true
#ro.qc.sdk.sensors.gestures=true
#ro.qualcomm.sensors.pedometer=true
#ro.qc.sensors.step_detector=true
#ro.qc.sensors.step_counter=true
#ro.qualcomm.sensors.pam=true
#ro.qualcomm.sensors.scrn_ortn=true
#ro.qualcomm.sensors.smd=true
#ro.qualcomm.sensors.game_rv=true
#ro.qualcomm.sensors.georv=true
# LGE CHANGE_E, 2013-10-29, [email protected]"
Not sure if anything there can help, but I know that the sharpening is applied when there's something light on a dark background or vice versa and also if you have any type of floating menu it'll sharpen everything in the background.
Samsung does this as well but as far as I know only in multi window mode.
Its not a screen issue as its not always apparent. And as far as I know the oppo find 7 has the same panel and doesn't exhibit these effects.
So anyone have any ideas?
Kernel related ?
Display drivers?
Maybe we should all email lg and ask them for an option to remove it.
Just fyi oppo use japan display inc panel while lg use their own panel
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
daleski75 said:
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
Click to expand...
Click to collapse
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Lostatsea23 said:
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Click to expand...
Click to collapse
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
daleski75 said:
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
Click to expand...
Click to collapse
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Lostatsea23 said:
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Click to expand...
Click to collapse
When it finally rolls out to the USA then I think it will get better dev support.
I'll have the device soon, but I'm not sure we're able to turn it off since it may be the part of the driver. Haven't done it yet, but if we can debug the running code and binary patch the trigger effect into not signaling, we may fix it. If it IS a trigger at all; e.g. we should find when it does signal the driver/gpu to apply sharpening and just switch code from JE to JNE or similar to kill the trigger and never apply it.
Theoretically.
Hopefully LG can turn it off and not a hardware combo issue with the 801 and this particular display tech.
It can be turned off. They purposely added it
Lostatsea23 said:
It can be turned off. They purposely added it
Click to expand...
Click to collapse
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Lostatsea23 said:
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Click to expand...
Click to collapse
Well, I don't believe a whole bunch of smart engineers, designers and such in dev and QA would not notice it sucks...
And for screen modes, after so much hassle, I hope and expect LG is preparing us a "turn bloody thing off" setting...
Well once it comes out in the states I will be contacting some devs about it. We need a boot loader unlock as well though
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
flaring afro said:
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
Click to expand...
Click to collapse
They're dumb because it makes it look worse. In almost positive a fix will be found. If anything maybe the carrier releases will have this fixed already.
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
haris182 said:
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Nope. Exactly the same. Placebo
Sugar pills taste so good
rushless said:
Sugar pills taste so good
Click to expand...
Click to collapse
Lol. If an update to remove this isn't out in the next couple weeks. Bye bye G3