android-prepare-vendor | automate AOSP compatible vendor blobs generation
kandi X-RAY | android-prepare-vendor Summary
kandi X-RAY | android-prepare-vendor Summary
android-prepare-vendor is a Shell library.,roid-prepare-vendor has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
For the latest Android devices (Nexus and Pixel), Google is no longer providing vendor binary archives to be included into AOSP build tree. Officially it is claimed that all vendor proprietary blobs have been moved to /vendor partition, which allegedly doesn't need building from users. Unfortunately, that is not the case since quite a few proprietary executables, DSOs and APKs/JARs located under /system are required in order to have a fully functional set of images, although are missing from AOSP public tree. Additionally, if vendor.img is not generated when system.img is prepared for build, a few bits are broken that also require manual fixing (various symbolic links between two partitions, bytecode product packages, vendor shared library dependencies, etc.). Everyone's hope is that Google will revise this policy for its devices. However until then, missing blobs need to be manually extracted from factory images, processed and included into AOSP tree. These processing steps are evolving into a total nightmare considering that all recent factory images have their bytecode (APKs, JARs) pre-optimized to reduce boot time and their original classes.dex stripped to reduce disk size. As such, these missing prebuilt components need to be repaired/de-optimized prior to be included, since AOSP build is not capable to import pre-optimized bytecode modules as part of the makefile tree. Scripts & tools included in this repository aim to automate the extraction, processing and generation of vendor specific data using factory images as input. Data from vendor partition is mirrored to blob includes via a compatible makefile structure, so that vendor.img can be generated from AOSP builds while specially annotating the vendor APKs to maintain pre-signed certificates and not pre-optimize. If you have modified the build process (such as CyanogenMod) you might need to apply additional changes in device configurations / makefiles. The main concept of this tool-set is to apply all required changes in vendor makefiles leaving the AOSP source code tree & build chain untouched. Hacks in AOSP tree, such as those applied by CyanogenMod, are painful to maintain and very fragile. Repository data is LICENSE free, use it as you want at your own risk. Feedback & patches are more than welcome though.
For the latest Android devices (Nexus and Pixel), Google is no longer providing vendor binary archives to be included into AOSP build tree. Officially it is claimed that all vendor proprietary blobs have been moved to /vendor partition, which allegedly doesn't need building from users. Unfortunately, that is not the case since quite a few proprietary executables, DSOs and APKs/JARs located under /system are required in order to have a fully functional set of images, although are missing from AOSP public tree. Additionally, if vendor.img is not generated when system.img is prepared for build, a few bits are broken that also require manual fixing (various symbolic links between two partitions, bytecode product packages, vendor shared library dependencies, etc.). Everyone's hope is that Google will revise this policy for its devices. However until then, missing blobs need to be manually extracted from factory images, processed and included into AOSP tree. These processing steps are evolving into a total nightmare considering that all recent factory images have their bytecode (APKs, JARs) pre-optimized to reduce boot time and their original classes.dex stripped to reduce disk size. As such, these missing prebuilt components need to be repaired/de-optimized prior to be included, since AOSP build is not capable to import pre-optimized bytecode modules as part of the makefile tree. Scripts & tools included in this repository aim to automate the extraction, processing and generation of vendor specific data using factory images as input. Data from vendor partition is mirrored to blob includes via a compatible makefile structure, so that vendor.img can be generated from AOSP builds while specially annotating the vendor APKs to maintain pre-signed certificates and not pre-optimize. If you have modified the build process (such as CyanogenMod) you might need to apply additional changes in device configurations / makefiles. The main concept of this tool-set is to apply all required changes in vendor makefiles leaving the AOSP source code tree & build chain untouched. Hacks in AOSP tree, such as those applied by CyanogenMod, are painful to maintain and very fragile. Repository data is LICENSE free, use it as you want at your own risk. Feedback & patches are more than welcome though.
Support
Quality
Security
License
Reuse
Support
android-prepare-vendor has a low active ecosystem.
It has 317 star(s) with 139 fork(s). There are 35 watchers for this library.
It had no major release in the last 6 months.
There are 11 open issues and 125 have been closed. On average issues are closed in 30 days. There are 2 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of android-prepare-vendor is current.
Quality
android-prepare-vendor has 0 bugs and 0 code smells.
Security
android-prepare-vendor has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
android-prepare-vendor code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
android-prepare-vendor does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
android-prepare-vendor releases are not available. You will need to build from source code and install.
Installation instructions are not available. Examples and code snippets are available.
It has 1997 lines of code, 0 functions and 16 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of android-prepare-vendor
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of android-prepare-vendor
android-prepare-vendor Key Features
No Key Features are available at this moment for android-prepare-vendor.
android-prepare-vendor Examples and Code Snippets
No Code Snippets are available at this moment for android-prepare-vendor.
Community Discussions
No Community Discussions are available at this moment for android-prepare-vendor.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install android-prepare-vendor
You can download it from GitHub.
Support
N9 flounder WiFi (volantis). N9 flounder LTE (volantisg). Pixel 2 XL taimen. Pixel 3 XL crosshatch. Pixel 3a XL bonito. Please check existing issues before reporting new ones.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page