Android 14 beta 2.1 causes serious camera issues on Google Pixel models

Update (05/27/2023) – by DT

O Google released Android 14 beta version 2.1 this week to fix some bugs present in the operating system. However, it seems that the update has broken an important feature of the Pixel series smartphones.

According to reports from several users, the cameras of the Google Pixel models were adversely affected after installing the new Android 14 trial version. Owners of the devices speak of crashes and instabilities when taking pictures.

“I spent about five minutes taking a photo as it crashed, froze and couldn’t save the photo. Everything else in the beta seems to be working fine, but I use my camera a lot so this is very detrimental to my daily use,” reported Redditor Brent_Fournier69.

Another Reddit user said that the Pixel 7 Pro camera app update caused the problem. He said: “It worked fine for me yesterday but there was an app update for the camera. Today it freezes when you try to take pictures.”

Another user pointed out that forcibly stopping the app and clearing the cache twice can fix the problem. To do this, just go to Settings > Apps > See all apps and scroll down to the Camera app.

The user is then redirected to an app information page. There are three options in the bar under the camera app icon: Open, Disable, and Force Stop. Just select Force stop. On the same page, just tap “Storage & Cache” and then tap “Clear Cache”.

Google has not commented on this bug, but an official fix should be released soon.

Update (05/25/2023) – by DT

Android 14 Beta 2.1 is released with fixes for major system bugs

This Thursday (25) Google released the beta version 2.1 of Android 14. The new build adds a number of fixes for major bugs that affected the company’s mobile OS in Beta 2 and didn’t bring big news.

The new released version of Android 14 Beta 2.1 is UPB2.230407.019 and it adds May security patches to Pixel 6, 6 Pro and 6 devices which were previously stuck in April security update.

The release notes aren’t particularly exciting for this release, but they do include fixes for a bug that prevented some users from opting out of the beta program and having to update the device to get out of the test build.

It’s worth mentioning that Android 13 QPR3 is still in a beta program, which should be released as a stable update next month. The stable build of the system for all users is scheduled to be released in the 2nd semester.

The full release note is below:

Today we are sending out an Android 14 Beta 2.1 Patch UPB2.230407.019 which includes the following fixes:

Fixed an issue that prevented users from completing device setup after opting for a device running a beta version of Android 14 from the beta program. However, this fix is ​​not backwards compatible, so users who wish to exit the beta program should do the following before exiting:

Update your device to Android 14 Beta 2.1 via the over-the-air (OTA) update prompt or by downloading an OTA image and applying the update manually.

If your device is not yet part of the beta program and is experiencing this issue, please follow the steps above and download Beta 2.1.

Reset the PIN, pattern, or password used on the device by navigating to Settings > Security & privacy > Lock screen. You can use the same PIN, pattern, or password as before, but you must follow the setup flow.

Opt out of the beta program by following the instructions for the question “How do I opt out and revert to a public version of Android” in the FAQ section of the Android beta program page. If your device is not registered, you can download public Android 13 images.

Fixed other issues that could cause the battery level to show as 0% regardless of the device’s actual charge level. (Issue #281890661)

Fixed issues that sometimes caused audio to drop out through the device speakers. (Issue #282020333, Issue #281926462, Issue #282558809)

Fixed system stability issues that could cause apps or the device to crash or crash. (Issue #281108515)

Fixed an issue with always-on display mode when using a device running Android Auto. (Issue #282184174)

Fixed an issue that sometimes caused the Google Photos app to crash when trying to open certain photos.

Fixed an issue where, with gesture navigation enabled for a device, putting a video into picture-in-picture mode in the Google TV app would cause the picture-in-picture window to disappear even though the playback resumed and the audio continued.

Fixed an issue that caused the Google Contacts app to crash when managing account settings.

Fixed an issue where the Google Messages app icon for notifications would not appear when always on mode was enabled.

For more information, see our release notes. Also, check out the current list of top open issues reported by developers and users.

How to get Android 14 Beta 2.1 patch?

If you are currently enrolled in the Android Beta program, you will automatically receive an over-the-air (OTA) update to Android 14 Beta 2.1. Eligible devices include Pixel 4a 5G, 5, 5a, 6, 6 Pro, 6a, 7, 7 Pro series devices. If your registered device is still running Android 13 QPR3 Beta and you choose not to upgrade to Android 14 Beta 2.1, you will continue to receive QPR3 Beta updates as they become available.

If you haven’t registered yet and would like to join the Android beta, visit

Note: It may take up to 24 hours before you receive the OTA update on your device. You can check for updates by going to Settings > System > System updates.

Original text (05/22/2023)

Cloned apps can be hidden in work profile in Android 14 Beta 2

A new feature in the beta version of Android 14 may be of great interest to those users who use the system for both personal affairs and corporate profile management.

First of all, it must be remembered that in the first visualizations of the system, app cloning was revealed. In February, Android expert Mishaal Rahman gave an insight into Google’s implementation of app cloning for Pixel. Now, Rahman has rolled out an update to the feature, with a new option that allows users to hide cloned apps from their work profile.

Rahman says the feature is enabled with the ENABLE_APP_CLONING_CHANGES_IN_LAUNCHER flag. This makes it possible to use a secondary login for an account just for your personal profile.

The February update’s main complaint, namely the inability to differentiate between standard app icons and cloned app icons on your personal profile home screen, still lingers. This is happening even though an icon for cloned apps is highlighted on the App Cloning Settings page, but the issue should be fixed in future updates.

If app cloning is widely available, it should be accessible under Settings > Apps > Cloned Apps. Google creates a “cloned user profile” when an app is cloned, and users must set up their password and other information when they access the cloned app for the first time.

Google’s next major software release could also bring a host of other changes, such as a vastly improved screen recording experience and separate sliders for ringtone and notification alerts. The current version of Android 14 Beta 2 also includes many bug fixes and some developer-oriented updates are scattered.