-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google (Velvet package) broken signature in final image #275
Comments
OpenGapps marks the package as having LOCAL_CERTIFICATE := PRESIGNED, so it shouldn't get signed again. You can check if you do
You'll then get a file
|
Same here. I don't know if zipaligning is the issue |
I checked the logs and signature in packaging looks good. |
I run into the same problem. Velvet is in priv-apps but doesn't get installed on first first time boot or after factory reset. wkr ADT |
I was doing some research and tried a little bit of tinkering in the Does anybody know what else is done in these intermediates folders? Something that might be failing because of the size of the apk? |
@ADeadTrousers You might want to look at the build rules for it in
|
The second command block does the deed (I shortend the paths for readability) (if (zipinfo package.apk '*.dex' 2>/dev/null | grep -v ' stor ' >/dev/null) ; then
zip2zip -i package.apk -o package.apk.tmp -0 "classes*.dex"
mv -f package.apk.tmp package.apk
; fi ) After that the file got a significant raise in size and the zipalign in the next block got triggered because of the misalignment of the new apk but does no (additional) harm I guess. The option |
@ADeadTrousers I think you want to set |
@MarijnS95 Anyway, in my opinion the "problem" of the broken signature is associated with the aforementioned repackaging. |
Searching the |
For those interested in a (temporary?) fix I created a little patch that you could use: You would need this AND set |
Needed to fix Google's Velvet broken signature. Reference: opengapps/aosp_build#275 Signed-off-by: David Trpchevski <[email protected]>
I included the opengapps as vendor tree in lineageos 17.1 with a oneplus 7 pro. Until sep 24 2020 all was fine - after that date the velvet package was not liner installed after flash but it was present in priv-apps.
i chacked the package and the apk signature was broken. I replaced the apk with the original from git lfs storage and all is working fine again. It seems during building the source tree for the image something wen't wrong.
The original apk is ~ 200MB while the included apk in to target is ~ 240MB - both apk's are same version so it sems it is resigned or repacked during build run. Orighinal apk is 301109107.apk from arm64 SDK29.
Now the big question: is something failing in the opengapps tree or is something failing in the lineage build process.
All other google parts are working fine - only velvet is affected in my case so it looks to me on opengapps side is something going wrong.
The text was updated successfully, but these errors were encountered: