Security Patch Archives

AppWizard

October 13, 2026

LineageOS 24 nightly build for Google Pixel 10

LineageOS has released a new nightly build, LineageOS 24.0, for the Google Pixel 10 (codenamed frankel), dated October 11, 2026, with a size of 1.61 GiB and an October 2026 security patch level. The build is named lineage-24.0-20261011-nightly-frankel-signed.zip and is based on the Android 17 framework. Installation requires the latest Android 17 firmware, a computer with adb and fastboot, USB debugging enabled, and prior booting into the stock operating system. Users should check essential features like SMS and calls, and remove Google accounts to avoid Factory Reset Protection issues. Apps requiring device-integrity checks may not function correctly. Nightly builds for the Pixel 10 Pro were reported available on October 12, 2026, while builds for other models like the Pixel 10a, Pixel 10 Pro XL, and Pixel 10 Pro Fold have not yet been released.

AppWizard

October 6, 2026

How to check if your Android phone is still getting security updates

Smartphones may not receive crucial security updates, leaving them vulnerable to threats despite appearing to function well. Users can check their device's security status by navigating to Settings > About Phone to see the last security patch date. If it exceeds three to six months, the device may be nearing its support cutoff. Google Play system updates can also enhance security and should be checked via the Play Store. Manufacturers typically do not publicize end-of-life dates, but resources like endoflife.date can help users find this information. For example, the Samsung Galaxy S26 FE will receive updates until September 2033, while the Google Pixel 6 Pro will stop receiving support in October 2026. Google offers seven years of updates for Pixel 8 and newer models, while Samsung provides up to seven years for Galaxy S24 and Z Fold/Flip6 models. OnePlus offers four years of OS updates and up to six years of security patches. The European Union mandates a minimum of five years of software updates for new smartphones sold within the region starting June 2025. If a phone stops receiving updates, users should enable automatic app updates, avoid unverified apps, use two-factor authentication, back up data, and be cautious with public Wi-Fi. If the last security patch is over six months old or the device has surpassed its support cutoff, upgrading to a newer model is advisable.

AppWizard

October 5, 2026

Google’s Android Security State Libraries Enable Component-Level Security Verification

Google has launched AndroidX Security State libraries, enabling applications to verify security patch status at a granular level for individual components. This allows developers to conduct precise security verifications tailored to their applications' needs. The libraries categorize security patch levels into Device SPL, Published SPL, and Available SPL, providing enhanced visibility into device security. Functions such as queryAllAvailableUpdates() and areCvesPatched() help identify pending updates and check CVE status. The Security State Provider library standardizes communication for update notifications among OEMs.

BetaBeacon

September 20, 2026

MuMu Player vs GameLoop vs KOPLAYER: Android 15 Gap

Android emulators for PC have become a crowded market with close to a dozen actively maintained clients. Tencent and NetEase have first-party products like GameLoop and MuMu Player to control the PC on-ramp to their mobile catalogs. Independent players like BlueStacks and LDPlayer focus on platform-agnostic performance and feature breadth. KOPLAYER appears to be abandoned in 2026 with no updates, functioning website, or active development. MuMu Player supports Android 15, offering newer features for mobile games. GameLoop is focused on Tencent's mobile titles with updated documentation. MuMu Player and GameLoop are free, while KOPLAYER is also historically free. MuMu Player and GameLoop have ongoing updates and security, while KOPLAYER's lack of updates poses a security risk.

AppWizard

September 19, 2026

Why ESG reporting standards matter in the Android and mobile tech ecosystem

ESG reporting standards are becoming increasingly important in mobile technology, affecting various aspects such as data management, material sourcing, energy consumption, privacy, supply chain dynamics, and product accountability. The lifecycle of mobile devices involves raw material sourcing, component manufacturing, device assembly, shipping, marketing, sales, updates, repairs, trade-ins, and disposal. Companies must understand ESG standards to create coherent sustainability narratives and may need to disclose supplier practices, carbon emissions, and governance documentation when partnering with larger firms. Consumers are now asking more questions about the longevity of software updates, repairability, data collection, packaging design, and the accountability of product creators. The rise of connected devices complicates ESG reporting due to extended product lifecycles and the need for ongoing software support. Companies should track product lifespan estimates, warranty data, repair trends, and update schedules to improve product quality and ESG reporting credibility. Emerging tech companies can start their ESG journey by cataloging product claims, consolidating evidence, designating ownership of records, and reviewing product lifecycle information. Global sustainability frameworks exist but may not align with consumer needs for straightforward product information. Successful mobile tech companies will need to bridge formal reporting requirements with accessible product-level communication. Trust and transparency in practices will increasingly influence consumer choices in mobile technology.

AppWizard

September 18, 2026

That security patch date on your Android phone is no longer the full story

Google has launched the AndroidX Security State and Security State Provider libraries, enhancing Android's security framework. These tools allow applications to assess the security status of individual components on a device, rather than relying solely on the overall security patch level. Applications can now verify specific security fixes, identify available updates, and check for pending installations. This is particularly useful for security-sensitive applications, such as banking software, which can confirm the presence of necessary security fixes before allowing transactions. The libraries also enable apps to check for the resolution of specific vulnerabilities (CVEs), ensuring critical fixes are in place before enabling features like tap-to-pay. Phone manufacturers can communicate specific security fixes without changing the overall security patch date, meaning a device may show an outdated patch date while still having resolved certain vulnerabilities.

AppWizard

September 18, 2026

Android apps can now check security patches down to individual device components

The new AndroidX Security State libraries, with stable releases of Security State v1.1.0 and Security State Provider v1.0.0, allow developers to evaluate the security status of individual device components. They provide three levels of security patch information: Device Security Patch Level (DSPL), Published Security Patch Level (PSPL), and Available Security Patch Level (ASPL). These libraries enable checks on critical components of the Android operating system, including system modules and the Linux kernel, which are represented by version numbers rather than monthly patch dates. Applications that prioritize security can utilize this detailed patch information to assess vulnerabilities, particularly those tracked as Common Vulnerabilities and Exposures (CVEs). The libraries also integrate with the Open Source Vulnerabilities (OSV) database for access to Android Security Bulletin data and device-specific vulnerability reports. Additionally, Android 17 allows manufacturers to declare individual security fixes beyond the stated security patch level, and Google is working with manufacturers to transition their OTA update clients to this new standardized system.

AppWizard

September 18, 2026

Android 17 QPR2 Beta 5: key changes

Android 17 QPR2 Beta 5 was released on September 15, 2026, with a public rollout for Pixel devices starting the next day. This beta version enhances the Proactive Assistance feature on Pixel 10 and Pixel 11 devices, allowing users more control over personalized suggestions and addressing various bugs. It is a development build for supported Pixel devices and Android Emulator images, with identified builds CP41.260828.004.A8 and CP41.260828.005.A6, and a security patch level dated August 5, 2026. The update package size for the Pixel 10 Pro XL is approximately 667 MB. The notable change in Beta 5 is the introduction of two Proactive Assistance entries in the Settings menu, allowing users to manage proactive suggestions more effectively. The updated settings page includes a "Use app content for suggestions" option, enabling users to control which applications can share screen content and notifications. Google's release notes list several fixes, including issues with Bluetooth device icons, unexpected reboots, missing volume controls, search-field highlight rendering, unlocking Private Space, HDR behavior, Google Wallet touchscreen unresponsiveness, camera crashes, and distorted Bluetooth call audio. The stable release of Android 17 QPR2 is expected in December 2026, and users are advised that Beta 5 is a developmental tool that may contain errors. Additionally, new restrictions on programmatic USSD requests for call forwarding have been introduced to reduce potential fraud.

AppWizard

September 17, 2026

Google Pixel: Android 17 QPR2 Beta 5 Released

On September 15, 2026, Google released the beta OS update "Android 17 QPR2 Beta 5" for Google Pixel devices in the Android Beta Program. This update includes support for new Pixel devices: "Pixel 11," "Pixel 11 Pro," "Pixel 11 Pro XL," and "Pixel 11 Pro Fold," while excluding "Pixel 6" and "Pixel 6 Pro." The update is distributed via Over-the-Air (OTA) to 23 models, including "Pixel 6a," "Pixel 7," and "Pixel 8 Pro." Key features include "Call Forwarding Hardening," which restricts access to call-forwarding USSD codes to enhance security against scams. The update also includes eight bug fixes, addressing issues with Bluetooth device type display, unexpected reboots, volume slider UI, text rendering, Private Space unlocking, HDR mode, Camera app crashes, and Bluetooth audio distortion. The build number changes to "CP41.260828.004.A8" or "CP41.260828.005.A6," with the Android security patch level updated to "August 5, 2026," and "Google Play services" upgraded to version 26.28.33 or later.

AppWizard

September 15, 2026

Google rolling out Android 17 QPR1 for Pixel

Android 17 QPR1 is rolling out for Google Pixel devices, coinciding with the September 2026 Feature Drop and security patch. Key updates include enhanced blur effects in the system UI, a redesigned system media player with a Material 3 carousel interface, updated Quick Settings with new animations and features, and improved app management options. The rollout includes Pixel 6, 7, and 8 series devices. Users can check for the update in Settings > System > System update. The Android Beta Program will continue for future testing, and users on the beta must opt out to receive the stable version without wiping their devices.