I am experiencing problems in order to see in Logcat the information related with the debug of my applications.
I never had that problem before, but when I recently purchased a Huawei Y300-0100 for developing I faced that issue. This problem doesn't appear using other devices.
A snapshot of the LogCat:
11-08 01:32:24.960: E/Trace(24713): error opening trace file: No such file or directory (2)
11-08 01:04:53.290: W/dalvikvm(23882): Refusing to reopen boot DEX '/system/framework/hwframework.jar'
11-08 01:04:55.570: I/Adreno200-EGL(23882): <qeglDrvAPI_eglInitialize:299>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_REL_2.0.3.04.01.01.21.010_msm8625_JB_REL_2.0.3_Merge_release_AU (Merge)
11-08 01:04:55.570: I/Adreno200-EGL(23882): Build Date: 10/26/12 Fri
11-08 01:04:55.570: I/Adreno200-EGL(23882): Local Branch:
11-08 01:04:55.570: I/Adreno200-EGL(23882): Remote Branch: quic/jb_rel_2.0.3
11-08 01:04:55.570: I/Adreno200-EGL(23882): Local Patches: NONE
I tryied to find a solution but I have not been able to figure out what's wrong and how can I fix that.
Anybody has this smartphone and is not having issues? I would appretiate any comment.
Thank you.
Ok, after a long search on the web I finally encountered [that answer][1]: Huawei Ideos - LogCat not responding . Following the same instruction now I can see the debug messages like:
Log.d("hello","that's a probe")
On logcat, the "error opening trace file: No such file or directory (2)" has not disappeared.
Do you use the NDK library .so files in the application,I confront the same problem,I solve this problem just by fix the name of the library,Maybe that your application could not find the .so libarary.Hope it give some ideas.
Related
I got this error when I deploy my Android APK onto a device. The same error is reported by the Google Play Pre-launch report:
11-03 16:50:34.845: W/NativeLibraryUtils(14918): Unable to load native
code from existing library
/data/app/com.google.android.gms-1/lib/arm/libgmscore.so
11-03 16:50:34.845: W/NativeLibraryUtils(14918):
java.lang.UnsatisfiedLinkError: dlopen failed:
"/data/app/com.google.android.gms-1/lib/arm/libgmscore.so" is 32-bit
instead of 64-bit
11-03 16:50:34.845: W/NativeLibraryUtils(14918): at
java.lang.Runtime.load0(Runtime.java:908)
11-03 16:50:34.845:
W/NativeLibraryUtils(14918): at
java.lang.System.load(System.java:1505)
11-03 16:50:34.845:
W/NativeLibraryUtils(14918): at
mpy.b(:com.google.android.gms#11509430:9)
11-03 16:50:34.845:
W/NativeLibraryUtils(14918): at
com.google.android.gms.common.security.ProviderInstallerImpl.a(:com.google.android.gms#11509430:1)
...
There are some others with the same problem, but they are often related to Swift Android development. For instance, a similar (the same?) issue has been reported here: “dlopen failed: is 32-bit instead of 64-bit” in tests only. I am on Xamarin. The error makes no sense to me nor does anything related to what I am reading.
I tried all sorts of solutions such as, but not limited to:
different linker options (None, SDK only etc.)
recompile of all custom assemblies
clean builds, forced NuGet package download etc.
different supported ABI settings
If I run the code in debug mode on my emulator, everything is fine. The version built in release mode via VSTS and deployed onto Google Play doesn't work.
Any tip, hint and wild guess will be appreciated.
Today we got a strange crash. During the first installation the app downloads and unzips openh264 to the internal directory of the app, happens on a Schedulers.io() thread from rxAndroid.
This is the first crash of this kind (>5k installations) and I found this link (very interesting blog by the way) with a matching error message. I'm not sure if really someone tried to replace the openH264 lib or if someone tried to install the apk file on a x86 device. I'm still using 1.4 of openH264 and have read the 1.5 release notes. There is no hint of security fixes.
Some more details about the device:
Android: 4.3
Manufacturer: Samsung
Model: GT-I9300
And finally, here is the crash log:
java.lang.IllegalStateException: Fatal Exception thrown on Scheduler.Worker thread.
at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:62)
at android.os.Handler.handleCallback(Handler.java:730)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:176)
at android.app.ActivityThread.main(ActivityThread.java:5419)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/path/files/libopenh264.so" has bad ELF magic
at java.lang.Runtime.load(Runtime.java:330)
at java.lang.System.load(System.java:511)
at path.BeatMarker.init(BeatMarker.java:33)
at path.fragments.main.MainFragment.onOpenH264Done(MainFragment.java:475)
at path.fragments.main.MainPresenterImpl.onOpenH264Done(MainPresenterImpl.java:25)
at path.fragments.main.MainLoaderImpl$1.onCompleted(MainLoaderImpl.java:61)
at rx.observers.SafeSubscriber.onCompleted(SafeSubscriber.java:81)
at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.pollQueue(OperatorObserveOn.java:201)
at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber$2.call(OperatorObserveOn.java:170)
at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
... 9 more
I'm pretty sure, the crash happens here:
at path.BeatMarker.init(BeatMarker.java:33)
These are the lines:
File libOpenH264File = new File(context.getFilesDir(), "libopenh264.so");
System.load(libOpenH264File.getAbsolutePath()); //line 33
Gets called, when the download and unzip is completed.
Can the error occur, while the lib is downloading and the network connection get lost?
Any help or hint is welcome, thanks in advance! :)
I'm trying to render a model in libgdx - everything runs perfectly on the desktop, but on android force stop on modelBatch.render(poleInstance, environment);
Log:
03-30 16:37:40.317 5249-5249/? E/cutils-trace﹕ Error opening trace file: No such file or directory (2)
03-30 16:37:42.621 5269-5269/? E/cutils-trace﹕ Error opening trace file: No such file or directory (2)
03-30 16:37:46.181 5283-5283/com.badlogic.gdx.tests E/OpenGLRenderer﹕ Getting MAX_TEXTURE_SIZE from GradienCache
03-30 16:37:46.209 5283-5283/com.badlogic.gdx.tests E/OpenGLRenderer﹕ Getting MAX_TEXTURE_SIZE from Caches::initConstraints()
03-30 16:37:46.533 5283-5297/com.badlogic.gdx.tests E/EGL_genymotion﹕ [getAttribValue] Bad attribute idx
03-30 16:37:46.533 5283-5297/com.badlogic.gdx.tests E/EGL_genymotion﹕ tid 5297: eglGetConfigAttrib(605): error 0x3004 (EGL_BAD_ATTRIBUTE)
03-30 16:37:46.533 5283-5297/com.badlogic.gdx.tests E/EGL_genymotion﹕ [getAttribValue] Bad attribute idx
03-30 16:37:46.533 5283-5297/com.badlogic.gdx.tests E/EGL_genymotion﹕ tid 5297: eglGetConfigAttrib(605): error 0x3004 (EGL_BAD_ATTRIBUTE)
03-30 16:37:46.825 5283-5297/com.badlogic.gdx.tests E/AndroidRuntime﹕ FATAL EXCEPTION: GLThread 168
com.badlogic.gdx.utils.GdxRuntimeException: File not found: com/badlogic/gdx/graphics/g3d/shaders/default.vertex.glsl (Classpath)
at com.badlogic.gdx.files.FileHandle.read(FileHandle.java:134)
at com.badlogic.gdx.backends.android.AndroidFileHandle.read(AndroidFileHandle.java:78)
at com.badlogic.gdx.files.FileHandle.length(FileHandle.java:548)
at com.badlogic.gdx.backends.android.AndroidFileHandle.length(AndroidFileHandle.java:167)
at com.badlogic.gdx.files.FileHandle.estimateLength(FileHandle.java:229)
at com.badlogic.gdx.files.FileHandle.readString(FileHandle.java:194)
at com.badlogic.gdx.files.FileHandle.readString(FileHandle.java:187)
at com.badlogic.gdx.graphics.g3d.shaders.DefaultShader.getDefaultVertexShader(DefaultShader.java:409)
at com.badlogic.gdx.graphics.g3d.shaders.DefaultShader.<init>(DefaultShader.java:504)
at com.badlogic.gdx.graphics.g3d.shaders.DefaultShader.<init>(DefaultShader.java:500)
at com.badlogic.gdx.graphics.g3d.utils.DefaultShaderProvider.createShader(DefaultShaderProvider.java:46)
at com.badlogic.gdx.graphics.g3d.utils.BaseShaderProvider.getShader(BaseShaderProvider.java:34)
at com.badlogic.gdx.graphics.g3d.ModelBatch.render(ModelBatch.java:269)
at com.badlogic.gdx.tests.PathTest.render(PathTest.java:221)
at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:391)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1523)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1240)
03-30 16:37:51.401 5283-5283/com.badlogic.gdx.tests E/AndroidGraphics﹕ waiting for pause synchronization took too long; assuming deadlock and killing
03-30 16:37:51.521 475-517/system_process E/InputDispatcher﹕ channel '528ce2b4 com.badlogic.gdx.tests/com.badlogic.gdx.tests.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
Yes, my question is similar to this, but updating the library didn't helped
And yes, file com/badlogic/gdx/graphics/g3d/shaders/default.vertex.glsl in place
My code place here
The error is File not found, so apparently it cannot find the file. If you are sure the file is included, this might be caused by duplicate references (although it doesn't have to). For example if you include (and export) the gdx library in both your core and android project. You could check this by right clicking each project, click on Java Build Path and then the Order and Export tab. Make sure that the gdx project (or jar, depending if you work from source or nightly/stable) is only included (and exported by clicking the checkbox) in the core project.
However, having assets (which the shader files are) on the classpath is merely to support out-of-box rendering for libgdx. In your case would advise to copy the shader files to (a subfolder of) your assets folder and use those instead. That makes managing your assets a lot cleaner. You can load the shaders using the constructor of ModelBatch, e.g.:
modelbatch = new ModelBatch(Gdx.files.internal("data/default.vertex.glsl"), Gdx.files.internal("data/default.fragment.glsl"));
Of course, you still might want to double check your project configuration.
Please install Arm Transition on your Genymotion Emulator
Here is a detailed guide on How to install this transition :
How to install Google Play Services in a Genymotion VM (with no drag and drop support)?
I hope this helps.
I installed my application and the application is running well already.
But after sometime, the app can't be opened and the error is "error opening trace file: No such file or directory". What could be the problem?
I installed the same app to Samsung Note2 with Android version 4.1.2. I don't have any problem.
I installed to another device with Android version 4.1.1, and that device has problem.
My LogCat message is as shown below.
10-07 20:51:50.910: W/System.err(19785): Invalid int: ""
10-07 20:51:51.140: W/dalvikvm(19785): threadid=1: thread exiting with uncaught exception (group=0x40e97438)
10-07 20:52:09.510: E/Trace(19817): error opening trace file: No such file or directory (2)
10-07 20:52:09.530: W/dalvikvm(19817): Refusing to reopen boot DEX '/system/framework/hwframework.jar'
10-07 20:52:09.750: W/System.err(19817): Invalid int: ""
10-07 20:52:09.910: I/Adreno200-EGL(19817): <qeglDrvAPI_eglInitialize:299>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_REL_2.0.3.04.01.01.21.010_msm8625_JB_REL_2.0.3_Merge_release_AU (Merge)
10-07 20:52:09.910: I/Adreno200-EGL(19817): Build Date: 10/26/12 Fri
10-07 20:52:09.910: I/Adreno200-EGL(19817): Local Branch:
10-07 20:52:09.910: I/Adreno200-EGL(19817): Remote Branch: quic/jb_rel_2.0.3
10-07 20:52:09.910: I/Adreno200-EGL(19817): Local Patches: NONE
10-07 20:52:09.910: I/Adreno200-EGL(19817): Reconstruct Branch: AU_LINUX_ANDROID_JB_REL_2.0.3.04.01.01.21.010 + NOTHING
10-07 20:52:09.970: W/dalvikvm(19817): threadid=1: thread exiting with uncaught exception (group=0x40e97438)
The "error opening trace file" message is a red herring -- it just means your device doesn't support systrace.
The "Invalid int" message might have something to do with the problem, but really what's happening is something is throwing an exception that isn't caught.
Normally when a thread exits with an uncaught exception you get to see the exception in the log, but something seems to be preventing that here. If you run the app in the debugger, and set an exception breakpoint on all uncaught exceptions, you should be able to see where it's coming from. (Alternatively, try to track down the source of the "Invalid int" message and put a breakpoint there.)
Upgrading to ndk 8b I receiving some crash report (most of them are Galaxy SII with Android 4.03)
java.lang.UnsatisfiedLinkError: Cannot load library: reloc_library[1286]: 1836 cannot locate '__gnu_thumb1_case_uqi'...
at java.lang.Runtime.loadLibrary(Runtime.java:370)
at java.lang.System.loadLibrary(System.java:535)
at com.iuculano.fplayer.SDLActivity.void onCreate(android.os.Bundle)(SourceFile:324)
at android.app.Activity.performCreate(Activity.java:4465)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1052)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1932)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1993)
at android.app.ActivityThread.access$600(ActivityThread.java:127)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1159)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4507)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
at dalvik.system.NativeStart.main(Native Method)
The exception is caused by a simple System.loadLibrary("main");
What does it mean? cannot locate '__gnu_thumb1_case_uqi'
The __gnu_thumb1_case_uqi is a helper which does an indexed jump on a densely packed switch table; quickly implements the switch. You have two options: avoid it or link with it.
If you increase an optimization level (by using -O3) you might not need this symbol. Also, changing the CPU may help as well as using thumb2 instructions. Compiling with the -ffreestanding option may also avoid this symbol. If you have control over the switch statement, you can replace it with an array of function pointers.
This routine is inside libgcc. You can statically link libgcc. Somewhere in the Android SDK/compiler, there must be a libgcc.a. Link with libgcc.a, using -L and -l or use -static-libgcc linker option to get the code (see http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html).
Edit: If you aren't compiling anything, then you can find libgcc.so on your system. It might be in /lib or /usr/lib or perhaps some place weird for Android devices. Adding the directory where the libgcc.so is located to the environment variable LD_LIBRARY_PATH could also fix the problem. It maybe unfortunate that Samsung released incompatible binaries and you have no way to fix the issue if you aren't compiling your own code. The correct libgcc.so maybe inside something like /usr/lib/thumb for multi-lib distributions. I don't know much about the Davlik stuff, but the Android JVM might not pointing to the right set of libraries when it runs.
Are you compiling for armv7? If you're not, try compiling for armv7.
Producing optimised NDK code for multiple architectures?
read about 'arm' vs 'thumb' in the accepted answer in the above link.
then, remove your config instructions to build for thumb and verify that you are building for arm...
OR...
ill make a wild guess ... its the library order you have in the linker statement in your 'Android.mk'
try the google forum for ndk ... searching for 'cannot locate symbol'...
Really desperate?
see 'Runtime errors' section here