Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Unity 2018.3 is now released.
    Dismiss Notice
  6. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

[BUG] Performance of Canvas UI on some Android devices

Discussion in 'Project Tiny' started by Ballabumbu, Feb 11, 2019.

  1. Ballabumbu


    Aug 17, 2018
    Hi all,
    we are currently running into severe performance issues on some android devices.
    Seems like interactable Canvas / UI Elements are drastically reducing the frame-rate on some Android versions. We can reproduce the issue with the Tiny Arms Revenge Unity Example as well.
    Tap responsiveness on UI Elements becomes unreliable / slow.
    Changing the build settings from WebGL to Canvas to Auto seems to have no effect.
    On iOS performance was good on all devices.

    Here is a list of Android devices we were able to test on:

    bugged in mobile view NOT in desktop view:

    Android 8.0.0​

    bugged in mobile AND desktop view:

    Android 9​

    Android: 8.0.0​

    NOT bugged in desktop or mobile view:

    Android 5.1.1​

    NOT bugged in mobile and desktop

    As you can see older Android versions seem to have no problems.

    Please have a look at it! It seems related / similar to that older Bug-report:
    Maybe it's not totally fixed / reapearing issue?

    Thanx a lot!
    Last edited: Feb 12, 2019
    Zoelovezle likes this.
  2. raymondyunity


    Unity Technologies

    Apr 30, 2018
    Thanks for the feedback. Looks like it's affecting new Samsung phones. I can see it happen on a SM-J701M (Android 7.0.0) as well. Unfortunately, fixes towards runtime improvements are stalled until C# is out. Sorry for the inconvenience. I have noted this issue though.
    Zoelovezle likes this.