After our latest answer, in which we proposed running the sample with the -e option, there was no response. So we had to assume that the problem was resolved -- maybe by using a different driver. Also, you mention APP SDK 2.8. APP SDK 2.9 was released last year -- maybe the issue no longer exists.
We cannot know until you tell us.
Can you let us know the specifics -- the APP SDK version, the driver version, and details about the problem (if different from the above)? We will try to reproduce it at our end.
