Any idea when this will get pushed out to stable? I just upgraded to 68.0.3440.87 (Official Build) (64-bit) this morning and am not able to use my external Dell monitor at its native resolution. If I go to a different resolution the colors are fine but the resolution is very much less than ideal. I'm using an Asus C302 and a USB-C hub with an HDMI output.

I just got an update on the stable channel and was hit with this very same issue.  Going into flags and disabling night light fixed the issue.  

I upgraded to 68.0.3440.87 (Official Build) (64-bit) two days ago and since then I cannot use my external Samsung C27F591FD monitor at its native 1920x1080 resolution. If I lower resolution by one or two notches the colors are ok but such a setting is not usable for my work. I am using HDMI output on my Acer Chromebook 14 for Work (CP5-471). Turning off the night light flag (#ash-enable-night-light) and rebooting doesn't fixed the issue. Re-enable the Night Light flag and turn off the #use-monitor-color-space flag doesn't fixed the issue.

Hi! This issue affects several thousands of users in our organisation.
I have tested our two devices which we have: Asus C302C Noteebook PC and hp Chromebook x360 11 G1. We have the latest available version for our devices: 67.0.3396.101 and I have tried the latest beta - same issue.

Flag: Night light enabled does not help. Neither does different resolutions or mirrored/extended display settings or which adapter I have (I have tried two very different brand new ones).

Any type of workaround would be deeply appreciated. And also let me know if I can help out testing stuff. Thanks.

I forgot to mention (very relevant, sorry) that this happens on TVs. In this case a Samsung TV (see attached image - the above image is on the Chromebook screen and the one below is the TV).
We cannot reproduce this problem on a normal PC monitor.

It does not work with these two: 
https://www.kjell.com/se/sortiment/dator-natverk/datortillbehor/usb-tillbehor/usb-adaptrar/adapter-usb-c-till-hdmi-p69198

https://www.startech.com/AV/usb-c-video-adapters/usb-c-hdmi-adapter~CDP2HD

We can also see that it works on more advanced adapters (than the usual, simple USB-C to HDMI) like this one: https://www.kjell.com/se/sortiment/dator-natverk/kablar-adaptrar/usb/usb-adaptrar/multiadapter-usb-c-till-hdmi-p96544

Deleted: houston_we_got_a_problem.png 1.2 MB

	houston_we_got_a_problem.png 1.2 MB View Download

M-67 should not be affected by this issue, it must be a different bug.

If the issue you're referring to in comment #82 is the problem, then it seems to be something else. 

+Adding some more graphics folks.

For issue in #82, see issue 870518.

Same issue, EXACTLY!  This has ruined my productivity. I received the Aug 10 update today, and right after, I experienced this washed out color problem. I'm on ACER 14 Chromebook AND ACER monitor. One thing others don't say is that my toast screens says a crazy resolution 1842x1079 (see attached photo), not the native resolution it is set to. I don't even have these resolutions as selections on either the book or the monitor. WTF? This is so messed up, guys! Really fucked me as we only use chromebooks at work!

see my crbug 875501 for all my system details.

Deleted: Screenshot 2018-08-17 at 7.08.40 PM.png 154 KB

	Screenshot 2018-08-17 at 7.08.40 PM.png 154 KB View Download

actually here is my info from cbr 875501


Chrome Version       : 69.0.3497.35
OS Version: 10895.21.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. plugging in ANY monitor to chromebook
2.
3.

What is the expected result?

plug in monitor, start working like always.

What happens instead of that?

extends screen to 1824x1079 when both chromebook and monitor resolutions are set to 1920x1080. makes the extended screen worthless. cant see anything. all washed out. cant work like this at all on MY PRIMARY WORKBOOK. see the toast in the screen shot. WTF?  It never did that before the update.

Same issue for several guys on my team.

Same issue here again, it was fixed in 68 and the bug came back even worse to version 69 and Canary (70) has the same bug.  Someone please check this out, we use these laptops with external screens and can not use HDMI at the highest resolution settings.  I have tried all toggles, only 67 works but does not have the settings for a UHD monitor.  Going to a dongle with Display Port was my only option and thank God the monitor supports that.

dcastagna@, I'm also seeing this on latest image on caroline (10968.0.0-18.08.14)
Could be another regression, or could be another issue exhibiting the same
problem.

Could you please look into this?

Yeah this is now affecting everyone on my team who has restarted and ended up on this version:

Version 69.0.3497.35 (Official Build) beta (64-bit)

External screens are washed out to the point of being unusable. We have to fall back on just using the laptop screens for now which is very productivity limiting. There's no way for users to manually adjust gamma settings to try and temporarily resolve this? At least not that I can find.

I can provide additional details just let me know what is useful.

daniellewis@ and others, could you please try connecting the external
monitor with the flag chrome:flags#use-monitor-color-space set to 
Disable? We landed that in M67 to read the colorimetry parameters of
the external monitor, but it also reads the gamma value.

@comment91 @mcasas@chromium.org

Did nothing for me.  Still washed out on any external monitor used.

Am also on Version 69.0.3497.35 (Official Build) beta (64-bit) and encountering the same problem on an external Samsung monitor. 

Problem seems to only happen with the highest screen resolution - 1920x1080 (60 Hertz). Going one resolution lower - 1680x1050 works fine.

Tried the suggested chrome flag setting in Comment 91 - improved things a bit, but still washed out and unusable.

Take a look at the code in 68.x - I know it got yanked as a whole but that version worked correctly.  I just changed the flags as per comment 91 and did not make a difference.  It almost seems when you max out the settings for the resolution it goes all bonkers and sets the output much higher than it should.

+spang@chromium.org, +dnicoara@chromium.org, 

I suspect this commit didn't actually help: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/1d19a15f6d57f0d43429cd89bcd79983f7285990

And this revert is the one that caused it to regress: https://chromium.googlesource.com/chromium/src/+/d6f31cebe469cef13f081b8cef0c20e6677a29b3

We should probably reland the above CL as a temp solution until marcheu@ and dcastagna@ come back from their OOO.

abodenha@ FYI.

We have started to see this issue in beta 69.0.3497.35, on an asus 302 chromebook, on resolution 1920x1080 (60 Hertz), dropping 1 resolution resolves the washout seen. 

It seems like this is affecting a lot of people. Thanks for looking into this and working on a fix.

I have a few questions:
1. Do we know which version introduced this regression?
2. Which channels are currently affected?
3. Are there any known workarounds?
4. Is there an ETA for a fix? (if so, what are the ETAs for the different channels?)

sorta-workarounds:
 - Changing display resolution to 1920 x 1200 (60 Hz) makes the problem go away (but makes my 4K panel blurry). Some resolutions have the problem; others don't.
 - Enabling night mode and setting color temperature all the way to "warmer" makes it easier to see stuff that's washed out, but it also makes my monitor super yellow

If it helps, I have an Asus C302CA running 69.0.3497.35 (beta channel) that exhibits this issue (only on an external monitor; internal display is perfect) when running at 3840 x 2160 (30 Hz). 1920 x 1200 (60 Hz) is OK; 1920 x 1080 (60 Hz) is bad.

Thanks!


--

chrome://gpu:

Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Hardware accelerated
Out-of-process Rasterization: Disabled
Hardware Protected Video Decode: Unavailable
Rasterization: Hardware accelerated
Skia Deferred Display List: Disabled
Skia Renderer: Disabled
Surface Synchronization: Enabled
Video Decode: Hardware accelerated
Viz Service Display Compositor: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
decode_encode_srgb_for_generatemipmap
disable_discard_framebuffer
msaa_is_slow
rely_on_implicit_sync_for_swap_buffers
scalarize_vec_and_mat_constructor_args
Problems Detected
Protected video decoding with swap chain is for Windows and Intel only
Disabled Features: protected_video_decode
Framebuffer discarding causes jumpy scrolling on Mali drivers: 301988
Applied Workarounds: disable_discard_framebuffer
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Mesa drivers in ChromeOS handle varyings without static use incorrectly: 333885
Applied Workarounds: count_all_in_varyings_packing
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Decode and Encode before generateMipmap for srgb format textures on Chromeos Intel: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Avoid waiting on a egl fence before pageflipping and rely on implicit sync.: 721463
Applied Workarounds: rely_on_implicit_sync_for_swap_buffers
Don't expose disjoint_timer_query extensions to WebGL: 808744
Viz service display compositor is not enabled by default.
Disabled Features: viz_display_compositor
Skia renderer is not used by default.
Disabled Features: skia_renderer
Skia deferred display list is not used by default.
Disabled Features: skia_deferred_display_list
Version Information
Data exported	2018-08-21T05:17:07.712Z
Chrome version	Chrome/69.0.3497.35
Operating system	Linux 10895.21.0
Software rendering list URL	https://chromium.googlesource.com/chromium/src/+/ebd60c91b0e2df29a6a90e2ea298b82f89dc834f/gpu/config/software_rendering_list.json
Driver bug list URL	https://chromium.googlesource.com/chromium/src/+/ebd60c91b0e2df29a6a90e2ea298b82f89dc834f/gpu/config/gpu_driver_bug_list.json
ANGLE commit id	35a0888481f6
2D graphics backend	Skia/69 f4bd5f148c150c7ffe73bdf1aa6f9d565c0c2125-
Command Line	/opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=30.0.0.142 --ui-prioritize-in-gpu-process --use-gl=egl --enable-native-gpu-memory-buffers --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --login-profile=user --has-chromeos-keyboard --enable-touchview --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --child-wallpaper-large=/usr/share/chromeos-assets/wallpaper/child_large.jpg --child-wallpaper-small=/usr/share/chromeos-assets/wallpaper/child_small.jpg --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --enable-consumer-kiosk --arc-availability=officially-supported --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-user=brc@google.com --login-profile=515661690ead7079db016b35758a1f88a69511fe --flag-switches-begin --flag-switches-end --policy-switches-begin --isolate-origins=https://appspot.com/,https://chromium.org/,https://googleapis.com/,https://googleplex.com/,https://googlesource.com/,https://youtube.com/,https://google.com/,https://withgoogle.com/,https://googleacquisitionmigration.com/,https://googleusercontent.com/,https://googleprod.com/,https://nest.com/,https://myworkday.com/,https://chromiumapp.org/,https://lucidchart.com/,https://service-now.com/,https://concursolutions.com/,https://salesforce.com/,https://gcorppartners.com/,https://morganstanley.com/,https://schwab.com/,https://qualtrics.com/,https://ultipro.com/,https://google.secure2-enroll.com/,https://googlegroups.com/,https://google.secure.force.com/,https://ebenefitsnow.com/,https://firebase.com/,https://elo.plusrelocation.com/,https://anthem.com/,https://g.viapeople.net/,https://gdjap.com/,https://asana.com/,https://perquisite.net/,https://postini.com/,https://perkhub.com/,https://gstave.us/,https://geolearning.com/,https://lecorpio.com/,https://inverify.net/,https://preceda.com.au/,https://secureacceptance.cybersource.com/,https://solium.com/,https://fgvms.com/,https://withgoogle.com/,https://ridecell.com/,https://tds.ie/,https://sprinklr.com/,https://smartsheet.com/,https://fieldglass.net/,https://dochub.com/ --policy-switches-end --vmodule=*arc/*=1,*/assistant/*=1,*chromeos/login/*=1,auto_enrollment_controller=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,*night_light*=1,update_engine=1,component_updater_service=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2
Driver Information
Initialization time	247
In-process GPU	false
Passthrough Command Decoder	false
Sandboxed	true
GPU0	VENDOR = 0x8086 [Intel Open Source Technology Center], DEVICE= 0x191e [Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2) ] *ACTIVE*
Optimus	false
AMD switchable	false
Driver vendor	Mesa
Driver version	18.2.0
Driver date	
Pixel shader version	3.20
Vertex shader version	3.20
Max. MSAA samples	16
Machine model name	
Machine model version	
GL_VENDOR	Intel Open Source Technology Center
GL_RENDERER	Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2)
GL_VERSION	OpenGL ES 3.2 Mesa 18.2.0-devel (git-0f959215c3)
GL_EXTENSIONS	GL_ANDROID_extension_pack_es31a GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_APPLE_texture_max_level GL_EXT_blend_func_extended GL_EXT_blend_minmax GL_EXT_buffer_storage GL_EXT_clip_cull_distance GL_EXT_color_buffer_float GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_copy_image GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_frag_depth GL_EXT_geometry_point_size GL_EXT_geometry_shader GL_EXT_gpu_shader5 GL_EXT_map_buffer_range GL_EXT_multi_draw_arrays GL_EXT_occlusion_query_boolean GL_EXT_polygon_offset_clamp GL_EXT_primitive_bounding_box GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_separate_shader_objects GL_EXT_shader_framebuffer_fetch GL_EXT_shader_framebuffer_fetch_non_coherent GL_EXT_shader_integer_mix GL_EXT_shader_io_blocks GL_EXT_shader_samples_identical GL_EXT_tessellation_point_size GL_EXT_tessellation_shader GL_EXT_texture_border_clamp GL_EXT_texture_buffer GL_EXT_texture_compression_dxt1 GL_EXT_texture_cube_map_array GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_norm16 GL_EXT_texture_rg GL_EXT_texture_sRGB_decode GL_EXT_texture_type_2_10_10_10_REV GL_EXT_unpack_subimage GL_INTEL_conservative_rasterization GL_INTEL_performance_query GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KHR_texture_compression_astc_ldr GL_KHR_texture_compression_astc_sliced_3d GL_MESA_shader_integer_functions GL_NV_draw_buffers GL_NV_fbo_color_attachments GL_NV_image_formats GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_EGL_sync GL_OES_compressed_ETC1_RGB8_texture GL_OES_copy_image GL_OES_depth24 GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_geometry_point_size GL_OES_geometry_shader GL_OES_get_program_binary GL_OES_gpu_shader5 GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_primitive_bounding_box GL_OES_required_internalformat GL_OES_rgb8_rgba8 GL_OES_sample_shading GL_OES_sample_variables GL_OES_shader_image_atomic GL_OES_shader_io_blocks GL_OES_shader_multisample_interpolation GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_surfaceless_context GL_OES_tessellation_point_size GL_OES_tessellation_shader GL_OES_texture_3D GL_OES_texture_border_clamp GL_OES_texture_buffer GL_OES_texture_cube_map_array GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_texture_stencil8 GL_OES_texture_storage_multisample_2d_array GL_OES_vertex_array_object GL_OES_vertex_half_float GL_OES_viewport_array
Disabled Extensions	GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Disabled WebGL Extensions	EXT_disjoint_timer_query EXT_disjoint_timer_query_webgl2
Window system binding vendor	Mesa Project
Window system binding version	1.4 (DRI2)
Window system binding extensions	EGL_ANDROID_blob_cache EGL_EXT_create_context_robustness EGL_EXT_image_dma_buf_import EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_create_context_no_error EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image_base EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export
Direct rendering	Yes
Reset notification strategy	0x8252
GPU process crash count	0
Compositor Information
Tile Update Mode	One-copy
Partial Raster	Enabled
GpuMemoryBuffers Status
ATC	Software only
ATCIA	Software only
DXT1	Software only
DXT5	Software only
ETC1	Software only
R_8	CAMERA_AND_CPU_READ_WRITE, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
R_16	Software only
RG_88	SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
BGR_565	GPU_READ
RGBA_4444	Software only
RGBX_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE
RGBA_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE
BGRX_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE
BGRX_1010102	Software only
RGBX_1010102	SCANOUT_CPU_READ_WRITE
BGRA_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
RGBA_F16	Software only
YVU_420	GPU_READ
YUV_420_BIPLANAR	SCANOUT_CAMERA_READ_WRITE, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
UYVY_422	Software only
Display(s) Information
Info	Display[1881264395124736] bounds=[3840,713 1920x1080], workarea=[3840,713 1920x1032], scale=1, internal.
Color space information	{primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}
Bits per color component	8
Bits per pixel	24
Info	Display[4693658129385987] bounds=[0,0 3840x2160], workarea=[0,0 3840x2112], scale=1, external.
Color space information	{primaries_d50_referred: [[0.6479, 0.3310], [0.3200, 0.5983], [0.1563, 0.0654]], transfer:0.0000*x + 0.0000 if x < 0.0000 else (1.0000*x + 0.0000)**2.2000 + 0.0000, matrix:RGB, range:FULL}
Bits per color component	8
Bits per pixel	24
Video Acceleration Information
Decode h264 baseline	up to 4096x4096 pixels
Decode h264 main	up to 4096x4096 pixels
Decode h264 high	up to 4096x4096 pixels
Decode vp8	up to 4096x4096 pixels
Encode h264 baseline	up to 4096x4096 pixels and/or 30.000 fps
Encode h264 main	up to 4096x4096 pixels and/or 30.000 fps
Encode h264 high	up to 4096x4096 pixels and/or 30.000 fps
Log Messages
[8877:8884:0820/220215.764385:VERBOSE1:drm_device_manager.cc(53)] : Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1
[8877:8884:0820/220215.772900:ERROR:drm_gpu_display_manager.cc(209)] : There is no display with ID 1881264395124736
[8877:8884:0820/220215.773065:ERROR:drm_gpu_display_manager.cc(209)] : There is no display with ID 4693658129385987
[8877:8884:0820/220216.164892:ERROR:drm_gpu_display_manager.cc(209)] : There is no display with ID 1881264395124736
[8877:8884:0820/220216.164965:ERROR:drm_gpu_display_manager.cc(209)] : There is no display with ID 4693658129385987
[8877:8884:0820/220216.169900:ERROR:drm_gpu_display_manager.cc(209)] : There is no display with ID 1881264395124736
[8877:8884:0820/220216.169967:ERROR:drm_gpu_display_manager.cc(209)] : There is no display with ID 4693658129385987
[8877:8884:0820/220217.070688:VERBOSE1:drm_display.cc(104)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=26 connector=37 origin=0,0 size=1920x1080
[8877:8884:0820/220217.075621:VERBOSE1:drm_display.cc(104)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=30 connector=52 origin=0,1140 size=3840x2160

Deleted: internal display.jpg 1.2 MB

	internal display.jpg 1.2 MB View Download

Deleted: external display.jpg 1.2 MB

	external display.jpg 1.2 MB View Download

Same issue...washed out external monitor via HDMI (unusable)
Asus C302 Flip
Chrome 69.0.3497.35 (Beta Channel)

Only temp fix is to drop the resolution to 1600x900...although that resolution does not look great.

Piling on. Same issue on ASUS C302, on the stable channel

@warren - you mention stable channel, you mean on version 67 is that correct?
I am also on an Asus C302 and did not see the behavior starting until the monitor was able to set the resolution and refresh rate separately.  What monitor are you sending the signal to? And what HDMI cable are you using?  Are you on 60Hz on the monitor and have you tried a different cable? Note that a lot of dongles branded as 4K are not able to produce more than 30Hz.
  

My mistake - I was on the beta channel, NOT stable. 

The monitor is a Samsung 1080p monitor, but I also got the same results on another monitor. It is plugged in via an Anble USB-C to HDMI adapter, but I also tried an Apple USB-C to HDMI adapter and got the same problem.  The problem started after the last (beta) update

+1 for meet this issue as well.
Please help fix this ASAP as really suffer by this issue!!


ChromeOSversion 69.0.3497.35 beta (64 bit)) on HP Chromebook

Resolution 1920x1080 (60 Hertz), dropping 1 resolution resolves the washout seen. 

Same issue on Samsung Chromebook Pro (caroline) 69.0.3497.35 Beta channel. 
No problem with VGA output through USB-C dongle. 
Washed out colors occur with USB-C to HDMI (2 different dongles, multiple different screens and cables). 
Colors normalize at any resolution other than 1920x1080 (60Hz), but the image either doesn't fill the available display space or elements are hidden in the periphery.

Chiming in from the peanut gallery as well, I have the same issue on the Samsung Chromebook Pro running caroline on stable channel v68.0.3440.87. Using USB-C to HDMI get the same washed out screen at 1920 x 1080 on a Viewsonic 24 inch monitor. While not optimal it does render fairly well under 1680 x 1050 (60 Hertz)

 Issue 876292  has been merged into this issue.

Sorry but Stable 68 was pulled, your Chromebook should roll back to version 67 - https://9to5google.com/2018/08/15/google-chrome-os-68-pulled-wifi-issue/

Re 108: Devices that have updated to 68 will not rollback to 67 (there is no mechanism for doing so)

The event referenced in the article was a temporary pause to the rollout (a fairly common thing) I'm not sure why it got so much press.

Re 109, thanks for the clarification on the rollback. Given that I am only encountering an issue with an external display I am reluctant to go down the path of power-washing my system unless more substantial issues arise creating unworkable scenarios. Just hoping a fix comes soon for those days when I work at home.

Apologies, I will do better research

Everyone having this issue, have you tried disabling night light in flags?  

I had enabled mine a while back and wasn't having any issues until the most recent update.  After disabling it again, my external monitor is working fine.  

Re 112: No, disabling "Enable Night Light" flag does not solve the issue, at least not on my Asus C302 (69.0.3497.35).

afakhry@ we can certainly revert the chromium change as a temporary measure.

We should really also fix disabling of the CTM. afakhry@ do you know if Ash sets the CTM to identity if night light is disabled? I'm thinking that those that did disable night light currently need to reboot in order to have the CTM disabled.

Yes, NL sets the CTM to identity when temperature is 0, or when NL is off. We know this is the issue, but marcheu@ thought the commit in #75 fixed this issue. 

Disabling NL on M-69+ *won't* help, on 68 yes. This is because `ColorCalibrationData::correction_matrix` is initialized to identity, which we needed to do to fix  issue 848444  and issue 839672. 

I will discuss with dcastagna@ to see if we should reland the commit in #50.

Just one more data point: Same issue on 69.0.3497.35 (Official Build) beta (64-bit) - ACER-LILI

I just tried latest M-70 canary, and I can't repro the issue. Let me try on M-69.

Weird! I can't repro on 69.0.3497.58 / 10895.33.0. I used to be able to repro on the same device and monitor long ago. Anyone is able to repro on this same version?

I was testing on eve.

Oshima-san was able to repro on M-70 on caroline. I think both devices have different kernel versions. I think marcheu's commit got merged to kernel 4.4 only.

Just spoke with dcastagna@ and yes, the fix needs to be merged back to kernel 3.18. Until then caroline devices will suffer from this issue.

CAVE has similar issues on both 69 and 70 in Canary, I dropped into the coal mine yesterday and can confirm the issue appears there too on this system (Asus C302).

Great news @afakhry, thanks for looking into it, I hope to see a revision coming up, are you streaming it into beta or did you want us to test in Dev first?

RE: #112
No, see my reply #80. My problem started with updating to 68 stable 12 days ago and still continued.

I am having this issue with
ChromeOSversion 69.0.3497.35 beta (64 bit)) on HP Chromebook + Dell U2311H LCD
Resolution 1920x1080 (60 Hertz),

After update version to 69.0.3497.58 beta (64 bit), "Wash Out" Issue still exist !!

The latest update on beta today messed it up even more - I had to roll back to stable for tonight.... lol  - will try to upgrade to Canary tonight.

Encountered this issue on external display (Acer B326HK) acting as primary monitor connected to HP Chromebook 13 with ChromeOS Version 69.0.3497.35 (Official Build) beta (64-bit). Reducing the resolution from 3840x2160@30 to 2560x1440@60 improves the wash out.

I registered  issue 876292  but it was merged into this one.
To add our experience of this issue so far for 25 of our ~200 Chromebooks:

When updated to (69.0.3497.35  Channel: beta), Chromebooks (model HP 13 G1) connected to an external display via HDMI set to 1920x1080 show a high contrast on the external display.
Workarounds include rolling back to stable or changing the resolution down a notch.

I also have problem with washed out screen on some resolutions with external display.
Asus C302.
Don't know if this info helps, but i think the colors are perfect when i press ctrl+shift+F5 (screenshot).
I attach 2 photos, standard and what I see when i take a screenshot.

Deleted: Standard.JPG 1.2 MB

	Standard.JPG 1.2 MB View Download

Deleted: Ctrl-shift-F5.JPG 1.5 MB

	Ctrl-shift-F5.JPG 1.5 MB View Download

The fixes are being merged now by dcastagna@.

Same problems here on an asus c302 for about the last week or so chrome version 69.0.3497.58

Will it be merged to beta and dev?  Stable 68 is perfectly fine.

No, stable 68 isn't perfectly fine for some devices. See my comment #80.

Have you installed the one that was released on August 28?  Comment 80 is weeks ago

As imply from my reply #80 release 68.0.3440.87 Stable was installed to my Acer Chromebook 14 for Work (CP5-471) on 12th August. Its built date is 2nd August and no other stable release was available for my device so far.
PS: Manual check invoked updating process just now.

I am on stable 68.0.3440.118 (Official Build) (64-bit) and I own a Samsung CB Pro, and I have the same issue, so the issue is in the latest stable release as well

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/f8a1102352dff8fdc5190c7a1c41a609c2863010

commit f8a1102352dff8fdc5190c7a1c41a609c2863010
Author: Johnson Lin <johnson.lin@intel.com>
Date: Wed Aug 29 23:08:55 2018

UPSTREAM: drm/i915: Fix Limited Range Color Handling

Some panels support limited range output (16-235) compared
to full range RGB values (0-255). Also userspace can control
the RGB range using "Broadcast RGB" property. Currently the
code to handle full range to limited range is broken. This
patch fixes the same by properly scaling down all the full
range co-efficients with limited range scaling factor.

v2: Fixed Ville's review comments.

v3: Changed input to const and used correct data types as
    suggested by Ville

v4: Fixed some missing data type corrections.

BUG= chromium:848540 
TEST=boot on eve, check the seiki 4K TV color isn't washed out

Signed-off-by: Johnson Lin <johnson.lin@intel.com>
Signed-off-by: Uma Shankar <uma.shankar@intel.com>
Reviewed-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Signed-off-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/1517327489-26128-1-git-send-email-uma.shankar@intel.com
(cherry picked from commit db9c06dfff43b2a040ba2b4f2300c30e454dd930)
Signed-off-by: Stphane Marchesin <marcheu@chromium.org>

Change-Id: Idd4092c779a60fb7f55fc6f8cf0ae956136e6d4d
Reviewed-on: https://chromium-review.googlesource.com/1141356
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Stphane Marchesin <marcheu@chromium.org>
Tested-by: Stphane Marchesin <marcheu@chromium.org>
Commit-Queue: Stphane Marchesin <marcheu@chromium.org>
(cherry picked from commit 3bff20548b6157428e0b2922a9c8e7aad5fab6fc)
Reviewed-on: https://chromium-review.googlesource.com/1155388
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Tested-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1191245
Commit-Ready: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>

[modify] https://crrev.com/f8a1102352dff8fdc5190c7a1c41a609c2863010/drivers/gpu/drm/i915/intel_color.c

Just updated to 70.0.3532.8 dev (64-bit), problem still exists, exactly like comment 129 and 130.

Merge approved, M69:

https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1191244

https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1191245

https://bugs.chromium.org/p/chromium/issues/detail?id=848540

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/dd4e4948e50f4a52c8fec550bf79444fd1cad8bb

commit dd4e4948e50f4a52c8fec550bf79444fd1cad8bb
Author: Johnson Lin <johnson.lin@intel.com>
Date: Thu Aug 30 20:12:01 2018

UPSTREAM: drm/i915: Fix Limited Range Color Handling

Some panels support limited range output (16-235) compared
to full range RGB values (0-255). Also userspace can control
the RGB range using "Broadcast RGB" property. Currently the
code to handle full range to limited range is broken. This
patch fixes the same by properly scaling down all the full
range co-efficients with limited range scaling factor.

v2: Fixed Ville's review comments.

v3: Changed input to const and used correct data types as
    suggested by Ville

v4: Fixed some missing data type corrections.

BUG= chromium:848540 
TEST=boot on eve, check the seiki 4K TV color isn't washed out

Signed-off-by: Johnson Lin <johnson.lin@intel.com>
Signed-off-by: Uma Shankar <uma.shankar@intel.com>
Reviewed-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Signed-off-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/1517327489-26128-1-git-send-email-uma.shankar@intel.com
(cherry picked from commit db9c06dfff43b2a040ba2b4f2300c30e454dd930)
Signed-off-by: Stphane Marchesin <marcheu@chromium.org>

Change-Id: Idd4092c779a60fb7f55fc6f8cf0ae956136e6d4d
Reviewed-on: https://chromium-review.googlesource.com/1141356
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Stphane Marchesin <marcheu@chromium.org>
Tested-by: Stphane Marchesin <marcheu@chromium.org>
Commit-Queue: Stphane Marchesin <marcheu@chromium.org>
(cherry picked from commit 3bff20548b6157428e0b2922a9c8e7aad5fab6fc)
Reviewed-on: https://chromium-review.googlesource.com/1155388
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Tested-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1191245
Commit-Ready: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
(cherry picked from commit f8a1102352dff8fdc5190c7a1c41a609c2863010)
Reviewed-on: https://chromium-review.googlesource.com/1197184

[modify] https://crrev.com/dd4e4948e50f4a52c8fec550bf79444fd1cad8bb/drivers/gpu/drm/i915/intel_color.c

Sorry to report that 69.0.3497.73 still has a washed out screen on Platform
10895.40.0 (Official Build) beta-channel cave and Firmware
Google_Cave.7820.384.0

No improvements from update

Can confirm the most recent update 3497.73 from the beta channel is still not fixed on the asus c302

Same as comment 139, latest Dev update to 70.0.3532 did not resolve issue.

Didn't fix for me on beta channel.

same problem here on c302.
i was on son built 67 and worked fine, tried beta 68 and got the problem so i rolled back.
now on stable 68 the problem still there...
i use my screen mirrored for presentations at work so i cant decrease resolution.

This issue is really suffering!!!
Anyone has fix plan for this issue please ?

Thanks.

Same thing is happening for me.  Asus Chromebook C302; Chrome Dev 70, first time trying.  Washed out external monitor on 1920x1080@60hz, washed out on 1280x720@60hz.  Not washed out a 1680x1050, but stretched obviously since it's not the same aspect ratio.

I'm having the same problem. Just commenting for visibility.

Asus Chromebook c302ca. Stable, not Dev.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/93cbc36846062987197cf72d2190d503bc5c8e54

commit 93cbc36846062987197cf72d2190d503bc5c8e54
Author: Johnson Lin <johnson.lin@intel.com>
Date: Tue Sep 04 22:11:58 2018

UPSTREAM: drm/i915: Fix Limited Range Color Handling

Some panels support limited range output (16-235) compared
to full range RGB values (0-255). Also userspace can control
the RGB range using "Broadcast RGB" property. Currently the
code to handle full range to limited range is broken. This
patch fixes the same by properly scaling down all the full
range co-efficients with limited range scaling factor.

v2: Fixed Ville's review comments.

v3: Changed input to const and used correct data types as
    suggested by Ville

v4: Fixed some missing data type corrections.

BUG= chromium:848540 
TEST=boot on eve, check the seiki 4K TV color isn't washed out

Signed-off-by: Johnson Lin <johnson.lin@intel.com>
Signed-off-by: Uma Shankar <uma.shankar@intel.com>
Reviewed-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Signed-off-by: Ville Syrjl <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/1517327489-26128-1-git-send-email-uma.shankar@intel.com
(cherry picked from commit db9c06dfff43b2a040ba2b4f2300c30e454dd930)
Signed-off-by: Stphane Marchesin <marcheu@chromium.org>

Change-Id: Idd4092c779a60fb7f55fc6f8cf0ae956136e6d4d
Reviewed-on: https://chromium-review.googlesource.com/1141356
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Stphane Marchesin <marcheu@chromium.org>
Tested-by: Stphane Marchesin <marcheu@chromium.org>
Commit-Queue: Stphane Marchesin <marcheu@chromium.org>
(cherry picked from commit 3bff20548b6157428e0b2922a9c8e7aad5fab6fc)
Reviewed-on: https://chromium-review.googlesource.com/1155388
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Tested-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1191245
Commit-Ready: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
(cherry picked from commit f8a1102352dff8fdc5190c7a1c41a609c2863010)
Reviewed-on: https://chromium-review.googlesource.com/1204654
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Tested-by: Ahmed Fakhry <afakhry@chromium.org>
Trybot-Ready: Ahmed Fakhry <afakhry@chromium.org>

[modify] https://crrev.com/93cbc36846062987197cf72d2190d503bc5c8e54/drivers/gpu/drm/i915/intel_color.c

Asus C302, new update today: 70.0.3538.7
Now my external display works ok.

Same, latest Dev update 70.0.3538.7 fixed this. Now, how do we prevent a regression... 

Thanks all for the feedback.

@#152: We do have tests that catch this kind of issues (look at  crbug.com/867652 ). Those tests are currently not blocking a patch from landing though since they're not run in the CQ.
For this particular bug, the issue has been there for a while, we started noticing it when we enabled night light, since we were not using the color transform matrix extensively before.

Confirmed post 151, 152 - dropped into Dev Channel for this.  Thanks all for looking into this.

Also confirming Comment 151 and 152, issue is fixed, thank you very much!

When will we see this pushed to Beta?

Updated to Version 69.0.3497.73 (Official Build) beta (64-bit). No change in beta, problem is on-going as per my report in #c128.

Confirmed that Beta still has the issue of washed out external screen, even after update this morning to 69.0.3497.73 (Official Build) beta (64-bit) on Cave.

I just updated to Version 69.0.3497.87 (Official Build) beta (64-bit) and the bug is squashed, the extended screen is properly displayed on a Asus C302 with a Samsung 28inch UHD monitor.

Same, this is fixed for me in the latest beta release. Thanks! 

Running Version 70.0.3538.7 (Official Build) dev (64-bit) on a PixelBook.

I still see this issue if Night Light is on and it is against a light/white background with dark text.

Dark background with light text, no issues.  Turn off Night Light and no issues.

THANK YOU!!! Beta FIXED!!!!!!! thank you thank you thank you!

The latest beta also fixed it for me, thanks!

Chrome OS version 69.0.3497.87 (Official build) beta (64-bit)
Hardware: Asus Chromebook Flip C302CA + Asus MX239 23" monitor (1920x1080 @ 60 hertz)

My 2018 Acer Chromebook 15 with an Acer external 1080p display over VGA is still washed out.  The colors are just so muted.  It feels like my Pixel 2 XL display before Google put 'Vivid' in.  I'm on 69.0.3497.87.  Wish this were fixed for me.

now just have to wait the fix to arrive stable....

Issue still remains on Chromebook 2015. Running Version 71.0.3567.0 (Official Build) dev (64-bit)

External monitor washed out color with USBC to HDMI. The only time you can get the true colors is if you set the system to extended display. Then the colors work but the windows will stretch across two displays. 

Issues Still persist as above on 2015 chromebook pixel 

LCD is fine, but extended display is not. If you select mirror this display it will actually look ok but the resolution will be horrible. I set mine up so I can close the lid and have only the External LCD, the red and all the colors are washed out still. 

Can we please have confirmation when this will arrive in v69 stable?

Hi, first time poster in bug tracker.

We have a large ChromeOS fleet. We control our Chrome Releases with vigorous testing before general rollout. Our next release will be OSV69.

Currently testing on 69.0.3497.95, ASUS C302 Flipbook.

we are seeing this on external ASUS V248 monitor, USBC - HDMI. Switching resolution using extended mode makes no difference. It's almost like the Contrast is set too high. (We did check the monitor settings)

Re#168: I just tried to repro this on samus (2015 pixelbook) and I was unable to. This device doesn't even support a color transform matrix, and NL is set using the compositor.

You might be referring to another problem. It would be helpful if you file a new bug with pictures/videos showing the buggy colors. It might be a completely different issue.

Hi,

We can raise a new bug once we do a series of tests.

I can say that in ChromeOS V63, when the ASUS 302C was unboxed with its original OS, looked fine on external monitor. I took photos but they don't accurately represent the screen (before and after shots).

apologies, the comment to raise new bug was regards to the pixel, not asus. We wont be raising a new bug yet for Asus.

Hi,

As of ChromeOS 69.0.3497.120 (stable)we are still seeing this "Washed Out" affect on extended.

Tested on Google Pixel (Link) with identical parallel setup.

1. Reset both ASUS monitors to Defaults
2. Connect Chromebook 1 over USBC-HDMI to monitor 1 (running ChromeOS V62)
3. Connect Chromebook 2 over USBC-HDMI to monitor 2 (Running ChromeOS V69.0.3497.95)

These shots are screen captured.

Chrome62 Has less Contrast to Chrome69, clearly visible in the screenshots (using dark scene with abstract lighting)

Deleted: test setup.jpg 153 KB

	test setup.jpg 153 KB View Download

Deleted: ChromeOSV62 External Monitor.png 1.5 MB

	ChromeOSV62 External Monitor.png 1.5 MB View Download

Deleted: ChromeOSV69 External Monitor.png 3.2 MB

	ChromeOSV69 External Monitor.png 3.2 MB View Download

Correction. These were tested on the Mini HDMI port on the Pixels.

But we see the same thing on the USBC-HDMI on C302.

This is still pretty horrible. I'm using the latest Acer 15.6"  Chromebook hooked up to an external Acer 1080p display using an USB-C -> VGA adapter.  The colors at 1080 are NOT good.  The palette looks like it's lower bit-depth and everything is lighter and duller.  I changed the display resolution down to 1680x1050 60Hz and suddenly all my vivid deeper color came back (even though my resolution now officially sucks).    I'm on the very latest beta channel version 71.0.3578.94.  

Please tell me Google hasn't forgotten about this issue. It's really shockingly bad.

Re #176: This bug has been closed for a long time, and the number of comments is really huge, so I think the best approach here to file a new bug at https://bugs.chromium.org/p/chromium/issues/entry?components=UI&labels=OS-Chrome, provide more info about you device, external monitors, cables, hubs, repro steps ... etc. (if any). Also paste version info from chrome://version. If you can also file a feedback report (Alt+Shift+i) while the problem is happening, that would be really helpful.

Please paste the link to the new bug here once filed.

Thanks!