PTCInc / vuforia-engine

Bug and feedback issue tracker for the Vuforia Engine SDK
https://developer.vuforia.com
19 stars 0 forks source link

Vuforia Camera Black Screen Issue on Samsung F13 and A55 (Android 14) #149

Open IrfanKMT opened 2 weeks ago

IrfanKMT commented 2 weeks ago

Hello everyone,

We are experiencing a black screen issue when starting the Vuforia camera on specific Android devices. Our game, developed using Unity and Vuforia, works fine on most devices but encounters problems on the following:

Samsung Galaxy F13 (Android 14) Samsung Galaxy A55 (Android 14) Details:

Unity Version: 2022.3.24f1 (also tested with 2021.3.9f1) Vuforia SDK: 10.25.4 Game Link: https://play.google.com/store/apps/details?id=com.root16.mapologyworld&hl=en_IN

Issue:

On the mentioned devices, the game launches without any errors, but when the Vuforia camera starts, the screen goes black. We've tested the game on several other devices, and it works as expected, so the problem seems specific to these Samsung models running Android 14.

What We’ve Tried:

Tested with different Unity versions (2022.3.24f1 and 2021.3.9f1). Verified permissions for camera access. Ensured that the latest updates for both Unity and Vuforia are in use. Request:

Has anyone encountered a similar issue, or does anyone have suggestions for potential solutions? Any guidance or troubleshooting tips would be greatly appreciated!

Thank you!

ptc-thesbyro commented 2 weeks ago

Hello,

Thanks for reaching out.

Could you try and reproduce the black screens on the devices with the Vuforia Core Samples?

Thank you

IrfanKMT commented 2 weeks ago

Hello,

Thanks for reaching out.

Could you try and reproduce the black screens on the devices with the Vuforia Core Samples?

Thank you

Hello, Thanks for quick response. Yes we have tried with vuforia core sample. same issue. We have tried to test in other samsung device like, Samsung S21FE (14), Samsung F23(14) working fine. but appear black screen in Samsung F13(14) and Samsung A55(14).

Thank you

ptc-epassaro commented 2 weeks ago

Hi @IrfanKMT,

While we work on trying to reproduce this issue, have you maybe tried removing Vulkan from the Graphics APIs list in the Android Player Settings and using only OpenGLES3 instead? There have been reports in the past of rendering issues in Unity with the Vulkan APIs on Exynos/Mali-based devices like the ones you are having trouble with.

IrfanKMT commented 2 weeks ago

Hi @IrfanKMT,

While we work on trying to reproduce this issue, have you maybe tried removing Vulkan from the Graphics APIs list in the Android Player Settings and using only OpenGLES3 instead? There have been reports in the past of rendering issues in Unity with the Vulkan APIs on Exynos/Mali-based devices like the ones you are having trouble with.

Hi @ptc-epassaro Yes i have tried without Vulkan (using only OpenGLES3) and with Vulkan as well. Same issue occur.

ptc-epassaro commented 2 weeks ago

Ok, then it would be great to have some more details. Could you please send us a log from the affected devices? Here we have some documentation on how to better capture Unity and Vuforia logs on Android: https://developer.vuforia.com/library/troubleshooting/troubleshooting-your-app#collect-logs

Also, which version of ARCore is installed on the devices?

IrfanKMT commented 2 weeks ago

@ptc-epassaro IMG-20240828-WA0009 We didn't get any error in log We use marker base AR. so i think no need ARCore.

ptc-epassaro commented 2 weeks ago

@IrfanKMT one thing I see from the log is that you have more than one VuforiaBehaviour in the scene, which shouldn't have any effect at runtime, but I would suggest you to remove all the VuforiaBehaviours from your scene except one.

By default, Vuforia will try to use ARCore if it's installed on your device. You might have an app called "Google Play Services for AR" installed on your phone. If you do, please send us the version of the app.

For the logs, please try to use the adb logcat command line tool and follow the steps here to capture a complete log. With that, we might be able to get a better idea of the cause of this issue.

IrfanKMT commented 2 weeks ago

@ptc-epassaro Thanks for your suggestion. i will remove VuforiaBehaviours from my scene except one. I don't device handy right now. so not able to get log using logcat. I have tested on multiple devices(Samsung S20(13), S21FE(14), F23(14), A35(14) etc) working fine in this device but black screen appears in Samsung F13(14) and A55(14). Thank you.

ptc-epassaro commented 2 weeks ago

@IrfanKMT I see, okay, we will try our best on our side and will keep you posted!

IrfanKMT commented 2 weeks ago

@IrfanKMT I see, okay, we will try our best on our side and will keep you posted!

Thank you.

ptc-epassaro commented 2 weeks ago

Hi @IrfanKMT, from our tests it seems like Exynos-based devices like yours should work without issues when updated to the latest version of ARCore. When you have the chance, it would be great if you could update those devices to the latest version of the Google Play Services for AR. If you give it a try, please let us know how it goes. We will keep trying to reproduce the issue on our side in the meantime.

IrfanKMT commented 2 weeks ago

@ptc-epassaro Okay sure i will update and let you know.

KybokyN commented 2 weeks ago

We have a similar problem with our application. It works on every snapdragon device we have tested. Devices that we have a problem with are A33, A54 (probably other Exynos based devices) and Samsung Galaxy Tab A8 10.5 with Unisoc Tiger T618 chipset. Something that is in common to those not working devices:

On first start application asks for camera permission and we allow it but when we start AR scene the camera is not activating (no green dot in top right part of screen) and everything is black. As we were testing on Galaxy Tab A8 we found out it works if we put "optional" or "required" in ARCore Requirement inside Vuforia Configuration image Problems arise on other devices if we use those optional/required options. Problems like inverted colors in camera stream (AR detection worked) and green screen. Those problems were happening on some Xiaomi devices

Unity Version: 2022.3.23f1 Vuforia SDK: 10.24.4 (also tested on newer vuforia version)

IrfanKMT commented 2 weeks ago

Hi @IrfanKMT, from our tests it seems like Exynos-based devices like yours should work without issues when updated to the latest version of ARCore. When you have the chance, it would be great if you could update those devices to the latest version of the Google Play Services for AR. If you give it a try, please let us know how it goes. We will keep trying to reproduce the issue on our side in the meantime.

@ptc-epassaro I have update Google Play Services for AR in A55 and working fine(Issue resolved). And F13 is not compatible. Thank you.

ptc-emaggio commented 2 weeks ago

@KybokyN by setting ARCore Requirement to DONT_USE Vuforia will use the Camera2 API, instead of ARCore camera API. We would be interested to know more about the inverted color problem on Xiaomi devices. Since this is likely unrelated to the black screen problem could you please create a separate issue including details about the specific device?

ptc-epassaro commented 2 weeks ago

@IrfanKMT glad to know that it works on the A55 now! We will keep investigating the issue on the F13 and in apps that don't use ARCore and will update this thread with our findings.

Thank you all for all the info!

IrfanKMT commented 1 week ago

@IrfanKMT glad to know that it works on the A55 now! We will keep investigating the issue on the F13 and in apps that don't use ARCore and will update this thread with our findings.

Thank you all for all the info!

@ptc-epassaro Did you get any solution for Samsung F13. If you found something it will help to us. Thank you for your support.

ptc-epassaro commented 1 week ago

Hi @IrfanKMT, the only update is that we found a way to reproduce this issue on Exynos/Mali-based devices. We're still working on a solution though. We will keep you posted as soon as we have something new.

Thank you for the patience!

IrfanKMT commented 1 week ago

Hi @IrfanKMT, the only update is that we found a way to reproduce this issue on Exynos/Mali-based devices. We're still working on a solution though. We will keep you posted as soon as we have something new.

Thank you for the patience!

@ptc-epassaro Thank you for the update!