Google’s pushed its Android 13 beta to Pixel devices. And while it might be tempting to install the firmware, there are a number of Android 13 beta problems impacting Pixel owners right now.
The official Android 13 release date will land sometime after July, but you can give the new operating system a try right now if you own a Pixel 6, Pixel 6 Pro, Pixel 5, Pixel 5a, Pixel 4a, Pixel 4a (5G), Pixel 4, or Pixel 4 XL.
The Android 13 beta lets users try out new Android 13 features ahead of time. It will also help Google squash bugs and performance issues ahead of the final release.
While you might be weighing a move away from Android 12, beta software isn’t for everyone. The beta is pre-release software and early software is often buggy. In fact, Google’s already called out several issues on board the beta. Some of these issues are minor, others might convince you to stick around on Android 12 for a bit longer.
If you’re debating a move to the Android 13 beta, you should be familiar with these issues before you install the software. And if you’re already running the Android 13 beta on your Pixel, you should keep an eye out for problems. If you do run into issues, you should report them to Google so the company can improve the final product.
- Android 13 Beta Problems
- How to Report Android 13 Beta Problems
- How to Fix Android 13 Beta Problems
- Where to Find Android 13 Beta Feedback
- What’s Next
In this guide we’ll take you through the current state of Android 13 beta problems, provide you with potential fixes, show you where to find feedback about the Android 13 beta, and show you how to report issues with the beta.
Android 13 Beta Problems
The Android 13 beta could have a huge impact on your Pixel’s performance. While some of you might see improvements, others will run into issues.
Google’s highlighted several potential issues with the current version of the Android 13 beta (Android 13 beta 2). Right now the list includes:
- This release might have various stability, battery, or performance issues on supported devices.
- For users with accessibility needs, this release might not be appropriate for daily use.
- Some apps might not function as expected when running on this release. This includes Google’s apps as well as other apps.
- On some devices, unlocking the phone with a fingerprint while the Always On Display option is active causes the entire screen to be tinted green temporarily.
- When a user checks for system updates by navigating to Settings > System > System update, the system incorrectly reports Android 12 as the device’s Android version, even when the device was already successfully updated to an Android 13 build. To work around this issue, check the device’s Android version by navigating to Settings > About phone.
- In some situations, the system shows a runtime permissions dialog out of context, asking the user to grant the notification permission on behalf of another app.
- On some devices, bright sunlight prevents the fingerprint reader from authenticating the user.
- Apps using OpenSSL version 1.1.1b through 1.1.1h may not work on some ARMv9 devices. This issue is also present on some ARMv9 devices running Android 12.
- In some cases, typing in the Search bar results in a blank list of suggestions.
- On Pixel devices, swiping on the all apps search result page can sometimes cause the Pixel Launcher to crash.
- On Pixel 6 and Pixel 6 Pro devices, the Now Playing page sometimes gets stuck on Downloading song database.
- The camera app crashes occasionally on Pixel 6 and Pixel 6 Pro devices.
- In some cases, Maps on Android Auto might not be able to access the user’s location. If this happens, you can restore location access by opening the Android Auto settings.
- For some users, wireless projection initiation might get stuck at the Looking for Android Auto… notification. If you encounter this issue, please reboot your phone.
- When Bluetooth headphones are connected, AV playback on some apps does not work.
- In some cases when trying to pair Bluetooth devices, pressing the side button on the ADT-3 device does not activate a Bluetooth device search. If remote pairing is lost, you can work around this by using ADB commands to simulate remote input. Alternatively, you can reflash the unit.
- Remote control buttons can’t be reconfigured using the Remote & Accessories menu.
- The option to change HDMI-CEC control is currently missing from the Remote & Accessories menu.
- When casting to 4k TVs, only the top left quarter of the image is shown.
- In some cases when the ADT-3 device is connected to an LG TV, the remote control does not work.
- When using the Google Play Movies app, 4K playback is corrupted by a gray screen and noise.
- For iOS devices, the Google Home app fails to connect to the ADT-3 device. To work around this issue, use the Google Home app on an Android device or the ADT-3 remote control.
You can learn more about these issues, and others, over on Google’s IssueTracker website.
How to Report Android 13 Beta Problems
If you run into bugs or performance issues on the Android 13 beta, you’ll want to report back to Google. Your feedback will help the company identify, and potentially fix, issues before the official version of the operating system arrives.
There are a few different ways to send feedback about Android 13’s performance. Google recommends sharing feedback on the Android Beta Reddit.
You can also share feedback directly with Google via the Android 13 Issue Tracker and the Android Beta Feedback app. You can learn more about those over on Google’s website.
How to Fix Android 13 Beta Problems
If you encounter an issue with the Android 13 beta you can’t rely on Google to fix the issue. The company won’t release new Android 13 builds every week and there’s no guarantee the next release will have a fix for your problem.
If you want to stay on the beta and don’t want to wait for Google, you’ll have to try and fix the issue(s) yourself. Our list of fixes for the most common Pixel 4 problems is a great starting point.
If you’re having trouble installing the Android 13 beta on your Pixel device, you’ll want to check out Google’s guide for advice.
If the issues become too frustrating, you can move your phone off of the Android 13 beta. However, you won’t be able to unenroll from the beta and go back to a public release until you’ve wiped all locally saved data on your device. Google also notes that you might encounter issues restoring a backup.
Where to Find Android 13 Beta Feedback
As we push away from the Android 13 beta’s release, you’ll want to monitor feedback from early adopters.
Short-term feedback about the software is useful, but you’ll also want to make sure you dig into long-term feedback from beta testers if you’re on the fence about making a move from Android 12 to Android 13 beta or from one version of the Android 13 beta to another.
Google says the next update for the Android 13 beta, Android 13 beta 3, will arrive in June. The company hasn’t specified a date yet.
Android 13 beta 4, which is a near-final build for final testing, will land in July while the final release will land sometime after that.
Install macOS Monterey 12.4 for Better Security
If security is important to you, think about installing the macOS Monterey 12.4 update right away.
macOS Monterey 12.4 delivers a whopping 50+ new security patches. These will help protect you and your device from harm.
If you're interested in exactly what Apple's patched up, you'll want to head on over to the company's security site.
As for older macOS updates, macOS Monterey 12.3.1 brought two security patches to Mac users. You can read more about them over on Apple's website.
Apple's macOS Monterey 12.3 update had 40+ security patches on board. If you want to learn more about these upgrades, you can check the particulars over on Apple's security site.
The macOS Monterey 12.2.1 update brought an important patch to Mac users. You can learn more about the patch over at Apple's security site.
Apple's macOS Monterey 12.2 update had 13 security patches on board. If you're interested in the details, head on over to Apple's website to learn more.
macOS Monterey 12.1 included 40+ new security patches to Macs. You can read all about them over on the company's security site.
Microsoft says it discovered a new 'Powerdir' vulnerability lurking in macOS. Powerdir allows "an attacker to bypass the operating system’s Transparency, Consent, and Control (TCC) technology, thereby gaining unauthorized access to a user’s protected data." Fortunately, Apple patched up the issue in macOS Monterey 12.1.
macOS Monterey 12.1 also included some important upgrades to privacy. The software delivered Apple's communication safety features for kids. You'll find these features in the Messages app, in Siri, in Spotlight, and in Search.
If you're moving up from macOS Big Sur, you'll also get macOS Monterey 12.0.1's 30+ security patches when you update. If you're interested in the exact nature of these improvements, you can read about them over on Apple's website.
In addition to those patches, the macOS Monterey update comes with additional security and privacy upgrades.
If you're an Apple Card user, you'll now get a security code that changes regularly to use when you make online transactions.
Apple's also included a built-in authenticator that's similar to Google Authenticator. This will let you generate verification codes for enhanced sign-in security under your Passwords.
New Mail Privacy Protection helps prevent senders from tracking your Mail activity and there's a new recording indicator in Control Center for apps that are accessing your mic.
As an Amazon Associate I earn from qualifying purchases.