the attachment has an Android.mk, so it will produce a binary called "broken_fences" when compiled from within an android build tree.
Pushing that binary to the device, just run the binary with ./broken_fences while surfaceflinger is running. It will print out "FAILURE" and have a program exit code of -1 on devices that don't have functioning sync.
the attachment has an Android.mk, so it will produce a binary called "broken_fences" when compiled from within an android build tree.
Pushing that binary to the device, just run the binary with ./broken_fences while surfaceflinger is running. It will print out "FAILURE" and have a program exit code of -1 on devices that don't have functioning sync.