With QPR1 now stable, Google is rolling out Android 13 QPR2 Beta 1 as the next sizable Pixel update that will be released in March.
There should only be two Quarterly Platform Release betas for Android 13 if what Google telegraphed in August stands. Like QPR1, that should mean three QPR2 betas with a stable launch in March 2023 and a relatively bug-free experience for those that sign-up via the Android Beta Program.
If you’re still part of the Beta Program from testing Android 13 QPR1 you can unenroll from google.com/android/beta without a device wipe if you have not yet installed QPR2 Beta 1.
If you have already updated, leaving the program will result in a wipe and your next opportunity to exit without losing data will be in March after the stable launch of Android 13 QPR2.
The Android Beta Feedback app is available on Pixel phones to submit problems. You can access it from the app drawer or via Quick Settings to file bugs in the Google issue tracker, while the Android Beta community is on Reddit.
The following known issues exist:
Android Platform
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a “Settings keeps stopping” message and then the system Settings app can’t be opened.
An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps
After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between the 1/8x and 1/4x while in Slow Motion mode.
Android 13 QPR2 Beta 1 system images are available for the Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, and Pixel 7 Pro. as well as in the Android Emulator.
Most users will be installing Beta 1 (T2B1.221118.006) with the December security patch from the Android Beta Program website. You can expect an OTA update in the coming hours. If you need help, here’s our full guide on installing Android 13.
You can now share your car key in Apple Wallet with Android users,
starting with Google Pixel
If you happen to be an owner of one of the very few cars on the market with Car Key support, you are now able to share that car key credential with non-iPhone users for the first time.
Apple is working with the IETF and industry members to standardize cross-platform car key sharing. The first implementation of this support has landed today for Google Pixel owners. Google is working on rolling out support for all Android 12+ devices soon.
The Car Key feature allows Apple Wallet to treat unlocking your car in the same manner as you can conduct contactless payments with Apple Pay: Walk up to your car and then present your iPhone or Apple Watch to unlock it.
You can share car keys by using the Share button inside the Wallet app. You could previously send the key to other iPhone users. On iOS 16.1 or later, the Wallet app generates keys that also work with other supporting platforms, most notably Android users.
Share using the system share sheet with your favorite app like Messages, Mail, and WhatsApp. You can secure the process using an optional one-time code.
At any later time, you can revoke access to a shared car key. Simply open the Wallet app, select your car key and tap on the People icon to manage the current list of shared keys for that vehicle.
Apple’s partnership with the IETF was first announced at this year’s WWDC. The group is still working on a final specification to make publicly available for adoption by anyone. But for now, only Apple and Google have access to the necessary protocols and are working on the respective implementations privately.
It’s a really cool technology that furthers Apple’s goal to replace the wallet in your pocket, alongside other initiatives like Digital ID and Apple Pay. Hopefully, more Car Key compatible vehicles will be available soon.
Apple releases iOS 16.2 beta 4 to developers ahead of expected launch this month
Following the release of iOS 16.1.2 to iPhone users on Wednesday, Apple released iOS 16.2 beta 4 to developers on Thursday. Along with iOS 16.2, Apple has also been testing new betas for watchOS 9.2, tvOS 16.2, and macOS Ventura 13.1. Read on as we detail what’s new in these updates.
iOS 16.2 and iPadOS 16.2 include some notable changes. The Freeform collaboration app is now available to iPad, iPhone, and Mac users. There are also changes to the Home app, updates to the Weather app, and more.
On November 28, Apple also released a “Rapid Security Response” update for users running iOS 16.2 beta. Once the feature becomes available to everyone, Apple will be able to quickly fix security exploits without having to release a new version of iOS just for this.
In addition to iOS 16.2 beta 4, Apple has also made the following updates available to all developer beta testers:
It’s no secret that Pixel phones – especially the Pixel 7 and 7 Pro – take downright fantastic photos. Of course, it’s always nice to have RAW images so you have a little more freedom in your editing process. This guide will take you through enabling RAW file picture capture on your Google Pixel.
No matter what device you shoot on, your final image will generally come out as one of two file formats – JPEG or RAW. Of course, we’re all familiar with JPEG files, which produce a perfectly fine photo. The caveat is that they’re lossy and stripped of all the surrounding detail and data that would make editing easier. With that, though, they’re incredibly easy to store and share without sacrificing much storage space.
On the other hand, a RAW photo is lossless and keeps a lot of that captured data available, making editing much easier. A RAW file on your Google Pixel – or anywhere for that matter – allows you to make greater adjustments without sacrificing overall detail. With that, a RAW file is much larger, and having many stored on your device can definitely bog it down and soak up space. On top of that, it isn’t widely supported as a readable file format without first being converted.
Related: Here’s what every camera on the Pixel 7 Pro does
Of course, if you don’t plan on doing heavy editing with your Pixel’s photos, there wouldn’t be a need to also capture RAW images. For those that do plan to, the Pixel 7 and 7 Pro are newly supported devices in Adobe’s RAW catalog, which means color profiles are supported from those devices. The Pixel 6 and 6 Pro are supported as well.
How to take RAW images on your Pixel
The Pixel’s stock camera app allows you to operate in a mode called RAW + JPEG, which will take both JPEG and RAW pictures on your Google Pixel. This option will inevitably take up much more space on your device, though if you plan on exporting the RAW images, this shouldn’t be an issue.
Enabling the feature is pretty easy and takes a quick setup. After that, you can toggle the RAW + JPEG option on and off.
On your Pixel, open the camera.
If you haven’t changed the default method, you can double-tap your power button.
Tap the camera settings drop-down button at the top.
Hit More settings.
Tap Advanced.
Toggle on RAW + JPEG control.
Now, when you open the camera settings drop-down menu, you can tap RAW to get both RAW and JPEG images.
Taking RAW pictures on your Pixelwith this option enabled will result in an additional folder appearing in your Google Photos library called “Raw.” That folder is where you can find all of your RAW images to export or edit.
Tip: Don’t set the “Raw” folder to automatically back up to the cloud. This will eat your storage up like there’s no tomorrow.
How to export RAW images
If you plan on editing your RAW pictures elsewhere such as Adobe Lightroom, you’ll want to export your images. There are several ways you can do this without losing any image quality. Our suggestion would be to upload them to Google Drive to maintain quality and download them to the device you’re editing with.
If you plan on editing from your Pixel, you don’t have to export. Simply select images in your editing app from the Raw folder in your library and you’ll be able to tune them how you like.
Open Google Photos.
Tap Library.
Select the “Raw” folder.
Open an image or select multiple and hit Share.
As mentioned, you can use Google Drive to upload your images if you wish. Doing it that way will keep your files at full size until you download them and edit them down.
Overall, the RAW image feature on Google’s Pixel lineup comes in handy. With newly supported RAW files from the Google Pixel 7 and 7 Pro in Adobe’s suite, it’s a little easier to edit those fantastic Pixel images.
Google’s Pixel 7 and Pixel 7 Pro are important phones for a few reasons, but one of the biggest is how they support apps. As it turns out, the Pixel 7 series delivers the first Android phones that block support for apps that aren’t 64-bit. What does that mean for you? Let’s discuss.
It’s been no secret that Google has been working toward a future where Android is a 64-bit operating system, as opposed to one that still supports 32-bit software. What’s the difference between the two? In short, a 64-bit operating system can access drastically more memory addresses, which leads to improvements on both performance and security. Google boasted speed improvements to Chrome for Android, for instance, when it moved to a 64-bit build.
Android made the move to support 64-bit apps in 2011 with the launch of Android 5.0, but the platform has always supported 32-bit apps in the years since. It was in 2019 that Google moved to make 64-bit support a requirement for all apps distributed through the Google Play Store, Android’s primary source of apps, with the Play Store later ending serving apps that either didn’t support 64-bit or didn’t have a 64-bit version.
Now, Google is taking the next step by releasing the Pixel 7 and Pixel 7 Pro with 64-bit only support for apps, but not through a firm block.
As Mishaal Rahman confirmed, the Pixel 7 series only supports 64-bit apps. The devices are not running on a 64-bit only version of Android, though, instead only blocking the installation of 32-bit apps with a message “app not installed as app isn’t compatible with your phone” appearing when a user attempts to install a 32-bit app.
What does this mean for you?
In theory, Google’s change to supporting exclusively 64-bit apps on the Pixel 7 series should have no noticeable impact on your experience.
This is largely because of the groundwork Google has laid out over the past decade on building up support for 64-bit in Android. One of the only apps that comes to mind as a 32-bit only app is the flash-in-the-pan hit Flappy Bird, which hasn’t been updated since the game’s monumental success and still-shocking closure. Rahman also points out that a version of the Pebble smartwatch app doesn’t support 64-bit, which means that the older smartwatches, which are technically still functional, though unsupported, can’t be paired to Google’s latest Pixel phones.
Notably too, there’s also a potential positive from this. Rahman claims that benchmarks for power efficiency and performance on devices with more than 4GB of RAM jump by 5-10%.
Meanwhile, Google’s Pixel Tablet is expected to be the first Android device that is truly 64-bit only, as Android 14 may make that move further for other devices.
Most devices have some sort of battery saver mode, while Google’s Pixel lineup comes with an “Extreme Battery Saver.” So what is it, and what makes it extreme? This guide will take you through it.
On most Android devices, battery saver works in a very similar way. Unnecessary processes are turned off in the background, your screen’s refresh rate slows down (even to the point of turning off variable refresh rate entirely), and your phone switches to a dark theme to save energy. You might also experience the lack of certain features, such as the always-on display.
All of these limitations combined significantly improve your batter’s efficiency, and battery saver mode can mean the difference between a dead phone in two minutes or an extra 25 minutes of power, roughly speaking.
So what is the Pixel’s Extreme Battery Saver?
Beyond the regular battery saver, the Pixel’s Extreme Battery Saver is an added layer of battery efficiency. In fact, in order to use the latter, you need to initially have battery saver active.
Once it is, you can access the extreme version, which goes beyond turning off a couple of features. Rather, Extreme Battery Saver turns off most of your apps and completely pauses notifications from them. In essence, most nonessential apps completely halt background usage.
This feature is used for pretty dire circumstances and can get you even more battery life when you really need it. While you can’t access most apps during Extreme Battery Saver mode on the Pixel, you can choose to classify some apps as essential. After doing so, those apps become usable while the limitation is turned on.
How to turn it on
Before turning it on, you need to adjust a couple of settings that specify how you use it.
On your Pixel, head to your settings by swiping down twice and hitting the settings cog.
Tap Battery.
Hit Battery Saver.
Select Extreme Battery Saver.
Choose when to use it – you can choose to have it turn on automatically with regular battery saver or you can have your Pixel ask you first.
Choose your essential apps.
Note: Don’t go wild. The fewer apps you choose, the better your battery life will be.
Once you configure these settings, you can choose to have the extreme mode turn on after battery saver is initiated. The best way to turn the battery saver on is to access your Quick Settings on your Pixel and turn it on from there. We have a great guide on doing just that.
Google is preparing to expand Pixel’s support for showing At A Glance notifications from smart doorbells to also include alerts from Ring products.
About APK Insight: In this “APK Insight” post, we’ve decompiled the latest version of an application that Google uploaded to the Play Store. When we decompile these files (called APKs, in the case of Android apps), we’re able to see various lines of code within that hint at possible future features. Keep in mind that Google may or may not ever ship these features, and our interpretation of what they are may be imperfect. We’ll try to enable those that are closer to being finished, however, to show you how they’ll look in the case that they do ship. With that in mind, read on.
Over the course of this year, Google has put a significant amount of effort into the expansion of the At A Glance widget that is ever present on the homescreen and lock screen of Pixel devices. What originally started as useful reminders from Assistant and Calendar has become an all-in-one hub for things your phone thinks you might want to know immediately.
One such recent improvement was the addition of support for alerts from Nest Doorbells, indicating that someone is at the door and (if recognized by Familiar Faces) who it is. Now it seems Google is preparing to expand At A Glance’s support for smart doorbells to include third-party options.
As spotted in the latest release of Android System Intelligence — “T.5” which is notably the first non-beta update to the app’s Android 13 variant — the At A Glance widget is picking up support for doorbells from Ring. Since 2018, Ring has been owned by Amazon, but the company has been no stranger to Google’s ecosystem, offering full Google Assistant integration.
“Show who’s at the door when your Nest or Ring doorbell rings”
Where the existing integration with Nest is easily possible as the Google Home app is installed by default on Pixel phones, the upcoming Ring doorbell support will require that you have Ring’s app installed. Given the feature has so far only appeared in Android 13 builds of Android System Intelligence, it’s likely this particular integration won’t be launching until much later this year.
At A Glance has steadily expanded over the past year
The new tidbit comes as part of a broader movement by Google to integrate At A Glance with third-party apps and services. In recent weeks, we’ve seen preparation for the widget to support delivery notifications from services like Doordash and ETA alerts from ridesharing apps like Uber and Lyft.
For a patch, Android 13 Beta 3.2 contains many more changes than expected and we’re diving into everything new as a result.
Over the coming hours, we’ll dive into all of Android 13 Beta 3.2’s new features and every single change. (The newest updates will be at the top of this list. Be sure to check back often and tell us what you find in the comments below.) Beta 3.1 screenshots appear on the left and Beta 3.2 at the right.
Prep towards new Easter Egg
Tweaked Pixel Tips layout: More prominent highlights
Tweaks to Clipboard
Sharing is now done via the bottom-left corner overlay.
The share button is no longer in the full-screen editor. After making any edits and tapping “Done,” you’re taken back to the previous screen with the corner overlay still visible.
Pixel Launcher: ‘Always show keyboard’ in app drawer
Updated Google Lens icon
Google rolls out Android 13 Beta 3.2 to Pixel with several bug fixes
Following a patch last Friday, Google is back with Android 13 Beta 3.2 today to fix more issues on Pixel phones.
Google usually does not release more than one patch in-between major previews, but Beta 3.1 was required as a more pressing fix — coming only two days after Beta 3 — given the unavailability of the Beta Feedback app for new users.
At a high-level, Beta 3.2 includes the “latest bug fixes and improvements to stability and performance.” Five Android 13 issues are specifically addressed with this update:
Fixed an issue where the back gesture wasn’t working in some apps.
Fixed an issue where the At a glance settings page would collapse inconsistently when scrolling.
Fixed an issue where some apps would crash instantly on opening.
Fixed an issue where the microphone would turn on and off unexpectedly during unrelated use of the device.
Fixed an issue where the Google Photos app would crash frequently.
These problems are particularly application and user-facing, though we have not seen widespread reports of them.
Factory images for Android 13 Beta 3.2 build TPB3.220610.004 (versus TPB3.220513.017.B1 previously) are available now. On a Pixel 4a, the OTA comes in at 238MB.
After the main release and two patches, Google is now asking for feedback on Android 13 Beta 3 in a survey that’s slightly different from past versions by focusing on the search experience.
For starters, the survey is hosted on Qualtrics instead of Google Forms and asks for demographic information (age and occupation). It opened today and ends on June 28 at 5 p.m. PT.
This survey should take no longer than 10 minutes to complete. Please keep in mind that all questions and content within this survey are confidential and should not be shared with anyone.
This Android 13 Beta 3 survey is not limited to Pixel with various OEMs, including those that have not announced preview programs yet, listed:
Realme, Momo, Oppo, Samsung, Microsoft, Google Pixel, OnePlus, Motorola, Sony, and Nokia
After specifying the current build on your device, Google asks which “search box did you primarily use since using your device on Android 13”: Search widget on the home screen or All Apps Drawer search box. You’re able to select “Both.” Google wants to know whether Android 13 has changed your usage compared to Android 12. Listed capabilities include:
Apps not yet installed (i.e. Google Play store apps)
Settings
Apps (installed on your phone)
Google Assistant
Pixel Tips
Contacts
Content within Apps
Quick app actions (i.e. shortcuts)
Web content (e.g. websites, Google search results page)
Screenshots
There’s then a question about “how easy or difficult was it to find what you were searching for in the search box” with the ability to expand further via written responses; Google then asks you to compare the two search fields.
Likely to help improve the process of registering your fingerprint on devices with in-display readers, Android 13 Beta 3 has gained a new enrolment UI.
Of course, with the Pixel 6a and Pixel 7 series yet to be officially available, that means the new UI is currently limited to the Pixel 6 and 6 Pro. If you update a device which already has pre-registered biometric data, you may never actually see this new UI. However, when enrolling a fingerprint or thumbprint, during the latter stages of this process in Android 13 Beta 3, you will see a new animation and guides to help you get a better reading of your finger.
Given the bad press that the Pixel 6 and 6 Pro in-display fingerprint scanners have received, it’s likely that this new guidance and improved UI have been added to ensure better registration processes for all users. We do know that the upcoming Pixel 6a will utilize a different in-display scanner, but it remains to be seen if this new change will help alleviate the Pixel 6 series issues.
By adding a new fingerprint enrolment UI within Android 13, it makes it more obvious just when to begin adjusting your finger and add the extremities or edges. In Android 12, a text prompt alongside guide brackets are currently used, which are actually not entirely visible when pressing your finger on-screen.
Making this change to the fingerprint enrollment section within Android 13 could have major benefits for the upcoming Pixel 7 series, but could also help those with problems with their existing Pixel 6 series handset and ensure better unlock times when using the new unlock method.
While there is undoubtedly a lot of science that goes into making your Pixel water resistant, the ratings we currently see on our devices are not an exact science. Depending on what rating you see and what you’re told, it can get a little confusing. So is your Google Pixel waterproof or water-resistant? Here’s what you need to know.
What does your IP rating mean?
For every device, a dust and water resistance rating is released with it. It can range anywhere from IP00 to IP69K, with IP00 being unable to resist any dust or water in any capacity at all and the latter being completely water and dust-proof, even under pressure.
When it comes to smartphones, you’ll likely never see an IP00 rating simply because having an enclosure around the internals dictates at least some amount of water and dust resistance. More often than not, you’re looking at ratings around IP67 and IP68. So what does that mean?
Dust and solid object resistance
Well, the IP rating is split into two numbers – the first and second digit. The second number the first number after “IP” is the amount of resistance to dust and hazardous objects, with 6 being the highest. An IP6X rating means that your device is completely resistant to “dust ingress,” which basically means you don’t have to worry about dropping it in dirt and having any particle enter the enclosure of your Pixel. Most of Google’s Pixels have an IP6X rating, so this isn’t so much of a worry.
Water resistance
The second number after “IP” is the rating against liquid. Most devices now rate somewhere between a 6 and 8. If your IP rating is IPX6, your device is able to resist something equivalent to a harsh 12.5mm wide stream of water from any direction; where the line starts to get blurred is at IPX7 and IPX8. A lot of devices fall into one of these categories.
At IPX7, you’re looking for two qualifying resistance factors. The phone is able to withstand being submerged up to 1 meter for less than 30 minutes. At IPX8, your device can withstand more than 1 meter. Unfortunately, this could mean anywhere from 1 centimeter over a meter to 2 meters, with the exact rating being left up to the manufacturer.
Remember, these ratings are intended to represent water resistance, meaning the Google Pixel is not waterproof, only resistant up to a certain degree depending on the rating.
Rule of thumb
Since the latter rating is somewhat left up to the manufacturer to decide, here’s the general rule of thumb we recommend you exercise: if your Google Pixel has an IPX8 water resistant rating, avoid submerging over 1 meter anyways. Since this could mean that your device is protected at 3’1/8″, it’s much better to play it safe and pretend like you only have an IPX7 rating.
Does the IP rating stay the same throughout the Pixel’s life?
No. No, it does not.
Your Pixel’s IP rating, whether that’s IP67 or IP68, will not remain the same the whole time you have the phone – the rating is meant to represent what state the device is in when it left the factory. In fact, there are a few ways that the IP rating could take a dip. Anything from dropping the device to having the Pixel repaired could cause that IP rating to come down a bit.
The bits and pieces that makeup water and dust resistance also happen to be materials that are shock absorbing. This includes silicones and types of glue inside your Pixel. If your device does fall and take a hit, some of that glue could come loose, developing a weak spot in your Pixel’s water resistance rating.
What waterproofing rating is your Pixel?
As mentioned, Google’s line of Pixels usually falls in either the IP67 or IP68 rating, with newer phones being IP68. Unfortunately, Google doesn’t release an IP rating for some “a” series devices, such as the Pixel 4a or 3a. For these devices, it’s better to avoid water and dust altogether. Here’s the rating for your Google Pixel’s waterproofing:
Pixel 6 Pro – IP68
Pixel 6 – IP68
Pixel 5a – IP67
Pixel 5 – IP68
Pixel 4a – N/A
Pixel 4 – IP68
Pixel 4 XL – IP68
Pixel 3a – N/A
Pixel 3a XL – N/A
Pixel 3 – IP68
Pixel 3 XL – IP68
Pixel 2 – IP67
Pixel 2 XL – IP67
Pixel – IP53
Pixel XL – IP53
In all, it’s important to know what your Pixel can handle in terms of water and dust. To be on the side safe, even if your Google Pixel has an IP68 water resistant rating, don’t submerge your phone past 1 meter underwater if you can help it. Also, note that these ratings don’t stand true the whole lifespan of the device and can absolutely degrade over time.
One of the best features of Google Pixel phones is Call Screen, an easy way to handle spam calls without actually picking up the phone. This week, the feature is officially expanding past the US, Canada, and Japan to seven new regions.
Flying under the radar on Pixel 6 launch day last week, Google quietly revealed that Call Screen would expand to seven more countries. These countries specifically include:
UK
France
Germany
Australia
Ireland
Italy
Spain
We’ve since found that the feature was rolling out in the UK early this week and reports have since come in from France, Australia, and Germany.
It’s worth noting that the feature is limited in these additional countries compared to how it works in the US, Canada, and Japan. Call Screen on Pixel phones in these countries will be limited to its manual form, rather than supporting the automatic screening feature that allows the phone to detect spam calls on its own and screen those on your behalf. That option was first rolled out to Pixel owners in the US at the end of 2019.
Call Screen helps users in the U.S., Canada and Japan screen 37 million calls each month, and today we’re expanding manual Call Screen to Pixel users in the U.K., France, Germany, Australia, Ireland, Italy and Spain. Our latest on-device speech models make the transcriptions more accurate than ever on Pixel 6 and Pixel 6 Pro thanks to Pixel’s new Google Tensor.
