Debazh apk works everywhere. A release apk (it doesn't matter, it was installed with googleplay, or by hand, through launching the apk itself) does not work on Meizu m2. So that you understand, the phone is normal, with normal firmware, everything works on it, except for my application. On other phones, the flight is normal. Tested on galaxy, xperia, zenfone.

"Does not work" means that when you click on the application icon you can see the second attenuation of the screen, as if something is now turned on and ... everything. Again the desktop.

It was done in RAD Studio, on Delphi (please do not say anything about it, I did not, now I have to force this monster to work, myself in shock) using FireMonkey. And yes, it is cross-platform. I compile the same code under iOS and it works.

I do not even know, to be honest, what else to add. What, in general, could be the problem? For me, it looks like some kind of magic.

Here are the logs from events_log

09-30 02:01:44.749 787 1546 I am_create_activity: [0,215441632,364,com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity,android.intent.action.MAIN,NULL,NULL,270532608] 09-30 02:01:44.749 787 1546 I wm_task_created: [364,1] 09-30 02:01:44.749 787 1546 I wm_task_moved: [364,1,9] 09-30 02:01:44.801 787 1546 I am_pause_activity: [0,750531609,com.meizu.flyme.launcher/.Launcher] 09-30 02:01:44.818 787 1546 I am_home_stack_moved: [0,0,1,1,startedActivity setFocusedActivity] 09-30 02:01:44.819 787 1546 I am_focused_activity: [0,com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity] 09-30 02:01:44.836 1512 1512 I am_on_paused_called: [0,com.meizu.flyme.launcher.Launcher] 09-30 02:01:44.871 787 1320 I am_proc_start: [0,1563,10088,com.il.GS,activity,com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity] 09-30 02:01:44.936 787 849 I am_proc_bound: [0,1563,com.il.GS] 09-30 02:01:44.940 787 849 I am_restart_activity: [0,215441632,364,com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity] 09-30 02:01:44.947 787 849 I am_focused_activity: [0,com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity] 09-30 02:01:45.077 787 1490 I am_crash: [1563,0,com.il.GS,8961604,java.lang.IllegalArgumentException,Unable to find native library: GS,NativeActivity.java,170] 09-30 02:01:45.079 787 1490 I am_finish_activity: [0,215441632,364,com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity,crashed] 09-30 02:01:45.079 787 1490 I am_home_stack_moved: [0,1,0,0,finishActivity adjustFocus] 09-30 02:01:45.079 787 1490 I wm_task_moved: [16,1,0] 09-30 02:01:45.096 787 1490 I am_home_stack_moved: [0,1,0,0,finishActivity adjustTopFocus setFocusedActivity] 09-30 02:01:45.098 787 1490 I am_focused_activity: [0,com.meizu.flyme.launcher/.Launcher] 09-30 02:01:45.112 787 1490 I am_pause_activity: [0,215441632,com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity] 09-30 02:01:45.183 787 1469 I am_proc_died: [0,1563,com.il.GS] 

It is logical to assume that the problem is here: IllegalArgumentException,Unable to find native library: GS,NativeActivity.java,170 Now I will try to google something on this issue

I found this in the main_log:

 09-30 02:01:45.076 1563 1563 E AndroidRuntime: FATAL EXCEPTION: main 09-30 02:01:45.076 1563 1563 E AndroidRuntime: Process: com.il.GS, PID: 1563 09-30 02:01:45.076 1563 1563 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity}: java.lang.IllegalArgumentException: Unable to find native library: GS 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2655) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2725) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.ActivityThread.access$800(ActivityThread.java:180) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1562) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:111) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.os.Looper.loop(Looper.java:194) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5824) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1010) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Unable to find native library: GS 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.NativeActivity.onCreate(NativeActivity.java:170) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at com.embarcadero.firemonkey.FMXNativeActivity.onCreate(FMXNativeActivity.java:139) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6107) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2608) 09-30 02:01:45.076 1563 1563 E AndroidRuntime: ... 10 more 

Gentlemen, still not figured out how to fix it. Logs say that java does not find the native library with the name of my application. What does this even mean? Why on debag-version finds? Or not looking? Why only reliznika flies? What do these entries in the logs mean in general, and what is the mysterious native libriary called GS (let's say, the application is also called). Where did she come from?

  • And in the logs, then there is something? - Yuriy SPb
  • I'm just trying to get to them now somehow, as far as I understand it, they either don’t write them at all, or they need to rutnut the phone to get to them, or I need to include something in the engineering menu so that it starts writing them. Infa a lot and all different. I have not seen logs yet. If there are any clues on this issue - I’ll be happy to hear it - Stanislav
  • > 09-30 02: 01: 46.230 787 1320 I ActivityManager: Start proc 1625: com.il.GS/u0a88 for activity com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity> 09-30 02: 01: 46.297 787 1469 W ActivityManager: Force finishing activity 1 com.il.GS/com.embarcadero.firemonkey.FMXNativeActivity> 09-30 02: 01: 46.341 787 1469 W ActivityManager: finishTopRunningActivityLocked, taskNdx is 75, activityNdx is 0> 09-30 02: 01: 46.415 787 1496 I ActivityManager: Process com.il.GS (pid 1625) has died - Stanislav
  • one
    Well, in Java when we write applications, then in the manifest, you can specify debuggable="true" and see all application logs in logCat AndroidStudio. Signing an application with a release key can also be automatized and a release version immediately collected from the studio. So all the logs can be seen - YuriySPb
  • one
    Try to find something else in the logs up to this point. What you brought is just a message about the completion of the process, and we would have a reason) In theory, it should be there. And the exhaust logs is better to add to the question - YuriySPb

0