Hi Dan, Thank you for your reply.
>From your reply what I infer is: better to go for clean build for OTA, as incremental build may have issues. I think I would follow that; a wrong OTA would be a costly risk for me. In parallel I will play with build.prop to see if I can rectify the issue. I am building v5.1. I am okay with the additional time taken in build; what I am not happy is the 'wrong diffs' identified by 'ota_from_target_files'. I use same machine and same set of commands for build. I do not touch anything, but one app folder. (I want this app as a priv-app; hence the build and OTA. I deploy it to few thousand devices). Regards, Aby. On Monday, March 6, 2017 at 4:41:38 AM UTC+5:30, Dan Willemsen wrote: > > We've only recently begun trusting incremental builds, though all of our > release builds (that would go to an OTA system) are still full clean builds. > > Which android version are you building? Two clean builds on Android-N > should be quite similar, especially once you follow the guidelines here for > any code that you've added: > http://source.android.com/devices/tech/ota/reduce_size.html > > If you still want to use incremental builds, I would suggest running "m > installclean" in between the builds -- that "fixes" a number of issues with > files being uninstalled in between builds. > > It looks like to force regeneration of this file, you could remove > $OUT/obj/ETC/system_build_prop_intermediates/system.prop. Or just change > the value of BUILD_ID, which should probably change between builds sent to > an OTA system anyway. > > - Dan > > On Sun, Mar 5, 2017 at 9:49 AM Aby Mathews <[email protected] <javascript:>> > wrote: > >> >> down votefavorite >> <http://stackoverflow.com/questions/42578037/aosp-ota-incremental-version-issue#> >> >> I am facing an issue with AOSP incremental OTA build. If I do an >> incremental build (without make clean), build completes fast and I get a >> smaller OTA file, and OTA updates successfully on the target system; BUT >> the incremental build number of target system remains same. >> (os.build.version.incremental returns old number) So next time when another >> OTA is generated and tried to update, it fails, giving error : "package >> expects build fingerprint of ../../../(build number)/.. ". as, incremental >> build number is part of build fingerprint. >> >> If I do 'make clean' before 'make dist', things work fine; but build time >> is much more and OTA file is bloated; many packages which are NOT modified >> are identified as modified by some %, and is added to OTA. >> >> How to increment build number without 'make clean' ? >> >> -- >> -- >> You received this message because you are subscribed to the "Android >> Building" mailing list. >> To post to this group, send email to [email protected] >> <javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
