Oneplus End of Life Dates

other

Developers rely on accurate and timely information to manage their projects effectively, particularly when it comes to tracking end-of-life dates for the devices they support, such as Oneplus. Created to provide a centralized resource for this purpose, the Oneplus end-of-life tracking website offers a comprehensive overview of supported versions and security patch timelines. Maintained by dedicated professionals, this website aims to empower developers with the knowledge they need to plan upgrades and ensure seamless continuity for their applications. With its inception, the website has been bridging the gap between device manufacturers and developers, facilitating a more coordinated approach to software maintenance.

The landscape of Oneplus versions currently comprises a total of 12 versions, out of which 1 has already reached its end-of-life, leaving 11 active versions. As of the latest updates, version 11 is slated to be the next to expire, with its end-of-life date set for 2028-02-07. This timeline is crucial for developers to prepare and migrate their applications to newer, supported versions. The most recent version to have reached its end-of-life was version pad1, which occurred on 2026-05-01, marking an important milestone in the lifecycle of Oneplus devices. Understanding these timelines is essential for maintaining the security and compatibility of applications developed for these devices.

From a security standpoint, the Oneplus ecosystem currently shows a clean slate, with 0 CVEs tracked and no critical vulnerabilities reported. This positive security posture indicates that Oneplus devices have not been significantly impacted by known security flaws. As a result, there is no most affected version to highlight, and the KEV status is not applicable in this context. Despite this favorable situation, developers should remain vigilant and proactive, ensuring they stay informed about any future security patches or updates that may affect the Oneplus devices their applications support. By doing so, they can take appropriate action to safeguard their users and maintain the integrity of their applications.

Last updated: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
15r Dec 22, 2025Dec 22, 2029Dec 31, 2031in 1986dActive
15 Nov 13, 2025Nov 13, 2029Nov 13, 2031in 1938dActive
pad3 Jun 5, 2025Jun 5, 2029Jun 19, 2031in 1791dActive
13t Apr 24, 2025Apr 24, 2029Apr 24, 2031in 1735dActive
13r Jan 7, 2025Jan 7, 2029Jan 7, 2031in 1628dActive
13 Oct 31, 2024Oct 31, 2028Oct 31, 2030in 1560dActive
pad2 Jul 16, 2024Jul 16, 2027Jul 16, 2028in 723dActive
12r Jan 23, 2024Jan 23, 2028Jan 23, 2029in 914dActive
12 Jan 23, 2024Jan 23, 2028Jan 23, 2029in 914dActive
pad1 May 1, 2023May 1, 2026May 1, 202684d agoEOL
11r Feb 7, 2023Feb 7, 2027Feb 7, 2028in 563dActive
11 Feb 7, 2023Feb 7, 2027Feb 7, 2028in 563dActive

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions