Re: [android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.

2018-12-26 Thread 'Dan Willemsen' via Android Building
You can actually hold the timestamp stable in system/build.prop too, by setting the BUILD_DATETIME environment variable to a stable value (it's the number of seconds since the unix epoch, normally generated with `date +%s`). Since we've focused on keeping the individual files identical while

Re: [android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.

2018-12-23 Thread Vitaliy Freidovich
Hello, I would kindly disagree, as your environment might change from build to build, and the resulting images could theoretically, and perhapps practically, behave differently. Thus it's a correct bahaviour in my opinion that the checksum changes. Good luck, On Fri 21 Dec 2018, 5:58 p.m. ,

Re: [android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.

2018-12-21 Thread Colin Cross
We work pretty hard to make sure that the contents of the system image don't change unless the source tree is changed, and AOSP master should be in pretty good shape, although bugs do creep in sometimes. The build time and build number are stored in system/build.prop and change on every build

[android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.

2018-12-21 Thread ltephonetwo
Hi Android Experts, We need some help / information that, Is there any way to keep android images (system.img, boot.img etc ) checksum [md5sum/crc32] same even after fresh build or recompilation??. Even though without changing a single bit in the AOSP Source code if we