Virtual Device fails to register device-info, blocking app install on SDK v0.24.9859

Vega Open Beta Q&A
1

App Name: KidVerse (Educational App)
App Link on Amazon Appstore: [App not yet published]
SDK Version: v0.24.9859
React Native Version: RN 0.72 (aligned with Vega SDK)

Issue Summary (one sentence):
Virtual Device boots but fails to register device-info, causing run-app to fail with device-type-id errors.

Details:

  • Device registration failure: vega device list shows “No devices found” even though Virtual Device is running.

  • Device-info missing: vega device info -d VirtualDevice returns empty values (os: unknown, product: "", etc.).

  • Run-app failure: vega run-app fails with error: Could not get value for ‘com.amazon.devconf/system/device-info/device-type-id’. Sometimes “Unspecified run-time error”, sometimes “No permission for operation.”

  • Logs incomplete: No device.log file is generated in ~/vega/sdk/vega-sdk/main/0.24.9859/logs/.

  • VVD reinstall issue: vega sdk install vvd fails with “Version not found: main@vvd”.

Steps already tried:

  • Upgraded to latest SDK (0.24.9859).

  • Stopped/started emulator with --no-gl-accel --gui.

  • Deleted instance folders and restarted.

  • Ran vega platform doctor (environment OK, but no device info).

Request:
Please advise how to properly reinstall or repair Virtual Device system images so that device-type-id resolves and apps can be installed successfully.

4

Hi @Nomankhan,

Welcome to the Amazon Developer Community!

Your symptoms - vega device list showing no devices, empty device info, and device-type-id errors - indicate the VDA connection between your CLI and the Virtual Device isn’t being established.

Regarding vega sdk install vvd: This command doesn’t exist. VVD is bundled with the SDK automatically and can’t be installed separately (Manage Your SDK Versions ( Manage Your SDK Versions | Vega CLI Tools )).

To resolve, try these steps in order:

  1. Clean restart VVD - Stop and restart with an extended timeout. See the “Using Vega CLI” section under Run Your App on VVD ( Run Your App on Vega Virtual Device or Fire TV | Design and Develop Vega Apps ). Use --timeout 120 to allow extra boot time.
  2. If device still not found, reinstall your SDK to get a fresh VVD image. Follow the “Update Existing Installation” tab on Install Vega Developer Tools ( Install the Vega Developer Tools | Vega Get Started ).
  3. If that still fails, do a complete fresh install by following the “First-Time Installation” tab on the same page (remove ~/vega/sdk first).

The missing device.log is expected when VDA hasn’t connected - logs will appear once the device registers properly.

If the issue persists, please share:

  • Your OS (macOS/Ubuntu + architecture)
  • Full output from vega virtual-device start --timeout 120

References:

Warm regards,
Aishwarya

5

Hello Aishwarya,

It’s very nice of you to guide me and explain the installation process of VVD.

Firstly, I’ll follow the process step by step from a clean restart with --timeout 120 and will move on to SDK reinstallation in case of need. Also, I’ll provide you with the output of vega virtual-device start --timeout 120 along with my Ubuntu/architecture.

Thanks!

6

Hi Aishwarya,

Thanks for your earlier guidance. I followed the suggested steps:

  • Clean restart with --timeout 120 → Virtual Device shows “Virtual device ready.”

  • Tried vega device list and vega device info -d VirtualDevice → still returns “No devices found” and empty values (os: unknown, product: "", etc.).

  • Updated SDK to v0.24.9914 via installer script → installation completed successfully, VVD extracted and installed.

  • Verified with vega platform doctor → environment looks OK, but device registration still fails.

  • Deleted instance folders and restarted → same issue persists.

  • No device.log generated in ~/vega/sdk/vega-sdk/main/0.24.9914/logs/.

Current behavior:
Even after reinstall/update, Virtual Device boots but CLI cannot establish VDA connection. run-app fails with:

Code

Could not get value for 'com.amazon.devconf/system/device-info/device-type-id'

Environment:

  • OS: Ubuntu 24.04 LTS (x86_64)

  • SDK Versions: v0.24.9859 (active), v0.24.9914 (installed)

  • React Native: RN 0.72

Could you please advise how to repair or force reinitialize the Virtual Device system images so that device-type-id resolves and apps can be installed?

In my Ubuntu 24.04 setup, the Virtual Device GUI shows only the remote control interface, no ‘Register this device’ option. Please confirm if registration is supported on Linux builds or only on macOS/Fire TV.

7

Hi @Nomankhan,

We tested SDK v0.24.9859 on Ubuntu 24.04 LTS (x86_64) and VVD works correctly on our end. The Virtual Device boots, VDA connects, and vega device list resolves the device. This confirms the issue is specific to your local environment, not a bug in the SDK or an Ubuntu 24.04 incompatibility.

To help us diagnose the problem, first start the Virtual Device:

vega virtual-device start

Once it shows “Virtual device ready”, run the following commands and share the output:

1. Verify VDA can communicate with the emulator. This tells us if the bridge between your CLI and the Virtual Device is active:

vega exec vda devices

2. Confirm your VDA version matches the SDK. A version mismatch can cause connection failures:

vega exec vda version

3. Verify hardware virtualization is enabled. VVD requires KVM to run the emulator. If KVM is not available, the emulator may start in a degraded mode that prevents VDA from connecting:

kvm-ok

4. Check if the emulator port is occupied by another process. VDA communicates with the emulator on port 5554. If another process is using this port, the connection will fail:

ss -tlnp | grep 5554

5. Check available system memory. VVD needs at least 2GB of free memory. Low memory can cause the emulator to start but fail to initialize services properly:

free -h

6. Kill any ADB server running on your machine. ADB and VDA use the same underlying protocol. If you have Android Studio or ADB installed, it can conflict with VDA and steal the connection to the emulator:

adb kill-server

Also, try restarting the VDA server after the Virtual Device is running:

vega exec vda kill-server
vega exec vda start-server

Then check again with vega exec vda devices and vega device list.

Please share the output of all the commands above and we’ll be able to pinpoint the issue.

8

  1. Device bridge check

    bash

    vega exec vda devices -l

    Output:

    Code

    emulator-5554          device transport_id:1

  2. VDA version check

    bash

    vega exec vda version

    Output:

    Code

    Vega Device Adapter version 2.6+3d072013
Server Version 41
Platform Version 34.0.4

  3. KVM check

    bash

    kvm-ok

    Output:

    Code

    INFO: /dev/kvm exists
KVM acceleration can be used

  4. Emulator process check

    bash

    ps aux | grep qemu

    Output (snippet):

    Code

    ... vege-virtual-device -ports 5554,5555 ...

  5. Device info attempt

    bash

    vega device list
vega device info -d emulator-5554

    Result: hangs, no output.

  6. Shell property check

    bash

    vega exec vda shell getprop

    Output:

    Code

    /bin/sh: getprop: command not found

  7. Logs check

    bash

    tail -n 50 virtual_device.err
tail -n 50 virtual_device.out

    Output (important lines):

    Code

    Could not open '.../userdata.qcow2': No such file or directory
WARNING | QEMU main loop exits abnormally with code 1
Virtual device unresponsive after 120s

    Issue: Vega Virtual Device boots but hangs on vega device list / vega device info. Emulator‑5554 is visible, but system services crash.

    Environment: Ubuntu 24.04 LTS (x86_64), SDK v0.24.9914, RAM 3.6 GiB (1.7 GiB free), KVM enabled.

    Diagnostics:

    • vega exec vda devices -l → emulator‑5554 visible

    • vega device list → hangs

    • vega exec vda shell getprop → command not found

    • Logs show: Could not open userdata.qcow2, QEMU exits abnormally

    Request: Please guide how to regenerate/fix missing userdata.qcow2 and cache.ext4 files. Is this a known issue with SDK v0.24.9914 on Ubuntu?

9 
Could not open '.../userdata.qcow2': No such file or directory

Seems very strange. Can we check if:
~/vega/sdk/vega-sdk/main/0.24.9914/vvd/instances/<instance_id>/userdata.qcow2
file exists?

It should automatically get generated on vega virtual-device start – one possible way to uncorrupt it is to delete that ~/vega/sdk/vega-sdk/main/0.24.9914/vvd/instances/<instance_id> folder and then rerun vega virtual-device start