Hand Tracking causes App freeze after Headset reconnect
T
Tim
started a topic
over 1 year ago
Steps to reproduce:
Restart device
Run Spaces Samples app
Select the Hand tracking demo - its loading shortly and switches to the hand tracking scene.
"Quit out" of the app (Force close the Spaces Samples app, the Spaces Services app and reconnect device)
Run Samples app again and run the Hand tracking demo ---> The app completely freezes
Repeat step 4+5 with the same result
After restarting the mobile device, Hand tracking will work again, until "quitting out" and restarting
The same behaviour is also noticable in our own project. The first run after the device restart, I can turn hand tracking on and off, as many times I like without problem. After closing the app and restarting it freezes up, when switching to hand tracking.
Note: Only force closing the app and restarting without reconnecting the headset is functional. As soon the Headset gets reconnected, stuff starts to break
Best Answer
S
Simon Steiner
said
over 1 year ago
Hi Tim,
I could easily reproduce this issue with your steps - thanks for the clear instructions. I think this is already known bug and related to the user unplug behavior starting with spaces 0.11.1 and will be fixed in a future release.
In the meantime we recommend the following measures:
Gracefully shutdown your application before unplugging your glasses (in Unity via Application.Quit() or Unreal via QuitGame)
When unplugging your glasses before a graceful shutdown force close Snapdragon Spaces Services and your application or best restart your phone
I was able to avoid the issue by force closing the Spaces Services and the Samples application.
To gracefully exit the Spaces Samples app you can hold the Menu button for a couple of seconds. You could implement similar behavior for your own application.
I could easily reproduce this issue with your steps - thanks for the clear instructions. I think this is already known bug and related to the user unplug behavior starting with spaces 0.11.1 and will be fixed in a future release.
In the meantime we recommend the following measures:
Gracefully shutdown your application before unplugging your glasses (in Unity via Application.Quit() or Unreal via QuitGame)
When unplugging your glasses before a graceful shutdown force close Snapdragon Spaces Services and your application or best restart your phone
I was able to avoid the issue by force closing the Spaces Services and the Samples application.
To gracefully exit the Spaces Samples app you can hold the Menu button for a couple of seconds. You could implement similar behavior for your own application.
-Simon
1 person likes this
Simon Steiner
said
over 1 year ago
(this menu button)
1 person likes this
T
Tim
said
over 1 year ago
Hey Simon,
I was actually able to solve the problem, since the time of the original post. Like you said the problem was the "unplugging" without properly closing the app. After implementing the "Application Close" like it was described in your documentation the problem disappeared when using it every time for closing the app.
Tim
Steps to reproduce:
Restart device
Run Spaces Samples app
Select the Hand tracking demo - its loading shortly and switches to the hand tracking scene.
"Quit out" of the app (Force close the Spaces Samples app, the Spaces Services app and reconnect device)
Run Samples app again and run the Hand tracking demo ---> The app completely freezes
Repeat step 4+5 with the same result
After restarting the mobile device, Hand tracking will work again, until "quitting out" and restarting
The same behaviour is also noticable in our own project. The first run after the device restart, I can turn hand tracking on and off, as many times I like without problem. After closing the app and restarting it freezes up, when switching to hand tracking.
Note: Only force closing the app and restarting without reconnecting the headset is functional. As soon the Headset gets reconnected, stuff starts to break
Hi Tim,
I could easily reproduce this issue with your steps - thanks for the clear instructions. I think this is already known bug and related to the user unplug behavior starting with spaces 0.11.1 and will be fixed in a future release.
In the meantime we recommend the following measures:
I was able to avoid the issue by force closing the Spaces Services and the Samples application.
To gracefully exit the Spaces Samples app you can hold the Menu button for a couple of seconds. You could implement similar behavior for your own application.
-Simon
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstSimon Steiner
Hi Tim,
I could easily reproduce this issue with your steps - thanks for the clear instructions. I think this is already known bug and related to the user unplug behavior starting with spaces 0.11.1 and will be fixed in a future release.
In the meantime we recommend the following measures:
I was able to avoid the issue by force closing the Spaces Services and the Samples application.
To gracefully exit the Spaces Samples app you can hold the Menu button for a couple of seconds. You could implement similar behavior for your own application.
-Simon
1 person likes this
Simon Steiner
(this menu button)
1 person likes this
Tim
Hey Simon,
I was actually able to solve the problem, since the time of the original post. Like you said the problem was the "unplugging" without properly closing the app. After implementing the "Application Close" like it was described in your documentation the problem disappeared when using it every time for closing the app.
-
Does Snapdragon Spaces support Unity?
-
Unity Project Template Recommendation
-
Supported Unity Version
-
Bug: recurring Unity deployment error after the first deployment (manifest error, probably)
-
cannot download the Unity SDK
-
FATAL EXCEPTION No virtual method getDeviceProductInfo
-
Image target to 6DOF Tracking
-
Cant download Snapdragon Spaces Services
-
Can't create runtime tracked image libraries
-
What is the best way to upgrade an existing Spaces Unity project to a newer version of the SDK?
See all 165 topics