Re: [android-building] No ram.img file after successfully building AOSP

To run the emulator, you'll need to build for one of the aosp_arm/aosp_arm64/aosp_x86/aosp_x86_64 targets -- aosp_blueline only works with the real device. - Dan On Thu, Mar 28, 2019 at 8:35 AM wrote: > build completed successfully (05:33:52 (hh:mm:ss)) > > im running the emulator

[android-building] No ram.img file after successfully building AOSP

build completed successfully (05:33:52 (hh:mm:ss)) im running the emulator command in my AOSP folder. Not sure why the ram.img isnt built. For the Google Pixel 3 - blueline. emulator emulator: WARNING: Couldn't find crash service executable

[android-building] Running VTS present the following anomalies:Resource temporarily unavailable

03-28 17:23:23 E/VtsVendorConfigFileUtil: Vendor test config file /config/vts-tradefed-vendor-config-prod.json does not exist vts-tf > java.io.IOException: Resource temporarily unavailable at java.io.FileInputStream.read0(Native Method) at

Re: [android-building] Re: Flashing AOSP master on Pixel failed (Android Q)

I've added wrong vendor image by mistake and now it stucked in bootloader mode. Showing error slot unbootable I tried to put in recovery mode but showing same error. And even phone is not showing on $fastboot devices. I was trying to re-flash images but nothing is working. Saurabh Sakhare