Call for testing: Google/Huawei Nexus 6P (angler) owners
-
@Flohack so I flashed the special TWRP and disabled the screen dimming so that the battery would just drain until it died. The percentage dropped to 0% and stayed there a while before the percentage just disappeared altogether. O had to leave for work but the phone still hadn't turned off by that point.
-
@wbrawner Sounds interesting, isn´t it ^^
-
@Flohack said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
Got recovery installed, ready to go for the next step
-
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...
-
Ok we are good to go! 32bit ARMHF image confirmed to work here.
-
Can the halium-install script be run on osx?
-
@kodaxx Oh I have to ask, but I see those dependencies:
qemu-user-static
qemu-system-arm
e2fsprogs
simg2imgI am not sure you will be able to have commands from those packages avaiable in OSX.
-
@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?
-
@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?
-
@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
-
@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.
-
@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
-
Here's the output of /sys/fs/pstore/console-ramoops again, this time from the SSH session: https://paste.centos.org/view/ded52881
-
@Flohack I will try it from a live install
-
@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?
-
I am following now again my guide to see if I got the same issue.
-
Hmm sorry to say, it worked for me with the first flash. Strange.
-
@Flohack /system/vendor is populated and /etc/init/rsyslog.override exists. rsyslogd wasn't running though
-
@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.logfile, so I took a look there: https://paste.centos.org/view/ead8190eThis 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 systemI'm still investigating but no leads as of now.
-
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 systemThe 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.
