-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lyra_android_example.apk crashed. #147
Comments
@TangYuFan Hi, I also encountered this problem, have you solved this yet? I tried upgrade the version of sdk, but the compiling process failed, only version 30 can build successfully. Besides, is this apk can be adapted to android 15? Thank you so much. |
@TangYuFan Hi, thanks, I found this line in DenseStorge.h, should I comment out this line, can you tell me how do you solve this? By the way, I found that the app didn't crash after I commented out the encode and decode methods in jni_lyra_benchmark_lib.cpp. Can we use email to discuss it, i struggle with this problem for weeks, my email is [email protected], thanks a million. |
My colleague found through GDB debugging that it is hanging on this destructor. Sorry, I don't know the specific modifications. My algorithm colleague fixed the problem and directly provided me with the .so dynamic library file. |
We're trying to implement the encode and decode method separately using the .so dynamic library file, can you share it? Really appreciate your help. |
Hello, the Android example compiled according to the readme file runs well on some phones and crashes on some phones。
The compilation script I tried:
(1) bazel build -c opt lyra/android_example:lyra_android_example --config=android_arm64 --copt=-DBENCHMARK
(2) bazel build -c opt lyra/android_example:lyra_android_example --fat_apk_cpu=armeabi-v7a,arm64-v8a --copt=-DBENCHMARK
Running apk on some phones has crashed. The following is the error log:
May I ask how to solve the above problems? Is compiling a script requiring special instructions? Because I use encoding and decoding interfaces to package it into SO for Android phones, some phones may not run properly。
The text was updated successfully, but these errors were encountered: