MiCode / MiCode/Xiaomi_Kernel_OpenSource

Request for the Release of Kernel Source Code for Redmi Note 13 4G ("sapphire/sapphiren")

Open
#40,392 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
9.9k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

Hello Xiaomi Developers and Community Managers,

We are writing to formally request the release of the complete and corresponding kernel source code for the Redmi Note 13 4G, codename “sapphire”.

As required by the GNU General Public License version 2 (GPLv2) —under which the Linux kernel is licensed— any manufacturer distributing a product containing the kernel must make the complete corresponding source code publicly available.

The timely release of kernel sources is essential for compliance with open-source licensing and for maintaining transparency within the developer community. It also enables developers to create custom ROMs, kernels, and recoveries, improving device performance, security, and user experience. This helps extend the longevity of Xiaomi devices and strengthens the trust and collaboration between the company and the global open-source community.

We kindly ask that the kernel source code for this device be published to the official MiCode GitHub repository (github.com/MiCode) as soon as possible.

Thank you very much for your attention and continued support of the open-source ecosystem.

Sincerely,
The Redmi Note 13 4G (“sapphire/sapphiren”) user and developer community

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue requests kernel source publication for the Redmi Note 13 4G (sapphire/sapphiren) in the MiCode repository, but names no files, tests, or code entry points. Start by reviewing the request and repository context; done would mean the complete corresponding source is publicly available there.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.