Call for testing: Google/Huawei Nexus 6P (angler) owners
-
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.
-
@spotlight207 This did the trick for me! Thanks a ton for the suggestion, I've now got a working UT device
-
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!
-
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.
-
Great news, Bluetooth is working now! I will update the files on the Nextcloud drive tomorrow. Then you can try this as well
-
Anyone have info on resetting to Android 7.1? Can't find those files anywhere
edit: found this here: https://dl.google.com/dl/android/aosp/angler-n4f26j-factory-01874fd6.zip
Supposedly 7.1.1 stock rom for anyone else looking
-
@kodaxx said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
https://dl.google.com/dl/android/aosp/angler-n4f26j-factory-01874fd6.zip
Thanks, adding it to the document.
-
@Flohack Is calling via Bluetooth working as well or is it just sending a files/streaming music?
-
@Stefano calling would work for sure but there is no audio yet in calls, regardless of normal handset, or speakerphone, or headset. Its a problem of audio data not routed correctly to/from the modem, and I will work on that soon. See also feature list above
-
Trying it all out now!
-
@phillip-walters Have you been successful?
-
@phillip-walters if you get exec format error then probably you have downloaded the 64bit rootfs, which is not yet possible to be installed with halium-install. Please try 32bit
-
Stuck at boot logo, here is the output of my dmesg. Any thoughts?
-
@kodaxx I can see you are in Telnet rescue mode. Thats not good, somethings then wrong with the installation. Can you telnet to the given address in dmesg and inside your phone, press again dmesg and you post this output?
-
This post is deleted! -
This post is deleted!
