Introduction
The Holo era ended on November 3, 2014, and it ended hard. Material Design didn’t just replace Holo’s dark blue aesthetic — it rewrote every rule about how Android should look, move, and feel. The result was the most dramatic visual overhaul since Android 1.0, and the most controversial.
Android 5.0 Lollipop was officially released on November 3, 2014, with 5.1 following on March 9, 2015.
Lollipop was Android’s biggest bet: a unified design language spanning phones, tablets, watches (Android Wear), TVs (Android TV), and cars (Android Auto). It made ART the mandatory runtime, killing Dalvik. It introduced lock screen notifications, Priority mode, and the Overview screen that replaced the old Recents view with a Rolodex-style stacked card layout. It also debuted on the Nexus 6 and Nexus 9 — both of which were widely criticized — and was rushed enough that 5.0 was plagued with bugs, including a memory leak that took until 5.1.1 to fix.
Material Design was brilliant. Lollipop 5.0 was not. That tension defines this release.
Quick Facts
| Item | Value |
|---|---|
| Version | Android 5.0 – 5.1.1 |
| Codename | Lollipop |
| API Level | 21 (5.0), 22 (5.1) |
| Release Date | Nov 3, 2014 (5.0) / Mar 9, 2015 (5.1) |
| Linux Kernel | 3.10 (5.0), 3.10/3.14/3.18 (5.1, device-dependent) |
| Initial Device | Nexus 6 (phone) / Nexus 9 (tablet) / Nexus Player (TV) |
| Previous Version | Android 4.4 KitKat |
| Next Version | Android 6.0 Marshmallow |
What’s New
Material Design
Material Design was Google’s most ambitious design initiative ever. It replaced Holo’s flat, dark-blue aesthetic with a colorful, layered, motion-rich design language based on physical metaphors: surfaces cast shadows, ink rippled on touch, elements transitioned with shared-axis animations. Everything had a z-axis position, and the system rendered realistic elevation shadows.
Key Material Design elements:
- Bold colors: The system color palette exploded from Holo blue to a full spectrum. Apps got
colorPrimary,colorPrimaryDark, andcolorAccentattributes. - Elevation and shadows: Views cast shadows based on their Z elevation. Cards and the FAB (Floating Action Button) floated above content.
- Ripple touch feedback: Tapping any interactive element triggered a radiating ink ripple effect.
- Shared element transitions: When navigating between activities, elements could animate seamlessly between screens.
- Floating Action Button: A circular, elevated action button for the primary screen action — the defining UI element of Material Design.
- Motion as meaning: Animations weren’t decorative; they communicated spatial relationships and state changes.
Material Design wasn’t just a new look — it was a design system with comprehensive guidelines, component specs, and animation principles. Google applied it across Android, the web, Chrome OS, and eventually iOS apps too. It was the first time Android had a design language that design professionals took seriously.
ART Replaces Dalvik
Lollipop killed Dalvik. ART became the sole Android runtime, with full AOT compilation for all apps. The performance benefits KitKat previewed now applied to every app, on every device:
- Faster app launches: AOT-compiled apps launched 10–30% faster than Dalvik equivalents
- Smoother runtime performance: No JIT compilation pauses during app use
- Better garbage collection: ART’s concurrent GC was more efficient than Dalvik’s
The transition wasn’t painless. Some older apps relied on Dalvik-specific behavior and crashed on ART. App installs and OS updates took significantly longer due to AOT compilation. Android 7.0 Nougat would later introduce a hybrid JIT/AOT compiler to address these issues, but for Lollipop, AOT was the only option.
Lock Screen Notifications
Lollipop moved notifications to the lock screen, making the lock screen the primary notification surface. Users could read, expand, and dismiss notifications without unlocking the phone. For privacy, individual apps could be configured to hide sensitive content on the lock screen, showing only “Contents hidden.”
This was a dramatic UX shift. The lock screen went from a gatekeeper to an information hub. Apple adopted the same pattern with iOS 10 in 2016, two years later.
Priority Mode / Do Not Disturb
Lollipop introduced system-wide notification priority controls. Users could configure “Priority mode” — only notifications from starred contacts and apps would interrupt, and only during configured hours. All other notifications were silently collected.
This was Android’s first native Do Not Disturb implementation, and it was frustratingly incomplete in 5.0. There was no silent mode that allowed alarms — priority mode was the only option for muting, and it was confusingly tied to notification filtering rather than simple volume control. Android 5.1 added proper “None,” “Priority,” and “All” modes with clearer behavior, but the damage was done. “Where did silent mode go?” became a meme in Lollipop’s early reviews.
Overview Screen (Recents Redesign)
The old Recents view — a list of app thumbnails — was replaced with the Overview screen, a stacked-card Rolodex-style view that persisted across reboots. Open apps appeared as 3D-canted cards; swiping left or right dismissed them.
The card stack looked great in demos and demoed Material Design’s spatial metaphors perfectly. In practice, it was disorienting. Cards from weeks-old sessions mixed with currently-running apps. Chrome tabs appeared as separate cards, cluttering the list. Google eventually reverted to a simpler Recents design in later Android versions.
Battery Saver
Battery Saver mode reduced performance, limited vibration, and restricted background data when battery dropped below 15% (or a user-configured threshold). The status bar and navigation bar turned orange as a visual indicator — a smart choice that made the power-saving state unmistakable.
Battery Saver extended screen-on time by roughly 90 minutes on the Nexus 5, according to Google’s internal testing. It was Project Volta’s most visible consumer feature.
Project Volta
Project Volta was Lollipop’s battery optimization initiative. Its centerpiece was the JobScheduler API, which batched non-urgent background tasks — network requests, database syncs, log uploads — into coordinated windows when the device was charging or idle. Instead of every app waking the device independently, JobScheduler consolidated work into fewer, longer wake periods.
Battery Historian, a new developer tool, visualized per-component power consumption over time, letting developers identify battery-draining behavior in their apps.
User Interface Changes
Everything looked different. Material Design touched every pixel:
- Settings app: Completely redesigned with colored headers, card-based sections, and search.
- Notification shade: White background with cards, per-notification priority controls, and quick settings on a second pull-down.
- Quick Settings: Expanded with a torch (flashlight) toggle, cast screen, and hotspot — features users had been requesting for years.
- System animations: Every transition — app open/close, activity change, dialog appearance — got Material motion: expanding circles, shared-axis slides, and elevation changes.
- Navigation buttons: Simple geometric shapes (triangle, circle, square) replaced the Holo-era icons. Cleaner, simpler, more modern.
- Status bar color: Apps could tint the status bar to match their color scheme — a small change with huge visual impact.
Performance Improvements
- ART mandatory: AOT compilation improved app performance across the board.
- Battery life: Project Volta’s JobScheduler and Battery Saver improved real-world battery endurance.
- 64-bit support: Lollipop introduced native 64-bit ARM (ARMv8/AArch64) and x86-64 support, enabling the next generation of processors with larger address spaces and improved performance.
On the Nexus 5 (Snapdragon 800, 2 GB RAM), Lollipop 5.0 was slower than KitKat. App launches were slightly faster due to ART, but system animations dropped frames and the Overview screen stuttered. The 5.0.1 and 5.0.2 point releases improved things, and 5.1 was noticeably faster. Google’s ambition had outpaced its optimization — a recurring Android theme.
Security Improvements
- SELinux fully enforced: All domains, all processes. Lollipop completed the SELinux enforcement started in Jelly Bean.
- Verified Boot (full): Verified Boot was extended beyond the system partition to include dm-verity for block-level integrity checking. Tampered system images were detected at boot and refused to load.
- Smart Lock: Trusted devices (Bluetooth), trusted places (geofences), trusted face, and on-body detection could keep the device unlocked in safe contexts.
- Encryption by default: New devices shipping with Lollipop were required to enable full-disk encryption out of the box (this requirement was later loosened for low-RAM devices).
The encryption mandate was significant. Google was forcing OEMs to ship encrypted devices, even if it meant a performance hit. Some OEMs (particularly in the budget segment) resisted, but the encryption default closed one of Android’s biggest security gaps: device theft with trivial data access.
Developer Features
API Levels 21 and 22 delivered the largest SDK expansion since ICS:
| API | Description |
|---|---|
android.support.design | Design Support Library — FloatingActionButton, Snackbar, TextInputLayout, CoordinatorLayout |
android.app.job.JobScheduler | Battery-optimized background task scheduling |
android.hardware.camera2 | Full-featured camera API with manual controls, RAW capture, burst mode |
android.media.projection | Screen capture and recording APIs |
android.service.notification | Notification listener enhancements for Android Wear |
android.app.usage | App usage statistics API |
android.telecom | Telecom framework for VoIP and carrier integration |
| Shared Element Transitions | Animated shared element transitions between activities |
| 64-bit support | arm64-v8a, x86_64 ABI support |
| Vector drawables | Resolution-independent vector assets via VectorDrawable |
The Design Support Library was Google’s acknowledgment that implementing Material Design from scratch was too much work. Instead, Google shipped pre-built Material components — FAB, Snackbar, TextInputLayout, CoordinatorLayout, AppBarLayout — through the support library. This was the beginning of the pattern that later became Jetpack: Google providing standardized UI components so developers didn’t have to reinvent them.
Camera2 was also a milestone: it gave developers manual control over focus, exposure, ISO, and white balance — features previously locked to OEM camera apps. RAW (DNG) capture enabled professional photo workflows on Android for the first time.
Devices That Shipped With Android 5.0 Lollipop
- Motorola Nexus 6 — Google’s sixth Nexus phone, built by Motorola. 5.96-inch 1440p AMOLED, Snapdragon 805, 3 GB RAM, 13 MP OIS camera. It was enormous, expensive ($649 unlocked), and divisive. Critics loved the screen and front-facing speakers; everyone hated the size.
- HTC Nexus 9 — Google’s second Nexus tablet, built by HTC. 8.9-inch 2048×1536 IPS, Nvidia Tegra K1 Denver, 2 GB RAM. The 4:3 aspect ratio matched the iPad, a first for Android. The hardware was plagued by light bleed, mushy buttons, and inconsistent build quality.
- Nexus Player — The first Android TV device, built by Asus. Intel Atom processor, 1 GB RAM, voice remote. It launched a new platform category for Google.
- Samsung Galaxy S6 / S6 Edge — Samsung’s most dramatic design change ever. Glass and metal unibody, 5.1-inch 1440p Super AMOLED, Exynos 7420, 3 GB RAM. Launched with 5.0.2 and TouchWiz “Nature UX” (now lighter and closer to stock). The S6 Edge’s curved display was a genuine hardware innovation.
- LG G4 — 5.5-inch 1440p Quantum IPS, Snapdragon 808, 3 GB RAM, 16 MP f/1.8 camera with laser autofocus. Leather back option. Launched with 5.1.
Comparison With Android 4.4 KitKat
| Android 4.4 KitKat | Android 5.0-5.1 Lollipop |
|---|---|
| Holo design language | Material Design |
| Dalvik + ART (optional) | ART only (mandatory) |
| Notifications in shade only | Lock screen + shade notifications |
| Silent mode via volume | Priority mode (confusing, then fixed in 5.1) |
| 32-bit only | 64-bit support (arm64, x86_64) |
| WebView auto-update via Play | WebView auto-update via Play (continued) |
| No Battery Saver | Battery Saver mode |
| Ad-hoc background tasks | JobScheduler batched background work |
| API Level 19 | API Levels 21–22 |
Lollipop was the biggest design and architecture change since ICS, and arguably bigger. Material Design transformed Android’s visual identity. ART changed the runtime foundation. Lollipop set the direction for Android’s next decade.
Legacy and Impact
Material Design is Lollipop’s lasting legacy. It didn’t just change Android — it changed Google. Material Design became Google’s universal design language across Android, web, Chrome OS, iOS, and even physical products. The elevation-and-shadow metaphor, the bold color palette, the FAB, the motion guidelines — these defined Google’s visual identity for years.
But Lollipop 5.0 itself was buggy. The memory leak (a system_server issue that caused progressive performance degradation until reboot) affected every device and wasn’t fully fixed until 5.1. The “silent mode” confusion generated weeks of negative press. The Nexus 6 was too big; the Nexus 9 was poorly built. Lollipop’s adoption was slow not just because of OEM delays but because users on KitKat heard the horror stories and waited.
5.1 repaired the damage. It was faster, fixed the memory leak, added proper notification volume controls, and restored user trust. By the time the Galaxy S6 shipped with 5.0.2 and then 5.1.1, Lollipop was stable. But 5.0’s rough launch cemented a pattern that persists: major Android releases are buggy at launch, and the .1 release is what people should actually install.
End of Support
- Google Play Services: Last version supporting Lollipop was 23.x (2022).
- Google Play Store: Lollipop still has partial Play Store access, but many apps now require API 23+ (Marshmallow) or higher.
- Material Design: The design system has evolved — Material 2 (2018) and Material 3 / Material You (2021) — but Lollipop’s Material 1.0 apps still look acceptable on modern devices.
Lollipop devices exist in a functional gray area: some apps still support API 21, Play Store partially works, and the base OS is modern enough for TLS 1.2. But security updates ended years ago, and the device is effectively unsupported.
Fun Facts
- Why “Lollipop”? The name continued the dessert sequence. The Building 44 statue was a giant lollipop with the Android bugdroid perched on top. The statue was so large it required structural reinforcement.
- Easter egg: Lollipop’s easter egg was a Flappy Bird clone with an Android bugdroid navigating lollipop obstacles. It was absurdly difficult — the hardest Android easter egg ever — and spawned endless “I got a 3 on the Lollipop easter egg” social media posts.
- “Material” name origin: Matias Duarte’s team chose the name “Material” because the design was inspired by paper and ink — physical materials with surfaces, edges, and shadows. The goal was digital design that behaved like real objects.
- Android 5.0’s internal codename: Internally, Lollipop was “Lemon Meringue Pie” before the Lollipop name was finalized. Early AOSP commits reference LMP.
- Nexus 6 price shock: The Nexus 6 at $649 was the first Nexus phone priced like a premium flagship, ending the Nexus program’s reputation for unbeatable value. Google defended the price by pointing to the premium specs; users pointed to the Nexus 5 at $349 and asked what happened.
Frequently Asked Questions
What API level is Lollipop?
API Level 21 (5.0) and Level 22 (5.1).
Why was Lollipop 5.0 so buggy?
The transition from Dalvik to ART, the complete UI rewrite for Material Design, and the aggressive release timeline resulted in a build with multiple issues — most notably a memory leak in system_server that caused progressive slowdowns until reboot. These were mostly fixed by 5.1.
What happened to silent mode?
Lollipop 5.0 replaced silent mode with “Priority mode,” which only allowed notifications from starred contacts and apps. Users who just wanted to mute their phone were confused. 5.1 restored proper “None,” “Priority,” and “All” volume modes.
What is Material Design?
Material Design is Google’s design language introduced in Lollipop. It uses physical metaphors — surfaces, elevation, shadows, ink ripples — to create a consistent, motion-rich visual language. It replaced Holo and has been refined through multiple versions (Material 2, Material 3 / Material You).
Did Lollipop encrypt devices by default?
Google mandated full-disk encryption by default for new Lollipop devices. Some manufacturers were granted exemptions for low-RAM devices, leading to inconsistent implementation across the ecosystem.
Final Thoughts
Lollipop was Android’s most ambitious release, and it almost collapsed under its own weight. Material Design reimagined every UI element. ART rewrote the runtime. Project Volta restructured background processing. Lollipop touched every subsystem and shipped too early.
But the ambition was correct. Material Design gave Android a visual language that designers respected. ART delivered performance that Dalvik couldn’t. The lock screen, notifications, and Quick Settings redesigns set patterns still in use. The 64-bit support, the camera2 API, the design support library — all foundational.
Lollipop defined the Android we still use. Material You on Android 12 builds on Material Design concepts from Lollipop. The notification system, the Quick Settings tiles, the Overview screen — refined, redesigned, but recognizably Lollipop’s architecture. The 5.0 launch was a mess, but 5.1 proved the vision was right.
Related Articles
- Android Version History (2008–Present)
- Android 4.4 KitKat: Complete Guide
- Android 6.0 Marshmallow: Complete Guide
- Material Design: A Complete History
- The Nexus 6: Google’s Biggest Mistake?
- ART Runtime: From Experimental to Mandatory
References
- Official Android 5.0 / 5.1 Platform Highlights (developer.android.com)
- Android Developers Blog: “Android 5.0 Lollipop SDK and Updated Support Library” (October 2014)
- Google I/O 2014 keynote, Matias Duarte Material Design presentation
- Motorola Nexus 6, HTC Nexus 9, Nexus Player product documentation
- ART runtime technical documentation (source.android.com)
- JobScheduler and Project Volta technical documentation
- Material Design specification v1.0 (material.io, archived)