Search Unity

Failure to initialize! Your hardware does not support this application, sorry!

Discussion in 'Android' started by totiherms, Mar 17, 2015.

  1. totiherms

    totiherms

    Joined:
    Oct 7, 2014
    Posts:
    4
    Hi,
    I can't run my game in a Samsung Galaxy Tab 10.1 (SGH-T859). The same game built with Unity 4 works fine.
    I read that Unity 5 is not compatible with non-Neon devices, will not be included in a next update of unity?
    The devices that not support this build (non-Neon) are excluded automatically in Google Play or I have to add it manually??
     
  2. sixagon

    sixagon

    Joined:
    Feb 11, 2015
    Posts:
    1
    I'm getting this same error on a Galaxy Tablet with a game built in Unity 5. Running 4.04.
     
  3. spacefrog

    spacefrog

    Joined:
    Jun 14, 2009
    Posts:
    550
    I think Tegra 2 devices are excluded since Unity 5
    My Asus transformer TF101 was hit by the same cut in Unity device support
     
  4. CharlesBarros

    CharlesBarros

    Joined:
    Nov 17, 2011
    Posts:
    61
    • Dropped support for non-NEON CPU devices (e.g. Tegra 2). This gives a significant performance boost to Mecanim and PhysX among other things.
    Source: https://unity3d.com/unity/whats-new/unity-5.0
     
    tolstenko likes this.
  5. WASSA

    WASSA

    Joined:
    May 13, 2014
    Posts:
    1
    Is there no way to work around this??
     
  6. CharlesBarros

    CharlesBarros

    Joined:
    Nov 17, 2011
    Posts:
    61
    Nope. You should mark the following devices as not supported in the Play Store Developer:
    • Acer Iconia Tab A100 and A500
    • Asus Eee Pad Transformer
    • Asus Eee Pad Slider
    • LGE Optimus 2X
    • LGE Optimus Pad
    • Motorola Atrix 4G
    • Motorola Droid Bionic
    • Samsung Galaxy S II - There is over 35 Galaxy S II models available. You need to block only the following ones:
      • SGH-I777
      • SGH-I727
      • SGH-I727R
      • SGH-I927
      • SGH-I927R
    • Samsung Galaxy Tab 10.1
    • Motorola Xoom
     
    LightingBox2, tolstenko and Kirbyrawr like this.
  7. Asse83

    Asse83

    Joined:
    Aug 1, 2009
    Posts:
    169
    Honestly, that is absolutely not cool!

    Excluding a bunch of devices to gain some performance for features that are never used to the fullest on mobile devices is a no-go. We constantly get support-mails regarding this and have to exclude new devices every day since the list above is far from complete..
     
  8. 39thstreet

    39thstreet

    Joined:
    Jan 30, 2012
    Posts:
    96
    Has anybody pulled together or found a bigger list of Tegra 2 devices? It's really horrible to have to try to dig all these up manually.
     
  9. 39thstreet

    39thstreet

    Joined:
    Jan 30, 2012
    Posts:
    96
    Been looking into this, and I do not believe the list of devices posted by @CharlesBarros is 100% accurate. For example, the Samsung i727 ( Samsung Galaxy S II Skyrocket i727 ) uses a Qualcomm MSM8260 Snapdragon. I believe this support Neon. I ran some tests on this device, and it does not crash with the "Failure to Initialize" like the Motorola Xoom and Samsung Galaxy Tab 8.9 P7310 do.

    It's a shame this information isn't more clearly posted somewhere online.

    Here's the best list I could come up with of Tegra 2 devices ( crosschecked these on sites, but still device model names are inconsistent and confusing):
    Acer Iconia Tab A100
    Acer Iconia Tab A101
    Acer Iconia Tab A200
    Acer Iconia Tab A500
    Acer Iconia Tab A501
    Advent Vega
    Asus Eee Pad Slider SL101
    Asus Eee Pad Transformer TF101
    Dell Streak 10 Pro
    Dell Streak 7
    Dell Streak 7 Wi-Fi
    eLocity A7
    Exper EasyPad P10AN
    LGE Optimus 2d SU660 star_450-05
    LGE Optimus 2X SU990
    LGE Optimus EX SU880
    LGE Optimus Pad V900
    LGE Optimus Q2 LU6500
    LGE Revolution
    MALATA SMB-A1011
    Micromax A85
    Motorola ATRIX
    Motorola Droid Bionic XT865
    Motorola Droid X2
    Motorola MOTO MT870
    Motorola MOTO XT882
    Motorola Photon 4G MB855
    Motorola Xoom MZ505
    Motorola Xoom MZ600
    Motorola Xoom MZ601
    Motorola Xoom MZ604
    Mouse LuvPad AD100
    Olivetti OliPad 100
    ONKYO TA117
    Point of View Mobii 10.1
    Samsung Captivate Glide i927
    Samsung Galaxy R I9103
    Samsung Galaxy Tab 10.1 ( ALL MODELS!)
    Samsung Galaxy Tab 8.9 ( ALL MODELS!)
    Sony Tablet P
    Sony Tablet S
    T-Mobile G-Slate
    T-Mobile G2x
    TORADEX Colibri T20
    Toshiba FOlio AC100
    Toshiba Thrive
    Velocity Micro Cruz Tablet L510
    ViewSonic G Tablet
    WooW Digital The One
    ZTE Grand X V970
     
    Last edited: May 22, 2015
  10. Waz

    Waz

    Joined:
    May 1, 2010
    Posts:
    252
    Thanks - I'm using this list as a starting point so my beta doesn't break too many devices (I already got 2 failures on the first day with about 50 installs of the beta).

    EDIT: it seems the Play Store only allows you one list of excluded devices per application, not per APK. This is bad news for anyone updating their existing app to Unity 5.

    Motorola Droid Bionic XT865 doesn't appear to be in the Play Store list of excludable devices, but the XT875 is (as "Droid Bionic – cdma_targa"), which uses OMAP. Quite a few others in that list don't seem to have an entry in the devices list, so my final list of devices I could exclude is:

    (55 total)
    1. ACER
      1. Iconia Tab A501– picasso
      2. Iconia Tab A100 (VanGogh)– vangogh
      3. Iconia Tab A200– picasso_e
    2. ASUS
      1. Eee Pad TF101– TF101
      2. Eee Pad TF101-WiMAX– TF101-WiMAX
      3. Eee Pad Slider– SL101
    3. DELL
      1. Dell Streak 10 Pro– Streak10Pro
      2. Dell Streak 7– streak7
    4. GOOGLE
      1. XOOM– stingray
      2. XOOM– wingray
    5. LGE
      1. Optimus 2X– star_450-05
      2. Optimus 2X– p999
      3. Optimus 2X– p990_CIS-xxx
      4. Optimus 2X– p990
      5. Optimus 2X– p990hN
      6. Optimus 2X– p990_262-xx
      7. LG Revolution– bryce
      8. Optimus 2X– p990_EUR-xx
    6. MOTOROLA
      1. Droid X2– daytona
      2. XOOM– umts_everest
      3. Photon 4G– sunfire
      4. Atrix– olympus
      5. XOOM– umts_hubble
      6. XOOM– wifi_hubble
    7. SAMSUNG
      1. Galaxy Tab 8.9– GT-P7310
      2. Galaxy Tab 10.1– SHW-M380K
      3. Galaxy Tab 10.1– SCH-I905
      4. Galaxy Tab 10.1– SHW-M380S
      5. Galaxy Tab 8.9– SGH-I957R
      6. Galaxy Tab 8.9– SHV-E140S
      7. Galaxy Tab 10.1 v– p3
      8. Galaxy Tab 10.1– GT-P7500D
      9. Galaxy Tab 10.1– SGH-T859
      10. Galaxy Tab 8.9– GT-P7320
      11. Galaxy Tab 10.1 N– GT-P7501
      12. Galaxy Tab 10.1– SC-01D
      13. Galaxy Tab 10.1 N– GT-P7511
      14. Galaxy Tab 10.1– SHW-M380W
      15. Galaxy Tab 10.1– GT-P7503
      16. Galaxy Tab 8.9– SHW-M305W
      17. Galaxy Tab 8.9– GT-P7300
      18. Galaxy Tab 8.9– SGH-I957D
      19. Galaxy Tab 8.9– SHV-E140L
      20. Galaxy Tab 8.9– SGH-I957M
      21. Galaxy Tab 8.9– SHV-E140K
      22. Galaxy Tab 10.1– GT-P7500
      23. Galaxy Tab 8.9– SCH-P739
      24. Captivate Glide– SGH-I927
      25. Galaxy Tab 10.1– SHW-M300W
      26. Galaxy Tab 8.9– SGH-I957
    8. SONY
      1. Sony Tablet P– nbx02
      2. Tablet S– nbx03
    9. TOSHIBA CORPORATION
      1. Thrive 7– tostab04
    10. ZTE
      1. Grand X– P175A20
    11. UNKNOWN
      1. MALATA
    This really needs to be formally maintained, preferably by Unity.
     
    Last edited: Jun 2, 2015
  11. FuzzyQuills

    FuzzyQuills

    Joined:
    Jun 8, 2013
    Posts:
    2,869
    Isn't there just a check to see if the device's CPU has NEON extensions? Or can't play store do that?
     
  12. Waz

    Waz

    Joined:
    May 1, 2010
    Posts:
    252
    There doesn't appear to be a manifest flag for non-NEON. Google's policy appears to be that vendors should check at runtime and provide an alternative implementation for non-NEON, not simply bomb out as Unity 5 does.
     
  13. FuzzyQuills

    FuzzyQuills

    Joined:
    Jun 8, 2013
    Posts:
    2,869
    Well, it did have an alternative, but to boost performance, Unity just "bombed out" as you put it. I still don't see the logic of doing that... :D
     
  14. 128bit

    128bit

    Joined:
    Oct 8, 2014
    Posts:
    117
    Fun fact, it did worked for me in 4.1, updatet the s2 now to 4.2 and boom, same fail message appears now :D
     
  15. FuzzyQuills

    FuzzyQuills

    Joined:
    Jun 8, 2013
    Posts:
    2,869
    DUDE, FILE A BUG REPORT!!! It appears you just hit a case you can prove!

    Pitty I can't check my 'droid to see if it does the same thing. (Stupid thing has NO oficial updates being a chinese tablet!)
     
  16. 128bit

    128bit

    Joined:
    Oct 8, 2014
    Posts:
    117
    Since the non neon cpu support is dropped offcially, il think it doesnt make sense to fill one. Just wondered that it worked on my s2 :D
     
  17. FuzzyQuills

    FuzzyQuills

    Joined:
    Jun 8, 2013
    Posts:
    2,869
    And an S2 doesn't have NEON, yet it launched fine before? o_O Strange... :D

    EDIT: re-read both your posts... so you're saying android 4.1 seems to "spoof" NEON support?! :D
     
  18. 128bit

    128bit

    Joined:
    Oct 8, 2014
    Posts:
    117
    I dunno, just encountered that it worked with my s2 & android 4.1. Same apk didnt worked in updated android 4.2 same device :D There where some lightning bugs, but it worked. Strange...
     
    Last edited: Jul 6, 2015
  19. sandbaydev

    sandbaydev

    Joined:
    Aug 9, 2013
    Posts:
    68
    I got report that HTC Desire 510 (htc_a11ul) would not work (my app built on Unity 5.0). Anyone encountered the same?
     
  20. Ox_

    Ox_

    Joined:
    Jun 9, 2013
    Posts:
    93
    Can confirm a Unity 5 game working on S2.

    Also Wikipedia says:
    https://en.wikipedia.org/wiki/Samsung_Galaxy_S_II#Hardware_and_design

    Thank you a lot, I was searching for this list everywhere.
     
  21. Linda Kerkhoff

    Linda Kerkhoff

    Joined:
    Nov 19, 2013
    Posts:
    1
    Thanks a lot for the list, you could add GT-P7510 (Samsung - just another Galaxy Tab 10) and AT100 (tostab03) (TOSHIBA CORPORATION) as well.

     
  22. vsharma

    vsharma

    Joined:
    Jun 25, 2015
    Posts:
    1
    So manually blacklisting non neon devices in Google Play is the only solution when upgrading from Unity 4 to Unity 5?

    Is there any filter which we can use rather than maintaining a manual list? So that I can use multiple APK feature http://developer.android.com/google/play/publishing/multiple-apks.html to support both neon (Unity 5 build) & non neon devices (Unity 4 build).
     
  23. tolstenko

    tolstenko

    Joined:
    May 31, 2012
    Posts:
    14
    Add to the unsupported device list: MZ605, another version of Motorola Xoom.
     
  24. coshea

    coshea

    Joined:
    Dec 20, 2012
    Posts:
    251
    Screen Shot 2016-03-16 at 10.15.18.png
    In the GDC talk, this developer used Device Intelligence to filter out old Android devices

    skip to 1:26:34


    This service doesn't seem available to the public, but would be great if Unity had a list of Android devices that has the wrong GPU supported by Unity 5.
     
  25. LotusBlack

    LotusBlack

    Joined:
    Apr 9, 2015
    Posts:
    35
    SERIOUSLY...

    Not even an official reply here on the matter, I accidentally found out about this after updating an old app because of a user's support ticket.
    Unity really should keep a list like this updated.
     
  26. Aram-Azhari

    Aram-Azhari

    Joined:
    Nov 18, 2009
    Posts:
    141
    There are over 10000 android devices out there. I bet thousands of them are not game capable.
     
  27. Dakwamine

    Dakwamine

    Joined:
    Aug 5, 2012
    Posts:
    21
  28. FireBird2013

    FireBird2013

    Joined:
    Mar 9, 2017
    Posts:
    1
    Hi there is a simple way to work around this
     
  29. seidlfranz

    seidlfranz

    Joined:
    Mar 31, 2017
    Posts:
    12
    Sorry for sending this solution so late, but I am new on Unity and had to solve this Problem by myself.

    I got the same problem and I solved it by Copying the jniLibs Folder into Project:/src/main Folder.from the exported Project.

    In this will be helpful for other having the same problem
     
  30. totsboy

    totsboy

    Joined:
    Jul 12, 2013
    Posts:
    248
    I'm getting this error on Samsung Galaxy S8 o_O

    @seidlfranz my jniLibs folder is already inside src/main
     
  31. unity_aAXGbqALXB8Mdw

    unity_aAXGbqALXB8Mdw

    Joined:
    Feb 21, 2018
    Posts:
    1