IssueTracker

Note: after the issue is reproduced, the device becomes unusable until a factory reset, as any attempts at UI interaction will just be blocked by the "System UI has stopped" dialog.

Stack trace:

--------- beginning of crash
03-20 21:33:01.381  1786  1786 E AndroidRuntime: FATAL EXCEPTION: main
03-20 21:33:01.381  1786  1786 E AndroidRuntime: Process: com.android.systemui, PID: 1786
03-20 21:33:01.381  1786  1786 E AndroidRuntime: java.lang.IllegalArgumentException: invalid Bitmap format
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at android.opengl.GLUtils.texImage2D(GLUtils.java:133)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at com.android.systemui.ImageWallpaper$DrawableEngine.loadTexture(ImageWallpaper.java:684)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at com.android.systemui.ImageWallpaper$DrawableEngine.drawWallpaperWithOpenGL(ImageWallpaper.java:606)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at com.android.systemui.ImageWallpaper$DrawableEngine.drawFrame(ImageWallpaper.java:403)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at com.android.systemui.ImageWallpaper$DrawableEngine$1.onPostExecute(ImageWallpaper.java:504)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at com.android.systemui.ImageWallpaper$DrawableEngine$1.onPostExecute(ImageWallpaper.java:486)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at android.os.AsyncTask.finish(AsyncTask.java:695)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at android.os.AsyncTask.-wrap1(Unknown Source:0)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:712)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:164)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6494)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
03-20 21:33:01.381  1786  1786 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
03-20 21:33:01.387  4260  4395 D EGL_emulation: eglMakeCurrent: 0x9db85b40: ver 3 0 (tinfo 0x9db834e0)
03-20 21:33:01.403  1663  1678 I ActivityManager: Showing crash dialog for package com.android.systemui u0

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

I think this should be escalated to at least a P2, or even a P1. More and more people are running into this issue with different wallpapers:
https://www.reddit.com/r/GooglePixel/comments/86t4s6/pixel_2_xl_system_ui_has_stopped_after_switching/
(The Redditor used the background from here: https://www.reddit.com/r/Amoledbackgrounds/comments/862fg1/cheshire_cat_1440_x_2960/)

Hi for the third times i had this problem, i sent already 1 pixel 2 XL to assistance but now the second had the same problem , UI stopped and then factory reset, what i have to do ? I'm from Italy thanks

This also happens for me. Please fix it soon and get a patch out.

This issue happens when using 16-bit RGB picture. 8-bit RGB picture is no problem, and default wallpaper is 8-bit.  But this bug is really serious!

Same issue.

Pixel 2 XL on Android 8.1.0, attempted to change wallpaper from default to: https://www.nasa.gov/sites/default/files/thumbnails/image/stsci-h-p1821a-m-1699x2000.png (also attached to this post)

Device would attempt to boot and fail to load UI, ultimately going into "Android Recovery" with the only options being "Try again" (resulting in the same bootloop) or "Factory data reset."

It's unacceptable that a wallpaper change can result in a soft bricking of the phone, ultimately leading to loss of data. This issue needs to be escalated.

I just had this issue happen to me. It only happened with images I had downloaded to my device. The built in wallpapers, and photos I took that had been uploaded to the cloud, and were not on my device, were able to be set as my wallpaper no problem.

Did the factory reset in "Android Recovery", as well as a full wipe and new system install from the factory images through Fastboot.

Here is a link to a video of the process causing the issue. https://photos.app.goo.gl/dnvIhhNXhFs6g1Tf1

Had the same issue two months ago. Also happened with some non-builtin wallpaper.

Had the same issue today.  It was not a Pixel stock wall but just a regular image (beach). Only thing I could notice was the size of the image (was about 15MB).  As soon as I tried to set it, System UI crashed and a wicked bootloop occurred.

Had to factory reset.

Verizon Pixel 2XL Android 8.1 with April patch installed.

It's happened to me 3x when changing wallpaper. Fuggen annoying

My Pixel 2 XL is stuck in a boot loop after I changed the wallpaper. I went into the recovery mode and performed a factory reset

After re downloading my data, I then tried to change the wallpaper a second time. The phone is now stuck in a boot loop again, before doing another factory reset, I'd like to know what I can to stop this system error from reoccurring

Thanks!

So frustrating! I'm getting the exact same system UI crash on my Pixel 1 after I set a custom wallpaper. Only recourse is to factory reset.

I have had this exact same problem twice on my Pixel 2 XL. I went back and found the images I was trying to set as wallpaper when my phone boot looped and both images were 16-bits per channel in Photoshop, which supports the earlier poster who said the problem was the bit depth of the images. If bit depth is in fact the problem with the images, two questions come to mind:

1. Is there an Android app that allows you to check the bit depth of images?
2. Would it make any difference to use a third-party launcher - like Nova - to set wallpaper or is the problem too low-level?

Following up on question #2, I installed Nova and tried setting the two wallpapers that had boot looped my phone. Both wallpapers crashed Nova, but not the phone.

Any update on this from the product and engineering team?

We have been unable to reproduce the issue with the steps provided. If you are able to reproduce the issue again or have additional information to help us, please let us know.

Setting "Pixel_BackgroundXL.png" as background on the latest Android 8.1 emulator still causes System UI crash. It was also crashing on the earlier Android P developer previews. However, it is no longer crashing on Android P Developer Preview 3, which came out today.

Repro steps for crashing 8.1:
1. Download the PNG file intact to the /sdcard/Downloads folder
2. Long press on the home screen and click on "Wallpapers" to change the wallpaper
3. Click on "My photos"
4. Browse to the "Pixel_BackgroundXL.png" file
5. Apply wallpaper, "apply to both"

Immediately, System UI goes into crash loop.

I can confirm this issue is real.

I have an application (SageTV Miniclient for Android) (SageTV is owned by google, and open source).   Up until Android 8.0 our application worked fine, loading all the image assets without issue.  Then when 8.1 came out, a handful of image assets would fail to load and give the error (Invalid Bitmat Format).  So, to be clear, all these images worked fine until 8.0.  If we open the images in Photoshop and then resave, then the problem goes away as well.   This is reproducible in the Emulator, and I'm attaching a small project that demonstrates the problem.  Basically there is an image, "test_bad.png" that can be loaded using the Bitmap apis, but when you set the image into an opengl texture using GLUtils.texImage2d you get the bad image format, resulting in this error.

07-06 06:44:07.777 12304-12323/? W/System.err: java.lang.IllegalArgumentException: invalid Bitmap format
        at android.opengl.GLUtils.texImage2D(GLUtils.java:155)
        at androidtv.sagex.opengltestapp.OpenGLTexture.set(OpenGLTexture.java:82)
        at androidtv.sagex.opengltestapp.MyGLRenderer.onSurfaceChanged(MyGLRenderer.java:83)

AVD: Pixel API 25 -- works  (shows blue background, green triangle, and png icon in top left corner)
AVD: Pixel API 26 -- Invalid Bitmap (fails, shows red background, no blue background, no green triangle, no icon -- since it failed to load bitmap and the program aborted)
AVD: Pixel API 27 -- Invalid Bitmap (fails, shows red background, no blue background, no green triangle, no icon -- since it failed to load bitmap and the program aborted)

It's clear that "something" changed in the opengl texture management between 7.1.1 and 8.0, since given the same image, same code, but only a different Android version, the image works, and then doesn't work.

Can anyone verify that this issue has been fixed in Android P final?

Ran into this just now on a (thankfully relatively new) Razer Phone running 8.1. I'm attaching the image that caused it.

Same problem here.
Coincidentally, I also tried to change the wallpaper to the very same Lagoon Nebula (as pe...@labsociety.com did) on my Nokia 6 (probably running 8.1).
Now my phone keeps turning off its lock screen.
Is it possible to solve this issue without a factory reset?

Just experienced this on a Pixel 2XL and a new Pixel 3XL with the Astronomy Picture Of the Day for 3/14/19
(I'm guessing it's a size issue). Device immediately crashes and the OS is corrupted such that a factory reset is needed

This happened to me 3 times in the last month with a Pixel 2XL. Two weeks ago I switched to a Pixel 4 XL and experienced the same issue this morning.  I have been using a Pixel for 2 years, and other android phones for ten years prior to that, and never have I seen this issue even though I've always frequently rotated my wallpaper.

I am having the exact same issue. My phone (Pixel 2 XL, Android 10, May 2020 security patch) is stuck in infinite SystemUI crash loop. I'm using Pixel Launcher and the Google Wallpapers app (both stable, no beta releases). I enabled the daily wallpaper in the Wallpapers app in the Cityscape section (or something like that, I don't remember the exact name of the section - there are mainly images of cities/buildings). It used to be fine the past couple of days - every day, the wallpaper would refresh and I got a new one each morning. But this morning I woke up to my phone's SystemUI constantly crashing.

I am guessing the wallpaper is somehow either corrupt or the phone just can't handle it. I don't know if it's a 16 bit picture, I don't know its resolution. I just know that I'm using preinstalled Google apps (Pixel Launcher and Wallpapers), no beta, just stable software, and I'm using one of the advertised features (daily wallpapers). And it rendered my phone useless. When the issue first appeared, I was getting constant SystemUI crashed dialogs. Now the dialogs don't even appear, the screen just goes black, then it turns on again just to immediately turn off, and so on and so on. When the screen is on, I am not able to unlock (I can't enter the PIN quickly enough, and I can't use fingerprint unlock after reboot - see the attached video). I can't access the settings or any other apps to change the wallpaper, nothing. After the screen turns on and off multiple times, the phone reboots to recovery and tells me that my data may be corrupt and that I may want to factory reset the device. I get an option to try again or to perform a factory reset. Trying again results in the same scenario. Factory resetting is not an option, I've got valuable data on my phone (although I guess I will have to factory reset it, eventually... but I'm never getting a Pixel phone again after this experience).

The only thing I can do in the SystemUI crash loop is holding the power button and accessing the power menu. From there I can either turn the phone off, reboot, or perform a safe boot by holding the power off button. Neither helps. After turning the phone on (no matter if its safe boot or not), the wallpaper is still the same and the phone still crashes.

What am I supposed to do? Are there any options? Can I change wallpaper via ADB (although I'm not sure whether I can even access ADB without unlocking the phone)? I can't clear Pixel Launcher or Google Wallpapers app data via ADB without root permissions (or without custom recovery with built-in file explorer), right?

The only thing I can think of is waiting until tomorrow, if the daily wallpaper refreshes to something that won't crash my phone. But I'm not sure if the Wallpapers app even launches and does some background work when the phone is not unlocked.

https://drive.google.com/file/d/1kMSE28m2f1EFASsoiorMFTmX_QXbqjpx/view?usp=sharing (20200507_110118.mp4)

I just had this happen to me this morning, which makes it 3 times in the past month or so. Also was using daily wallpaper feature (cityscapes, in case that matters).

This has been happening to me. Three times in the last month I've had to do a factory reset. Only thing I have changed recently is I'm now using the daily wallpaper feature - cityscapes. Hopefully disabling this feature will resolve the issue. Come on Google wallpapers shouldn't brick a phone  

Woke up to this issue AGAIN. That makes 4x in the past 6 weeks. Pixel 2 XL using the daily cityscapes wallpapers.

I managed to recover from this issue with with ADB and a simple app I wrote, no need to do a factory reset (if you have access to ADB): https://www.youtube.com/watch?v=1tvpSxVCqRU

In the linked video, there are exact steps how to reproduce the issue (and how to recover from it). Please, someone from Google, have a look at it so that you know how to reproduce it, and then please fix this finally. This is unacceptable, you can't keep an issue like this in production opened.

Perfect! Thank you for doing the testing and reproduction of the issue, since Google didn't seem willing, even after we narrowed it down to the Cityscapes wallpaper. Will they read this considering the status is closed, or should this info be resubmitted as a new issue?

Hello Team Pixel,

Thank you for taking the time to report this issue. We have removed the wallpaper in question from the app and will roll out a preventative fix in a future Android release.

Pixel Community Team

Thank you! At least it's finally getting fixed rather than being forgotten about

pitching in to say I'm still getting wallpaper resets when using the earth live wallpaper, several times a week

How to fix this, pixel 4 also got this issue