Sunday, 9 October 2016

Laptop screen colors too dark or red even at maximum brightness

This isn't a programming issue, I just want to make note of the solution that I found for future usage.

I had purchased an Acer laptop a few months back. I have experience with Dell laptops only where I didn't have to do any color calibration. It looked great from the first boot.

However with the Acer laptop I was able to see a significant issue with the screen colors to the point that it was unusable. Dark pixels when playing video were indistinguishable. To add to that screen seemed too red, like skin color was tinted dark unnatural red.

I thought this was due to the brightness setting however the issue persisted even after setting brightness to maximum. I also tried color calibration in Windows personalization settings, but it didn't work. I was convinced that issue was with brightness.

In the calibration settings we can see following image for brightness setting.



When opening this setting on the laptop with the issue in question background and person's coat won't be distinguishable.

I talked to the shop where I purchased the laptop from and they said this was an issue with Acer laptops, so I returned it and made a note to never buy an Acer laptop again.

Laptop had Windows 10 Home OS.

Then I purchased another laptop, it wasn't from Dell again. And I saw the same issue. However this laptop was too nice and I was determined to make it work.

So I finally found a solution after spending hours on the Internet searching for the issue.

The issue is with Gamma setting. This setting determines the maximum brightness of the laptop screen.



By default on Windows 10 its set in the middle of the slider. Which works for Dell laptop out of box without changing it.

However with laptops where default maximum brightness is not good enough this setting can be changed. So I pushed the gamma slider towards top and issue was resolved. This surprisingly also took care of the issue of too much red saturation in the images.

Friday, 25 March 2016

CXF Warning : class xyz has no JAX-RS Path or HTTP Method

Ok, it's been a long time. I have faced too many issues and got solutions for quite a few of them. I don't think I have time to log all of them properly so I'll just put them in minimum words here and if I ever get some time I'll properly format these entries.

I was working with CXF Rest services and I just could not figure out why my service was giving 404. Other service with virtually same configuration were working and some were giving flat out 404.

After taking a look at logs I found that for these services (404) there were entries like class xyz doesn't has no JAX-RS Path or HTTP Method.

I was trying to find the differences between the working and non working services. Every service had an interface and implementation class. Annotations were applied to the interfaces. Almost everything looked normal.

Then I finally saw that some of the JAX RS annotations were present in the implementation classes for the services giving 404. As soon as I removed them, Viola! it worked like magic.

After all this work and searching I was thinking why would you do this to me ( CXF ?).

As it turns out if a concrete REST class contains any REST annotations then it's super class/interface is not scanned for annotations.

I can almost swear that it worked for older versions of CXF, anyway all is well if it ends well.

CXF version used : 3.15