Fehler im Emulator beginnen nach dem ASOP -Build -Android -Emulator, das ich versuchte, das Laufen zu bringenAndroid

Forum für diejenigen, die für Android programmieren
Anonymous
 Fehler im Emulator beginnen nach dem ASOP -Build -Android -Emulator, das ich versuchte, das Laufen zu bringen

Post by Anonymous »

Nach erfolgreichem Zusammenstellen des AOSP -Builds aus dem Repo versuchte der Emulator mit dem Befehl in der Dokumentation < /p>
zu starten

Code: Select all

$launch_cvd --daemon
< /code>
, jedoch auf das folgende Fehlerprotokoll: < /p>
06-03 14:31:46.869 2117619 2117619 I launch_cvd: main.cc:179 Using system_image_dir of: ===================================================================

NOTICE:

By using this Android Virtual Device, you agree to Google Terms of Service (https://policies.google.com/terms). The Google Privacy Policy (https://policies.google.com/privacy) describes how Google handles information generated as you use Google Services.

===================================================================

Automatically send diagnostic information to Google, such as crash reports and usage data from this Android Virtual Device. You can adjust this permission at any time by running "launch_cvd -report_anonymous_usage_stats=n". (Y/n)?:n

Reading --config option from: /path/to/output_file/out/target/product/vsoc_x86_64/android-info.txt

Launching CVD using --config='phone'.

exec of /usr/lib/cuttlefish-common/bin/capability_query.py with path "/usr/lib/cuttlefish-common/bin/capability_query.py" failed (No such file or directory)

VM manager crosvm is not supported on this machine.

Invalid vm_manager: crosvm

06-03 14:31:56.823 2117619 2117619 E launch_cvd: subprocess.cpp:207 Subprocess 2122296 was interrupted by a signal 'Aborted' (6)

06-03 14:31:56.823 2117619 2117619 E launch_cvd: main.cc:263 assemble_cvd returned -1

Quick Reply

Change Text Case: 
   
  • Similar Topics
    Replies
    Views
    Last post