Webview-based Vega app fails on Ubuntu
VVD crashes after launch
Cause: The following can interfere with VVD startup: • Certain USB hubs or docking stations • Audio interfaces (like Focusrite 2i2) when you use them for both input and output simultaneously Solution: For USB or docking station interference:- Disconnect all USB hubs from your host machine.
- Disconnect any docking stations from your host machine.
- Restart the VVD.
- Use your audio interface for either input or output, but not both simultaneously.
- Alternatively, temporarily use different devices for input and output while you run VVD.
Unable to register VVD for Amazon service
Cause: VVD requires registration before you can use any Amazon services for testing. Without completing the registration process, your app can’t access Amazon services on a virtual device. Solution:- Select “Register this device” on the top right.
- Record the registration code shown on the screen.
- Complete device code registration Go to www.amazon.com/code and enter the code.
VVD crashes due to low memory
Cause: VVD may crash when running multiple resource-intensive processes (such as screen, audio, and video recording) simultaneously. High memory usage creates memory pressure, causing VVD to crash. Solution: Check memory usage while VVD is running. On Mac:- Open Activity Monitor (Applications > Utilities > Activity Monitor).
- Select the “Memory” tab.
- Open a terminal.
-
Use one of these commands:
top(basic system monitor)htop(if installed, more user-friendly)free -h(shows memory in GB/MB instead of bytes)
Without -h, the output shows bytes:
- Close resource-intensive processes.
- Close unnecessary apps.
-
Restart VVD:
VVD fails to start
Cause: You see an error about read or write permissions on/dev/kvm because your Ubuntu system has virtual technology (KVM) disabled.
Solution:
Make sure your Ubuntu image has enabled KVM virtualization technology. If you’re running Ubuntu as a virtual machine, enable hypervisor support. Go to Settings > Processors & Memory > Advanced options to find this setting.
App freezes after device service crash
Cause: The VVD service crashes, causing your app to freeze and become unresponsive. The app remains frozen even after restarting services because VVD breaks the connection. Solution:-
Stop the VVD:
-
Restart the VVD:
-
Restart the app:
VVD can’t connect to the internet
Cause: VVD can’t connect to the internet due to potential network configuration issues. Solution: Test connectivity by opening a shell on VVD:Module dependency not found for kepler-ui-components
Cause: Your app uses@amazon-devices/kepler-ui-components, but you’re testing on an older VVD version that doesn’t include the required native modules. Each SDK version includes a VVD image with specific native OS components. VVD versions from SDK 0.21 and earlier don’t include native modules added in recent updates.
Symptoms:
You see this error when installing your app:
vega sdk ls to confirm that the new version is marked as Active SDK Version. If it isn’t, see New SDK version isn’t active after you install it.
If you can’t upgrade, use one of these alternatives:
- Test on a physical Fire TV Stick 4K Select. Physical devices receive regular updates and include all required modules.
- Remove the
@amazon-devices/kepler-ui-componentsdependency from your app, or limit VVD testing to functionality that doesn’t use UI Components.
