eric/gitlab-instance-0a899031_redroid-android13
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

s''

Browse Source
This commit is contained in:
eric
2026-04-03 23:22:27 -05:00
parent a7f39a399f
commit a57303c579
14 changed files with 1555 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

136
README.md
View File

@@ -1,92 +1,102 @@
# redroid-android13
这个仓库只保留了 `5570` 那套优化过的 Android 13 redroid 最小集，不再带 `gapps/litegapps/ndk/widevine` 这些无关入口。
目标很明确：
## Getting started
- 基于 `redroid/redroid:13.0.0`
- 集成 `MindTheGapps`
- 集成 `libhoudini`
- 集成 `Kitsune Mask / Magisk Delta`
- 启动后伪装成 `Pixel 7 Pro`
- 修复 `Magisk Installed N/A` 和设置页不可用的问题
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
## 保留的文件
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
- `redroid.py`
- `run_redroid.py`
- `bootstrap_redroid.py`
- `stuff/mindthegapps.py`
- `stuff/houdini.py`
- `stuff/houdini_hack.py`
- `stuff/magisk.py`
- `assets/redroid_extreme_post_fs_data.sh`
## Add your files
## 依赖
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin http://gitlab.yidooplanet.com/gitlab-instance-0a899031/redroid-android13.git
git branch -M main
git push -uf origin main
```bash
python -m pip install -r requirements.txt
```
## Integrate with your tools
容器侧默认按 `docker` 写，`podman` 也能用。
- [ ] [Set up project integrations](http://gitlab.yidooplanet.com/gitlab-instance-0a899031/redroid-android13/-/settings/integrations)
## 构建 5570 对应镜像
## Collaborate with your team
```bash
python redroid.py -mtg -i -m
```
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
这会生成并构建：
## Test and Deploy
```bash
redroid/redroid:13.0.0_mindthegapps_houdini_magisk
```
Use the built-in continuous integration in GitLab.
## 启动容器
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
```bash
python run_redroid.py \
--image redroid/redroid:13.0.0_mindthegapps_houdini_magisk \
--bridge libhoudini \
--device-profile pixel-7-pro \
--data-dir ~/data-redroid13 \
--port 5570 \
--replace
```
***
## 启动后做 5570 硬化
# Editing this README
```bash
python bootstrap_redroid.py \
--serial 127.0.0.1:5570 \
--device-profile pixel-7-pro \
--proxy-host auto \
--install-extreme-script
```
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
这一步会做 5 件事：
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
- 跳过 SetupWizard
- 标记系统已完成初始化
- 开启高精度定位模式
- 允许 `com.android.shell` 使用 mock location
- 应用 `Pixel 7 Pro / user / release-keys / locked / green` 画像
## Name
Choose a self-explaining name for your project.
如果带上 `--install-extreme-script`，还会把 [`assets/redroid_extreme_post_fs_data.sh`](C:\Users\admin\Desktop\redroid-android13\assets\redroid_extreme_post_fs_data.sh) 安装到 `/data/adb/post-fs-data.d/20-redroid-extreme.sh`，让下面两件事在重启后继续成立：
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
- `vendor/bin/su` 指向 Magisk applet，应用命名空间可见
- `Pixel 7 Pro` 属性在每次开机时重新注入
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## 已验证结果
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
这套仓库对应的 `5570` 实例已经验证过：
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
- `ro.product.model=Pixel 7 Pro`
- `ro.build.type=user`
- `ro.build.tags=release-keys`
- `ro.boot.vbmeta.device_state=locked`
- `ro.boot.verifiedbootstate=green`
- 应用 UID 下 `su -V` 返回 `27001`
- 应用 UID 下 `su -mm -c id` 能拿到 `uid=0(root)`
- `Kitsune` 首页的 `Installed` 正常显示
- `Kitsune` 设置页正常打开，`SuList / MagiskHide` 可配置
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## 当前范围
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
这个仓库只负责把 `5570` 的系统环境复现出来，不包含：
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
- 虚拟摄像头
- camera HAL
- TikTok Live 专用补丁
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
后续如果要继续推进直播链路，直接在这个仓库往上叠加即可。