Android 14 beta 2.1 is out with a bunch of new fixes but there is a nasty camera bug that you should be ready to face right after the installation. As per the information, the new firmware is causing glitches with the Google Camera app for Pixel devices.
Yes! As one upgrades to the new Android 14 beta 2.1, the camera app freezes and breaks suddenly while switching to an ultrawide lens, due to a crash bug. Some users further said that the swap to ultrawide mode was perfect. However, the problem occurred when returning to the primary lens.
Flashing more light on this concept, a Redditor said that while everything seems fine with this beta build, the camera app is constantly troubling with frequent crashing and freezing.
“Just spend about 5 minutes trying to capture a photo cause it was crashing, freezing, and not saving the photo. Honestly might roll back to stable and go through the effort of resetting. Everything else about the beta seems to be working fine, but I use my camera quite a bit so this is very detrimental to my everyday usage.”
That’s not it! The crash also appears in the video mode where you may find a pop-message saying a part of the last recording may not have been saved. Consequently, after installing the beta build, the camera app demands a 300+MB update. But this action did not help users with a fix to the respective bug.
Temporary Fix
Voila! There is a quick fix that can aid you with this trouble. All you have to do is, when opening the camera app, just switch to portrait mode and then back to standard. This will stop the crash no matter how many times you switch between primary and ultrawide lenses.
Follow our socials → Google News, Telegram
On the flip side, a user on Reddit mentioned that a force stop and clearing the camera cache can help as well. All you have to do is, visit the Settings menu > Apps and select the Camera. Go to the info page and tap on Force Stop.
Meanwhile, you can try reverting to Android 13 which brings you on a stable platform. Though we expect that the company will soon release a fix to this issue in the coming days.
(Source)
