Android/Sign: Difference between revisions
< Android
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
By default, Android build script use testkeys to sign all the files which is in [http://dev.laptop.org/git/users/ben/android_build/tree/target/product/security build/target/product/security/]. |
By default, Android build script use testkeys to sign all the files which is in [http://dev.laptop.org/git/users/ben/android_build/tree/target/product/security build/target/product/security/]. |
||
For a decent release, build has to be |
For a decent release, build has to be resigned with release keys created by private builder. |
||
Here is the instructions to generate all the keys resign needed. [http://www.kandroid.org/online-pdk/guide/release_keys.html#generatingKeys generatingKeys] |
Here is the instructions to generate all the keys resign needed. [http://www.kandroid.org/online-pdk/guide/release_keys.html#generatingKeys generatingKeys] |
Revision as of 04:29, 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.
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.
cd vendor/olpc/xo4/sugar-combiner . build_release.sh vendor/olpc/security/xo4