# Black Screen on Android

**URL:** <https://community.nianticspatial.com/t/black-screen-on-android/2103>\
**Category:** I'm Stuck\
**Created:** [May 31, 2022, 6:19am UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103 "2022-05-31T06:19:16Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![von](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@von](https://community.nianticspatial.com/u/von)\
**Post date:** [May 31, 2022, 6:19am UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/1 "2022-05-31T06:19:17Z")

</div>

- **Issue category** : ARDK Documentation
- **Device type & OS version** : Android 12
- **Host machine & OS version** : Windows 10
- **Issue Environment** : On Device
- **ARDK version** : 2.0.0
- **Unity version** : 2021.3.3f1 (also tried with 2020.3.35f1)

Description of the issue:  
I saw the five topics related to my issues. I have tried all of those and did not help me with my problem. I also want to say that I tried and built the app targeted to Android 12 and Android 8, with their respective configuration. I also tried the project with Unity 2020.3.35f1 and got the same result. The following are my configurations:

![AndroidPermission](https://us1.discourse-cdn.com/niantic/original/1X/8580303c9fde7f1e714e0d16a415fa1db03695c2.png)

 ![APILevel](https://us1.discourse-cdn.com/niantic/original/1X/e937703d37e106239cd59855e4253750f9a367e6.png)  
 ![BuiltType](https://us1.discourse-cdn.com/niantic/original/1X/cf75d2e45ed7a64fd5d873bbb326a955a4cbdf3f.png)  
 ![TargetArch](https://us1.discourse-cdn.com/niantic/original/1X/c975d0b4f2539e8300e192579ff1d0425eff73b7.png)

In addition I also tried lowering the Minimum API Level to 6. When I targeted level 30, I added the queries tag in my AndroidManifest. The app asked for access to the camera the first time I ran it. In between builds, I always uninstalled the app and reinstall it to test a new configuration. I also checked that my app has the correct permission. I also manually added access to the mic and location on each install.

I am able to build the same project to iOS and can see my sample app running on an iPhone.

What else am I missing on my Android build?

---

<div class="post-metadata">

**Author:** ![BBIT-Solutions](https://avatars.discourse-cdn.com/v4/letter/b/bc79bd/32.png) [@BBIT-Solutions](https://community.nianticspatial.com/u/BBIT-Solutions)\
**Post date:** [May 31, 2022, 9:49am UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/2 "2022-05-31T09:49:36Z")

</div>

Do you get any information in the logcat?

---

<div class="post-metadata">

**Author:** ![von](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@von](https://community.nianticspatial.com/u/von)\
**Post date:** [May 31, 2022, 1:06pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/3 "2022-05-31T13:06:35Z")

</div>

This is all I got…

 ![Screenshot_20220531-210353](https://us1.discourse-cdn.com/niantic/original/1X/910a27dd1ad8c3e43c4f28d08b13b7acb303e8e6.png)

---

<div class="post-metadata">

**Author:** ![BBIT-Solutions](https://avatars.discourse-cdn.com/v4/letter/b/bc79bd/32.png) [@BBIT-Solutions](https://community.nianticspatial.com/u/BBIT-Solutions)\
**Post date:** [May 31, 2022, 1:54pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/4 "2022-05-31T13:54:13Z")

</div>

Hmm, there should be more actually. Can you filter for the tags ARDK and/or Unity?

---

<div class="post-metadata">

**Author:** ![Todd\_Little](https://avatars.discourse-cdn.com/v4/letter/t/b782af/32.png) [@Todd\_Little](https://community.nianticspatial.com/u/Todd_Little)\
**Post date:** [May 31, 2022, 3:00pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/5 "2022-05-31T15:00:51Z")

</div>

I don’t know if this is related, but I upgraded to 2.0.0 and I’m starting to get a java ARCore result.length error message. This is with my Galaxy S9. It’s as if the device is not recognized as an ARCore device even though it worked earlier versions of ARDK.

---

<div class="post-metadata">

**Author:** ![von](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@von](https://community.nianticspatial.com/u/von)\
**Post date:** [May 31, 2022, 3:16pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/6 "2022-05-31T15:16:04Z")

</div>

Filtering with “ARDK” or “Unity” gives me nothing.

---

<div class="post-metadata">

**Author:** ![Todd\_Little](https://avatars.discourse-cdn.com/v4/letter/t/b782af/32.png) [@Todd\_Little](https://community.nianticspatial.com/u/Todd_Little)\
**Post date:** [May 31, 2022, 3:24pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/7 "2022-05-31T15:24:12Z")

</div>

Unity has an Android Logcat package. Try adding that and keep the phone connected via USB [Android Logcat | Android Logcat | 1.3.2 (unity3d.com)](https://docs.unity3d.com/Packages/com.unity.mobile.android-logcat@1.3/manual/index.html)

---

<div class="post-metadata">

**Author:** ![BBIT-Solutions](https://avatars.discourse-cdn.com/v4/letter/b/bc79bd/32.png) [@BBIT-Solutions](https://community.nianticspatial.com/u/BBIT-Solutions)\
**Post date:** [May 31, 2022, 4:57pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/8 "2022-05-31T16:57:08Z")

</div>

I also ran into strange problems since upgraded to 2.0.0…  
results.length could also be somehow related with the ARCore’s HitResult, just from the naming 🤔  
Do you maybe have some more context (when it occurs or exact line of the error or so)?

---

<div class="post-metadata">

**Author:** ![BBIT-Solutions](https://avatars.discourse-cdn.com/v4/letter/b/bc79bd/32.png) [@BBIT-Solutions](https://community.nianticspatial.com/u/BBIT-Solutions)\
**Post date:** [May 31, 2022, 5:01pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/9 "2022-05-31T17:01:26Z")

</div>

@von Oh, just noticed, that you have also have set Minimum API Level to 29. Could you try 24 (Android 7, Nougat) instead? I remember this is recommended somewhere in the docs.

---

<div class="post-metadata">

**Author:** ![von](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@von](https://community.nianticspatial.com/u/von)\
**Post date:** [May 31, 2022, 6:07pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/10 "2022-05-31T18:07:12Z")

</div>

Oh wow!! I missed it by two versions. So I tried this with Marshmallow (level 23), as I was testing with an old phone and Android 10 and it did not work. The following are what I tried in all:

Min API Level: Android 6.0  
Target API Level: Any Level  
Status: FAILED

Min API Level: Android 10.0  
Target API Level: Android 10.0 and Android 11.0  
Status: FAILED

Min API Level: Android 11.0  
Target API Level: Android 10.0, Android 11.0, 31 and 32  
Status: FAILED

Min API Level: Android 7.0  
Target API Level: Android 10.0  
Status: FAILED

Min API Level: Android 7.0  
Target API Level: Android 11.0  
**Status: SUCCESS**

Thanks a lot for your help @BBIT-Solutions !

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/niantic/user_avatar/community.nianticspatial.com/system/32/13_2.png) [@system](https://community.nianticspatial.com/u/system)\
**Post date:** [May 31, 2022, 8:07pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/11 "2022-05-31T20:07:33Z")

</div>

Closed on May 31, 2022, 8:07pm UTC

This topic was automatically closed 2 hours after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![Jesus\_Niantic](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@Jesus\_Niantic](https://community.nianticspatial.com/u/Jesus_Niantic)\
**Post date:** [June 1, 2022, 7:03pm UTC](https://community.nianticspatial.com/t/black-screen-on-android/2103/12 "2022-06-01T19:03:56Z")

</div>

Hello Voltaire,

I’m glad to see that you were able to get this issue resolved. Would you mind sharing the brand and model of device you were building your project to? We’re in the process of looking into a few other reports of black screens and sharing this information would really help.
