How THIS wallpaper kills your phone.

Here's a funny story. I managed to break my

phone

just by applying

wallpaper

to it and I'm not alone. It seems like hundreds of people in the last week have had their entire

phone

wiped because of

this

. This photo from Aversa on Twitter Ice. Famous leaker in the universe, he basically made a post saying that people are spreading

this

wallpaper

, please don't apply it, but of course people did what a sister or a phone enthusiast would know world-renowned intelligent people and I don't think so. I have ever seen karma come back faster. The comments section is filled with two types of responses: people who have applied it and gotten away with it on their phones and who seem to be using it as a way to demonstrate that they chose a superior device. and the other less fortunate group that applied it and quickly realized that they probably shouldn't if they posted the videos of their devices basically going schizophrenic, in many cases they had to delete everything.

Listen to cat people, the cat never. lies anyway, there are three unusual things that happen here, number one: whether

your

device is destroyed or not depends on who did it, for example, Google and Samsung know not to go there: if you upload the photo to a social networking site as error and download it again, the colors will change to this less vibrant version and it is safe to use and three, you can notice that I have been showing you this wallpaper on my Samsung phone all this time and the way I have done it. It's just take a screenshot of the image and set it as my wallpaper which is safe;

At first glance, none of this makes sense, so what's going on here? Well, I spelled it for the last three days trying to figure it out, okay? The initial assumption was that it is malware. Someone obviously designed this wallpaper so that it conflicts with the Android code and starts bricking phones. The resolution is exactly 1440 by 2560, which is the current standard Android wallpaper resolution that is designed to apply as wallpaper and add. I've never seen a wallpaper in my life that can kill phones so consistently. What are the chances of someone stumbling across that by accident? Well, the more I looked into it, the more it seems like my initial assumption was wrong.

I thought it was the best way. To find out if something was malicious or not, it was about finding out where it came from, so I did a reverse image search. Google Images now has a clever little feature that allows you to use an image to search for similar images and by doing so within two Minutes I traced the cursed wallpaper back to its original source. It turns out that the wallpaper that was circulating was not the original photo. This is the original photo from HDQ Walls. Don't worry and if you don't know the original and verify the image data, you can.

Look, it's just a photo taken with a Nikon D80 camera. Surely that can't be the problem. It's just someone who took his camera to a national park, maybe he came to the tower during the night to take this awesome photo of a sunrise that doesn't go away. break

your

phone and a lot of people online were saying that the reason the cursed photo was crushing ferns was because it was encoded in a color profile called google skier, but the singers now managed to get the original photo and I could see that this was not a skier image from Google, I applied it to my Galaxy S 20 ultra, big mistake, the Galaxy S 20 ultra was gone in one fell swoop, it went silent, I couldn't get past the lock screen and even safe mode wouldn't let me get it back all.

The person who had appointments on that phone that I didn't back up is gone and I won't lie, this felt like that part of a detective movie where the detective gets too involved in a case and the criminal isn't happy with it. that, so start. taking away members of my family. I lost my data trying to fight this because I thought it would be okay. I thought this is the original image. It is just a picture. This may not be the problem, but I was wrong and I am. a little bummed, but a channel sub would be awesome, but anyway we can see that this crash was not caused by a malicious third party tampering with the image afterwards, as I had initially suspected it was the original photo that was enough to break. his phone, so that leaves the question: is he okay?

Let's talk about color for a minute. take a look at this diagram. This represents all the colors that humans can see. This triangle inside is the sRGB color space. It is a subset. It's a small section. of the entire color gamut and, more importantly, in this case it is the only set of colors that Android actually understands, so yes, most Android phones historically have not been able to display the full color gamut, but they are limited this way for the For the sake of consistency, sRGB is what almost all devices are calibrated for digital cameras, printers on the Internet, so by having an operating system based on it, you can ensure that, say , post something on Instagram for example, and when I see that post on the other end, I can make sure that you're seeing it the way I wanted or that when I see a photo online and print it it should look pretty similar to the view preview that I saw on the screen, but there are many different color spaces.

I have Adobe RGB as an example which has a wider range of colors or if you want to get a little crazy with things Profoto RGB which is this huge triangle here and this all looks really complicated but all it means is that if I convert a image from srgb to Adobe RGB will effectively widen the color space, the color that was previously here is mapped here, so this is a random photo - it was taken a few days ago in srgb and moved to the wider Adobe RGB, it will simply be becomes more vibrant and the same thing will happen again if we go from Adobe to Prophoto RGB because these points are moving towards these points, so what I have to do with the dawn of nightmares, it turns out that Prophoto RGB is the color space that has this photo. coded and you can see the appeal of doing this now that I know how it was coded.

In fact, I can go back to the standard srgb and it becomes this. This is the true original photo and suddenly it doesn't look so attractive. So whoever took the photo probably thought, "Oh, I really like the colors in Prophoto RGB mode. I'll just export it that way and this explains what I mentioned above about Weibo. Weibo doesn't support this ultra white color space, so that if you upload a profile encoded image on Weibo, the reason it changes is because it's actually being converted back to srgb, so okay, we've established that something in this color space is causing a problem, but it's not so simple because android can actually handle Profoto even though android only supports srgb, it is programmed to convert images from other color spaces back to srgb just so we can have that level of consistency, believe me I wish this was simpler too, but when I look at it, it seems like this conversion is actually where the problem is, Android is trying to convert this Profoto to an sRGB image, that's the bottleneck and you won't believe it, the reason these devices fail comes down to it. to a pixel, this one is here according to de'vide who I was talking to about Google color.

The engine cannot in its entire life convert this pixel to srgb specifically because of its luminance, luminance is basically brightness, but just adjust it based on the way we humans actually see things because you might know that these humans see hues greens much better. From what we see red tones and we see red better than blue, so the luminance of a pixel in Android is calculated by this formula, it gives green the most weight, then red and then blue, to put it bluntly. Otherwise, you need a lot of blue light. to give the same luminance as some green light anyway, the maximum value of red, green or blue individually is 255, so the way this code is put together you shouldn't be able to get an overall combined value higher than 255 because all the formulas What we're really doing is taking a weighted average, but for this particular pixel it turns out that the red, green, and blue values ​​are all incredibly high 255 255 and 243, so by plugging it into the formula we get red as 54.2 1/3 green is 180 2.3 76 and blue is 17.5 for 4-6.

If you add all these up, you get around 254, which is still below 255. So what's the problem? It turns out that Google uses a type of rounding that basically rounds each of these numbers up so that those RGB values ​​actually end up in 55 plus 183 plus 18, which gives 256, which is above the theoretical maximum of 2 5 5 error 1 number in a pixel is enough to send your device into this spiral of doom in a normal situation when android encounters a problem like This will try to close the process but by setting it as wallpaper, android can't just close it, you are creating a permanent error loop as it keeps trying to fix itself and this also explains why the image screenshots are Sure, there is a misconception with screenshots.

When you capture a photo, your Android phone doesn't make a copy of the photo, it creates a new image which by default will be an sRGB shot because it's Android, so that conversion is causing all the problems that don't need to happen. If you're wondering why only some devices are broken by the wallpaper, it's because they're all phones that use Google's default color engine, which is the part that's ruining the conversion, but you should worry about that. Not really, I mean obviously don't apply this wallpaper ever, but I've been working with a group of developers who have been working for hours continuously trying to recreate the bug and we couldn't decrease the chances of you seeing this appear. other wallpapers, I think it's quite low, but for your peace of mind, the upcoming Android 11 should fix this problem anyway, it's pretty easy to solve, you just need one line of code that says if this value is above 255 , then make it 255.

Anyway this has been a stressful video for the doctor, if you enjoyed it please consider subscribing and a big thanks to Michelle on Twitter and Daveed who is working on his own custom ROM called POS P right now , those guys have helped tremendously with this without my name being said. It's Aaron, this is Mr. E's boss and I'll see you next time.