Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice
  2. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  3. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Mobile 5.4.0b13 - Some Android Devices Crash on launch, Does not crash on 5.3.3f1 [RESOLVED]

Discussion in '5.4 Beta' started by Baraphor1, Apr 11, 2016.

  1. Baraphor1

    Baraphor1

    Guest

    This Issue was resolved in B18


    Hello,

    We have migrated to the beta version to start working towards a WebGL build of our game because the WebPlayer is going away.

    However with certain devices, our Android build will no longer run, it will start and then go back to the main screen. This does not happen with 5.3.3f1, however it happens with all the Beta's we have tested from 5.4.0b9 +

    Here is a list of devices that we are aware of where this issue happes.

    More detailed Information on those devices here: https://docs.google.com/spreadsheets/d/1dcYhYkd_BPEuoUV3EZtL8BOsS8ilWP8SGobkt5j3c34/edit?usp=sharing


    Here is a link to the apk built in the latest beta, this is a public version that is released, however I cannot share the project, just the apk link for a released version.
    https://drive.google.com/file/d/0B_u1V4MURiMJWEh3UG9Oc2E4Rmc/view?usp=sharing
     
    Last edited by a moderator: May 26, 2016
    Manny02468, MrEsquire and cmanny like this.
  2. cmanny

    cmanny

    Joined:
    Oct 22, 2015
    Posts:
    10
  3. Baraphor1

    Baraphor1

    Guest

    It does look related, we are not testing on a blank project though. So far we can find no common thread on our end, including we have run the apk through cloud testing through various sources and get mixed results, for instance Samsung's cloud builds the game will run on the s3 but with other cloud build systems it will not. There was a version difference of 4.3 (samsung) to 4.4 (other site).

    I am going to look at the bug report and see if I can add something.
     
    MrEsquire likes this.
  4. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    We have confirmed the issue, no more bug reports/projects needed.
    Android team is working on fixing it with high priority. Updates to come soon. Appreciate your patience!
     
    cmanny likes this.
  5. Baraphor1

    Baraphor1

    Guest

    Did B15 resolve this issue?
     
  6. Bastienre4

    Bastienre4

    Joined:
    Jul 8, 2014
    Posts:
    191
    According to the change log, no.
     
    MrEsquire likes this.
  7. ottolb

    ottolb

    Joined:
    Jul 1, 2009
    Posts:
    42
  8. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    Tried with the just released b16?
     
  9. Bastienre4

    Bastienre4

    Joined:
    Jul 8, 2014
    Posts:
    191
    No but it should be the same according to the changelog...
     
  10. Baraphor1

    Baraphor1

    Guest

    I hope this gets fixed soon. I wish Unity provided more information on this issue.
     
    Last edited by a moderator: Apr 28, 2016
    MrEsquire likes this.
  11. sevensails

    sevensails

    Joined:
    Aug 22, 2013
    Posts:
    483
    It's strange! 3 weeks waiting for fixes for this problem (Game does not starts on several models of Android devices) and another for the setParent(null) bug and nothing. Two very critical bugs that seems to be ignored by Unity Team.
     
  12. Stephan-B

    Stephan-B

    Joined:
    Feb 23, 2011
    Posts:
    2,269
    Just ran my usual test scene with Unity 5.4 Beta 16 and getting a crash on start. This same scene works fine on the same devices when using Unity 5.3.
     
  13. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    Sorry guys for the delay. I'm trying to get the fix into beta 18, along with a list of other Android fixes.
     
  14. Manny02468

    Manny02468

    Joined:
    May 2, 2016
    Posts:
    3
    Is the HTC Desire 626 a part of this list?
     
  15. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    There's no strict list of devices that are affected by the bug. However, if the symptoms you experience look similar, it will likely get fixed in b18.
     
  16. Manny02468

    Manny02468

    Joined:
    May 2, 2016
    Posts:
    3
    Do you know when this will be released?
     
  17. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    As far as I know, in several days.
     
    Manny02468 likes this.
  18. sevensails

    sevensails

    Joined:
    Aug 22, 2013
    Posts:
    483
    I bet beta 18 will be released by Next Wednesday. Can't wait for it.
     
  19. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    I wish this was on b17 already been waaaaaay toooooo long with this known bug. It's like been on ER been told to wait a few days for treatment.
     
    Last edited: May 5, 2016
  20. Baraphor1

    Baraphor1

    Guest

    It is good to know this will be in Beta 18.
     
  21. Bastienre4

    Bastienre4

    Joined:
    Jul 8, 2014
    Posts:
    191
    Good to know ! Can we know (roughtly) what is the origin of this bug ?
     
  22. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    Some issues with new atomic operations code on ARM.
     
  23. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    in theory it should be fixed on b18... counting the minutes for its release. Like literally, I was up until 2 am hoping it was released yesterday.
     
  24. MrEsquire

    MrEsquire

    Joined:
    Nov 5, 2013
    Posts:
    2,712
    lol @ staying up for it
     
  25. sevensails

    sevensails

    Joined:
    Aug 22, 2013
    Posts:
    483
    The b18 release is late! Let's hope the delay is because it will come with tons of fixes! =)
     
    MrEsquire likes this.
  26. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    I just need this fix, it's critical. The others are annoying or whatever you want to call it. But when you can't even load a game on the device is not fun to wait months for a fix.
     
  27. Manny02468

    Manny02468

    Joined:
    May 2, 2016
    Posts:
    3
    I need this update I'm tired of not being able to play my favorite game. When will the update be released????? Its months since the bug has been discovered and no update yet.
     
  28. Khash-Firestorm

    Khash-Firestorm

    Joined:
    Jun 30, 2013
    Posts:
    87
    I just want to let you know that about 5% of the Windows PC users experience crash in version 5.4.0b15 and 5.4.0b17
    This issue was not present in unity 5.3.3f1

    Our game is public with about 500 users daily so its fair "test" base.

    Crash produced by this unity version does not happen on all machines (it seems that its somewhat specific, so some machines gets it often, some does not at all)
    Crash does not log any data in neither release log format nor script-debug.
    I have observed spike in "null" related issues logged by Unity performance in some strange locations which are not reproducable for us which I think might be somehow linked to the above issue.

    We keep investigating issue, any suggestions would be appreciated :)
     
    MrEsquire likes this.
  29. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    well, posting on a different thread may be more helpul since this is Android specific.
     
  30. Khash-Firestorm

    Khash-Firestorm

    Joined:
    Jun 30, 2013
    Posts:
    87
    yes, but seems very similar to my issue so I think its worth to extend spectrum of search fr the problem :)
    And I think I might just have a bypass to it. Need some further tests by my players (I cannot reproduce issue myself)
     
  31. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    no, it's not related at all. This is ARM code crash, PC run on intel chips. The only thing that is similar is that it crashes.
     
  32. Khash-Firestorm

    Khash-Firestorm

    Joined:
    Jun 30, 2013
    Posts:
    87
    and the fact that the issue showe up as a regression in 5.4. Anyway i will not bother you anymore. Cheers!
     
  33. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    oh boy, when is b18 gonna be released...
     
  34. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    b18 is out! anyone has tried if this is fixed? the release notes are very cryptic...
     
  35. LevanSanadiradze

    LevanSanadiradze

    Joined:
    Dec 12, 2012
    Posts:
    7
    I'll test it now and tell you result
     
  36. LevanSanadiradze

    LevanSanadiradze

    Joined:
    Dec 12, 2012
    Posts:
    7
    It's fixed
     
    MrEsquire likes this.
  37. creat327

    creat327

    Joined:
    Mar 19, 2009
    Posts:
    1,756
    Finally!!! :)
     
  38. avclubvids

    avclubvids

    Joined:
    Jan 6, 2015
    Posts:
    27
    It's not fixed... it is better but not 100% solved. I can now at least build a basic empty scene with analytics and collaborate turned on, but it does the same instacrash with the Tango SDK imported. I'm trying all the suggested tweaks and will post if I am able to completely eradicate the crashing. Ugh.
     
  39. avclubvids

    avclubvids

    Joined:
    Jan 6, 2015
    Posts:
    27
    In case it helps track this nasty thing down, I've isolated it to an issue in the main androidManifest file that the Tango SDK imports. I am poking at it line by line to try to find the specific piece that is causing the instacrash, here is the file should it prove useful to anyone else:

    Code (CSharp):
    1. <?xml version="1.0" encoding="utf-8"?>
    2. <manifest
    3.     xmlns:android="http://schemas.android.com/apk/res/android"
    4.     package="com.unity3d.player"
    5.     android:installLocation="preferExternal"
    6.     android:theme="@android:style/Theme.NoTitleBar"
    7.     android:versionCode="1"
    8.     android:largeHeap="true"
    9.     android:versionName="1.0">
    10.     <supports-screens
    11.         android:smallScreens="true"
    12.         android:normalScreens="true"
    13.         android:largeScreens="true"
    14.         android:xlargeScreens="true"
    15.         android:anyDensity="true"/>
    16.     <uses-feature android:name="android.hardware.camera.autofocus" android:required="false" />
    17.     <uses-permission android:name="android.permission.INTERNET" />
    18.     <uses-permission android:name="android.permission.CAMERA" />
    19.     <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    20.     <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    21.     <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    22.  
    23.     <application
    24.         android:icon="@drawable/app_icon"
    25.         android:label="@string/app_name"
    26.         android:debuggable="true">
    27.         <meta-data android:name="IMMERSIVE_MODE" android:value="true" />
    28.         <activity android:name="com.projecttango.permissionrequester.RequestManagerActivity"
    29.                   android:theme="@android:style/Theme.Translucent.NoTitleBar" >
    30.         </activity>
    31.         <activity android:name="com.google.unity.GoogleUnityActivity"
    32.                   android:label="@string/app_name"
    33.                   android:configChanges="fontScale|keyboard|keyboardHidden|locale|mnc|mcc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|uiMode|touchscreen">
    34.             <meta-data android:name="unityplayer.ForwardNativeEventsToDalvik" android:value="true" />
    35.             <meta-data android:name="unityplayer.UnityActivity" android:value="true" />
    36.             <intent-filter>
    37.                 <action android:name="android.intent.action.MAIN" />
    38.                 <category android:name="android.intent.category.LAUNCHER" />
    39.                 <category android:name="android.intent.category.LEANBACK_LAUNCHER" />
    40.             </intent-filter>
    41.         </activity>
    42.     </application>
    43. </manifest>
     
  40. Legend-

    Legend-

    Joined:
    May 20, 2016
    Posts:
    27
    I use Bluestacks 2 for testing, and it still crashes on startup (after unity splash screen)
    Unity 5.4.0b18 NOT fixed this issue...
    But in the version 5.2.4f1 all works perfectly.
     
  41. MrEsquire

    MrEsquire

    Joined:
    Nov 5, 2013
    Posts:
    2,712
    Does BlueStacks provide log entries, anything you can see?
     
  42. Legend-

    Legend-

    Joined:
    May 20, 2016
    Posts:
    27
    Yes, using logcat, but is not only Bluestacks, on real devices crashes too
     
  43. avclubvids

    avclubvids

    Joined:
    Jan 6, 2015
    Posts:
    27
    Just to triple check, I went back to 5.3 to test: I can confirm that this issue is still active in 5.4b18. It's fine in 5.3, does not work in 5.4b18. Here is a logcat dump of the crash on launch in a 5.4 project that has the Tango "Mira" Unitypackage imported and nothing else. The single file that causes this crash is the main AndroidManifest.xml. If I remove it, the app launches (but Tango obviously doesn't work) and if I delete lines from the manifest until only the ones required to build are still present, it still crashes.

    Logcat:

    Code (JavaScript):
    1.  
    2.  
    3. 12-31 17:37:21.161 896-1504/? I/ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.Mirada.testing_5_4_b18/com.google.unity.GoogleUnityActivity} from pid 1266
    4. 12-31 17:37:21.256 166-166/? W/art: Could not get current activity
    5. 12-31 17:37:21.273 896-1176/? I/ActivityManager: Start proc com.Mirada.testing_5_4_b18 for activity com.Mirada.testing_5_4_b18/com.google.unity.GoogleUnityActivity: pid=5771 uid=10164 gids={50164, 3003, 1028, 1015}
    6. 12-31 17:37:21.293 896-910/? I/art: GcCauseBackground partial concurrent mark sweep GC freed 3436(165KB) AllocSpace objects, 7(3MB) LOS objects, 9% free, 16MB/17MB, paused 5.821ms total 80.324ms
    7. 12-31 17:37:21.313 896-1321/? W/NvAppProfileService: App Profiles: Enabled
    8. 12-31 17:37:21.326 896-1321/? I/PowerServiceCient: Successfully bound to service
    9. 12-31 17:37:21.349 158-245/? E/cutils: Failed to mkdirat(/storage/sdcard1/Android): Read-only file system
    10. 12-31 17:37:21.349 158-245/? W/Vold: Returning OperationFailed - no handler for errno 30
    11. 12-31 17:37:21.350 5771-5771/? W/ContextImpl: Failed to ensure directory: /storage/sdcard1/Android/obb/com.Mirada.testing_5_4_b18
    12. 12-31 17:37:21.353 158-245/? E/cutils: Failed to mkdirat(/storage/sdcard1/Android): Read-only file system
    13. 12-31 17:37:21.353 158-245/? W/Vold: Returning OperationFailed - no handler for errno 30
    14. 12-31 17:37:21.354 5771-5771/? W/ContextImpl: Failed to ensure directory: /storage/sdcard1/Android/data/com.Mirada.testing_5_4_b18/files
    15. 12-31 17:37:21.355 5771-5771/? W/NativeActivity: ANativeActivity_onCreate not found
    16. 12-31 17:37:21.355 5771-5771/? D/AndroidRuntime: Shutting down VM
    17. 12-31 17:37:21.358 5771-5771/? E/AndroidRuntime: FATAL EXCEPTION: main
    18.                                                  Process: com.Mirada.testing_5_4_b18, PID: 5771
    19.                                                  java.lang.RuntimeException: Unable to start activity ComponentInfo{com.Mirada.testing_5_4_b18/com.google.unity.GoogleUnityActivity}: java.lang.IllegalArgumentException: Unable to load native library: /data/app-lib/com.Mirada.testing_5_4_b18-2/libmain.so
    20.                                                      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2196)
    21.                                                      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2246)
    22.                                                      at android.app.ActivityThread.access$800(ActivityThread.java:136)
    23.                                                      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1197)
    24.                                                      at android.os.Handler.dispatchMessage(Handler.java:102)
    25.                                                      at android.os.Looper.loop(Looper.java:136)
    26.                                                      at android.app.ActivityThread.main(ActivityThread.java:5030)
    27.                                                      at java.lang.reflect.Method.invoke(Native Method)
    28.                                                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
    29.                                                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:609)
    30.                                                   Caused by: java.lang.IllegalArgumentException: Unable to load native library: /data/app-lib/com.Mirada.testing_5_4_b18-2/libmain.so
    31.                                                      at android.app.NativeActivity.onCreate(NativeActivity.java:186)
    32.                                                      at com.google.unity.GoogleUnityActivity.onCreate(GoogleUnityActivity.java:44)
    33.                                                      at android.app.Activity.performCreate(Activity.java:5231)
    34.                                                      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
    35.                                                      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2160)
    36.                                                      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2246)
    37.                                                      at android.app.ActivityThread.access$800(ActivityThread.java:136)
    38.                                                      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1197)
    39.                                                      at android.os.Handler.dispatchMessage(Handler.java:102)
    40.                                                      at android.os.Looper.loop(Looper.java:136)
    41.                                                      at android.app.ActivityThread.main(ActivityThread.java:5030)
    42.                                                      at java.lang.reflect.Method.invoke(Native Method)
    43.                                                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
    44.                                                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:609)
    45. 12-31 17:37:21.360 896-1176/? W/ActivityManager:   Force finishing activity com.Mirada.testing_5_4_b18/com.google.unity.GoogleUnityActivity
    46. 12-31 17:37:21.476 1380-5791/? D/DropBoxEntryAddedChimeraService: User is not opted-in to Usage & Diagnostics.
    47. 12-31 17:37:21.899 896-916/? W/ActivityManager: Activity pause timeout for ActivityRecord{651e8f60 u0 com.Mirada.testing_5_4_b18/com.google.unity.GoogleUnityActivity t10 f}
    48. 12-31 17:37:23.006 249-249/? D/Raydium_ts_main: ## Report rate in 10 seconds =621
    49.  
    50.  
     
  44. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    java.lang.RuntimeException: Unable to start activity ComponentInfo{com.Mirada.testing_5_4_b18/com.google.unity.GoogleUnityActivity}: java.lang.IllegalArgumentException: Unable to load native library: /data/app-lib/com.Mirada.testing_5_4_b18-2/libmain.so

    This actually says a Unity library libmain.so is missing.
     
    hernanb likes this.
  45. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    Folks, issues with Tango or emulators are probably something different.
     
    MrEsquire likes this.
  46. LevanSanadiradze

    LevanSanadiradze

    Joined:
    Dec 12, 2012
    Posts:
    7
    In my case it works perfectly.. I'm using bluestacks for testing. I had the black screen crash problem which was fixed in b18... I'm using Google Play SDK in my project but not Tango SDK so I think the Tango SDK should be the source of problem
     
    Last edited: May 26, 2016
  47. Baraphor1

    Baraphor1

    Guest

    Can Confirm this, as I posted the original issue, no user has reported this problem since we released a build from B18
     
    Yury-Habets likes this.