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

Call for testing: Google/Huawei Nexus 6P (angler) owners

Scheduled Pinned Locked Moved Porting
627 Posts 43 Posters 447.0k Views 13 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.
    • F Offline
      flohack
      last edited by 15 Jan 2020, 21:53

      Ok we are good to go! 32bit ARMHF image confirmed to work here.

      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

      1 Reply Last reply Reply Quote 0
      • K Offline
        kodaxx
        last edited by 16 Jan 2020, 05:46

        Can the halium-install script be run on osx?

        F 1 Reply Last reply 16 Jan 2020, 07:41 Reply Quote 0
        • F Offline
          flohack @kodaxx
          last edited by 16 Jan 2020, 07:41

          @kodaxx Oh I have to ask, but I see those dependencies:

          qemu-user-static
          qemu-system-arm
          e2fsprogs
          simg2img

          I am not sure you will be able to have commands from those packages avaiable in OSX.

          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

          F 1 Reply Last reply 16 Jan 2020, 07:42 Reply Quote 0
          • F Offline
            flohack @flohack
            last edited by flohack 16 Jan 2020, 07:42

            @kodaxx The problem is that the images must be mounted (ext4 file system), converted from sparse to full image for the system.img etc. Those things might be specific. On the other hand, if you can build Android on Mac, maybe, then this tools could be available. Otherwise maybe you can try a virtual machine with Ubuntu?

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

            K 1 Reply Last reply 16 Jan 2020, 18:39 Reply Quote 0
            • W Offline
              wbrawner
              last edited by 16 Jan 2020, 12:39

              @Flohack I'm able to get the install to happen but the device doesn't boot. It gets stuck at the Google splash screen indefinitely. I put some more details in the pad. Any ideas where to go from here?

              F 1 Reply Last reply 16 Jan 2020, 13:49 Reply Quote 0
              • F Offline
                flohack @wbrawner
                last edited by 16 Jan 2020, 13:49

                @wbrawner Do you get an RNDIS connection to be able to ssh in? Anything in your hosts dmesg ? If not, let it sit for a while, then boot into recovery with VOl-UP and holding power, and then do cat /sys/fs/pstore/console_ramoops and see if thats says smth

                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                W 1 Reply Last reply 16 Jan 2020, 14:15 Reply Quote 0
                • W Offline
                  wbrawner @flohack
                  last edited by 16 Jan 2020, 14:15

                  @Flohack Here's some info I posted in the pad: https://pastebin.com/fycE5rG4 https://pastebin.com/gtUsAUhg

                  Here's the output of /sys/fs/pstore/console-ramoops: https://pastebin.com/1Htmi5iN

                  I tried to SSH in with phablet@10.15.19.82 but I get connection refused.

                  1 Reply Last reply Reply Quote 0
                  • W Offline
                    wbrawner
                    last edited by 16 Jan 2020, 15:05

                    @Flohack I did a reinstall of LineageOS, did a factory reset from TWRP, and reinstalled UT. Now I've been able to SSH in but I'm still stuck at the Google boot logo

                    W F 2 Replies Last reply 16 Jan 2020, 15:09 Reply Quote 0
                    • W Offline
                      wbrawner @wbrawner
                      last edited by 16 Jan 2020, 15:09

                      Here's the output of /sys/fs/pstore/console-ramoops again, this time from the SSH session: https://paste.centos.org/view/ded52881

                      1 Reply Last reply Reply Quote 0
                      • K Offline
                        kodaxx @flohack
                        last edited by 16 Jan 2020, 18:39

                        @Flohack I will try it from a live install

                        1 Reply Last reply Reply Quote 0
                        • F Offline
                          flohack @wbrawner
                          last edited by 16 Jan 2020, 19:05

                          @wbrawner SSH is a good sign. Can you please verify you got the /system/vendor folder with some content? Also check if /etc/init/rsyslog.override exists. Finally, is rsyslogd daemon running?

                          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                          W 1 Reply Last reply 16 Jan 2020, 20:08 Reply Quote 0
                          • F Offline
                            flohack
                            last edited by 16 Jan 2020, 19:29

                            I am following now again my guide to see if I got the same issue.

                            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                            1 Reply Last reply Reply Quote 0
                            • F Offline
                              flohack
                              last edited by 16 Jan 2020, 19:51

                              Hmm sorry to say, it worked for me with the first flash. Strange.

                              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                              1 Reply Last reply Reply Quote 0
                              • W Offline
                                wbrawner @flohack
                                last edited by 16 Jan 2020, 20:08

                                @Flohack /system/vendor is populated and /etc/init/rsyslog.override exists. rsyslogd wasn't running though

                                1 Reply Last reply Reply Quote 0
                                • W Offline
                                  wbrawner
                                  last edited by 17 Jan 2020, 01:26

                                  @Flohack so I'm doing a bit of digging around. Lightdm is exiting for some reason: https://paste.centos.org/view/2dae5581

                                  The logs mention this /var/log/lightdm/unity-system-compositor.log file, so I took a look there: https://paste.centos.org/view/ead8190e

                                  This line stands out to me:

                                  Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
                                  std::exception::what: Failed to find platform for current system
                                  

                                  I'm still investigating but no leads as of now.

                                  1 Reply Last reply Reply Quote 0
                                  • S Offline
                                    spotlight207
                                    last edited by 17 Jan 2020, 02:36

                                    Unfortunately, the above issue also affects the Nexus 5X. Mir seems to die as it can't load the vendored libraries due to missing symbols. (Copying key parts beneath as the above paste expires in a day.)

                                    cannot locate symbol "atrace_end_body" referenced by "/android/vendor/lib/hw/hwcomposer.msm8992.so"...
                                    [1970-01-01 00:11:54.604946] <information> mirplatform: Found graphics driver: mir:android-caf (version 1.1.0) Support priority: 0
                                    cannot locate symbol "atrace_end_body" referenced by "/android/vendor/lib/hw/hwcomposer.msm8992.so"...
                                    [1970-01-01 00:11:54.613499] <information> mirplatform: Found graphics driver: mir:android (version 1.1.0) Support priority: 0
                                    ERROR: /build/mir-1.2.0+0~20191220231858.24~1.gbp4edda9/src/server/graphics/default_configuration.cpp(172): Throw in function mir::DefaultServerConfiguration::the_graphics_platform()::<lambda()>
                                    Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorstd::runtime_error >
                                    std::exception::what: Exception while creating graphics platform
                                    ERROR: /build/mir-1.2.0+0~20191220231858.24~1.gbp4edda9/src/platform/graphics/platform_probe.cpp(109): Throw in function std::shared_ptrmir::SharedLibrary mir::graphics::module_for_device(const std::vector<std::shared_ptrmir::SharedLibrary >&, const mir::options::ProgramOption&, const std::shared_ptrmir::ConsoleServices&)
                                    Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorstd::runtime_error >
                                    std::exception::what: Failed to find platform for current system

                                    The closest explanation I've been able to find is that these functions were added in Oreo, compared to Nougat which the system is currently built with. I would guess to try and downgrade the vendor image to something from 7.1.2, but it should be noted this causes my Nexus 5X to bootloop. Perhaps the 6P will have better luck.

                                    W 1 Reply Last reply 17 Jan 2020, 03:40 Reply Quote 0
                                    • W Offline
                                      wbrawner @spotlight207
                                      last edited by 17 Jan 2020, 03:40

                                      @spotlight207 This did the trick for me! Thanks a ton for the suggestion, I've now got a working UT device πŸ™‚

                                      1 Reply Last reply Reply Quote 0
                                      • F Offline
                                        flohack
                                        last edited by 17 Jan 2020, 17:24

                                        Wow, why it worked for me then? Do wwe have different vendor partitions? OMG I should say you need to reset your device to Android 7.1 before!

                                        My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                        1 Reply Last reply Reply Quote 0
                                        • F Offline
                                          flohack
                                          last edited by 17 Jan 2020, 17:38

                                          Ok I adapted the installation instructions. You MUST reset your device from anything it had to Android 7.1 in order to get the right firmware and vendor partition.

                                          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                          1 Reply Last reply Reply Quote 1
                                          • F Offline
                                            flohack
                                            last edited by 17 Jan 2020, 23:53

                                            Great news, Bluetooth is working now! I will update the files on the Nextcloud drive tomorrow. Then you can try this as well πŸ˜‰

                                            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                            S 1 Reply Last reply 18 Jan 2020, 09:59 Reply Quote 1
                                            26 out of 627
                                            • First post
                                              26/627
                                              Last post