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

rocket2nfinity · 23 Apr 2020, 21:31

@Flohack Never tried it. Always had it running on 8

rocket2nfinity · 23 Apr 2020, 21:34

@Flohack 8-core TWRP still works just fine. Android works with all 8 cores enabled

flohack · 24 Apr 2020, 18:47

@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

rocket2nfinity · 25 Apr 2020, 01:42

@Flohack Android stock 7.1.2 - check
bootloader unlocked - check

output 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: false

I: 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: closed

real 0m0.016s
user 0m0.003s
sys 0m0.004s
I: Cleaning up
umount: .halium-install-rootfs.1KyDM: not mounted.
error: closed

rocket2nfinity · 25 Apr 2020, 01:44

This post is deleted!

flohack · 25 Apr 2020, 15:53

@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: closed

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

rocket2nfinity · 25 Apr 2020, 18:26

@Flohack Tried on two computers, one I am sure only has one copy of adb. Same result

flohack · 25 Apr 2020, 18:28

@rocket2nfinity Its just strange that it worked for many people but you

rocket2nfinity · 25 Apr 2020, 18:33

@Flohack It worked for me before too using your rootfs from your server. But with the new rootfs it hangs

rocket2nfinity · 25 Apr 2020, 18:39

@Flohack what does the "ut" after -p do in the hallium-install script?

rocket2nfinity · 25 Apr 2020, 18:53

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

flohack · 25 Apr 2020, 19:44

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

rocket2nfinity · 26 Apr 2020, 00:06

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

rocket2nfinity · 26 Apr 2020, 00:09

@Flohack I do see one thing is running - VoLTE!

I got no audio, but it just made a call using VoLTE

flohack · 26 Apr 2020, 12:34

@rocket2nfinity How do you know that?

flohack · 26 Apr 2020, 12:36

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

rocket2nfinity · 26 Apr 2020, 14:57

@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

rocket2nfinity · 26 Apr 2020, 15:41

@Flohack I also just turned off the apns for cellular to disconnect from network. Tried making a phone call with only wifi and it connected! (Again with no sound, but I can hear dial tones through the receiving phone when I press them on the cell phone). It also did not do that before.

In this case I can't conclusively say that it made a call using WiFi because something is broken in cellular settings APN (it doesn't properly report my current network settings). However, it did show unknown network state in navbar after I disconnected the APNs.

So without faith in the cellular settings, and no way to control or test it in UT network settings, I'm thinking it's possible Wi-Fi calling is on as well. It is, in the 4636 settings under Android. When I had it on Android, those features just worked unless I manually turned it off. For fun, when I re-flashed to check Android 4636, I did test it and VoLTE and Wi-Fi calling was on and functional.

rocket2nfinity · 26 Apr 2020, 16:12

I'm thinking it's possible you guys didn't do anything to enable VoLTE, maybe T-mobile did. They are moving much faster than expected on their Network reconfiguration and are whitelisting any device that is VoLTE capable of their Network. Maybe it was always capable under UT and they just turned it on.

flohack · 26 Apr 2020, 17:26

@rocket2nfinity There is a possibility that a modem will negotiate VoLTE by itself, yes. But we cannot query for it nor turn it on or off, so we will never know ^^ except your provider does VoLTE-only mode