Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.2.1p1
Issue ID
1013215
Regression
No
[Android] SystemInfo.systemMemorySize returns the incorrect value for One Plus 5 and Samsung S9+
To reproduce:
1. Open project
2. Build and run on Android on One Plus 5 or Samsung S9+
3. Notice that:
-On a Samsung S9+ (model number: Samsung SM-G965F), observe 1099MB being shown (instead of 6GB)
-On a OnePlus ONEPLUS A5000 (specifically: Android OS 8.0.0 / API-26 (OPR1.170623.032/119))
Observe the result as 1618MB or 3622MB instead of 8GB
-On another device(e.g. Nexus 6, it shows ~3GB as expected)
Reproduced: 5.6.4p1, 2017.1.3p4, 2017.2.1p3, 2017.3.2f1, 2017.4.3f1, 2018.1.0f2, 2018.2.0b3
-----
Fixed in 2018.3. For earlier versions see: https://forum.unity.com/threads/systeminfo-systemmemorysize-return-weird-value-on-samsung-s9.527096/#post-3637195
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Unity-Nikos
Sep 04, 2018 09:25
Fixed in 2018.3. For earlier versions see: https://forum.unity.com/threads/systeminfo-systemmemorysize-return-weird-value-on-samsung-s9.527096/#post-3637195
NiallSoe
Aug 16, 2018 09:52
Which release has this been fixed in?