Bypass Focus Remote popup.

[Emagine]

Hello.

On the HTC Focus, is there a way to disable the message "Aim forward and long press home button to continue" every time a user puts on the headset?

 

All the apps we need to develope will be run in KIOSK mode without a controller, so I need to bypass this menu.

 

Thank you.
James

[Tony PH Lin]

Hello ,

 

This feature is provided in enterprise solution.

Please visit below link to get more info.

https://enterprise.vive.com/us/

Thanks.

 

[Emagine]

Thank you for the reply.

Just to clarify, does this mean that if we pay $150 for the VIVE Focus Advantage warranty per headset, that paired with the units serial number will unlock some hidden menu to allow me to bypass the remote control?

No problem with the fee, I just need clarification that I'm understanding this right so that I can recommending our company uses these headsets for our clients.

Thank you.
James.

[Tony PH Lin]

Hi ,

 

This inquiry is more business oriented, and I'll pass internally to my colleague then to contact you for the feedback soon.

Thanks.

[Tony PH Lin]

Hi  (James),

 

You can use below command in your Manifest if you only need to disable controller pairing UI.

 

<meta-data android:name="no_controller_pairing" android:value="true" />

However if your application require to use the feature of Kiosk Mode, thenit can only be activated by Advantage pack.

Please let me know your requirements, then I'll pass your request to my colleagues since it's more business oriented and ask them to contact you.

Thanks.

[Emagine]

Thank you very much. I will give this a try right away.

 

The Dev Kit I'm using has the KIOSK mode option, so I should be able to use that to test everything. I will let you know how I get on. If this works as expected we will certianly switch to using the Vive Focus for our clients with the addon Advantage pack.

Kind regards
James.

[Emagine]

Hello.
Just tried that and it works perfectly. Excellent, that's exactly what we are looking for.

Thanks a million for all your help. The Vive Focus is a pretty awsome product.

Kind regards
James.

[pascalvanbeek]

I just tried this myself as well, and it did not help. Any clues what could be the problem?

 

My manifest looks like this:

 

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.unity3d.player"
xmlns:tools="http://schemas.android.com/tools">
<application android:icon="@drawable/app_icon"
android:label="@string/app_name"
android:theme="@style/Theme.WaveVR.Loading"
android:resizeableActivity="false"
tools:replace="android:theme"> <!--You can use your theme here.-->
<activity android:name="com.htc.vr.unity.WVRUnityVRActivity"
android:label="@string/app_name"
android:enableVrMode="@string/wvr_vr_mode_component">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
<category android:name="com.htc.intent.category.VRAPP" />
</intent-filter>
<meta-data android:name="unityplayer.UnityActivity" android:value="true" />
<meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="true" />
<meta-data android:name="no_controller_pairing" android:value="true" />
</activity>
</application>

<uses-permission android:name="android.permission.RECORD_AUDIO" />
<!-- <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" /> -->

<uses-permission android:name="com.htc.vr.core.server.VRDataWrite"/>
<uses-permission android:name="com.htc.vr.core.server.VRDataRead"/>
<uses-permission android:name="com.htc.vr.core.server.VRDataProvider" />
</manifest>

 

I am using:

- Unity 2019.1.2f1

- WaveVR 2.1.0

- Vive Focus (System version: 1.69.1405.3)

 

I have verified that the 'no_controller_pairing' line has made into the manifest that is embedded into the apk (checked with https://github.com/google/android-classyshark).

 

But, I still get the 'aim forward...' message.

 

Any clues?

[pascalvanbeek]

Solving my own question, it appeared that the added 'meta-data' line should go within the application tags, but outside the activity tag. Is that correct?

 

so not 

         ...
        <meta-data android:name="no_controller_pairing" android:value="true" />
   </activity>
</application>

 

but:  

 

          ... 
     </activity>
     <meta-data android:name="no_controller_pairing" android:value="true" />
</application>

 

[Corvus]

Yes that's correct. All Wave meta data fields should be outside the activity tag but inside the application tag.