Android 13 Beta 3.2: The vibration icon is now also displayed on the lock screen statusbar.

Previously, Google added a separate switch to the Sound & Vibration settings, but this icon was only displayed in the status bar of the unlocked device. Now this problem has been fixed.

Google News | En

Android 13 Beta 3.2: work on the Easter egg has begun.

Now it is the same as in Android 12, but with the number 3 instead of 12. The 1, apparently, will be added in the next build. ¯\_(ツ)_/¯

Google News | En

Android 13 Beta 3.2: Clipboard overlay replaces the 'edit' button with the 'share' button.

But you can still edit the copied image/text. To do this, just tap on the preview.

Credits: Mishaal Rahman

Google News | En

Google Pixel 6 series supports mounting exFAT drives in Android 13. This is the first time that a Pixel has had native support for exFAT. Previously, Pixel users would have to download a paid app to mount exFAT drives. Native support comes from the fact that the Android Common Kernel 5.10+ branches ship with the new Microsoft-endorsed + Samsung-developed exFAT driver.

Read more here

Google News | En

At I/O 2022, Google announced an upgrade to Nearby Share that will let users quickly copy text or images on one device and share it with another. This feature hasn't rolled out yet, but it's possible to enable it in the latest version of Google Play Services.

As you can see, a new button appears in Android 13's clipboard overlay (details on that here) that lets you immediately Nearby Share any text/images you copy.

For more on what Google announced at I/O, here's a summary.

Google News | En

The Smart Unlock feature previously discovered by 9to5Google could be branded as Nearby Unlock when it launches, or they could be two different things. Either way, here's a look at the settings page for the unreleased Nearby Unlock feature.

Google News | En

A user with a bricked Pixel 7 Pro contacted us, and here's what we were able to find out. [Part 1]

Recently, a user with a prototype Pixel 7 Pro came to our Google News group. Unfortunately, his device was bricked by Google, so we were unable to get much information. However, we did determine the following based on early boot logs:

• The Pixel 7 Pro likely uses the Samsung S6E3HC4 display panel. For comparison, the Pixel 6 Pro uses the S6E3HC3. 9to5Google earlier said there was "no indication" that this display will appear on the Pixel 7 Pro, but boot logs show this panel is being used. Also that it will have a 3120x1440 resolution.

[Part 2]

(пост на русскоязычном канале)

Google News | En

A user with a bricked Pixel 7 Pro contacted us, and here's what we were able to find out. [Part 2]

• The second-generation Tensor chip may still be using Arm Cortex-A55 cores for its little cores. This is according to a line in the BL31 log, which is the final EL3 bootloader stage. According to this line, a CPU workaround is being applied for the cortex_a55 cores. It would be very odd for a Cortex A55 workaround to be used if the Tensor 2 didn't have A55 cores.

• Speaking of CPU, the Tensor 2 will still have a 4+2+2 CPU cluster

• Other components mentioned in the boot logs include the CS40l26 haptic driver IC from Cirrus Logic, the ST21NFC NFC chip from STMicroelectronics.

• We can also confirm the codenames for the Pixel 7 (panther) and Pixel 7 Pro (cheetah). Codenames for other boards/products are also revealed in ABL, including "cloudripper" (dev board), "ravenclaw" (possibly Pixel 6 Pro outfitted with GS201 for testing), and "felix" (likely Pixel 7a). Interestingly, the previously leaked "lynx" codename isn't mentioned here.

[Part 1]

(пост на русскоязычном канале)

Google News | En