Call for testing: Google/Huawei Nexus 6P (angler) owners
-
@Flohack You asked in another thread what would prevent a person from recommending or using UT as a daily driver - that was one of the things in the American market. The other is the ability to videochat through an app or web app and push notifications for said apps. That's also very important in this time of quarantine. If we had that, I think it would be good to go.
I personally am very satisfied with the function of the OS and the apps and web apps available. You all have done a wonderful job bringing UT back to life. If I could just get notifications from those web apps that someone messaged, called or emailed me, I'd never look back at Android.
Two nice to have things that I wish was available are Redshift and Swype. I know Redshift is on the back burner for the moment. I posted GPL source code for the QT build of Swype that the Sailfish community created. I think the hangup there was an update to QT. Those are the only two features, other than videochat, that I miss - now that I've got VoLTE back.
-
Got every setup to
halium-install -p ut <rootfs.tar.gz> <system.img>
Unfortunately the install-script fires:
I tried it under macOS and Ubuntu 20.04 (in docker container). I also swapped between the standalone script and the full master branch but the error kept showing up.
I appreciate the project you guys are running here, I'd love to see UB Touch on my spare Nexus 6P,
Thanks you, Hannes
-
@harness Can @JBBgameich tell me whats going on here?
-
Guys can some of you try to install the 64bit rootfs? Download this https://ci.ubports.com/job/xenial-hybris-edge-rootfs-arm64/lastSuccessfulBuild/artifact/out/ubuntu-touch-hybris-xenial-edge-arm64-rootfs.tar.gz and follow the usual installation instruction with halium-install?
-
Ah and please can you test if rotation still works?
-
@Flohack Installed, keeping same system.img and halium-8-core boot
All works except:
rotation - broke when I switched to upstream rootfs last time
bluetooth - broke with this 64 bit rootfs. Worked before.
hotspot - don't think it ever worked
phone - Connects OK. Receives calls ok, but no audio.
developer mode - adb access to computer via usb
no accelerometer
no compass
camera won't even open now
No flashlight
-
@rocket2nfinity Ok so the rotation is interesting, so it was already on the 32bit? Bluetooth I need to take a look, I think I know what this is...
Thanks! You can switch back to 32bit if you like, no further testing so far from my side.
-
@Flohack Are you planning on making the N6P 64bit going forward? If so, then I'll just keep it. But if your'e planning on making armhf the default, then I'll change back. It had some hiccups that occasionally caused stalling and reboots on the 32bit upstream rootfs. But it's been running smooth on your 64 bit build.
-
@Flohack I also just realized that I did not see that you added anbox to the build and wanted us to test it. I'm happy to if you like.
-
@rocket2nfinity I think I still did not add Anbox patches but I will do.
As for 64bit, yes that should be the default in the future. I am happy to switch it in the instructions if its just Bluetooth. Unfortunately I still cannot install 64bit rootfs due to a bug with halium-install that cannot set the ssh password correctly. As soon as this is solved I look into the BT problem. I think its just one binary that needs to be exchanged
-
@Flohack Then I'm happy to stick with 64bit.
Please do add Anbox to the build. I'd love to test it on the N6P. I've been playing with it on the N5, but the N5 simply doesn't have the memory to run a lot of the android apps on top of UT.
I know anbox is sandboxed, but is there any way to give it at least camera and microphone access? I'm still hoping for any solution that would allow me to videochat on UT.
-
@rocket2nfinity >Yeah will do. Sorry, no hardwarea ccess is yet done, but we are looking for developers now, as the upcoming Volla Phone with Android 9 base should get this. So it is definitely planned ^^
-
@Flohack I am wondering how to check if I have successfully installed the 64 bit rootfs? This is how I Installed the files:
I didn't wipe the phone, instead I ran the flash-all.sh in the factory image and usually it did not install the the images, I installed them manually.
Everything was installed without any errors, when i checked for updates there was the old updates on apps that I had done before reflashing the phone. Rotation works too. -
@Rondarius erm you confuse me a bit with flash-all.sh - You would not do this if you want to change the UT root fs, just use the halium-install tool as mentioned in the docs.
-
Oh, I thought I had to reflash the phone to android.
4 Google Pixel 3A
1 Google Nexus 6P
2 Google Nexus 5
2 Pinephones
2 Sony Xperia X -
Why is the old installs of the apps still exists in the install history? and how do I check if I did install the new rootfs?
-
@Rondarius Oh no not really. Switching rootfs is very easy with UT. Why you see old Apps and settings? Because the roo file system is ready-only and can be replaced at any time, it wont hurt your apps or data. You would need to remove 2 folders in recovery if you really want to do this. later the installer will do this for you, when I managed to bring N6P to the installer
Best bet is that you try
file /bin/ls
and see what comes up. That would determine the bitness of the executable file, and therefor which rootfs is being used.
-
The terminal app crashes at launch
-
@Rondarius Yeah you now have 32bit apps installed that might be a problem. On the other hand that was preinstalled, not sure. You might have to use ssh via RNDIS, try ssh phablet@10.15.19.82
-
ssh worked and I used the ip-adress that the N6P was using on my network. I am runing 64 bit. When I reflashed the phone i didn't tuch the recovery image, that explains why I had all of the settings and apps from previous install.
