Skip to content

Archive for


Mevo, the live-streaming camera, is now Twitter compatible thanks to new API

Why it matters to you

The camera designed for live-streaming couldn’t broadcast to Twitter at the first lannch because it didn’t have access, but now Twitter’s API release means the camera can go live on both Facebook and Twitter.

Mevo, the camera designed for live-streaming, is now Twitter-compatible. The Mevo is the first camera to use Twitter’s live API after the social media platform launched the third-party compatibility feature earlier today, March 21.

Mevo is a simple camera that’s designed specifically for live-streaming. The camera is meant to be set up and remotely controlled with an iOS app, making it easier to actually get inside your own live videos. Launched last year, Mevo at first only included Facebook Live and Livestream.

More: Mevo Livestream review

Now, the camera supports both Periscope and Twitter. The new feature is possible thanks to Twitter’s API, which makes it possible for third-party companies to directly integrate Twitter’s live video features. While Facebook released live video API nearly a year ago, Twitter is now following suite with a their own API for third party integration.

Twitter live-streams through Mevo are accessible through the iOS Mevo app. After updating the app, current Mevo users can tap on the red record icon in the corner and select the Twitter and Periscope icons. After authorizing the app to access a Twitter account, users can add a title to the video, then tap “Go Live.”

Mevo’s app update also includes the option for controlling the camera’s field of view and warp level using five different modes. The update, to version 1.2.1, also included a few bug fixes and stability improvements.

Twitter’s just-released API should mean a number of companies will be integrating live-streaming directly to the social media platform, as well as making it easier for big broadcast companies using pro-level video and editing equipment to stream live. While more companies will likely be integrating Facebook Live features, the Mevo remains a camera uniquely designed just for going live as it is the only consumer option of this type on the market, with quality and usability above what is available when streaming from a smartphone.


Wikileaks has hit some snags in its efforts to cooperate on fixing CIA hacks

Why it matters to you

Getting those CIA hacks fixed before they’re made fully public might be a bit more problematic than it first appeared.

When Wikileaks released its cache of CIA documents earlier in March, it held back the details on zero-day exploits that would allow cybercriminals to access vulnerabilities in computer equipment used by the American public. Wikileaks promised to hold onto them until it could work with developers on making sure the vulnerabilities in question are patched.

That was a welcome tactic, theoretically, but it has apparently run into some snags. It appears Wikileaks attached some conditions to its cooperation and meeting those conditions might be problematic for some of the companies involved, Schneier on Security reports.

More: WikiLeaks won’t publish zero-day exploit details until developers can fix them

WikiLeaks provided an update via Twitter that laid out the fact that, according to the organization, some companies are hesitant to sign off on the conditions due to their U.S. security clearances:

Update on CIA #Vault7 "zero day" software vulnerabilities


— WikiLeaks (@wikileaks) March 18, 2017

There might be other conditions holding companies back. According to sources, one condition is a 90-day time limit on getting vulnerabilities patched. Such a condition would be similar to the practices of Google’s Project Zero, which has a hard limit of 90 days on how long it will wait to publish an exploit after information is shared with a vendor.

According to Motherboard, there might be other issues as well. Companies could be concerned about how the documents were procured and whether any of the information on the CIA hacks came from the Russian government. Regardless of the reasons, it’s clear that Wikileaks and the developers involved with the vulnerabilities have some distance between them on how to proceed in fixing and then disclosing the exploits.

In the meantime, there is a project underway that seeks to make sense of the 400 companies, products, and terms included in the Vault 7 cache of documents that Wikileaks has already published. If successful, the project would at least help anyone concerned about whether any of their devices have potentially been compromised.

This is a very fluid situation involved a number of organizations that all have stakes in the outcome. The information will likely make its way to the public sphere and so the only question remaining is what exactly will be the impact and whether or not all of the CIA hacks have been resolved.

Mar is devoting $50 million in grants to help close the education gap

Why it matters to you

Google is helping fight educational inequity by pledging $50 million in grants.

If there is one critical weapon in the fight against inequality, it’s education. After all, Google points out, there remain 130 million students around the world have yet to fully grasp basic subjects like reading and math, even after four years of primary education. But now, the tech giant is hoping to tackle this problem head on by way of $50 million in grants to nonprofits “building tech-based learning solutions,” all of which are geared toward closing the education gap.

Already, Google has given more than $110 million over the course of the last five years with this goal in mind. But this latest announcement serves as Google’s “largest dedicated portfolio” to date and focuses on nine organizations representing countries from across the world. Not only will Google be providing financial support but Google volunteers will also aid in various areas of expertise, including user experience design, translation, offline functionality, and data analytics.

More: Misplace your car? A new Google Maps feature in Android will help you find it

“Our education grants will focus on three areas where technology can help: giving more students access to quality learning materials, supporting teacher development, and reaching students in conflict zones,” Google noted in a blog post announcement. “Around the world, students in low-income communities have to learn with fewer books, out-of-date texts, and materials that are culturally irrelevant or even in the wrong language.” But with technology, Google hopes to overcome geographic and financial hurdles, and provide students with educational resources that are engaging, interactive, and ultimately, effective.

Google will focus primarily on three key issues — first, giving students the right materials to succeed; second, keeping teachers trained and engaged; and finally, helping students learn in crisis. You can stay up to date on Google’s progress by signing up for the company’s education email list.


Pre-register now for Galaxy on Fire 3: Manticore, the latest sci-fi epic launching on Android

Can you save the world from impending destruction?


Fans of epic space battles rejoice — you can now pre-register to be informed of the official release of Galaxy on Fire 3: Manticore, the latest sci-fi epic released by Deep Silver FISHLABS. You can sign up for pre-registration here to be notified once the game is available on select Android devices.

Check out the trailer below:

The game is a sequel to the well-recieved Galaxy on Fire 2 HD, which has been downloaded millions of times from the Google Play Store while maintaining a solid 4.4 user rating. You should certainly check it out if you haven’t already.

The latest entry in the franchise promises to be bigger than ever, with even better graphics than the previous titles and a variety of missions to unlock.The game will feature next-gen Vulkan graphics standard along with the legacy Open GL ES graphics standard to ensure the game is available across a wider range of devices. Reviews on Metacritic of the iOS version have been somewhat mixed, with some reviewers disappointed with the changes the developers made to some of the core gameplay elements compared to GoF2.

We’ll just have to wait and see for ourselves. In the meantime, Galaxy on Fire 2 HD is a free download from the Google Play Store, with in-app purchases available to unlock the two story add-ons Valkyrie and Supernova.


What’s New in Android O: Everything you need to know


See what the latest and greatest version of Android has in store for you!

Android O brings several changes to existing features as well as all new features. Since it first arrived in 2008, Android has been a very fluid bit of software. The mobile space is always evolving and Android has evolved along with it so it could meet the needs of people like us who use it every day.

With the first developer preview of Android O, we get a glimpse of some of the new features we can expect when it’s released later this year. Google also tells us that this is just a few of the things we can expect with the next version of Android.

How to get Android O on your Pixel or Nexus (and how to roll back to Nougat)

Background limits

Starting with Android 7.0, Android can restrict certain activities an application wants to do while it’s in the background. Android O builds on this beginning and places top priority on saving power and improving battery life without the user (that’s us!) having to do anything or install anything,

New limits on implicit broadcasts (sending “signals” for other apps or activities to act upon), background services (activities of an app that continue to run when it’s not on the screen) and location updates (checking to see where you are using Android’s location services) are automatic. This means it’s easier to build apps that don’t have an impact on battery life and the user doesn’t have to manage anything.

This is a new area for Android, so developers are encouraged to study the documentation and try out the background execution and location limits before Android O is available for consumer devices.

Notification channels


Android N brought a new framework for notifications and ways for developers to use it so we get more information in a space where real estate is at a premium.

With Android O Google is introducing new Notification channels: grouping notifications together by their type. Notifications are still managed by the app that delivers them, but users can control how things are displayed on a per-channel basis. This way we can decide things like how a news app notifies us or a music player shows a persistent notification. Notification channels is a new way for us to control the rich notifications that Android apps bring to us.

Autofill APIs

Platform support for autofill means better security and a powerful way for an application to store repetitive information.

With the new Autofill API, a user will be able to choose a source for autofill data, and applications that need to store and retrieve this sort of data no longer will need to act as an Accessibility service. An app like a password manager can bundle its own activity for using the autofill API and we can choose it when we need it much like choosing a new keyboard. An app could also be built that acts as a global storage for autofill data without being associated with any one particular program.

Picture in picture for handsets


Google is moving PiP display support to Android phones.

Currently, Android TV has a native PiP display method but handsets use a standard multi-window view versus an overlay. With the new way of doing things, and apps can be designed so that the supplementary window is strictly for content and controls or other bits of app chrome can be placed elsewhere.

This also brings a new way to handle screen overlays and methods for a device to launch an app or activity (a portion of an app) on a remote display.

Font resources in XML

Android O promotes fonts to a full resource type.

This means that fonts can be defined the same way colors and other resources are in application layouts using XML, and developers will have more control over the fonts and style they use. This might mean we can have apps with their own custom fonts without any complicated procedures by developer or users.

Adaptive icons

The Google Pixel Launcher brought adaptive icons, and now Android supports them systemwide and natively.

Options can be given for different shaped masks that define the outside border (think squircles) and icons can be animated. Adaptive icons will be supported in the launcher, shortcuts, device Settings, sharing dialogs, and the app overview screen.

Wide-gamut color for apps

Developers building applications for Android O on devices that support wide-gamut color can now leverage those displays.

Apps like photo editors and image viewers can make use of this, and the developers simply need to enable a setting letting the system know the app is wide-gamut color aware and embed a wide color profile. Some of the support profiles are AdobeRGB, Pro Photo RGB, and DCI-P3.


Android O brings some changes to the way our devices communicate with other devices. Welcome changes include:

  • High-quality Bluetooth audio through the Sony LDAC codec. Your favorite songs will sound even better through Bluetooth connections.
  • NAN (Neighborhood Aware Networking) connectivity using the Wi-Fi Aware specification. Devices with supported hardware can communicate with each other using Wi-Fi without a central access point.
  • Telecom framework introduces new ways for third-party calling apps to work with each other and with your carrier’s special features. New APIs now support apps that don’t need to use the universal system phone app to display calling information and this data can be displayed and controlled over Bluetooth.

Keyboard navigation


Android on Chromebooks means we need a better way to use all the features of an app through the keyboard and mouse. Android O focuses on building a better model for arrow and tab key navigation. This is one of those things that are both better and easier for developers and end users.

AAudio API for Pro Audio

The new AAudio API was built for applications that need a high-performance and low-latency audio path. Audio data can be read and written via normal streams and the AAudio API handles the routing and latency.

The first versions of the AAudio APIs are not yet complete but are a great way for developers who need these features to provide feedback. We want the people building an equivalent of GarageBand for Android to have some say in how the new features work!

WebView enhancements

Android O enables the multiprocess mode for WebView components from Nougat as the default and adds an API so that developers can handle their own errors and crashes.

This makes applications that use web development languages better stability and security, and users will benefit if developers enable Google Safe Browsing for remote URLs.

Java 8 APIs and runtime optimizations

Android O supports new Java Language APIs, including the new java.time API introduced with the latest version of Java 8. Optimization for the new runtimes is also included for better performance and stability in apps designed for Android O.

It’s important to remember that early builds of Android O are designed for app developers to get a head start and aren’t really consumer focused. That means the features introduced during any preview period are subject to change, get better, break or even be removed. We’ll keep this page updated as we see more from Google about Android O!

More to come

We’ll probably hear lots more about Android O and its upcoming beta program in the next few weeks, so stay tuned!

Android O


  • Everything new in Android O
  • Should you put Android O on your phone?
  • How to install the Android O Developer Preview
  • Android O isn’t in the Android Beta Program yet
  • Join the Discussion


Should you install Android O developer preview on your Pixel or Nexus?


Android O is now available to download as a developer preview. But that doesn’t mean you should do it.

The day that Google releases a new version of Android is one of the most exciting of the year, especially for early adopters like us who want to play with all the new features and see what’s in store for the final release.

But unlike last year, when Google released its Android N preview alongside an easy-to-install beta program, the company is going decidedly old school with this one, reverting back to the tried-and-true method of factory images that require an unlocked bootloader and some knowledge of terminal commands. This isn’t a surprise — Google has been doing this for both developer previews and final releases for years — but delaying an easy-for-consumers-to-install Android O version until later in the year speaks to the early nature of Android O right now. In other words…

You shouldn’t install the Android O developer preview on any phone you need to use on a daily basis.

Things are going to be broken


We say this every year, but things are definitely going to be broken with the Android O developer preview. There are going to be lots and lots of bugs, and core features of the phone, from making calls to connecting to Wi-Fi and Bluetooth devices, may be incomplete or completely not working.

Moreover, many of Google’s own apps will not have been updated to take advantage of the new system APIs — things like Font Resources, Adaptive Icons, and Picture-in-Picture — potentially limiting its usefulness.

Third-party apps are not going to be compatible

Google doesn’t usually allow developers to release public versions of their apps with support for the latest Android APIs until a few weeks before the final public release. In this case, that means we’ll likely have to wait until late August or even into September — months after Google I/O — for anything resembling an interesting set of user interactions.

In the meantime, the Android O dev preview will likely have been updated at least three times with new versions that fix bugs and overcome some of the more core functionality issues we’re seeing in the initial release. For something like Picture-in-Picture, for instance, you’re not going to see a working version of YouTube — probably the most important app to support the feature — until close to the final release.

It’s a pain in the butt to install


Finally, it’s not easy to install the Android O developer preview, especially if you’re not familiar with the commands that require you to unlock your bootloader and flash a system image.

Worse, even if you get there, you will have to factory reset your phone at some point in the process — when you unlock your bootloader in the first place, or when you flash your phone back to Nougat.

But we’re not going to stop you

Obviously, if you want to install Android O on your phone or tablet, we can’t stop you. So if you’re going to do it, at least read up on the procedure, and know what you’re getting yourself into.

How to get Android O on your Pixel or Nexus

There’s lots more to come

Google promises that it will talk lots more about Android O at Google I/O in May, and that there will eventually be an easy-to-install beta, just like there was with the Android N beta in 2016. This is good news — the updates will likely come fast and furious — and we’d recommend waiting until then to install Android O on any phone or tablet you actually want to use on a daily basis.

Android O


  • Everything new in Android O
  • Should you put Android O on your phone?
  • How to install the Android O Developer Preview
  • Android O isn’t in the Android Beta Program yet
  • Join the Discussion


Google announces Android O, Developer Preview image now available


Start getting ready for the latest version of Android.

Google is continuing its transparency of pre-releasing early builds of new versions of Android with the announcement of the Android O Developer Preview. As always, the Developer Preview is designed to give developers an early look at what’s coming in Android O so they can start to make their apps compatible with the new APIs and design guidelines. It does, of course, give all of us fans of Android an early look at what Google has up its sleeve in terms of new features as well.


Android O, as it stands right now with what Google is showing us, doesn’t have a ton of eye-popping features. Just like previous Developer Previews, you get a little taste of new features and more importantly overall structural changes, but future builds of the Developer Preview can and will add more as Google develops it.

Here are a few of the high points in Android O Developer Preview 1:

  • Background limits: Additional automatic limits will be put on apps running in the background, particularly in terms of background services and location updates. These changes will let developers create apps that have less impact on performance and battery.
  • Notifications: With Android O, users will be able to manage which kinds of notifications come from each app, rather than controlling all notifications for that app the same way. How granular the controls are will be defined by the app developer. There are also new visual changes to grouping of similar notifications that make it “easier for users to see what’s going on” when receiving messages or glancing at the shade.
  • Autofill APIs: Users can choose an “autofill” app similarly to how you currently choose a default keyboard. Password managers will be able to work with this autofill setting to surface usernames and passwords that you can enter into apps without switching to the password manager.
  • Adaptive icons: Developers can create adaptive icons that can change based on how the system wants to display them, so they fit in on different phones with different interface looks. New icons can be animated in various parts of the interface when interacted with.
  • Bluetooth audio: Android O supports high-quality Bluetooth audio codecs, including Sony’s LDAC codec.

These are the changes that are most likely to get users excited and ready for the new version to come to their phones, but still require lots of work from developers to support the new changes. At least in this first Developer Preview, there’s very little to “show” here — it’s mostly framework and API changes that let developers create better experiences when running apps on Android O.

More: How to install the Android O Developer Preview

The first Android O Developer Preview is available today in the form of a factory image file, and is in no way designed to be used on a primary phone or by regular consumers. It’s available for the Pixel, Pixel XL, Nexus 6P, Nexus 5X, Pixel C and Nexus Player. Coinciding with that decision, Android O is not yet part of the Android Beta Program — you’ll have to wait for a later release that’s considered more stable.


According to Google’s Android Developers website, the Android O Dev Preview is not expected to be bumped to revision 2 until mid-May, with Dev Preview 3 landing in mid-June and a fourth preview landing shortly before final release in Q3 2017.

Android O


  • Everything new in Android O
  • Should you put Android O on your phone?
  • How to install the Android O Developer Preview
  • Android O isn’t in the Android Beta Program yet
  • Join the Discussion


Android O isn’t available in the Android Beta Program yet, will likely join in mid-May

Everyone with a Pixel or modern Nexus will get their opportunity to use Android O soon.

With Android O entering Developer Preview status, this is our first opportunity to download and run a preview version of the latest OS. Unfortunately for those who became accustomed to simply enrolling in the Android Beta Program and getting builds over-the-air, this first Developer Preview of Android O isn’t available in the Beta Program.

If you want Android O right now, your only way to get it will be through manually flashing an image of the Developer Preview.


And that is a great indication of who should actually be using the first publicly-available build of Android O: developers who need the system image to start working on updating their apps for the new platform version. When Google feels it’s stable enough to push out to Beta Program users, which tend to be more of the realm of enthusiasts eager to see the new interface and features, an update will arrive to everyone who opts into the Android Beta Program.

More: How to manually update your Pixel or Nexus

Most of us should just be patient and wait for the Android Beta Program update.

Considering that Google just released an updated version of Android 7.1.2 to the Beta Program, this timeline of waiting until after the first Developer Preview makes sense — even though the first Developer Preview of Android N did land on the Android Beta Program the same day as the flashable image last year.

Google’s timeline for the Android O Developer Preview lists mid-May for the Dev Preview 2, and specifically calls it a “beta” launch to the Dev Preview 1’s “alpha” state. There’s a great chance this means that the Android Beta Program will get in on the Android O fun with this release. It is set to coincide with Google I/O 2017, naturally.

But we don’t know for sure yet. We’ll just have to wait and see. For now, if you want to try your hand at Android O on a non-critical device, you’ll need to manually flash the system image yourself.

For the vast majority of us who will plan to wait for the Android Beta Program release, expectations are that it will be available for the Pixel, Pixel XL, Nexus 6P, Nexus 5X, Pixel C and Nexus Player once released.

Android O


  • Everything new in Android O
  • Should you put Android O on your phone?
  • How to install the Android O Developer Preview
  • Android O isn’t in the Android Beta Program yet
  • Join the Discussion


How to get Android O on your Pixel or Nexus (and how to roll back to Nougat)


Here’s how to get the Android O Developer Preview on your Nexus or Pixel device.

The Android O Developer Preview is here, and if you’re one such developer (or just a person who doesn’t listen to good advice!) here’s how to install it onto your phone or tablet.

Which devices support the Android O Developer Preview?

The preview is supported on the following phones and tablets:

  • Pixel
  • Pixel XL
  • Pixel C
  • Nexus 6P
  • Nexus 5X
  • Nexus Player

What you need to know beforehand

The Android O Developer Preview is being released only as a factory image, which means you can’t just go to Android’s beta page and get the update as an over-the-air release. This is because O, in its current form, is very early, and isn’t intended to be installed by the general population — just by developers.

In order to update a phone or tablet to Android O, you need to first unlock your bootloader.

Before we go into these steps, it is strongly recommended that you have previous knowledge of working with the Android SDK (software development kit) and Terminal (OS X or Linux) or Command Prompt (Windows), as it is possible to harm your device if something were to go wrong in the following process.

You’ll need to download an updated Android SDK that has the latest Android O tools and images, and you can grab it from the Android Development website and follow their instructions on how to install it correctly. For the following process all you will need is the adb and fastboot files which are located in the Platform Tools folder.

Additionally, all the following commands are written as they would be in Terminal on a Linux or OS X platform. If you are following this guide and using a Windows machine, you will not need to use the “./” seen in the guide.

Enable developer settings and USB debugging

Before you begin, you’ll need to have a compatible Nexus or Pixel device running Android 7.x Nougat.

Go to your Settings and scroll down to About Phone/Tablet
Tap on the Build number seven times until the dialog box says you are now a developer
Go back to the Settings menu and you should find a new option called Developer options. Click into the Developer options
Make sure that the developer options are turned on and that USB debugging is checked on
Make sure Enable OEM unlock is checked.
Plug your device into your computer and click “OK” on the dialog box asking you to Allow USB debugging while connected to the computer. You can also select to always allow access on that computer

If done correctly, this will be everything you will need to do on your phone or tablet for the moment.

Unlocking your bootloader


Nexus devices and Pixel phones bought from Google directly have a bootloader you can unlock. If you want to manually flash software, you’ll need to do this.

To do this you must first boot into your bootloader. You can either manually turn off your phone or tablet and hold down the power button and the volume down button to enter your device’s Bootloader Menu or you can enter the following commands into your terminal or command prompt.

Run the following command to make sure your device is properly connected to your computer. If it returns a string of characters it means that you are all set to start updating your device.

./adb devices

Now to enter into the Bootloader menu just run the following command.

./adb reboot bootloader

At the bottom of the screen there will be several things listed including the lock state of the device. This should say locked unless you have unlocked your bootloader in the past and never went back and locked it again.

To unlock your bootloader, which is required only when flashing a stock firmware image (not sideloading and update, which we’ll get to soon), you must enter the following commands. Remember that when unlocking your Nexus’ bootloader it will factory reset your device, so you will lose everything stored on it. If you have not yet backed up anything important on your device you can hit the power button while Start is highlighted in the Bootloader menu and this will boot you back into your device like normal. Now back to unlocking your bootloader.

Use the command:

./fastboot flashing unlock

A dialog will appear on the device asking if you are sure about unlocking. Again this will factory reset your device, so if you want to back out of the process you just need to select no with the power button. If you are ready to unlock your bootloader you press the volume up button and then the power button to confirm that you wish to unlock your bootloader.

./fastboot reboot-bootloader

It is recommended to reboot the bootloader just to give itself a check to make sure everything is working correctly before moving onto the next step.

Flashing the stock firmware image

Now that your bootloader is unlocked, it’s time to flash the Android O image. To find the system images, head on over to the Factory Images page, find your device, and download the latest factory image available. It is easiest to then uncompress the file in the Platform Tools folder where the adb and fastboot files are so that you don’t have to type the path to the different files when flashing the firmware. (Or if you know that you can drag a file into a terminal window to copy the path, just do that.)

To begin, make sure you are still in the bootloader menu on your device and double check that your bootloader is in fact unlocked.

First, make sure that your computer is communicating correctly with your phone or tablet. As long as your device’s serial number comes back as a connected device you are ready to begin updating your device.

./fastboot devices

Now it is time to flash the updated bootloader with the following command.

./fastboot flash bootloader [bootloader file].img

You will not see anything on the screen of your device but there should be a dialog in your terminal or command prompt. When it is done flashing the bootloader you should reboot back into the bootloader as to make sure everything is still working correctly.

./fastboot reboot-bootloader

Next you flash the updated radios. This step is only necessary if you are updating the firmware of a phone or tablet that has cellular radios built into it.

./fastboot flash radio [radio file].img

./fastboot reboot-bootloader

Finally, it’s time to flash the actual system image to your phone or tablet.

Warning: The following line of code will wipe your device. If you do **not* want your device to be wiped, remove the “-w” from the command. The update should still take just fine, and it will not wipe your user data.

./fastboot -w update [image file].zip

When this is done, your phone will restart itself and boot up normally. As this process clears all data from your device, it will take slightly longer for your device to boot up into Android O for the first time. Once you have been greeted with the device setup walkthrough process, you know you have successfully flashed a new version of the firmware.

If you do not want to enter the commands manually there are scripts included inside the compressed folder containing the system image that will do most but not all of the heavy lifting for you. The flash-all script files will automate the flashing of the bootloader, radios (if needed), and the system image. The problem with this process is that you must first make sure that your phone is in the bootloader menu and its bootloader must be unlocked before starting the script. Of course if these are not already done the script will fail to run and nothing will happen.

How to revert back to Nougat from the Android O Developer Preview


So you ignored our advice (or you’re a developer who needs his or her phone or tablet back) and need to re-install Nougat. That’s pretty easy! All you need to do is find the right system image compatible with your handset or slate and run the same procedures as above but with the Android Nougat image.

When finding your Nougat image, make sure you are downloading the correct one that corresponds with your device. If you’re running a Verizon or Rogers Pixel, for instance, you’ll have to make sure you download the right one.

Problems? Confused?

If you’re having issues or want to ask a question, come join us in our forums for all the tips, tricks and advice you can handle!

Android O


  • Everything new in Android O
  • Should you put Android O on your phone?
  • How to install the Android O Developer Preview
  • Android O isn’t in the Android Beta Program yet
  • Join the Discussion


Android O Dev Preview 2 won’t land until mid-May, with final release in Q3

Google is increasingly transparent about its software releases.

With the Developer Preview program, we get a super early look at what Google’s working on in Android O — the only downside is it takes several months then to get all of the information. With the release of Android O Developer Preview 1 we don’t have a complete look at all of Android O’s new features, but we do have a timeline for when updates to the Dev Preview program will land.


As you can see, we’re looking at a considerable wait before our second release — the timeline pegs it for mid-May, conveniently coinciding with Google I/O 2017 where we expect to learn more about the core features of the OS rather than just heavily developer-focused changes. This would be a good bet for when the Android Beta Program could get on board, depending on how stable the release is.

The first big update to Android O will land in mid-May, likely at Google I/O.

We then have to wait about a month for a third Developer Preview release in mid-June, which coincides with Google finalizing the new APIs in Android O so developers can lock in changes to their apps to make sure they’re ready for the final release. We’ll get a quick tune-up Developer Preview 4 sometime about a month later, and then the waiting game starts for the final full announcement in Q3 2017 — likely coinciding with a Pixel 2 launch.

So that means we all have a nice long road ahead of speculation and playing with far-from-finished software on our Pixels and Nexuses. And if you want to get into the future a little but don’t have an extra device to sacrifice for the cause, consider waiting until we get to at least Developer Preview 2 — you’ll be glad you waited.

Android O


  • Everything new in Android O
  • Should you put Android O on your phone?
  • How to install the Android O Developer Preview
  • Android O isn’t in the Android Beta Program yet
  • Join the Discussion

%d bloggers like this: