[android-building] Re: Android Wear 9.0 released

2019-03-22 Thread 'Xin Li' via Android Building
Hi, all, Today, we pushed kernel projects for the following devices: Tag | Project| Branch | Device android-wear-9.0.0_r0.12 | kernel/msm | android-msm-stargazer-3.18-pie-wear-dr | stargazer/weeve PWDI.181207.009 -- -- You received

[android-building] Re: Android Wear 9.0 released

2019-03-22 Thread 'Xin Li' via Android Building
Hi, all, Today, we pushed kernel projects for the following devices: Tag | Project| Branch | Device android-wear-9.0.0_r0.10 | kernel/msm | android-msm-catshark-3.18-pie-wear-dr | PWDD.190121.005.A1 catshark android-wear-9.0.0_r0.11 |

Re: [android-building] ckati takes very long during regenerating of something...

2019-03-22 Thread 'Dan Willemsen' via Android Building
Which branch are you working on? verbose.log.gz is new in master(Q), before then, the ckati info should be in soong.log. I believe the persist-after-ctrl-c behavior should also be gone in master, but I haven't done any extensive testing to make sure. - Dan On Fri, Mar 22, 2019, 6:49 AM wrote:

Re: [android-building] ckati takes very long during regenerating of something...

2019-03-22 Thread yfliu
I got the same problem and there's no verbose.log.gz in my out dir, I don't know why, but I can offer some clue, this happens when I change some overlay xmls and modify the overlay order in device.mk. I got a intel i7 CPU, 16GB memory and 1TB ssd. The top shows I never seen AOSP generate ninja

Re: [android-building] Re: AOSP libselinux build error for android-q-preview-1

2019-03-22 Thread abhishekkumardwiv...@gmail.com
Just adding double_loadable:true in libselinux bp solves this issue, as in the error report suggestion. And there was no issue in bootup upon this build image. On Wed, Mar 20, 2019 at 9:19 PM wrote: > > Hi, > I have the same issue when I try to build for taimen (Pixel-2XL) device. > Any new

[android-building] how to merge resources using DEVICE_PACKAGE_OVERLAYS

2019-03-22 Thread yfliu
My structure of the device folder is like this: device/google/clockwork/overlay/packages/apps/CarrierConfig/res/xml/vendor.xml device/htc/soulshark/overlay/packages/apps/CarrierConfig/res/xml/vendor.xml and the two xml look like this: