retrodude - is that happening in Chrome for Android or the stock browser? The stock browser sucks really bad and it would not surprise me if that was a glitch in the browser itself. It doesn't sound like the kind of thing that we can easily work around.
It's only for stock browser. Chrome runs fine, same with firefox. The issue is that large publishers like spilgames still require you to have games working on native stock browser for older devices like the S3. And yea it blows since stock browser is so buggy it's annoying. The R168 version of construct has the exported file working fine on stock browser. I think for publishing it might be best to currently use this version.
There were some drastic changes in the two new updates so it's hard to tell what could be causing it.
Here's a link to a odd work around:
http://stackoverflow.com/questions/1827 ... -in-chrome
This portion here causes an odd flickering with values at 0.99, so changing it to 0.999999 opacity is kind of a temporary fix. I'll see if I can place a temporary fix in the manual section. But I recommend just downgrading to R168 for anyone that is doing sponsorship and publishing since its quite stable and doesn't have this issue.