Call for testing: Google/Huawei Nexus 6P (angler) owners
-
Sorry, I haven't tried it yet. It feels like it is something else that is not working maybe @Flohack could help you out here.
-
@Rondarius That's what I was thinking. Re-installed Android worked, bootloader is 3.68 and is working and able to reboot to bootloader or recovery, radio is 3.81. No errors installing anything after re-installing android, it all said ok. But then, no boot.....
-
@rocket2nfinity did it work with 4 cores before?
-
@Flohack Never tried it. Always had it running on 8
-
@Flohack 8-core TWRP still works just fine. Android works with all 8 cores enabled
-
@rocket2nfinity Please try to verify whats in the pst:
- Phone reset to stock Android 7.1.2 by Google
- Bootloader unlocked
- Please paste output of halium-install
I am about to preparing a custom script for the UBports installer, that will make things much easier to handle
-
@Flohack Android stock 7.1.2 - check
bootloader unlocked - checkoutput of hallium -install script:
Debug: Chosen rootfs is ubports-touch.rootfs-xenial-armhf.tar.gz
Debug: Chosen android image is system.img
Debug: Chosen release is ut
Debug: Compress images before pushing: falseI: Writing rootfs into mountable image
I: Writing android image into mountable image
I: Running post installation tasks
enabling Mir ... [done]
enabling SSH ... [done]
Please enter a new password for the user 'phablet':
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
I: Shrinking images
e2fsck 1.44.1 (24-Mar-2018)
resize2fs 1.44.1 (24-Mar-2018)
Resizing the filesystem on .halium-install-imgs.eazbo/system.img to 48516 (4k) blocks.
The filesystem on .halium-install-imgs.eazbo/system.img is now 48516 (4k) blocks long.I: Unmounting images
I: Pushing rootfs and android image to /data via ADB
I: Pushing rootfs to /data via ADB
adb: error: connect failed: closed
I: Pushing android image to /data via ADB
adb: error: connect failed: closedreal 0m0.016s
user 0m0.003s
sys 0m0.004s
I: Cleaning up
umount: .halium-install-rootfs.1KyDM: not mounted.
error: closed -
This post is deleted! -
@rocket2nfinity said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
adb: error: connect failed: closed
I: Pushing android image to /data via ADB
adb: error: connect failed: closedYes the data cant be pushed to the device. Maybe you have multiple adb´s on your computer and they are fighting with each other? I had this once.
-
@Flohack Tried on two computers, one I am sure only has one copy of adb. Same result
-
@rocket2nfinity Its just strange that it worked for many people but you
-
@Flohack It worked for me before too using your rootfs from your server. But with the new rootfs it hangs
-
@Flohack what does the "ut" after -p do in the hallium-install script?
-
@Flohack Oops! I do have two adb installed on both machines. Forgot that I used both and needed su adb to flash a ROM to a Mediatek device.
Thanks for the tip!
-
@rocket2nfinity -p sets the postprocessing to Ubuntu Touch type. Without that the rootfs is not prepared in the right way, for example ssh wont work etc.
-
@Flohack So, what's changed in the build? Calls and camera still appear to be not functional, although it seems smoother somehow. Rotation is not working. GPS is working. Accelerometer and compass are not - not sure if they ever were. Just discovered this handy sensor status app in the open store.
It does not appear to be syncing up with the main UBPorts daily builds. Is it supposed to? - no menu option under updates to specify channel. I flashed the rootfs from the cli site and halium and system from your site as instructed.
Running on 8-cores by the way. Smooth as butter.
-
@Flohack I do see one thing is running - VoLTE!
I got no audio, but it just made a call using VoLTE
-
@rocket2nfinity How do you know that?
-
@rocket2nfinity Yes there is no device channel yet for the phone so no daily updates, and no channel options. That will hopefully change once we got calls fixed.
I also saw that rotation stopped working. Hmmm thats really strange.
The reason for this update was that before I had to tweak the rootfs manually, but now with the new system.img you can grab the latest devel nightly and install if needed, so I dont have to do anything anymore. That was the first step to getting it into an update channel ^^ -
@Flohack First thing I noticed was "L" in the navbar for network. Don't know what you all did, but before it said 4g. So, I made a test call and noticed the L drop to 3G and then go back to L after I hung up. That is exactly what it used to do when using VoLTE. Checked ofono list-modems (which is the closest I can come, unless there is a better way, to getting the info in ##4636#"#*) bearer is LTE - which according to the ofono manual would not be possible unless the device is VoLTE capable.
So, just for fun, went back to Android just to check network preferences under ##4636## and sure enough it says LTE auto ps preferred which is VoLTE. Re-flashed UT and it retains the network state. How did you all accomplish that? Didn't do that until the new rootfs.
Edit: star pound star pound 4636 pound star pound star is the proper command. The forum auto formatting for some reason doesn't like me typing that command in
