Hi
For VRX the Spaces Services come delivered with the device firmware and can not be modified unless you have been given a special build from Lenovo.
The current VRX firmware version 673 has Spaces Services 0.14.1 installed.
By trying to remove the Spaces Services you likely disabled some Spaces functionality required to run VRX Home. I'd recommend to factory reset the device via adb.
On VRX Hand Tracking can not be active simultaneously with the controllers. Try removing the batteries from your controllers (on the latest firmware just not moving/using the controllers is enough) and check if hand tracking is working now. Try using the Hand Tracking sample from our pre built Snapdragon Spaces Sample that comes together with the SDK package.
We've diligently attempted to resolve the hand-tracking issue by updating the device, but unfortunately, no software update is available. We've also searched for firmware downloads or related documentation, but no such options appear to be available. Despite our best efforts, the hand-tracking problem remains unresolved.
Additionally, we conducted tests using the hand-tracking sample provided in the Snapdragon SDK, but it also did not work. The issue persists even in VRX home. Furthermore, our attempts to create a custom SDK app have not led to any improvements.
For your reference, we've attached a screenshot of the device, including software details.
We kindly request your guidance and assistance in addressing this persistent hand-tracking problem. Any insights or support you can provide would be greatly appreciated.
There is no update option available.
When we lunch snapdragon space hand traking sample demo. It gives a Hand tracking not found error. 
Hi and Thanks for reporting where did you get the Spaces Hand Tracking Sample Demo from SDK 15 if so you should try the new SDK that just came out SDK 17. Also do you know if your device got registered with Lenovo Hub or you did not register your device with any one yet?
We can connect over a call to go over the hand-tracking issue. I will ask you to generate some logs for me so we can do a deeper investigation. Also, I want to see if I can get a later build on VRX. Here is my email. Feel free to look at my schedule if you have teams, or you can give me your email, and I can schedule something.
Afedorch@qti.qualcomm.com
Many thanks for all the files, this is super helpful I verified the issue and started interaction with engineering team on fixing this issue.
Unfortunately, you cannot use hands and controllers at the same time, as controllers emit infrared light that will disrupt the hand tracking model.
There is a plan to enable switch with controller button or automatic set up when you should be able to switch to hands if controllers are set on the table. Engineering team is working on implementing this in the next VRX builds.
I am wondering if there is a fix for simultaneously using hands and controller as of now.
We are facing the same issue on our side, we still have to remove the controller batteries.
HI Afedorch,
This solution works for me after I get SD's latest VRX image update.
Hi Daniel,
The hand tracking only works if you lunch the app with controller like Unity Sample and then pull the batteries out. This is a temporary hack, while SDK team is working on more elegant solutions.
We apologize for all the inconvenience. Plese let me know if it works for you, also what build number is your device is on?
Hello! We are having the same problem with hand tracking on Lenovo device, we have tried all the suggested alternatives we have seen here. Have any solutions been found?
I have sent an email with the log file attached.
Anilsolanki
I want to inquire about an issue we're facing with the Lenovo VRX device. We've been trying to enable hand tracking, but it's not working. To check this, we updated the Qualcomm service to version 15. However, after this update, the Lenovo VRX UI(Home) disappears and doesn't display properly. When we restart the Device, it briefly appears for about 2 seconds and then turns into a black screen. We also attempted to remove the service using ADB commands, but that didn't resolve the issue. Do you have any suggestions or solutions to help us resolve this problem?