Update: June 4, 2020 at 3:39 p.m. ET: It looks like a fix is almost here. Google and Samsung are both internally testing fixes for the wallpaper bug. Weâ€™ll of course update you once we hear about fixes rolling out to Android devices.
According to Googleâ€™s Romain Guy on Twitter, the underlying issue with the wallpaper bug is related to how luminance is computed in Android, not color space conversion as we once thought.
Yeah the color space conversion is unrelated, the real problem is the way luminance is computed.
â€” Romain Guy (@romainguy) June 3, 2020
Original article: June 3, 2020 at 10:35 a.m. ET: The dreaded soft bricking wallpaper bug is under review by Google, and the company is working on a solution.
A user posted about the issue on AOSP, and a Google representative named Wu Ahan responded claiming that the company is reviewing a solution to the problem:
Hi all, sincerely thanks for your contribution, we have an internal solution under reviewing.
The representative didnâ€™t mention anything about a timeframe for when the fix would be available, so users will need to continue to be careful for the time being.
Weâ€™ve figured out exactly what it is about the image that causes Android devices to soft brick. Itâ€™s a bit complicated, and you can read the full breakdown in this article. To summarize, the SystemUI only handles sRGB images for the wallpaper, and it doesnâ€™t check against non-sRGB images. Setting a non-sRGB wallpaper can then cause an issue that leads to the crash due to an error in the variables.
Of course, we donâ€™t recommend trying the wallpaper for yourself, as it could end up permanently damaging your phone. As always, be careful what you set as your wallpaper, and you shouldnâ€™t run into any issues.