3. Connecting Your Headset

• Ensure that the headset has fully booted up, which traditionally takes about 30 seconds.
  
• Connect your VR headset via USB-C to your computer. If initially unsuccessful, please retry the connection.
  
• Accept the USB-C connection request inside the headset by selecting "Yes" and "Always Allow from this Computer." Make sure a green dot appears in the DTT app, showing it's connected to the headset. A red dot indicates it is not connected.
• The "allow" pop-up window will appear while the headset is in kiosk mode - the mode where only the M+F app is accessible.
  
• If you do not see this messaging in kiosk mode, reach out to your administrator so they can update the ArborXR settings to allow file transfer and USB debugging. 
  
• Non-HMS Quest devices can temporarily exit kiosk mode by pressing the Home button (or pinching the thumb and index finger together as described directly below) → ArborXR Quick Access Menu → gear icon → Unlock Advanced Settings → enter PIN (if applicable)→ Exit ArborXR Home → follow steps below
• Quest users: If ArborXR (the app launcher) is running in its home environment and you do not see a modal to allow the connection, open the universal menu (see steps directly below on how to access the universal menu). The notification to accept the USB connection will be in the notifications area (the bell icon on the Meta Quest toolbar).
• Press the button with the Meta (or Oculus) logo on the right controller to access the universal menu. 
  
• To access the universal menu without controllers, look at your palm at eye level and then pinch your thumb and index finger together until the menu appears, then release. 
  
• Select the bell icon and click on the notification to connect the headset.

• On your laptop: select "Allow" when asked "Allow accessory to connect?" in a pop-up window.
  
• Once connected, the button labeled Import session data should turn green, indicating that the headset is recognized.
  

4. Importing Data

• Click on Import session data to load your session files into the app. A progress bar will appear, indicating the upload is underway.

5. Syncing to Cloud

• To sync your data, click Sync Assessments. To send additional session information, including encountered errors, hit Sync Logs.
• You will see each a total count for submitted, failed, and waiting sessions.
  

6. Updating the App

• Select the .zip file to update using the Choose file
   button.
• Choose the file you wish to upload and hit "open"
• Click Update and wait for the update process to complete. If it takes longer than a few minutes, check for error messages.
• To verify the update, disable wifi on your headset and launch the Moth+Flame App.
  

Once the zip file is chosen, the "select the .zip file to update" button will turn green and read "update." Select "update" to upload the zip file.

As the zip file is extracted and installed, the window will darken and you will see progress messaging:

​

​

​

​

Once installed, you will see a "Device successfully updated!" message. The screen will no longer be darkened once the upload is complete. If the upload is unsuccessful, you will receive an error message.

7. Confirming the Update

1. Restart the headset after successfully updating it with the Data Transfer Tool. 
   
2. After restarting, go to the “About”  menu inside the app and check that the version number matches the version that was provided to you. 
   

Please reach out to your Moth+Flame Customer Success Manager or productsupport@mothandflamevr.com if you have difficulty updating your headset fleet with the Data Transfer Tool.

Q+A

Q: How does the DTT zip file behave in a pre-existing ArborXR/MDM environment?

A: The DTT zip file successfully versions up the app in a pre-existing ArborXR environment, even if the headset is offline. This streamlines the update process, eliminating the need to update the headset with an Arbor package separately.

Q: What is the advantage of using the Data Transfer Tool (DTT) for updates?

A: By using the DTT, you can handle all application and module updates exclusively through this tool. 

Q: What should we expect in terms of app version metadata in the ArborXR home launcher after using DTT for updates?

A: The app version metadata displayed in the ArborXR home launcher will not change. For example, if you click the "more info" button under the Moth+Flame icon, it will still show the old version information. However, when you launch the Moth+Flame App and check the "About" section in the menu, you will see the updated version that was sent via DTT.

Q: What happens if a headset goes online after being updated with the DTT?

A: If the app version in ArborXR is updated to match what was placed on the headset offline, the headset does not require a new download of the app when it goes back online. This ensures a seamless experience even if the headset transitions between offline and online states.

Q: Will headsets that receive updates using the DTT copy over active classes?

A: Yes, active classes associated with the module files will be transferred.

Q: If I login to DTT with an email that is associated with multiple organizations in the portal, which organization am I logged into? Are the sessions sent to the organization I’m logged into in DTT (if so, how is that determined if my email is in multiple orgs)? 

A: Sessions are not tied to your login. Instead, they are linked to the device group the headset belongs to. This means you can log in and import sessions from another user's headset, and the sessions will still report accurately to the device group and organization that the headset is assigned to in the portal.

Q; I'm having issues with the DTT and can't upload my sessions or logs to the portal. Is there another way I can upload them?

A: Yes. Please see this article

Q: Does the Data Transfer Tool support OBB files?

A: Yes, to upload an OBB file, make sure to create a zip file and include the OBB file as well as the apk file. The name of the zip file should follow the format "vrconversation_" followed by the version number, for example, 0.15.5.860.

Q: If headsets are in the wrong Device Group in the portal and I move them to the correct device group before syncing sessions from the DTT, which device group will the sessions go to when running a report?

A: The sessions will be assigned to the device group they are in at the time of the sync. So, in this example, sessions will go to the correct device group.