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

flohack · 15 Jan 2020, 19:33

@wbrawner Sounds interesting, isn´t it ^^

kodaxx · 15 Jan 2020, 21:03

@Flohack said in Call for testing: Google/Huawei Nexus 6P (angler) owners:

https://pad.ubports.com/p/nexus-6p-alphatesting

Got recovery installed, ready to go for the next step

flohack · 15 Jan 2020, 21:35

I am nearly done with preparations and uploading. But I found we can only use 32bit rootfs for the moment, so I am finishing this now. Should be ready in 20mins...

flohack · 15 Jan 2020, 21:53

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

kodaxx · 16 Jan 2020, 05:46

Can the halium-install script be run on osx?

flohack · 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.

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?

wbrawner · 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?

flohack · 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

wbrawner · 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.

wbrawner · 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

wbrawner · 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

kodaxx · 16 Jan 2020, 18:39

@Flohack I will try it from a live install

flohack · 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?

flohack · 16 Jan 2020, 19:29

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

flohack · 16 Jan 2020, 19:51

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

wbrawner · 16 Jan 2020, 20:08

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

wbrawner · 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.

spotlight207 · 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.

wbrawner · 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