NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.
... e corruption (you'll recognize my description when you see it), set "render quality" under settings to "quality" instead of "performance".
This appears to be a bug in Jelly Bean itself, exact cause unknown (will submit official bug report soon). Setting "render quality" to "quality" is a temporary workaround.
I will release an update to DSLR Controller which will remove the image corruption in "performance" mode as well mid-August. I already have the fix but there is not enough time to do a test and release cycle before I leave on vacation (in a few hours).
In case you came here by Google-ing because you have the exact same problem in your app, at this point, the problem seems to only happen if your image width is not a multiple of four bytes. If you are using ARGB_8888 (32bpp) images this will always be the case, but if you are using RGB_565 (16bpp) images this will only be the case if the image width is an even number. Note that the corruption does not always show up, but it can show up under these conditions. I have not seen the problem happen when ensuring my RGB_565 images were an even width, and without that it happens constantly.
Great to know! Thanks for a great product!
Now if only +HTC actually could allow USB OTG/USB Host mode on the HOX I could use my phone instead of the Asus Transformer.. ;-)
Typical +HTC, always two years behind on the competition.
Yup... :( It pretty much sucks and there's absolutely now reason for it either.. I've actually escalated this with +HTC to let them know I'm not able to use you wonderful software with their products.. but of course as usual nothing will happen except me switching to another brand.
2 years behind the competition and I am still 8 month under the contract..... Seems to me I lost 30 month.... :-[