# Common Known Issues

There are known issues that may affect the development workflow. These are common known issues and will be tackled in future releases of the Snapdragon Spaces SDK or the Snapdragon Spaces Services runtime. Some issues that may be encountered, are development tool specific. Please see the corresponding tools Known Issues for more support.

# Apps will not display on glasses with Snapdragon Spaces 0.6.0

There is a new requirement on Camera permission for Snapdragon Spaces Services application.

  • Find the Snapdragon Spaces Services application from the App Launcher
  • Press and hold (Long press) on Snapdragon Spaces Services and select "App info".
  • Press to enter "Permissions" -> Verify Camera is under Allowed. If not, tap and set it to "Allow only while using the app". Please see Running Spaces applicaitons for more details.


This issue has been fixed in 0.6.1, but the Camera permission still needs to be granted to enable Hand Tracking functionality.

# Application close

Since the main activity of the application is started on the Viewer, it won't show up on the multitasking view/recent apps list in Android, which is not ideal if the application should be closed. The samples included in the Snapdragon Spaces Unity package showcase two different ways of closing the application gracefully:

  • Press & hold the Host controller's Menu button for 2 seconds (Implemented in the SampleController.cs script).
  • Addition of a dedicated UI button in the main menu scene.

Otherwise, the only option to close the application, is by force stopping like described in the next section.

# Application start

In some occurrences, the application might not start properly on the Viewer. To troubleshoot the issue, Force Stop both the application and the Snapdragon Spaces Services runtime. This can be done by long pressing on the app icon in the app launcher until a context menu showing App Info appears. After opening the App info view, verify Camera is listed under Permissions and then the application can be stopped by clicking Force Stop.

Force stopping the Spaces Services

Here are some reasons that might lead to an unsuccessful start of the application:

  • First app start after a Host device reboot.
  • Closing one Spaces app and opening another one too fast before Snapdragon Spaces Services quit properly.

# Application freeze

# Handset events

Locking and unlocking the Host device, or any other application interruption, will lead to the application being suspended and a blank/black view being present on the Viewer.

# Unplugging glasses

If the glasses are disconnected while a Spaces application is running it will cause the handset to lock up temporarily. This can be resolved by waiting a few seconds and then following the steps to force quit Spaces Service. For the best developer experience follow the Application close.

# Companion controller's pointer ray not visible

The ray of the Companion controller might be invisible in some occasions, like switching from Gaze input to the Companion controller in the samples by clicking on the Menu button. In that case, creating a custom controller with a head pose reset on every click on the Menu button, would improve the user experience.

# Image Tracking issues

# Detection distance

The current underlying implementation of the image tracking subsystem uses the Viewer device's left tracking camera at the moment, which is not perfectly suited for image detection. The current detection range lies around 30 to 50 cm for a DIN A4/US letter sized target, therefore.

# Pose offset

The pose of the detected and tracked image can be off by around 2 to 5 cm, depending on the viewing distance and angle.

# Rendering issues

# Screen wobble

Virtual content might wobble under fast movement.