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

spotlight207

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

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

flohack

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!

flohack

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.

flohack

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

kodaxx

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

flohack

@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.

Stefano

@Flohack Is calling via Bluetooth working as well or is it just sending a files/streaming music?

flohack

@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

phillip.walters

Trying it all out now!

flohack

@phillip-walters Have you been successful?

flohack

@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

kodaxx

dmesg

Stuck at boot logo, here is the output of my dmesg. Any thoughts?

flohack

@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?

kodaxx

This post is deleted!

kodaxx

This post is deleted!

kodaxx

https://pastebin.com/V8KPpS3q

Actually looks like I'm getting some install errors that I didn't notice before..

The relevant bit being:

adb: error: failed to copy '.halium-install-imgs.Zzv9k/rootfs.img' to '/data/rootfs.img': remote I/O error
.halium-install-imgs.Zzv9k/rootfs.img:....1 MB/s (2194800640 bytes in 257.129s)
I:    Pushing android image to /data via ADB
adb: error: failed to copy '.halium-install-imgs.Zzv9k/system.img' to '/data/system.img': remote Read-only file system
.halium-install-imgs.Zzv9k/system.img:... 1079.7 MB/s (1310720 bytes in 0.001s)

real	4m17.556s
user	0m0.107s
sys	0m0.762s
Error: Couldn't copy the files to the device, is it connected?
I: Cleaning up
umount: .halium-install-rootfs.oRFiq: not mounted.

flohack

@kodaxx Did you wipe your system before? It might be needed if the partition was encrypted. In your TWRP, format all partitions and try again. A readonly filesystem can only be this, I hope

kodaxx

@Flohack yes, I have completely wiped. I have pushed other files with no issue. When I run the tool, it looks like it's working, once it gets to 100% pushing rootfs, I get this error and everything fails.

At that point, pushing other files does not work either until I remount or wipe, and running the tool again immediately fails

flohack

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

shing other files does not work either until I remount or wipe, and running the tool again immediately fails

Can you try to psuh those files manually with adb? Lets at least see if that works. I dont want to tell it, but it might be that your flash ram is faulty.