Trouble with Android

Michael Hatch hatchfactory at gmail.com
Fri Mar 15 15:41:52 CDT 2013


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.

Kind Regards,
Michael Hatch


On Fri, Mar 15, 2013 at 1:08 PM, Ben Rubinstein <benr_mc at cogapp.com> wrote:

> Hmm... attempting to do some very simple trial stacks on Android, after
> not having done any for a long time - having fought my way through a few
> strangeness with regards to expired debug certificates and the like, I now
> find that all my stacks - built with 5.5.3 or above - simply display black,
> on two different test devices.
>
> An older version of one of the stacks, an APK I happen to have lying
> around my hard drive that was built about 14 months ago, can be
> re-installed and works fine.
>
> Do I need to re-install the Android SDK if I haven't done so for over a
> year?  Or is there some other obvious thing that someone can tell me I'm
> doing wrong?
>
> Many thanks,
>
> Ben
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>


More information about the use-livecode mailing list