PitchBlackRecoveryProject / android_bootable_recovery

The heart :heart: of PBRP
https://pitchblackrecovery.com
Apache License 2.0
100 stars 42 forks source link

[Feature Request] #88

Open sundaqiang opened 3 years ago

sundaqiang commented 3 years ago

PBRP has the ability to modify codename, can you add a tool to modify more read-only attributes? Many official upgrade packages now recognize more than Just Codename. This feature can be adapted to more similar models using a PBRP image.

AndroiableDroid commented 3 years ago

Hmmm, sounds good that can be implemented. Can you plz elaborate about the variables which needed more.

hraj9258 commented 3 years ago

@AndroiableDroid Like build fingerprint and few other device specific props

sundaqiang commented 3 years ago

Hmmm, sounds good that can be implemented. Can you plz elaborate about the variables which needed more.

ro.separate.soft ro.product.device ro.product.system.model

There will be a lot, I think we can do something like Mprop(https://github.com/jedy/mprop, you can use this tool in the normal system, but can't use in PBRP) such a command-line tool, so that we can in the rc file to perform a custom sh, get the original system and write PBRP attribute.

Many models of the same CPU and the same manufacturer can use the same PBRP image.If you can write the properties of the original system to PBRP after startup, you can save a lot of work.Of course, attributes can vary from vendor to vendor, so a command-line tool that lets developers read and write attributes is most appropriate.

AndroiableDroid commented 3 years ago

Hmmm, sounds good that can be implemented. Can you plz elaborate about the variables which needed more.

ro.separate.soft ro.product.device ro.product.system.model

There will be a lot, I think we can do something like Mprop(https://github.com/jedy/mprop, you can use this tool in the normal system, but can't use in PBRP) such a command-line tool, so that we can in the rc file to perform a custom sh, get the original system and write PBRP attribute.

Many models of the same CPU and the same manufacturer can use the same PBRP image.If you can write the properties of the original system to PBRP after startup, you can save a lot of work.Of course, attributes can vary from vendor to vendor, so a command-line tool that lets developers read and write attributes is most appropriate.

Does resetprop not work like that?

sundaqiang commented 3 years ago

Hmmm, sounds good that can be implemented. Can you plz elaborate about the variables which needed more.

ro.separate.soft ro.product.device ro.product.system.model There will be a lot, I think we can do something like Mprop(https://github.com/jedy/mprop, you can use this tool in the normal system, but can't use in PBRP) such a command-line tool, so that we can in the rc file to perform a custom sh, get the original system and write PBRP attribute. Many models of the same CPU and the same manufacturer can use the same PBRP image.If you can write the properties of the original system to PBRP after startup, you can save a lot of work.Of course, attributes can vary from vendor to vendor, so a command-line tool that lets developers read and write attributes is most appropriate.

Does resetprop not work like that?

Thank you very much, I found this tool, but for example, after I modify this property (resetProp ro.product.device XXX), the about page of PBRP will not be updated, how should I deal with this?

AndroiableDroid commented 3 years ago

Ya that could be figure out. Resetprop working fone for you?

sundaqiang commented 3 years ago

Useful, but does not update information about the page in real time

sundaqiang commented 3 years ago

Ya that could be figure out. Resetprop working fone for you?

Thanks, I've taken care of my thoughts!