UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Ubuntu-Touch OTA-8 Nexus 5 Issues

    Scheduled Pinned Locked Moved Support
    8 Posts 7 Posters 952 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • shapleyS Offline
        shapley
        last edited by

        Hi All,

        I hope this is just my experience since upgrading to OTA-8 but there are a couple of issues;

        1. Slower startup to the screen authentication.
        2. Anbox freeze when starting android apps.
        3. Slow icon redraw after scrolling.
        4. When you plug in a slimport cable the screen digitiser won't display a 'pointer arrow'.
        5. Generally more sluggish performance.
        1 Reply Last reply Reply Quote 0
        • H Offline
          htc_tattoo
          last edited by

          Unfortunately i had the same experience. N5 gets warm, eats battery and does hardly respond after upgrading to OTA-8.
          As much as i could see the network-manager was using more than 50% of CPU. But i didn't have time (and skills) to search deeper.
          Switching to RC-channel fixed it, but i would prefer to stay on stable channel...

          advocatuxA 1 Reply Last reply Reply Quote 0
          • D Offline
            domubpkm
            last edited by domubpkm

            I am not a specialist and i don't know if it could solve some of these problems but i have often read on the forum that make a round-trip dev channel /stable channel could fix sometimes dysfunctions. Why a round-trip favourably impact, i don't know also.

            1 Reply Last reply Reply Quote 0
            • advocatuxA Offline
              advocatux @htc_tattoo
              last edited by

              @htc_tattoo hi, currently the rc image and OTA-8 image in stable are the same.

              Were you running anbox or something like that? I have a Nexus 5 which battery doesn't get warm, and network-manager doesn't eat the battery 😉

              H 1 Reply Last reply Reply Quote 0
              • ? Offline
                A Former User
                last edited by

                Number 4 is a known bug: https://github.com/ubports/ubuntu-touch/issues/301

                1 Reply Last reply Reply Quote 0
                • S Offline
                  schouk
                  last edited by schouk

                  Hi,

                  I had the same issue. Disabling anbox fixed the performance issues:

                  anbox-tool disable
                  

                  After that I saw that

                  anbox-tool status
                  

                  said "Kernel: NOT OK"

                  So I repeated the steps in the documentation: https://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html#how-to-install
                  It did not work with the first try. So I executed the steps of the troubleshooting paragraph: https://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html#troubleshooting and then again the steps above...

                  After that Anbox works again 🙂

                  1 Reply Last reply Reply Quote 0
                  • H Offline
                    htc_tattoo @advocatux
                    last edited by

                    @advocatux Yes, i was running anbox on a fresh OTA-7 install. Switching to OTA-8 made it slow, switching to RC-channel installed version 36 and gave the performance back.
                    Now i tried to switch back to stable (version 6) and it works as well. But it removed anbox.
                    After reinstalling anbox (following to the documentation) my N5 works with OTA-8 and anbox.

                    1 Reply Last reply Reply Quote 1
                    • K Offline
                      kugiigi
                      last edited by

                      I think these experiences has been known to happen when upgrading with Anbox installed.
                      Maybe a note about this should be added in the Anbox documentation.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post