Yes, the Android Q update isn’t slated to come out until August, but right now you can download and install Android Q beta 4 and enjoy a few minor tweaks from beta 3, mostly for dark mode, and bug fixes.
As this Android Developers Blog post explains, the beta 4 release collects the final Android Q APIs and official SDK before the full Android Q launch later in the summer. Exciting!
We know that Dark Theme, the long-awaited system-wide dark mode, is the biggest shift from Android Pie. We’re also seeing the Android 10 Q beta launch on non-Pixel phones, though we’re expecting it to launch on Google’s first-party handsets before the others, like previous Android releases.
What else is new with Android Q? We’ve got a working features list below, based on what we’ve tested in the ongoing beta and and saw at Google IO.
Android Q release date
March 13: The first Android 10 developer beta has launched
April 3: Android Q beta 2 gave us bugs fixes and app bubbles
May 7: Android Q beta 3 launched at Google IO 2019
Early June: The final incremental update, beta 4, should land in June
July: Beta 5 and beta 6, release candidates, may land this month
August: The final release has routinely happened in August
Google’s Android Q developer beta is already here – at least if you own one of 23 of the compatible Android Q beta phones, including all Pixel phones to the,
- OnePlus 6T.
- Google Pixel 3
- Google Pixel 3 XL
- Google Pixel 3a
- Google Pixel 3a XL
- Google Pixel 2
- Google Pixel 2 XL
- Google Pixel
- Google Pixel XL
- Asus Zenfone 5Z
- Essential Phone
- Huawei Mate 20 Pro
- LG G8
- Nokia 8.1
- OnePlus 6T
- Oppo Reno
- Realme 3 Pro
- Sony Xperia XZ3
- Techno Spark 3 Pro
- Vivo X27
- Vivo Nex S
- Vivo Nex A
- Xiaomi Mi 9
- Xiaomi Mi Mix 3 5G
Even the Essential Phone got the update. We’ll have to see if the OnePlus 7 gets added to the Android Q list on May 14 when the phone will launch worldwide.
Google has outlined six stages to its six-month-long beta process, including the initial release, three incremental updates, one update with final APIs and the official SDK, and then two release candidates. That’s all before the final version of Android 10.
Its monthly updates should give us an official Android Q release date in August, and historically, that’s when we’ve seen the final update launch in past Android versions. But that doesn’t mean every Android phone will have Android Q by August.
The roll out to other Android phones will happen throughout 2019 and even into 2020, as various manufacturers add their own features and interfaces to the operating system. There’s a chance you’ll have to wait months after the initial Android Q release before you see the OS update on your device.
Android Q: what’s new
We’re getting a better idea of the new Android Q features to come thanks to the beta of Google’s mobile operating system. Additional features and bug fixes have come with beta 3 and we expect the same from Android Q beta 4 in early June.
Some of the changes are confirmed, while others remain rumors. Here’s what you can expected ahead of the official Android Q release date in August.
Android Q won’t have Android Beam
One feature Android Q won’t have is Android Beam, the NFC peer-to-peer sharing method when two devices are nearby. Placing phones back-to-back will do nothing in the beta and final software, we confirmed at Google IO.
Will Google replace Android Beam with another peer-to-peer sharing method? That remains to be seen. We may have to wait until the final Android Q release date to see it, or maybe when the Google Pixel 4 launches (excepted in October).
Closing privacy loopholes
A report from the International Computer Science Institute found that over 1,300 apps on the US Google Play Store routinely scraped personal data from users even if explicitly denied by relevant permissions settings.
Google is reportedly fixing these issues with the full release of Android Q in August, though presumably not in any planned beta beforehand.
Android Q is preparing for foldable phones in 2019, or “foldables and innovative new screens,” according to the Android Developers Blog post.
The Samsung Galaxy Fold – while it was in our hands briefly seamlessly switched between the folded and unfolded screen states. By Google natively supporting this type of UI continuity in the backend, it’ll likely come to more foldable phones when they launch with Android Q onboard.
For developers, Android Q beta 2 includes a ‘foldables emulator’ in Android Studio 3.5, according to Dave Burke, Google’s VP of Engineering.
Android Q ‘bubbles’ multitasking
You’ve seen the bubbles UI before if you’ve used Facebook Messenger chat heads. It’s an easy way to keep active conversations on-screen as small floating profile pics, while going about your normal tasks in the rest of the interface. You can tap the pic when you want to switch back to the conversation.
Google is supporting this idea throughout Android Q and calling it a new way to multitask. So far, its examples are coming to Messages and Hangouts. But Google is reducing development time, interactivity consistency, and user privacy safeguards, so expect to see it in additional apps outside of Google’s ecosystem.
Dark Theme, the system-wide dark mode
There’s a system-wide dark mode coming to Android Q and it’s called Dark Theme. We’ve tested in out at Google IO and it works as intended, but needs to roll out to more of the menus. So far it’s limited to the settings menu. It’s very early.
You’ll be able to trigger Dark Theme in two different ways, and both are in the notification shade. The first way is with a dedication Dark Theme quick settings button that switches between the default Light Theme and new Dark Theme.
The second way is to turn on a Battery Saver mode, which automatically turns on Android Q Dark Theme. This is a boon for phones with OLED screens, which will burn fewer pixels by essentially turning off pixels in regions of the display that are intentionally black.
New Android Q privacy features
The Android Developer Blog post announcing the developer beta confirmed a heavy emphasis on boosting privacy in Android Q, a focus that was reaffirmed in the Google IO 2019 keynote.
Users will have more control over app access to location info, shared files and repositories like Photos and Videos. Another helpful change: instead of apps automatically switching focus when they have an Activity in the background (like an alarm or call), appmakers can opt to send high-priority notifications first.
Android Q beta 3 also introduced a new feature Scoped Storage which allows users to control how apps access external storage (say, in a MicroSD card). It will also better protect users from being identified by restricting access to non-resettable device identifiers, like your phone’s serial number and/or IMEI, and randomizing its MAC address when connected to different Wi-Fi networks.
These might be some of the most onerous changes for developers in Android Q, which is why, as the Android Developers Blog post reads: “We are bringing these changes to you early, so you can have as much time as possible to prepare.”
Android Q has some particular tricks up its sleeve for 5G. New APIs will enable apps to detect user connection rate and latency, as well as detect if the connection is metered.
This will give developers more refined control over how much data to send to users, especially when they have poorer connections or have data-downloading limits.
Developer tools for apps: system settings, connectivity, media and more
Developers will be able to show contextually-important system settings within their apps, which harnesses the ‘Slices’ feature that came in Android 9 Pie. So instead of having to navigate to Settings to switch on Airplane Mode or toggle Wi-Fi or Mobile Data on/off, say, you’ll be able to do that right within your mobile browser.
There are also tweaks to connectivity, including ‘adaptive Wi-Fi’ that enables high performance/low latency modes, which would be useful for things like online gaming or voice calls.
Like all the depth and blur in Pixel camera software? In Android Q, apps can request depth data (JPEG + XMP metadata + depth and confidence map) to, say, offer “specialized blurs and bokeh options in your app,” as the Android post suggests. “You can even use the data to create 3D images or support AR photography use-cases in the future.”
Android Q will also support more multimedia codecs: AV1 to let media providers stream high-quality video, Opus for audio encoding, and HDR10+ for high dynamic range video “on devices that support it” like, say, the Samsung Galaxy S10 family.
Face ID-style authentication for logins and purchases
Another dive into the developer build XDA Developers acquired revealed the OS might get a feature iOS users have bragged about for awhile: Face ID. The next version of Android might support phones packing the hardware to use facial scans for authentication.
It’s unclear just how it will work, or if it would combine sensor readings for a comprehensive scan of facial features. But we did get hints via error codes in one of the OS’ APK, which variably tell the user to move the phone in different directions for the device to get a better look at their face.
Other strings of code found by XDA are also promising, like one that blatantly informs users they can “Use your face to unlock your phone, authorize purchases, or sign in to apps.”
Whether phones will be able to use Face ID is another story: they need to have the hardware installed whether that’s sensors or the right specs – for the feature to work.
Goodbye back button, hello (only to) gesture controls
While recent Android phones from different brands have tried to push their own gesture controls for years, the OS has always kept its static three-button navigation as an option. Those days might be at an end as that XDA preview build showed only gesture controls, per Tom’s Guide.
From the looks of it, users may only be able to use the navigation system present in the Google Pixel 3: a small pill at the bottom of the screen that you can swipe in the cardinal directions to get around.
It’s key to note that Android allows brands to develop their own navigation methods and systems to go along with their overlays, so it’s very unlikely that this will be the only way to navigate. This build is also a bit out of date, so who knows if something as integral as OS movement would be finalized that far out..