Android/Sign: Difference between revisions

From OLPC
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 should be signed with release keys
For a decent release, build has to be signed with release keys created by specific device.


Instructions to generate all the keys resign needed. [http://www.kandroid.org/online-pdk/guide/release_keys.html#generatingKeys generatingKeys]
Instructions to generate all the keys resign needed. [http://www.kandroid.org/online-pdk/guide/release_keys.html#generatingKeys generatingKeys]

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.

* Put the keys generated by you in vendor/olpc/security/xo4

cd vendor/olpc/xo4/sugar-combiner
. build_release.sh vendor/olpc/security/xo4

Revision as of 04:21, 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 signed with release keys created by specific device.

Instructions to generate all the keys resign needed. generatingKeys

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.

  • Put the keys generated by you in vendor/olpc/security/xo4
 cd vendor/olpc/xo4/sugar-combiner 
 . build_release.sh vendor/olpc/security/xo4