Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.3.0b2
Issue ID
965159
Regression
No
GetPixel() on a Texture2D will always return White on Android devices
Steps to reproduce:
1. Open user attached project "NawmalAR.zip"
2. Build for android device
3. Print or open image "P.png" on the monitor from "NawmalAR\Assets\NawmalAssets\images"
4. With the device point to the image so it gets recognized
5. The background for the image will always be white
Expected: Since there are color pickers set up, the background should try to be close to what is exactly around the image
Actual: The background is always white, regardless of actual background color (See repro video)
Reproduced on 2017.2.0p1, 2017.3.0b2, 2017.3.0b8
(2018.1.0a3 vuforia doesn't work at all)
Devices Under Test:
Xiaomi MI NOTE Pro*, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 430, Build:Xiaomi/leo/leo:7.0/NRD90M/7.10.12:user/release-keys
Xiaomi Mi 4i*, OS:5.0.2, CPU:arm64-v8a, GPU:Adreno (TM) 405, Build:Xiaomi/ferrari/ferrari:5.0.2/LRX22G/V8.1.5.0.LXIMIDI:user/release-keys
(Transparency of video lost, billboard background replaced with green, but bottom background repros like the others i.e. is all white)
Google Nexus 5X*, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 418, Build:google/bullhead/bullhead:8.0.0/OPR4.170623.009/4302492:user/release-keys
(Vuforia flipped upside down, but that is a known issue. This bug repros anyway)
Samsung SM G925F (Galaxy S6 Edge)*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zeroltexx/zerolte:7.0/NRD90M/G925FXXU5EQH6:user/release-keys
(Loads white background - repro, but doesn't load the billboard video, though you can hear the sounds)
HUAWEI EVA L19*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880, Build:HUAWEI/EVA-L19/HWEVA:7.0/HUAWEIEVA-L19/C432B386:user/release-keys
(Same as above - Loads white background - repro, but doesn't load the billboard video, though you can hear the sounds)
Samsung SM G928F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zenltexx/zenlte:7.0/NRD90M/G928FXXU3CQG2:user/release-keys
(Same as above, except for 2018.1.0a3)
(Crashes on 2018.1.0a3:
11-06 14:01:32.175 24860 24874 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 24874 (UnityMain)
11-06 14:01:32.175 3037 3037 W : debuggerd: handling request: pid=24860 uid=10078 gid=10078 tid=24874
11-06 14:01:32.176 3151 24979 D ExynosCamera: [CAM_ID(0)][]-DEBUG(m_companionThreadFunc):Companion Node(109) s_input)
11-06 14:01:32.176 3151 24979 D ExynosCamera: [CAM_ID(0)][]-DEBUG(m_companionThreadFunc):duration time( 39 msec)
11-06 14:01:32.249 24990 24990 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Whole log attached as well)
All devices were connected to the internet at the time of testing
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] The Error "ReleaseButton expects buttonId" is thrown when trying to add file using drag and hold in the Project Window
- Highlighted text is difficult to see in “Create Node” menu when Editor theme is set to light
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
Add comment