LiveCode Forums.

Hello.

It took me nearly 2 weeks, full-time, to finally make LiveCode work, a 'Hello' app, on a Android 2.2 emulator. I turned off the computer. The next day, I ran SDK Manager to make sure that I have updated everything. Then I tried to run that same 'Hello' app, and the screen of the emulator remained blank: the simple app simple doesn't work anymore on the emulator. Yet, when I copy the entire Android SDK folder into another laptop that has Livecode too, it works! It's the SAME SDK content!!

Using AVG Manager, I created an emulator for Android 4.0 (which is loaded thanks to the SDK Manager). That emulator doesn't show the 'Hello' message either. I don't get any error: it just stays black. I created a Android 3.1 emulator, and it's worse: I get an error.

Also, I was told to wait a few minutes for the app to load into the Android emulator. How long do I wait?

I'm lost for words. How an extremely app can work on an emulator one day, and not the next?

Any idea someone? I find the integration of Android with Livecode very flacky, not reliable. I have a friend who uses LiveCode with iOS without an issue at all. The trouble seems to be with Android only.

Finally, once I have an Android app working the emulator, how do I transfer it into an actual physical Android tablet? I haven't seem any info on the Internet about that necessary step.

Hello.

Out of desperation, I tried to run the 'Hello' app one last time, and it worked beautifully this time!! I didn't even have to wait more than 30 seconds. All the times I tried before, I'd wait 30 minutes for that black emulator to show my app to no avail. Don't you have a sense that there are bugs in either Android or LiveCode?

this seems to be a known issue

what's alarming is it STILL exists

Anyway, for those that missed it;

livecode 5.51
android 2.2

In the android VDM manager, when you create your virtual device, MANUALLY add the following and set them to "NO";
1) accelerometer
2) magnetic field support
3) orientation support

Obviously it means, these features can not work either!

Having spend 16 TENSE hours looking at blank black screen apps, except occasionally, this now lets them emulate faultlessly.

What I don't understand is why this was SO hard to find out and why it still exists.
Perhaps someone can enlighten me?

Peter

[SEARCH TAGS - hello world on android, android balck screen, intermittent app emulation ]

I was getting the same thing only I never thought to wait that long. I just thought any AVD under 2.3 didn't work at all. One of the engineers debugged it for me at the RevLive conference. There's an incompatibilty somewhere that conflicts with sensors on early versions of the Android OS; he didn't know if the problem was in the emulator or in LiveCode. Turning off sensors fixes it. The emulator doesn't support sensors anyway, so turning them off doesn't deprive your app of anything.