Log in or register to post comments

Crash on init with Samsung Galaxy S7

July 17, 2016 - 9:17pm #1

Hi,

I have an app that has been working on several Android devices for quite some time.

However, when I have tried running it on a new Samsung Galaxy S7 (Android 6.01), it crashes at the beginning on QCAR.setInitParameters. Seems like it doesn't find the lib or something like that - is it a 64 bit issue?

The error:

Uncaught Exception: java.lang.UnsatisfiedLinkError: No implementation found for void com.qualcomm.QCAR.QCAR.onResume() (tried Java_com_qualcomm_QCAR_QCAR_onResume and Java_com_qualcomm_QCAR_QCAR_onResume__)

Any idea how to fix this?

 

Thanks,

yakobom

Crash on init with Samsung Galaxy S7

July 20, 2016 - 1:45am #10

Thank you. Still, the same code works on other devices and not on the Samsung S7, and the exception is on the vuforia jar. Any ideas on what could be the problem?

Crash on init with Samsung Galaxy S7

July 19, 2016 - 5:43pm #9

Hello,

32-bit applications that are built with the Vuforia SDK are compatible with the Samsung Galaxy S7.

Thanks.

Crash on init with Samsung Galaxy S7

July 19, 2016 - 7:37am #8

Hi,

Just so give some more details, The error I have mentioned is thrown later, before that I had a similar one that was caught:

No implementation found for void com.qualcomm.QCAR.QCAR.privateSetInitParameters(android.app.Activity, int, java.lang.String) (tried Java_com_qualcomm_QCAR_QCAR_privateSetInitParameters and Java_com_qualcomm_QCAR_QCAR_privateSetInitParameters__Landroid_app_Activity_2ILjava_lang_String_2)

 

Anyone?

Crash on init with Samsung Galaxy S7

July 18, 2016 - 9:05pm #7

Hi,

The application is not 64-bit - it is a 32-bit application that runs on many other devices. Are you saying that Vuforia cannot run on Samsung Galaxy S7?

Crash on init with Samsung Galaxy S7

July 18, 2016 - 2:16pm #6

Hello,

Vuforia currently does not support 64-bit Android applications.

Thanks

Crash on init with Samsung Galaxy S7

July 18, 2016 - 7:08am #5

Hi,

I have just checked it, in order to be certain - this is not the issue. Also, it does not make sense that a lack of permission would cause an UnsatisfiedLinkError exception...

Crash on init with Samsung Galaxy S7

July 18, 2016 - 4:51am #4

Could it be that your app doesn't have the permission the access the camera?

Since Android 6 you have to specifically ask for it in your app.

Crash on init with Samsung Galaxy S7

July 17, 2016 - 11:53pm #3

Thanks sandy4990, but I already have the android:largeHeap="true" definition in my manifest file... Any other ideas?

Crash on init with Samsung Galaxy S7

July 17, 2016 - 10:23pm #2

try adding - android:largeHeap="true" - in application tag of your AndroidManifest.xml file.

Log in or register to post comments