Introduction
Can any Android release from the late 2010s claim to have changed the platform’s trajectory more than Oreo? Project Treble didn’t add emoji or notification dots — it restructured Android’s entire hardware abstraction layer to solve the update problem that had plagued the platform since 2008. In an era when most people judged Android releases by emoji counts, Oreo was doing the engineering work that would determine whether Android devices got updates at all.
Android 8.0 Oreo was officially released on August 21, 2017, with 8.1 following on December 5, 2017.
Oreo introduced notification channels — the biggest notification architecture change since Android 1.0. Picture-in-picture brought floating video windows to phones. Autofill platform made password managers first-class citizens. And Project Treble modularized the OS so manufacturers could deliver updates faster — or in theory, at all. The Pixel 2 launched with Oreo and the best smartphone camera ever measured, while the Essential PH-1 tried (and failed) to be the third premium Android option.
Quick Facts
| Item | Value |
|---|---|
| Version | Android 8.0 – 8.1 |
| Codename | Oreo |
| API Level | 26 (8.0), 27 (8.1) |
| Release Date | Aug 21, 2017 (8.0) / Dec 5, 2017 (8.1) |
| Linux Kernel | 4.10+ |
| Initial Device | Google Pixel 2 / Pixel 2 XL (8.0) |
| Previous Version | Android 7.0/7.1 Nougat |
| Next Version | Android 9 Pie |
What’s New
Notification Channels
Oreo’s notification channels were a structural change to how Android handled notifications. Every notification from an app was assigned to a “channel” — a category like “Messages,” “Promotions,” “Alerts,” or “Silent.” Users could control the behavior of each channel independently:
- Block all promotional notifications but allow transactional ones
- Set specific channels to silent (no sound, no vibration) while others vibrate
- Override the importance level for individual channels
- All this, without the app being able to override user choices
This was a power-user feature that casual users benefited from without knowing it existed. Developers had to categorize their notifications — apps that dumped everything into a single channel had noisy, uncontrollable notifications. Good apps implemented channels thoughtfully, and the notification experience improved dramatically.
The channel system also meant apps could no longer change notification importance programmatically. If a user set a channel to “Low” priority, the app couldn’t override that to “Urgent.” This was a deliberate power shift from developer to user, and it was the right call.
Picture-in-Picture (PiP)
Android Oreo brought picture-in-picture to phones. YouTube, Google Maps navigation, Duo video calls, and Netflix (eventually) could float in a small, movable overlay while the user did other things. The PiP window could be dragged, dismissed, or tapped to return to full screen.
PiP had been available on Android TV since Nougat. Oreo brought it to phones with PictureInPictureMode in the framework. The implementation was good — smooth, low-latency, no performance impact in testing — but adoption was slow. YouTube limited PiP to YouTube Premium subscribers (a paywall that generated backlash). Google Maps PiP was useful for navigation while messaging. Most third-party video apps took years to implement it.
Project Treble
Project Treble was the most important under-the-hood change in Android since the transition to ART. It modularized Android’s hardware abstraction layer (HAL), separating vendor-specific code (drivers, hardware support) from the Android framework.
Before Treble, every Android update required chipset vendors (Qualcomm, MediaTek, Samsung) to recompile their driver code against the new framework. Vendors had no incentive to support old chipsets, so manufacturers couldn’t update devices even if they wanted to. The result was the Android update crisis: most phones received one major update, if any, and security patches were inconsistent at best.
Treble created a stable Vendor Interface (VNDK) between the framework and vendor implementation. Framework updates no longer required vendor code changes. A device with Treble could theoretically boot a Generic System Image (GSI) — a pure AOSP Android build — regardless of manufacturer.
Treble was mandatory for devices shipping with Oreo (and devices upgrading to Oreo from Nougat, though implementation was less strict). It was also the reason Android update timelines improved noticeably after 2018: Samsung extended update guarantees to 3 years, OnePlus and Nokia delivered faster updates, and the GSI program let developers test new Android versions on Treble-compatible devices months before official OTAs.
Autofill Platform
Oreo made password managers system-level services. Instead of using accessibility services (which were slow, insecure, and prone to breaking), password managers could implement AutofillService and receive native integration with Android’s autofill framework.
Autofill worked across browsers, apps, and WebViews. It was more reliable, more secure (the system managed autofill, not the accessibility layer), and faster than any previous approach. LastPass, 1Password, Dashlane, and Google’s own autofill service all adopted the API.
This was a direct response to iOS’s superior password manager integration. With Oreo, Android caught up and arguably surpassed iOS in this area — the autofill framework was more flexible and supported more providers.
Smart Text Selection
Oreo used on-device machine learning to recognize text types — addresses, phone numbers, URLs, names — and suggest appropriate actions. Double-tap an address in any app, and Android offered to open it in Google Maps. Double-tap a phone number, and it offered the dialer. The text selection handles intelligently snapped to recognized entity boundaries.
This ran entirely on-device using TensorFlow Lite, with no data sent to Google. The model was small enough to run on the Pixel 2’s Pixel Visual Core, and later, on any device with a sufficiently powerful CPU/GPU.
User Interface Changes
- Notification dots: App icons on the launcher showed a colored dot when the app had unread notifications. Long-pressing showed the notification preview. This was Apple-style notification badging, Android-style.
- Revamped emoji: Oreo replaced Android’s blob emoji with a redesigned set closer to the Unicode standard. The blobs — beloved by Android enthusiasts — were gone, and the backlash was swift. Google eventually added a blob sticker pack to Gboard as a concession.
- Settings redesign: Oreo’s Settings app was completely reorganized into logical categories with a cleaner, whiter design.
- Battery menu: The battery settings showed per-app usage more clearly and added adaptive battery prediction (how long until the battery dies based on current usage).
Performance Improvements
- Background execution limits: Oreo restricted what apps could do in the background — no more starting services, no more implicit broadcasts, strict limits on location updates. This dramatically reduced background CPU wake-ups and improved battery life.
- Android Go (8.1): Android 8.1 introduced Android Go — a lightweight configuration for devices with 512 MB–1 GB RAM. Go editions of Google apps (YouTube Go, Maps Go, Gmail Go) ran on these devices, optimized for storage, data, and memory. Android Go brought modern Android to devices that cost $40–80, primarily in India, Africa, and Southeast Asia.
- Boot time: Treble’s modular architecture reduced boot time by reducing driver initialization dependencies.
Security Improvements
- Google Play Protect: Oreo made Play Protect a visible, branded feature — “Google Play Protect: No harmful apps found” in the Play Store and security settings. Play Protect scanned 50 billion apps daily by 2017, and Oreo made that visible to users.
- System-level permissions for unknown sources: Instead of a single “Allow unknown sources” toggle, Oreo let users grant individual apps permission to install APKs. This was more secure and more usable.
- Rollback protection: Oreo’s verified boot was extended to prevent rolling back to older, potentially vulnerable system images.
- Wi-Fi security: Support for WPA3 was laid with Oreo’s improved Wi-Fi subsystem, though full WPA3 certification came later.
Developer Features
| API Level | Key Additions |
|---|---|
| 26 (8.0) | Notification channels, PiP, Autofill, Smart Text Selection, Fonts in XML (downloadable fonts), adaptive icons, wide-gamut color, AAudio (low-latency audio API), Wi-Fi Aware, WebView enhancements, background execution limits |
| 27 (8.1) | Android Go configuration, Neural Networks API, shared memory API, WallpaperColors API, autofill enhancements, Bluetooth battery level reporting |
Adaptive icons were important for visual consistency: icons could be displayed in circular, squircle, rounded-square, or square masks depending on the launcher, with a unified adaptive icon format that supported both a foreground and background layer.
Devices That Shipped With Oreo
- Pixel 2 & Pixel 2 XL — Launched with 8.0. 5.0/6.0-inch 1080p/1440p P-OLED, Snapdragon 835, 4 GB RAM, 12.2 MP camera (DxOMark 98, highest ever at launch). The Pixel 2 XL’s LG-manufactured P-OLED panel had severe blue shift and burn-in issues. The 5-inch HTC-built Pixel 2 had a Samsung AMOLED and was fine.
- Essential PH-1 — Andy Rubin’s ambitious but doomed phone. Titanium and ceramic body, 5.7-inch 1312×2560 LTPS, Snapdragon 835, 4 GB RAM. Launched with 7.1, updated to 8.0 quickly. Brilliant hardware, terrible camera, company collapsed.
- Samsung Galaxy S9 / S9+ — Launched with 8.0 and Samsung Experience 9.0. 5.8/6.2-inch 1440p Super AMOLED, Snapdragon 845 / Exynos 9810, 4/6 GB RAM, dual-aperture f/1.5-f/2.4 camera. Incremental but refined.
Comparison With Nougat
| Android 7.x Nougat | Android 8.x Oreo |
|---|---|
| Basic notification grouping | Notification channels with per-channel control |
| PiP on Android TV only | PiP on phones |
| Accessibility-based autofill | System-level Autofill framework |
| Basic text selection | ML-powered Smart Text Selection |
| Monolithic framework | Project Treble modular architecture |
| Blob emoji | Redesigned Unicode-standard emoji |
| No Android Go | Android Go (8.1) for low-RAM devices |
| API Levels 24–25 | API Levels 26–27 |
Oreo was Android’s infrastructure release. Notification channels, Treble, autofill, and background limits weren’t flashy, but they improved Android’s fundamentals in ways users felt daily — fewer unwanted notifications, better battery life, password managers that actually worked, and the promise (finally) of faster updates.
Legacy and Impact
Project Treble is Oreo’s most significant legacy. It didn’t immediately solve the update problem — Samsung still took months to deliver Android 9 to the Galaxy S9 — but it created the technical foundation for faster updates. The GSI program let developers and enthusiast test new Android versions on any Treble-compatible device. ROM development flourished. Manufacturers that cared about updates (OnePlus, Nokia, Essential) used Treble to deliver OTAs faster.
Notification channels became the standard notification architecture for all subsequent Android versions. The per-channel control empowered users in a way Android had never done, and developers were forced to think about notification taxonomy, not just notification frequency.
Android Go extended Android’s reach to the bottom of the market, where billions of potential smartphone buyers lived. Go-edition apps ran on 512 MB RAM devices, consumed less data, and cost less storage. By 2020, over 100 million Android Go devices had been activated.
End of Support
- Play Services: Support continues for Oreo (API 26+), though some features require API 29+.
- Security patches: No official patches since late 2021 (Pixels), early 2022 (Samsung flagships).
Oreo devices are still semi-functional — Play Store works, most apps support API 26+, and Treble means GSIs can theoretically provide newer Android versions. But without security patches, they’re not advisable for daily use.
Fun Facts
- The Oreo partnership: Google’s second branded Android release (after KitKat). Oreo cookies featured Android-themed packaging worldwide. The announcement coincided with a solar eclipse on August 21, 2017 — Google unveiled “Android Oreo” at a press event in New York during the eclipse.
- Easter egg: Tapping the Android version showed an Oreo cookie. Long-pressing launched an octopus floating in a dark ocean. Swiping let you “swim” the octopus. One of the stranger Android easter eggs.
- Blob emoji backlash: The death of Android’s blob emoji generated more consumer outrage than any technical change in Oreo. Headlines like “Google killed the blob emoji and people are furious” were not satire. Google’s subsequent blob sticker pack was a direct response.
- Essential PH-1’s failure: The Essential Phone was the most anticipated Android phone of 2017 — Andy Rubin, creator of Android, launching his own device. It shipped months late, the camera was terrible, Essential dropped the price from $699 to $499 within months, and the company folded in 2020 after failing to ship a sequel.
Frequently Asked Questions
What API level is Oreo?
API Level 26 (8.0), Level 27 (8.1).
What is Project Treble?
Project Treble modularized Android’s hardware abstraction layer, separating the Android framework from vendor-specific driver code. This allows framework updates without requiring chipset vendor recompilation, enabling faster and longer-term OS updates.
What are notification channels?
Notification channels are categories that every notification belongs to. Users can control the behavior (sound, vibration, visibility) of each channel independently. Developers must assign notifications to channels; apps that don’t implement channels properly are noisy and less usable.
Did Pixel 2 displays have issues?
Yes. The Pixel 2 XL’s LG P-OLED panel suffered from blue shift at angles, graininess at low brightness, and burn-in after extended use. Google extended the warranty to 2 years and issued several software updates to mitigate the issues. The smaller Pixel 2 used a Samsung AMOLED and was fine.
Final Thoughts
Oreo was the kind of Android release that engineers celebrated and consumers ignored. Project Treble didn’t ship with a demo video or emoji. Notification channels required developers to do work before users saw benefits. Background limits improved battery but occasionally broke apps in confusing ways.
But these changes were structural, not cosmetic. Treble addressed a problem that had plagued Android for a decade. Notification channels gave users agency over their attention. Autofill made security convenient. Android Go brought modern Android to people who couldn’t afford $200 phones.
Oreo was Android growing up — doing the unglamorous work of building a platform that could scale, update, and secure itself without constant hand-holding. It wasn’t the Android release people talked about, but it was the one that made the next five years of Android possible.
Related Articles
- Android Version History (2008–Present)
- Android 7 Nougat: Complete Guide
- Android 9 Pie: Complete Guide
- Project Treble: How Android Fixed Its Update Problem
- Notification Channels: A Developer’s Guide
- Android Go: Google’s Emerging Market Play
References
- Official Android 8.0 / 8.1 Platform Highlights
- Android Developers Blog: “Introducing Android 8.0 Oreo” (August 2017)
- Project Treble technical documentation (source.android.com)
- Google Pixel 2 / Pixel 2 XL product documentation
- Android Go Edition technical specifications
- Google Play Protect transparency report, 2017