Forums » Bugs
background cannot be disabled on android
disabling background in graphics settings (background quality off) does nothing. expect black background, still see stars etc. changing driver does not change outcome.
tested on..
samsung tab a, android 7 stock
snapdragon quad core, 2gb ram, Adreno 504
samsung note5, (sm-n920w8) android 7 stock
snapdragon octa core, 4gb ram, Mali-T760
samsung note5, (sm-n920c) android 7 rooted
exynos octa core, 4gb ram, Mali-T760
samsung s8 (sm-g950w) android 9 stock
snapdragon octa core, 4gb ram, Adreno 540
samsung note9, sm-n960w, android 10 stock (not tested recently)
snapdragon octa core, 6gb ram, Adreno 630
pretty sure ive tested it on the samsung s6 (sm-g920f) but not recently
exynos octa core, 3gb ram, Mali-T760
ive had conversations in 100 with people using various models i have not tested and their results appear to be the same.
tested on..
samsung tab a, android 7 stock
snapdragon quad core, 2gb ram, Adreno 504
samsung note5, (sm-n920w8) android 7 stock
snapdragon octa core, 4gb ram, Mali-T760
samsung note5, (sm-n920c) android 7 rooted
exynos octa core, 4gb ram, Mali-T760
samsung s8 (sm-g950w) android 9 stock
snapdragon octa core, 4gb ram, Adreno 540
samsung note9, sm-n960w, android 10 stock (not tested recently)
snapdragon octa core, 6gb ram, Adreno 630
pretty sure ive tested it on the samsung s6 (sm-g920f) but not recently
exynos octa core, 3gb ram, Mali-T760
ive had conversations in 100 with people using various models i have not tested and their results appear to be the same.
Thanks, we'll take a look.
No background change nor detail change (looks like stuck on highest setting).
Same results tried on a samsung s10 (exynos) android 10, 8gb ram.
Samsung a90 5g (snapdragon 855) android 10, 6gb ram
Samsung tab s7 (snapdragon 865) android 10, 6gb ram
All tested on ES3 driver and ES2 driver
Same results tried on a samsung s10 (exynos) android 10, 8gb ram.
Samsung a90 5g (snapdragon 855) android 10, 6gb ram
Samsung tab s7 (snapdragon 865) android 10, 6gb ram
All tested on ES3 driver and ES2 driver
This should be fixed now.