UBIK Wiki Test / Augmensys - User contributions [en]

UBIK Client Basics

2014-06-23T10:00:12Z

ATO:

== Prerequisites ==
=== Options ===
There are two types of settings in UBIK client: [[Global Settings]] and [[User Specific Settings]].

The [[Global Settings]] include the following

{| class="wikitable" | width = "75%"
|-
! Name!! Purpose
|-
| ''AuthServerName''|| The name of the server to connect to for user authentication
|-
| ''AuthPortNumber''|| The port number to use when connecting to the authentication server (optional)
|-
| ''UBIKAuthContentService''|| The name of the UBIK authentication service
|-
|}

The [[User Specific Settings]] include the following

{| class="wikitable" | width = "75%"
|-
! Name!! Purpose
|-
| ''UBIKContextName''|| The UBIK [[CONTEXT]] name
|-
| ''UBIKApplicationName''|| The UBIK [[APPLICATION]] name
|-
| ''UBIKContentService''|| The name of the UBIK content service
|-
| ''Protocol''|| The protocol to use for data communication over the Internet (e.g.: HTTPS)
|-
| ''ServerName''|| The name of the server to connect to for fetching content
|-
| ''PortNumber''|| The port number to use when connecting to the content server (optional)
|-
| ''PriorityThreshold''|| Any property with a priority number greater than this integer setting value is regarded as a high priority property and is highlighted when being displayed
|-
| ''UpdateExpirySeconds''|| The number of seconds one has to wait before the same update will be considered necessary. If an update of certain content has just ended successfully and is requested again within the amount of time configured in this setting, the client simply dismisses the new request. However, this setting does not affect [[Forced Updates in Manual Synchronization Mode]].
|-
| ''SyncMode''|| The possible values are Automatic, Manual Commit and Offline. For more details, please refer to [[Sync Mode]].
|-
| ''ShowSystemProperties''|| If set to true, all properties will be displayed; otherwise, only the ones that are marked as [[METACLASSSCOPE#Visibility|visible]].
|-
|}

Additionally, the demo application and its unique user specific settings are listed as follows

{| class="wikitable" | width = "75%"
|-
! Name!! Purpose
|-
| ''PrepareMode''|| This is set to true/false when users switch the client to offline/online mode in the start menu. However, editing this setting directly might not trigger the expected behavior
|-
| ''NumberPropertyEditor''|| Whether to use the normal keyboard or the [[UBIK Number Pickers]] for editing numeric properties
|-
| ''CurrentAltitude''|| The (mock) altitude in meters to use in Augmented Reality activities
|-
| ''ContentDistanceFilterThreshold''|| The threshold in meters up to which billboards are displayed in Augmented Reality activities
|-
|-
| ''PositioningMode''|| The different positioning modes of the [[Location Manager]] can be selected with this setting.
|-
|}

=== Demo Login ===
Username: Demo 
Password: 1234

== Working with {{UBIK}} ==

=== Login ===
Users need to login in order to access confidential data. This can be done in the [[Login Dialog]].

=== Menu ===

{| class="wikitable" | width = "50%"
|-
! Menu!! Menu item!! Purpose
|-
| ''Activity wheel'' || - || Shows if the client is currently downloading content from the server
|-
| ''Sync mode'' ||-|| Opens the sync manager (in manual sync mode)
|-
| ''Home'' || Start menu || Opens the start screen
|-
| ''Home'' || Settings || Opens the settings dialog
|-
| ''Home'' || Information || Shows information about the software version and the device
|-
|}

=== Info Activity ===
Shows static information about the app, like the version code and the minimum required web service version.
Also allows to [[Add a Certificate (UBIK Android)|add a server certificate]] to the app.

=== Content Browser ===
Allows to navigate through the entire data model in a hierarchical manner, as it is published by the server.

==== Context Menu ====

==== Root objects ====

==== Child objects ====

==== Editors ====
===== Geo Editor =====
Editor used to set GEO locations for a specific content object. This is done by accessing the GEO property editor of the object.

==== Properties ====
===== Teach In =====
The user can enter the location manually or, if available, can use the location provided by the positioning service. In case the positioning service doesn't deliver any location the user has only the possibility to enter the location manually.

==== Documents ====
===== Redlining =====
See the section [[Documents_(UBIK_Android)#Redlining|redlining]] in the [[Documents_(UBIK_Android)|Documents]] article.

=== POI View ===
Brings up the [[POI View|Augmented Reality view]] and displays Points of Interest (POI's) related to the current location of the mobile device.

=== Map View ===
Opens the [[map View|Map view]] and displays Points of Interest (POI's) related to the current location of the mobile device.

=== Online/Offline mode ===
Switches between online and offline mode.

=== ID Marker ===
Provides a fast and convenient way for users to find objects that are identifiable through [[optical code|optical codes]], in this case ID Markers.

=== QR Code ===
Provides a fast and convenient way for users to find objects that are identifiable through [[optical code|optical codes]], in this case QR Codes.

=== Markerless ===
Opens the [[POI View|Augmented Reality view]] supporting [[Help:Configure_Dynamic_AR_Content#Markerless_Activity|Markerless Scanning]] based on Image Detection.

=== ID Marker 3D ===
Opens the [[POI View|Augmented Reality view]] supporting [[Help:Configure_Dynamic_AR_Content#ID_Marker_Activity|ID Marker Scanning]] based on ID Markers.

=== Support Button ===
[[File:Ubik android support button.png|220 px|thumb|border|alt=Support Button|Support Button]]
The Support Button starts the Communication Application "Skype" and is available in the Action Bar of the UBIK.Android.Demo Application.
It will be used to call directly a Support Hotline.

[[Category:UBIK Client]]

2014-04-16T09:46:18Z

2014-04-16T09:14:45Z

ATO:

HowTo:Use POI Groups

2014-04-15T07:31:53Z

2014-03-04T08:34:35Z

ATO:

== Introduction ==
The Dynamic AR Content feature allows the user to see different content according to a marker configuration.
The configurable content are 3D objects, movies and {{UBIK}} objects. Currently this feature is enabled for ID Markers and Markerless scanning, meaning image tracking.
Therefore, every time the user has scanned an ID marker or a picture, the corresponding object (3D object, movie or {{UBIK}} object) will be processed and, according to the configuration, displayed on the screen.

== Setup ==
In order to be able to use the feature properly, a setup folder is required and can be found at the following link [Folder Structure]. The setup folder contains:
# A root folder, named ''UBIK''
# The ''UBIK'' root folder contains a child folder, named ''ARConfig''
# The ''ARConfig'' contains two child folders named ''IDMarker'' and ''Markerless''
## ''IDMarker'' folder contains the resources and configuration files needed for scanning an id marker
## ''Markerless'' folder contains the resources and configuration files needed for scanning a picture
# ''IDMarker'' and ''Markerless'' folder contain a ''res'' and a ''conf'' folder
## The ''res'' folder contains all the resources to be shown, like 3D objects, videos and links to {{UBIK}} objects
## The ''conf'' folder contains all the configuration files

The following picture shows an exemplary sketch of the folder structure:
:[[File:folder_structure.png]]

== Action Mapping XML Setup ==

After the folder is configured, the next step is to validate the schema against an online validator. A solution can be found at [http://www.utilities-online.info/xsdvalidation/ Online XML Schema Validator]. The schema used to validate against can be found inside the ''UBIK'' Folder and is named ''xsd_schema_validation''.

The action mapping xml contains different actions such as GeometryAction, MovieAction and UBIKObjectAction.

* The following xml shows an example configuration:
<source lang="xml">
<TrackingActionMapping>
<GeometryAction TrackingID="1">
<GeometryResource>
<ResourcePath>pump.obj</ResourcePath>
<Scale>100</Scale>
</GeometryResource>
</GeometryAction>

<UBIKObjectAction TrackingID="2"/>
<GeometryAction TrackingID="5">
<GeometryResource>
<ResourcePath>pump.obj</ResourcePath>
<Scale>100</Scale>
<RotationDegrees>
<Z>90</Z>
</RotationDegrees>
</GeometryResource>
</GeometryAction>

<UBIKObjectAction TrackingID="6">
<UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
</UBIKObjectAction>

</TrackingActionMapping>
</source>

All Action tags must specify a Tracking id, as an attribute. The Tracking id must exist in the tracking xml.

{{Attention|If a texture is used for a geometry, the material (*.mtl file) and the texture (picture) must all exist in the same place in order for to have the 3D object displayed properly, Only the geometry has to be specified as a resource in the Action Mapping, though.}}

=== GeometryAction Tag ===

Inside the ''GeometryAction'' tag there can be a GeometryResource tag that defines the type of resource required for the GeometryAction.

==== GeometryResource Tag ====

The GeometryResource contains:
# '''Resource path''': the resource path of the 3D object or video to be displayed.
# '''Scale''': if specified, the 3D object will be scaled to this size.
# '''OffsetMillimeters''': if specified, this value will be added to the position of the detected marker when displaying the 3D object. The offset can be defined along the X, Y and Z axis.
# '''RotationDegrees'''. if specified, the 3D object will be rotated by this value against the detected marker.

* ''Resource path example''. pump/pump.obj.

* ''OffsetMillimeters example''.
<source lang="xml">
<OffsetMillimeter>
<X>10</X>
</OffsetMillimeter>
</source>

=== MovieAction Tag ===

Inside the ''MovieAction'' tag there can be two possible resources defined, a MovieResource and a PlayButton resource.

==== MovieResource ====

The ''MovieResource'' Tag contains the same values as the ''GeometryResource'' except the rotation vector.

==== PlayButton Tag ====

The ''PlayButton'' Tag, if it is defined, contains the same values as the ''GeometryResource'' tag. Its purpose is to start a video, if the geometry is touched.

=== UBIKObjectAction Tag ===

The ''UBIKObjectAction'' tag should enable handling of the {{UBIK}} objects when scanning either a picture or an id marker. The tag must contain the tracking id attribute and, optional, the ubik-uid tag.
# Example. When configuring a tag without the ubik-uid tag the object is searched based on its MarkerID property which is the value inside TrackingID attribute. If the ubik-uid tag exists the object is searched based on the value inside the ubik-uid tag.
== Tracking Data XML ==

The first step is to configure the tracking data xml in order for {{UBIK}} to recognize scanned pictures and id's.
In case the marker is a picture (image), the location of the pictures must also be provided. In the example it's ../res/pic_name.(png, jpeg).
The id located in the tracking data xml should be the same as the order of the id in the list of ids.

* This example below the configuration of the location of the image:
<source lang="xml">
<SensorCOS>
<SensorCOSID>1</SensorCosID>
<Parameters>
<referenceImage widthMM="420" heightMM="297">../res/img_pic.png</referenceImage>
</Parameters>
</SensorCOS>
</source>

== '''Usage''' ==
In order to use the previously configured xmls, you can use either the ID Marker activity or the Markerless activity on the {{UBIK}} Android Client.

=== ID Marker Activity ===

Having in mind the setup tracking ids, you can now scan id markers.
* For an id that has a 3D object mapped in the action xml, the object should be displayed on the screen as shown in the next picture.
* If the id has a video object mapped in the action xml, you should see a video object on the screen, depending on the existence of the play button.
* If the play button exist you should see first see the play button, and after it's clicked the mapped video. If the play button doesn't exist, the movie will be shown immediately.

=== Markerless Activity ===

The scenario is very similar with the id marker activity with the only difference that instead of ids you have to scan your tracking images.

=== Examples ===

With the existent configuration from the zip file, you should see the following picture when scanning the first id or the first picture:
:[[File:scanning_id1.png]] 

When scanning the second id or the second picture, you should see the following:
:[[File:scanning_id2.png]] 

When scanning the sixth id, using the Markerless activity, you should see a play button and, if pressed, a movie.
* Play button:
:[[File:scanning_id3_play_button.png]] 
* Movie:
:[[File:scanning_id3_movie.png]] 

When scanning the sixth id using the IdMarker Activity you should see a play button also and, if pressed, a movie too.
* Play button:
:[[File:scanning_id6_play_button.png]] 
* Movie:
:[[File:scanning_id6_movie.png]] 

[[Category:How-To]]
[[Category:UBIK Client]]

HowTo:Configure Dynamic AR Content

2014-03-03T15:18:18Z

ATO:

== Introduction ==
The Dynamic AR Content feature allows the user to see different content according to a marker configuration.
The configurable content are 3D objects, movies and {{UBIK}} objects. Currently this feature is enabled for ID Markers and Markerless scanning, meaning image tracking.
Therefore, every time the user has scanned an ID marker or a picture, the corresponding object (3D object, movie or {{UBIK}} object) will be processed and, according to the configuration, displayed on the screen.

== Setup ==
In order to be able to use the feature properly, a setup folder is required and can be found at the following link [http://wiki.augmensys.com/images/6/66/Dynamic_AR_Content_Folder_Structure.rar Folder Structure]. The setup folder contains:
# A root folder, named ''UBIK''
# The ''UBIK'' root folder contains a child folder, named ''ARConfig''
# The ''ARConfig'' contains two child folders named ''IDMarker'' and ''Markerless''
## ''IDMarker'' folder contains the resources and configuration files needed for scanning an id marker
## ''Markerless'' folder contains the resources and configuration files needed for scanning a picture
# ''IDMarker'' and ''Markerless'' folder contain a ''res'' and a ''conf'' folder
## The ''res'' folder contains all the resources to be shown, like 3D objects, videos and links to {{UBIK}} objects
## The ''conf'' folder contains all the configuration files

The following picture shows an exemplary sketch of the folder structure:
:[[File:folder_structure.png]]

== Action Mapping XML Setup ==

After the folder is configured, the next step is to validate the schema against an online validator. A solution can be found at [http://www.utilities-online.info/xsdvalidation/ Online XML Schema Validator]. The schema used to validate against can be found inside the ''UBIK'' Folder and is named ''xsd_schema_validation''.

The action mapping xml contains different actions such as GeometryAction, MovieAction and UBIKObjectAction.

* The following xml shows an example configuration:
<source lang="xml">
<TrackingActionMapping>
<GeometryAction TrackingID="1">
<GeometryResource>
<ResourcePath>pump.obj</ResourcePath>
<Scale>100</Scale>
</GeometryResource>
</GeometryAction>

<UBIKObjectAction TrackingID="2"/>
<GeometryAction TrackingID="5">
<GeometryResource>
<ResourcePath>pump.obj</ResourcePath>
<Scale>100</Scale>
<RotationDegrees>
<Z>90</Z>
</RotationDegrees>
</GeometryResource>
</GeometryAction>

<UBIKObjectAction TrackingID="6">
<UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
</UBIKObjectAction>

</TrackingActionMapping>
</source>

All Action tags must specify a Tracking id, as an attribute. The Tracking id must exist in the tracking xml.

{{Attention|If a texture is used for a geometry, the material (*.mtl file) and the texture (picture) must all exist in the same place in order for to have the 3D object displayed properly, Only the geometry has to be specified as a resource in the Action Mapping, though.}}

=== GeometryAction Tag ===

Inside the ''GeometryAction'' tag there can be a GeometryResource tag that defines the type of resource required for the GeometryAction.

==== GeometryResource Tag ====

The GeometryResource contains:
# '''Resource path''': the resource path of the 3D object or video to be displayed.
# '''Scale''': if specified, the 3D object will be scaled to this size.
# '''OffsetMillimeters''': if specified, this value will be added to the position of the detected marker when displaying the 3D object. The offset can be defined along the X, Y and Z axis.
# '''RotationDegrees'''. if specified, the 3D object will be rotated by this value against the detected marker.

* ''Resource path example''. pump/pump.obj.

* ''OffsetMillimeters example''.
<source lang="xml">
<OffsetMillimeter>
<X>10</X>
</OffsetMillimeter>
</source>

=== MovieAction Tag ===

Inside the ''MovieAction'' tag there can be two possible resources defined, a MovieResource and a PlayButton resource.

==== MovieResource ====

The ''MovieResource'' Tag contains the same values as the ''GeometryResource'' except the rotation vector.

==== PlayButton Tag ====

The ''PlayButton'' Tag, if it is defined, contains the same values as the ''GeometryResource'' tag. Its purpose is to start a video, if the geometry is touched.

=== UBIKObjectAction Tag ===

The ''UBIKObjectAction'' tag should enable handling of the {{UBIK}} objects when scanning either a picture or an id marker. The tag must contain the tracking id attribute and, optional, the ubik-uid tag.
# Example. When configuring a tag without the ubik-uid tag the object is searched based on its MarkerID property which is the value inside TrackingID attribute. If the ubik-uid tag exists the object is searched based on the value inside the ubik-uid tag.
== Tracking Data XML ==

The first step is to configure the tracking data xml in order for {{UBIK}} to recognize scanned pictures and id's.
In case the marker is a picture (image), the location of the pictures must also be provided. In the example it's ../res/pic_name.(png, jpeg).
The id located in the tracking data xml should be the same as the order of the id in the list of ids.

* This example below the configuration of the location of the image:
<source lang="xml">
<SensorCOS>
<SensorCOSID>1</SensorCosID>
<Parameters>
<referenceImage widthMM="420" heightMM="297">../res/img_pic.png</referenceImage>
</Parameters>
</SensorCOS>
</source>

== '''Usage''' ==
In order to use the previously configured xmls, you can use either the ID Marker activity or the Markerless activity on the {{UBIK}} Android Client.

=== ID Marker Activity ===

Having in mind the setup tracking ids, you can now scan id markers.
* For an id that has a 3D object mapped in the action xml, the object should be displayed on the screen as shown in the next picture.
* If the id has a video object mapped in the action xml, you should see a video object on the screen, depending on the existence of the play button.
* If the play button exist you should see first see the play button, and after it's clicked the mapped video. If the play button doesn't exist, the movie will be shown immediately.

=== Markerless Activity ===

The scenario is very similar with the id marker activity with the only difference that instead of ids you have to scan your tracking images.

=== Examples ===

With the existent configuration from the zip file, you should see the following picture when scanning the first id or the first picture:
:[[File:scanning_id1.png]] 

When scanning the second id or the second picture, you should see the following:
:[[File:scanning_id2.png]] 

When scanning the sixth id, using the Markerless activity, you should see a play button and, if pressed, a movie.
* Play button:
:[[File:scanning_id3_play_button.png]] 
* Movie:
:[[File:scanning_id3_movie.png]] 

When scanning the sixth id using the IdMarker Activity you should see a play button also and, if pressed, a movie too.
* Play button:
:[[File:scanning_id6_play_button.png]] 
* Movie:
:[[File:scanning_id6_movie.png]] 

[[Category:How-To]]
[[Category:UBIK Client]]

HowTo:Configure Dynamic AR Content

2014-03-03T15:17:49Z

ATO:

== Introduction ==
The Dynamic AR Content feature allows the user to see different content according to a marker configuration.
The configurable content are 3D objects, movies and {{UBIK}} objects. Currently this feature is enabled for ID Markers and Markerless scanning, meaning image tracking.
Therefore, every time the user has scanned an ID marker or a picture, the corresponding object (3D object, movie or {{UBIK}} object) will be processed and, according to the configuration, displayed on the screen.

== Setup ==
In order to be able to use the feature properly, a setup folder is required and can be found at the following link [http://wiki.augmensys.com/images/6/66/Dynamic_AR_Content_Folder_Structure.rar Folder Structure]. The setup folder contains:
# A root folder, named ''UBIK''
# The ''UBIK'' root folder contains a child folder, named ''ARConfig''
# The ''ARConfig'' contains two child folders named ''IDMarker'' and ''Markerless''
## ''IDMarker'' folder contains the resources and configuration files needed for scanning an id marker
## ''Markerless'' folder contains the resources and configuration files needed for scanning a picture
# ''IDMarker'' and ''Markerless'' folder contain a ''res'' and a ''conf'' folder
## The ''res'' folder contains all the resources to be shown, like 3D objects, videos and links to {{UBIK}} objects
## The ''conf'' folder contains all the configuration files

The following picture shows an exemplary sketch of the folder structure:
:[[File:folder_structure.png]]

== Action Mapping XML Setup ==

After the folder is configured, the next step is to validate the schema against an online validator. A solution can be found at [http://www.utilities-online.info/xsdvalidation/ Online XML Schema Validator]. The schema used to validate against can be found inside the ''UBIK'' Folder and is named ''xsd_schema_validation''.

The action mapping xml contains different actions such as GeometryAction, MovieAction and UBIKObjectAction.

* The following xml shows an example configuration:
<source lang="xml">
<TrackingActionMapping>
<GeometryAction TrackingID="1">
<GeometryResource>
<ResourcePath>pump.obj</ResourcePath>
<Scale>100</Scale>
</GeometryResource>
</GeometryAction>

<UBIKObjectAction TrackingID="2"/>
<GeometryAction TrackingID="5">
<GeometryResource>
<ResourcePath>pump.obj</ResourcePath>
<Scale>100</Scale>
<RotationDegrees>
<Z>90</Z>
</RotationDegrees>
</GeometryResource>
</GeometryAction>

<UBIKObjectAction TrackingID="6">
<UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
</UBIKObjectAction>

</TrackingActionMapping>
</source>

All Action tags must specify a Tracking id, as an attribute. The Tracking id must exist in the tracking xml.

{{Attention|If a texture is used for a geometry, the material (*.mtl file) and the texture (picture) must all exist in the same place in order for to have the 3D object displayed properly, Only the geometry has to be specified as a resource in the Action Mapping, though.}}

=== GeometryAction Tag ===

Inside the ''GeometryAction'' tag there can be a GeometryResource tag that defines the type of resource required for the GeometryAction.

==== GeometryResource Tag ====

The GeometryResource contains:
# '''Resource path''': the resource path of the 3D object or video to be displayed.
# '''Scale''': if specified, the 3D object will be scaled to this size.
# '''OffsetMillimeters''': if specified, this value will be added to the position of the detected marker when displaying the 3D object. The offset can be defined along the X, Y and Z axis.
# '''RotationDegrees'''. if specified, the 3D object will be rotated by this value against the detected marker.

* ''Resource path example''. pump/pump.obj.

* ''OffsetMillimeters example''.
<source lang="xml">
<OffsetMillimeter>
<X>10</X>
</OffsetMillimeter>
</source>

=== MovieAction Tag ===

Inside the ''MovieAction'' tag there can be two possible resources defined, a MovieResource and a PlayButton resource.

==== MovieResource ====

The ''MovieResource'' Tag contains the same values as the ''GeometryResource'' except the rotation vector.

==== PlayButton Tag ====

The ''PlayButton'' Tag, if it is defined, contains the same values as the ''GeometryResource'' tag. Its purpose is to start a video, if the geometry is touched.

=== UBIKObjectAction Tag ===

The ''UBIKObjectAction'' tag should enable handling of the {{UBIK}} objects when scanning either a picture or an id marker. The tag must contain the tracking id attribute and, optional, the ubik-uid tag.
## Example. When configuring a tag without the ubik-uid tag the object is searched based on its MarkerID property which is the value inside TrackingID attribute. If the ubik-uid tag exists the object is searched based on the value inside the ubik-uid tag.
== Tracking Data XML ==

The first step is to configure the tracking data xml in order for {{UBIK}} to recognize scanned pictures and id's.
In case the marker is a picture (image), the location of the pictures must also be provided. In the example it's ../res/pic_name.(png, jpeg).
The id located in the tracking data xml should be the same as the order of the id in the list of ids.

* This example below the configuration of the location of the image:
<source lang="xml">
<SensorCOS>
<SensorCOSID>1</SensorCosID>
<Parameters>
<referenceImage widthMM="420" heightMM="297">../res/img_pic.png</referenceImage>
</Parameters>
</SensorCOS>
</source>

== '''Usage''' ==
In order to use the previously configured xmls, you can use either the ID Marker activity or the Markerless activity on the {{UBIK}} Android Client.

=== ID Marker Activity ===

Having in mind the setup tracking ids, you can now scan id markers.
* For an id that has a 3D object mapped in the action xml, the object should be displayed on the screen as shown in the next picture.
* If the id has a video object mapped in the action xml, you should see a video object on the screen, depending on the existence of the play button.
* If the play button exist you should see first see the play button, and after it's clicked the mapped video. If the play button doesn't exist, the movie will be shown immediately.

=== Markerless Activity ===

The scenario is very similar with the id marker activity with the only difference that instead of ids you have to scan your tracking images.

=== Examples ===

With the existent configuration from the zip file, you should see the following picture when scanning the first id or the first picture:
:[[File:scanning_id1.png]] 

When scanning the second id or the second picture, you should see the following:
:[[File:scanning_id2.png]] 

When scanning the sixth id, using the Markerless activity, you should see a play button and, if pressed, a movie.
* Play button:
:[[File:scanning_id3_play_button.png]] 
* Movie:
:[[File:scanning_id3_movie.png]] 

When scanning the sixth id using the IdMarker Activity you should see a play button also and, if pressed, a movie too.
* Play button:
:[[File:scanning_id6_play_button.png]] 
* Movie:
:[[File:scanning_id6_movie.png]] 

[[Category:How-To]]
[[Category:UBIK Client]]