Terrible rendering performances on OnePlus 3T

Our 2D mobile game is performing great on a wide range of devices, keeping a steady 30fps frame rate.
Unfortunately, on OnePlus 3T this doesn't happen: no matter what's on the screen, it keeps having very high frame times, often over 100ms.

There are approximately 60 draw calls, handled without a single hiccup by older devices (such as OnePlus One, for instance). OnePlus 3T used to perform good, and I suppose those issues shown up when we upgraded from Unity 2018.2.x to 2018.3.x.

I tried several different build configurations, such as:
- use OpenGLES3, OpenGLES2 or Vulkan
- disabling Multithreaded Rendering
- disabling Static and/or Dynamic Batching
- disabling GPU skinning
- enabling Graphics Jobs, Lightmap Streaming, Protect Graphics Memory, Frame Timing Stats
- using IL2CPP or Mono
- targeting ARMv7 or ARM64
- enabling Sustained Performance Mode
- disabling Prebake Collision Meshes, Keep Loaded Shaders Alive or internal profiler
- changing all vertex compression settings
- disabling Optimize Mesh Data

None of those improved its performances.

I'm using the lowest graphical settings available, forward rendering path with no shadows, HDR, antialiasing, lightmaps, fog, reflection probes nor soft particles.

This is a glimpse of the profiler:



Has anybody experienced anything similar, or has some clue on how to solve it?
Thanks

 

The same problem for me... extremely bad performance on that device

 

@aleksandrk I'm now on 2018.4.0f1, but it surely had same issues also on 2018.3.7f1, 2018.3.8f1, 2018.3.11f1 and 2018.3.12f1.

 

@aleksandrk I'd like to, but I'm quite sure I won't be able to narrow down the issue into a repro.
Do you think it will be worth submitting a bug report even without it (IE posting profiler screens only)?

 

I'm sorry, I cannot submit this project.

My OnePlus 3T device is currently running OxygenOS 5.0.8, Android 8.0.0, sec patch 2018-11-01, kernel 3.18.66-perf+ (2018-12-06), build ONEPLUS A3003_28_181206, and it should be the latest stock available to date.

 

Ok, I'll send you a DM.

Meanwhile, I reported this bug attaching several data samples collected from the profiler under different build configurations and running on different phones (OnePlus 3T, OnePlus One and Honor 7)

https://fogbugz.unity3d.com/default.asp?1154989_so11mjogcfns1i5d

 

@aleksandrk, I think I found the main culprit for this behavior.

I have 2 Screen-Space Canvases that reference a moving camera: if I switch their rendering mode to Overlay, performances improve dramatically on OnePlus 3T.

On the other phones I tested, there's no performance cost in using Screen-Space mode compared to Overlay.

The strange thing is that profiler never reported any significant time consumption in the UI section.