Using aosp_x86_64-eng, still not work. 在 2017年4月30日星期日 UTC+8上午12:28:10，Chih-Wei Huang写道： > > > > Imran Khushwaqt於 2017年4月26日星期三 UTC+8上午11時15分03秒寫道： >> >> HI, >> I have synced AOSP master and build successfully. Using these commands. >> Make clobber >> >> lunch aosp_arm-eng >> >> emulator. >> >> >> Emulator starts up with message "*Running an x86 based android virtual >> device (AVD) is 10x Faseter. We strongly recommend creating a new AVD*". >> >> and On console it says* AVD is out dated. Please update using android >> studio*. An other message with emulator commands pops up is "*Could not >> detect * >> >> *an ADB binary. Some emulator functionality will not work until a custom >> path to ADB is added in the extended settings page.*" >> >> > > As it said, use the x86 emulator instead of arm. > > > lunch aosp_x86-eng > > > or if you prefer the 64-bit OS: > > lunch aosp_x86_64-eng > > > > > >> My Question is how can I create new AVD and add it to build path during >> lunch or make command or add custom path in extended settings >> >> page to avoid these error and make AVD faster. >> >> >> What I have tried is >> >> Open android studio and updated all AVD in android studio sdk directory. >> This doesn`t worked and then I changed sdk path in android studio >> >> to AOSP WORKING_DIRECTORY/sdk and updated the installed packages. But still >> its not working and emulator takes around one and half hour >> >> or two to start. >> >> What can I do to make it fast. I am using Mac OS 10.12 with 1.5 GHZ core i5 >> with 8 GB of RAM. >> >>
-- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
