Q: Someone else is logged in when I launched the app. How do I change users?
A: Log out by going to the top right and selecting the circular profile icon. Select "Log out." From there, you can log in by following Step 2. When you are finished, you may log out to avoid someone else launching the app with your login credentials.
Q: How does the VR app sent by the DTT behave when an app has previously been installed on a headset running ArborXR or another MDM?
A: The DTT zip file successfully upgrades 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 without the headset needing to be online.
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?
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 to the cloud, 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 cloud sync. So, in this example, sessions will go to the correct device group.