Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/oxygen-updater/build-props
Collection of `build.prop` files or `getprop` outputs of OnePlus devices
https://github.com/oxygen-updater/build-props
android oneplus oxygenos properties
Last synced: about 1 month ago
JSON representation
Collection of `build.prop` files or `getprop` outputs of OnePlus devices
- Host: GitHub
- URL: https://github.com/oxygen-updater/build-props
- Owner: oxygen-updater
- Created: 2020-03-12T22:04:52.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2023-09-20T09:43:50.000Z (about 1 year ago)
- Last Synced: 2024-07-31T08:17:22.356Z (4 months ago)
- Topics: android, oneplus, oxygenos, properties
- Homepage: https://oxygenupdater.com
- Size: 682 KB
- Stars: 30
- Watchers: 5
- Forks: 7
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
Awesome Lists containing this project
- awesome - oxygen-updater/build-props - Collection of `build.prop` files or `getprop` outputs of OnePlus devices (miscellaneous)
README
# build-props
This repo is meant for keeping a track of `build.prop`, `oem_build.prop` files and `getprop` outputs of different OnePlus devices.
Some of these files were originally part of the [Android app repo](https://github.com/oxygen-updater/oxygen-updater) (and probably still are). We've separated them into their own repository, as it's easier to add/remove files if they're decoupled from the app's code.
## File naming schemes
File names are usually taken from the `ro.rom.version` field, stripping out "HydrogenOS", "OxygenOS", or variants of the OS name. For devices running on the ColorOS-based OxygenOS (eg Nord 2, 10 Pro), `ro.build.display.id` is used.
The extension can either be `.prop` (for a `build.prop` or `oem_build.prop` file), or `.getprop` (for a `getprop` output), depending on what the file is.
## Directory structure
```java
├── ...
├──device-name
│ ├──regional-variant
│ ├──VERSION.BUILD_TAG.prop
| ├──VERSION.BUILD_TAG.oem_build.prop
│ ├──VERSION.BUILD_TAG.getprop
│ ├── ...
│ ├── ...
└── ...
```
**device-name**s are shortened forms: e.g. `op1`, `op6t`, `op7pro`
**regional-variant**s are either:
* `eea`: EU
* `india`: India
* `intl`: International/Global
* Carrier variants (e.g. `t-mobile`, `sprint-5g`)
Generally, start with the carrier name, followed by any other differentiator (e.g. wireless technology (`5g`))
## FAQ
### How do we obtain these files?
`build.prop`s and `oem_build.prop`s are usually extracted directly from the ZIP, or copied manually from a rooted device.
They are located in `/system` partition for devices running versions of OxygenOS that are not based on ColorOS codebase. `oem_build.prop` files are specific to OxygenOS 11.
For devices running on the ColorOS-based OxygenOS (meaning OxygenOS 11.3 and newer), the `build.prop` file is retrieved from `my_manifest` partition.
A `getprop` output can be obtained either by:
* Installing ADB, connecting the device, and running the `adb shell getprop > filename.getprop`
* Installing a terminal app from the Play Store, and running the `getprop > filename.getprop` command within that app
Note: depending on the app, you might have to manually copy-paste the entire output into a file, as some apps don't support writing files to internal storage. Besides, make sure you **remove the serial numbers, as it's PII**. Ctrl F for the following and remove the value of the output:
* `serial`
* `iccid`
* `uid`
* `uuid`
* `imei`
Either way, make sure you rename the file to match the appropriate [naming scheme](#file-naming-schemes).
### I'm not an Oxygen Updater project team member. Can I add files too?
Absolutely! Just fork this project, make changes, and open a PR.