You're telling the OS specifically what the default ICC profile should be, and the setting is not taking? That is very strange. Now, if the Huey software is constantly updating the profile, and the OS isn't seeing this updated profile as the previously-identified default, then I can understand the behavior.
In fact, as flakey as the OS behavior sounds, it probably makes perfect sense on some level. The OS needs to detect and react to hardware changes, such as different displays, and it should not retain a profile for a specific display if the display is changed. If, for some reason, the OS is interpreting certain interruptions as indications of a hardware update or change, it might make sense for it to reload a generic default.
I think that the author of the article you linked to is on the right track with blaming conflicts between the OS and the 3rd-party software, but I also think it has to do with the OS's reaction to certain interrupts.
I don't use any 3rd-party software to load ICC profiles, so I have no relevant experience to share.
|
