Android/Sign: Difference between revisions
< Android
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
If you can successful build Android for XO-4, there is a script [http://dev.laptop.org/git/users/ben/android_vendor_olpc_xo4/tree/sugar-combiner/build_release.sh?h=android-4.3.1-xo4 build_release.sh] which can help to resign build using specific keys. |
If you can successful build Android for XO-4, there is a script [http://dev.laptop.org/git/users/ben/android_vendor_olpc_xo4/tree/sugar-combiner/build_release.sh?h=android-4.3.1-xo4 build_release.sh] which can help to resign build using specific keys. |
||
* Before |
* Before running the script, The BUILD_ID can be changed to a unique string which indicates which build it is. |
||
vim build/core/build_id.mk |
vim build/core/build_id.mk |
||
export BUILD_ID=MY-RELEASE-ID |
|||
cd vendor/olpc/xo4/sugar-combiner |
cd vendor/olpc/xo4/sugar-combiner |
||
Revision as of 04:39, 22 September 2014
By default, Android build script use testkeys to sign all the files which is in build/target/product/security/.
For a decent release, build has to be resigned with release keys created by private builder. OLPC official build is signed by release keys generated by OLPC. The build has to be resigned if you plan to release a customized release.
Here is the instructions to generate all the keys resign needed. generatingKeys
- Put the keys generated in vendor/olpc/security/xo4
If you can successful build Android for XO-4, there is a script build_release.sh which can help to resign build using specific keys.
- Before running the script, The BUILD_ID can be changed to a unique string which indicates which build it is.
vim build/core/build_id.mk export BUILD_ID=MY-RELEASE-ID
cd vendor/olpc/xo4/sugar-combiner . build_release.sh vendor/olpc/security/xo4
After enter all the passwords for key store, the output folder contains all the release build.