Search Issue Tracker

Won't Fix

Votes

1

Found in

2022.3.10f1

Issue ID

UUM-49145

Regression

No

[Android] Black squares or white squares appear in random locations on the device's screen

-

Steps to reproduce:
1. Open the attached “FlickeringTerrainIssue” project
2. Open “AlienMap” scene
3. Delete “AlienMap_Main_Grp/AlienTerrain/35a7fa360c0bc7b0af4c-bf0e-4b49-8048-35a7fa360c0b” GameObject in the Hierarchy window and save the scene to fix “Tree prefab at index 0 is missing.” error
4. Build And Run the project on the device
5. Observe the device’s screen in landscape

Expected result: There are no visual glitches
Actual result: Black and white squares flicker on the screen

Reproducible with: 2022.3.3f1, 2022.3.10f1
Not reproducible with: 2021.3.30f1, 2022.3.2f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6

Reproducible on: macOS Ventura 13.5 (Intel)
Not reproducible on: No other environment tested

Reproducible with devices:
VLNQA00513 - OnePlus Nord N10 5G (BE2029), CPU: Snapdragon 690 SM6350, GPU: Adreno 619, OS: 11
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
One Plus 11R 5G (by user)
Real Me 3PRO (by user)
Motorola Moto G40 (by user)
POCO F3 GT (by user)

Not reproducible with devices:
VLNQA00498 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 13
VLNQA00336 - HUAWEI Y6p (MED-LX9N), CPU: MediaTek MT6762R, GPU: PowerVR Rogue GE8320, OS: 10
VLNQA00146 - HTC 10 (HTC 10), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.0
VLNQA00017 - Huawei Nexus 6P (angler), CPU: Snapdragon 810 MSM8994, GPU: Adreno 430, OS: 8.0.0
iPhone 12 mini (iOS 14.1)

Notes:
- Could not reproduce the issue when recording a video using adb and adub or a built-in screen recorder

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.