Hey folks
The instructions are confusing me here. It seems the modern way to store drivers is to flash them from vendor.img, which is part of the official factory images, to /vendor on the phone. Seems straightforward enough.
But, the AOSP build instructions state "run the included self-extracting script from the root of the source tree, then confirm that you agree to the terms of the enclosed license agreement. The binaries and their matching makefiles will be installed in the vendor/ hierarchy of the source tree."
Those self-extracting scripts spew out a variety of files *including* vendor.img which is very very similar to the vendor.img that is shipped by Google.
Do I need to do this extraction step? Do the other files that get spewed out matter for the AOSP build? The checksums of the .img files are NOT the same when the self-extracted /vendor folder is not at the root.
Very confused...
The instructions are confusing me here. It seems the modern way to store drivers is to flash them from vendor.img, which is part of the official factory images, to /vendor on the phone. Seems straightforward enough.
But, the AOSP build instructions state "run the included self-extracting script from the root of the source tree, then confirm that you agree to the terms of the enclosed license agreement. The binaries and their matching makefiles will be installed in the vendor/ hierarchy of the source tree."
Those self-extracting scripts spew out a variety of files *including* vendor.img which is very very similar to the vendor.img that is shipped by Google.
Do I need to do this extraction step? Do the other files that get spewed out matter for the AOSP build? The checksums of the .img files are NOT the same when the self-extracted /vendor folder is not at the root.
Very confused...
from xda-developers http://ift.tt/2cYjVy0
via IFTTT
Aucun commentaire:
Enregistrer un commentaire