We need to load/save display preferences with mustash. The display preferences code is located in chrome/browser/chromeos/display/ running in the chrome process while display management is located in the mus-ws process. As such, chrome can't directly access the display management code anymore.
I think the new preference service should be able to solve this? Chrome can still load/save the preferences and mus-ws can access the values stored for the initial display states and save new states when they're accessed.
Comment 1 by kylec...@chromium.org
, Jan 6 2017