Creating customized AVD

325 views
Skip to first unread message

mzwt

unread,
Nov 15, 2020, 10:35:19 PM11/15/20
to Android Automotive OS Discussion Group
I am trying to define customized AVD based on default "Automotive (1024p landscape)" in Android Studio without success.
Anyone has same issue or know on how to do it?
(Can be general issue with defining customized AVD, but I just resumed using Android Studio recently and could not decide.)

1) Install AS 4.2 Canary 16
2) Enable (install) following images on SDK manager

Q: Automotive with Play Store Intel x86 Atom System Image
Pie: Automotive Image x86 Atom System Image

3) Open AVD manager

3-1) Select "Create Virtual Device..."
3-2) Choose "Automotive" category
3-3) Select "Automotive (1024p landscape)
3-4) Push "Clone Device..."
3-5) Set desired property values, in my case changed "Device Name" and "Screen" (size and resolution).
Make sure "Device Type" is "Android Automotive".
3-6) Press "Finish"
3-7) My new definition is there.  Select it and Press "Next".

3-8) on "Select a system image" dialog, no system image is listed.
(this is my problem.)

If you select either of "Polerstar 2" or "Automotive (1024 landscape" (the definitions initially provided), I can see system images and can select the image to be used with the device definition.

So, which is the way to make automotive system image available on my custom device definition?

(Also, even if I cloned "Automotive (1024p landscape)", my cloned copy does not have Play Store icon on "Choose a device definition" dialog.
Is this expected behavior?)

mzwt

unread,
Nov 15, 2020, 11:27:52 PM11/15/20
to Android Automotive OS Discussion Group, mzwt

Android Automotive OS Discussion Group

unread,
Nov 18, 2020, 12:43:53 PM11/18/20
to Android Automotive OS Discussion Group, mzwt
Thx for flagging the bug, we are looking into it. 

Android Automotive OS Discussion Group

unread,
Nov 22, 2020, 8:47:50 AM11/22/20
to Android Automotive OS Discussion Group, Android Automotive OS Discussion Group, mzwt
Please find the workaround posted on the bug  
https://b.corp.google.com/issues/169483535#comment7
Reply all
Reply to author
Forward
0 new messages