Dan has it right. Trying to target hardware aspects of specific systems in an effort to prevent execution on non-sanctioned machines can't be terribly effective in that there are literally hundreds of systems and they are all remarkably similar. I'm guessing, that it would take a tremendous amount of work to use this to differentiate systems.

IMO, a far better scheme would be to impose artificial boundaries, for example a sophisticated system specific encrypted identity or simply exploiting a devices identity file -- ala the data in the prop file.

I suspect that this is an NDK application, and that they're using something like ARM NEON extensions for decoding of DRM and parsing of video which would be off limits to Dalvik. Still, if they are using the NDK, it would be much more difficult to support multiple systems as testing would have to be done on each individually -- which is likely why only a handful of system are officially 'supported'.

I would have tried to find a creative way to use Dalvik to lower the cost of support and testing substantially. For example, use fragment shaders to decode the DRM'd video quickly and efficiently in the GPU. I'm sure other solutions exist, but they would require a bit of creativity, which may be too much to ask.