Mobile App crashing on launch on android 4.1

Application crashes immediately on launch. Device: Samsung Galaxy Win. Android 4.1.2
Empty project crashes too. But on Sony Zperia Z2 android 5 works fine.

Can't find any workarounds.

 

Anything in the android logs?
http://answers.unity3d.com/questions/492681/how-to-use-adb-logcat.html#answer-571021

 

Only this:

 

Can you try with limiting to GLES2, changing from Graphics Automatic in build options.
Android crashing really needs be looked at, maybe not enough reports to QA.
Worries me most as a mobile developer.

 

I tried. Didn't help.

 

bug reported it? sounds like something important to fix, i've got lot of reports of android crashes but i don't have any of the devices so i can't test it

 

Yes. But didn't get reply yet.
Same on note 3 neo, android 4.3

 

I hope it gets fixed in the next Beta, there is another Android issue waiting for in next Beta and iOS fixes for TV added in 5.3.4patch1

 

Could we have the bug report # here please?

 

Case 782548

 

https://issuetracker.unity3d.com/is...n-specific-android-devices-from-unity-5-dot-4

 

It's only to me or b12 is non-usable for Android?

I was able to Build and Run on an Alcate OneTouch. But I published it as Beta on Google Play Store and it Install but does not works on a Moto G and it does not even install anymore on my Alcatel (using the play store), Error Device is not Compatible). But it was working on 4.3 version.

 

Game really does not work on Moto G! Anybody here faced the same problem?

It keeps showing the navigation bar on and off and does not even initializes.

https://www.dropbox.com/s/ayr1tyr72excozy/video.mp4?dl=0

 

I also get a crash on MotoG, it's in b8-13 it seems, I tried all betas.

 

Any crash logs from adb debug log?
May help developers.

 

Here is the logcat.txt from the device where the test failed. I hope it helps!

 

Here's the relevant logcat excerpt I found:

 

Exactly the same error here (on a Wiko Cink Five -android 4.1.2- and a Sony xperia E3 ) . Even an empty scene crash. The problem seems to be from mono (i didint filter the logcat) :

D/Unity (10973): GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_AMD_program_binary_Z400 GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_robustness GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_NV_fence GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_depth_texture_cube_map GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_vertex_type_10_10_10_2 GL_OES_vertex_array_object GL_QCOM_alpha_test GL_QCOM_binning_control GL_QCOM_driver_control GL_QCOM_perfmon_global_mode GL_QCOM_extended_get GL_QCOM_extended_get2 GL_QCOM_tiled_rendering GL_QCOM_writeonly_rendering GL_EXT_sRGB GL_EXT_sRGB_write_control GL_EXT_texture_sRGB_de
D/Unity (10973): code GL_EXT_texture_filter_anisotropic GL_EXT_multisampled_render_to_texture GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_disjoint_timer_query
D/StatusBar.NetworkController( 1124): onSignalStrengthsChanged signalStrength=SignalStrength: 99 0 -120 -160 -120 -1 -1 16 -114 -13 80 2147483647 2147483647 gsm|lte level=1
D/StatusBar.NetworkController( 1124): refreshViews connected={ data } level=1 combinedSignalIconId=0x7f020133/com.android.systemui:drawable/stat_sys_signal_1_fully combinedActivityIconId=0x7f02013a mobileLabel=Orange F wifiLabel= emergencyOnly=false combinedLabel=Orange F mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x7f020133 mQSPhoneSignalIconId=0x7f020058 mDataDirectionIconId=0x7f020115 mDataSignalIconId=0x7f020133 mDataTypeIconId=0x7f020115 mQSDataTypeIconId=0x7f020062 mNoSimIconId=0x0 mWifiIconId=0x0 mQSWifiIconId=0x7f020079 mBluetoothTetherIconId=0x108088c
D/QcConnectivityService( 1006): getMobileDataEnabled returning true
E/mono (10973):
E/mono (10973): Unhandled Exception: System.ExecutionEngineException: SIGILL
W/InputDispatcher( 1006): channel '428a26e8 infinity.pixel.rogue.ui2/com.unity3d.player.UnityPlayerActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
W/MediaFocusControl( 1006): AudioFocus audio focus client died
E/InputDispatcher( 1006): channel '428a26e8 infinity.pixel.rogue.ui2/com.unity3d.player.UnityPlayerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
I/MediaFocusControl( 1006): AudioFocus removeFocusStackEntry(): removing entry for android.os.BinderProxy@41b4a528
W/InputDispatcher( 1006): Attempted to unregister already unregistered input channel '428a26e8 infinity.pixel.rogue.ui2/com.unity3d.player.UnityPlayerActivity (server)'
I/ActivityManager( 1006): Process infinity.pixel.rogue.ui2 (pid 10973) has died.
I/WindowState( 1006): WIN DEATH: Window{428a26e8 u0 infinity.pixel.rogue.ui2/com.unity3d.player.UnityPlayerActivity}
W/WindowManager( 1006): Force-removing child win Window{428cd8b8 u0 SurfaceView} from container Window{428a26e8 u0 infinity.pixel.rogue.ui2/com.unity3d.player.UnityPlayerActivity}
W/ActivityManager( 1006): Force removing ActivityRecord{41b64be8 u0 infinity.pixel.rogue.ui2/com.unity3d.player.UnityPlayerActivity t47}: app died, no saved state
W/WindowManager( 1006): Failed looking up window
W/WindowManager( 1006): java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@42486760 does not exist
W/WindowManager( 1006): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8158)
W/WindowManager( 1006): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8149)
W/WindowManager( 1006): at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1072)
W/WindowManager( 1006): at android.os.BinderProxy.sendDeathNotice(Binder.java:493)
W/WindowManager( 1006): at dalvik.system.NativeStart.run(Native Method)
I/WindowState( 1006): WIN DEATH: null
D/Zygote ( 216): Process 10973 exited cleanly (1)
D/CustomizationProcess( 1395): dismissCustomizationDialog:true
D/StkAppService( 1362): onStart()---
D/StkAppService( 1362): onStart()---msg.arg1 == 7 , slotId = 0
D/StkAppService( 1362): handleMessage()---opcode == 7
W/Binder ( 1287): Caught a RuntimeException from the binder stub implementation.
W/Binder ( 1287): java.lang.NullPointerException
W/Binder ( 1287): at android.inputmethodservice.IInputMethodWrapper.setSessionEnabled(IInputMethodWrapper.java:280)
W/Binder ( 1287): at com.android.internal.view.IInputMethod$Stub.onTransact(IInputMethod.java:129)
W/Binder ( 1287): at android.os.Binder.execTransact(Binder.java:404)
W/Binder ( 1287): at dalvik.system.NativeStart.run(Native Method)
W/InputMethodManagerService( 1006): Got RemoteException sending setActive(false) notification to pid 10973 uid 10189
I/ActivityManager( 1006): Timeline: Activity_windows_visible id: ActivityRecord{42751ac8 u0 com.sonyericsson.home/com.sonymobile.home.HomeActivity t1} time:24622857
^C

 

still not fixed on b14
i thought this was going to be an urgent matter

 

Is that a joke when it comes to mobile Android, least urgent with Unity!

 

Are they even aware of this ?

 

That's good to know

 

Dont see why they are not - as you can see at start of thread, original author has filled bug report and the thread has some discussion, there are not that many threads in the beta section to claim "it has been missed". Maybe they have not reproduced it yet, but I hope in next beta.

The naggin with Android will continue as one who is not a professional developer studio cannot afford what happens in the past with the Android community, you release a nice game on iOS and good rating, release same game on Android and you get backlash,Crashing and Black Screens and all sorts, 1 star scarred, then its pointless really, once the 1 stars hit your screwed.

 

How to test Android?

 

Well, this is annoying actually... Hope it will be fixed soon.

 

Another thread to monitor, think same issue.

http://forum.unity3d.com/threads/5-...h-on-launch-does-not-crash-on-5-3-3f1.397088/

 

Cause of this bug I cant release the project, and my customers are displeased ((
On 5.3 was rotation bug when object is negatively scaled, and qa adviced me to use beta.

 

Can you provide more details about the issue, is it general bug affecting many Android phones or certain types?
We really need to know about Android problems so we can keep a eye out as there so many devices of course.
As mentioned main concern is releasing a Android game in the future thats been tested on a few physical devices one owns and all is fine, soon as released to store, many negative comments from Android users! Sorry but the whole Android graphic,crashing,black screens issues have been present in every Unity release.

 

Well that answers one simple questions -> that its device specific..
And how do we know which devices it fixes (devices with a common GPU, or certain processor chips?)

 

@Yury Habets Thanks for this confirmation.

 

It's not animation rotation, it's just rotation. I've checked 5.3.4p5 bug is still there.

 

Any progress?