Search Issue Tracker
Duplicate
Votes
1
Found in
2018.4
2019.4
2020.3
2021.1
2021.2
Issue ID
1337462
Regression
No
[Android] SystemInfo ARM big.LITTLE configuration reports 1 big + 7 little (instead of 4+3+1) for CPUs with 4+3+1 configuration
For CPUs that have 4 silver + 3 gold + 1 prime cores configuration, Unity SystemInfo ARM big.LITTLE configuration reports 1 big + 7 little.
Currently, Unity has a hard-coded threshold that treats all cores < 85% capacity as little cores.
Steps:
1. Clean device logcat: adb logcat -c
2. Build and Run New Empty Project on Android device with 4+3+1 cores configuration
3. In Terminal:
- if on Windows: adb logcat | findstr "SystemInfo ARM"
- if on macOS: adb logcat | grep -F "SystemInfo ARM"
Expected: Terminal output: SystemInfo ARM big.LITTLE configuration reports 4+3+1 configuration.
Actual: Terminal output: SystemInfo ARM big.LITTLE configuration: 1 big (mask: 0x80), 7 little (mask: 0x7f)
Reproduced with:
Samsung Galaxy S21 5G, Qualcomm Snapdragon 888, 4x ARM Cortex-A55 @ 1804MHz, 3x ARM Cortex-A78 @ 2419MHz, ARM Cortex-X1 @ 2841MHz, Adreno (TM) 660
VLNQA00362 Samsung Galaxy Z Fold2 5G (SM-F916U1) 11 Snapdragon 865 SM8250 Adreno (TM) 650
(user's info) Snapdragon 870 device
Reproduced with: 2018.4.35f1, 2019.4.27f1, 2020.3.8f1, 2021.1.9f1, 2021.2.0a18.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1349057