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

2019-03-28 Thread 'Dan Willemsen' via Android Building
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 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
> AOSP/prebuilts/android-emulator/linux-x86_64/emulator64-crash-service
>
> emulator: WARNING: system partition size adjusted to match image file
> (1018 MB > 800 MB)
>
> statvfs('AOSP/out/target/product/blueline/snapshots/default_boot/ram.img')
> failed: No such file or directory
> emulator: WARNING: encryption is off
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> 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 android-building+unsubscr...@googlegroups.com.
> 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 android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
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 android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-03-28 Thread chianglee1201
 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 
AOSP/prebuilts/android-emulator/linux-x86_64/emulator64-crash-service

emulator: WARNING: system partition size adjusted to match image file (1018 
MB > 800 MB)

statvfs('AOSP/out/target/product/blueline/snapshots/default_boot/ram.img') 
failed: No such file or directory
emulator: WARNING: encryption is off

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
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 android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-03-28 Thread zx850369769
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 java.io.FileInputStream.read(FileInputStream.java:207)
at jline.Terminal.readCharacter(Terminal.java:99)
at jline.UnixTerminal.readVirtualKey(UnixTerminal.java:122)
at jline.ConsoleReader.readVirtualKey(ConsoleReader.java:1606)
at jline.ConsoleReader.readBinding(ConsoleReader.java:764)
at jline.ConsoleReader.readLine(ConsoleReader.java:511)
at jline.ConsoleReader.readLine(ConsoleReader.java:457)
at 
com.android.tradefed.command.Console.getConsoleInput(Console.java:829)
at com.android.tradefed.command.Console.run(Console.java:940)
at 
com.android.compatibility.common.tradefed.command.CompatibilityConsole.run(CompatibilityConsole.java:81)
03-28 17:23:24 E/VtsVendorConfigFileUtil: Vendor test config file 
/config/vts-tradefed-vendor-config-prod.json does not exist

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
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 android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-03-28 Thread Saurabh Sakhare
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
8007157873


On Mon, Mar 25, 2019 at 8:52 PM andrew_esh  wrote:

> I would not expect the AOSP source code base to be fully runnable at this
> stage. Anything on there is probably going to be previews of bits and
> pieces of what will eventually become the full release. The only way to get
> Android Q running on a device at this stage is to install one of the binary
> preview blobs. I don't expect the full source for Q to drop until late
> September.
>
> https://www.techradar.com/news/android-q
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> 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 android-building+unsubscr...@googlegroups.com.
> 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 android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
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 android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.