mirror of
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf.git
synced 2024-11-16 14:09:48 +00:00
Forgot
This commit is contained in:
parent
be50f4be4c
commit
46d1fe4f9f
@ -298,7 +298,7 @@ As long as Google doesn't roll out hardware based key attestation universally, i
|
||||
|
||||
The prefered method is to pick a device manually from the list of devices (based on the module fingerprints list) or set your own custom value. Do NOT pick your own device, instead try a device that is as close to your actual device as possible. The closer it is to your actual device the less is the likelyhood that things will stop working as a result of the model prop change.
|
||||
|
||||
It is also possible to pick a custom value, if that's what you prefer.
|
||||
It is also possible to use a custom value, if that's what you prefer.
|
||||
|
||||
If a device isn't picked from the list or a custom value entered, this feature will by default use an old devices model prop value, based on your device or currently set fingerprint, to make sure that it is recognised as a device without the necessary hardware (picked from the available devices in the module fingerprints list). Using an actual model value from an old device may also help with keeping OEM specific features working (like the Samsung Galaxy Store). If device/OEM specific features still doesn't work after activating this option, or your device is otherwise behaving strangely, try picking a device manually from the included list (see below). If no model prop value from an old enough device is available, the value from `ro.product.device` will be used instead.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user