In this guide, we will show you the steps to fix the Wallpaper & Style crashing issue on Android 14 Beta 1. Google has recently rolled out the first beta build of its fourteenth iteration of the OS. And with that, there are a few noteworthy and intriguing features that you are likely to welcome abode. But since it is still in the testing phase, a handful of bugs and issues are along the obvious lines as well.
In this regard, numerous users have voiced their concern that the Wallpaper & Style section is crashing on their Pixel device running the latest Android 14 Beta 1. We generally interact with this page to change wallpaper, change Mateiraul You themes, enable Dark Mode, change App Grid, or enable Themed Icons. And as of now, the latter [Themed Icons] is the culprit behind this issue.
So if you had already enabled Themed icons before updating to Android 14, and have since updated to this latest OS, then you wouldn’t be able to access this section, neither from the Settings menu nor via the long press on an empty region on your home screen. With that said, we did manage to find a nifty workaround that should help you rectify this issue. So without further ado, let’s check it out.
Fix Wallpaper & Style crashing On Android 14 Beta 1
[UPDATE: Google has now fixed this issue in Android 14 Beta 1.1] In order to rectify this issue, you’ll have to delete the data of the Pixel Launcher. However, do keep in mind that doing so will remove your customized launcher settings as well. If that’s too much to ask for, then you should probably wait for a few days [or even weeks] until the Silicon Valley giant rolls out a fix. But if you are ready to proceed ahead, then here’s what you need to do:
- Head over to Settings > Apps > All Apps > Pixel Launcher.
- Then go to Storage and Cache and tap on Clear Storage.
- Now tap on Delete in the confirmation prompt that appears.
That’s it. This should fix the Wallpaper & Style crashing issue on Android 14 Beta 1. As far as the official stance on this matter is concerned, the developers might be aware of this issue, but they haven’t given out any ETA for the rollout of a fix. As and when that happens, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.