Trouble with Android

Ben Rubinstein benr_mc at
Mon Mar 18 17:19:12 EDT 2013

On 15/03/2013 20:41, Michael Hatch wrote:
 > I have found that in android setting the acceleratedrendering of a stack in
 > preopenstack will sometimes cause black screens and other unwanted effects,
 > so I now set it via opencard of the first card. Setting the compositor to
 > software or disabling acceleratedrendering might be a good starting point
 > to check while debugging.

On 16/03/2013 05:13, J. Landman Gay wrote:
> As mentioned, using acceleratedRendering on an Android device running OS 2.2
> or earlier will launch to a black screen if you use the defaults. If you set
> the compositorType to "software" it works, but I got some unwanted artifacts
> when I did that. As far as I know it hasn't been fixed yet, so I had to
> require Android 2.3 or higher.
> Another thing is incompatibility with 4.1 Jelly Bean. I had to rebuild with
> 5.5.4 to fix that. Earlier versions of LiveCode apps opened to a black screen
> on Jelly Bean.

Thanks both, but it doesn't seem to be either of those.  I've never used 
acceleratedRendering, I haven't got that far yet! (and after a careful search 
have confirmed that no trace of it has crept into my stack).  One of my test 
devices is Android 2.3.4, the other is 4.0.3, but same result on both, 
including when building from LC 5.5.4.

I did have some success when, in despair, I opened took the "Orientation 
Example" stack and was able to build that succesfully so that it opened on 
Android.  Then I copied all the elements of my stack into it - and it still 
worked.  So now I have two apparently identical stacks - both one card, the 
same controls on each, the same scripts in the card and the stack - but one 
has developed Android-black-screen disease.  I've not yet found the critical 
difference between them.

So I'm thinking that I've stumbled across another way to cause 
Android-black-screen, which isn't either of the ones you've mentioned (and 
which happens with the latest test version of LC as well as earlier ones).  If 
anyone knows of any other causes, which I can test to see if that's what's 
going on here, please let me know.  Otherwise (when I've got some time on my 
hands) I'll try to keep cutting down the problem stack to form a minimal 
version I can report to RunRev.

Many thanks,


More information about the Use-livecode mailing list