Hi cemas. This could be due to the recent addition of the mobile specific tonemapper cvar. From the Release Notes, see: New: Added “r.Mobile.TonemapperFilm” console variable which can be used to enable/disable new filmic tonemapper on Mobile devices, independently from Desktop platforms (disabled by default).
To see if it helps, you can try setting r.Mobile.TonemapperFilm 1