I could not understand anyway, why Android example can recognize only one VuMark.
What is wrong with other VuMarks on Vuforia site?
Or is it some strange Android example behaviour?
It's a pitty, that there are no examples.
It will take too much efforts to create my own.

I could not understand anyway, why Android example can recognize only one VuMark.
What is wrong with other VuMarks on Vuforia site?
Or is it some strange Android example behaviour?
It's a pitty, that there are no examples.
It will take too much efforts to create my own.

Apologies upfront if I tell you the blood obvious:

The VuMark you refer to is a single instance of hundreds of VuMarks that you could generate if you had access to either its generator on the Target Manager on the Vuforia website or if you had the original Adobe Illustrator file. I don't think Vuforia provides either. You could experiment with the 'MortonTuxedos' and 'Chateau' examples in VuMark-Designer-6.0.112 which include the Illustrator files.

Did you have a look at the VuMarkHandler script which is attached to the VuMarkManager object in Unity? If you look at the last part of UpdateClosestTarget() you can see that the "String" refers to the datatype of the VuMark, that 0 is the data encoded in the VuMark (perhaps next time they can think of something slightly more inspiring and intuitive to encode in a  string than an integer) and that the VuMark icon is copied from the VuMark that the camera sees.

Your currentVumarkIdOnCard.length=8 suggests that the encoded string is 8 characters long.

currentVumarkIdOnCard=0АЂАЂАЂАЂАЂАЂАЂ suggests that the first character is 0 and the rest is probably just "\0" string terminators.