[Missing Source] [SM8845] Systemic GPLv2 Non-Compliance on Ace 6T (PLR110) - Isolated Device Branch Neglect & 7 Skipped Builds

[iMakeSoftware]

Title: [Missing Source] [SM8845] Systemic GPLv2 Non-Compliance on Ace 6T (PLR110) - Isolated Device Branch Neglect & 7 Skipped Builds

Device: OnePlus Ace 6T (PLR110)
Platform: Qualcomm SM8845

[PLATFORM]: Qualcomm SM8845
[DEVICE]: OnePlus Ace 6T (PLR110)
[SEVERITY]: GPLv2 Licensing Breach / Source Omission
[STATUS]: 7-Day Ultimatum Active

Description

Hi @OnePlusOSSAdmin,

The source repository tracking for the SM8845 platform is in an ongoing state of structural non-compliance with the GNU General Public License v2 (GPLv2). The administration is systematically failing to distribute matching source trees alongside public production OTA releases.

1. Current Active Breaches & Cross-Branch Neglect

The public repositories are currently heavily fragmented, structurally broken, and unusable for active production builds on the Ace 6T:

• android_kernel_common_oneplus_sm8845 remains abandoned on the obsolete 16.0.5.702 base. This leaves a severe architectural mismatch for the 16.0.7.200, 16.0.7.201, 16.0.8.300, 16.0.8.301, and 16.0.9.400 OTA cycles.
• android_kernel_oneplus_sm8845 is completely frozen at 16.0.7.201.
• In the android_kernel_modules_and_devicetree_oneplus_sm8845 repo, an isolated sync for 16.0.8.300 was pushed exclusively to the OnePlus 15R branch (introducing 74 files changed, 1,979 additions, and 488 deletions). However, the Ace 6T branch in that exact same repository has been completely neglected and remains frozen on 16.0.7.201.

Attempting to build a kernel for modern firmware using these mismatched repositories results in breaking version discrepancies and critical driver regressions, completely defeating the purpose of the public source code. Distributing compiled binaries to consumer hardware without publishing the corresponding core kernel, common tree, and device-specific branch updates directly violates Section 3 of the GPLv2.

2. Comprehensive Timeline of Unreleased Source Gaps

An audit of the tracking pipeline against the official public OTA distribution history reveals a systemic pattern of omitting required source code drops. Following the release of the PLR110_16.0.1.308(CN01) source tree, the following seven subsequent production builds were pushed to users as stable OTAs but skipped entirely in the public source history:

• PLR110_16.0.2.402(CN01) - NEVER RELEASED
• PLR110_16.0.2.403(CN01) - NEVER RELEASED
• PLR110_16.0.3.501(CN01) - NEVER RELEASED
• PLR110_16.0.3.503(CN01) - NEVER RELEASED
• [Source tree jumps directly from 16.0.1.308 base to 16.0.5.702]
• PLR110_16.0.8.300(CN01) - NEVER RELEASED (Ace 6T branch)
• PLR110_16.0.8.301(CN01) - NEVER RELEASED
• PLR110_16.0.9.400(CN01) - NEVER RELEASED

The upstream commit history completely skips entire multi-month maintenance lifecycles, leaving permanent gaps in the distribution ledger and preventing basic regression tracking or stable kernel engineering.

3. Prior Requests & Ignored Community Feedback

This request serves as an extension and formal escalation of the existing community issue tracker thread:

• See: Synchronize code for OnePlus PLR110_16.0.8.300(CN01) android_kernel_oneplus_sm8845#1 - Synchronize code for OnePlus PLR110_16.0.8.300(CN01)

The community formally requested the 16.0.8.300 source dropped over a month ago. OnePlus has completely ignored this open issue while continuing to distribute newer un-synced binaries (up to 16.0.9.400) to consumer devices.

---

⚠️ FORMAL LEGAL NOTICE OF PENDING SFC ESCALATION

Due to the extensive history of skipped source branches, the abandoned common tree, and active multi-version omissions, this platform is in clear violation of the GPLv2.

If complete, compileable source code matching all distributed iterations (up to the current 16.0.9.400 release cycle) is not fully synchronized across ALL core SM8845 repositories and individual device branches within 7 calendar days (by August 06, 2026), this matter will be escalated.

A formal compliance report will be submitted directly to the Software Freedom Conservancy (SFC) to initiate a formal legal open-source investigation. We strongly advise your open-source compliance team to step in and synchronize these trees immediately.