how-to-easily-install-the-android-12-developer-preview

How to easily install the Android 12 developer preview

Update February 18th, 2:10PM ET: Google released the first of its Android 12 developer previews, so we’ve updated the info in this post to be relevant if you want to install it on your phone. The instructional photos might include a mention of Android 11, but we’ve ensured the steps are still accurate.

You can try out the Android 12 developer preview software right now if you have a Pixel 3 or later, but it’s understandable if the idea of flashing your device to install the OS is intimidating. It can be a tricky process, and the steps differ slightly depending on what phone you have and what kind of computer you’re going to use to download the software. But Google itself makes this process much more streamlined.

Google’s Android Flash Tool is a web application that handles most of the steps of flashing for you. There are a few steps that you’ll need to do yourself before the new software can be installed, which we’ll walk you through below, but Google’s tool basically eliminates most of the hassle and complexity that makes it easy to mess up.

There are a few important notes to make up here at the top. First, once you flash your phone with the developer preview, your device will get all future developer preview and beta updates over the air. In other words, you won’t need to flash your phone again when new builds of Android 12 are released. Just head to your system settings and fetch an update.

The second note is just your standard disclaimer that you do this at your own risk. This is unfinished software, and installing it could lead to malfunctions with your device or to software that you usually use. And depending on settings that you adjust in the Android Flash Tool, you might have to wipe all of the data from your phone. So proceed with caution.

Photo by Vjeran Pavic / The Verge

Is my phone compatible with Android 12?

The Android 12 developer preview is compatible with the Pixel 3, Pixel 3 XL, Pixel 3A, Pixel 3A XL, Pixel 4, Pixel 4 XL, Pixel 4A, Pixel 4A 5G, and the Pixel 5. It’s possible that Google will broaden the list of devices supported by Android 12 in the upcoming beta, but for now, you’ll need one of those phones to get the software.

What browser do I need to use to flash my phone?

Google says that you can use any browser that supports the WebUSB API, which is supported by Chrome as well as Microsoft Edge version 79 and later. The Android Flash Tool works with all the major operating systems, including Linux, macOS, Chrome OS, and Windows 10, though browser compatibility may vary depending on your OS.

Step 1: Activate these three settings on your Android phone

  • Enable the Developer Options menu in your phone. First, open the Settings app. For phones running Android 8 (Oreo), click System. Otherwise, if your phone has Android 7 (Nougat) or later, scroll down to About Phone, then find Build Number. Tap Build Number seven times to enable Developer Options.
  • Turn on USB debugging (this lets your phone and computer communicate via USB) within the Developer Options menu. To do this, head to Settings > System > Advanced > Developer Options. You’ll find USB debugging with just a little scrolling down.
  • Enable OEM unlocking. This option is also part of the Developer Options menu, further up the page than where you found USB debugging. If that option isn’t available for you to enable, that might be because it’s already enabled.

Photo by Vjeran Pavic / The Verge

Step 2: Connect your phone to your computer and get started

  • If you use Windows 10, you’ll need to install this driver first for your phone to be recognized. People using macOS or Linux don’t need a driver.
  • Connect your phone to your computer with a USB cable. Then visit this page to proceed.
  • The Android Flash Tool will ask for permission to access ADB keys in a pop-up window, which is necessary to install software on your phone. You’ll need to tap “OK” to proceed with this process.

You’ll need to hit OK to proceed with the installation.

  • Click “Select device.” Your device should appear in a pop-up window on your computer, so go ahead and click it.
  • Once you do that, you should now see a request on your phone that says “Allow USB debugging?” You’ll also see a long string of numbers and letters that should match up with what your PC shows if you click the gear icon on the Android Flash Tool page. On your phone, check the box next to “Always allow from this computer,” then tap Allow.
  • After that, your device should show up on the Android Flash Tool as being connected. Click on the box with the name of your device to proceed.

Once your device shows up as being connected, click into it.

  • You’ll want to pay attention to what appears in the “Selected build” section of the Flash Tool (see below). It should say “Android 12 Developer Preview 1.” Before you hit the blue “Install” button at the bottom of the page, I recommend tapping the pencil icon next to “Selected build” and checking the “Lock Bootloader” box. This will lock the bootloader after this process is complete, leaving you with a more secure device than if it remained unlocked.

Select the “Lock Bootloader” option, which will lock your bootloader after the software installation is complete.

  • The next window basically tells you to stop interacting with your phone during the rest of this process unless asked to do so and to not unplug your device. If you’re in a position to proceed, go ahead.

Make sure your data is backed up before you proceed.

  • One more prompt before getting started: a license agreement. You need to agree to the terms of the Android Software Development Kit License Agreement, which you can find here.
  • After you hit “I accept,” your phone will reboot into its bootloader screen. If nothing happens for a few seconds, don’t worry. You may also see a window pop up on your computer that says “Reselect your device.” In that case, leave your phone alone and select “Reselect device” on the computer. According to Google, your phone might be renamed “Android,” though it might just be identified with the model name (e.g., Pixel 3).
  • If you haven’t flashed software before, Google will probably need to unlock your bootloader to proceed with the installation. Keep in mind that doing this will trigger a factory reset on your phone. If you haven’t backed up your data, you’ll lose everything. Once you agree, you’ll need to allow the bootloader to unlock on your phone. To do this, use the volume keys to navigate to the option that says “Unlock the bootloader,” then hit the power button once to confirm.
  • After that, the Android Flash Tool will begin to download and install the software. You can continue to watch along, but don’t touch your phone at this point, even though it will restart several times. Just keep an eye on the progress using the Android Flash Tool page on your computer.

At this point, you can just sit and wait for the Android Flash Tool to wrap things up.

Once you’re all done, the phone will reboot one last time, and over on your PC, you’ll be met with a celebratory screen. You’re all done! And thankfully, you won’t have to go through this process again for the next Android 12 update — easy as this was. You’ll automatically receive updates to the developer preview over the air.

You’re all done!

android-12-developer-preview-is-available-now-with-many-under-the-hood-updates

Android 12 developer preview is available now with many under-the-hood updates

Google is releasing a developer preview for the next version of Android, Android 12, for Pixel devices today. As is the norm for Google, the very first previews of Android are full of a lot of developer-facing changes. Android 12 has updates to how the OS handles images, video, and future security updates.

It’s also the norm for Google to hold some of the major UI changes in reserve for its Google I/O conference, typically held in May. Although this developer preview does include some changes to the UI for notifications, until we install it we won’t know how closely it will map to the leak we saw earlier this month.

It’s available for Pixel 3 and newer phones but needs to be manually installed by flashing your device. It’s likely nowhere near ready for day-to-day use, but Google is promising that it will continue its beta program for regular users later this year.

Although the point of this first preview is to give developers a jump-start on getting their apps ready for the new version of Android, there are still features that should make a tangible difference to users. Specifically, Android is going to become more adept at handling different types of media.

Google did not provide images of Android 12’s user interface ahead of time. We will update this post with more details and images as soon as we are able.

New media formats in Android 12

There will be a new transcoding layer that will automatically make the HEVC video format work in apps that don’t natively support them. Currently, choosing to shoot in HEVC on an Android phone may mean that third-party apps won’t be able to natively use that video. The new transcoding layer for those apps should let users make the switch with more confidence.

Android 12 will support spatial audio, support MPEG-H, and be optimized for up to 24 channels of audio (up from eight before). It will also make it easier for developers to tie rumble effects to audio.

Google appears to be throwing its weight behind the AV1 Image File Format — otherwise known as AVIF. AVIF is meant to replace JPGs as the de facto image format, offering much better and cleaner compression with fewer artifacts. Netflix in particular has been a big proponent of the format. If AV1 sounds familiar, that’s because it’s an offshoot of the AV1 video format that major tech companies proposed some years back and both Netflix and Google have partially adopted. AVIF also isn’t to be confused with the similar HEIF, which Apple’s cameras have been shooting for some time.

Google says that it does not intend to make AVIF the default image format for the camera app, so this is still just a first step.

Sticking with multimedia, Android 12 will simply do a better job moving different kinds of media between apps. It’s creating a new “Rich content insertion” API that will let you cut and paste or drag and drop multiple kinds of content, including “plain and styled text to markup, images, videos, audio files, and more.”

A leaked look at Android 12. As of publication we don’t know precisely how accurate this is, but it lines up with Google’s description in its blog post.
Image: XDA-Developers

Android 12 interface changes

We will need to install the developer preview ourselves to get a closer look at the changes Google is introducing right now. Its blog post describes what’s new in somewhat general terms. It’s a safe bet that what Google is showing today will be a hint to larger changes due later in the year. Whether those changes really will match up with the leaked screenshots you see above remains to be seen.

Here’s how Google describes the changes it is making to notifications:

We’re refreshing notification designs to make them more modern, easier to use, and more functional. In this first preview you’ll notice changes from the drawer and controls to the templates themselves. We’re also optimizing transitions and animations across the system to make them more smooth. As part of the updates, for apps targeting Android 12 we’re decorating notifications with custom content with icon and expand affordances to match all other notifications.

The app icons do line up with the leaked screenshot above, though, again, that doesn’t necessarily mean that’s what the final version will look like. The “expand affordances” also line up — the downward-pointing caret you can see in the screenshot above would be easier to tap than the current system. Google also notes that it is asking developers to use an API that makes apps open up more quickly in the right spot when a user taps a notification.

Finally, Google says that it is changing how Android 12 will behave when you’re in a full-screen app like a video, a Kindle book, or a video game. Currently, it often takes two gestures to exit out of those apps — one to bring up the UI, another to actually exit out. With Android 12, Google says that it is “changing the default to allow users to navigate their phone with one swipe.”

Changes under the hood

In 2019, Google started updating certain components deep inside the Android OS directly, rather than waiting for carriers to push through a major update. Dubbed “Project Mainline,” it meant Google could issue security updates for critical parts of Android using the Google Play infrastructure. Ever since, it’s been adding more pieces of Android to the Mainline system. Android 12’s big addition to this system is the Android Runtime (ART), a fundamental subsystem for making Android apps run. The aforementioned media transcoder will also become a Mainline module.

Android 12 will have a few privacy and security updates, but they won’t be as prominently visible to users. The WebView engine that third-party apps use will adopt one of Chrome’s more recent cookie settings called “SameSite,” which could help mitigate some tracking. Google says that “more privacy and security features [will be] coming in later preview releases.”

Android recently began requiring apps to pop a notification when it needs to run a background activity — which turns out to be really distracting. In Android 12, Google says it “will be blocking foreground service starts from the background,” redirecting developers to a new API. If one of these background activities can finish up in less than 10 seconds, it may not need to display a notification at all.

Google is also releasing an Android 12 preview for Android TV right away, including giving developers the chance to test their apps on Google’s own Google TV platform.

What’s next for Android 12

Google is releasing the developer preview today, but again, it requires that you flash your device’s system image, so really it’s meant for developers only right now. Google says it will work on a “Pixel 3 / 3 XL, Pixel 3a / 3a XL, Pixel 4 / 4 XL, Pixel 4a / 4a 5G, or Pixel 5 device” or developers can simply run it inside the Android emulator.

There will be a public beta at some point, but expect it to take a few months. And if Google follows its past habits, there will be a more comprehensive look at what’s coming in Android 12 in May (or possibly June).

Last year, Android’s “platform stability” release came in early July, but this year Google is targeting August — the official release usually comes shortly thereafter. That could mean that Android 12 will arrive just a little later in the year than usual.

In the meantime, we and others will be digging in to the developer preview to see what other details we can find. More often than not there are enough hints scattered throughout the code to give us a good idea of Google’s final plans for Android.

chrome-os-now-has-a-built-in-screen-recorder

Chrome OS now has a built-in screen recorder

Google has announced that a built-in screen recorder is coming to Chrome OS in March. Google hopes the tool will make it easier for students and teachers to record virtual lessons. “Teachers have long recorded lessons to help students do homework and study for tests, but in the past year it’s become downright critical for virtual learning,” reads Google’s blog post.

It looks pretty simple. Once you’ve pressed the appropriate button on your Chromebook, you’ll see a countdown in the center of your screen. While your Chromebook is recording, a red circle will appear on the right side of the shelf.

A few other tools for Chromebook learners are in the works as well, and some have already arrived. Chrome OS’s screen reader, ChromeVox, has some new features: The voice now changes based on the language of the text it’s reading, and you can now search its menus.

Additionally, parents can now use Family Link (Google’s parental-control app) to manage their children’s school accounts in addition to their personal accounts. This means screen-time limits, bedtimes, and other restrictions parents place on their children’s personal accounts can apply to their school accounts as well.

On the hardware side, Google has announced that it’s launching over 40 new Chromebooks this year. It claims every model is “equipped to deliver exceptional Google Meet and Zoom experiences”.

To help schools navigate the new releases, the company has put out a list of available Chromebooks, which includes configurations from Samsung, Lenovo, HP, Dell, Asus, and Acer, and tips for selecting the right one. The company recommends a number of basic models, such as Acer’s Chromebook Spin 511 and Lenovo’s 300e, as well as fancier devices like the Chromebook Spin 713 (The Verge’s top Chromebook pick) and Samsung’s $1,000 Galaxy Chromebook.

A number of these units include LTE connectivity — Google is referring to these as “Always Connected” devices, and emphasizes their importance for students with limited internet access (though buying a device with LTE can bump the price up).

Chromebooks are big sellers in the education market, due in part to their affordability and districts’ widespread use of Google Classroom, Google’s online education portal. 2020 was the Chromebook’s best year ever, due largely to increased demand from schools providing at-home instruction for the first time.

Google has been building out its services for remote school and meetings since the start of the COVID-19 pandemic. In the early months of remote schooling, Google made Meet meetings with up to 100 participants available to anyone with a Google account. It’s added a number of features to Meet as well, in an effort to keep up with large competitors Zoom and Microsoft Teams. The company has rolled out custom backgrounds, blur effects, real-time captioning, low-light mode, and hand-raising in recent months.

xbox-cult-classic-stubbs-the-zombie-is-getting-remastered-for-modern-consoles

Xbox cult classic Stubbs the Zombie is getting remastered for modern consoles

If you ever wanted a zombie game where you played as the undead instead of fending off against it, you’ll have another chance soon. Stubbs the Zombie in Rebel Without a Pulse is being rereleased on March 16th for PC, PS4, Switch, and Xbox One and will be playable on PS5 and Xbox Series X / S via backwards compatibility.

Aspyr Media, the company that originally published Stubbs the Zombie, is handling the port. The studio recently worked on porting Star Wars Episode I: Racer to modern consoles, so it’s safe to say this remaster is in good hands.

Originally released in 2005 on the Xbox, Stubbs the Zombie has players control the titular character with the main goal of wreaking havoc and devouring human brains. It’s a third-person action title developed by the now-defunct Wideload Games. The game also came to Windows and Mac OS X roughly a month after its original release date, with a release on Steam coming nearly two years later, which was later removed from the platform.

The announcement is good news for fans who played the 2005 original. In recent years, Stubbs the Zombie has become one of the rarest games to own on the original Xbox. Microsoft made the game available digitally for the Xbox 360 in 2008 as an Xbox Originals title, but the company pulled it from the Xbox Live Marketplace in late 2012. With no other ways to play the game in nearly a decade, your only option was to own an original Xbox console and a physical copy, which is pretty pricey.

raspberry-pi-taps-into-brewery-management

Raspberry Pi Taps Into Brewery Management

(Image credit: Arithmech Analytics)

New Orleans-based Danger Shed wanted to know how much beer they had in their inventory, so with the help of a Raspberry Pi 4 and some Python code, they developed their own inventory application, Keg Punk!

Image 1 of 4

(Image credit: Arithmech Analytics)

Image 2 of 4

(Image credit: Arithmech Analytics)

Image 3 of 4

(Image credit: Arithmech Analytics)

Image 4 of 4

(Image credit: Arithmech Analytics)

Written in over two thousand lines of Python, Keg Punk is the project of craft brewery manager Patrick Murphy. It comes in three forms: A $200 complete kit including the official Raspberry Pi Display and a Raspberry Pi 4, a $19 pre-loaded micro SD card, or a $15 download for brewers to build themselves should they already have the official screen and a spare Raspberry Pi. Despite the kit coming with a Raspberry Pi 4, it is equally at home with older Raspberry Pi models, but sadly not the Raspberry Pi Zero because it doesn’t have a DSI connector.

No matter the version you choose, the base Python application is written on top of Raspberry Pi OS (formerly Raspbian), and Keg Punk supports up to 10 taps. The system has a simple touchscreen interface designed for brewers to quickly input their brews via the Cellar screen.

The home screen for Keg Punk is the Taproom, and here we can track overall cellar inventory and manage which beer is on which virtual ‘tap,’ handy when there are multiple beers in your stock room.

Right now, Keg Punk does not show current levels in kegs, but the team is already hard at work on Keg Punk 2.0, which aims to have this functionality via a series of sensors providing input, along with a second screen that updates the available list of beers for the public to order.

This could be a ‘refreshing’ project for the eager brewer and Raspberry Pi fan.