Hi Leo,
the artifacts I mentioned above are also visible when displaying a local stored html page in the browser and performing horizontal scrolling actions. In this case no VPU is involved.
I have attached two links to this entry. The first link shows a short video with the mentioned tearing artifacts. The second link includes the html package I used on the SABRE board to record the video.
1. https://www.dropbox.com/s/2kv0mnj1vhcsaow/Tearing.MOV
2. https://www.dropbox.com/s/f47mzhsp6md8pgz/public_html_swiper_lib_eval.7z
Installing the public_html_swiper_lib_eval package:
1. Uncompress the public_html_swiper_lib_eval.7z file
2. copy the public_html_swiper_lib_eval folder in the root directory of the SABRE board
3. start the shell script /public_html_swiper_lib_eval/start.sh on the SABRE board
As result of the start.sh script, a Chrome instance is launched and the file:///public_html_swiper_lib_eval/layout.html URL is displayed inside the browser. The page can be scrolled horizontally by using swiping gestures or with a mouse attached to the USB OTG connector of the SABRE Dual Lite board. The tearing artifacts are immediately visible.
As alternative the public_html_swiper_lib_eval can be exposed through a Web server to the browser running on the SABRE board.
I rather assume the behaviour is related to the fact that the display content is updated during v-sync.
Also attached a third link, showing the behaviour on an Android 4.2.2 image running on the same SABRE Dual Lite board https://www.dropbox.com/s/e0n4kptjehigmt8/No_Tearing_Android_4.2.2.MOV , where no screen tearing artifacts are visible.
Kind regards,
Gabriel.
