Developers can override most touch events and some gestures via the Android KeyEvents API. See interaction methods for the Vuzix Blade on the Developer Center.
Developers can override most touch events and some gestures via the Android KeyEvents API. See interaction methods for the Vuzix Blade on the Developer Center.
We are working on this feature and will make it available via a future OTA update.
Navigate to Settings > Device > Volume > Vibrations. There will be an option to disable/enable the vibrations based on current configuration.
Visit the Vuzix App Store for a listing of browsers available to the Blade.
Please note, it is highly recommended to use the trackpad input feature from the companion app when navigating a browser on the Blade.
To manage files between the Vuzix Blade and your Mac please visit the following site to download Android File Transfer.
To manage saved networks, navigate to the "Saved Networks" menu.
To enable Developer mode (Dev Options) with ADB Debugging, please visit the following Knowledge Article: Enable ADB Debugging on the Vuzix Blade.
When using the Camera1 API:
For the best experience, avoid calling the method setRecordingHint(true). Passing the value true to this method will shorten the exposure time in the shutter, resulting in a higher frame rate, but less brightness.
When using the Camera2 API:
Use CameraDevice.TEMPLATE_PREVIEW over CameraDevice.TEMPLATE_RECORD for increased brightness in low-light environments.
The Blade supports 7.6MP (3264 x 2448) and 4.8MP (2593x1944) JPGs for still pictures and 1080p (1920 x 1080) and 720p (1280x720) for Videos.
While booting:
While running:
To see advanced settings on Blade, you can enable Developer mode or Dev Options.
The Camera LED status turns on while camera hardware is being accessed. Camera LED also turns on when photos are taken or videos are being recorded. Note that just accessing the camera hardware via the API can turn it on.
Due to the nature of the Vuzix Blade, third-party Android applications not specifically designed for the Blade may not run as expected (or at all).
No, the Blade doesn't support quick charge.
The Blade is not a CTS (Compatibility Test Suite) compliant device and does not support the Play Store or other Google Mobile Services (GMS) not covered by the Android Open Source license.
The Blade pulls GPS location data from a linked companion device.
As such, you will need to define a location listener:
private final LocationListener mLocationListener = new LocationListener() {
@Override
public void onLocationChanged(final Location location) {
//your code here
}
};
Then utilize the LocationManager API to register for updates:
mLocationManager = (LocationManager) getSystemService(LOCATION_SERVICE);
mLocationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, LOCATION_REFRESH_TIME,
LOCATION_REFRESH_DISTANCE, mLocationListener);
And finally, add the permissions to access the data by adding one of the following to your manifest:
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
or
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
Attempt to re-connect by:
Make sure the USB Connectivity mode is updated from charge only to MTP or PTP.
The battery icon indicates the Blade's charge level.
The SD card icon is present when either the internal storage, external SD card, or both, have been filled to more than 90% of their capacity. Moving or deleting files on the system will automatically clear this warning.
The airplane icon indicates airplane mode is currently active on the Blade. To disable, hold the power button and select Airplane Mode from the popup menu.