7 worst Android 16 beta bugs so far

Android 16 is on the way. Google has confirmed that the next major Android update is on the right track for a June 2025 version, earlier than any recent version of the software. However, you can already install the Android 16 Beta. Android 16 Beta 1 was launched in January, and we can expect several updates before the stable update in June.

The installation of a beta version of Android has always been a risky proposal. These beta versions are a chance for Google to test construction in nature and discover the main bugs before the stable version. But Android 16 is not different from the previous Android versions, its beta constructions launched with a plethora of bugs that affected the Android experience in a subtle and significant way. Here are the worst Android 16 beta bugs that we have seen so far.

You have to press your screen frantically to modify the theme of your phone

In Android 16 Beta 2, press one of the color palettes in the Wallpaper & Style menu (consulted by pressing and holding your home screen, or via the Settings application) would not immediately change the theme of your phone. We tested this bug and found that we had to press about 25 times on a color palette icon before the phone recorded the switch.

This bug occurred if users had thematic icons activated or not. Although thematic icons are always in beta version (and therefore more likely to have bugs), the wallpaper theme theme switch has been a stable feature from Android 12. You cannot reliably change the theme of the wallpaper in Android 16 Beta 2 while heading in the system of the system colors, as indicated in the higher GIF on the left above. Restarting the device has not resolved this problem.

6

Telephones have ignored the battery limiter adjustment to 80%

Pixel phones always charge 100%

Since November 2024, Pixel phones have a functionality that allows you to prevent the battery from invoicing more than 80%. This feature slows down the battery degradation, which is crucial for people who wish to keep their phone as long as possible. However, Android 16 Beta 2 broke this functionality and made this parameter completely useless.

If you activate this feature in Android 16 Beta 2, your phone’s battery would always take care of 100%. Sometimes, phones with this activated feature will be loaded 100%, but it is an intentional aberration designed to recalibrate the estimated battery capacity. This bug meant that your phone was charged 100% each time. Completely emptying or restarting the phone has not resolved this problem.

5

Telephone calls restored random phones

However, the bug was limited to Pixel 7 devices

Many Pixel 7 users on Android 16 Beta 1 reported that their devices reddead randomly in the middle of the call. Worse, the problem is not identical on all devices. A user noted that his phone restarts four out of five phone calls and that the problem seemed to appear around five minutes. Another user reported that after restarting, their call logs had been deleted. Another has further reported that their phone would restart at random moments during calls. Whatever the specific symptoms, this bug made people unable to use their phone for minutes at a time.

This bug affected Pixel 7A, Pixel 7 and Pixel 7 Pro devices. Interestingly, this bug appeared for the first time last year and was crushed as part of the Android 15 QPR2 Beta 3 update in January 2025. Android 16 Beta 1 seemed to have broken this fix. Google marked this bug as a high priority due to the impact he had on personal and professional calls of people.

Intelligent house controls were inaccessible

For many users on Android 16 Beta 1, the Google Home app refused to open. The Google Home widget also refused to operate, displaying the error message “The widget is not supported”. This left people unable to access their intelligent house orders. Whatever method you have used to open the Google Home application, it would crash or refuse to open each time.

This bug could be temporarily resolved by resetting the Google Home application, but we found that the bug reappeared shortly after. Others have managed to correct the bug by stifling the application and cleaning the cache.

The emission of commands to Google Home via Google Assistant or Gemini seemed to bypass the bug, but users could not issue commands that, and not open the application. This bug was relatively rare because most people said that the Google Home app worked well for them.

3

The Google Files application crashed when opening a PDF file

Fortunately, the bug was limited to the Files application

Android 16 beta 1 users have indicated that the Google Files application would block each time they were trying to open a PDF file. The application would block immediately when selecting a PDF file to open; The preview of the document would not appear.

We have reproduced this bug on a Pixel 8, and hundreds of other users reported this bug on various pixel phones running Android 16 Beta 1. For some users, erasure of the cache and storage of the application resolved the problem, but for us, this method only worked for the first PDF file that we opened.

This bug was limited to the Google Files application. Other applications, including Google Drive and third -party file manager applications, could open PDF files very well.

2

Navigation of broken gestures on third -party launchers

The pixel launcher was slightly more stable

Pixel users who used a third -party launcher noticed that Navigation on gestures was broken on Android 16 Beta 1. This bug prevented users from switching between applications by sliding on the navigation bar, forcing them to find the application in the application drawer instead of a quick blow and press. The animation of the transition to a recent application would appear, but the user was sent to the home screen instead of the selected application.

This bug was predominant on third -party launchers, but users of pixel launchers also encountered it. Microsoft Launcher, Lawnchair, Niagara and Nova Launcher users said the bug disappeared when they returned to the pixel launcher. A few Original pixel users have declared this problemAlso, but the majority of users meeting this bug used third -party launchers.

Fortunately, there was an easy solution

Some users have reported that The police colors were broken In the quick settings menu on several pixel peripherals running Android 16 Beta 1. The time and date font was illegible because their dark gray font mixed in the black background.

Fortunately, it seemed that this bug could be corrected by passing the phone in dark mode, then restarting it. After deactivating the dark mode, the text of the quick parameters was returned to normal.

Install the Android 16 beta at your own risk

Some of the bugs, such as random restarts during telephone calls and the Broken Google Home application, have caused major problems to users. These are excellent examples of the reason why we do not recommend installing Android 16 Beta on a device that you use regularly for important calls.

However, do not take these bugs as a sign of a disastrous launch of June. The beta version of Android 16 is about as stable as recent beta versions and, with the exception of the stubborn bugs of Android 15, the stable mainly launches these bugs.