What you need to know

• Android 17 QPR3 Beta 2 has added a toggle to require PIN/fingerprint authentication before anyone can touch Airplane Mode, Wi-Fi, Bluetooth, or Mobile Data on a locked phone.
• Non-security tiles like Flashlight, Auto-rotate, and Battery Saver stay unlocked and accessible without extra friction.
• The latest Android 17 beta release also resolves random reboots, system crashes, Bluetooth pairing failures, idle battery drain, and buggy internet tiles.

Google is finally giving Pixel owners a way to stop thieves from disabling their phone’s connectivity right from the lock screen.

The new security feature is coming in Android 17 QPR3 Beta 2, which will let users require authentication before anyone can toggle Wi-Fi, Bluetooth, mobile data, or airplane mode. It's a small change, but it could make a stolen phone a little less useful to whoever walks away with it.

This update, which came on October 20 with build number DP11.261002.005, does more than just fix a number of bugs. The Android Beta team says on Reddit that it also fixes intermittent device crashes and unexpected reboots, Bluetooth pairing failures, excessive idle battery drain, and issues with the Internet Quick Settings tile. Below is the complete list of issues fixed in the latest beta round.

• Devices intermittently crash and reboot during normal use. (Issue #570031572, Issue #570031155, Issue #569529428, Issue #569222433, Issue #570414567, Issue #570725957, Issue #569237164, Issue #572493638)
• Internet Quick Settings tile displays persistent text when mobile data is active without Wi-Fi. (Issue #354469154, Issue #367059437)
• Media output dialog ignores the monochrome system theme when external audio devices are connected. (Issue #476304142)
• Pin icon glitches position next to pinned apps in the share sheet. (Issue #476234992)
• Internal PublishedApi declarations trigger unexpected API lint and source compatibility check errors. (Issue #562178518)
• Device unexpectedly shuts down during WhatsApp video calls. (Issue #554451749, Issue #559966303)
• Lock screen in-progress notifications overlap with other UI elements and cause stuttering panel animations. (Issue #547371609, Issue #548539836, Issue #562186670)
• Cellular data, MMS, and hotspot services fail to connect on Dish Network. (Issue #537736046)
• Screen recording freezes and stops capturing frames after screen rotation. (Issue #541325203)
• System UI, fonts, and apps render at an abnormally small scale regardless of configured display size settings. (Issue #563321433)
• Display turns black and becomes unresponsive after ending a phone call. (Issue #564953545)
• Terminal app fails to launch the Linux development environment virtual machine after installation. (Issue #551657934)
• Wi-Fi Aware fails to establish subsequent data paths with a no interfaces available error after releasing an accept-any responder network request during connection confirmation. (Issue #550726291)
• Paired watch continues to ring after an incoming call is answered on the phone. (Issue #564594780)
• Airbnb app fails to connect when attempting to send messages. (Issue #563024453)
• Quick Settings Bluetooth subtitle is misaligned to the right. (Issue #559417120)
• App drawer unexpectedly closes when switching keyboard language. (Issue #558774933, Issue #540389222, Issue #533125590)
• Bluetooth pairing fails due to a connection timeout when attempting to pair with a device. (Issue #563675080)
• VoLTE, VoNR, and Wi-Fi calling are unavailable on the IT&E network. (Issue #556432987)
• High idle battery drain caused by motion sensors remaining active after using Face Unlock or the camera. (Issue #568078965)
• Wi-Fi Calling unavailable on the OXIO network. (Issue #563089593)

A more interesting addition is the connectivity restriction, as noted in a few replies to the Reddit post. Sometimes thieves can disable a phone’s network connections from the lock screen, making it more difficult for owners to track down a lost device. It’s another hurdle to force you to unlock before changing these settings, though it obviously won’t prevent all theft or ensure recovery.

To enable it, go to Settings > Security & privacy > Device unlock or Settings > Display & touch > Lock screen, then turn Lock Quick Settings connectivity on. Once enabled, you must unlock the device before you can change any of the four protected connectivity settings.

Google is also leaving common shortcuts like flashlight, auto-rotate, and Battery Saver accessible, so the security feature doesn’t relegate the lock screen to a glorified clock. Locking each and every Quick Settings tile would be way too limiting for those who enjoy shortcuts without unlocking their phone. So it’s a more targeted way to protect the settings that could interfere with connectivity and tracking.

Android 17 QPR3 Beta 2 is available for eligible Pixel devices enrolled in Google’s Android Beta Program. As with any beta software, users should expect the possibility of bugs and avoid installing on a device they can’t afford to have misbehave.

What you need to know

• Google's new Noto 3D emojis, introduced with Android 17 and the Pixel 11 series, are starting to reach older phones.
• A Reddit user reports receiving the redesigned emojis on their Pixel 6a, possibly through a system update.
• The rollout appears limited for now, while Google has confirmed plans to bring the new emojis to all Android phones.

Google appears to be rolling out its new Noto 3D emojis to older Android phones.

With the launch of Android 17 and the Pixel 11 series, Google introduced a new emoji design language. Android users have complained for years that emojis on the platform look rather plain and bland, especially compared to what competitors offer. But with Android 17, Google introduced its new Noto 3D emoji design, bringing more depth and a three-dimensional look to emojis.

Google says the new emojis feature more depth and dimension, making them better at expressing emotions and giving them a more distinctive look. Until now, these emojis have largely been exclusive to the new Pixel 11 series, but it looks like Google is finally starting to bring them to older Android phones as well.

As spotted by a user on Reddit (via 9to5Google), the new Noto 3D emojis have reportedly started appearing on the Pixel 6a. The user says their emoji selection has been updated to show the new designs and believes the change arrived through a system update rather than a Gboard update.

Google has so far kept the new emojis exclusive to the Pixel 11 series, but this report suggests the company may have started expanding their availability to older Pixel phones.

That said, the rollout doesn't appear to be widespread just yet. We checked both the Pixel 9a and Pixel 9 Pro running the latest Android 17 software, and neither device has received the new emojis, even after installing the latest Google Play system update.

Still, with at least one user reporting that the new emojis have appeared on their older Pixel, there's a chance Google has started a gradual rollout that could reach more devices over the coming days or weeks.

Google has already announced plans to make the new emoji designs available across its apps and on devices from several Android manufacturers, including Nothing, Lenovo, Xiaomi, Oppo, OnePlus, Vivo, Honor, Motorola, and more.

What you need to know

• Google is developing new Pixel diagnostic tools to help troubleshoot problems with calls, Wi-Fi, and mobile data.
• The new tools appear under Device Health & Support, alongside existing battery, Bluetooth, and touchscreen diagnostics.
• Pixel phones could soon identify connectivity problems and either attempt a fix or guide users through troubleshooting..

One of the issues we regularly run into on Android phones, unfortunately, is related to mobile data, Wi-Fi, and overall connectivity. But it looks like Android 17 could soon be able to diagnose and fix some of these problems for you.

Google has been building out its Pixel troubleshooting and diagnostics tool for a while now. Pixel phones can already check for issues related to battery health, connectivity, Bluetooth, and even touchscreen problems. But now, it looks like Google is expanding these tools to help users fix calling, Wi-Fi, and mobile data issues as well.

As spotted by Android Police, the recently released Android 17 QPR3 Beta 1, alongside the latest Google Play Services beta, introduces new diagnostic tools designed to troubleshoot problems with calls, Wi-Fi, and mobile data. The new options appear under the Device health & support section.

So, if you're having trouble connecting to Wi-Fi, experiencing dropped calls, or your mobile data suddenly stops working, you'll be able to open the relevant diagnostic tool and have your Pixel check what's going wrong behind the scenes.

Depending on the issue, the tool could either attempt to fix the problem automatically or guide you through the necessary steps to get things working again. This could save users from having to manually dig through network settings or reset their connections every time something stops working.

For now, these new tools have only been spotted in Android 17 QPR3 Beta 1 with the Google Play Services beta, so they aren't widely available yet. However, considering they're already showing up in testing, there's a chance Google could introduce them with the stable Android 17 QPR3 release early next year.

Given how frequently Pixel owners have complained about connectivity issues over the years, having built-in tools that can actually help diagnose and fix those problems could be a pretty useful addition.

What you need to know

• You can now move passwords and passkeys directly between supported apps on Android without exporting sensitive data to an unencrypted file.
• Your new password manager hands the process to Android, which detects compatible managers installed on your phone and coordinates the transfer.
• Once authorized, Android moves the credentials between apps without requiring manual file handling.

Android has always made it a pain to switch password managers. Moving passwords usually involved exporting your data into an unencrypted text file, and passkeys were pretty much stuck in place. Android is tackling both of those issues with a new transfer experience that makes moving your credentials much more secure and simple.

In a blog post, Google said the new system lets you transfer passwords and passkeys directly between password managers, without first having to download a file.

That eliminates one of the biggest security hassles of the old process, which was that sensitive credentials were sitting unprotected on your device for a while. Furthermore, passkeys weren’t transferable, so you had to manually recreate them across websites and apps.

The process is built to be mostly out of your way. Start in your new password manager and select the option to import or copy credentials from another provider. The app then hands the job to Android, which knows which compatible password managers you have already installed on your phone and shows you where the data can come from.

You are then sent back to the password manager you already use to select, review, and approve the transfer. Once approved, the passwords and passkeys move between the apps in just a few seconds.

The feature is already available with Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane. Dashlane notes that CXP is compatible with devices running Android 10 or newer with the latest Play Services update. Bitwarden needs Android 14+ with Play services 26.21+.

It is not merely a matter of convenience. Passkeys are more secure than passwords and resistant to phishing. Adoption has been stalled in part due to user concerns around vendor lock-in. CXP removes that barrier.

Bitwarden says the creation of passkeys peaked this summer at over 500% compared to early 2024, with nearly half of all passkeys created in the past three months alone.

Google says more partners are on the way. If you’ve been waiting to change password managers because of the hassle, that excuse just went out the window.

What you need to know

• Android 17 QPR1 Beta 8 eliminates the long-running audio bug that caused random crackling, distortion, and loud static on Pixel devices.
• The audio issue lingered across multiple beta releases and generated 30+ reports in Google's issue tracker before this fix.
• Build CP31.260623.010 arrives two weeks after Beta 7, focusing purely on system stability and bug fixes ahead of the official September Feature Drop release.

Google has released Android 17 QPR1 Beta 8, fixing one of the most frustrating bugs Pixel testers have been dealing with: distorted audio that would randomly blast loud static during media playback or notifications.

The update, build CP31.260623.010, comes a little over two weeks after Beta 7 and is another cleanup release before the Pixel Feature Drop in September.

Google’s changelog says the biggest fix is for an issue with managing buffers in the audio framework that could cause unexpected crackling, corruption, and bursts of static. It’s a problem that has persisted over many QPR1 beta releases, spawning more than 30 separate tickets in Google’s issue tracker.

Android 17 QPR1 was already at Platform Stability with Beta 6, so developers have been working against finalized APIs while Google turns its attention to stability.

Beta 8 is available for eligible Pixel devices enrolled in the Android Beta Program, including the Pixel 6 series through the latest Pixel 10 lineup. There is, however, one big exception. Pixel 6 and Pixel 6 Pro owners still get this QPR1 Beta 8 update, but it’s basically the end of the line for those phones. Google has already confirmed that those models won’t be moving on to Android 17 QPR2, with the stable Android 17 QPR1 release expected to be their last major software update this September.

Beta 8 might finally make the preview stable enough for you to use on a daily basis if you’ve been putting off trying it because of audio glitches. Otherwise, you might want to hold off a little longer because the polished, stable QPR1 release is now just around the corner.