Nice wallpaper you've got there. It would be a shame if it bricked your phone

But that's exactly what will happen if you decorate Androids with pretty mountain scene


A picturesque Android wallpaper image is exhibiting some unwelcome side effects on most Android phones, effectively "soft-bricking" them until the user manages to perform a factory reset.

Soft-bricking is the nicer, less permanent version of hard-bricking (the latter irreparably damages the physical hardware or firmware). Although a soft-bricked device is pretty much unusable, you can eventually restore it to normality by addressing the underlying software issue.

In this case, the background – which depicts a stunning landscape scene – would cause the Android process com.android.systemui to crash.

This Ronseal-esque process is vital to the normal functioning of an Android phone. Google's documentation describes it thusly: "Everything you see in Android that's not an app."

SystemUI has been known to fail occasionally, particularly in rougher pre-release versions of Android. It is, after all, yet another piece of software. That said, in the rare occasions when this happens, Android will always try to recover by restarting the process. That usually solves things.

Not here. With the wallpaper still in place, the conditions that forced it to crash in the first place are still present. So it crashes. Again.

And restarts. And crashes. Rinse and repeat ad nauseam.

IceUniverse, who is well known in the leaker community for their ability to uncover accurate information about Samsung's upcoming wares, first identified the issue, suspecting it primarily affected Samsung devices.

Further investigation proved that wasn't the case and identified multiple susceptible blowers, including several Google Pixel phones. That's because this issue derives from an issue within Android and how it handles colour space.

Android natively uses the sRGB (standard RGB) colour space. The malevolent wallpaper uses plain old RGB. When Android tries to convert this image, the Y axis on the image histogram exceeds the limit of 256, creating a fatal exception and causing SystemUI to crash.

This glitch is prevalent on every version of Android, save for the current Android 11 developer release. Davide Bianco, lead developer of custom ROM POSP, has filed a bug report within the Android Open Source Project. Separately, the developers of LineageOS have created their own fix.

Of course, Android is Android. If we exclude custom ROMs, patches tend to be issued at the mercy of vendors and carriers alike. As a result, it's almost certain that most users of Google's mobile OS will remain susceptible until they decide to buy a new phone.

It would therefore be prudent to exhibit caution when downloading new backgrounds. Or anything for that matter. ®

Similar topics


Other stories you might like

  • UK Home Secretary delays Autonomy founder extradition decision to mid-December

    Could be a Christmas surprise in store from Priti Patel

    Autonomy Trial Autonomy founder Mike Lynch's pending extradition to the US has been kicked into the long grass again by the UK Home Office.

    Lynch is wanted in the US to stand trial on 17 charges of fraud and false accounting. He is alleged to have defrauded Hewlett Packard investors over the sale of British software firm Autonomy in 2011.

    Continue reading
  • Want to buy your own piece of the Pi? No 'urgency' says Upton of the listing rumours

    A British success story... what happens next?

    Industry talk is continuing to circulate regarding a possible public listing of the UK makers of the diminutive Raspberry Pi computer.

    Over the weekend, The Telegraph reported that a spring listing could be in the offing, with a valuation of more than £370m.

    Pi boss, Eben Upton, described the newspaper's article as "interesting" in an email to The Register today, before repeating that "we're always looking at ways to fund the future growth of the business, but the $45m we raised in September has taken some of the urgency out of that."

    Continue reading
  • All change at JetBrains: Remote development now, new IDE previewed

    Security, collaboration, flexible working: Fleet does it all apparently

    JetBrains has introduced remote development for its range of IDEs as well as previewing a new IDE called Fleet, which will form the basis for fresh tools covering all major programming languages.

    JetBrains has a core IDE used for the IntelliJ IDEA Java tool as well other IDEs such as Android Studio, the official programming environment for Google Android, PyCharm for Python, Rider for C#, and so on. The IDEs run on the Java virtual machine (JVM) and are coded using Java and Kotlin, the latter being primarily a JVM language but with options for compiling to JavaScript or native code.

    Fleet is "both an IDE and a lightweight code editor," said the company in its product announcement, suggesting perhaps that it is feeling some pressure from the success of Microsoft's Visual Studio Code, which is an extensible code editor. Initial language support is for Java, Kotlin, Go, Python, Rust, and JavaScript, though other languages such as C# will follow. Again like VS Code, Fleet can run on a local machine or on a remote server. The new IDE uses technology developed for IntelliJ such as its code-processing engine for features such as code completion and refactoring.

    Continue reading

Biting the hand that feeds IT © 1998–2021