Problem running Android build

Getting Started Newbie Questions
#1

Since going to 2011.484 Windows/Android I have not been able to get an app to load and run in the Android Emulator. In the previous version I could. I am using an Android 2.3 emulator, (2.2 will not load the APK.) and when I try to run, it gets upset about openal lib. (logcat below) There is a lib\armeabi-v7a\libopenal.so in the apk file.

I am using a very small program that worked before. Is anyone else having any issues?

Thank you

ANDROID 2.3:

I/ActivityManager( 64): Start proc com.dad.min for activity com.dad.min/.MyCoronaActivity: pid=321 uid=10034 gids={300
3}
I/ARMAssembler( 64): generated scanline__00000177:03515104_00001002_00000000 [87 ipp] (110 ins) at [0x46077848:0x4607
7a00] in 13223891 ns
W/dalvikvm( 321): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/ansca/corona/CoronaActivity
;
W/dalvikvm( 321): Class init failed in newInstance call (Lcom/dad/min/MyCoronaActivity;)
D/AndroidRuntime( 321): Shutting down VM
W/dalvikvm( 321): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime( 321): FATAL EXCEPTION: main
E/AndroidRuntime( 321): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 321): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 321): at java.lang.Class.newInstance(Class.java:1409)
E/AndroidRuntime( 321): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime( 321): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1536)
E/AndroidRuntime( 321): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1638)
E/AndroidRuntime( 321): at android.app.ActivityThread.access$1500(ActivityThread.java:117)
E/AndroidRuntime( 321): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:928)
E/AndroidRuntime( 321): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 321): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 321): at android.app.ActivityThread.main(ActivityThread.java:3647)
E/AndroidRuntime( 321): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 321): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 321): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
E/AndroidRuntime( 321): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/AndroidRuntime( 321): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 321): Caused by: java.lang.UnsatisfiedLinkError: Couldn’t load openal: findLibrary returned null
E/AndroidRuntime( 321): at java.lang.Runtime.loadLibrary(Runtime.java:429)
E/AndroidRuntime( 321): at java.lang.System.loadLibrary(System.java:554)
E/AndroidRuntime( 321): at com.ansca.corona.CoronaActivity.(Unknown Source)
E/AndroidRuntime( 321): … 15 more
W/ActivityManager( 64): Force finishing activity com.dad.min/.MyCoronaActivity
W/ActivityManager( 64): Activity pause timeout for HistoryRecord{40668f30 com.dad.min/.MyCoronaActivity}
W/ActivityManager( 64): Activity destroy timeout for HistoryRecord{40668f30 com.dad.min/.MyCoronaActivity}
[import]uid: 41667 topic_id: 9784 reply_id: 309784[/import]

#2

Well, I picked up a Droid, and am able to run builds from the current Corona version. So whatever is going on above, is about the emulator. At least now I can run things. [import]uid: 41667 topic_id: 9784 reply_id: 36476[/import]

#3

Same problem with Android Emulator [import]uid: 53514 topic_id: 9784 reply_id: 37212[/import]

#4

Since build 484, Corona SDK builds for arm7.

Android emulator currently does not support arm7 and causing the error. [import]uid: 10478 topic_id: 9784 reply_id: 37215[/import]

#5

Thanks [import]uid: 53514 topic_id: 9784 reply_id: 37219[/import]

#6

I am having this same output in adb logcat, or at least close enough to it being OpenAL not initialized. However I am not using the emulator - I was using two different devices.

Colby Kyros Tablet and someones phone from the office. After searching, I found the Colby tablet is using an ARM 11** processor, so I guess this is the issue?

How much of the Android market is Corona missing? Or rather, how much are they actually hitting? It would not be cool to make an app that fails on people when they buy and download it.

**Which is actually ARMv6 according to wiki. How confusing do they have to be… So I now have to assume that Colby Kyros Tablet cannot support the Android applications made with the Corona SDK. Is there any official word on supporting these/more devices? [import]uid: 143067 topic_id: 9784 reply_id: 102297[/import]

#7

Hey tbimpakt,

We have several threads discussing why we stopped supporting ARMv6 - lower end Android devices have a lot of issues with performance, that’s a big part of it - but read the threads, you’ll see all the reasoning laid out.

Google will show what devices an app is compatible with which should help with your other concern.

Peach :slight_smile: [import]uid: 52491 topic_id: 9784 reply_id: 102394[/import]