Google has ended support for Android 6.0 Marshmallow. The move came quietly in recent weeks. Devices stuck on the 2015 release can no longer receive Play Services updates. That leaves them exposed.
Android Authority first reported the change. The publication noted Google updated its Play Services requirements page to demand Android 7.0 or higher. Snapshots from June 2026 captured the prior minimum of Android 6.0. The shift caps nearly 11 years of official backing. No other Android version lasted longer.
But don’t expect your old phone to stop working tomorrow. Calls and texts continue. Basic functions hold up for now. Yet the absence of Play Services patches carries real risks. Security flaws go unaddressed. Apps begin to break. Users face a slow erosion of capability.
The Security and Compatibility Fallout
Without fresh Play Services code, devices miss critical fixes. Google bundles API updates, bug patches, and compatibility layers into those deliveries. Miss them and newer apps refuse to install. Some existing ones lose features. One game developer moved fast. Art of War 3: Global Conflict posted on Facebook: “Android devices version 6.0 and below are no longer supported.” The warning reached players before many noticed the broader change.
Android Authority highlighted specific app behavior. Gmail still lists Android 6.0 as supported. YouTube does not. The app now demands Android 10 or above. Owners can fall back to the browser version. That workaround buys time. It doesn’t solve the underlying problem. A Reddit thread in r/Android captured user frustration. Many discovered the cutoff when apps failed to update.
Fragmentation numbers tell part of the story. Google’s own data from December 2025, analyzed by Android Headlines, showed Android 6.0 Marshmallow holding 0.4% market share. The same figure appeared in a Composables distribution chart updated December 1, 2025. Android 5.1 Lollipop sat at 0.3%. Older builds refuse to vanish completely. Millions of handsets still ping the Play Store. Each one now sits outside the protection perimeter.
Compare that to modern releases. Android 15 led with 19.3%. Android 16 followed at 7.5%. Newer platforms receive years of guaranteed patches. Google extended support windows for flagships. The contrast grows sharper every cycle. Manufacturers once shipped devices on Marshmallow. Those handsets reached end of life years ago. Yet some lingered in emerging markets or as secondary phones.
So the decision reflects math as much as mercy. Maintaining backports for a decade-old codebase costs engineering hours. Vulnerabilities discovered today demand custom fixes. Google drew the line. The company followed a similar path with Android 5.0 Lollipop in 2024. Play Services support dropped then. Marshmallow simply waited its turn.
Developers feel the pressure too. They must raise their apps’ minimum SDK. Targeting Android 7.0 unlocks modern libraries. It also cuts off a sliver of the audience. That sliver still generates support tickets. Better to force an upgrade. The ecosystem moves forward. Legacy code drags it back.
Security experts have warned about this exact scenario for years. Unpatched Android devices become vectors for malware. Banking apps, health records, location data — all ride on the same vulnerable foundation. One successful exploit can expose everything. And with Play Services sidelined, many defenses simply stop updating.
Yet some owners can’t upgrade. Budget constraints lock them in place. Carrier support ended long ago. Hardware limitations prevent newer Android installs. For them the news lands hard. A functional phone suddenly feels obsolete. Browser alternatives help with video and mail. They don’t restore full app access. Progressive web apps offer limited relief. The experience degrades.
Google didn’t issue a press release. The change surfaced through support pages and app errors. That quiet approach matches past deprecations. It avoids panic. It also leaves many users unaware until something stops working. One day an update prompt appears. The next day it doesn’t. The device drifts into unsupported territory.
Industry watchers point to longer support cycles as progress. Pixels now get seven years. Samsung matches that on its flagships. The gap between new and old narrows. Still, the tail of the distribution curve persists. Android 11 and 13 each held over 13% in recent tallies. Those versions lost security patches earlier. Their users already navigate similar risks.
Marshmallow introduced features that defined later releases. Doze battery optimization. App permissions overhaul. Fingerprint API improvements. At launch it felt fresh. A decade later it represents technical debt. Google balanced the books. The bill came due in mid-2026.
Enterprises running legacy systems face extra work. Inventory audits become urgent. Migration plans accelerate. Consumer users get simpler advice: buy a new device or accept reduced functionality. Either choice carries cost.
The episode underscores Android’s success and its curse. Billions of activations created unmatched reach. That same scale makes uniform updates difficult. Manufacturers, carriers, and users share responsibility for the long tail. Google can only pull so many levers.
Future deprecations will follow. Android 7.0 Nougat already shows its age. Its share matches Marshmallow at 0.4%. The pattern repeats. Each generation buys time. Then support ends. The cycle continues.
Owners of affected devices should check app compatibility immediately. Update what you can. Use web versions where possible. And consider hardware refresh if security matters. The internet doesn’t wait for outdated software. Threats evolve daily. Protection must keep pace.
Google’s action closes one chapter. It opens discussion on how long any platform should support ancient code. Eleven years set a record. It may stand for some time. The next old version won’t wait quite as long.
WebProNews is an iEntry Publication