Robert Triggs / Android Authority
TL;DR
- Google appears to have overlooked a bug in Android 15 that affected the wallpaper-based theme system.
- As a result, users get fewer unique wallpaper color options and some duplication.
- This bug was first discovered in the beta release, but was also reflected in the stable build.
The rollout of Android 15 for Pixel devices doesn’t seem to be going as smoothly as Google had hoped. In addition to missing some of the touted features in this update, we’ve also seen some reports of Pixel users facing annoying bugs in the Instagram app. Google has confirmed that the missing features will be rolling out to users in the coming weeks, and Instagram has already released an update to fix issues with Stories, but the latest Android release includes Google There is one bug that doesn’t seem to have gotten much attention.
There is a small issue with Android 15’s wallpaper-based theme system. This affects the Wallpaper Color carousel in the Wallpaper and Styling settings on Pixel devices. This carousel lets you choose color combinations for your theme’s icons, text, and other UI elements based on your current wallpaper. Instead of being able to choose your own color combination, the carousel will display several duplicates.
The attached screenshot shows overlapping color combinations on both ends of the carousel. Switching to a different wallpaper changes your selection, but all you get is a few unique options and a ton of overlap. Google was aware of the issue when it was first discovered in the fourth beta release of Android 15 in July, but the stable build that rolled out to Pixel devices earlier this week still has Exists.
According to an entry in Google’s Issue Tracker, the Google employee responsible for the bug concluded that the feature was working as intended. However, carousels offer more unique color combinations, and there were no duplicates in previous Android releases.
Unfortunately, the entry in the issue tracker is given a “Not fixed (intended behavior)” status, so it doesn’t appear that a fix is in progress. Another entry for the same issue states that someone is still assigned to the bug, but Nothing has been updated since August.
We reached out to Google for comment on this matter and to confirm whether this is indeed intended behavior or a bug. We will update this post as soon as we know more.
