While Android 12 is still simply only making its style onto supported phones that don't have 'Pixel' in their proper noun, we're already building a moving picture of what to expect from the adjacent major release of Google's mobile Bone – Android 13.

Expected to launch in Fall 2022, existing reports and insights from its first two developer previews point to Android 13 building on features established in Android 12 (like Fabric You), while likewise introducing new additions that encompass everything from privacy and security, to gaming and battery performance.

What is Android 13's codename?

While Android'southward development team shelved the practice of revealing each major release's codename to the public, once reaching Android x it continued the trend internally; with fans always curious to acquire what each new release is colloquially chosen at the visitor.

If yous're unaware, each iteration of Android (since version 1.5, at least) has come with a codename inspired by a sweet treat; with each subsequent release adopting a new name, progressing in alphabetical social club.

Android 1.5 was labelled 'Cupcake', while 1.6 was 'Donut, 2.0 'Eclair', 2.2 'Froyo', ii.3 'Gingerbread', 3.0 'Honeycomb', 4.0 'Ice Cream Sandwich', four.1 'Jellybean', 4.iv 'KitKat', v.0 'Lollipop', half-dozen.0 'Marshmallow', vii.0 'Nougat', viii.0 'Oreo' and Android 9.0 'Pie'.

While Android 10's official codename was simply listed every bit 'Android10', its unofficial codename is cited as existence 'Quince Tart', Android 11's is 'Red Velvet Block' and Android 12's is reported to be 'Snowfall Cone'.

For the letter 'T', Android 13 looks to be taking a trip to Italia, with the supposed codename of 'Tiramisu' being confirmed in the Bone'southward kickoff developer preview. Delicious.

When can I get Android 13?

The first official signs of Android 13'southward beingness took identify on 11 February 2022, when Google released the start programmer preview build of its next major Bone update.

Each generation of Android undergoes numerous stages in its development earlier finally making its way to the masses, starting with programmer previews, earlier more complete public betas go far, after which a general release takes identify; usually spearheaded by Google's own Pixel phones and those manufacturers who subscribe to the each update's Android Programmer Preview Program.

Here's when previous Android releases (and their respective betas) arrived:

Android 9 Pie

  • First public beta: 8 May 2018
  • Total version release: 6 August 2018

Android 10

  • First public beta: 7 May 2019
  • Full version release: three September 2019

Android eleven

  • First public beta: 10 June 2020
  • Full version release: 8 September 2020

Android 12

  • Beginning public beta: eighteen May 2021
  • Total version release: 4 Oct 2021

And here's where we're tracking the release dates of Android 13'south programmer previews, betas and its final release:

Android 13

  • First developer preview: 11 February 2022
  • Second developer preview: 17 March 2022

Android 11's and 12'due south showtime programmer previews made their debuts in February 2020 and 2021, respectively, with the starting time public beta for each recent Android release consistently existence made available in May, each year.

Google's Android 13 platform stability milestones roadmap | Source: Android Developers Blog
Google's Android 13 platform stability milestones roadmap | Source: Android Developers Blog

With this in mind (and the fact that Android 13's starting time two developer previews have kept step with previous releases), it seems safety to assume that this twelvemonth's first public beta will likely be served up in May too; likely set to coincide with the annual Google I/O 2022 programmer briefing, which is scheduled to boot off on 11 May this year.

The outset stable build of 'Tiramisu' is then expected to hitting devices in the Autumn – most likely in September.

Which phones will get Android 13?

The safest way to ensure you're going to receive an invite to the next release of Android is to ain a recent Google Pixel phone, with every Pixel launched since 2019'south Pixel 4 line already promised an upgrade to Android xiii.

Hither's the listing of Pixels already set to receive Android 13:

  • Google Pixel 4
  • Google Pixel four Forty
  • Google Pixel 4a
  • Google Pixel 4a 5G
  • Google Pixel five
  • Google Pixel 5a 5G
  • Google Pixel half-dozen
  • Google Pixel half-dozen Pro

Across Google's own Pixel phones, the Android 13 whitelist becomes a petty trickier to map out. Later on years of severe fragmentation, large brands (like Samsung, OnePlus and Vivo) take started making more than concrete promises; matching (or surpassing) Google's three-year Bone update commitment. Other companies, meanwhile, nevertheless seem to make up one's mind how many new generations of Android their smartphones and tablets will receive on a device-past-device basis.

The best manner to find out is to check with each manufacturer direct but for those looking for a cheat sheet, our 'Best Brands for Android Updates' feature should as well shed some lite on those phone makers that'll be bringing Android 13 to their existing lineups.

What'south new in Android xiii?

The biggest shift brought about by Android 12 – to Pixel users at least – was the introduction of Material You: a new design language for the Android user experience. Across that, the update showcased a heap of new privacy and security controls, not to mention convenient (and overdue) extras, like scrollable screenshots and even a one-handed way.

While the arrival of the first programmer preview shed some light on what Android 13 has to offer, at this phase in its evolution it's the chore of diligent developers and enthusiasts to dig around and unearth potential features and improvements destined to grace 2022's big Android release; with the bulk of known and expected features consolidated by the likes of Android Police force and the team at XDA Developers.

Features confirmed in developer preview 1:

Photo picker

An extension of Android's existing document picker, the photo picker is set to serve every bit "a standard and optimized [sic] way for users to share both local and cloud-based photos securely."

Like the certificate picker, this characteristic side-steps the need for permission to access all photos and videos on a device in order to let the user access shared media, and should ameliorate unify Android'southward media sharing feel across devices from various manufacturers.

In his post concerning what's included in programmer preview 1, Android's VP of technology, Dave Shush also stated that this characteristic will too exist made bachelor to older Android devices, every bit far back as Android 11 (excluding Android GO devices), getting pushed as part of a futurity Google Play system update, rather than part of a major Os update.

Nearby device permissions for WiFi

Contrary to Android'due south current configuration, the improver of the NEARBY_DEVICES_RUNTIME permission will allow apps more easily observe and connect to nearby devices, without needing to inquire for location data; simplying interconnectivity over WiFi with nearby devices and making things easier for app developers in the process.

Quick Settings tiles

New APIs for developers to brand custom tiles to fit within the quick setting section of Android'due south notification shade. Developers volition also be able to have their apps throw out a prompt for users to instantly add such tiles with a tap.

Themed app icons

As an extension of the system-wide palettes that Material You uses to wearing apparel your telephone's interface with a consistent colour theme, in Android 13, app icons tin besides benefit from this result.

While Google has full control over its own apps, irresolute app icons to friction match a theme tin get inconsistent when it comes to third-political party offerings.

Android 13 DP1, Themed app icons | Source: Android Developers Blog
Source: Android Developers Blog

To address this, developers are being urged to include a monochromatic version of their app'due south icon inside their app submissions, which paired with the code volition allow Android 13 to dress the icon file with the dynamic Material You color theming magic that it introduced in Android 12.

Every bit it stands, Material You lot remains a Pixel-exclusive trait, yet, the Google has plans to bring themed app icons to other devices by working with manufacturers directly.

App-past-app languages

Multilinguists rejoice! A feature codenamed 'Panlingual' looks set to allow users to specify language settings on an app by app ground, meaning those who apply apps that aren't natively in the same language as their device's system language won't have to worry about working with a poorly translated app.

Ideal for bilingual, trilingual and polyglots who might prefer to have different apps set to different languages, everywhere.

Native animation tools for developers

Apps might commencement to look a little more dynamic, with Google implementing something called "RuntimeShader objects."

Developers will be able to leverage the aforementioned tools the company itself uses to adorn Android with UI effects like rippling, blur and stretch overscroll.

The continuation of Project Mainline

Project Mainline aims to make the process of updating parts of Android and calculation new features like to that of how apps are already updated, via Google Play system updates, rather than having to include them every bit part of fully-fledged Bone updates.

This is how Google intends to push features like the same Photo Picker, rather than making it an Android 13-exclusive addition.

Features confirmed in developer preview ii:

New notification permissions

Apps hoping to fire off user-targeted notifications volition initially have to ask for the privilege of doing so on Android thirteen, while on Android 12 devices (or lower) "the arrangement volition handle the upgrade catamenia on your (the developer's) behalf." Google's developer site doesn't specify what "handle" means, in context, nevertheless.

Developer downgrade permissions

A refined app permissions model in Android xiii will downgrade previously-granted or newly redundant permissions on supported apps, in the pursuit of greater user privacy.

Improved language-related text management

A dry but important set of improvements come with how Android thirteen handles certain text.

Android 13 DP2 text managment
Japanese text wrapping comparing (left), improved line heights for non-Latin scripts (right)

Japanese text wrapping will ensure more than coherent and readable characters within Japanese-linguistic communication apps and improved line heights for non-Latin scripts (examples given include Tamil, Burmese, Telugu, and Tibetan) will arrange line superlative dynamically based on the language beingness used to ensure characters are no longer cut off (great for non-Latin app UIs in item).

What's more than, new text conversion APIs will come into play when using phonetic languages (such as Japanese and Chinese), where text will be able to be converted from (in the case of Japanese) Hirgana to Kanji straight, removing additional steps currently at play when performing deportment like searches.

Colour vector font support

Android 13 gains COLR version 1 font support and emojis are now to employ the COLRv1 format, making for faster-rendering and crisper fonts (and emojis) at calibration.

COLRv1 vector emoji (left), bitmap emoji (right)
COLRv1 vector emoji (left), bitmap emoji (correct)

Native Bluetooth LE sound support

The foundation for Bluetooth Low Energy audio support had already been laid in Android 12, merely Android 13 brings the functionality to life.

As spotted by technical analyst Mishaal Rahman, long before the release of the second Android thirteen developer preview, Bluetooth LE had but ever been used for data transmission but Google has now folded in the LC3 (the Depression Complexity Communications Codec) for Bluetooth A2DP (Avant-garde Sound Distribution Profile), allowing for high-quality audio with lower power demands, by fashion of Bluetooth LE.

MIDI two.0 support

Support for MIDI 2.0-compliant devices over USB allows for "increased resolution for controllers, ameliorate back up for non-Western intonation, and more expressive performance using per-notation controllers," according to Google's ain developer site. Great news fundamentally for musicians and music producers.

Notifications for excessive background battery usage

While not explicitly mentioned in the annunciation article for Android 13 developer preview 2, equally initially spotted by Android Police, changes made to the Bombardment Resource Utilisation department of Android 13's developer documentation make mention of a new notification that'll pop up when the arrangement detects an app causing excessive bombardment drain.

The notification arises after a 24-hour period, in which Android 13 takes into account factors like foreground services (even those that have visible notifications), work tasks, background services and an app's cache to decide whether extrenuous battery drain is coming from a item source.

Features either confirmed or expected based on leaks and rumours:

Lock screen clock placement

The lock screen clock, as information technology appears on near-stock and AOSP builds of Google'southward mobile Os sits front end and centre on-screen, occupying nearly of the brandish. While some skinned versions of Android let for lock screen customisation to some degree, seldom is at that place the option to shift the clock around.

Android 13 will supposedly support such a feature natively, letting y'all alter the style and placement of the clock, branded the 'double-line clock'. At that place are fifty-fifty signs that this detail update might arrive fifty-fifty sooner, as part of Android 12L.

Switch account from lock screen

Sticking with the lock screen, while Android already supports multiple users and at that place are multiple ways to modify users on-device, Android xiii may innovate a new option that lets different users switch profiles, directly from the lock screen.

NFC payments for secondary users

One fundamental feature that secondary users aren't able to access when sharing a single device is the ability to make NFC payments, something that only the principal user has admission to. Android 13 looks equally though it'll add together contactless payment support for multiple users on one device.

Tap-to-transfer

Android Beam was meant to be the platform'southward respond to AirDrop on iOS, with the added convenience of existence able to initiate a connection with a unproblematic NFC 'handshake' past placing two devices dorsum to dorsum.

Frustratingly, it never quite took off in the aforementioned way and has since been replaced by Nearby Share, which offers similar convenient sharing but through a mix of Bluetooth and WiFi Directly instead.

Trusted sources take now informed AndroidPolice of a potential forthcoming feature codenamed 'Media TTT' (along with a prepare of relevant screenshots) that looks to be using close proximity-based connectivity technology (potentially NFC) as a means of 'throwing' media to other devices and outputs.

Piffling else is known most the characteristic merely it'south assumed that, if it does appear in Android 13, information technology'll manifest as 'Tap-to-transfer' and support more user-friendly file and media sharing on the platform.

UWB support to go wider

Android 12 added native back up for UWB (ultra-wideband) connectivity, a characteristic only really leveraged by the Pixel 6 Pro – the only Pixel to currently support the feature (UWB-capable devices from other manufacturers, like Samsung and Honour, rely on their ain UWB software back up to role).

An UWB 'generic hardware abstraction layer' is obviously in the works for Android xiii, offering a common toolset for manufacturers to work with when implementing the engineering on their devices going forward.

More colour for Material You

I of the novel talents of Material You is its ability to theme the entirety of your device's interface by automatically colour-picking a palette based on (and thus complementing) your chosen lock screen/dwelling house screen wallpaper.

This palette uses what Google'southward branded as "tonal spot" colours, however, Android 13 looks set to introduce three additional variations: "Vibrant" which adds a little more multifariousness to the palette, "Expressive" which expands the range of colours used beyond those of the wallpaper influenced swatch, while "Spritz" will offer a desaturated alternative, for a more than muted advent.

Sound output picker glow-upward

The output picker implemented in Android 10 which lets users choose where the sound for their chosen media is channelled to (headphones, loudspeaker, Bluetooth-connected speakers, etc.), may well get a makeover in Android 13.

In its current guise, the feature adds independent volume sliders for each bachelor output source, although this implementation may exist discipline to change before release.

Opt-in notifications

Android already has a fairly robust notification management arrangement, only Android 13 may also give users the power to grant or deny newly-installed applications notification privileges from the get-get, just like iOS does.

QR code scanner

Similar one-handed mode – which finally found a dwelling in Android 12 – one long-overdue addition in Android xiii could exist the shortcut to a dedicated QR lawmaking scanner. The boilerplate user might not realise that their photographic camera (or Google Lens) tin already scan QR codes simply Google apparently wants to make the process more than obvious and accessible.

AndroidPolice already has screenshots of a new quick settings shortcut to a QR lawmaking scanner, too as the ability to access it from the lock screen. Whether this is a separate app of characteristic from the existing implementations of QR code scanning built into Android is unclear.

Flashlight brightness command

Every bit uncovered by senior technical writer at Esper – Mishaal Rahman, Android 13 includes two new APIs in 'getTorchStrengthLevel' and 'turnOnTorchWithStrengthLevel'. Equally their names suggest, one allows developers to know what brightness level a devices LED flash is set to, while the other lets them control the torch based on that brightness value.

While some apps and manufacturers' devices already allow for this sort of control, this is the start time we're seeing support broiled into Android straight. The ability to control LED brightness may be dictated by hardware limitations, however, meaning not all Android phones will allow for such functionality.

Google Banana home button toggle

There are already a lot of ways to invoke the Google Banana on most Android phones (especially Pixels) just in that location are signs that, for those who still prefer navigating around their devices with on-screen buttons (in place of border gestures), the ability to toggle long-pressing the domicile push to summon the Assistant will be reinstated.

Opening games faster

Rahman again spotted updated AOSP lawmaking that suggests phones running Android 13 will be able to launch games faster, past way of an API that boosts CPU functioning momentarily.

Pixel phones are most likely going to be the principal beneficiaries of such a characteristic but it's unclear at this stage as to whether information technology'll also be attainable to other devices too.

Native back up for DNS over HTTPS

New code in the AOSP points to the potential of upgraded security, thanks to the addition of support for DNS over HTTPS.

Equally per XDA Developers' piece on the feature, Android currently supports DNS over TLS (unremarkably abbreviated to 'DoT'), however, DNS over HTTPS (or 'DoH' for short) uses the HTTP or HTTP/2 encryption protocol, which offers a slight reward over DoT's TLS encryption, with regards to privacy.

Phantom process toggle

Android 12 introduced a power direction characteristic called 'PhantomProcessKiller' which, equally the name suggests, stops processes running in the groundwork in an effort to free upward resources and prevent excessive ability drain.

Updates to AOSP suggest that Google has seen the error in this indiscriminate approach – particularly where power users are concerned – and looks to exist adding a toggle into Android'south developer options that will allow users disable the PhantomProcessKiller if they wish.

TARE: The Android Resources Economy

As part of how Android handles power management going forward, TARE (The Android Resource Economy) looks to be a feature Google is currently working on that awards or deducts 'credits' from an app, based on how many processes it tries to perform through 'JobScheduler' and 'AlarmManager',  relative to the device's battery percentage.

Nosotros'll have to await until Google publishes official information on TARE to meliorate sympathize how it'll operate but it sounds like a novel way to handle app processes and device power direction on Android xiii.