Re: [android-building] Failing to build sdk and sdk_addon in master P

2018-12-27 Thread 'Dan Willemsen' via Android Building
Just like anything else you want installed, put it in PRODUCT_PACKAGES, either in the core build system's core product makefiles, or in your product's makefiles. I'm not sure why those builds are failing without more information -- at least the normal SDK build is passing on our CI systems:

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

2018-12-27 Thread ltephonetwo
Hi All, As per the Group suggestions I have fixed the BUILD_NUMBER, DATE, TIME etc. Despite doing all those things it is differing. my Expt is like this 1. make clean and build get system.img -> rename to system-1.img 2. make clean and build get system.img -> rename to

[android-building] Issues in running ARM emulator after building the AOSP source code

2018-12-27 Thread Priyanka Bose
Hi, I am am trying to run the emulator for aosp_source code : arm64 target. I have downloaded the source code from the android AOSP master , and built the android image . Everytime i try to start the emulator it hangs with android logo screen. It never boots to the home screen. I followed the

Re: [android-building] Failing to build sdk and sdk_addon in master P

2018-12-27 Thread konstantin . karasik
Thank you, using 'm mkstubs' worked. Though normal building with sdk_addon or just sdk still doesn't. And if i want to build it automatically as part of the build similar to the doclava or other such jars. Where do i need to put it to work? On Thursday, December 27, 2018 at 12:34:54 AM UTC+2,