CODEWITHSUNDEEP
androidandroid-source
sdabet
sdabet

Reputation: 18670

Running AOSP on emulator

In order to get familiar with AOSP, I'm aiming at building an image and running it on an emulator, following the official documentation.

After setting up an Ubuntu 16.04 VM, I use the following commands:

repo init -u https://android.googlesource.com/platform/manifest
repo sync
source build/envsetup.sh
lunch full-eng
make -j8
emulator

Compilation works fine, the emulator starts but its screen remains blank. No particular error trace in the console.

I tried it without any proprietary binaries, and also with Nexus 5 binaries, but it didn't change anything.

I also tried with lunch aosp_arm-eng but same result.

What am I missing?

I can successfully shell into the emulator. In dmesg output I noticed the following error traces:

[   23.952504] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory
[   23.954517] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory
[   23.956460] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory

And the output of service list command is:

generic:/ # service list
Found 10 services:
0   media.resource_manager: []
1   media.player: []
2   media.camera: []
3   media.sound_trigger_hw: []
4   media.radio: []
5   media.aaudio: []
6   media.audio_policy: []
7   netd: []
8   media.audio_flinger: []
9   batteryproperties: [android.os.IBatteryPropertiesRegistrar]

Upvotes: 13

Views: 8650

Answers (2)

Grant
Grant

Reputation: 99

I know this is probably dead now, but figured I'd post for others to find.

I also had a similar issue and I fixed it by running:

cd aospDir
source build/envsetup.sh
lunch sdk_phone_x86_64
m -j16       # builds using 16 cores

Then once that finished:

adb start-service
emulator

For me it was an issue with adb not starting.

Upvotes: 0

SamT01
SamT01

Reputation: 124

Build for aosp_x86_64 or arm. Should work then! Other images are no longer supported to run on emulator. They are for their respective devices. arm and x86/x86_64 should work on emulator as they are generic in nature.

EDIT: Just saw that you tried running for aosp_arm_eng, in that case would you mind posting results after you run emulator with following command?

$ emulator -verbose

Upvotes: -2

Related Questions