https://2.bp.blogspot.com/-LqRniYeVeEk/XOLYEiOcKCI/AAAAAAAAJ...
If on a Pixel 3 or Samsung Galaxy S10 or another P3 capable display, it's a faint-but-visible red logo. Otherwise it's just solid red.
Edit: If not on Android Q, try using Firefox.
There seem to be some odd behavior depending on the software and this may not be always consistent.
It might be included only in the Android Q update.
Googling around shows that it might be restricted to custom apps only?
"There is one way to bypass this issue, and that is to explicitly tell Chrome to override the default provided system colour profile and just tell it the display is Display P3. This enables colour management in the app, and short of writing a custom application, is the only way to get wide colour gamut content to work on the Pixel 3."
https://www.anandtech.com/show/13474/the-google-pixel-3-revi...
Take a screenshot of the full-screen image. Do you see the logo flash?
Zoom in to the image. Do you see the logo appear, but only near the edges of the display?
Computers!
On my Pixel 3 XL, the behaviors I described occur, and also the logo is invisible unless the overlay is shown (in which case it's drawn only near the edges, unless you're taking a scree...oh.
I get it.
Image math is getting done internally in a wide gamut. Including alpha blending. But it's converted to sRGB before being displayed.
The things I described all, I suspect, modify the image- mostly by just dimming it, and the resulting dimmed wide color values map to different sRGB colors (where the undimmed colors all map to the same shade of red.)
as to what's actually happening: not a clue! just pointing out possibilities :)
If anyone is curious: https://i.imgur.com/IGTAWZF.png
I then saved it as a PNG (still showing the logo in Windows image viewer) and uploaded to Imgur. I assume pasting it into paint compressed the colors?
I saved it as a PNG and uploaded it. I don't know the technical details behind this but I'm assuming Paint compressed the colors.
I'm looking at this from a macbook pro 2015 so I assume no wide colour support (?), yet I see the logo. Which conversion, at which step, caused that effect?
The clipboard here is probably copying the image buffer in the untransformed state, and pasting it into MSPaint would dump those values incorrectly.
The issue would be the mechanics of the copy (attaching metadata) and pasting (interpreting the metadata in conjunction with the source image buffer.)
So technically, no, there's no conversion on the source data, it's the representation in the pasted context that's the issue.
Yet I cannot get the android logo to display on Chrome or when the picture is downloaded and viewed on the default photo viewer.
Oh well maybe a future update will solve this issue. :p
Actually I'm a hobby photographer, and I generally favor accurate color representation over any other special color modes. I do remember playing around with the settings when I got my phone and I think I just forgot to switch the color mode back to normal from vivid.
Which would mean that the red logo is just a result of mismapped colors.
I was pretty surprised to see the logo on a phone from 2011 with a rather meh screen…
I tried setting the flag (chrome ://flags/#force-color-profile) and choosing P3, but I still see just a red square in Chrome.
EDIT: muro's tip (open in photos (menu -> device folders)) worked. Not sure why opening the same image from the Photos home screen doesn't work.
However, donwloading the png file and opening it on any image viewer it shows two different shades of red. I guess firefox is applying a silly color contrast change to its images before displaying them.
It's also solid red in GIMP 2.10, which surprised me.
Edit: answered below - download to device, open in photos (menu -> device folders)
tl;dr: (╯°□°）╯︵ ┻━┻ color is hard.
Not sure about Chrome as I set the color flags to be sRGB a long time ago as, compared to Firefox, colours in Chrome are unsatisfactory on Linux.
I also tried on a consumer grade laptop that runs the latest (19.04) Ubuntu with one of those glossy screens, definitely not designed for Display P3. This failed in Firefox, Chrome, Gimp but the thumbnail in the file browser came good. How come when the hardware isn't there for it?
It seems like 25% of the colours are missing with a lot of that being green, green being quite an important colour. It must be possible to have some creative fun with this. If you can get images that only kids can see on their phones but adults not see on their boring PCs then you could have some variant of 'satanic backmasking' going on.
'Satanic backmasking' was where you could hear stuff about Satan on Beatles records if you played them backwards, listening whilst stoned. Politicians bothered themselves about young minds being corrupted by such things back in the day.
Maybe DCI-P3 images can court a similar controversy, shame April Fools Day is a lame day of corporate gags where nobody is fooled, otherwise DCI-P3 is ripe for moral panic, terrorising the adults with another thing for them to get their politicians frenzied about.
I hope Chrome gets to do colour a bit better, to Firefox standards. Otherwise we will be with half the world's screens not showing all the colours. Although not the same gap as between colour and monochrome, it is a huge difference to anyone that works with colour and needs subtle colour variations.