Release Notes 1 5 9

QUALCOMM Augmented Reality SDK 1 ©2012 Qualcomm Incorporated

Vuforia SDK for Android - Release Notes [QCAR v1.5.9]

Last update: February 22, 2012

Introduction

This file contains general release notes for the Vuforia Augmented Reality SDK.

QCAR v1.5.9 Bugfixes / Features

Vuforia branding introduced to SDK

Fixed memory leaks

Fixed issue where frame and augmentation of previous run is visible for a few frames

Added OcclusionManagement sample app showing how to create an occlusion effect using the

video texture feature

The android:minSdkVersion has been updated to 8 – this means QCAR can only be installed on

devices running Android 2.2 Froyo or above. Android 2.1 Éclair is no longer supported

Detection and tracking speed has been improved

Added new CONTINUOUS_AUTOFOCUS mode to QCAR and exposed it in samples via GUI

o Note:Continuous auto focus is only available on select Android devices, e.g. Galaxy

Nexus S, Pantech Vega Racer

Fixed an issue where the reordering of trackables in the dataset XML file causes tracking to fail

Fixed an issue where the registering for YUV pixel format images fails

Added support for ICS and Honeycomb devices

Known Issues

The MACRO and INFINITY focus modes don‟t work on the Galaxy Nexus (driver seems to ignore

this setting)

The CONTINUOUS_AUTOFOCUS mode stops working after triggering a single autofocus action

and can only be activated again when you stop and restart the camera (e.g. by pausing and

resuming a QCAR sample application)

On certain devices, the video preview rendering and the rendering layer order may be

mismatched after another application overlays the QCAR rendering window. Apps may optionally

destroy the Android activity with a call to Activity.finish() in your main Activity‟s onPause() and

may reinitialize it onResume(). This no longer happens on devices running Honeycomb or above.

“CPU Pegged” issue is showing up randomly and causing a crash on certain devices

The Motorola Flipout is currently not supported

On rare occasions under very low light conditions, FrameMarkers may detect the same marker

twice with different IDs

The BackgroundTextureAccess and OcclusionManagement apps support only landscape-left

orientation

On ICS devices a black screen has been observed after unlocking the phone with the “face

unlock” feature

QCAR v1.5.4 – Beta1


Bugfixes / Features

Provided developer access to the background video texture (allows custom visual effects)

Added the ability to swap out data sets at runtime - If your app needs to augment more than 60

images, you can now create multiple datasets -using the web-based My Trackables tool- and

load the appropriate dataset at runtime. You no longer have to upgrade your app to change the

target dataset, and you can now build AR experiences that work on a large number of images

Added support for creating Frame Markers at runtime

Added support for resizing Image Targets at runtimeImproved FrameMarker tracking including

support for partial occlusions. Note that the design of the frame markers has been changed and

developers must use the new frame markers present in the assets folder of the SDK package to

take full advantage of these new improvements

Improved ImageTarget tracking including reduced pose jitter, improved recovery from tracking

failure and faster detection

Faster QCAR start-up times

Known Issues

Android Ice Cream Sandwich is currently not supported

Reordering trackables in the .xml configuration file after a dataset is generated will cause tracking

failures

After resuming a previously paused sample app, the last rendered frame prior to pausing will be

very briefly displayed as Android doesn‟t seem to clear the back buffer upon onResume(). You

can work around this by calling glClear(GL_COLOR_BUFFER_BIT). If double buffering is

enabled, you may need to call it multiple times.


mismatched after another application overlays the QCAR rendering window. Apps may optionally

destroy the android activity with a call to Activity.finish() in your main Activity‟s onPause() and

may reinitialize it onResume()

Trackable names that are greater than 10 characters sometimes cause the app to freeze

MultiTarget tracking often breaks when all of the parts (ImageTargets) are not completely in

front of the camera

“CPU Pegged” issue is showing up randomly and causing a crash on certain devices

The Motorola Flipout is currently not supported

On rare occasions under very low light conditions, FrameMarkers may detect the same marker

twice with different IDs

The Video Background Access app supports only landscape-left orientation

Domino creation in Dominoes sample on re-launch is not currently working

On certain devices toggling the flash works only after the second time after onResume()

Images cannot be retrieved in YUV pixel format


Optimized performance of both the synchronous & asynchronous rendering modes


Fixed a bug where a NullPointerException was thrown when calling setFlashTorchMode

Fixed an issue where false positives detections occurred for some targets

Reduced jitter in augmentations for both ImageTargets and MultiTargets

Fixed a bug where the video background does not render in full screen on some devices

Fixed a bug in the Dominoes sample app where an array out of bounds access could happen

Added support for Android 3.x (Honeycomb)


Added support for controlling the camera flash mode

Added support for controlling the camera focus mode

Added support for synchronous and asynchronous video rendering (bound to the camera capture

frame rate vs. fixed rate)

Fixed an issue where the augmented content is not rendered in the correct location in portrait

mode

Fixed issue where Virtual Buttons don‟t always work with OpenGL 1.1 in the Dominoes sample

app

Renamed MultiImageTarget to MultiTarget

Improved overall tracking and detection performance

Improved redetection performance of recently lost targets

Improved detection and tracking of Frame Markers

Improved video background rendering performance

Improved robustness of Virtual Buttons

Changed default Virtual Button sensitivity to LOW

Added support for the vast majority of devices running Android 2.1 and above. See list of

supported devices available at developer.qualcomm.com/ar

Simplified building of sample apps: Sample apps now use Android NDK functionality to copy the

QCAR shared libraries to the libs folder

Extended sample applications to control flash and auto focus via application GUI

Added new tracking targets for Virtual Button and MultiTarget sample apps

Improved the Image Target ratings mechanism on the Target Management System (TMS)

Fixed a bug where the TMS would not accept images of certain sizes

New Android permissions required: ACCESS_WIFI_STATE and READ_PHONE_STATE

Known issues

The following screen orientations that are available in Android 2.3 (Gingerbread) and above are

not supported by the QCAR SDK

o SCREEN_ORIENTATION_REVERSE_LANDSCAPE

o SCREEN_ORIENTATION_REVERSE_PORTRAIT

After resuming a previously paused sample app, the last rendered frame prior to pausing will be

very briefly displayed. The reason for this is that Android doesn‟t seem to clear the back buffer

upon onResume(). You can work around this in your application by calling


glClear(GL_COLOR_BUFFER_BIT). You may need to call it multiple times to handle the case

where double buffering is enabled.


mismatched after another application overlays the QCAR rendering window.

QCAR v0.10.0 – BETA2 Bugfixes / Features

Added support for multi-image target reconfiguration (add / remove / reconfigure parts on the fly)

Added support for virtual button reconfiguration (add / remove / reconfigure buttons on the fly)

Updated existing sample applications:

Reconfigurable virtual buttons

Reconfigurable multi-image targets

Added dialog boxes to display QCAR initialization errors

Removed Shared library and moved shared code into individual sample apps to create independent stand-alone projects

Known issues

Rare application freeze and "CPU may be pegged" issue has been observed on Android 2.2 (Froyo).

This has been observed by others working with camera and OpenGL on Android

Video preview rendering and rendering layer order mismatched after another application overlayed QCAR rendering window Camera-JNI and mPreviewLock messages appear in logcat output on Android 2.1

Application in „portrait mode‟ may result in displaced augmentations

Documents

Release Notes 1 5 9